text:
feat(noRestrictedImports): add import_names and allow_import_names settings

Summary
Extend noRestrictedImports with the option to use importNames and allowImportNames to specify the set of (dis)allowed imports.
Motivation:

The no-restricted-imports ESLint provides the feature.
Personal need: I needed it to make sure that when using the react-i18next library, I'm always retrieving the t function from the useTranslation hook, instead of using import { t } from 'i18next'.

Example Configuration
{
    "options": {
        "paths": {
            "lodash": "Using lodash is not encouraged",
            "underscore": "Using underscore is not encouraged",
            "import-foo": {
                "importNames": ["Bar"],
                "message": "Please use Bar from /import-bar/baz/ instead."
            },
            "import-bar": {
              "allowImportNames": ["Bar"],
              "message": "Please use only Bar from import-bar."
            }
        }
    }
}

Test Plan
Extensive snapshot tests for all different variations of import, import() and require() are included in this PR.

One thing which I'm not sure about, and which somebody else might be able to explain to me:
What is the reason for AnyJsImportLike (now renamed to AnyJsImportSourceLike) to target JsModuleSource instead of JsImport, just to then ignore all ocurrences of JsModuleSource that are not within a JsImport?

The compile errors must have snuck in during git rebase, will have a look at them later.

You may need to rebase, because currently there's a lot of unrelated commits included. Note that I recently did some work on the rule in the next branch, so it might be best to rebase on there instead of main.

You may need to rebase, because currently there's a lot of unrelated commits included.

There actually are no unrelated commits included, it's just a large amount of changes.
I'll split off the changes to framework code into one or more separate PRs to keep this PR cleaner.

Note that I recently did some work on the rule in the next branch, so it might be best to rebase on there instead of main.

Thanks for the pointer! I had a look at the changes in next. In my opinion, it might make sense to split off the extensions done in next into a fully separate noPackagePrivateImports rule altogether, because, except for the fact it's also analyzing imports, it's fully orthogonal to the rest of noRestrictedImports as implemented e.g. by the corresponding ESLint (and this PR).

In my opinion, it might make sense to split off the extensions done in next into a fully separate noPackagePrivateImports rule altogether, because, except for the fact it's also analyzing imports, it's fully orthogonal to the rest of noRestrictedImports as implemented e.g. by the corresponding ESLint (and this PR).

Hm, I just went in the other direction, but you make a fair point :sweat_smile:

What is the reason for AnyJsImportLike (now renamed to AnyJsImportSourceLike) to target JsModuleSource instead of JsImport, just to then ignore all ocurrences of JsModuleSource that are not within a JsImport?

The intention of that node was to query the actual specifier string. For top-level, JsModuleSource was the very node we need, however for dynamic import and require() there aren't specific nodes for that, so we needed to use the generic nodes.

Sorry about the rebase, I got rid of AnyJsImportSourceLike and had to adapt all code. All previous review comments should be resolved now, though.

Fixed the last few issues. Should be ready for merge now :+1:
Possible future work (in a separate PR):

Support for * and ** wildcards in import paths using biome_service::matcher::pattern (will follow up with that after this PR is merged)
Code action for removing the restricted imports (and/or replacing them with the correct import)
Separate severity per restricted import source and/or per restricted import name (useful for refactoring codebases). The noRestrictedImports lint is so flexible it is basic
Tweak schemars (and serde/biome_deserialize) such that the mutually exclusive nature of importNames and allowImportNames is respected/validated

Really nice work, @cr7pt0gr4ph7 !
Only thing I can think of is that the naming of importNames vs allowImportNames is a little weak. It sorta makes sense within the context, but I think it would be clearer of it were restrictedImportNames vs allowedImportNames (not also the change in tense).

I experimented with different possibilities (preventImportNames, rejectImportNames, forbidImportNames, denyImportNames and other synonyms), but I arrived at the conclusion that when looking at the resulting 'biome.jsonfiles, just usingimportNames` is more readable & still clear due to context:
{
	"$schema": "../../../../../../packages/@biomejs/biome/configuration_schema.json",
	"linter": {
		"rules": {
			"nursery": {
				"noRestrictedImports": {
					"level": "error",
					"options": {
						"paths": {
							"node:fs": "Importing from node:fs is forbidden",
							"bare-forbidden": {
								"importNames": [
									""
								]
							},
							"default-forbidden": {
								"importNames": [
									"default"
								]
							},
							"namespace-forbidden": {
								"importNames": [
									"*"
								]
							},
							"member-forbidden": {
								"importNames": [
									"forbidden1",
									"forbidden2",
									"forbidden3",
									"forbidden4",
									"forbidden5",
									"forbidden6",
									"forbidden7",
									"forbidden8",
									"forbidden9"
								]
							},
							"bare-allowed": {
								"allowImportNames": [
									""
								]
							},
							"default-and-member-allowed": {
								"allowImportNames": [
									"default",
									"allowed1",
									"allowed2",
									"allowed3",
									"allowed4",
									"allowed5",
									"allowed6",
									"allowed7",
									"allowed8",
									"allowed9"
								]
							},
							"namespace-allowed": {
								"allowImportNames": [
									"*"
								]
							},
							"member-allowed": {
								"allowImportNames": [
									"allowed1",
									"allowed2",
									"allowed3",
									"allowed4",
									"allowed5",
									"allowed6",
									"allowed7",
									"allowed8",
									"allowed9"
								]
							}
						}
					}
				}
			}
		}
	}
}

Support for * and ** wildcards in import paths using biome_service::matcher::pattern (will follow up with that after this PR is merged)

You might be interested in what @Conaclos is about to land: https://github.com/biomejs/biome/pull/4609
We plan to use that crate internally in our configuration

Thanks for the thorough response!
Maybe I could still suggest denyImportNames? But I'm happy either way :)

denyImportNames is a bit more self-explanatory, but importNames has the big advantage of being visually distinguishable from allowImportNames due to the different length, even when just skimming over a configuration file, which avoids mistakes. I'm usually always in favor of the self-explanatory name, but considering that these configurations may get pretty long in some cases. So I'd favor keeping importNames, but if general consensus favors a different name, that's also okay.
If no objections are made, this should be ready for merge now IMO.

Support for * and ** wildcards in import paths using biome_service::matcher::pattern (will follow up with that after this PR is merged)

You might be interested in what @Conaclos is about to land: #4609
We plan to use that crate internally in our configuration

Good pointer! Though even before #4609, RestrictedGlob is already available in biome_js_analyze.
I also left some notes on #4609.

authors: arendjr cr7pt0gr4ph7 ematipico

repo: biomejs/biome


text:
🛑 Biosimulations API is down

In b330015, Biosimulations API (https://api.biosimulations.org) was down:

HTTP code: 0
Response time: 0 ms

tracked in https://github.com/biosimulations/status/issues/17

Resolved: Biosimulations API is back up in 02e5e2d.

source: gharchive/issue

repo: biosimulations/status

license: MIT

license_type: permissive

license_source: github-api


text:
Set cplex problem logger name

The current behaviour will overwrite the root logger level of any application using optlang together with cplex (in practice silence most log output and confuse developers). This fix creates a logger with an explicit name instead of using root. I chose cplex.problem instead of __name__ since it's not actually a logger for the current module; not 100% sure what the best name is though.

Good point, that's definitely not good behaviour. Ideally I think the name should be more specific. It is possible to have several independent cplex instances at the same time, so I guess it might be nice to be able to see from the log which one it is. For now I'm just gonna merge this though.

source: gharchive/pull-request

authors: KristianJensen kvikshaug

repo: biosustain/optlang

license_source: bigquery


text:
Incorporate basic api

hookup basic api calls for looking up and querying genesets
change base url from /mygeneset.info-website to /
add copy button component
add loading/error states to geneset edit page
hookup geneset page to actual genesets from api
improve table sorting method (fix bug where two columns with identical keys dont get sorted properly
hookup actual api calls to "try it out" section
refactor "try it out" component, add tooltips
get rid of "GenesetEdit" HOC

geneset page redirect broken
_exists_:kegg query breaks results format


text:
🛑 Bangla Plex API is down

In 59a8ce4, Bangla Plex API (https://banglaplexapi.bymirrorx.eu.org/popular/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bangla Plex API is back up in cab9b69 after 7 minutes.


text:
Adding use state and use effect for react js cheatsheet

I want to add some basics of using use state and use effect in react

Sure go ahead

Someone else already updated it, so i added the useContext hook.
Also, i must mention that the previous contributor who added useState and useEffect blatantly copied the docs without even remembering that they were supposed to shorten it for making it a cheatsheet xD

repo: biratdatta/Webpage-Maker


text:
fix: prime field default options not showing in ui

The default field options weren't showing as the default values in the UI. An example of this is the Group field which defaults repeated to true, however the switch in the SchemaSettingsComponent shows it as false.
The cause of this seems to be the name change from PrimeField.id to PrimeField.type in the commit refactor: prime-field extraction, which got missed out in a couple of places.
I've renamed PrimeField.options back to PrimeField.defaultOptions, as I think it's less confusing. Let me know if you want it be PrimeField.options though, and I can resubmit without it

Sounds good to me!
Thanks @pippinthegreat

authors: birkir pippinthegreat

repo: birkir/prime


text:
Cordova iOS - Facebook Native App callback return issue?

I have integration/implement Facebook Login in Demo.framework.
Import Demo.framework in my own Cordova Custom Plugin.
Within (FBLoginViewController.m) Custom Plugin call my Demo.framework's function (it's working).
Create Cordova Demo and within demo i have < button /> tag with onClick() method in index.html file and call fbLoginMethod (function) which is define in Custom Plugin's FBLoginViewController.m file.
When FBLoginManage Class open Facebook Native App for Authentication. After Authentication success FBSDK delegate not getting return at index.html.

Note : Without Facebook Native App same Login process scenario is working. (within SFSafariViewController).

Hi @sachinakhaire, did you solved this issue? I'm facing same problem now.

authors: sachinakhaire ulisesvera

repo: bisrael/cordova-plugin-facebook

license: mit


text:
Locking mechanism to prevent asset transfer while on Auction

Auction will finalize anyway but would be less confused if asset should not transferred while on Auction.

As discussed @justinphamnz, i'll be taking a shot at this issue

@justinphamnz PR here: https://github.com/bit-country/Bit-Country-Blockchain/pull/87

authors: justinphamnz mikejamesli

repo: bit-country/Bit-Country-Blockchain


text:
Creates a package for the bench project, moves BlockBench into that p…

…ackage
Now BlockBench won't show up in the root package for our scaladocs

Coverage remained the same at 90.459% when pulling d1dfd478f3fc5730d72b0bb1fe4b17c43608465c on Christewart:2019-05-14-mv-block-bench-to-package into 88122fc30ae040a2a5ac7a85bec92c321448ed74 on bitcoin-s:master.

authors: Christewart coveralls

repo: bitcoin-s/bitcoin-s-core


text:
Newsletters: add 124 (2020-11-18)

Another short one this week.

[ ] Update topic entries @harding
[ ] Update releases/RCs Tuesday @harding
[ ] Clients and services section @bitschmidty
[ ] C-Lightning #4168 @dongcarl

All looks good to me so far. No additional review comments.

ACK. Everything looks good to me. Thanks @harding and other authors!

124 in the books!
Thank you @harding @dongcarl @jnewbery @adamjonas @Xekyo @jonatack !

authors: bitschmidty harding jnewbery


text:
[#42] Support primary keys with other name

fixes #42

Sorry, got sidetracked by other meetings! Looks retroactively good 👍

authors: agatheblues jwharrow


text:
Don't trap exit in Browser.

We either need to handle the {:EXIT, _pid, :chrome_has_crashed}
message or alternatively just not trap the exit, which will make the
Browser process die alongside its linked Connection process.
Addresses #54.
See http://erlang.org/doc/man/erlang.html#process_flag-2

nevermind this...
i'm finally beginning to see


text:
Downgrade from 3 to 2.4 Script Failing: Missing yarn Package

Started with a pre-built CompanionPi image from the downloads page, v3.2. Followed the instructions to clone 2.4 to my Pi.
sudo git clone https://github.com/bitfocus/companion.git -b stable-2.4 /usr/local/src/companion
Ran sudo-companion-update, which gets most of the way there, however fails during package retrieval.
`yarn run v1.22.21
$ ./tools/update.sh
You are not currently on a branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>

Check Node version
Found v14.19.0
Node version is OK
Core
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
error Error: https://registry.yarnpkg.com/secure-json-logic/-/secure-json-logic-0.9.11.tgz: Request failed "404 Not Found"
at ResponseError.ExtendableBuiltin (/opt/fnm/node-versions/v14.19.0/installation/lib/node_modules/yarn/lib/cli.js:696:66)
at new ResponseError (/opt/fnm/node-versions/v14.19.0/installation/lib/node_modules/yarn/lib/cli.js:802:124)
at Request. (/opt/fnm/node-versions/v14.19.0/installation/lib/node_modules/yarn/lib/cli.js:66218:16)
at Request.emit (events.js:400:28)
at Request.module.exports.Request.onRequestResponse (/opt/fnm/node-versions/v14.19.0/installation/lib/node_modules/yarn/lib/cli.js:141751:10)
at ClientRequest.emit (events.js:400:28)
at HTTPParser.parserOnIncomingClient (_http_client.js:647:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
at HTTPParser.execute ()
at TLSSocket.socketOnData (_http_client.js:515:22)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.`
Manually checked, could not find a package on yarn or npm by the name secure-json-logic.

Try again
I've removed the module which wants that dependency, so it should now be able to install everything

No change. Started with a fresh image, fresh git clone and ran updater from scratch, got exactly the same error log.

Oh, I didn't realise that it would force you to update to a specific release version.
I've created a new version v2.4.2b which will hopefully be an option for you to update to.
This should work without needing to reset the image

Still no luck, does not appear in the list. Could I type it in manually into the custom field? It asks: "What git ref?"
Appreciate your help.

v2.4.2b might work as the ref.
Or 53ccee641bcba120aaa6fb85948826e6365b61aa

That was able to push past that missing dependency, however it looks like it fails during the build. Terminal output attached.  Question as well, the whole point of trying to do this build is to run a module that was not updated for V3. Is there just a V2 pre-built image anywhere that exists?
Attempt1 - String.rtf.zip

Was it the raspberrypi-gpio module you are wanting?
It turns out I did start updating that months ago, but never managed to find time to test it. I've pushed the updated code https://github.com/bitfocus/companion-module-raspberry-gpio, if you clone the repository to I think its /opt/module-local-dev on the pi and run yarn inside the clone, it might install itself. I have no idea if it works yet though.
I know it needs some work before it can be included in the official builds, as part of it is picky about where it is compiled

Haha how'd you know!
In all seriousness, yes that is the module. I remember seeing install instructions on where to put things in the issues there, so I'll play around and see what I can find, and I'll see if I can get it installed on 3.2.0. You're awesome, thank you.

Hey it installed and at least works in the web GUI! Had to follow the instructions listed here as a base: https://github.com/bitfocus/companion-module-raspberry-gpio/issues/10
Steps to install:

Start with fresh 3.2.0 CompanionPi image.
cd /opt/companion-module-dev
sudo git clone https://github.com/bitfocus/companion-module-raspberry-gpio.git
cd companion-module-raspberry-gpio
sudo apt install npm
npm install -g yarn
This part is where getting yarn to install got a little weird because of some permissions issues alluded to in that original issue I linked. I just created/gave permissions to any directories it wanted until it was happy using sudo chown -R $USER . Not sure if it matters, but I ensured that I was in the /opt/companion-module-dev/companion-module-raspberry-gpio when I installed yarn.
yarn add onoff
yarn install
sudo reboot

This gets companion to recognize the module. I now have to find a way to make a 3.3V signal to test the GPIO inputs and see if it actually does anything, but this is a big step. Thank again.

repo: bitfocus/companion-pi


text:
Feature: Implement Light mode for the UI

Disclaimer:
Please go through existing feature requests to avoid creating duplicates. If you found a similar issue please post a comment there. If you are uncertain your issue is related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

[x] I have checked for a similar issue and sure it hasn't been reported before.

Description:
Add an option to change the UI to follow Light theme, Dark theme, or the System theme.
User flow & interface:
It can be added as a row of button just like how the "Status Icon Type" is done.

I've implemented Light/Dark theme with a little bit of a redesign. Should be available in app version v1.3.0 and higher if you have OTA Updates enabled.

repo: bitgapp/eqMac


text:
Feature: Implement X so users can do Y (REPLACE THIS)

Disclaimer:
Please go through existing feature requests to avoid creating duplicates. If you found a similar issue please post a comment there. If you are uncertain your issue is related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

[x] I have checked for a similar issue and sure it hasn't been reported before.

Description:
A clear and concise description of what the feature is and should the developer implement it.
User flow & interface:
A clear and concise description of how the user would interact with the proposed change (User interface, guidance and understanding of the feature)

Hi, this looks like an empty template, so I am closing it now, please open a new issue if you have a feature request.


text:
Beta tag.

Look at the tag

Closing this issue as discussed with dev.
Verified this issue on dev app v 2.0.0(353)

repo: bithyve/hexa


text:
CLI specifying elements via -e fails

Specifying elements via the command line parameter -e and -a does not work with multiple elements or attributes.
Documentation says default elements are title,p,h1,h2,h3,h4,h5,h6 but specifying them via -e seems to be like asking to localize no elements, returning strings only for the alt attribute, see output below.
It looks like the problem is with the comma separator, because specifying a single element or attribute works as expected.
$ s18n extract -help

  Usage: s18n-extract [options]

  Options:

    -h, --help                output usage information
    -a, --attributes [attrs]  html attributes to localize [default: "alt,title" | none: "."]
    -d, --directives [dirs]   html attributes to mark elements for localization [default: "localize" | none: "."]
    -e, --elements [elems]    html elements to localize [default: "title,p,h1,h2,h3,h4,h5,h6" | none: "."]
    -p, --paths [paths]       paths or patterns (globby) to find parsable html files [default: "**/*.html"]
    -s, --string        extract from string of parsable html
    --hash <algo>             hashing algorithm to calculate string IDs [default: md5]
    --length <length>         length of string IDs [default: 8]
    --format <type>           format in which to return the locale, "object" or (JSON) "string" [default: "string"]

  Examples:

    $ s18n extract -s "
Hello, World!
"
    $ s18n extract -p "**/*.html, !notranslate/*.html"
    $ s18n extract -a . -e . -d translate=yes
    $ s18n extract > locales/en.json

kai@bluesteel ~/github/web
$ s18n extract -p index.html | head -7
{ '43334488': '
\n
Yowureport - Hackerspaces & Makerspaces
\n
Association announcement in 都會時報 (2014/08/01)
\n
\n\n\n
\n
Supporters of the Taipei Hackerspace
\n
',
  '48292469': '圓環(南京) (to East)',
  '66376152': 'Github Organization / Repository',
  '01af1289': '+886-2-2550-7630',
  c20ad4d7: '12',
  fc916446: '1386nJBU5xV5gdR9pMAea2wRSz6rz4apFu',
  b2eb7349: '306',

kai@bluesteel ~/github/web
$ s18n extract -e title,p,h1,h2,h3,h4,h5,h6 -p index.html
{ '5e717dc2': 'AskMorris',
  '7bc4a85e': 'CTimes',
  '36df9c5f': 'Eiger',
  '22845bef': 'Enspyre',
  '0511c146': 'Gandi',
  '6c8754a5': 'Hackerspace support Bitcoin QR code',
  c31010d1: 'Inhon',
  d2bc36f8: 'MobileGeeks',
  '282c3cc8': 'OSSLab',
  d794d3f7: 'Via' }

kai@bluesteel ~/github/web
$

For reference, HTML file is here: https://github.com/taipeihackerspace/web/blob/master/index.html

I boldly tried to fix the problem, but probably did it wrong: forked, branched, made correction, then was asked to install commitzen in order to be able to commit, ran cz, gave a lot of comment info, ... and then I'm not sure what happened,  had to control-C out of commitzen, not very zen-like experience.
Anyway it was a one-line change in arrayify(), here it is:
lib/extract.js, line 187:
< return [unknown]
> return unknown.split(',');

Hey @kaicarver – thanks for opening the issue. I'd love to accept a pull request if you want to take another swing at it! I'm betting the tests failed when you tried to commit. You can run the gulp task to watch and test as you're building, see: https://github.com/bitjson/s18n#contributing
I'll also try to look into this a little later.

OK maybe I'll try again some time. But honestly I am beginning to wonder if this module, though it looks very nice, is usable for me, because I keep running into very basic stuff that doesn't work at all (I'll post one more issue). Maybe it's just the CLI that doesn't work well and that no one uses, and the library works well?

Hey @kaicarver – this CLI is definitely lacking. By far the most used interface for s18n is gulp-l10n, if you'd prefer something more stable. While s18n's javascript API has 100% test coverage, the CLI is not tested by the build. The gulp plugin, however, has 100% test coverage over the entire interface, so you shouldn't encounter any issues over there.
That being said, I'm planning to take another pass of s18n's CLI in the next few days, so hopefully I can clean it up a bit, maybe even add the CLI to test coverage (#2) so it can't rot so easily.
Thanks for posting the issues you're finding!

thanks for the tip, I will try using s18n via gulp-l10n. My initial goal was to do a super-quick-and-dirty localization, so I'll try to keep doing that, and maybe make some bugfix or feature contributions later.

Hey @kaicarver – is this solved now by #11? Thanks for the PR!

It should be! No time to make an automated test, but it did fix it on my
local version from a few casual tests.
On Apr 21, 2016 23:20, "Jason Dreyzehner" notifications@github.com wrote:

Hey @kaicarver https://github.com/kaicarver – is this solved now by #11
https://github.com/bitjson/s18n/pull/11? Thanks for the PR!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/bitjson/s18n/issues/8#issuecomment-212969293

Great, thanks! I'll close this for now, and I'll try to write some good test cases soon.

authors: bitjson kaicarver


text:
OIDC provider disappeared in v2.2 without any notice.

We upgraded from v2.1 to v2.2 but it seems the oidc provider disappeared.
Eventhough it's documented that it exists:
https://github.com/bitly/oauth2_proxy#openid-connect-provider
$ oauth2_proxy -provider oidc -cookie-secret a -client-id b -client-secret c -email-domain='*' -oidc-issuer-url='https://xxxx

Will complain that -oidc-issuer-url is not a recognised flag, and if we leave it away
it complains:
2018/11/13 22:25:53 main.go:103: Invalid configuration:
  missing setting: upstream

Actually -oidc-issuer-url doesn't show up at all in ouath2_proxy -help
And if we add -upstream=blah
Then the proxy defaults to -provider google:
2018/11/13 22:26:35 oauthproxy.go:157: OAuthProxy configured for Google Client ID: b

This is using the binary provided in the releases tab

Edit: OH apparently we were using master  and not v2.1 so we actually downgraded... oops
Anyhow, it would be nice if we could tag another release. Let me close this issue and open a new one for that


text:
Throwing errors on Ubuntu both nodejs and nodejs-legacy

> bitcore-wallet-service@0.0.3 start /root/src/node_modules/bitcore-wallet-service
> node app.js

Bitcore Wallet Service running on port 3001

events.js:72
        throw er; // Unhandled 'error' event
              ^
OpenError: IO error: ./db/bws.db/LOCK: No such file or directory
    at /root/src/node_modules/bitcore-wallet-service/node_modules/levelup/lib/levelup.js:118:34

npm ERR! bitcore-wallet-service@0.0.3 start: `node app.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the bitcore-wallet-service@0.0.3 start script.
npm ERR! This is most likely a problem with the bitcore-wallet-service package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node app.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls bitcore-wallet-service
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.16.0-23-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! cwd /root/src/node_modules/bitcore-wallet-service
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/src/node_modules/bitcore-wallet-service/npm-debug.log
npm ERR! not ok code 0

I followed instructions on http://stackoverflow.com/questions/21168141/can-not-install-packages-using-node-package-manager-in-ubuntu and installed legacy using sudo apt-get install nodejs-legacy
Still does not fix the problem...
Any tips?

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using npm@1.4.21
3 info using node@v0.10.25
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart bitcore-wallet-service@0.0.3
6 info start bitcore-wallet-service@0.0.3
7 verbose unsafe-perm in lifecycle true
8 info bitcore-wallet-service@0.0.3 Failed to exec start script
9 error bitcore-wallet-service@0.0.3 start: `node app.js`
9 error Exit status 8
10 error Failed at the bitcore-wallet-service@0.0.3 start script.
10 error This is most likely a problem with the bitcore-wallet-service package,
10 error not with npm itself.
10 error Tell the author that this fails on your system:
10 error     node app.js
10 error You can get their info via:
10 error     npm owner ls bitcore-wallet-service
10 error There is likely additional logging output above.
11 error System Linux 3.16.0-23-generic
12 error command "/usr/bin/nodejs" "/usr/bin/npm" "start"
13 error cwd /root/src/node_modules/bitcore-wallet-service
14 error node -v v0.10.25
15 error npm -v 1.4.21
16 error code ELIFECYCLE
17 verbose exit [ 1, true ]

Here's the /bitcore-wallet-service/npm-debug.log

Hello @dabura667 ,
This error is because the folder db/bws.db doesn't exist. We will fix that as soon as possible. Anyway you can manually create it with mkdir -p db/bws.db
Thanks for report!

repo: bitpay/bitcore-wallet-service


text:
Issue starting insight

Hello I have a bitcoin daemon running with this conf
rpcuser=user
rpcpassword=pass
txindex=1
rpcallowip=127.0.0.1
and I'm following this guide: https://github.com/bitpay/insight-api to install the insight-api.
When I run node insight.js I get this error message and I do not understand how to fix it:
info: insight server listening on port 3001 in development mode
{ '0': [Error: Could not connect to bitcoin via RPC: connect ECONNREFUSED] }
error: ERROR  Error: Could not connect to bitcoin via RPC: connect ECONNREFUSED
at ClientRequest. (/home/bitcoin/Desktop/insight-api/node_modules/bitcore/lib/RpcClient.js:207:15)
at ClientRequest.EventEmitter.emit (events.js:95:17)
at Socket.socketErrorListener (http.js:1547:9)
at Socket.EventEmitter.emit (events.js:95:17)
at net.js:441:14
at process._tickCallback (node.js:415:13)
could anybody help? Thanks!

You'll need server=1 and listen=1 in that conf, as well.
I'd also start it with livenet enabled, that way you're pointing towards the proper ports. Do that with:
INSIGHT_NETWORK=livenet npm start
Is this for bitcoin or an altcoin?

Outdated as bitcoind now runs in the same process.

authors: GreydonIselmoe braydonf vdidonato

repo: bitpay/insight


text:
On PR Builds, Would Like GIT_CLONE_TRIGGERED_COMMIT_HASH

For our dev builds, we are trying to expose the exact commit that triggered the build within the app so that they can reference it quickly or have it available. Unfortunately, on PRs the GIT_CLONE_COMMIT_HASH is the outcome of the merge from staging versus the commit as cloned.
Example Values:
=> GIT_CLONE_COMMIT_HASH
   value: ee8ca46253400cfdc3c63c6facd2dfbf47863a28
=> GIT_CLONE_COMMIT_MESSAGE_SUBJECT
   value: Merge commit '6a066ad5f4bb236dce7f677373951430bd9807b5' into staging

On PR Builds, would Like GIT_CLONE_TRIGGERED_COMMIT_HASH to be the value embedded within the GIT_CLONE_COMMIT_MESSAGE_SUBJECT. As of now, I'm going to write a REGEX to pull that information out so that I can set as an environment variable for my app to read and report. Yes, I know that technically the compiled/merged version is what is ultimately used to produce the app, but since that commit never makes it back to my GitHub repo, it's not helpful from a search/audit trail perspecxtive.

Once again I managed to post in the wrong location. Closing and posting to the correct channel https://github.com/bitrise-steplib/steps-git-clone/issues/102

repo: bitrise-io/bitrise-steplib


text:
sonarqube-scanner 3.0.1.733.0

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

@godrei & @trapacska please review!

Hi @koral-- ,
please use semantic versioning (MAJOR.MINOR.PATCH) for your step.
To apply your fixed version please re-share your step by:

close this PR
delete yoursonarqube-scanner-3.0.1.733.0 branch in your steplib fork
share the step again

@godrei I can change it to 1.0.0 but that version scheme is intentional.
3.0.1.733 is a version of Sonar Scanner CLI embedded in the step, it matches upstream version number: https://github.com/SonarSource/sonar-scanner-cli/releases/tag/3.0.1.733
Trailing 0 is a patch number of a step itself.
With this scheme, users know in advance which scanner CLI version is used. There is no need to browse changelogs. E.g. RxJavaProGuardRules uses the same scheme.
What do you think now?
If it is strictly required to use semantic versioning, shouldn't it be mentioned in the documentation?
I could not find such requirement in http://devcenter.bitrise.io/bitrise-cli/create-your-own-step/ and pages which can be reached from there like Step Development Guideline.

@koral-- thanks for the clarification!
When one of our steps is a wrapper around a tool, we provide an option to specify the tool's version and the step manages to download the desired version (maybe it is not an option in your case...).
Maybe you could mention the embedded Sonar Scanner CLI's version in the step title as an alternative solution.
If you want to use this version, we will need some more time, to validate if this kind of version is working well with our system, since this step would be the first one, which does not use 3 component semantic versioning.

I've planned to add an input with scanner version name before I read the guideline.
There is a rule: Do not use submodules, or require any other resource downloaded on-demand.
Scanner is not available in official apt-get repositories.
But if you suggest that this rule can be violated I will add input for version name. Scanner CLI ZIP has about 0.5 MB and is officially hosted on bintray so download issues should occur very rarely.
I'll add input for version and send new PR.
Thanks.

That sounds wonderful, thank you @koral-- ! :)

authors: godrei koral-- viktorbenei


text:
🛑 Luogu is down

In 7dc8041, Luogu (https://www.luogu.com.cn) was down:

HTTP code: 523
Response time: 1300 ms

Resolved: Luogu is back up in 0214d44 after 12 minutes.

repo: bitsstdcheee/luogu-status


text:
Fix #358: Do not try to convert Time to a NaiveDateTime before formatting

41b46b81/#336 adds a whitelist of native date types, and converts everything else to a NaiveDateTime before formatting. The Time type/struct was omitted from the list.
I assume the intention was to whitelist Time as well, as it is also a native "date" type. It also cannot be converted to a NaiveDateTime, as it represents only a time of day.
I've also added a test in the style of other issue fixes I've seen.
I'm new to both Elixir and Timex, so please let me know if I'm missing anything, and don't hesitate to request any changes! Thanks!

Coverage increased (+0.07%) to 68.013% when pulling 51a3e6fd25e86cfa5158f01ba8b52ed5956b4c56 on mlovic:master into 3852b8eb407a6c5cc7df8709511969330c8e2e8b on bitwalker:master.

Right now there isn't great support in Timex for using Time everywhere, since most everything assumes both a date and a time, but I'm ok with letting this in, since it appears to work when formatting. Thanks for the PR!

It appears that this fix hasn't made it into a release yet. Would you mind making a release (maybe 3.1.25?) with this included?

authors: bitwalker bklang coveralls mlovic

repo: bitwalker/timex


text:
Restore missing chief records

What this PR does:
This PR fixes the issue of the missing CHIEF files in the hmrc servers, so we have created 5 csv files with the missing records.
There are 2 new rake tasks... to insert and process the missing data.

 Create a script from production mysql dump, that reads the data for the missing files, so we can then restore it into the postgresql database

repo: bitzesty/trade-tariff-backend


text:
The download links on website are 404

On homepage:
Download
biwascheme-0.6.4.js
biwascheme-0.6.4-min.js
Both links are 404 Not Found

Oops, I've fixed it. Thank you for reporting.

authors: CodinCat yhara

repo: biwascheme/biwascheme


text:
Add a DebugStructGenerator

Replacing the StructGenerator with the DebugStructGenerator prints all OpenGL function invokations to stdout.
There are a lot of redundancies between generators. I think I'll open an issue to propose an API for gl_generator 1.0 and make everything cleaner.

Is someone opposed to this? Can I merge it?

Great stuff. I definitely think we should try to reduce the redundancies between generators.

authors: bjz tomaka

repo: bjz/gl-rs


text:
Is there a way to know that my laptop is turned off?

I have lnxlink on my dev laptop. When I shut the laptop down, HA remembers the previous state that lnxlink reported for all of my entities, and they don't go unavailable even after several days. For example, the idle time on my laptop has been "3" ever since I shut it down.
I'm trying to create a template sensor for whether or not I'm currently using my laptop, but so far I can't figure out how to make it accurate.
So far, I've come up with:
{{ (has_value('sensor.dev_laptop_idle') and
      (now() | as_local | as_timestamp - states.sensor.dev_laptop_idle.last_changed | as_local | as_timestamp < 120) and
      (is_state('sensor.dev_laptop_idle', 'OFF') or (states('sensor.dev_laptop_idle') | int) <= 600)) }}

However even that causes issues, because after restarting HA, the last_changed timestamp updates to the current time, and it then says I'm using my laptop for at least the next 120 seconds.
Is there any way to have an MQTT entity from lnxlink that goes unavailable when it stops receiving updates so that I can detect when it's no longer receiving data from lnxlink more accurately?
Side note: Is it a bug that when idle time is 0, Home Assistant reports the state as OFF?

For me when I turn off or restart my PC it automatically becomes unavailable. Could you send me some more info about your system?
Distribution, version, etc...
Unfortunately home assistant doesn't support on MQTT to check if it doesn't get any events for x time, to set unavailable the entity, but you could create an automation similar to the one you created:
alias: lnxlink powered down
description: ""
mode: single
trigger:
  - platform: template
    value_template: >-
      {{ (now() | as_local | as_timestamp -
      states.sensor.desktop_linux_idle.last_changed | as_local | as_timestamp) >
      10 }}
condition: []
action:
  - service: mqtt.publish
    data:
      qos: 0
      retain: true
      topic: lnxlink/desktop-linux/lwt
      payload: "OFF"

As for the idle time, I haven't noticed any report for state OFF, but I will keep it in mind.

My laptop is running Pop_OS! (based on Ubuntu) 22.04, however I'm a bit unclear on how that could affect whether or not the Home Assistant entities go unavailable when it's shut off.
Which entities go unavailable when you turn off your PC, all of them? And what makes them go unavailable since as you mentioned the lack of an MQTT post isn't sufficient?
Regarding a value of 0 being considered 'OFF' for idle time, whenever I'm currently using my laptop so that the idle time would be 0, I see the following log messages:
2023-04-25 16:08:34.627 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.dev_laptop_idle has device class duration, state class total_increasing and unit s thus indicating it has a numeric value; however, it has the non-numeric value: OFF (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
And my template sensor has to account for the state being 'OFF' as otherwise it doesn't match if I just treat it as numeric.

To control when the entities are unavailable, the MQTT topic lwt should be on state OFF. This is controlled by lnxlink which sends this just before the computer shuts down or lnxlink service is stopped.
The errors you get remind me of older versions of lnxlink. You can check which version you have installed from logs or using pip freeze. Make sure you have installed the latest version which at this time is 2023.4.1.
Unfortunately I am not using Pop_OS to test but it should work the same way as Ubuntu that I am using. I've tried to make the project work on any distribution, but if the entities don't go to unavailable, then you can use the automation I mentioned on my previous comment.

I'm on version 2023.4.0, I forgot to update to 2023.4.1. I'll give that a shot and see if it helps. Thank you!

Version 2023.5.0 has many issues fixed, if you still have issues, let me know.

With the new version 2023.6.0 sensors and binary_sensors automatically become unavailable.

authors: bkbilly bmcclure

repo: bkbilly/lnxlink


text:
Scalable types

Description
Covert back to the original method of typing to allow future scaling.
Type of Change

[x] Breaking change (would cause existing functionality to not work as expected)
[x] Documentation content changes
[x] Code style update (formatting, renaming)

Current Behavior
Most types are created using NotionObject.
Motivation and Context (move this to below "New Behavior"!)
The method of typing in v0.3.0 prevents mistakes and uses clean and simple syntax. Unfortunately, it's hard to understand and doesn't allow for scaling.
New Behavior
Types are created using a method of typing similar to that used in v0.2.0. (example)
Instead of using an Any type, all types will be exported. In index.ts of that directory, all types will be exported as the plural of the type name and then included in a union type with the singular type name.
For example:
// users.ts
interface UserBase { ... }

export interface Person extends UserBase {
    type: 'person'
    person: { ... }
}

export interface Bot extends UserBase {
    type: 'person'
    person: { ... }
}

// index.ts
import * as Users from 'users.ts'
export { Users }

export type User = Users.Person | Users.Bot

Checklist

[ ] My commits are clear and use gitmoji.
[ ] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

The method of typing has now changed twice now, only to switch back. Every time this happens, the package is bumped up a (pre-release) major version.
0.2.0 -> 0.3.0
0.3.0 -> 0.4.0 (this PR)
This PR will not be merged until the rest of the module is built out (response types and endpoints).


text:
Not all entries downloaded

The Excel was missing several items of my collection.
(I might debug this myself one day.)

Could you provide the discogs release id s for the missing ones

My collection is small (https://www.discogs.com/user/bomben/collection) this still might be the reason. If I sort for newest, which also was the way the Excel was sorted originally, it seems that it downloaded 125 old entries and then skipped all the others, which where newer ones. .
Not included in the download are those and more:

https://www.discogs.com/Me-Avalon-EP/release/10517165
https://www.discogs.com/Ansome-Penny-Pound-EP-/release/6021043
https://www.discogs.com/Avion-9-Leytonstone-Stefan-Rein-schelf-Untitled/release/7960905
https://www.discogs.com/Emmanuel-Installations/release/7868278

Sorry for the late reply. I was able to reproduce the error, i think the problem is somewhere in the processing of the data. The API requests are working. Maybe there is a problem with the regex. I'll look into it, but i don't have much time right now.

Funny, I also checked it yesterday evening. I get 179 items from the API, but some of them are empty (row is empty), which results in lesser items that are written to the file.

This will be solved by https://github.com/blackbunt/dump-discogs-collection-2-csv/pull/3#issue-1007047838.

authors: blackbunt viertelb


text:
[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 1.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: blackflux/kasa-smart-hub


text:
[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 1.10.169 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: blackflux/lambda-example


text:
The data link is broken

Or is it just me?
http://media.blacklotusproject.com/data/blacklotusproject-data-2013-10-22.tgz

blacklotusproject.com is toast. I need to put the file elsewhere for hosting.

I figured that was the case. Github has a 1GB limit so that could work ... or maybe SourceForge or BinTray.

SourceForge hosts things that aren't malware? :trollface:

Hahaha, only if you upload this, it could be the start of something beautiful. :neckbeard:

Wayback machine has it - http://web.archive.org/web/20150211234926/http://media.blacklotusproject.com/data/blacklotusproject-data-2013-10-22.tgz

The original .tgz file is now stored in this GitHub repo as a LFS object. GitHub allows 1GB of free LFS storage for free, and the .tgz file is about 318MB. This repo is good to go for forever.

authors: ryanpcmcquen ssorallen xxx

repo: blacklotusproject/data


text:
🛑 BlackPirateX main website is down

In ff02938, BlackPirateX main website (https://blackpiratex.com) was down:

HTTP code: 500
Response time: 3036 ms

Resolved: BlackPirateX main website is back up in 3a88e29.

repo: blackpirateapps/uptime


text:
Bug report — Sorting dates by descending shows null values first (0.5.2 beta)

What happened?
Dataview 0.5.2 seems to have introduced an issue when sorting dates in descending order, e.g. sort date desc when the query contains null values.
Previously (0.4.2+) when sorting by descending date, the most recent dates would appear at the top of the list. Null values would appear at the bottom.
In 0.5.2 null values appear at the top, then followed by the most recent to oldest.
DQL
No response
JS
No response
Dataview Version
0.5.2
Obsidian Version
0.14.14
OS
MacOS

Yes, I confirm this change.
Meanwhile, you can use this:
SORT default(date, date("1900-01-01")) desc

I swapped the order that null appears in sorts (from nulls FIRST to nulls LAST by default); I'm not sure why I did that. Let me check the git history.

To be honest, still not sure why I did it; going to just revert to the original behavior. Nulls have been pretty annoying in comparisons since it's not well defined what should happen when you compare null to something else (should the comparison also return null instead of true/false? should it error?)

I am noticing that the same is true for numbers, null is listed first. IMO null should always be last in sorting because it implies no data is present. It is ambiguous in meaning so it should be sorted at the end, whereas if a number is present it should be prioritized.
Currently sorting by ascending numbers gives you:

null
0
1
2
3

I think it should be

0
1
2
3
null

TBH every person wants their own version of null sorting. IMO, use default() to assign a default val for nums so that your sorting order behaves accordingly. The other option would be to write your own sort using a combination of map() and other functionality.

@AB1908 I will look into that for my personal use. That said, I am not sure I understand the case for defaulting null values to the top of a sort.

It was mostly the default behavior and changing it seemed to have annoyed a number of users. I'd honestly ask everyone to use some custom sort logic if that kinda stuff is so important.

There is no sane default for handling nulls, since it will look wierd for one choice or the other regardless. The best I can do is probably add a NULLS FIRST/LAST clause to sort queries; this will still not work for direct comparisons (like value >= other-value where one of them is null).

There is no sane default for handling nulls, since it will look wierd for one choice or the other regardless. The best I can do is probably add a NULLS FIRST/LAST clause to sort queries; this will still not work for direct comparisons (like value >= other-value where one of them is null).

Was this added?

No. Can still get around it by using default() and/or some custom function for sorting.

repo: blacksmithgu/obsidian-dataview


text:
Support for dmgs extracted from IMG4

> tar -xf iPhone14,5_15.4.1_19E258_Restore.ipsw 078-29017-016.dmg

> file 078-29017-016.dmg
078-29017-016.dmg: IM4P, ramdisk

> ipsw img4 extract 078-29017-016.dmg
   • Parsing Im4p
      • Exracting payload to file 078-29017-016.dmg.payload

> apfs ls 078-29017-016.dmg.payload
Error: found unexpected UDIFResourceFile signure: , expected: koly

As you can see from that, the dmgs extracted from an IM4P can be mounted by hdiutil but not parsed by go-apfs.

I didn't know tar could unzip zip?!

I didn't know tar could unzip zip?!

bsdtar from libarchive can, which macOS and *BSD use as their /usr/bin/tar

❯ hdiutil imageinfo 078-26254-029.dmg.payload.dmg
Class Name: CRawDiskImage
Size Information:
        Total Bytes: 124961792
        Compressed Ratio: 1
        Sector Count: 244066
        Total Non-Empty Bytes: 124961792
        Compressed Bytes: 124961792
        Total Empty Bytes: 0
Checksum Type: none
Format: UDRW
partitions:
        partition-scheme: none
        block-size: 512
        appendable: true
        partitions:
                0:
                        partition-name: whole disk
                        partition-start: 0
                        partition-synthesized: true
                        partition-length: 244066
                        partition-hint: Apple_HFSX
                        partition-filesystems:
                                "HFSX":  <======= 👀
        burnable: true
Format Description: raw read/write
Checksum Value:
Properties:
        Encrypted: false
        Kernel Compatible: true
        Checksummed: false
        Software License Agreement: false
        Partitioned: false
        Compressed: no
Segments:
        0: 078-26254-029.dmg.payload.dmg
Backing Store Information:
        URL: file://078-26254-029.dmg.payload.dmg
        Name: 078-26254-029.dmg.payload.dmg
        Class Name: CBSDBackingStore
Resize limits (per hdiutil resize -limits):
 min     cur     max
244066  244066  2486271306

wanna help build a HFS+ parser 😁

Oh. I had just assumed that it was APFS, didn't realize HFS+ was still used.
I'll close this since it's out of scope of this project.

I still think it's cool, I didn't know that either.  I think that go-apfs should at least be able to recognize HFS and print out a helpful error message?

Yeah, an error message would be good. file doesn't recognize it so getting any information from it without hdiutil would be good 😃

authors: CRKatri blacktop

repo: blacktop/go-apfs


text:
Update Character “hadriana”

Automatically generated by Netlify CMS

👷 Deploy Preview for dynamic-cheesecake-5fbd8b processing.

Name
Link

🔨 Latest commit
2e89d931818f95cc86e98b3135a3a3844bd5ed9f

🔍 Latest deploy log
https://app.netlify.com/sites/dynamic-cheesecake-5fbd8b/deploys/62d88da043c74100083bf560

repo: blargoflatsome/fourshame


text:
Swagger Error

why swagger send me this error and my model have no field with name Id ?
{
"Data": null,
"Messages": [
"Invalid column name 'Id'."
],
"Succeeded": false
}

Which endpoint is this?

its new endpoint
`namespace AVATOR.Client.Infrastructure.Routes
{
public static class CraftsEndpoints
{
public static string ExportFiltered(string searchString)
{
return $"{Export}?searchString={searchString}";
}
    public static string Export = "api/v1/crafts/export";

    public static string GetAll = "api/v1/crafts";
    public static string Delete = "api/v1/crafts";
    public static string Save = "api/v1/crafts";
    public static string GetCount = "api/v1/crafts/count";
}

}`

Probably you have not updated your database. It should be easy to debug and figure out the exception?

thanks for your replay
Actually i did , but i see any new entity most have Id Field !
thanks in advance
regards

authors: arkannet iammukeshm

repo: blazorhero/CleanArchitecture


text:
deploy to apt repo from Travis CI

Need to add the GPG bits.

Dev packages are shipped to the edge component. Modeled after Docker's apt repo.
Deploy will happen on merge to master.

repo: blbradley/zcash-swing-wallet-ui


text:
Make getting a PCE App easy

Context
Currently, when you want to build your privacy portal using blindnet devkit, you are supposed to make a webpage, include the PRCI web component and give to it a URL of the PCE. See example here:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <title>Privacy Components for the Web - Minimal Static Demo</title>

Privacy Components for the Web - Minimal Static Demo

Assert Your Privacy Rights

    <bldn-priv-request computation-base-url="http://localhost:9000/v0"></bldn-priv-request>

Intended outcome
I want to make the integration, for clients using our PCE instance, as quick as possible. So I want them to get (from us, or maybe later through an interface) a URL* to provide in the computation-base-url argument, so that they can really have an easy quick-start.
It should also be possible (independently of this web page and the example code given above) to provide configuration meta-data/settings to configure the PCE App.
*several clients get to use the same URL, but must specify particular app id and other ifnromation used to identify them.

If no url is provided, staging one is used.

It should also be possible (independently of this web page and the example code given above) to provide configuration meta-data/settings to configure the PCE App.

PCE configuration settings shouldn't be set here since it's a data subject facing component. Do you have some particular setting in mind?

*several clients get to use the same URL, but must specify particular app id and other ifnromation used to identify them.

App information is extracted from the token, so no need to specify it in this component.

I am fine with all you wrote. My issue description is slightly outdated.

repo: blindnet-io/privacy-computation-engine


text:
fixes #36

This is the other way to fix the issue proposed in issue comments.
Adding length zero did not fix it, this fixes the issue by ensuring the indices exist.

forgot to close this at the time but this was superseded by #40

authors: blingenf chaseleif

repo: blingenf/copydetect


text:
[fix] keystone accounts disordered

Description
This PR fix the bug that Keystone wallet's accounts disordered in some cases.
Checklist

[x] The version field in package.json is incremented following semantic versioning
[ ] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[ ] This PR passes the Circle CI checks

Merged in #674

authors: soralit taylorjdawson

repo: blocknative/onboard


text:
Add layers panel

Problem
The JSX element hierarchy is (1) difficult to understand at a glance and (2) cumbersome to navigate. The current UI only allows users to navigate to the parent or children of the selected element:

Solution
This pull request implements a layers panel similar to other design tools like Figma and Sketch:
👉 Preview

Here's how I implemented the layers panel:

I wrote a getElementTree Babel plugin that returns a tree of JSX elements from given code. Here's an example of how getElementTree can be used:

import * as queries from './queries'
const elementTree = queries.getElementTree(code)
/*
{
  id: 'root',
  name: 'root',
  children: [
    {
      id: '4c30a053-04c3-4539-a407-837753aee8d4',
      name: 'HeaderBasic',
      children: [...]
    }
  ]
}
*/

I removed the old TreeView from the top of the "Editor" panel because it just displayed a subset of the information that is in the layers panel:

I created a Tree component to render the data returned by getElementTree. Tree is rendered in a new left side panel:

Questions

Are there better names for getElementTree and Tree?

Next steps
This is an MVP layers panel. There are several features I'd love to see added in the future, like:

Hover on an element in the layers panel to highlight the element in the canvas (and vice versa)
Drag and drop to reorder elements in layers panel
Expand/collapse elements in layers panel
Improve the mobile experience

Closes #146

This is amazing @colebemis! 💟💟💟
Thank you for implementing this, and for taking the time to write up such a thorough description! 🙏

authors: colebemis johno

repo: blocks/blocks


text:
🛑 Maxthon API is down

In f819fff, Maxthon API (https://api.maxthon.com) was down:

HTTP code: 500
Response time: 309 ms

Resolved: Maxthon API is back up in c60334f after 50 minutes.

repo: bloodchen/upptime


text:
🛑 Maxthon API is down

In 1215e07, Maxthon API (https://api.maxthon.com) was down:

HTTP code: 500
Response time: 349 ms

Resolved: Maxthon API is back up in 38b2a3c after 10 minutes.


text:
🛑 Maxthon API is down

In 1b389d3, Maxthon API (https://api.maxthon.com) was down:

HTTP code: 500
Response time: 214 ms

Resolved: Maxthon API is back up in d48c37c after 1 hour, 49 minutes.


text:
Changing scale type on existing figure

I'm building a multipurpose dashboard that should be able to graph a wide variety of data with different settings. One of the requirements is being able to graph against milliseconds while another is to graph against datetimes. I currently have code similar to the following:
x_sc = DateScale()
y_sc = LinearScale()

ax_x = Axis(label='time', scale=x_sc, grid_lines='solid', tick_format='%m/%d/%y', tick_rotate=90)
ax_y = Axis(label='y_val', scale=y_sc, orientation='vertical', tick_format='0.2f')
pz = PanZoom(scales={'x': [x_sc], 'y': [y_sc]})
data = Lines(x=x_data, y=y_data, scales={'x': x_sc, 'y': y_sc})

zoom_interacts = widgets.ToggleButtons(options=OrderedDict([
                                        (' ', None),
                                        ('xy ', pz)]),
                                        icons = ["stop", "arrows"]
                                        )

fig = Figure(axes=[ax_x, ax_y], marks=[data])
link((zoom_interacts, 'value'), (fig, 'interaction'))
widgets.HBox([fig, zoom_interacts])

swap = widgets.Select(
    options=['dates', 'ms'],
    description='Swap',
    disabled=False
)
def swapAxes(b):
    global x_data
    global ax_x
    global data
    global fig
    if(b == 'dates'):
        ax_x.scale = DateScale()
        x_data = date_data
    else:
        ax_x.scale = LinearScale()
        x_data = ms_data

interactive(swapAxes, b=swap)

where y_data, date_data, and ms_data are all numpy arrays. When the figure first renders it works as long as I'm using ms_data with a linear scale or date_data with a date scale. But when I try to change the scale using the select the values on the x_axis simply disappear. Is there a way to change this scale back and forth between a date scale and a linear scale?

You have to change the scale on your mark too.
Something like this should work.
def swapAxes(b, arrayData):
    global date_data
    global ms_data
    if(b == 'dates'):
        ax_x.scale = DateScale()
        data.x = date_data
    else:
        ax_x.scale = LinearScale()
        data.x = ms_data
    data.scales['x'] =  ax_x.scale

interactive(swapAxes, b=swap)

Though probably best not to use global variables.

Thanks for the reply. I couldn't agree more on the global variables, this is just some code I've been playing around with to familiarize myself more with bqplot and experiment with it. This change doesn't seem to have an effect though. The scale just disappears from the figure as soon as I use the swap select and doesn't return.

Can you post a full workable example?
At this stage, I would guess it is either:

Min and max on the scale needs resetting
The marks have been assigned the wrong scales
The axes have been removed from the figure somehow.
something else

It took me a while.  2 things:

date_format  in the DateScale
Redefine the scales from scratch. So line.scales = {'x': ax_x.scale, 'y': ax_y.scale},  not line.scales['x'] =  ax_x.scale .  Not sure why.

import numpy as np
import pandas as pd
from bqplot import *
from ipywidgets import *
from collections import OrderedDict

y_data = np.random.randint(-100, 100, size=48)
base = np.datetime64('2000-01-01', 'us')
date_data = np.array([base + np.timedelta64(i, 'h') for i in range(48)])
ms_data = np.arange(48)
x_data = date_data

x_sc = DateScale(date_format = "%m-%d-%y")
x_scLin = LinearScale()
y_sc = LinearScale()

ax_x = Axis(label='RTC (ms)', scale=x_sc, grid_lines='solid', tick_rotate=45)
ax_y = Axis(label='Reading (mVs)', scale=y_sc, orientation='vertical')
pz = PanZoom(scales={'x': [x_sc], 'y': [y_sc]})
line = Lines(x=x_data, y=y_data, scales={'x': x_sc, 'y': y_sc})

zoom_interacts = widgets.ToggleButtons(options=OrderedDict([
                                        (' ', None),
                                        ('xy ', pz)]),
                                        icons = ["stop", "arrows"]
                                        )

swap = widgets.Select(
    options=['dates', 'ms'],
    description='Swap',
    disabled=False
)
fig = Figure(axes=[ax_x, ax_y], marks=[line])
link((zoom_interacts, 'value'), (fig, 'interaction'))
hbox  = widgets.VBox([fig, zoom_interacts])

def swapAxes(b):
    if b == 'dates':
        line.x = date_data
        ax_x.scale = x_sc
        ax_x.tick_rotate=45

    else:
        line.x = ms_data
        ax_x.scale=x_scLin
        ax_x.tick_rotate=0
    line.scales = {'x': ax_x.scale, 'y': ax_y.scale}
hbox

interactive(swapAxes, b=swap)

That worked great! Thank you so much for the help!

authors: DougRzz shorstman

repo: bloomberg/bqplot


text:
Disable yarn's nodemanager virtual memory check

This PR disables Yarn NodeManager virtual memory check.

What is the purpose of doing this?

This prevents YARN containers from being killed when they request more that twice the physical memory requested.

authors: amithkanand cbaenziger ekund

repo: bloomberg/chef-bach


text:
testbed/arcyd/docker-test.sh: redo as testshell

Replace 'sleep 5' in docker-test with an invocation of bash, so that
users can easily play with a running instance.
Rename to 'docker-testshell'.
Provide documentation for some common things to try out in the
test shell.
Test Plan:
$ ./precommit.sh
$ ./testbed/arcyd/docker-testshell.sh
    .. try seeing the logs ..
    .. try seeing the info log ..
    .. try standing up a new instance ..
    $ exit

Thanks!

repo: bloomberg/phabricator-tools


text:
Check compatibility with Cardano Node 8.0.0

Known issues:

Protocol param local state query fails with following error

WARN  [2023-05-11 13:43:44,212] io.netty.channel.DefaultChannelPipeline: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
! java.lang.NullPointerException: Cannot invoke "java.math.BigInteger.intValue()" because the return value of "com.bloxbean.cardano.yaci.core.util.CborSerializationUtil.toBigInteger(co.nstant.in.cbor.model.DataItem)" is null
! at com.bloxbean.cardano.yaci.core.util.CborSerializationUtil.toInt(CborSerializationUtil.java:55)
! at com.bloxbean.cardano.yaci.core.protocol.localstate.queries.CurrentProtocolParamsQuery.deserializeResult(CurrentProtocolParamsQuery.java:103)

Era query like UtxoByAddress doesn't work

With 8.0, GenesisBlockFinder doesn't return the correct start point, so sync fails.

repo: bloxbean/yaci


text:
[BUG] Private chats having hex codes and fonts inside the text

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
Whenever someone private chats, it displays this weird <fontcolor=#HEXCODE> [username]  thing, ever since I got the new bloxstrap.

Bloxstrap Log
N/A

Upload your configuration please: https://github.com/pizzaboxer/bloxstrap/wiki/Uploading-your-Bloxstrap-configuration

This seems more like the game's problem. Are you sure this doesn't happen with the regular Roblox bootstrapper?

happens in every single game ive tested.

This seems more like the game's problem. Are you sure this doesn't happen with the regular Roblox bootstrapper?

happens in every single game ive tested.

Send your fast flags here

This seems more like the game's problem. Are you sure this doesn't happen with the regular Roblox bootstrapper?
happens in every single game ive tested.
Send your fast flags here
no fast flags except the presets

no fast flags except the presets

Are you sure this does not happen with the regular Roblox bootstrapper?

no fast flags except the presets

Are you sure this does not happen with the regular Roblox bootstrapper?

yeah, my friends seem to have no issue

huh, it seems to have fixed after i restarted my pc

apparently not, ill send the configs here:
ClientAppSettings.json
Settings.json
State.json

i think this is an issue on roblox's part, i have uninstalled bloxstrap and it still persists.

authors: LVIENG bluepilledgreat pizzaboxer

repo: bloxstraplabs/bloxstrap


text:
Conman template: wrong execpath

Value:
SERVER execpath="/usr/share/conman/exec"
Is not adapted to new path of conman.

Solved by @bouriquet

PR #115

authors: actatux oxedions

repo: bluebanquise/bluebanquise


text:
fix branch validation for converged and dedicated stacks

fixes branch validation by properly detecting dedicated/converged stacks
tests API functionality
repaired network connectivity and inter-connectivity testing
breaks functionality into paramaterized includes where possible
most importantly, i think it works

Old PR: https://github.com/blueboxgroup/ursula/pull/1789

Closing in favor of #1885

repo: blueboxgroup/ursula


text:
[iOS] [Real Device] Error occurs when sound is played continuously.

Full Description
At first the sound sounds fine, but after a few taps the sound stops. At that time an error occurs.
No errors occur in the simulator. However, errors do occur on the real device.
Is there any way to solve this problem?
Code to Reproduce
  GestureDetector(
    child: Text('Press'),
    onTap: () async {
      for (var i = 0; i < 100; i++) {
        print(i);
        final player = AudioPlayer();
        await player.play(AssetSource('audio/handclap1.mp3'));
        await Future<void>.delayed(const Duration(milliseconds: 100));
      }
    },
  ),

Log Errors
flutter: 0
"method: setSourceUrl"
"playerId: f0ffb3ca-4f07-4971-86b4-602d08c33c7b"
""
"method: resume"

...

flutter: 52
"method: setSourceUrl"
"playerId: dfa54159-ec71-446b-a42b-17b003d09506"
""
[VERBOSE-2:ui_dart_state.cc(198)] Unhandled Exception: AVPlayerItem.Status.failed
#0      MethodChannelAudioplayersPlatform._doHandlePlatformCall (package:audioplayers_platform_interface/method_channel_audioplayers_platform.dart:173:9)
#1      MethodChannelAudioplayersPlatform.platformCallHandler (package:audioplayers_platform_interface/method_channel_audioplayers_platform.dart:147:7)
#2      MethodChannel._handleAsMethodCall (package:flutter/src/services/platform_channel.dart:404:55)
#3      MethodChannel.setMethodCallHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:397:34)
#4      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:380:35)
#5      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:377:46)
#6      _invoke2.<anonymous closure> (dart:ui/hooks.dart:190:15)
#7      _rootRun (dart:async/zone.dart:1426:13)
#8      _CustomZone.run (dart:async/zone.dart:1328:19)
#9      _CustomZone.runGuarded (dart:async/zone.dart:1236:7)
#10     _invoke2 (dart:ui/hooks.dart:189:10)
#11     _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5)
#12     _Channel.push (dart:ui/channel_buffers.dart:132:31)
#13     ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17)
#14     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:589:22)
#15     _dispatchPlatformMessage (dart:ui/hooks.dart:89:31)

Files/URLs/Sources
local mp3 file.
Screenshots
No
Platforms

OS: ios
OS version: 15.5
Device: iPhone SE3. Real Device.
audioplayers version: 1.0.1

Same exception here!
My files are wav or mp3, temporary created File objects.

Use soundpool instead of this plugin. This plugin worked fine.
https://pub.dev/packages/soundpool

repo: bluefireteam/audioplayers


text:
目录/文件的修改时间显示不正常

目录/文件的修改时间全部显示为“今天”
是否应该按照文档中修改：
https://github.com/Studio-42/elFinder/wiki/Client-Server-API-2.1#information-about-filedirectory
"ts"     : 1334163643,           // (Number) file modification time in unix timestamp. Required.

you are right
thanks


text:
more logging of executor-module failures

For example, UpdateStatefulSetReplicas doesn't log anything in the error case. There are other similar cases.

Actually I think we're good here. In cases where the error is not being logged at point of generation, it's being returned to a caller that will log it.


text:
Added the inverse style modification method

I wasn't able to find the inverse style modification mentioned in the README.md after further investigations I found that the inverse style modification is not implemented so I implemented it myself.
I did not use the CSI 7 m as it is not widely supported, I implemented my own system which converts the foreground to background and the background to the foreground

Did you look into how it is done in the upstream implementation of chalk? My goal was to solve #17 exactly the way chalk does it so that the two implementations stay the same.

uhh sorry I don't understand what you are talking about can you elaborate more?
also sorry for my bad english

I'm new to this contribution thing of open-source can you explain what you mean by upstream implementation? I cannot find any branch with a related name

Sorry for being a bit cryptic :wink:
This project here is basically a port of the "original" chalk in JavaScript: https://github.com/chalk/chalk
When I was migrating the project I was trying to stay relatively close to the original so that I can easily backport and adapt changes made there. Admittedly I haven't looked into the original implementation for a while, which is also why I may have missed the inverted feature. My goal regarding the feature would be to implement it similarly to avoid diverging too much.
I'm currently running low on time, which is why it may take a bit until I can analyze the original implementation.


text:
Display of Chinese characters in link card

Describe the bug
In the link card, Chinese characters turn into random symbols
To Reproduce
https://bsky.app/profile/yilinwriter.bsky.social/post/3k4kioo3z2j2q
Expected behavior
Readable display

Came across this by coincidence

It's something about the cardyb service and charsets, I think. Here's the fetch for the above post:
https://cardyb.bsky.app/v1/extract?url=http://www.mingpaocanada.com/van/htm/News/20230809/vas1h_r.htm
The page uses charset "big5-hkscs".
Here are two other fetches for sites with Chinese characters:
https://cardyb.bsky.app/v1/extract?url=https://world.taobao.com/ (uses utf8)
https://cardyb.bsky.app/v1/extract?url=https://www.thepaper.cn/ (uses utf8)

@Jacob2161 looks like this is a cardyb issue

authors: alimony mschwendener pfrazee

repo: bluesky-social/social-app


text:
Identity Unknown upon logging in

Describe the bug
When i log in it does not load anything and displays a red bar saying "identity unknown". I can log in the app but it does not display any page content, my account or anything.
To Reproduce
Steps to reproduce the behavior:

Log in

Expected behavior
Being able to log into my account and use the app.
Screenshots
iOS:

Web:

Details

Platform: iOS & Web
App version: 1.7.3

Can't reproduce.

Hi @TawayDev, sorry you are seeing that. Can you share some additional information to help us debug?

what is your account handle (and/or DID if you know that)?
are you on a self-hosted PDS or the Bluesky (*.bsky.social) PDS service? if self-hosted, did you migrate the account?
roughly when did you create your account? did you change handles recently?
have you done any DID operations using the API directly? (if you aren't sure, the answer is probably "no")

Hi @bnewbold, sorry for the late reply. I've figured it out. I viewed my account without logging in and it said invalid handle because i'm using my own domain so i changed it back to .bsky.social and then again to my own and it fixed the login issue. In console when the issue happened it just wrote {"error":"AuthMissing","message":"Authentication Required"}

authors: TawayDev bnewbold hellmrf


text:
Fix scrollbars on windows

Fixes extra scrollbar on windows
Stops the "Search for..." bit in the mini search results being hidden behind a spinner

Before
After

Why not put the vertical scrollbar only on list itself (ignoring the search box)?
And I think that you can customize the scrollbar visual in most recent browsers without big problem

authors: AdrianoCahete mozzius


text:
CA library not safe to use when shutting down

Following up on the recurring unexpected exceptions/segfaults during teardown:
@danielballan and @dmgav and I chatted about this a bit this morning and in a nutshell concluded:

Solving this in pyepics, along the lines of what @klauer you proposed here, is ultimately the correct way to tackle this. It will need some fleshing out though, to address the additional exceptions I mentioned here https://github.com/bluesky/ophyd/issues/834#issuecomment-615480304.
Alternatively, or additionally, to make ophyd play nice with current versions of pyepics, it may be a good idea to have ophyd avoid making any calls that involve libCA once it detects that Python is shutting down, since it is no longer safe to do so at that point.

The change in this PR is an idea on how to achieve point 2.
It appears to work, in that the caproto tests run without problems with this in place.
It feels a bit dirty though, and makes me question my sanity, so I welcome any and all critical comments and thoughts on why this is a horrible idea.

I was about to make the exact same comment as @danielballan (but with a global bool flag rather than a list).

I was going to ask: Is there an advantage to using a list over a bool?

Surprisingly, I thought about the separate bool flag too, but then I noticed that ca is used a few more times throughout the module, so ideally we should check if the flag is set in every function that is using ca.

I was hoping to get away with only checking in release_pvs (for now?), since I think that's the only one that could realistically be called during shutdown... is it safe to tentatively assume that, until proven otherwise?

I was going to ask: Is there an advantage to using a list over a bool?

I have no idea, but I know a few projects use list. I'm interested too.

The advantage is that if you do:
# modue.py
global_state = True

def change_state():
    global_state = False

and some other package in the module does
from .module import global_state

it will not get up to date information, where if you mutate global_state itself the reference remains useful. But that is not applicable here and I think the current implementation is good.

Power-cycled to re-run CI now that #864 is merged, which fixed some flake8 issues that appeared on master due to flake8 becoming stricter.

from .module import global_state

it will not get up to date information

Yeah I think some style guides forbid importing module variables for exactly this reason.

Thanks for the explanation @danielballan!
I modified it to work the way you suggested. Seems safer / a good habit to encourage, even if not strictly needed the way it is used here.

Will merge/release by end of week if there are no objections.

This still isn't quite right. Downstream library typhos test suite is hanging due to ophyd cleanup even with this PR:
Thread 0x00000001133fedc0 (most recent call first):
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 882 in pend_io
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 544 in wrapper
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 905 in poll
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 544 in wrapper
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 1053 in connect_channel
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 570 in wrapper
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 437 in connect
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 422 in wait_for_connection
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 729 in get_ctrlvars
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/ophyd/ophyd/_pyepics_shim.py", line 103 in _getarg
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 963 in count
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 357 in _check_auto_monitor
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 409 in auto_monitor
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 444 in clear_auto_monitor
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/ophyd/ophyd/_pyepics_shim.py", line 136 in release_pvs
  File "/Users/klauer/docs/Repos/ophyd/ophyd/signal.py", line 1708 in destroy
  File "/Users/klauer/mc/envs/lucid/lib/python3.6/weakref.py", line 548 in __call__
  File "/Users/klauer/mc/envs/lucid/lib/python3.6/weakref.py", line 624 in _exitfunc

Note that release_pvs clears auto monitor, which tries to connect because count isn't available. I had tried to fix this on pyepics's side, but apparently it was a huge can of worms (https://github.com/pyepics/pyepics/pull/203)

Thanks, @klauer. Will hold off in that case.

@hhslepicka with the new pyepics master, is your test suite still failing?

Not failing anymore

Just checking that I understood correctly: Typhos tests pass okay with both the latest pyepics master and this branch of ophyd, correct?
To be sure we're not ending up with redundant fixes I tried various on/off combinations of:

this branch
https://github.com/pyepics/pyepics/pull/204
https://github.com/pyepics/pyepics/commit/1bb4a68c81d5fe128cfdd43aa9cebf5d4bdeb9a2
https://github.com/bluesky/ophyd/pull/866

Caproto's tests pass with both 1+4 and 1+2+4. They fail with 2+4, 2+3, and 2+3+4.
If I understood correctly, Typhos tests pass with 1+2+4, but fail with just 1+4.
In summary: This PR should still be merged, but some downstream projects may experience failures unless they also have pyepics at the current master or later. 2 and 4 are needed and already merged, so no action required. 3 is not merged and doesn't need to be, so no action required.
Is this consistent with everyone else's understanding?

I think that's probably about right. Though any project with many disconnected PVs will greatly increase the possibility of the teardown hanging without (2) and (3). It certainly may happen with the ophyd test suite. Try even the simple:
import ophyd

sigs = {
    i: ophyd.EpicsSignal(f'sim:mtr{i}', name=f'sig{i}')
    for i in range(10000)
}

Hangs with pyepics/pyepics@9371da8 (on clear_auto_monitor)
Succeeds with pyepics/pyepics@master
This, in my opinion, indicates that there should be a new push for a pyepics tag and a bump in ophyd's requirement of it.

Typhos pass with:

pyepics - fixed from 204
ophyd - master

Okay, so we probably want to merge this and maybe beta tag it so we can fix caproto tests, but hold off on a full ophyd release until (3) is merged and pyepics has a new tag.
It would be great to confirm this branch doesn't break Typhos tests as well.

And a heads up on the pyepics side of things, with the current master the following snippet still triggers an uncatchable exception on teardown:
import epics

class Broken:
    def __init__(self, pv):
        self.pv = epics.get_pv(pv)
    def __del__(self):
        self.pv.clear_auto_monitor()

mypv = Broken('sim:mtr1')

Adding (3) replaces the exception with the RuntimeError that is introduced there. But that is a big improvement, because this one can be caught in del.
Using weakref.finalize in a simple example like this sidesteps the issue entirely, but as we've seen that's not enough by itself in more complex situations.

I also tried replacing, in epics/ca.py:
    if AUTO_CLEANUP:
        atexit.register(finalize_libca)

... with ...
    if AUTO_CLEANUP:
        weakref.finalize(sys.modules[__name__], finalize_libca)

... hoping that this would delay finalization enough to avoid the problem altogether, because the module shouldn't go out of scope until nothing needs it, ergo after del and any other finalizers referencing things in ca ran.
Unfortunately it made no noticeable difference. :(

@MikeHart85 why not pursue the fix for that at pyepics instead of patching here?
Seems like the best way despite not being the easier way.

That would be ideal, agreed. Initially it just wasn't really clear to me whether the error was on our end (calling functions we shouldn't be during teardown) or in pyepics (failing on function calls that should succeed or fail more gracefully).
Now I think it's fair to say it's the latter, but we already have these workarounds, and not yet any complete solution in pyepics. If we can find one, I'd certainly prefer that to this.

The pyepics PR referenced above would make this PR obsolete, but let's see if it is accepted before closing this.

With the pyepics PR merged, this PR is likely obsolete and can be closed without merging.
I'm not seeing Caproto test failure anymore locally, when using Ophyd 1.5.0 and the latest pyepics master. Would be great to confirm that this is also the case in CI and other projects that had similar issues.

authors: MikeHart85 danielballan dmgav hhslepicka klauer leofang tacaswell

repo: bluesky/ophyd


text:
検索結果の  で検索クエリがサニタイズされて表示されている

これはエスケープして表示されるのがよいのでは。

タグっぽい部分が削除されて表示されていました。
例: <test>hoi -> hoi

TextNormalizer.normalize_title でサニタイズされているっぽいので、オプションでどうにかするのは難しそう… https://github.com/kpumuk/meta-tags/blob/v2.1.0/lib/meta_tags/meta_tags_collection.rb#L90

ふむ〜

まぁ記号入れないと影響ないからとりあえずは...

Move to https://github.com/bm-sms/daimon-news/issues/385

authors: mtsmfm tricknotes

repo: bm-sms/daimon-news-multi-tenant


text:
Add bend ref_tilt

Add bend ref tilt, include example and fix bibtex entry.

Also added linear fringe kick to bend element

repo: bmad-sim/Bmad-X


text:
disable_postal_code_gather with override_service_body_id

Happens in 4.2.10.
When these two options are put together and you try to search for someone to talk to, it instead proceeds to the next menu where it asks you to search by location.  There is a conditional issues that I observed that needs to be fixed..
This condition is hit:
https://github.com/bmlt-enabled/yap/blob/968207e147cb1c7ffcd654526371b8efbe9dd557/legacy/input-method.php#L26-L27
Which causes a redirect to happen, when it's intended to go here first:
https://github.com/bmlt-enabled/yap/blob/968207e147cb1c7ffcd654526371b8efbe9dd557/legacy/input-method.php#L32-L34
I would fix this in the next version by writing tests to catch each condition.

will be fixed in 4.3.0

repo: bmlt-enabled/yap


text:
Pin API has non-working link to #Modes

In the options table, it says "see Modes" but the link to:
http://johnny-five.io/api/pin/#Modes
doesn't work.

Fixed https://github.com/rwaldron/johnny-five/wiki/Pin/b349aeb896b0861ad0316c6c7838e6c9d556882d

authors: Resseguie rwaldron


text:
[question] how tx.WriteTo do a consistent snapshot

Sorry if this is a dumb ques.

Bolt is a single file so it's easy to backup. You can use the Tx.WriteTo() function to write a consistent view of the database to a writer. If you call this from a read-only transaction, it will perform a hot backup and not block your other database reads and writes.

From the code, it just opens the file and do a read. But some write transactions are still modifying the file. Since we has a read tx, and make it meta0 in new file, it will hold the snapshot of the transaction. But new write txs are still writing, so we still copy new data but they just not reachable, am i right?
And since the fill rate is around 0.5, which means the WriteTo's efficiancy is 50% maximum?

Since we has a read tx, and make it meta0 in new file, it will hold the snapshot of the transaction. But new write txs are still writing, so we still copy new data but they just not reachable, am i right?

Yes, that's correct. The meta page points to the root of the B+tree which is immutable so those pages cannot be altered while the read transaction is open. Other free pages can be overwritten but those will be ignored since they are not accessible from the root.

And since the fill rate is around 0.5, which means the WriteTo's efficiancy is 50% maximum?

The FillPercent only affects how pages are split when they are filled. WriteTo() has the same affect as any other read-only transaction and simply prevents pages in that transaction from being reused. If you are copying for a long time then your database will start to grow.
It's best not to run Tx.WriteTo() over a slow connection if your DB is large. It's better to copy the file locally to your hard drive, stop the transaction, and then transfer the copied file over the slow connection.

repo: boltdb/bolt


text:
Academy-related SVG Updates

Jira
http://vjira2:8080/browse/BDS-1950?filter=-1
Summary
Icon-related updates to support the broader Academy work.
Details

Adjusts our existing icon-generator.js logic to not mistakenly rename width- or height- attributes, ONLY width and height attributes. Ensures these SVG icons are processed correctly given that they use attributes our original build wasn't accounting for.
Adds ~10 new SVG icons
Updates icon-related supporting files (ex. Icon schema)
Updates our global .gitignore to eventually get us to fully stop tracking any file changes to the dynamically generated index.js used in @bolt/components-icons

How to test

Confirm tests pass as expected
Review new icons on the Icon component's section to ensure the new icons are showing up

We already have a big mess with the naming conventions, for example, all of these postfixes mean the same thing, which is a bordered circle around the icon:

-circle
-circled
-open

I refuse to add -outline to that list. I'd recommend to use -open instead because that's the most used. The one instance of -circle and -circled can be refactored later.

I'm good with making this swap to unify what we have (and as you said, we can always update the naming across the board later on)

repo: boltdesignsystem/bolt


text:
Serializer Conformance Testing

Problem:
We need to ensure the serializers create SBOMs consistently, with the expected degradation and structure.
Proposal
We should create a collection of golden documents, each with different characteristics and challenges for the serializer. Some examples include: documents missing IDs, documents missing root nodes, documents with broken edges, etc.
Conformance tests would load the raw proto, feed the document into the serializer to generate a document in each format. If we have options for the serializers we should test all scenarios.
Paired with native tools to extract data from the documents (both SBOM tools and more lower level utilities like jq we then extract data from the documents:

Using this corpus of data, the generated documents and the tools we need, we create three kinds of tests:

Reference Tests
These tests take the generated document and compare the data against the known features of the golden documents. This includes checking the number of packages, structure of the SBOM, edges, top level nodes,

Format Data Tests
These tests have to do with data specific to each format: Are the SPDX relationships sound? Is the CycloneDX dependency tree complete? Is the supplier data in the documents correct? Is the SPDX package verification code correct? etc.

Format Conformance Tests
These tests mean running the "official" format validators against t the generated documents to ensure the serializer/writer pair is generating valid syntax.

Open Questions

Should we scaffold the tests early or wait until the serializers are more or less "complete"?

cc @houdini91 -- I'd be curious for your take here.

authors: jspeed-meyers puerco

repo: bom-squad/protobom


text:
Citation in Journal

I would like to cite this repository in a journal paper I'm currently writing as I have used most of the code here.
I have already included the reference to the original DeepLabV3+ paper, but I also want to include this repository.
What is the best way to cite it?
Thanks!

As you did not receive any other guidelines, I'd suggest to simply use a "code citation", as it is getting more and more common in academic journals
the bibtex format is somewhat like this
@code{Charles2013,
author = {Emil Zakirov},
title = {Keras-Deeplab-v3-plus},
year = {2018},
publisher = {GitHub},
journal = {GitHub repository},
howpublished = {\url{https://github.com/bonlime/keras-deeplab-v3-plus}},
commit = {YOUR-COMMIT-HERE}
}
but in general - you could simply acknowledge the contribution of Emil Zakirov for his repository https://github.com/bonlime/keras-deeplab-v3-plus, somewhere at the top/bottom of your paper

authors: eladmeir pedrogalher


text:
🛑 Jackett is down

In f4ce4d9, Jackett ($URLS_JACKETT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jackett is back up in c645656.


text:
Columns are added as full-width columns to the pages with one column

For example: Wall page
https://www.boonex.com/forums/topic/add-column-to-wall-timeline-page.htm

can't reproduce the problem, please describe it in more details with screenshots.


text:
Resolutions

Unsupported resolutions, ultrawide especially

Maybe there is a way to adjust by radar position.
With help of this?:
https://cookbook.fivem.net/2019/08/12/useful-snippet-getting-the-top-left-of-the-minimap-in-screen-coordinates/

What is the resolution you are using ?

2560x1080

I've added new minimap position finder you can test it out

works just fine now, however u closed other issue about

When it begins the spam ?

After spawning in.
After restarting resource.
Idk, just always.

authors: boostless iSentrie

repo: boostless/Boost-DynamicHud


text:
uninstall/install new boot2docker will not install new iso

Even uninstall the boot2docker old version and install the new version, the version is not changed.
It is because that uninstall command will not remove ~/.boot2docker directory which contain boot2docker.iso
Therefore during the new installation phase, start.sh detects the ~/.boot2docker/boot2docker.iso exists, then the copy/download will not happen.
Suggest to remove boot2docker VM in virtualbox and ~/.boot2docker directory completely, or at least give remind.
Or update the script to add a check if there are new iso, then replace it. (like upgrade)

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).

authors: larrycai tianon


text:
fix(layout): using react component and default props for layout to fa…

…cilitate overriding

:tada: This PR is included in version 1.0.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: bootstrap-styled/documentation


text:
🛑 boot.bpn.su is down

In 1b06d76, boot.bpn.su (boot.bpn.su) was down:

HTTP code: 0
Response time: 0 ms

Resolved: boot.bpn.su is back up in 313537c.

repo: boringplace/status


text:
Change IList to IEnumerable

For large data sets that are not Lists.. eg. from a CSV file, materializing to a list is not practical.
The change would involve swapping out IList in favor of IEnumerable where possible. (Most places in the code I saw only enumerate the IList and do not actually use IList members).
If you're open to making this change let me know and I can submit a pull request.
Nathan

There have already been PR for this that was merged but later reverted because List was required for  UpdateEntitiesIdentity(SetOutputIdentity).
https://github.com/borisdj/EFCore.BulkExtensions/issues/147
Maybe to consider supporting both, you can try making a change in that direction.
Simple solution could be just to add duplicate Extension methods, although I don't like going far away from DRY, and then see where can flow of functions be merged, similary as is done for BulkConfig/Action and Async/Sync.

Bulk methods are now receiving IEnumerable.


text:
Update for karma-jasmine 0.3.3+

Syntax is now fit/ddescribe: http://jasmine.github.io/2.1/focused_specs.html

@MattiLehtinen thanks mate!

authors: MattiLehtinen vvakame

repo: borisyankov/DefinitelyTyped


text:
ManagedDatabase: Do not begin/commit/rollback all DBs at once

Was looking more into ManagedDatabase and the pain it brings and realized that it should/could go.
The reason we needed it was due to the multiple Database instances we used to hold, which is not the case anymore.
So first step is to get rid of those wrappers, and the next thing to take care of will be finalization. That's why I lumped in the second commit, as we will need to properly shut-down before we can remove our reliance on the module dtor.

The small commit introduced a regression:
Unittesting agora.test.Flash#### FATAL ERROR: index [0] exceeds array of length 0
This node was started at source/agora/test/Flash.d:914
This most likely means that the node crashed due to an uncaught exception
If not, please file a bug at https://github.com/Geod24/localrest/
Full error: core.exception.ArrayIndexError@source/agora/node/FullNode.d(1159): index [0] exceeds array of length 0
----------------
core/exception.d:875 onArrayIndexError [0x11132fc6c]
core/exception.d:848 _d_arraybounds_index [0x1113301b5]
source/agora/node/FullNode.d:1159 nothrow @safe void agora.node.FullNode.FullNode.pushBlock(const(agora.consensus.data.Block.Block)).__lambda7() [0x110665b09]
core/thread/context.d:46 void core.thread.context.Callable.opCall() [0x11135c34c]
core/thread/fiber.d:1151 void core.thread.fiber.Fiber.run() [0x11135c4d8]
core/thread/fiber.d:198 fiber_entryPoint [0x11135c415]
./ci/run.sh: line 21:  3795 Abort trap: 6           ./build/agora-unittests

repo: bosagora/agora


text:
Reporting CNMP metrics with scollector on windows

I'm trying to add in reporting cnmp metrics with a config file for scollector on windows. I've tried using both 0.6.0-beta1 and 0.5.0. I added the following to the config file:
[[SNMP]]
  Community = "xxxxx"
  Host = "123.123.123.123"

When I try starting up scollector it complains about an unknown MIB cisco. I understand I can specify specific MIBs, however I'm not sure what I should be putting in there exactly (should I reference something I specify in [[MIBs]]? How should I reference the built in ones?). I've found where in the code the error message is generated from, but I don't know enough about go to figure out where the MIBs should be loaded from. As far as I can tell they're hard-coded in files like snmp_cisco.go but I can't work out what I've done wrong in the config. I've also tried putting an MIB file in the same directory as scollector and referencing it by name: MIBs = ["MIB-FILE"]
How can I add report on an cnmp compatible device using scollector on windows?

I've managed to figure it out; I found the code that defines the built in names:
"ifaces":   SNMPIfaces,
"ios":      SNMPCiscoIOS,
"asa":      SNMPCiscoASA,
"nxos":     SNMPCiscoNXOS,
"bridge":   SNMPBridge,
"ips":      SNMPIPAddresses,
"ciscobgp": SNMPCiscoBGP,
"sys":      SNMPSys,
"fortinet": SNMPFortinet,
"lag":      SNMPLag,

Looks like the config default of "cisco" isn't valid, presumably because it was broken into multiple builtins at some point, but the default value wasn't updated.
Maybe it's worth updating the default value and documentation somewhere? Happy to have a go at a pull request if it helps.

This correct, we broke them out because we discovered that SNMP can be pretty different between Cisco's various operating systems. So we broke this up per operating system that is created by Cisco.
In truth, there ends up being exceptions in the code per certain devices IIRC... Cisco monitoring is a mess.
A documentation update via PR would be welcome.

authors: georgeduckett kylebrandt

repo: bosun-monitor/bosun