text:
chore(deps): update common-dev-assets digest to 593e4fb

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
d8a1b79 -> 593e4fb

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

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

This PR has been generated by Renovate Bot.

/run pipeline

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

GitHub release
v4.1.1

Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to e492ef5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
b208c35 -> e492ef5

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

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

This PR has been generated by Renovate Bot.

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

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.10.17

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.10.16 -> v1.10.17

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.10.17
Compare Source
Bug Fixes

deps: update module github.com/ibm/platform-services-go-sdk to v0.44.0 (#602) (d141e39)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

/run pipeline

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


text:
chore(deps): update ci-deps

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
54b3d7e -> 0a5cc32

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.10.1 -> v1.10.8

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.16.1 -> v1.17.0

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.10.8
Compare Source
Bug Fixes

deps: update module github.com/gruntwork-io/terratest to v0.43.6 (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/576es/576)) (93c8433)

v1.10.7
Compare Source
Bug Fixes

deps: update gomod (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/572es/572)) (93b5090)

v1.10.6
Compare Source
Bug Fixes

deps: update github.com/ibm-cloud/bluemix-go digest to b838ccd (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/568es/568)) (2f444ce)

v1.10.5
Compare Source
Bug Fixes

deps: update module golang.org/x/crypto to v0.10.0 (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/566es/566)) (5e52db4)

v1.10.4
Compare Source
Bug Fixes

bug keep statefile(#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/564es/564)) (2f66c32)

v1.10.3
Compare Source
Bug Fixes

Update packages (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/563es/563)) (76d8e3e)

v1.10.2
Compare Source
Bug Fixes

deps: update module github.com/go-openapi/errors to v0.20.4 (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/561es/561)) (318ba3a)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.17.0
Compare Source
Features

CRA will now use SCC instances api instead of deprecated account api (#&#8203https://github.com/terraform-ibm-modules/common-pipeline-assets/issues/500es/500)) (4044cc1)
default CRA profile is now FSCloud 1.3.0 for v2 pipeline (#&#8203https://github.com/terraform-ibm-modules/common-pipeline-assets/issues/500es/500)) (4044cc1)

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

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

This PR has been generated by Renovate Bot.

/run pipeline

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


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
de9d7f6 -> 0685378

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.38.2 -> v1.38.3

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.38.3
Compare Source
Bug Fixes

deps: update gomod (#864) (802df12)

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

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

This PR has been generated by Renovate Bot.

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.22 -> 1.22.0

github.com/IBM-Cloud/power-go-client
v1.7.1 -> v1.8.1

github.com/IBM/platform-services-go-sdk
v0.69.0 -> v0.69.1

/run pipeline

/run pipeline

/run pipeline

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.22 -> 1.22.0

github.com/IBM-Cloud/power-go-client
v1.7.1 -> v1.8.1

github.com/IBM/platform-services-go-sdk
v0.69.0 -> v0.69.1

/run pipeline

/run pipeline

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.22 -> 1.22.0

github.com/IBM-Cloud/power-go-client
v1.7.1 -> v1.8.1

github.com/IBM/platform-services-go-sdk
v0.69.0 -> v0.69.1

/run pipeline

/run pipeline

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

GitHub release
v1.4.28

Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
5f5fd35 -> 5cf7d9c

github.com/gruntwork-io/terratest
require
patch
v0.48.0 -> v0.48.1

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.42.5 -> v1.42.7

Release Notes

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.48.1
Compare Source
Modules affected

helm
azure
aws
k8s

What's Changed

feat: Adding release instructions in PR by @yhakbar in https://github.com/gruntwork-io/terratest/pull/1488
fix: Fixing the TestRemoteChartRender Unit Test failure by pecifing remote chart version by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1486
fix: Fix terraform-azure-aks-example unit test failure.  by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1489
chore: add function to retrieve latest version of a policy document by @james03160927 in https://github.com/gruntwork-io/terratest/pull/1490
fix: honor options.RestConfig in tunnel.ForwardPortE by @jduepmeier in https://github.com/gruntwork-io/terratest/pull/1464

New Contributors

@jduepmeier made their first contribution in https://github.com/gruntwork-io/terratest/pull/1464

Full Changelog: https://github.com/gruntwork-io/terratest/compare/v0.48.0...v0.48.1

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.42.7
Compare Source
Bug Fixes

deps: update module github.com/ibm/vpc-go-sdk to v0.64.0 (#906) (1d061e2)

v1.42.6
Compare Source
Bug Fixes

deps: update module github.com/gruntwork-io/terratest to v0.48.1 (#905) (511dc17)

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

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

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v1.4.46

Your semantic-release bot :package::rocket:


text:
[Feature Request]: Improve the home teleport

Is your feature request related to a problem?
The home command currently teleports the user to the 0 0 0 coordinates of the block where the home was set. This creates 2 issues:

The player is teleported to the corner of 4 different blocks, potentially partially inside a wall or in a spot where there is no ground to stand on.
If the home was set on a slab or any other non-full block, the teleporting player might phase through the ground.

Solution(s)
Make the command teleport the player to the middle of the block (0.5 ~ 0.5) and remember the Y coordinates.
Describe alternatives you've considered
No response
Mod Version
forge-1.20.1-1.1.0
Mod Loader Version
47.1.44
Mod Loader
Forge
Additional context
No response

Can be closed by ffb797719d30586115c943cea158980ff9f9f918

source: gharchive/issue

repo: terrarium-earth/Prometheus

license: MIT


text:
SW-5661 Add phases for application process

Add two new cohort phases for the two steps of the application process.
Give them IDs starting at 100 so it's clear they don't correspond to phase
numbers.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2170
#2169  👈
#2168
#2167
main

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

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Jul 17, 5:06 PM EDT: @sgrimm merged this pull request with Graphite.

repo: terraware/terraware-server


text:
Update npm version lookup 2

Didn't realize that
npm show @terraware/web-components versions --json | grep ${PACKAGE_JSON_VERSION} > /tmp/npm-output
was failing with an error if the version didn't exist.
Replace with something that works.

I will take a crack at simplifying this.
Now that npm view/show returns an error (unlike before), we can use the shell last error status $?
MacBook-Pro:web-components kb$ npm show @terraware/web-components@1.0.5 maintainers
terraware <npm@terraformation.com>
MacBook-Pro:web-components kb$ echo $?
0
MacBook-Pro:web-components kb$ npm show @terraware/web-components@5.0.5 maintainers
npm ERR! code E404
npm ERR! 404 No match found for version 5.0.5
npm ERR! 404
npm ERR! 404  '@terraware/web-components@5.0.5' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/kb/.npm/_logs/2022-12-03T15_29_12_152Z-debug-0.log
MacBook-Pro:web-components kb$ echo $?
1
MacBook-Pro:web-components kb$ npm show @terraware/web-components@1.0.5 maintainers 2> /tmp/err
terraware <npm@terraformation.com>
MacBook-Pro:web-components kb$ echo $?
0
MacBook-Pro:web-components kb$ npm show @terraware/web-components@5.0.5 maintainers 2> /tmp/err
MacBook-Pro:web-components kb$ echo $?
1
MacBook-Pro:web-components kb$

authors: charlie-tf karthikbtf

repo: terraware/web-components


text:
fix: remove functions from dependency lists that normally change on every render

If we want to use, for example, useOlLayer like this:
const layer = useOlLayer(() => new OlLayerVector({}), []);

we need to exclude the constructor function from any dependency list as the function will be recreated on every render.
For props that gets passed in like onSuccess we would not be able to use something like this:
<Component
  onSuccess={() => do something}
  />

At the moment we normally assume that a change in these functions should not cause a rerender. I think it is done similarly in existing libraries like antd where only changes in other props will cause rerenders.

Otherwise we would need to wrap every callback into a useCallback. Which would not be a good practice but would require some work.

repo: terrestris/react-util


text:
image not saving

const saveImage = () => {
   console.log('saved');
   imageRef.current.save({
     includeImage: true,
     cropToImageSize: true,
     imageType: 'jpg',
   });
 };

<SketchCanvas
              localSourceImage={{filename: imageString}}
              ref={imageRef}
              style={{flex: 1}}
              strokeColor={'red'}
              strokeWidth={3}
              onSketchSaved={(success, path) => {
                console.log('here');
                console.log('success is', success);
                console.log('path is', path);
                }}>
</SketchCanvas>
<Button title="save" onPress={saveImage} />

Nothing happens when clicking saveImage and onSketchSaved doesn't get executed.

any updates?

repo: terrylinla/react-native-sketch-canvas

license: mit

license_source: bigquery


text:
Bugfix: reaction to submit form when press Enter key

When you press the Enter key, the form is sent in an encrypted format.

While enabling this plugin, the type="submit" will be replaced with type="button" so the submit event will not be fired. Could you provide your HTML code to let me know what causes this issue.

Hello.
Let's go to https://codepen.io/Rekryt/pen/XogaaJ?editors=1010
Place your cursor to the input, write some text...

and press keyboard key "Enter", for submit form...

At the Networking we will see, that disableAutoFill not works correctly (name of input is not replaced to "email").

It appears to behave properly for me

authors: Rekryt barrychapman terrylinooo


text:
Add check_csr.sh

Description
Adds a simple script to validate CSR submissions
Type of change

[X] Documentation update

Checklist:
Confirm you have completed the following steps:

[X] I have made corresponding updates to the documentation.

@aaronpkahn cool script, but it's giving me an error.
% openssl req -out tesla.chqtest.net.csr -key ~/garnet/keys/tesla-api/tesla.chqtest.net/com.tesla.3p.key.pem -subj /CN=tesla.chqtest.net/ -new

% cat tesla.chqtest.net.csr
-----BEGIN CERTIFICATE REQUEST-----
MIHWMH4CAQAwHDEaMBgGA1UEAwwRdGVzbGEuY2hxdGVzdC5uZXQwWTATBgcqhkjO
PQIBBggqhkjOPQMBBwNCAAR4UUCCeq2kTehcBLSlmwl3DfEimd4PQhKLA5PUqekz
F6FradBOWa5StLZgCqbEngf6p+YTFSVPIqPK6rU1kggQoAAwCgYIKoZIzj0EAwID
SAAwRQIhAOpVBBg1zyaD6mCyU9dq1tt5XNw+x9lBfcXfmBXN0Q7wAiBh6P5OyUvN
fHCPvdIGZD4CzC6Thgme/Jjhn0lVuw8NZg==
-----END CERTIFICATE REQUEST-----

% ./tools/check_csr.sh tesla.chqtest.net.csr
----
CSR: tesla.chqtest.net.csr
Host: subject=CN = tesla.chqtest.net
curl: (3) URL rejected: Malformed input to a URL function
Could not retrieve https://subject=CN = tesla.chqtest.net/.well-known/appspecific/com.tesla.3p.public-key.pem

Is there a bug in the script or have I done something wrong? My CSR creation command comes from the instructions at https://developer.tesla.com/docs/fleet-api#fleet-telemetry

The check string also didnt work for me, and I generated my CSR using the provided openssl instruction. the SED command does not account for whitespace.
openssl req -in teslemetry.com/teslemetry.com.csr -subject -noout | sed 's/subject=[\/]*CN=//'
subject=CN = teslemetry.com

authors: Bre77 aaronpkahn jbanyer

repo: teslamotors/fleet-telemetry


text:
LIBUSB_ERROR_IO on Raspian (Raspberry Pi Linux)

Hi, I'm receiving the following error on Raspian for Raspberry Pi.  The exact same code works on Windows 10.  Also, I am able to connect and stream outputs from the same device using Python on my Raspberry Pi with no issues.
Can anyone offer any advice?
events.js:165
      throw er; // Unhandled 'error' event
      ^

Error: LIBUSB_ERROR_IO
    at startTransfer (/home/pi/dev-projects/node-security/node_modules/usb/usb.js:347:6)
    at Array.forEach (<anonymous>)
    at InEndpoint.startPoll (/home/pi/dev-projects/node-security/node_modules/usb/usb.js:354:21)
    at Object.<anonymous> (/home/pi/dev-projects/node-security/app.js:10:24)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Function.Module.runMain (module.js:690:10)
Emitted 'error' event at:
    at startTransfer (/home/pi/dev-projects/node-security/node_modules/usb/usb.js:349:9)
    at Array.forEach (<anonymous>)
    [... lines matching original stack trace ...]
    at Function.Module.runMain (module.js:690:10)

Here's my code ...
const usb = require('usb');

let device = usb.findByIds(3034, 10296);
device.open();
device.interfaces[0].endpoints[0].transferType = 0 // Only get outputs when changing transferType to 0

interface = device.interfaces[0];
interface.claim();

interface.endpoints[0].startPoll(3, 65); // < == This line causing the error

interface.endpoints[0].on('data', (data) => {
  console.log(data);
});

interface.endpoints[0].on('error', (error) => {
  console.log(error);
});

You can't change the transferType like that. It comes from the endpoint descriptor, and changing it in JS doesn't change what the kernel and device are expecting the endpoint type to be. I would expect to get a LIBUSB_ERROR_IO when attempting to submit a transfer with the wrong endpoint type.

authors: abovino kevinmehall

repo: tessel/node-usb


text:
Update refactor

Note that the target is jon-t2-update

"Test updates—fully green!"
Hahahahaha—except when running jshint. Whoops!!

Review items addressed, Travis is green, @johnnyman727 said " merge into my branch and merge my branch into master once you've handled those comments."... so here we go!


text:
TesseractConfig.cmake

After cmake generation, TesseractConfig.cmake not contains ccutil include directory. And when i try use TesseractConfig.cmake in my build - receive error platform.h not found

@egorpugin Can you have a look on this?

What headers should be public?
I thought all headers from api/
Tesseract really has bad directories structure.
Probably it should be reorganized as in many other projects.
include - public includes
src/[subdirs] - dir with sources and private headers

At least headers that are mentioned in "include_HEADERS" in Makefile.am should be installed/public.
Each directory has its own Makefile.am...

While using tesseract with TesseractConfig.cmake (without install), we can include several directories.
So, unintentionally we will give an access to all headers from those dirs. Not only to "include_HEADERS".
Users won't know it and could use noinst headers, so later they'll have issues.

Fixed in 7b94871ba20

authors: Pastor egorpugin zdenop

repo: tesseract-ocr/tesseract


text:
Unable to detect characters in simple two-word image

I'm having trouble getting tesseract to recognize any characters in the following image:

When I run tesseract from the command line on this image, I get "Empty page!!" - that is, no results - returned. Based on my reading of the Improving Quality section of the wiki, I thought that the issue might be that the words in this image are not dictionary words. With that in mind, I have tried both disabling the tesseract dictionaries altogether (using the load_system_dawg and load_freq_dawg config flags) as well as augmenting the existing dictionary with these additional words (LAO and CAUD). Neither of those approaches worked. I have tried tesseract versions 3, 4, and have built version 5 from source on a Mac computer. All have given the same result.
Curiously, if I type the exact words from that image into a word processor and take a screenshot, it works: the resulting image is readable by tesseract. It correctly parses each character. Here is that image:

The only difference between the two images is that the first one is of a slightly lower resolution/quality. Am I then to believe that tesseract is unable to recognize characters in a slightly inferior quality image like that? Is there anything I can do to improve that image quality? Is there something else I'm missing?
Thanks in advance.

Please respect guidelines for posting issue: use tesseract user forum for asking questions/support.

authors: rmacqueen zdenop


text:
Send gchat alert message to dev team if unstable image creation failed.

When a PR is submitted, pre-main.yaml workflow will create the container and push it into quay.io. This change will notify via gchat msg whenever there is an issue with one of the steps that resulted in that new unstable image not being created (hence not pushed) properly.

@sebrandon1

In a subsequent PR, we should add this to the tnf-image.yml for the same idea when our release runs fail.

Yep, good idea.


text:
execInContainer exit code

I am trying to find a way to determine if a command executed inside a container via execInContainer is successful or not, however ExecResult only returns stdout and stderr which does not really help..
There is a comment in the code "due to the limitations of the docker API, there's no easy way to get the result code from the process we ran" however it is quite old so I am not sure it is relevant anymore. Furthermore, docker-java exposes an API to inspect the command status via "inspectExecCmd", which returns the exit code.
Is it possible to add the exit code from inspectExecCmd to the ExecResult?

Hi @dmarkhas,
You're right, inspectExecCmd returns the exit code and can be used for this use case.
We a class for the exec pattern:
https://github.com/testcontainers/testcontainers-java/blob/master/core/src/main/java/org/testcontainers/containers/ExecInContainerPattern.java
The implementation should be as simple as adding a field to ExecResult class and calling the API you discovered before constructing it:
https://github.com/testcontainers/testcontainers-java/blob/604fd0ee0e8aba424c8ea63e887b4b941bb533d5/core/src/main/java/org/testcontainers/containers/ExecInContainerPattern.java#L86-L88
Would you like to contribute it? 😊

I'll be happy to :)
Will try to get it done tomorrow..

@dmarkhas that would be great, thank you!
There is also:
https://github.com/testcontainers/testcontainers-java/blob/master/core/src/main/java/org/testcontainers/containers/wait/internal/InternalCommandPortListeningCheck.java
and it will benefit a lot from this change 👍 We had to use a string constant to check the result :D

Thank you for your inputs and merging the PR! I forgot to update the docs to reflect this new API, so I have done so now in #1319 .

@bsideup are you guys planning to publish a release soon? or is there a snapshots repository I can use in the meanwhile? 😄

@dmarkhas we prefer Jitpack for it :)

Awesome 😸

authors: bsideup dmarkhas

repo: testcontainers/testcontainers-java


text:
[Bug] Reuse hash changes any time my docker registry token is renewed

Hi,
I have this really weird behaviour where testcontainers are reused but not always. If the container was just started, running my test again never starts a new one, but after a moment, about 5 minutes, it always creates a new one.
A little debugging session led me to the hash method in GenericContainer class.
It appears the createCommand used to generate that hash, contains docker auth elements.
Under the key authConfig, I think the key password contains the docker registry token because the username is _dcgcloud_token (using a google artifact registry as a docker registry).
The token being renewed automatically every now and then it breaks the container reusability.
As I see it we could simply remove this key from the command just before generating the hash, would that make sense to you ?

Hi @Dayde,
What version of Testcontainers are you using?

This was fixed in docker-java 3.2.13 and the latest Testcontainers uses it:
https://github.com/docker-java/docker-java/pull/1807
https://github.com/testcontainers/testcontainers-java/blob/46ba812ab2315626ca3d90c7432a2a0bbb544f5e/core/build.gradle#L79

You’re perfectly right I bumped the version to 1.17.1 before reporting this but I must have skipped a necessary maven clean/reload in IJ as I was still seeing the issue then.
I reran a bunch of test today and it’s working like a charm.
Sorry for this waste of your time and many thanks for the fix 😄

authors: Dayde bsideup


text:
[Enhancement]: ScriptUtils::runInitScript should load script also from local directory

Module
Core
Proposal
The ScriptUtils::runInitScript only accepts paths from the classpath. This isn't as powerful as I would have expected given:

Absolute paths or relative paths local to the maven module, for example, are useful as well
Being on the classpath means the Maven compile (or test-compile) phase must have run, but what if I want to use testcontainers in the generate-sources (or generate-test-sources) phase, e.g. to generate jOOQ code? In that case, the init scripts aren't available on the classpath yet, unless I create a separate module just for this, which is overkill

Additionally, there are many cases where the script doesn't have to be a file. An inline script in String form would suffice, e.g.
container.initScript("""
  create schema test;
  create table test.test (test int);
""");

Hi @lukaseder, thanks for raising the issue.
Currently, it is recommended to use Flyway or Liquibase for database initialization. Also, most of the database images provide a directory to initialize the database. So, withCopyToContainer and withCopyFileToContainer can be used along with Transferable.of, MountableFile.forClasspathResource and MountableFile.forHostPath. I wonder if those would help to fix your issue.

Additionally, there are many cases where the script doesn't have to be a file. An inline script in String form would suffice

Testcontainers provides Transferable in order to achieve your need.
String schema = """
    create schema test;
    create table test.test (test int);
    """;
...
withCopyToContainer(Transferable.of(schema), "/docker-entrypoint-initdb.d/schema.sql")

See mysql and postgres
ScriptUtils.runInitScript also has some limitations regarding sql syntax. That's the reason why our recommendation on relying to existing mechanism.

Currently, it is recommended to use Flyway or Liquibase for database initialization.

Ironically, I was looking into using testcontainers here precisely because of Flyway breaking tons of things in their upgrades, and for the use-case I had, I didn't want to debug through those breakages. The use-case is a simple example that just runs a single script containing 1 table, where Flyway (or Liquibase) would be total overkill.
I resorted to using sql-maven-plugin, because it does the job during the build.
I understand that this init script utility isn't a top priority, because it will always be a very limited tool. Though, being able to load a file with absolute (or relative) path rather than a file from the classpath seems to be relatively simple? A lot of build tools (including Flyway and Liquibase) support both classpaths and actual paths for such things. I think this looks like a low hanging fruit. If the 2 existing Resource lookups fail, just try checking if the path resolves to an actual java.io.File with File::exists, and if so, load that.

Also, most of the database images provide a directory to initialize the database. So, withCopyToContainer and withCopyFileToContainer can be used along with Transferable.of, MountableFile.forClasspathResource and MountableFile.forHostPath. I wonder if those would help to fix your issue.

Appreciate the workarounds, thanks. This will be helpful for others, I'm sure. In my case, I just wanted to avoid complexity given the example is so super simple. I removed Flyway because of complexity (that wasn't essential to the example). I'm sure a lot of users will find the init script very useful for exactly this purpose: Avoiding complexity.

authors: eddumelendez lukaseder


text:
docker-modem depencency  new version breaks tests

Expected Behaviour
Tests work correctly: postgres db runs in docker correctly
Actual Behaviour
Got error: No Docker client strategy found
Testcontainer Logs
testcontainers DEBUG Found applicable Docker client strategy: UnixSocketStrategy +0ms
testcontainers DEBUG Testing Docker client strategy URI: unix:///var/run/docker.sock +1ms
testcontainers WARN  Docker client strategy UnixSocketStrategy is not reachable +59ms
No Docker client strategy found
at node_modules/.pnpm/testcontainers@9.1.3/node_modules/testcontainers/dist/docker/docker-client.js:46:11
at fulfilled (node_modules/.pnpm/testcontainers@9.1.3/node_modules/testcontainers/dist/docker/docker-client.js:5:58)
Environment Information

Operating System: Ubuntu 22.04.2 LTS
Docker Version: Docker version 23.0.1, build a5ee5b1
Node version: v18.12.1
Testcontainers version: 9.1.3 (^9.0.0).

Description
Hello. After i today reinstall node-modules, i face the problem during tests running: No Docker client strategy found. But last week (on friday) everything was normal. I started looking for problem:

Increased testcontainers version from 8.16.0 to 9.1.3 - no changes.
Found that testcontainers's dependency - dockerode relesed a new version these holidays: 3.3.4 -> 3.3.5. I decreased it to 3.3.4 again in package.json in overrides section - no changes.
Found that dockerode's dependency - docker-modem relesed a new version these holidays: 3.0.6 -> 3.0.7. I decreased it to 3.0.6 again in package.json in overrides section. My tests started work correctly. There are the changes: https://github.com/apocas/docker-modem/compare/v3.0.6...v3.0.7.

I use testcontainers to run postges db this common way:
const container = await new GenericContainer('postgres:14-alpine')
      .withEnvironment({
        POSTGRES_DB: 'db_name',
        POSTGRES_USER: 'db_user_name',
        POSTGRES_PASSWORD: 'db_password',
      })
      .withExposedPorts('db_port')
      .withStartupTimeout(300000)
      .start();

Actually i don't know who should care about this problem (testcontainer or docker-modem maintainers)

Thanks for raising @fx-it, I will look into it.

Stepped on it just now

docker-modem has been released with a breaking change as a patch bump v3.0.6 -> v3.0.7.
Suggestion: pin v3.0.6 until resolved.

Hi @fx-it, @Gaen, could you please test testcontainers@9.1.4-beta.2 and confirm it's working for you?

Although I see the author of docker-modem is rolling back the change as another patch release, so I think there's nothing for us to do here.

Tomorrow will try on the lastest version of docker-modem and with stable version of testcontainers. I have to go now.

With the new docker-modem version this is resolved.

confirmed, works

authors: Gaen cristianrgreco fx-it

repo: testcontainers/testcontainers-node


text:
[docs] Add examples

Is your feature request related to a problem? Please describe.
For a person new to vale and its configuration, it can be a challenging task to configure and setup all the checks.
Besides the docs on https://errata-ai.github.io/vale/styles/, lots of the checks do not give any "easy" examples.
We should add text examples as a comment to every check.
In that way, users who are not wizards with "regex" can actually understand what the check is doing and how it looks like.
Describe the solution you'd like
Add a comment to every check and/or the docs explaining better what the check is doing with an example.

Yeah, I've wanted to do this for a while, and am about to create a style guide guide(!) for a client, so might use this as a good motivation to do this.

I started a bit already, not finished yet.
The way I am doing it now, is to create a "simple" README as overview and also add examples as comments to the yaml files itself: https://github.com/testthedocs/vale-styles/tree/master/ttd-light
Not sure, yet if that is a good approach but at least it feels better so far :)

authors: ChrisChinchilla svx

repo: testthedocs/vale-styles


text:
Exposure Graph Addition to SkyTab

Added a bunch of different stuff: exposure graph, adjusting the positioning of graphs and titles, added key for sunrise/sunset lines which were also added. No moon images yet, still waiting on those I think. Only "new" libraries used are from astropy, astroplan, pytz, matplotllib, and datetime.

data through end of March is online...
Clear Skies!

Elizabeth M Warner
UMD Obs Director
@.***
301-405-6555

On 4/6/2022 12:31 PM, Peter Teuben wrote:

I've merged it, I'll re-run a specific night later today so we can
review the new view, should be a good one!
—
Reply to this email directly, view it on GitHub
https://github.com/teuben/pyASC/pull/143#issuecomment-1090469625, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADP7D2YUHNM5MS76CX7I5G3VDW355ANCNFSM5SWTA77Q.
You are receiving this because you are subscribed to this
thread.Message ID: @.***>

repo: teuben/pyASC


text:
pow: offline aggregator CLI mode

Somewhat rough.
Already opening for review. I'll merge when this lands on a powergate release tomorrow.

Tagged now in https://github.com/textileio/powergate/releases/tag/v2.6.2
Merging.

repo: textileio/docs


text:
Custom storage stable

This PR add custom key value database to storage

@mambisi closing this, replaced by #840 which includes some cleanup, addresses some of the comments and is formatted

authors: mambisi tizoc

repo: tezedge/tezedge


text:
Wrong key 'exclude_dirs'

I'm not sure if this is a bug or merely a documentation issue.
$ organize check
Checking: /Users/soehlert/Library/Application Support/organize/config.yaml
...
snip
....
Wrong key 'exclude_dirs' in {'locations': ['~/Downloads'], 'exclude_dirs': ['! ~/Downloads/test'], 'subfolders':
False, 'filters': [{'created': {'days': 30, 'mode': 'older'}}], 'actions': ['trash']}

$ cat "/Users/soehlert/Library/Application Support/organize/config.yaml"
rules:
  # Old files
  - locations:
      - '~/Downloads'
    exclude_dirs:
      - '! ~/Downloads/test'
    subfolders: false
    filters:
      - created:
          days: 30
          mode: older
    actions:
      - trash

$ organize --version
organize, version 2.0.3

This errors out (I can share more of the output too if it's helpful)
$ cat "/Users/soehlert/Library/Application Support/organize/config.yaml"
rules:
  # Old files
  - locations:
      - '~/Downloads'
      - '! ~/Downloads/test'
    subfolders: false
    filters:
      - created:
          days: 30
          mode: older
    actions:
      - trash

$ organize check
Checking: /Users/soehlert/Library/Application Support/organize/config.yaml
Config is valid.

This config works, but according to the migration guide, this syntax is not valid anymore.
REMOVED: The exclamation mark exclude syntax (! ~/Desktop/exclude). See [Location options](https://organize.readthedocs.io/en/latest/locations/#location-options).

Yes in that case the documentation is not as clear as it should be. Try something like this:
rules:
  # Old files
  - locations:
      - path: '~/Downloads'
        exclude_dirs:
          - "test"
    subfolders: false
    filters:
      - created:
          days: 30
          mode: older
    actions:
      - trash

Note that if you disable the subfolders you don't need to exclude the test dir because it is never visited.

authors: soehlert tfeldmann

repo: tfeldmann/organize


text:
Create branch : use git.branchPrefix

Our branching policy is to name branches with the developers prefix.
Therefore, we're using the "git.branchPrefix" setting in VS Code to propose a default branch prefix (e.g. FVE/) when creating a new branch via 'Git: create branch'.
If we would create a branch from a work item in simplify, it would be nice if the proposed branch name (currently empty) would take info account the "git.branchPrefix" setting too.
More info: https://code.visualstudio.com/updates/v1_68#_git-branch-prefix

@fvet This should be fixed now and will be available with the next release. If not, please re-open and let us know what is missing

authors: fvet tfenster

repo: tfenster/azdevops-vscode-simplify

license: Unlicense


text:
Is using collection.models safe?

Hi guys,
I'm using collection.models to iterate on the models after fetchAll().
Since it's not in the documentation, could there be a problem or is it safe to use ?
Thanks !

Hi @Titozzz
I would suggest you to use the standard way that Bookshelf provides. All collections are populated with a list of lodash methods. The full list of lodash methods are also documented.
So you could easily do:
collection.map(function(model) {
  // perform mapping operation
})

Thanks you very much,
Will update my code then  :smile:
@vellotis

authors: Titozzz vellotis

repo: tgriesser/bookshelf


text:
Large Insert Failure

Large insert fails when using the query builder and executing functionality.
When create the query and cast it to a string and pass it to the knex.raw() execution method the query works perfectly.
var knex = require('knex')({
    client: 'pg',
    connection: connectionString,
    searchPath: 'knex,public',
    pool: {
        min: 0,
        max: 10
    },
    useNullAsDefault: false
});

var insert_data = [];
for (var i = 0; i < 6432; i++) {
    insert_data.push({
        "column1": 'text',
        "column2": 'text',
        "column3": 'text',
        "column4": 'text',
        "column5": 'text',
        "column6": 'text',
        "column7": 'text',
        "column8": 'text',
        "column9": 'text',
        "column10": 'text',
        "column11": 'text',
        "column12": 'text',
        "column13": 'text',
        "column14": 'text',
        "column15": 'text',
        "column16": 'text',
        "column17": 'text',
        "column18": 'text',
        "column19": 'text',
        "column20": 'text',
        "column21": 'text',
        "column22": 'text',
        "column23": 'text',
        "column24": 'text'
    });
}

/**
This method fails every time with an error from Postgres DB with the following error message:
      bind message supplies 36160 parameters, but prepared statement "" requires 167232
**/

knex('events').insert(insert_data)
    .then(function() {
        // handle success

    })
    .catch(function(err) {
        //This will always fail
    });

var insertQuery = knex('events').insert(insert_data).toString();
knex.raw(insertQuery)
    .then(function() {
        // this works

    })
    .catch(function(err) {});

Call to execute function for prepared statement exceeds the maximum numbers of parameters to a function in Postgres; we were having the same issue.
You just need to insert in smaller batches, you can get the maximum number of parameters that your build of Postgres accepts for functions, go slightly below for a safe limit and then calculate your batch size for a table at runtime by doing var batchSizeInRows = Math.ceil(maxFnParams * 0.95 / columnsPerRow).

Baseline is that even when using knex, one has to respect limits set by the underlying DB.

authors: bernays elhigu fennecbutt

repo: tgriesser/knex


text:
Ensure errors in batchInsert do not end up 'unhandled'. Fixes #1880

Not my finest work, but batchInsert needs a complete rewrite down the line anyways. Consider this a temporary fix and/or improvement to an otherwise broken class.

Thank you for fixing this, when can we expect this fix to be published?

I gave this late review, all good 👍

authors: elhigu lhaggar wubzz


text:
🛑 VPN is down

In 7317637, VPN ($SECRET_VPN_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: VPN is back up in 63d50ff after 13 minutes.

repo: tgstation-operations/status


text:
Split analyzer from the treemap UI code

This issue is a place to discuss and track a possible separation of webpack analyzer plugin code from the reporter UI code.
This idea was triggered by a proposal to add sunburst charts to the UI, where @th0r and me eventually thought it might be interesting to split these two concerns to distinct packages:

Or that the UI that is opened could be configurable, so that I could build a totally separate npm package that would only contain the UI parts that could be plugged into this packages webpack parts.

That's a very interesting idea and, at first glance, it won't be too hard to split analyzer from report UI.
We can move all current UI code from webpack-bundle-analyzer into, say, webpack-bundle-analyzer-treemap-reporter.
webpack-bundle-analyzer will be responsible only for analyzing bundle and feeding this info to reporter-plugins whose responsibility will be showing it in any way.
And the nice thing is reporter is not limited to some UI stuff - it can do anything it want with provided data!

I didn't hack on this on Christmas break but instead hacked on something completely different from work related matters to get a good vacation 🎅 . If I'll get to this, I'll let you know.

I'm gonna give this a go now. @bitpshr, would it be OK to try to get your beautiful sunburst chart to work first? It could be created as a webpack-bundle-analyzer-reporter-sunburst for example, if we'd want to try to prefix all the different reporters with webpack-bundle-analyzer-reporter- to ease discoverability.

Continuing from the refactoring done in #40, the current situation has a folder structure looking like this:
webpack-bundle-analyzer/
├── client
│   ├── components
│   └── vendor
├── lib
│   ├── bin
│   ├── chartData
│   └── viewer
├── node_modules
├── public
├── src
│   ├── bin
│   ├── chartData
│   └── viewer
├── test
│   ├── bundles
│   ├── src
│   └── stats
└── views

The only things reaching into top-level client, public and views folders are the root-level webpack.config.js and code under src/viewer.
Those folders and the webpack config form the implementation of the current treemap reporter.
I could extract the entire src/viewer/ folder to a new package, so that new reporters could create their own server and static strategies at will. This way all that the new reporters would need to do were to export two functions:
function generateReport(chartData, { openBrowser, reportFilename, bundleDir, logger })

and
function startServer(chartData, { openBrowser, port, logger })

The plugin's analyzerMode configuration option would select one of these. This way it would be up to the author of individual reporters to implement the static generation the way they would want to do it and to use whichever templating engine they'd like for the server build.
It might be a bit more difficult to try to extract things deeper down than these two functions, as it starts to get quite opinionated at that point and the separated reporters would be less powerful.
Take a look at the treemap implementation of these two functions:

generateReport
[startServer](https://github.com/th0r/webpack-bundle-analyzer/blob/84bb739330f5e7b2b6306f7ff2613adff07b8ad0/src/viewer/startServer.js]

What do you think? Would this be a good split point, or should I aim for something less powerful?

Here's a proof of concept example showing what the code layout could look like: https://github.com/valscion/webpack-bundle-analyzer/pull/1
The reporter used could be customized with the CLI flag --reporter or -R, providing it either a npm package name or an absolute path to a file exporting generateReport and startServer functions as described in my post above.
Another way to customize the reporter would be to pass a module exporting those same functions as the reporter option for the plugin.

What do you think? Would this be a good split point, or should I aim for something less powerful?

I'll answer my own question:
I don't think this actually is a good split point, or at least not the best API.
I'd like to test out a monorepo approach for here, to really separate the reporter-treemap as its own npm package and to fine-tune the custom reporter API to be better.
For that, I'd also like to redo some build and test infrastructure currently on the repository to get better test coverage and to get a smooth build pipeline across all the packages this repository could contain.
I also wouldn't want to put many hours to this unless you would be okay with my changes, @th0r. How much space would you be willing to give me with the current infrastructure? Could I help you maintain this repository and change things around internally, targeting to a new v3 release that really would separate the reporter packages?
I really want to help and allow this plugin to work for most of the bundle related analyze use cases. To make that a reality, I would need to be able to improve the current test coverage and to make adding tests less painful than they currently are.

Sorry @valscion, I'm currently have very tough deadline on work so don't have time to look at it, but will do it as soon as I can!
Thanks!

I've got it working in our app!! :tada: :tada:
diff --git a/config/webpack/webpack.performance.config.js b/config/webpack/webpack.performance.config.js
index cffcb61c5..4cd02bfa9 100644
--- a/config/webpack/webpack.performance.config.js
+++ b/config/webpack/webpack.performance.config.js
@@ -5,7 +5,7 @@ const config = generateConfig({
   optimizeBundle: true
 });

-const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;
+const BundleAnalyzerPlugin = require('webpack-bundle-analyzer-valscion-tmp').BundleAnalyzerPlugin;

 config.bail = true;

@@ -35,7 +35,8 @@ config.plugins = [
     // option. See more here: https://github.com/webpack/webpack/blob/webpack-1/lib/Stats.js#L21
     statsOptions: null,
     // Log level. Can be 'info', 'warn', 'error' or 'silent'.
-    logLevel: 'info'
+    logLevel: 'info',
+    reporter: require('webpack-bundle-analyzer-reporter-treemap')
   })
 ];

diff --git a/package.json b/package.json
index 284ceee4a..a0637753f 100644
--- a/package.json
+++ b/package.json
@@ -175,1 +175,2 @@
-    "webpack-bundle-analyzer": "2.1.0",
+    "webpack-bundle-analyzer-reporter-treemap": "1.0.0-alpha.1",
+    "webpack-bundle-analyzer-valscion-tmp": "3.0.0-alpha.2",

The current code is very much a proof of concept. The code can be found splitted into these:

https://github.com/valscion/webpack-bundle-analyzer/tree/batshit-crazy — this plugin, with all reporter code removed
https://github.com/valscion/webpack-bundle-analyzer-reporter-treemap — only the treemap reporter code

One more point to that - would it be great if there will be any possibility to get the generated data programmatically - so that I can eventually monitor the bundle sizes in my own way.

Getting the generated data programmatically is one goal of this UI split to me :relaxed:. I'd love to be able to monitor bundle sizes as well.

Hey - I might contribute to it if you could point me to the right part to modify. I'll then figure out what to do there.

Thanks for the offer! I think the blocker here is me not really knowing how to progress to make this OK by @th0r, so I think it'd be best if I can figure out the split logic by myself :)
I'm still a bit unsure of how I want the API between plugin and reporter to look like. If you want to try out creating your own reporter (one that could just fetch the generated data programmatically), have a look at the split-reporter-to-new-package branch, especially the part where the BundleAnalyzerPlugin.js has changed where I use the newly split reporter package.
If you want to hack around, it would be awesome if you could create a new reporter like the treemap reporter I extracted and test out whether the split-reporter-to-new-package branch approach would work for you. All you'd need to change there would be to change this:
const reporter = require('@webpack-bundle-analyzer/reporter-treemap');

...to require your new reporter's package instead.
Your new reporter would need to expose an API similar to how @webpack-bundle-analyzer@reporter-treemap has done.
const viewer = require('./viewer');

module.exports = {
  generateReport,
  createReporter
};

function generateReport(stats, opts) {
  return viewer.generateReport(stats, opts);
}

function createReporter(initialChartData, opts) {
  const server = viewer.startServer(initialChartData, opts);
  return server.then(({ updateChartData }) => {
    return {
      updateData: newData => {
        updateChartData(newData);
      }
    };
  });
}

Basically, you'd need to implement two functions, generateReport and createReporter.
The generateReport function is called synchronously and it is only ever called once. It gets the generated chart data as its first argument, and the second argument is the options object containing information and a Logger instance you should use to log stuff to console.
// https://github.com/webpack-bundle-analyzer/reporter-treemap/blob/master/src/index.js

function generateReport(stats, opts) {
  // ...do what you want with `stats` and `opts`.
  // It doesn't matter what this function returns
}

// https://github.com/th0r/webpack-bundle-analyzer/blob/split-reporter-to-new-package/src/BundleAnalyzerPlugin.js

class BundleAnalyzerPlugin {
  //
  // ...
  //
  generateStaticReport(stats) {
    const chartData = analyzer.getChartData(this.logger, stats, this.getBundleDirFromCompiler());
    // Here we call the `generateReport` function
    reporter.generateReport(chartData, {
      openBrowser: this.opts.openAnalyzer,
      reportFilename: path.resolve(this.compiler.outputPath, this.opts.reportFilename),
      bundleDir: this.getBundleDirFromCompiler(),
      logger: this.logger,
      defaultSizes: this.opts.defaultSizes
    });
  }
  //
  // ...
  //
}

The createReporter function is called when the reporter server is started, and it returns a promise. That promise should settle with an object that has updateData function in it. That updateData function will be called by the webpack plugin when new data is generated.
// https://github.com/webpack-bundle-analyzer/reporter-treemap/blob/master/src/index.js

function createReporter(initialChartData, opts) {
  // Start the server somehow...
  const server = viewer.startServer(initialChartData, opts);
  // ...and return a Promise...
  return server.then(({ updateChartData }) => {
    // ...that settles with an object that has a function in key "updateData".
    return {
      // This function here will be called by the BundleAnalyzerPlugin instance when
      // new data is available.
      updateData: newData => {
        // You probably want to do something in here with the `newData` you received.
      }
    };
  });
}

// https://github.com/th0r/webpack-bundle-analyzer/blob/split-reporter-to-new-package/src/BundleAnalyzerPlugin.js

class BundleAnalyzerPlugin {
  //
  // ...
  //
  async startAnalyzerServer(stats) {
    const chartData = analyzer.getChartData(this.logger, stats, this.getBundleDirFromCompiler());
    if (this.server) {
      (await this.server).updateData(chartData);
    } else {
      this.server = reporter.createReporter(chartData, {
        openBrowser: this.opts.openAnalyzer,
        host: this.opts.analyzerHost,
        port: this.opts.analyzerPort,
        bundleDir: this.getBundleDirFromCompiler(),
        logger: this.logger,
        defaultSizes: this.opts.defaultSizes
      });
    }
  }
  //
  // ...
  //
}

I hope that the code excerpts highlight what the second options argument contains. I'm happy to shed more light to this if something is confusing.

Oh, and it would be very valuable if you could test this out and give feedback on what it felt like to do this and what pain points you encountered along the way.

Thanks for the notes, really valuable. I think I'll probably wait for the API to be completed/merged and released, and eventually start working on it!

authors: XVincentX th0r valscion


text:
Clarifying ACL table

Fixed a bug that Shawn pointed out in the ACL table and explained why we have both _local/:id and local/thali:id

This change is

PR is added to the queue for testing as 2. task. (84ac8ae)

Test (Success) 62167425 build is completed (84ac8ae)
See https://github.com/ThaliTester/TestResults/tree/6216742584ac8ae_Clarifying_ACL_table_yaronyg/ for the logs

Test 6216742584ac8ae(84ac8ae) has failed
See https://github.com/ThaliTester/TestResults/tree/6216742584ac8ae_Clarifying_ACL_table_yaronyg/ for the fail logs

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

authors: ThaliTester cicorias yaronyg


text:
The meanning of the lastest float number in the scene00xx_0x.txt within the pred_instance file

Thanks for your amazing work!
Can you explain the meanning of the lastest float number in, for example, the scene0011_01.txt within the pred_instance file?
"predicted_masks/scene0011_01_000.txt 3 0.4161"

It is the confidencescore.
predicted_masks/scene0011_01_000.txt -> path to mask pred
3 -> Predicted label
0.4161 -> confidence score

thanks for your reply.There is a new question,Does softGroup have NMS before output instance_pred.

repo: thangvubk/SoftGroup


text:
Watchdog caught collective operation timeout: WorkNCCL(OpType=ALLREDUCE, Timeout(ms)=1800000) ran for 1809861 milliseconds before timing out

This error happens when in the validation step. Have you met this problem?

My environment is cuda11.3,  python3.7, pytorch 1.10

Same with you. Have you solved it?

Is this problem on custom dataset?

authors: c6376315qqso thangvubk weiguangzhao


text:
Launching an intent from the webpage

Offer the possibility to run an intent / launch a package using a JS function catched by the kiosk.
Fully Kiosk browser does that. The goal is to integrate a button Netflix for example in your Home Assistant dashboard that starts the application on the tablet.
Thank you! (and good work!)

It’s possible if you add some interface to the Android WebView.  If you have more information on how it works please add to this issue.

Well if I had to do it I would implement it this way; http://rapidprogrammer.com/android-how-to-call-native-java-methods-from-webview-javascript
The problem is how to execute it from the home assistant, with fully kiosk browser you need to activate an option in the settings of the software to authorize JS execution
Below is the code I use with FKB in HA:
entities:

icon: 'mdi:web'
name: Netflix
type: weblink
url: 'javascript:fully.startApplication(''com.netflix.mediaclient'')'
type: entities

That is a JavaScript interface, so you would add one to the WebView custom for WallPanel.

Looks like this feature was added in latest beta release. It does not appear to function though. Receiving "Unknown URL Scheme".
Testing with
"{"url": intent:#Intent;launchFlags=0x10000000;component=com.amazon.avod/com.amazon.avod.client.activity.HomeScreenActivity"}
Receiving an "Unknown URL Scheme Error". Is this an error on my part? Same command works on FKB.

@neuroverflow helped implement this feature, maybe he can help out testing the issue.  I am using this code:
 override fun shouldOverrideUrlLoading(view: WebView, url: String): Boolean {
                // open intent urls with native application
                isRedirect = true
                if (url.startsWith("intent:")) {
                    val separated = url.split(";").toTypedArray()
                    separated[0] // this will contain "intent:#Intent"
                    separated[1] // this will contain "launch flag"
                    separated[2] // this will contain "component"
                    separated[3] // this will contain "end"
                    val component = separated[2].removePrefix("component=")
                    val classname = component.split("/").toTypedArray()
                    val pkgName = classname[0] // this will set the packageName:
                    val clsName = classname[1] // this will set the className:
                    val intent = Intent()
                    intent.action = Intent.ACTION_VIEW
                    intent.setClassName(pkgName, clsName)
                    startActivity(intent)
                    return true
                } else {
                    view.loadUrl(url)
                    return true
                }
            }

I will make this a separate method and create some tests to make sure we are parsing the URL correctly.

Seems to me you want your url formatted like this:
"intent:#Intent;launchFlags=0x10000000;component=com.amazon.avod/.client.activity.HomeScreenActivity;end"

Seems to me you want your url formatted like this:
"intent:#Intent;launchFlags=0x10000000;component=com.amazon.avod/.client.activity.HomeScreenActivity;end"

I may be doing something incorrectly. Can you verify that my payload is correct, please?
{"url": "intent:#Intent;launchFlags=0x10000000;component=com.amazon.avod/.client.activity.HomeScreenActivity;end"}
I am receiving the following error. "net::ERR_UNKOWN_URL_SCHEME".
Testing with an external webpage does work {"url": "https://google.com"}

I'm also trying to use this feature. No luck so far with publishing a url via mqtt, I'm getting same ERR_UNKNOWN_URL_SCHEME error.
Is it possible that it doesn't work because shouldOverrideUrlLoading (WebView view, String url) was deprecated?
https://developer.android.com/reference/android/webkit/WebViewClient#shouldOverrideUrlLoading(android.webkit.WebView, java.lang.String)

I am still testing, this feature is still under development.  I will post a new app update when I get everything working properly.  Thanks.

Test version URL https://github.com/thanksmister/wallpanel-android/releases/tag/v0.9.4.3

@TheAlphaLaw I've set up this app that auto opens WallPanel every 1h, hopefully it'll work fine enough for me
https://play.google.com/store/apps/details?id=com.argonremote.openappscheduler&hl=en_US&gl=US

authors: TheAlphaLaw neuroverflow pawelnguyen thanksmister

repo: thanksmister/wallpanel-android


text:
When step is a multiple of 1 day, each point will offset multiple hours

Is your proposal related to a problem?
Hi
The problem is about Thanos-frontend.
When create a range query and step set 1day , frontend wil Active alignment response earch ponit at UTC 00:00.
But in other timezoon area，we hope alignment to local timezoon.
For example：In Asia/shanghai , when setp set 1d, we get point always alignment in every day 08:00.  because shanghai time between UTC has 8 hours.
Describe the solution you'd like
In my opinion, If step is a multiple of 1 day, then active offset start and end.
step_align.go line 22
func (s stepAlign) Do(ctx context.Context, r Request) (Response, error) {
	start := (r.GetStart() / r.GetStep()) * r.GetStep()
	end := (r.GetEnd() / r.GetStep()) * r.GetStep()

	// my new code is used as a local test
	// If you aggregate by day, you need to consider the time zone. Offset once by time zone.
	if r.GetStep()%day.Milliseconds() == 0 {
		start -= shanghai_offset_ms.Milliseconds()
		end -= shanghai_offset_ms.Milliseconds()
	}

	return s.next.Do(ctx, r.WithStartEnd(start, end))
}

Can add the time zone parameters as the startup configuration to the thanos-frontend.
Hope to get your opinion, If you agree with my advice, I will implement the code and create a pull request.

@ChaoHsupin you mean you are using the Thanos Query Frontend UI? Or the Query UI? If any of these, I think we should pick the timezone from the user's browser by default but also let them switch to others manually if they desire (like in Grafana). What do you think?

Hi,
I am interested in implementing this if you do not mind @douglascamata 😊
Would you please assign it to me?

@ritaCanavarro sure thing, go ahead. 💪

@ChaoHsupin you mean you are using the Thanos Query Frontend UI? Or the Query UI? If any of these, I think we should pick the timezone from the user's browser by default but also let them switch to others manually if they desire (like in Grafana). What do you think?

@douglascamata Thanks for your reply！We use frontend by  http API. I think it's a good idea to implement an optional time zone on the UI, which means we can call the API by passing in the time zone parameter.

Hi, I am interested in implementing this if you do not mind @douglascamata 😊 Would you please assign it to me?

@ritaCanavarro Thank you for your enthusiasm. If you need help, I'm happy to help!

Thanks @douglascamata!
@ChaoHsupin I will ping you here when I start so we can brainstorm 💪🏻

@douglascamata Thanks for your reply！We use frontend by http API. I think it's a good idea to implement an optional time zone on the UI, which means we can call the API by passing in the time zone parameter.

So we could have this additional and optional timezone parameter (just one idea, feel free to do anything you think will be good, @ritaCanavarro), but only other Thanos components (like the Query Frontend UI) would be aware of it (at least for now).
This means that if you use Grafana, it won't change anything there because Grafana only cares about what belongs to the Prometheus Query API. In this case you might have to disable step alignment in Thanos Query Frontend and/or change the step size used in the query in Grafana (this is done under the hood in HTTP calls that are part of the Query API).

@douglascamata Thanks for your reply！We use frontend by http API. I think it's a good idea to implement an optional time zone on the UI, which means we can call the API by passing in the time zone parameter.

So we could have this additional and optional timezone parameter (just one idea, feel free to do anything you think will be good, @ritaCanavarro), but only other Thanos components (like the Query Frontend UI) would be aware of it (at least for now).
This means that if you use Grafana, it won't change anything there because Grafana only cares about what belongs to the Prometheus Query API. In this case you might have to disable step alignment in Thanos Query Frontend and/or change the step size used in the query in Grafana (this is done under the hood in HTTP calls that are part of the Query API).

Thanks for your reminder, We fully implement a data query component  in inner（no used grafana），the component will invoke frontend API, So adding parameters in frontend API can solve this kind problems. For Grafana users, I think we can join the timezone in the Frostend startup parameter as an optional configuration to avoid  incompatible prometheus api protocol.

What difference does the time zone make for the step alignment? :thinking:

@GiedriusS as @ChaoHsupin reports, step alignment tends towards 00:00 UTC on 1d steps, but they are in a timezone far from UTC and would prefer it to align to 00:00 in their timezone.

@douglascamata thanks for the input I will consider it ;)
@ChaoHsupin how about we check how cortex/mimir also takes care of this issue like @GiedriusS mentioned?

Hi @ritaCanavarro, are you still working on this? If not, I would like to work on it and I would love to know your insights about this.   Thanks

Hi @Pradeep-Kurapati, feel free to take this issue and send me a msg on slack to discuss some insights 😄

authors: ChaoHsupin GiedriusS Pradeep-Kurapati douglascamata ritaCanavarro

repo: thanos-io/thanos


text:
pkg/server/grpc: Fix Unregister gRPC prometheus middleware metrics

This PR fixes unregistered gRPC metrics issues that accidentally introduced with https://github.com/thanos-io/thanos/pull/2228.
Signed-off-by: Kemal Akkoyun kakkoyun@gmail.com
cc @bwplotka

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Register metrics.

Verification

MINIO_ENABLED=1 ./scripts/quickstart.sh
Check local prometheus

Test failure is unrelated.


text:
Changelog - update the changelog entry position

Addressing the comment on my previous PR, and fixing the position of the changelog entry

https://github.com/thanos-io/thanos/pull/7335#pullrequestreview-2097086713

Thanks for the fix.

authors: eqfarhad fpetkovski


text:
Texture format swizzling

Fixes https://github.com/thatcosmonaut/SDL/issues/56.
Replaces:

R5G6B5 -> B5G6R5
A1R5G5B5 -> B5G5R5A1
A2R10G10B10 -> R10G10B10A2

and removes A2B10G10R10 entirely.
The reason for the last change is because I was incorrect in my initial write-up, D3D11/12 have no support for B10G10R10A2. So we'd have to swizzle R10G10B10A2 on the D3D side, which is not ideal. To keep as much swizzling logic as possible in Vulkan, I think we should exclusively offer RGBA order.
However, Vulkan's native surface support for A2R10G10B10 is ~12%. So instead we'll always use A2B10R10G10 (which has a ~62% surface support rate) and then swizzle it into RGBA order.
One remaining issue is with Metal's ABGR4 format. It doesn't support BGRA4 or any other swizzle natively, and D3D/VK don't support A4B4G4R4 natively. I'll need to set up a Metal swizzle for this format specifically.

One remaining issue is with Metal's ABGR4 format. It doesn't support BGRA4 or any other swizzle natively, and D3D/VK don't support A4B4G4R4 natively. I'll need to set up a Metal swizzle for this format specifically.

Marked this one as ready for now since I believe this is just a quick MTLTextureSwizzle, but if it's a major blocker that can be reverted (otherwise I'll apply this to the weekly update).

authors: TheSpydog flibitijibibo

repo: thatcosmonaut/SDL

license: Zlib


text:
how to edit dimmer?

Laravel Version: latest
Voyager Version: 1.0
PHP Version:7.1
Database Driver & Version:

Description:
Can we change dimmer on the dashboard? I have a table "Games" and I want to show it in the dashboard like the 'Posts' and 'Users' tables.

Yes you can , there is DimmerClass in voyager you can make your own dimmer class like this
https://github.com/the-control-group/voyager/blob/master/src/Widgets/PageDimmer.php
after edit config/voyager.php widgets section
'widgets' =>
 [
   'TCG\\Voyager\\Widgets\\UserDimmer',
   'TCG\\Voyager\\Widgets\\PostDimmer',
    App\Widgets\MyCustomDimmer::class,
],

thank you for the reply but I can't access your link, error 404.

thank you for reply, I made the changement and I got this error:
Class "TCG\Voyager\Widgets\GameDimmer" must extend "Arrilot\Widgets\AbstractWidget"
`<?php
namespace App\Widgets;
use Arrilot\Widgets\AbstractWidget;
use Illuminate\Support\Str;
use TCG\Voyager\Facades\Voyager;
class GameDimmer extends AbstractWidget
{
/**
* The configuration array.
*
* @var array
*/
protected $config = [];
/**
 * Treat this method as a controller action.
 * Return view() or other content to display.
 */
public function run()
{
    $count = Voyager::model('Page')->count();
    $string = trans_choice('voyager.dimmer.page', $count);

    return view('voyager::dimmer', array_merge($this->config, [
        'icon'   => 'voyager-file-text',
        'title'  => "{$count} {$string}",
        'text'   => __('voyager.dimmer.page_text', ['count' => $count, 'string' => Str::lower($string)]),
        'button' => [
            'text' => __('voyager.dimmer.page_link_text'),
            'link' => route('voyager.pages.index'),
        ],
        'image' => voyager_asset('images/widget-backgrounds/03.jpg'),
    ]));
}

}
`

found solution there:
http://karac.ch/blog/voyager-le-panneau-d-administration-laravel_partie3_pour-aller-plus-loin#widgets

Solution found. Closing

repo: the-control-group/voyager


text:
How to get the form fields to show them in the custumisez edit page ?

Description
I need a working way to get an array (or any other way) containing the form fields (which i already added them with the bread ) of my "reservations" content type cause I will need to do a lot of modification on the edit page of the "reservations " edit page

Please use the issue-template and follow the instructions in it (...questions are better asked in our Slack group)
Also this is basic Laravel/Eloquent knowledge and can be found in our views.


text:
Roles update

Hey Voyagers!
Like some of you, I needed a user role without the permission for breaking the system, (not able to manage Roles, Menu Builder, Database and Settings).
This PR will sort out this issue, and fixes a few more things.
1. New Role
Was created a Role named "root" that holds full permissions, while the role "admin" have restricted access. A user account "root" was also added, we can test login with: "root@admin.com" and "admin@admin.com". If you don't like the names, we could use "admin" for full rights, and have another role, like "manager" for the normal access...
2. Role Assigned on BREAD
In table data_types was added a field named "role", that is used at the Middleware Validation.
For changing a role, goto Database / Edit BREAD, scroll down and you'll find a role input.
3. Role Validation
Validation is using the existing VoyagerAdminMiddleware, was added an extra parameter (role) used for the verification. The role defined in BREAD, will be used for controlling this access.
4. User Role Manager
Added a view for Users, with available roles inputs, however this isn't saving yet, we need to handle relationships. Until we don't find a way for managing User Roles, maybe we can delete this file?

I'd prefer to manage access through permissions, instead of directly checking for hard-coded role names. Permissions can be given to roles, and Users can be given a role.  #245 allows for the creation and management of these permissions.

@fletch3555, this update adds some fixes, but we still need to be able to save Users Roles:

Roles are hard-coded in routes web.php only, if you look at Middleware it was removed and it's now being processed dynamically, for a given role parameter.
When you manage the BREAD, you can define the role:

I personally don't see the point of having a killer RBAC system like #245 is developing, but I understand we all have different needs.

The permission system in v0.10 supports this.

Thank's, I was about to close this.
It would be more interesting to develop on top of the BREAD, instead of coding new sections.

To others looking at how to manage full control, I normally see this role referred to as a SuperAdmin. So in my Voyager dashboard I did just that, created a role called SuperAdmin and in Roles it is a pretty simple setup. Just check "Select All" at the top and you have full permissions on every table. So I agree with Fletch and Mark.

Hi @JCanchor, this was long ago, but it's true you have a solution to manage it.
The only down side, if you need to handle a huge list of permissions, then you will be willing for a multi-roles system.
Anyway, when the time came, we will have multi-roles :)

authors: JCanchor akaZorg akazorg fletch3555 marktopper


text:
Illegal string offset 'locale'

Create a collection from $this->settings

That's effectively what the cast just a few lines above does.

You're probably getting that error because the User model in your app overwrites the casts attribute. Just add an array cast for the settings attribute in your app/User.php.
    /**
     * The attributes that should be cast to native types.
     *
     * @var array
     */
    protected $casts = [
        'email_verified_at' => 'datetime',
        'settings' => 'array',
    ];

The real solution would be for the installer to check if the User model has a casts property defined, and add this automatically.

Superseeded by #3909 commit https://github.com/the-control-group/voyager/pull/3909/commits/56e72e668a7c124f69172dbac1f12ba3bdad7272.

authors: CupOfTea696 emptynick workschan


text:
Created Jira guide

NOTE:

Please fill out the template below

Did you read the instructions in the README?

Y

Have you read the instructions in CONTRIBUTING?

Y

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?

Written in own words, information gathered from the Jira website which is linked to within the article for further information.

In response to issue #197

Merging it :+1:

authors: codemzy the-ethan-hunt

repo: the-ethan-hunt/first-timers-guide


text:
where is yae miko?

This is the list of character names
[
  'Aether',    'Albedo',         'Aloy',
  'Amber',     'Arataki Itto',   'Barbara',
  'Beidou',    'Bennett',        'Chongyun',
  'Diluc',     'Diona',          'Eula',
  'Fischl',    'Ganyu',          'Gorou',
  'Hu Tao',    'Jean',           'Kaedehara Kazuha',
  'Kaeya',     'Kamisato Ayaka', 'Keqing',
  'Klee',      'Kujou Sara',     'Lisa',
  'Lumine',    'Mona',           'Ningguang',
  'Noelle',    'Qiqi',           'Raiden Shogun',
  'Razor',     'Rosaria',        'Sangonomiya Kokomi',
  'Sayu',      'Shenhe',         'Sucrose',
  'Tartaglia', 'Thoma',          'Venti',
  'Xiangling', 'Xiao',           'Xingqiu',
  'Xinyan',    'Yanfei',         'Yoimiya',
  'Yun Jin',   'Zhongli'
]

where is yae miko? shes on the wiki https://genshin-impact.fandom.com/wiki/Yae_Miko

yae miko has not yet been released in the game yet. therefore I do not have data for her.
I will add data for her next week.
Sorry for any inconvenience

@theBowja don't worry take your time, as long as you add it before valentines day

going to be added on valentines day

authors: oniiichannnn theBowja

repo: theBowja/genshin-db


text:
Improve Social API

Users need to be able to customize/add social service with icons. We'll cater for some built in and direct users how to add new ones.
The new UX will handle better ordering, more customization, easy addition of future customization.
We'll make this retrocompatible.
UX
Old UX:
# config/_default/params.yaml
description: Something lorem ipsum
twitter: https://twitter.com/GoHugoIO
github: https://github.com/GoHugoIO

New UX:
# config/_default/params.yaml
ananke_socials:
- name: twitter
   url: https://twitter.com/GoHugoIO
   color: #1da1f2
- name: github
   url: https://github.com/GoHugoIO
   color: #6cc644

Adding user's own icon
User will be directed to add an svg file matching the service's name at /assets/ananke/icons/
Ex: If user wants to add twitch:
ananke_socials:
- name: twitch
   url: https://twitch.com/GoHugoIO

User will drop its svg as /assets/ananke/icons/twitch.svg
Adding built in icons/service
This will also improve the way contributor can submit new built in services by complementing a single source file for service name and color and add one (consistent formating) svg.
This should take care or help contributors handling #420 #419 #418 and more...

I guess we need the ananke_...?

authors: budparr regisphilibert

repo: theNewDynamic/gohugo-theme-ananke


text:
[BUGFIX] Awaiting of non-generic task does not hang forever/cause invocation exception.

Awaiting of ordinary non-generic Task always causes invocation exception or hangs if invocation timeout is 0.
Little fix for such a trouble.

Thank you for correcting this bug.

repo: theRainbird/CoreRemoting


text:
New global option nox.options.venv_backend to set the default backend

As you've understood from my recent activity on this repo, I am a conda user ;)
I like my noxfile.py but it could be much lighter if I did not have to write venv_backend="conda" everywhere.
Therefore I propose to define a new global option nox.options.venv_backend (or whatever alternate name you'll prefer of course)

Actually default_venv_backend will probably be more explicit.

repo: theacodes/nox


text:
Use 'pytest' instead of 'py.test' in examples and configuration

'pytest' is the recommended command since version 3.0.
The command was called 'py.test' only for historical reasons:
https://docs.pytest.org/en/latest/faq.html#why-can-i-use-both-pytest-and-py-test-commands
Gratz on the project! 👍

Nice. :) Thank you @nicoddemus

I think we'd gotten most of these that were user-facing previously, but always good to get the rest taken care of. :)

authors: nicoddemus theacodes


text:
issues with event tracking integration for ios14.5+

🐛 Help with integration
Hello, I want to use your package for tracking Facebook event for IOS14.5 +
I did everything according to the instructions but the events are not displayed
I create a project on react-native , versions of my packages
  "react-native-fbsdk-next": "^8.0.0",

FBSDKCoreKit (13.1.0):

FBAEMKit (= 13.1.0)
FBSDKCoreKit_Basics (= 13.1.0)
FBSDKCoreKit_Basics (13.1.0)
FBSDKGamingServicesKit (13.1.0):

FBSDKCoreKit (= 13.1.0)
FBSDKCoreKit_Basics (= 13.1.0)
FBSDKShareKit (= 13.1.0)

FBSDKLoginKit (13.1.0):

FBSDKCoreKit (= 13.1.0)

FBSDKShareKit (13.1.0):

FBSDKCoreKit (= 13.1.0)

To Reproduce
taken from example
#import <FBAEMKit/FBAEMKit.h>
// apply codes below to application:openURL:options:
// in AppDelegate.m or SceneDelegate.m
[FBAEMReporter configureWithNetworker:nil appID:{app-id}];
[FBAEMReporter enable];
[FBAEMReporter handleURL:url];
my AppDelegate.m

in what format should i set the app id ? putting @ at the beginning is the only option where xCode doesn't give me an error
Expected Behavior
I understand that I have to parse permission from the user and send it to your package

it works and i can see device share on ios14.5+
in order to see events from ios14.5+, do I have to make additional settings for the necessary events in this section?

this is how i track events

I have the same issue. I tried to fallback to version 7.3.3 but this problem still occurs there.

I found a problem, you need to separately configure events in facebook event manager and select the necessary events for SKAdNetwork and then select an event for ios 14.5 in the tab below

authors: RRaideRR YaroslavReact

repo: thebergamo/react-native-fbsdk-next


text:
Mac에서 실행 시 자바 런타임을 찾을 수 없는 문제

맥(Sierra 10.12.1)을 사용하고 있는데, 다음과 같은 코드를 실행하면
from textrankr import TextRank

다음과 같은 오류 메세지가 나옵니다.
No Java runtime present, requesting install.

KoNLPy에서 제가 보고했던 문제와 마찬가지로 Java 1.8의 버그인 것으로 추정됩니다. 다음과 같이 JAVA_HOME 환경 변수를 설정하면 문제 없이 동작합니다.
export JAVA_HOME=$(/usr/libexec/java_home)

참고로 저의 시스템에는 Java 1.8.0-66이 설치되어있습니다.
➜  ~ java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

konlpy를 필요한 경우에만 쓰도록 바꿨습니다 (0.7)

authors: suminb theeluwin

repo: theeluwin/textrankr


text:
Testing Plot2Dynmap on the Creative server. Adding if works.

As a(n) TFB Developer
I want to improve the server experience on our Creative server
So that people can have more fun and enjoy their stay
Detailed description:
I want to test and see if we can add Plot2Dynmap on the Creative server.
It has a lot of interactable features for the plots.
It's outdated, but I can't see a reason why it wouldn't work regardless.

Used this for the setup.
Everything works perfectly on localhost:8123.
In order to merge it onto the live server we have to find some way to use a public IP.
What should it look like, and how do we get it working?
And is there any way for players to be able to click on a plot and it will execute the /p visit [Player] command.
The map is already aware of the users info, maybe that could be useful somehow.

repo: theflyingbirdsmc/TFB-Network


text:
Update CircleCI to not use Ghost anymore and get new database

Part of #301 epic

Done in #327

repo: thegazelle-ad/gazelle-server


text:
Add workflows and parallelism to our CircleCI config

As described above, this is also first step towards adding our first end to end tests into CircleCI :)

I'm just using my admin privileges for this as there's not much to review and I'm the only one that's worked with CircleCI config anyway.


text:
Move 'var obj' in seek.js and other places

Also repair 'fix' command

Merged into master, closing

repo: thegrumpys/pcyl-cli


text:
Not compatible with latest Python 3.10+

Report
Is it possible to install with version compatible with latest python? Otherwise it's hard to work with updated pacakges like scvi-tools that require python >3.10.
> pip install pertpy
ERROR: Ignored the following versions that require a different python version: 0.1.0 Requires-Python >=3.8.0,<3.10; 0.2.0 Requires-Python >=3.8.0,<3.10; 0.3.0 Requires-Python >=3.8.0,<3.10
ERROR: Could not find a version that satisfies the requirement pertpy (from versions: none)
ERROR: No matching distribution found for pertpy

Version information
No response

We've already addressed this and you will be able to install it with Python 3.10 with the next release! In the meantime you can install pertpy from the development branch.
pip install git+https://github.com/theislab/pertpy.git@development

should do the trick if I recall correctly. Sorry for the inconvenience until then!

Thank you very much!

authors: Zethson nroak

repo: theislab/pertpy


text:
Which type of data anndata layers need to comprise to run scib.me.metrics_fast() depending on the integration method used?

Hi,
Thank you all the developers of scIB for the great package and also to suggest useful metrics to compare the performance of integration methods.

WARNING: You may want to skip to the end of the post to read the more concrete questions!

I've been trying to run the function scib.metrics.metrics_fast() (from scIB) for awhile but I've been facing some problems to understand which type of data layers the anndata objects need to hold depending on the method and parameters used during integration.
I should say that I'm mostly an R user and I'm interested in comparing the performance of Seurat and Scanorama across multiple data sets. I would like to run these methods following the parameters used in the paper Benchmarking atlas-level data integration in single-cell genomics - Fig.3b:

Seurat v3 RPCA: RPCA + HVG + scaling (full gene exp. matrix)

Scanorama: HVG + scaling (embedding)

Although I know a bit of python, I often prefer to avoid working with it since I find usually myself making simple mistakes which is quite frustrating. Additionally, I'm less familiar with general python packages (numpy, pandas, etc) as well as with the more specific scRNA-seq package scanpy which turns the code less readable for me. For all these reasons I thought to run Seurat and Scanorama (with reticulate) in R and use the final result to compare the performance with scIB in order to have the flexibility to change parameters in R for the integration tasks but minimize potential errors when using python.  I should also say that the reason why I'm not using the snakemake workflow scib-pipeline is because I've my own workflow and I don't know how much hard would be try to adapt it to run the integration methods as implemented in scib-pipeline
In order to try to reproduce Seurat v3 RPCA method and parameters, I tried the following (please see a minimal reproducible example below). Briefly, the data set was split by the batch variable, 2K HVG found and the data scaled. If I understood correctly there isn't a wrapper function for the method Seurat in the package scIB, since Seurat is implemented in R. After reading the code from the repository scib-pipeline, I understood that the conversion between anndata and Seurat objects is made with as.SingleCellExperiment() and as.Seurat() functions. My understanding is that the @data slot from the Seurat object will hold the scaled counts and these are for all the genes contrary to the integration python methods, where the HVG are found first, the table of normalized counts subsetted for HVG and, only then, it is performed scaling. On the other hand, in Seurat the scaled counts in the @data will be scaled again for the HVG exported as an RDS format. Is my interpretation correct?
## Packages
library("dplyr")
library("Matrix")
library("Seurat")
library("SeuratData")
library("SeuratDisk")

# Import data
if ( ! ( "panc8" %in% (InstalledData() %>% pull(Dataset)) ) ) InstallData("panc8")
panc8 <- LoadData("panc8")

# Set seed
set.seed(1024)

## Pre-process data
# Normalize
panc8 <- NormalizeData(panc8, normalization.method="LogNormalize", scale.factor=10000) # Normalization

# Save the original unintegrated object
panc8 <- UpdateSeuratObject(panc8)
SaveH5Seurat(panc8, "data/unint.h5Seurat")
Convert("data/unint.h5Seurat", dest="h5ad") # anndata.X : @data w/ 34363 genes x 14890 cells

## Split data by batch, find 2K HVG, scale & merge Seurat obj
# Split by batch
seu_ls <- SplitObject(panc8, split.by="tech")

# Find 2K HVG
seu_ls <- lapply(seu_ls, function(x) {
   		 x <- NormalizeData(x)
   		 x <- FindVariableFeatures(x, selection.method="vst",nfeatures=2000)
})
features <- SelectIntegrationFeatures(object.list = seu_ls)
saveRDS(features, "data/hvg_2k.rds")

# Scale
for (s in seq_along(seu_ls)) if (length(seu_ls[[s]]@assays$RNA@var.features)>0) seu_ls[[s]]@assays$RNA@var.features <- logical(0)
seu_ls <- lapply(seu_ls, function(x) {
   		 x <- ScaleData(x)
})
# Substitute 'data' by 'scaled.data' & merge Seurat objs
for (s in seq_along(seu_ls)) seu_ls[[s]]@assays$RNA@data <- as(seu_ls[[s]]@assays$RNA@scale.data, "sparseMatrix")
seu <- merge(seu_ls[[1]], unlist(seu_ls[2:length(seu_ls)]), add.cell.ids = names(seu_ls))

## Integration
seu_ls <- SplitObject(seu, split.by="tech")
seu_ls <- lapply(X = seu_ls, FUN = function(x) {
   		 x <- ScaleData(x, features = features, verbose = FALSE)
   		 x <- RunPCA(x, features = features, verbose = FALSE)
})
anchors <- FindIntegrationAnchors(object.list = seu_ls,
   			  anchor.features = features,
   			  reduction = "rpca")
int <- IntegrateData(anchorset=anchors)
DefaultAssay(int) <- "integrated"
int <- ScaleData(int)
int <- RunPCA(int)
int <- FindNeighbors(int, reduction="pca", dims=1:30) # run neighbour graph
int@assays$integrated@scale.data <- matrix(ncol=0,nrow=0) # fill with nothing
SaveH5Seurat(int, "data/seurat_int.h5Seurat")
Convert("data/seurat_int.h5Seurat", dest="h5ad") # anndata.X: norm corrected data w/ 2000 genes x 14890 cells

In the case of Scanorama seems simpler since from the code it seems that what it is provided (considering the preference for the parameters mentioned above) as input is a table of scaled counts for the HVG by batch (see short example below). Is my interpretation correct?
# Packages
library("dplyr")
library("Seurat")
library("SeuratDisk")
library("reticulate")
source("helper_functions.R")
scanorama <- import("scanorama")

# Set seed
set.seed(1024)

# Load scaled obj & HVG genes
panc8 <- LoadH5Seurat("data/scaled.h5Seurat")
features <- readRDS("data/hvg_2k.rds")

# Subset object to HVG
meta_data <- panc8@meta.data
counts <- GetAssayData(panc8, slot="counts", assay="RNA")
seu <- CreateSeuratObject(counts=counts[features,],
			  meta.data=meta_data)

# Split data by batch
seu_ls <- SplitObject(seu, split.by="tech")

# Normalize and scale by batch
seu_ls <- lapply(seu_ls, function(x) {
			 x <- NormalizeData(x)
			 x <- ScaleData(x, features=row.names(x))
			  })

## Parse data for Scanorama
mtx <- lapply(seu_ls, function(x) t(as.matrix(x@assays$RNA@scale.data)))
genes <- lapply(mtx, function(x) colnames(x))
cells <- lapply(mtx, function(x) row.names(x))
cells <- unlist(cells)
names(mtx) <- names(genes)  <- NULL

# Integration & batch-correction
int_ls <- scanorama$correct(mtx, genes,
			    return_dimred=TRUE,
			    return_dense=TRUE)

## Parse results
# Join dimensional reductions
int_dr <- do.call(rbind,int_ls[[1]])
colnames(int_dr) <- paste0("PC_", 1:100)
row.names(int_dr) <- cells

# Join integrated counts
int_t <- lapply(int_ls[[2]],t)
int_counts <- do.call(cbind,int_t)
row.names(int_counts) <- as.character(int_ls[[3]])
colnames(int_counts) <- cells

# Create Seurat object, merge scaled.data from list &
#save @scale.data in @data in integrated obj
int <- CreateSeuratObject(counts=int_counts,
			  assay="integrated")
			  #project="batch")
int@assays$integrated@data <- t(do.call("rbind",mtx))
if (!is.null(seu_ls)) { # add metadata
	meta_ls <- lapply(seu_ls, function(x) x@meta.data)
	meta_all <- merge_metadata(meta_ls)
	int@meta.data <- meta_all
	row.names(int@meta.data) <- colnames(int)
}

# Add dimensional reduction
std <- apply(int_dr, MARGIN=2, FUN=sd)
int@reductions$pca <- CreateDimReducObject(embeddings=int_dr,
					   stdev=std, key="PC_",
					   assay = "integrated")
row.names(int@reductions$pca@cell.embeddings) <- colnames(int)

Finally, I'm assessing the performance with scIB (see below). Here, it seems that I need to fix the category variables type and compute KNN graph with scanpy because SeuratDisk seems unable to save connectivities of this graph to the right place anndata.obsp["connectivities"] (perhaps due to incompatibility between versions). Here, my understanding is the following:

unintegrated anndata object: it needs to comprise normalized counts in the adata.X layer and it needs to contains cell labels (dependending on the metrics that I want to assess).

integrated anndata object (if type_="full"): it needs to comprise corrected scaled counts after integration, in the case of Seurat at least, in the adata.X layer (there will be as much genes as specified in the HVG parameter).

integrated anndata object (if type_="embed"): it needs to comprise scaled counts in the adata.X layer (there will be as much genes as specified in the HVG parameter) and embedding in adata_int.obsm["X_pca"] or adata_int.obsm["X_emb"] (because line).

# Import modules
import scib
import scanpy as sc

# Import anndatas files
unint=sc.read("data/unint.h5ad")
seurat_int=sc.read("data/seurat_int.h5ad")
scanorama_int=sc.read("data/scanorama_int.h5ad")

# Turn 'object' variables 'batch_key' & 'label_key' into 'category' variables
key_vars=["tech","celltype"]
for v in key_vars:
	unint.obs[v]=unint.obs[v].astype("category")
	seurat_int.obs[v]=seurat_int.obs[v].astype("category")
    scanorama_int.obs[v]=scanorama_int.obs[v].astype("category")

# Compute PCA & neighbor graph
scib.pp.reduce_data(seurat_int, n_top_genes=2000, neighbors=True, use_rep="X_pca", pca=True, umap=False)
scib.pp.reduce_data(scanorama_int, n_top_genes=2000, neighbors=True, use_rep="X_pca", pca=True, umap=False)

# Run fast metrics
seurat_res=scib.me.metrics_fast(adata=unint, adata_int=seurat_int, batch_key="tech", label_key="celltype", organism="human", type_="full")
scanorama_res=scib.me.metrics_fast(adata=unint, adata_int=scanorama_int, batch_key="tech", label_key="celltype", organism="human", type_="embed") #it does not fail because of: adata_int.obsm["X_emb"] = adata_int.obsm["X_pca"].copy() (https://github.com/theislab/scib-pipeline/blob/75ae100cf158191ee9097750e658b2f822cc837b/scripts/metrics/metrics.py#L142)

Just to summarise and re-phrase the questions above (which migh be simpler):

Which is the exact input for Seurat and Scanorama if I'm interested in using the top performance parameters obtained in the paper? (which were for the methods: Seurat v3 RPCA (RPCA + HVG + scaling - full gene exp. matrix); Scanorama (HVG + scaling - embedding))

Which type of information the unintegrated and integrated anndata objects need to provide to the function scib.me.metrics_fast() depending if I use type equal full or embed?

Sorry for the long post.
Thank you in advance for the great package and any feedback that you may give.
Best regards,
António

Please refer to the documentation for a user guide for the required preprocessing steps and the API documentation for the different metrics and wrappers.
Conversion with R is something that might need to be updated at some point.

authors: antonioggsousa mumichae

repo: theislab/scib


text:
Img not responsive

and it should look like directly from md

done ,not easy to find the way

repo: themefisher/dot


text:
🛑 Console is down

In 19cabdb, Console (https://api.themonetizr.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Console is back up in 205a7d1 after 8 minutes.

repo: themonetizr/upptime


text:
[FIX] Unparenthesized a ? b : c ? d : e is deprecated. Use either `…

…(a ? b : c) ? d : eora ? b : (c ? d : e)`

@themsaid

@themsaid any chance to merge this PR :smiley: ?

repo: themsaid/laravel-langman


text:
Created Validator endpoints

Continuing from a previous PR (https://github.com/thenewboston-developers/dotnetcore-sdk/pull/32)
This time rebased on the develop branch, and the only changes are the addition of the necessary appropriate classes.

That is incredibly strange. It works on my end, and I only changed those files. Seems JSON Deserialization is having a tough time.

Make sure all tests are being run, they are failing locally as well. I'll have a look some time tomorrow, just a few brief comments after glancing at it.

The appropriate DTOs in Bank/Models/ and Validator/Models/ haven't been created. These are going to hold the API responses, not the ValidatorNode. Make sure they have the appropriate data types that the API returns. You could name them BankValidator and ValidatorResponseModel, respectively.
PatchValidatorAsync() hasn't been tested.
Keep an eye on methods names, for example in your tests you're using BuildBankTransactionMock() which is copied from another class. Also always return an interface, when there exists one, not a concrete class.
Please remove any unnecessary empty lines, for example after [Fact] in some tests, or after a method has returned.

It looks to me like IValidatorService.GetAllValidatorsAsync() should return a Task<IEnumerable> instead of Task. When you change that return type and make all necessary adjustments in all other areas, the tests will pass.

These endpoints return paginated results, so Task<ResponseModel> is needed.

Yeah. I checked the servers to make sure, and they do return paginated results. The types for a couple values were integers instead of strings in the live servers as well, but I left those alone for now to avoid confusion.

I'm a bit late, but keeping track of some things that we should change.

Sorry, I'm only now seeing this. I'll create an issue for it.

repo: thenewboston-developers/dotnetcore-sdk


text:
What is the best practice for adding 'grant_type' parameter in getAuthorizationUrl() ?

I actually did this (directly in my controller):
            // Fetch the authorization URL from the provider; this returns the
            // urlAuthorize option and generates and applies any necessary parameters
            // (e.g. state).
            $authorizationUrl = $provider->getAuthorizationUrl([
                'grant_type' => 'authorization_code',
            ]);

Is that OK or is there a better way?

That's completely fine.

Thank you very much.

authors: pounard shadowhand


text:
Fixing issue #18 Problem retrieving user detail fields from v1 API

As described in https://github.com/thephpleague/oauth2-linkedin/issues/18, fixing the URL and test cases. Tests passed successfully.

Can confirm that this works as expected and is needed.
After updating to v4.1, details like name, url and email are not returned anymore. The fix in this PR works fine 👍

authors: AndreiIgna pwweb


text:
Difference between Query::new() and Query::fromVariable([])

Bug Report
(Fill in the relevant information below to help triage your issue.)

Information
Description

Package
uri-components

Version
7.4.1

PHP version
8.3.2

OS Platform
Linux

Summary
> $q = League\Uri\Components\Query::new()
= League\Uri\Components\Query {#5499}

> $q->getUriComponent()
= ""

> $q2 = League\Uri\Components\Query::fromVariable([])
= League\Uri\Components\Query {#5528}

> $q2->getUriComponent()
= "?"

Expected result
I would expect getUriComponent() to return "" in both cases
Actual result
League\Uri\Components\Query::fromVariable([])->getUriComponent() returns "?"

Well I see where this reasoning comes from but PHP behaviour is at "fault" on this one.
Query::fromVariable output depends on http_build_query behaviour whereas Query::new does not.
<?php
var_dump(http_build_query([])); // returns ''

http_build_query never returns null (aka the absence of query), it returns the empty string instead, while Query::new() by default returns null.
Hope this clarify the output.

Along the same line:
> $u = League\Uri\Http::new('http://abc.com?a=1')
= League\Uri\Http {#5714}

> $q = League\Uri\Components\Query::fromVariable([])
= League\Uri\Components\Query {#5525}

> League\Uri\Modifier::from($u)->mergeQuery($q)->getUriString()
= "http://abc.com?a=1&"

No It should not. Doing so would break expectation. You should interchangeably use fromVariable and http_build_query. Both work with array like in your example but also with objects which is a less documented feature with has an even more "strange" behaviour.
IMHO fromVariable should be used when migrating from http_build_query to proper query usage and creation.

Gotcha, maybe I just misunderstood the purpose of that function. The upgrade docs say to replace Query::createFromParams with Query::fromParameters, but I looked and that function is also deprecated and references fromVariable:
https://github.com/thephpleague/uri-components/blob/b94fe4097885f1b51c4c3fcb78025fbbabbb5d9d/Components/Query.php#L662
Is there a replacement for createFromParams/fromParameters that maintains similar behavior?

createFromParams/createFromParameters are indeed replaced by fromVariable because of an issue in the methods design for more information check the following issue https://github.com/thephpleague/uri-src/issues/123

I appreciate the clarification :+1:
I'll just update the places I construct Querys to something like:
if ($params) {
   $q = Query::fromVariable($params);
} else {
   $q = Query::new();
}

authors: davidrans nyamsprod

repo: thephpleague/uri-src