Avoid the duplicated granting userid to vswitch

Check if the userid has already been granted for the vswitch, if yes, then do nothing. Otherwise, it will cause the existing NICs in the VM down on the vswitch.

@jichenjc @bjhuangr @zhshuj pls help review, thx

pls help review and merge, thx

mostly good
@zhshuj please help review as well especially the logic then we can merge this

mostly good
@zhshuj please help review as well especially the logic then we can merge this

I also have the same confusion about user access to vswitch when attaching interface with differnt vlan ids.
At last found it is the Virtual_Network_Adapter_Connect_Vswitch SMAPI call that connect to vswitch and also grant access to vswitch at the same time.
Before the Virtual_Network_Adapter_Connect_Vswitch call in attaching NIC operation; the ZSJA002B only access to vswitch VSICICA with VLAN ID 100.

Adapter Connections:                            Connected: 2
   Adapter Owner: ZSJA002B NIC: 1000.P00 Name: HYD1G1      Type: QDIO
     PQUplinkTX: Normal
     Porttype: Access
     RX Packets: 0          Discarded: 0          Errors: 0
     TX Packets: 28         Discarded: 0          Errors: 0
     RX Bytes: 0                    TX Bytes: 1748
     Device: 1002  Unit: 002   Role: DATA       Port: 2176
     VLAN: 0100
     Options: Ethernet Broadcast
       Unicast MAC Addresses:
         02-01-0C-07-64-D7 IP: <IP_ADDRESS>
       Multicast MAC Addresses:
         01-00-5E-00-00-01
         33-33-00-00-00-01
 Adapter Owner: ZSJA002B NIC: 1003.P00 Name: HYD1G1      Type: QDIO
   PQUplinkTX: Normal
   Porttype: Access
   RX Packets: 356        Discarded: 0          Errors: 0
   TX Packets: 0          Discarded: 0          Errors: 0
   RX Bytes: 19208                TX Bytes: 0
   Device: 1005  Unit: 002   Role: DATA       Port: 2177
   VLAN: 0726
   Options: Ethernet Broadcast
        Unicast MAC Addresses:
          02-01-0C-00-00-55
        Multicast MAC Addresses:
          01-00-5E-00-00-01
          33-33-00-00-00-01

At last found it is the Virtual_Network_Adapter_Connect_Vswitch SMAPI call that connect to vswitch and also grant access to vswitch at the same time.

To confirm, this is done by the zcc call guest_nic_couple_to_vswitch which is also from neutron zvm agent, right?
So there are 2 steps: the 1st is grant userid to the vswitch and the 2nd is couple the nic to it?

At last found it is the Virtual_Network_Adapter_Connect_Vswitch SMAPI call that connect to vswitch and also grant access to vswitch at the same time.

To confirm, this is done by the zcc call guest_nic_couple_to_vswitch which is also from neutron zvm agent, right? So there are 2 steps: the 1st is grant VM's userid to the vswitch and the 2nd is couple the nic to it?

Yes. But seems grant VM's userid  is not necessary any more. we can check later.


Unable to upload empty file

Describe the bug
If you clear all text in an existing file and you want to upload the empty file without content, nothing happens.
To Reproduce
Steps to reproduce the behavior:

Create a new file at ioBroker scripts (I created a TypeScript file)
Download the file with the extension
Add some content to the file (just some comment will be enough)
Upload the file with the extension
You will see the changes in ioBroker scripts, the file was uploaded succesfully
Clear the content of the file and uload it with the extension
Nothing happens. Content is still in the file when you check ioBroker scripts

Expected behavior
File without no content should be uploaded with no content.
Desktop:

ioBroker.javascript v0.9.1
OS: Windows 10 Pro Insider Preview 21318.1000
Browser: Chrome Version 89.0.4389.90

This bug is fixed in v0.9.2


Saving a doc with inner objects behavior

Suppose we have a javascript object with a inner object that we want to save as a doc in pouchdb . In my case it has more lines and a couple of relationships, but for simplicity :
{
  id : "doc1",
  name : "Document 1",
  props : {
    id : 1,
    prop1 :  "hello",
    prop2 : "world"
  }
}

In normal pouch, we can put this to save a doc like:

But, if when we try to save with db.rel.save, it only stores the id of object, skipping all other content:

If before call db.rel.save, I do doc.props = [doc.props]; it will be stored as an array with the entire object. It has a big side effect doing this when we retrive in client, console.log($scope.doc) prints all doc correclty (including prop as an array with one object), but doing console.log($scope.doc.props) throws undefined.
So, what's happening when saving an object inside doc? It is the normal behavior?

I found the guilty of this behavior. If the inner object has an id prop, trigger that.  So this work:
{
  id : "doc1",
  name : "Document 1",
  props : {
    prop1 :  "hello",
    prop2 : "world"
  }
}

So, when I add a object to a doc, I save that prop in a standalone prop and then delete it from object. The result is:

This sounds like a bug in relational-pouch. So you're saying if there's an id prop anywhere, then it will remove the object? Definitely a bug; that should only happen if you define a schema.


Plushstore appears to be bugged, as well as plushy drops.

Describe the bug
Stickerbook appears to not give out the plushy you are supposed to obtain, and neither will the plushstore give you the plush you are trying to buy. It does take the money from you though.
To Reproduce
Plushstore:
type /plushstore and select any gen, buy one of the plushys and you do not get the plushy but the money gets taken.
do /stickerbook and select the book you want to fill out. You get all rewards except the plushy.
Expected behavior
Plushstore - Obtain the plushy you paid for
Stickerbook - Obtain the plushy you did the stickerbook for
Username:
JamieRRE
Server name (all applicable):
All

https://github.com/NebulaMC-GG/Bugs-and-Issues/assets/101290403/7aec7bd2-4eef-453e-9e38-f7bf7fc06382
Video of trying to buy a plushy from the store and it not working

Resolved


mcl_3dl: 0.5.4-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository mcl_3dl to 0.5.4-1:

upstream repository: https://github.com/at-wat/mcl_3dl.git
release repository: https://github.com/at-wat/mcl_3dl-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.10.1
previous version for package: 0.5.3-1

mcl_3dl
* Add odom/imu/cloud_queue_size params (#375 <https://github.com/at-wat/mcl_3dl/issues/375>)
* Fix flaky tests (#376 <https://github.com/at-wat/mcl_3dl/issues/376>)
* Contributors: Atsushi Watanabe

Holding kinetic releases for the upcoming sync


rendering TeX

Hi, this library seems to compare itself to MathJAX, however, the more research seems to show it's actually only an equation rendering system, and MathJAX is more comparable to TeX because  it renders strings like here is a function $f(x)$, ....
Am I missing something, or is documented how to do this somewhere?
There was an issue here (https://github.com/Khan/KaTeX/issues/3) that says it may be a possibility, where on the roadmap is this?
For example, how does one go about rendering this in KaTeX?
Here is a $r_2(n) = \{ (a,b) \in \mathbb{Z} | a^2 + b^2 = n \}$, which counts the number of representations of $n$ as a number of 2 squares.

MathJax is also an equation rendering system like KaTeX, only that it automatically renders all wrapped LaTeX nodes.
The same is possible using the auto render plugin https://github.com/Khan/KaTeX/blob/master/contrib/auto-render/README.md
KaTeX uses an synchronous approach for rendering LaTeX, which makes it a faster than MathJax

@pyramation KaTeX and MathJax both only typeset math within $ (or otherwise specified) delimiters.  https://github.com/Khan/KaTeX/issues/3 is about general support of TeX which is substantially more than just rendering math inside $ delimiters.  The focus of KaTeX is rendering of math, not recreating the full TeX system.

@kevinbarabash I understand, I actually wrote the library #3 was referring to. @waywaaard (thanks) I think that's generally what I'm talking about.

See also the related issue I raised (and eventually plan to do): #604


Add blog post about Artsy's switching to JWT

@joeyAghion Can you take a look at this and see if it makes sense to you and make sure I haven't missed anything.

Looking forward to fixing many spelling and grammatical problems 👀

https://jwt.io has a great visualization of the JWT structure, including the payload. We could borrow it entirely, or I'm happy to mock something up:

Thanks @ashfurrow, that would be great, I've added little more details there but would be nice to have some more visuals 👀

Here's the graphic, let me know if yo want it changed or anything:

Thanks @ashfurrow this looks great, I'll add them.

Graphic looks great!

I just modified last line the post to reflect how we are going to deprecate legacy tokens. Let me know if I missed anything.

Thanks @ashkan18!


used both in library and application , but print the same log twice

Are you using a multiline String with .trimMargin()? Logger seems to log twice when using .trimMargin().

Are you using a multiline String with .trimMargin()? Logger seems to log twice when using .trimMargin().

Same issue after upgrade to the newest version

Do you add LogAdapter twice? It should be used only once, that's the issue. It would be best if you can just initialize it in one place and use it in library.

yes, i have added LogAdapter twice !

Good to hear that. Closing this issue. 👍


Pull private containers

Hi!
I want to pull/push some private containers (hosted on hub.docker.com). But I can't.
I have cluster with 2 nodes and 2 managers.
% export DOCKER_HOST='....:4000';
% docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username: noose
Password:
Login Succeeded

% docker pull noose/my-container:latest
ip-10-0-1-206: Pulling noose/my-container:latest... : Error: image noose/my-container not found
ip-10-0-1-207: Pulling noose/my-container:latest... : Error: image noose/my-container not found
Error: image noose/my-container:latest not found

How it's possible that swarm is production-ready, but there are such errors?

It is known issue https://github.com/docker/swarm/issues/2217

Closing this issue since discussion is tracked in #2217 and fixed in #2272


Capacitor grounds not connected

As can be seen in the screenshots below, the grounds of the two capacitors are connected to each other and a ground fill island on the bottom side.
This ground fill island is then not connected to the rest of ground, but it should be.
Top side:

Bottom side:

That's a good find. Could you add pics to PR #28 to show the fix?

Yeah, would have been a good idea in the first place.
I have added screenshots of the full board and both layers.

@eltobu good catch, & @blurfl thanks for the fix. Can anyone tell if this issue is also in the KiCad version of the project as it was autogenerated a week before this fix?

@darigovresearch As far as I can tell, #28 addressed the problem in the KiCad version, and #29 addressed the problem in the EAGLE version.

Thanks @drspangle for confirming & @blurfl for the fix!


Bug/block ex

adds info to blockExplorer errores.
rename event to match other names.

Coverage remained the same at 94.53% when pulling 213451f0d6d5ed017f29a319afa1f98cb2116a59 on matiu:bug/blockEx into a93b914329e0ccb3643fb756d04d8673f0b74b00 on bitpay:master.

updated.

Coverage remained the same at 94.53% when pulling 629b1551a0b5cb85a8ad9ecd9cd947367b3a5ed0 on matiu:bug/blockEx into a93b914329e0ccb3643fb756d04d8673f0b74b00 on bitpay:master.


Update cert manager to 0.6.1

This updates cert-manager to 0.6.1 (latest chart).
Following changes have been introduced as compared to vanilla upstream chart:

Re-add createCustomResource: Upstream chart dropped the support for managing CRDs (recommendation is to do this manually). The code has been kept in templates, just not documented, so this has been re-added, using the original createCustomResource.
useCrdInstallHook: Upstream used crd-install hook to manage CRDs, which is one or relatively new constructs how to manage CRDs via Helm, but issue is that these CRDs are only created and never deleted. This does not work with GPII infra approach, recreating chart will fail (complaining about already existing CRDs). useCrdInstallHook has been introduced to manage this.
/charts for sub-carts: Subcharts normally live directly in chart root folder, such as /webhook, for some reason Terraform Helm provider can only handle subcharts if those are in /charts sub-directory (no luck with modifying the path in requirements.yaml in any way)
Disable validation webhook: Validation webhook was introduced in upstream, which does validation of CRDs (as certificate or issuer) on creation (as opposed to when these are processed). This is nice, but requires deploying additional components to the cluster and modification of namespace labels. As this doesn't really bring much of a benefit, it was disabled to avoid additional complexity. See https://docs.cert-manager.io/en/latest/admin/resource-validation-webhook.html for more details.

LGTM. Thanks for the detailed write-up of the local differences from upstream.


Missing activity definition fields

There are a number of fields missing from the Activity Definition:

Type
Extensions
More info
Various properties relating to interactions.

See https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md#actdef

Ignore me; i think i've got an old version.


Given i use junit reporter, the report generated is truncated and unreadable

Environment :

Node.js version: 14.5.0
NPM version: 6.14.5
Browser name and version: Chrome 87
Platform name and version: mac
WebdriverIO version: 6.10.11
wdio-image-comparison-service version: 2.0.0
@wdio/junit-reporter: "6.10.6

Config of WebdriverIO + wdio-image-comparison-service
const config = {

  user: process.env.BROWSERSTACK_USER,
  key: process.env.BROWSERSTACK_KEY,

  services: [
    ['image-comparison',
      // The options
      {
        baselineFolder: BASELINE_IMAGE_FOLDER,
        formatImageName: '{tag}-{logName}-{width}x{height}',
        screenshotPath: ALL_IMAGE_FOLDER,
        savePerInstance: true,
        autoSaveBaseline: true,
        blockOutStatusBar: true,
        blockOutToolBar: true,
        clearRuntimeFolder: true,
      },
    ],
  ],

  exclude: [
  ],
  specs: [
    './tests/**/*.spec.js',
  ],
  specFileRetries:  2,

  maxInstances: 50,

  capabilities: [
    {
      browserName: 'chrome',
      browser_version: '87',
      os: 'OS X',
      os_version: 'Catalina',
      acceptInsecureCerts: true,
      resolution: '1280x960',
      realMobile: false,
      local: false,
      buildName: buildDescription,
      projectBrowserName: SCREEN_SIZE.DESKTOP.type,
      projectName,
    },
    {
      browserName: 'chrome',
      'goog:chromeOptions': {
        mobileEmulation: { deviceName: 'iPhone X' },
      },
      browser_version: '87',
      os: 'OS X',
      os_version: 'Catalina',
      acceptInsecureCerts: true,
      resolution: '1280x960',
      realMobile: false,
      local: false,
      buildName: buildDescription,
      projectBrowserName: SCREEN_SIZE.IPHONE_X.type,
      projectName,
    },
  ],
  logLevel: 'error',

  bail: 0,

  baseUrl: 'http://localhost:3000',
  waitforTimeout: 20000,
  connectionRetryTimeout: 120000,
  connectionRetryCount: 3,

  framework: 'mocha',
  reporters: ['spec',
    ['junit', {
      outputDir: JUNIT_REPORTS,
      outputFileFormat() { // optional
        return 'visualTestRuns.xml';
      },
    }],
  ],

  mochaOpts: {
    // Babel setup
    compilers: ['js:@babel/register'],
    ui: 'bdd',
    timeout: 900000,
  }
  beforeSession(config, capabilities, specs) { // eslint-disable-line
    global.assert = chai.assert;
  },
};

Describe the bug
Given i run visual test runs using webdriverIO and image comparison library on browserstack or locally and parallel to each test runs ( ~50 runs at once)
when the test run completes and junit report generated
then i see the report incomplete and not usable :
 </system-out>
    </testcase>
  </testsuite>
</testsuites>e bytes)","args":[]}
RESULT: {"script":"return (function getDocumentScrollHeight() {\n    var viewPortHeight = Math.max(document.documentElement.clientHeight, window.innerHeight || 0);\n    var scrollHeight = document.documentElement.scrollHe ... (1184 more bytes)","args":[]}
COMMAND: POST /session/6050c309b30a41c8a0ebab3b4d5075152acf2f8d/execute - {"script":"return (function scrollToPosition(yPosition) {\n    (document.scrollingElement || document.documentElement).scrollTop = yPosition;\n}).apply(null, arguments)","args":[814]}
RESULT: {"script":"return (function scrollToPosition(yPosition) {\n    (document.scrollingElement || document.documentElement).scrollTop = yPosition;\n}).apply(null, arguments)","args":[814]}
COMMAND: GET /session/6050c309b30a41c8a0ebab3b4d5075152acf2f8d/screenshot - {}
RESULT: {}
COMMAND: POST /session/6050c309b30a41c8a0ebab3b4d5075152acf2f8d/execute - {"script":"return (function getDocumentScrollHeight() {\n    var viewPortHeight = Math.max(document.documentElement.clientHeight, window.innerHeight || 0);\n    var scrollHeight = document.documentElement.scrollHe ... (1184 more bytes)","args":[]}
RESULT: {"script":"return (function getDocumentScrollHeight() {\n    var viewPortHeight = Math.max(document.documentElement.clientHeight, window.innerHeight || 0);\n    var scrollHeight = document.documentElement

NOTE the same junit report works fine with functional tests on wdio
To Reproduce
Run any test with the config i provided and run the tests in parallel and you can see the junit report generated fail
Expected behaviour
get a readable report of all test run and retried
Log
Additional context

Hi @AutomationGuru
This module is sending a lot of data to the drivers, if that breaks the junit report then that is an issue with the report instead of  with this module. That's why I'm going to close this issue because it's not module related. Feel free to open a ticket for the junit reporter

Hi @AutomationGuru
This module is sending a lot of data to the drivers, if that breaks the junit report then that is an issue with the report instead of  with this module. That's why I'm going to close this issue because it's not module related. Feel free to open a ticket for the junit reporter

Understood thanks

Understood thanks


help: Tweak docs on keyboard shortcuts for composing messages.

Adjust the order in keyboard shortucts help menu and help center.
Make minor wording improvements.

This PR removes wording and ordering differences between the two docs that don't seem helpful to me.

`?` menu before/after

Before
After

Current help center page: https://zulip.com/help/keyboard-shortcuts#composing-messages

 Help center changes (screenshot)

Merged, thanks @alya!


Backporting fixes for kuttl jobs

This PR has two cherry picks to fix kuttl job in dev-preview2 branch:
https://github.com/openstack-k8s-operators/ci-framework/commit/438d628545d0951cc63d8dc468ec18bd586db414
https://github.com/openstack-k8s-operators/ci-framework/commit/b33a9da2d37a7119ed6c77f70acbb2e1d8088802
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running
[X] Appropriate documentation exists and/or is up-to-date:

[X] README in the role
[X] Content of the docs/source is reflecting the changes

recheck
timeout issues

/lgtm

/approve

/approve


KAFKA-17636 Fix scram bootstrap records

Fixes a regression introduced in https://github.com/apache/kafka/pull/16669 which inadvertently stopped processing SCRAM arguments.

back ported to 3.9 as 2cbc5bd3c


openchat_v3.2_super deployment to SageMaker doesn't work

Hi team,
I would like to deploy new model to AWS Sagemaker with below code and getting RuntimeError: weight model.layers.0.self_attn.rotary_emb.inv_freq does not exist seems something is missing in the model index. At least, I couldn't find it in https://huggingface.co/openchat/openchat_v3.2_super/blob/main/pytorch_model.bin.index.json
Thanks in advance for your help!
Here is the deploy.py
import json
import sagemaker
import boto3
from sagemaker.huggingface import HuggingFaceModel, get_huggingface_llm_image_uri

try:
	role = sagemaker.get_execution_role()
except ValueError:
	iam = boto3.client('iam')
	role = iam.get_role(RoleName='role-name')['Role']['Arn']

# Hub Model configuration. https://huggingface.co/models
hub = {
	'HF_MODEL_ID':'openchat/openchat_v3.2_super',
	'SM_NUM_GPUS': json.dumps(4)
}

# create Hugging Face Model Class
huggingface_model = HuggingFaceModel(
	image_uri=get_huggingface_llm_image_uri("huggingface",version="0.9.3"),
	env=hub,
	role=role,
)

# deploy model to SageMaker Inference
predictor = huggingface_model.deploy(
	initial_instance_count=1,
	instance_type="ml.g5.12xlarge",
    endpoint_name="openchat-v3-2-super",
	container_startup_health_check_timeout=600,
  )

# send request
predictor.predict({
	"inputs": "My name is Julien and I like to",
})

This is because of some optimizations for padding-free training, the missing weights can be safely ignored and just let HF initialize them. You can set the ignore missing weights flag.


🐛 takePhoto does not return on example/ app, in specific emulator

What were you trying to do?
I wanted to take a picture :)
Reproduceable Code
https://github.com/mrousavy/react-native-vision-camera/tree/main/example using
this emulator:
Device: "Pixel XL"
Image: "Android API 31 (Google APIs) x86_64"

What happened instead?
 DEBUG  state: ACTIVE
 DEBUG  state: END
 LOG  Taking photo...

and it hangs there forever.
Relevant log output
No response
Device
Emulator for "Pixel XL" using Image "Android API 31 (Google APIs) x86_64"
VisionCamera Version
HEAD
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

This is indeed very weird. Either it's falling back to Snapshot (not logged, so I guess not?), or it's a CameraX bug..

FYI, the logcat logs. This one is from Pixel 4 XL (instead of just Pixel XL).  Will attempt recovering from error.
01-19 11:45:25.402 22811 22898 D Camera2CameraImpl: Attempt to reopen camera[0] after error[ERROR_CAMERA_IN_USE]
01-19 11:45:25.403 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Transitioning camera internal state: OPENED --> REOPENING
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: Recalculating open cameras:
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: Camera                                       State
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: -------------------------------------------------------------------
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: Camera@fc88e22[id=0]                         OPENING
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: Camera@b21bf7a[id=1]                         UNKNOWN
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: -------------------------------------------------------------------
01-19 11:45:25.403 22811 22898 D CameraStateRegistry: Open count: 1 (Max allowed: 1)
01-19 11:45:25.403 22811 22898 D CameraStateMachine: New public camera state CameraState{type=OPENING, error=StateError{code=2, cause=null}} from OPENING and StateError{code=2, cause=null}
01-19 11:45:25.403 22811 22898 D CameraStateMachine: Publishing new public camera state CameraState{type=OPENING, error=StateError{code=2, cause=null}}
01-19 11:45:25.403 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Resetting Capture Session
01-19 11:45:25.404 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Releasing session in state REOPENING
01-19 11:45:25.404 22811 22898 D Camera2CameraImpl: CameraDevice.onError(): 0 failed with ERROR_CAMERA_DEVICE while in REOPENING state. Will attempt recovering from error.
01-19 11:45:25.404 22811 22898 D Camera2CameraImpl: Attempt to reopen camera[0] after error[ERROR_CAMERA_DEVICE]
01-19 11:45:25.404 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Transitioning camera internal state: REOPENING --> REOPENING
01-19 11:45:25.404 22811 22898 D CameraStateMachine: New public camera state CameraState{type=OPENING, error=StateError{code=3, cause=null}} from OPENING and StateError{code=3, cause=null}
01-19 11:45:25.404 22811 22898 D CameraStateMachine: Publishing new public camera state CameraState{type=OPENING, error=StateError{code=3, cause=null}}
01-19 11:45:25.404 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Resetting Capture Session
01-19 11:45:25.404 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Releasing session in state REOPENING
01-19 11:45:25.405 22811 22898 D CaptureSession: onSessionFinished()
01-19 11:45:25.391     0     0 I init    : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 21795) process group...
01-19 11:45:25.395     0     0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 21795 in 0ms
01-19 11:45:25.396     0     0 I init    : starting service 'vendor.camera-provider-2-4'...
01-19 11:45:25.431 22955 22955 I<EMAIL_ADDRESS><EMAIL_ADDRESS>legacy service is starting.
01-19 11:45:25.467   474 22918 W CallStack: update: Failed to unwind callstack.
01-19 11:45:25.467   474 22918 E ProcessCallStack: getThreadName: Failed to open /proc/self/task/22919/comm
01-19 11:45:25.467   474 22918 D CameraTraces: Process trace saved. Use dumpsys media.camera to view.
01-19 11:45:25.469   474   521 E Camera3-Device: flush: Transaction error: Status(EX_TRANSACTION_FAILED): 'DEAD_OBJECT: '
01-19 11:45:25.469   474   521 E CameraDeviceClient: detachDevice: flush failed with code 0xffffffe0
01-19 11:45:25.469   474   521 I Camera3-Device: disconnectImpl: E
01-19 11:45:25.469   474   521 E Camera3-Device: Camera 0: disconnectImpl: Shutting down in an error state
01-19 11:45:25.469   474   521 I CameraLatencyHistogram: ProcessCaptureRequest latency histogram (5172) samples:
01-19 11:45:25.469   474   521 I CameraLatencyHistogram:        40     80    120    160    200    240    280    320    360    inf (max ms)
01-19 11:45:25.469   474   521 I CameraLatencyHistogram:      99.96   0.02   0.00   0.00   0.00   0.02   0.00   0.00   0.00   0.00 (%)
01-19 11:45:25.469   474   521 W Camera3-OutputUtils: flushInflightRequests: Frame 5157 |  Timestamp:<PHONE_NUMBER>343, metadata arrived: true, buffers left: 1.
01-19 11:45:25.469   474   521 W Camera3-OutputUtils: flushInflightRequests: Frame 5170 |  Timestamp:<PHONE_NUMBER>343, metadata arrived: false, buffers left: 1.
01-19 11:45:25.469   474   521 W Camera3-OutputUtils: flushInflightRequests: Frame 5171 |  Timestamp: 0, metadata arrived: false, buffers left: 1.
01-19 11:45:25.471   474   521 I CameraLatencyHistogram: Stream 0 dequeueBuffer latency histogram (5172) samples:
01-19 11:45:25.471   474   521 I CameraLatencyHistogram:         5     10     15     20     25     30     35     40     45    inf (max ms)
01-19 11:45:25.471   474   521 I CameraLatencyHistogram:      74.23   5.99   14.40   5.12   0.25   0.00   0.00   0.00   0.00   0.00 (%)
01-19 11:45:25.472   474   521 I CameraLatencyHistogram: Stream 1 dequeueBuffer latency histogram (1) samples:
01-19 11:45:25.472   474   521 I CameraLatencyHistogram:         5     10     15     20     25     30     35     40     45    inf (max ms)
01-19 11:45:25.472   474   521 I CameraLatencyHistogram:      100.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00 (%)
01-19 11:45:25.472 22811 22930 W GraphicBufferSource: released unpopulated slots: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63]
01-19 11:45:25.472   474   521 I Camera3-Device: disconnectImpl: X
01-19 11:45:25.477   194   194 I hwservicemanager: getTransport: Cannot find entry android.hardware.graphics.mapper@4.0::IMapper/default in either framework or device VINTF manifest.
01-19 11:45:25.477 22955 22955 I Gralloc4: mapper 4.x is not supported
01-19 11:45:25.478   474   521 I CameraService: onTorchStatusChangedLocked: Torch status changed for cameraId=1, newStatus=1
01-19 11:45:25.478   474   521 I CameraService: disconnect: Disconnected client for camera 0 for PID 22811
01-19 11:45:25.479 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} CameraDevice.onClosed()
01-19 11:45:25.479 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Camera closed due to error: ERROR_CAMERA_DEVICE
01-19 11:45:25.479 22811 22898 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Attempting camera re-open in 700ms: androidx.camera.camera2.internal.Camera2CameraImpl$StateCallback$ScheduledReopen@1c7aab7
01-19 11:45:25.481 22955 22955 D HostConnection: createUnique: call
01-19 11:45:25.482 22955 22955 D HostConnection: HostConnection::get() New Host Connection established 0x7156be898850, tid 22955
01-19 11:45:25.482 22955 22955 D goldfish-address-space: allocate: Ask for block of size 0x100
01-19 11:45:25.483 22955 22955 D goldfish-address-space: allocate: ioctl allocate returned offset 0x3dfffe000 size 0x2000
01-19 11:45:25.484 22955 22955 D EmulatedCamera_QemuClient: Emulated camera list: name=virtualscene channel=0 pix=876758866 dir=back framedims=640x480,352x288,320x240,176x144,1280x720,1280x960
01-19 11:45:25.488 22955 22955 W libc    : Access denied finding property "qemu.sf.back_camera_hal"
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: Constructing emulated qemu camera 3: ID 0
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: parseResolutions: 640x480
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: parseResolutions: 352x288
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: parseResolutions: 320x240
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: parseResolutions: 176x144
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: parseResolutions: 1280x720
01-19 11:45:25.488 22955 22955 I EmulatedCamera_QemuCamera3: parseResolutions: 1280x960
01-19 11:45:25.489 22955 22955 W libc    : Access denied finding property "qemu.sf.back_camera_caps"
01-19 11:45:25.489 22955 22955 I EmulatedCamera_QemuCamera3: Camera 0 capabilities:
01-19 11:45:25.489 22955 22955 I EmulatedCamera_QemuCamera3:   BACKWARD_COMPATIBLE
01-19 11:45:25.489 22955 22955 E EmulatedCamera_Factory: 1 cameras are being emulated. 0 of them are fake cameras.
01-19 11:45:25.491 22955 22959 E EmulatedCamera_HotplugThread: addWatch: Could not add watch for '/data/misc/media/emulator.camera.hotplug.0', error: 'Permission denied' (13)
01-19 11:45:25.482 22955 22955 W android.hardwar: type=1400 audit(0.0:307): avc: denied { read } for name="u:object_r:default_prop:s0" dev="tmpfs" ino=122 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
01-19 11:45:25.492 22955 22955 E<EMAIL_ADDRESS>setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
01-19 11:45:25.492 22955 22955 E<EMAIL_ADDRESS>initialize: Vendor tag setup failed, will not be available.
01-19 11:45:25.492 22955 22955 W libc    : Access denied finding property "qemu.camera.fake.orientation"
01-19 11:45:25.492 22955 22955 V EmulatedCamera_BaseCamera: getCameraInfo
01-19 11:45:25.493 22955 22955 I HidlServiceManagement: Registered android.hardware.camera.provider@2.4::ICameraProvider/legacy/0
01-19 11:45:25.493 22955 22955 I HidlServiceManagement: Removing namespace from process name<EMAIL_ADDRESS>to<EMAIL_ADDRESS>01-19 11:45:25.493 22955 22955 I LegacySupport: Registration complete for android.hardware.camera.provider@2.4::ICameraProvider/legacy/0.
01-19 11:45:25.494   474   521 I CameraProviderManager: Connecting to new camera provider: legacy/0, isRemote? 1
01-19 11:45:25.495   474   521 I CameraProviderManager: Enumerating new camera device<EMAIL_ADDRESS>01-19 11:45:25.496   474   521 E CameraProviderManager: DeviceInfo3: Converted ICameraDevice instance to nullptr
01-19 11:45:25.497   474   521 I CameraProviderManager: Camera provider legacy/0 ready with 1 camera devices
01-19 11:45:25.497   474   521 I CameraService: onDeviceStatusChanged: Status changed for cameraId=0, newStatus=1
01-19 11:45:25.497   474   521 I CameraService: onDeviceStatusChanged: Unknown camera ID 0, a new camera is added
01-19 11:45:25.486 22955 22955 W android.hardwar: type=1400 audit(0.0:308): avc: denied { read } for name="u:object_r:default_prop:s0" dev="tmpfs" ino=122 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
01-19 11:45:25.490 22955 22955 W android.hardwar: type=1400 audit(0.0:309): avc: denied { read } for name="u:object_r:default_prop:s0" dev="tmpfs" ino=122 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
01-19 11:45:26.096 22811 22830 D EGL_emulation: app_time_stats: avg=4.80ms min=1.09ms max=29.65ms count=61
01-19 11:45:26.205 22811 22897 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Attempting to open the camera.
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: tryOpenCamera(Camera@fc88e22[id=0]) [Available Cameras: 0, Already Open: true (Previous state: OPENING)] --> SUCCESS
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: Recalculating open cameras:
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: Camera                                       State
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: -------------------------------------------------------------------
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: Camera@fc88e22[id=0]                         OPENING
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: Camera@b21bf7a[id=1]                         UNKNOWN
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: -------------------------------------------------------------------
01-19 11:45:26.205 22811 22897 D CameraStateRegistry: Open count: 1 (Max allowed: 1)
01-19 11:45:26.205 22811 22897 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Cancelling scheduled re-open: androidx.camera.camera2.internal.Camera2CameraImpl$StateCallback$ScheduledReopen@1c7aab7
01-19 11:45:26.207 22811 22897 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Opening camera.
01-19 11:45:26.210 22811 22897 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Transitioning camera internal state: REOPENING --> OPENING
01-19 11:45:26.211 22811 22897 D CameraStateMachine: New public camera state CameraState{type=OPENING, error=null} from OPENING and null
01-19 11:45:26.211 22811 22897 D CameraStateMachine: Publishing new public camera state CameraState{type=OPENING, error=null}
01-19 11:45:26.212 22811 22897 D UseCaseAttachState: All use case: [androidx.camera.video.VideoCapture-29ae22e7-ebba-4596-9fc0-e037d144ffd846650572, androidx.camera.core.ImageCapture-4f489441-14b4-4b53-86a8-11dfdc3fa3e962124821, androidx.camera.core.Preview-c760ae44-8138-4668-b6c5-471b5d43bd2185057279] for camera: 0
01-19 11:45:26.214   474   474 I CameraService: CameraService::connect call (PID -1 "com.mrousavy.camera.example", camera ID 0) and Camera API version 2
01-19 11:45:26.215   474   474 I Camera2ClientBase: Camera 0: Opened. Client: com.mrousavy.camera.example (PID 22811, UID 10149)
01-19 11:45:26.215   474   474 I CameraDeviceClient: CameraDeviceClient 0: Opened
01-19 11:45:26.217   194   194 I hwservicemanager: getTransport: Cannot find entry android.hardware.graphics.allocator@4.0::IAllocator/default in either framework or device VINTF manifest.
01-19 11:45:26.217 22955 22960 W Gralloc4: allocator 4.x is not supported
01-19 11:45:26.219 22955 22960 W libc    : Access denied finding property "ro.camera.req.fmq.size"
01-19 11:45:26.220 22955 22960 W libc    : Access denied finding property "ro.camera.res.fmq.size"
01-19 11:45:26.222   548   964 V CameraService_proxy: The activity is N or above and claims to support resizeable-activity. Crop-rotate-scale is disabled.
01-19 11:45:26.218 22955 22955 W HwBinder:22955_: type=1400 audit(0.0:310): avc: denied { read } for name="u:object_r:default_prop:s0" dev="tmpfs" ino=122 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
01-19 11:45:26.225 22811 22897 D Camera2CameraImpl: {Camera@fc88e22[id=0]} Transitioning camera internal state: OPENING --> OPENED
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: Recalculating open cameras:
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: Camera                                       State
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: -------------------------------------------------------------------
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: Camera@fc88e22[id=0]                         OPEN
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: Camera@b21bf7a[id=1]                         UNKNOWN
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: -------------------------------------------------------------------
01-19 11:45:26.225 22811 22897 D CameraStateRegistry: Open count: 1 (Max allowed: 1)
01-19 11:45:26.226 22811 22897 D CameraStateMachine: New public camera state CameraState{type=OPEN, error=null} from OPEN and null
01-19 11:45:26.226 22811 22897 D CameraStateMachine: Publishing new public camera state CameraState{type=OPEN, error=null}
01-19 11:45:26.227 22811 22897 D UseCaseAttachState: All use case: [androidx.camera.video.VideoCapture-29ae22e7-ebba-4596-9fc0-e037d144ffd846650572, androidx.camera.core.ImageCapture-4f489441-14b4-4b53-86a8-11dfdc3fa3e962124821, androidx.camera.core.Preview-c760ae44-8138-4668-b6c5-471b5d43bd2185057279] for camera: 0
01-19 11:45:26.227 22811 22897 D SyncCaptureSessionBase: [androidx.camera.camera2.internal.SynchronizedCaptureSessionBaseImpl@93511bc] getSurface...done
01-19 11:45:26.227 22811 22897 D CaptureSession: Opening capture session.
01-19 11:45:26.230 22811 22897 D DeferrableSurface: New surface in use[total_surfaces=3, used_surfaces=1](androidx.camera.core.SurfaceRequest$2@31e6af6}
01-19 11:45:26.230 22811 22897 D DeferrableSurface: use count+1, useCount=1 androidx.camera.core.SurfaceRequest$2@31e6af6
01-19 11:45:26.230 22811 22897 D DeferrableSurface: New surface in use[total_surfaces=3, used_surfaces=2](androidx.camera.core.impl.ImmediateSurface@45008fc}
01-19 11:45:26.230 22811 22897 D DeferrableSurface: use count+1, useCount=1 androidx.camera.core.impl.ImmediateSurface@45008fc
01-19 11:45:26.230 22811 22897 D DeferrableSurface: New surface in use[total_surfaces=3, used_surfaces=3](androidx.camera.core.SurfaceRequest$2@b54393}
01-19 11:45:26.230 22811 22897 D DeferrableSurface: use count+1, useCount=1 androidx.camera.core.SurfaceRequest$2@b54393
01-19 11:45:26.231   474   474 W cameraserver: createSurfaceFromGbp: Camera 0 with consumer usage flag: 2304: Forcing asynchronous mode forstream
01-19 11:45:26.232   474   474 W cameraserver: createSurfaceFromGbp: Camera 0: Overriding format 0x4 to IMPLEMENTATION_DEFINED
01-19 11:45:26.218 22955 22955 W HwBinder:22955_: type=1400 audit(0.0:311): avc: denied { read } for name="u:object_r:default_prop:s0" dev="tmpfs" ino=122 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
01-19 11:45:26.240   474   474 E Camera3-Device: configureStreams: Stream 1: DataSpace override not allowed for format 0x21
01-19 11:45:26.248   474   474 D Camera3-Device: Set real time priority for request queue thread (tid 22968)
01-19 11:45:26.249 22811 22897 D CaptureSession: Attempting to send capture request onConfigured
01-19 11:45:26.249 22811 22897 D CaptureSession: Issuing request for session.
01-19 11:45:26.251 22811 22897 D CaptureSession: CameraCaptureSession.onConfigured() mState=OPENED
01-19 11:45:26.251 22811 22897 D CaptureSession: CameraCaptureSession.onReady() OPENED
01-19 11:45:26.251   363   419 D goldfish-address-space: claimShared: Ask to claim region [0x3e01c2000 0x3e0384000]
01-19 11:45:26.254   194   194 I hwservicemanager: getTransport: Cannot find entry android.hardware.graphics.mapper@4.0::IMapper/default in either framework or device VINTF manifest.
01-19 11:45:26.255 22955 22961 D HostConnection: createUnique: call
01-19 11:45:26.255 22955 22961 D HostConnection: HostConnection::get() New Host Connection established 0x7156be898550, tid 22961
01-19 11:45:26.256 22955 22961 D goldfish-address-space: allocate: Ask for block of size 0x100
01-19 11:45:26.256 22955 22961 D goldfish-address-space: allocate: ioctl allocate returned offset 0x3dfffe000 size 0x2000
01-19 11:45:26.262 22955 22961 D HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV_Cache ANDROID_EMU_has_shared_slots_host_memory_allocator ANDROID_EMU_sync_buffer_data ANDROID_EMU_read_color_buffer_dma GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_gles_max_version_3_0
01-19 11:45:26.273 22955 22961 D HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV_Cache ANDROID_EMU_has_shared_slots_host_memory_allocator ANDROID_EMU_sync_buffer_data ANDROID_EMU_read_color_buffer_dma GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_gles_max_version_3_0
01-19 11:45:26.288   363   419 D goldfish-address-space: claimShared: Ask to claim region [0x3e0384000 0x3e0546000]
01-19 11:45:26.525   363   419 D goldfish-address-space: claimShared: Ask to claim region [0x3e0546000 0x3e0708000]
01-19 11:45:26.579   363   419 D goldfish-address-space: claimShared: Ask to claim region [0x3e0708000 0x3e08ca000]
01-19 11:45:27.118 22811 22830 D EGL_emulation: app_time_stats: avg=3.50ms min=1.42ms max=15.45ms count=47

Oh so it's actually crashing the app?

Actually, it’s not. It still works just hangs after takePhoto
On Wed, 19 Jan 2022 at 11:58, Marc Rousavy @.***> wrote:

Oh so it's actually crashing the app?
—
Reply to this email directly, view it on GitHub
https://github.com/mrousavy/react-native-vision-camera/issues/747#issuecomment-1016330043,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFWP74RV4AALENRKT6DQYDUW2KMDANCNFSM5MEZRYYQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

This seems to be an issue with the emulator
https://github.com/android/camera-samples/issues/432#issuecomment-952121904
https://github.com/android/camera-samples/issues/430
https://github.com/android/camera-samples/issues/428

have you solved this problem,  the newest version camera-core:1.1.0-beta03 still hang when i take photo

have you solved this problem, the newest version camera-core:1.1.0-beta03 still hang when i take photo

The issue is with the emulator device itself. Shut down the emulator device, then edit the settings for the device in the device manager. Click Show Advanced Settings then ensure your Cameras are set to "Emulated" instead of "VirtualScene".

have you solved this problem, the newest version camera-core:1.1.0-beta03 still hang when i take photo

The issue is with the emulator device itself. Shut down the emulator device, then edit the settings for the device in the device manager. Click Show Advanced Settings then ensure your Cameras are set to "Emulated" instead of "VirtualScene".

So is there no way to get takePicture to work if your using a physical webcam?
Why is this issue closed? I still am encountering the takePicture bug where it does not return anything.


Playback and performance issues on latest Chromium versions

As reported by many users, the latest Chromium updates made some changes that cause the player to have performance issues, cracking noises, clipping, static noise.

Temporary workaround added in v2.3.0, still an issue


Terminal doesn't respect "start /max" and "/min" parameters when running a console app as default terminal

Windows Terminal version
1.11.3471.0
Windows build number
10.0.22000.434
Other Software
Seemingly any console application (cmd, powershell, python, batch file) -- I'm using python as an example here.
Steps to reproduce

set terminal as default terminal
open command prompt in terminal
run for example "start /max python.exe" (or powershell, or cmd, or some batch file)
the window will show windowed, not maximised

Expected Behavior
New window starts maximised, as it does when the default Windows console is set.
The correct behaviour also happens if you run wt.exe itself, i.e. "start /max wt python"

Actual Behavior
New window starts windowed

BTW, the /min parameter is even worse. "start /min python.exe" starts the classic console, while "start /min wt python.exe" does make a minimised WT window, but you can't switch to it for some reason.

Alright, so there are three elements here. From the bottom up:

start /min wt python.exe we're tracking in #9053, so feel free to continue that element there.

Without knowing the details of what's possible, I'd expect Terminal to honor relevant fields in STARTUPINFO after a handoff from conhost. When a new tab (not a window) is created, I'd expect it to use lpTitle and -- if they're still relevant in any way -- dwXCountChars, dwYCountChars, and dwFillAttribute. When a new window is created, I'd expect it to honor the window's initial show state, position, and size: wShowWindow, dx, dy, dwXSize, and dwYSize. If honoring a setting isn't possible or isn't relevant when using Terminal as the default, please document it for STARTUPINFO, or document it in the console docs.
I understand skipping the handoff to Terminal if wShowWindow is SW_HIDE (0). A hidden Terminal window would be dysfunctional since a console app can't programmatically restore the window, and neither can the user. I don't understand skipping the handoff for SW_SHOWMINIMIZED (2), SW_MINIMIZE (6), SW_SHOWMINNOACTIVE (7), and SW_FORCEMINIMIZE (11). In principle, the user can easily restore a minimized terminal. Maybe this was implemented because Terminal doesn't support wShowWindow properly. For example, as mentioned above, start /min wt is broken. It's better to use the classic console until that gets fixed.

Without knowing the details of what's possible, I'd expect Terminal to honor relevant fields in STARTUPINFO after a handoff from conhost. When a new tab (not a window) is created, I'd expect it to use lpTitle and -- if they're still relevant in any way -- dwXCountChars, dwYCountChars, and dwFillAttribute. When a new window is created, I'd expect it to honor the window's initial show state, position, and size: wShowWindow, dx, dy, dwXSize, and dwYSize. If honoring a setting isn't possible or isn't relevant when using Terminal as the default, please document it for STARTUPINFO, or document it in the console docs.

I get doing lpTitle. That should be easy even if inserting a tab into an existing window. I guess same for dwFillAttribute.
But for the other ones related to sizing and visibility... I think what I'd do is... if the inbound connection specified any of those, I'd ensure the monarch/peasant granted them a fresh window to manipulate however they specified without tampering with the user's existing window. So they can only "join" automatically if they're not going to mess with what is existing and are flexible with the layout.

I understand skipping the handoff to Terminal if wShowWindow is SW_HIDE (0). A hidden Terminal window would be dysfunctional since a console app can't programmatically restore the window, and neither can the user. I don't understand skipping the handoff for SW_SHOWMINIMIZED (2), SW_MINIMIZE (6), SW_SHOWMINNOACTIVE (7), and SW_FORCEMINIMIZE (11). In principle, the user can easily restore a minimized terminal. Maybe this was implemented because Terminal doesn't support wShowWindow properly. For example, as mentioned above, start /min wt is broken. It's better to use the classic console until that gets fixed.

This was just a matter of scoping it. You're right, Terminal doesn't support wShowWindow completely/properly yet and we hadn't thought through all those scenarios, so the minimum scope to get the "hard part" of the actual handoff out of the way was my goal. Additionally, when I was doing my testing, two things stood out to me: 1. Applications that don't set any of the flags or any settings and ask for a completely blank console session are most commonly destined for an interactive session. 2. Applications that mess with all the flags during the ::CreateProcess call are usually extraordinarily sensitive to changes and performance characteristics, so I didn't want to impact them right away.

conhost reads the Cac, decides if it wants to handoff. It does not drain the Cac from the driver
openconsole gets handed off to, it reads the driver. The message in flight has the original Cac
so OpenConsole can read the startup info, without rev'ing the defterm interface

Note: For discussion:

I'm leaning towards closing this out with the combo of #14222 and #13838. We can pass the startup info into the Terminal now, but I'm reluctant to change the behavior where defterm filters out start /min cli-app.exe invocations. start /min wt cli-app.exe will work, and start /max cli-app.exe will both launch into the terminal, and start /min cli-app.exe will open a minimized conhost running cli-app.exe.


ci: add dockerfile for new pytorch versions

#652, as discussed with lightning team

1.12 & 1.11 need further verified

Verified: 1.13, 1.9

@NOBLES5E   have tested these dockerfiles on local nodes (with bytegrad/mnist benchmark passed), could you please take a look and help me merge this PR?

update lib path for the following error:
>>> import torch
>>> torch.cuda.device_count()
/opt/conda/lib/python3.8/site-packages/torch/cuda/__init__.py:82: UserWarning: CUDA initialization: Unexpected error from cudaGetDeviceCount(). Did you run some cuda functions before calling NumCudaDevices() that might have already set an error? Error 34: CUDA driver is a stub library (Triggered internally at  /opt/conda/conda-bld/pytorch_1646755903507/work/c10/cuda/CUDAFunctions.cpp:112.)
  return torch._C._cuda_getDeviceCount() > 0
0


Can't compile juniper_actix project.

Describe the bug
While I m trying to build project I m getting below error
 no variant or associated item named `__Nonexhaustive` found for enum `syn::Type` in the current scope
   --> juniper_codegen/src/common/parse/mod.rs:199:18

To Reproduce
Steps to reproduce the behavior:
(code example preferred)
Clone the latest code and try cargo build in juniper_actix folder.
Expected behavior
A clear and concise description of what you expected to happen.
It should build without errors.
Additional context
Add any other context about the problem here.
Getting similar issue in project while pointing to git repo in cargo file.

UPDATE: This commit 4f3939075a9e6c0da8fa138591e657153f27764c is working for me.

UPDATE: This commit 4f3939075a9e6c0da8fa138591e657153f27764c is working for me.

Looks like this might be caused by the syn 1.0.60 release, it just broke for me in a daily CI run that ran fine yesterday.

Looks like this might be caused by the syn 1.0.60 release, it just broke for me in a daily CI run that ran fine yesterday.

And it blocked my Custom Scalar implementations. As it is in latest code. I guess I have to disturb Juniper Gods now.
@trevyn @LegNeato  and others. Need some help over here.

And it blocked my Custom Scalar implementations. As it is in latest code. I guess I have to disturb Juniper Gods now.
@trevyn @LegNeato  and others. Need some help over here.

Thanks @obmarg for quick PR.

Thanks @obmarg for quick PR.

I already posted this on the PR, but I figured it might be useful here too!
For now this can be worked around by adding an explicit dependency to syn = "=1.0.59" in your Cargo.toml.
[dependencies]
actix-web = "3.3"
juniper = "0.15.2"
syn = "=1.0.59"

I already posted this on the PR, but I figured it might be useful here too!
For now this can be worked around by adding an explicit dependency to syn = "=1.0.59" in your Cargo.toml.
[dependencies]
actix-web = "3.3"
juniper = "0.15.2"
syn = "=1.0.59"

@Binero It did the trick. Build is working now. I am keeping the issue open until latest get merged. Hope that is OK.

@Binero It did the trick. Build is working now. I am keeping the issue open until latest get merged. Hope that is OK.


feat(enrolment-type): the enrolment type effects on views

Added enrolment type enum and external enrolment url field to PalvelutarjotinEvent.
PT-849 PT-1103.

Codecov Report

Merging #153 (64078e0) into master (2649a68) will increase coverage by 0.09%.
The diff coverage is 94.56%.

@@            Coverage Diff             @@
##           master     #153      +/-   ##
==========================================
+ Coverage   91.90%   91.99%   +0.09%
==========================================
  Files         102      103       +1
  Lines        3371     3411      +40
  Branches      601      606       +5
==========================================
+ Hits         3098     3138      +40
  Misses        270      270
  Partials        3        3

Impacted Files
Coverage Δ

...c/domain/event/occurrences/EnrolmentButtonCell.tsx
94.31% <94.31%> (ø)

...rc/common/components/externalLink/ExternalLink.tsx
100.00% <100.00%> (ø)

src/domain/event/occurrences/Occurrences.tsx
97.39% <100.00%> (+2.26%)
:arrow_up:

Continue to review full report at Codecov.

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


TreeItem::draw_item_content panics

Hi,
the following panics with 'assertion failed: self.is_derived' when calling draw_item_content:
use fltk::{app, prelude::*, window::Window, tree::*};

fn main() {
    let app = app::App::default();
    let mut wind = Window::new(100, 100, 400, 300, "Hello from rust");
    let mut tree = Tree::new(0,0,400,300, None);
    let mut item = tree.add("foo/bar").unwrap();

    item.draw_item_content(|_item, _render| 0);

    wind.end();
    wind.show();
    app.run().unwrap();
}

Is there something wrong with this code?

TreeItem’s that can draw are specially built to do so. The default item’s generated by add don’t support it.
You would use TreeItem::new(), set the draw_item_content callback then Tree::add_item().
A sample code can be found here:
https://docs.rs/fltk/latest/fltk/tree/struct.TreeItem.html#method.draw_item_content


How to get datasets with var,med and max noise?

Hi,
I tried to download ABC and Famous datastes and got vesion of original,free,and extra noise . It seems theres only one noisy datasets. Now I want to get datasets(or test datasets) with different levels of noise.Could you please provided them to me？Thanks！Looking forward to your reply.

ABC original is just called var-noise in the paper. It has the same settings as the ABC training set with random noise strength.

Thanks a lot. I checked ABC test again: abc,abc_extra_noisy and abs_noisefree. I am no sure whether one of them is max noise vesion of 0.05L.

Hello, I have my own building point cloud dataset in the format *.ply, what should I do about it that can be used for network training @ErlerPhilipp

Hi @Hxinyue,
please see this section in the readme: https://github.com/ErlerPhilipp/points2surf#dataset-from-point-clouds-for-reconstruction
Let me know if there are any problems.

Hello, I downloaded a building point cloud data set with the file format of *. ply, such as building_ 01.ply is a point cloud file of a single building. What should I do to use it in network training or final generation? Because there may be many things I don't understand when I first came into contact with this aspect. I look forward to your reply and answer.
------------------ 原始邮件 ------------------
发件人: "Philipp @.>;
发送时间: 2023年2月4日(星期六) 晚上6:43
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [ErlerPhilipp/points2surf] How to get datasets with var,med and max noise? (Issue #26)
你好@心悦,
请参阅自述文件中的这一部分：https://github.com/ErlerPhilipp/points2surf#dataset-from-point-clouds-for-reconstruction
如果有什么问题告诉我。
—
直接回复此邮件，在GitHub上查看或取消订阅.
你收到这个是因为你被提到了。消息ID：<ErlerPhilipp/观点2 @.***与>.

Training is only possible if you can provide ground-truth meshes. We need the meshes to calculate ground-truth signed distances for supervised training.
Assuming you mean reconstruction with final generation, please see my answer in your new issue. You need to choose a pre-trained model (e.g. max-model), create a new point cloud dataset and run a modified evaluation script.


PG federated server setup

This branch adds a new function CDB_SetUp_PG_Federated_Server that can be used like this:
SELECT cartodb.CDB_SetUp_PG_Federated_Server('amazon', '{
   "server": {
     "dbname": "testdb",
     "host": "myhostname.us-east-2.rds.amazonaws.com",
     "port": "5432"
   },
   "credentials": {
     "username": "read_only_user",
     "password": "secret"
   }
}');

As a bonus it has a small refactor of tests, extracting some common setup and teardown from FDW tests.

This other PR is a superset of this one: https://github.com/CartoDB/cartodb-postgresql/pull/373

Closing in favor of https://github.com/CartoDB/cartodb-postgresql/pull/373


Volumes_from data are different in the containers

I want to create a stack with Taiga.io I followed the instructions of https://hub.docker.com/r/htdvisser/taiga-back/ in docker hub. The stack, have 4 containers:

Taiga Back, is the backoffice of the app. Wrote in Python.
Taiga Front, the angular app to show the app
Postgres, the database.
Data, a simple container with a filesystem to share static files and user's files.

I wrote the docker-compose.yml and I ran the stack in my PC.
docker-compose.yml
data:
  image: tianon/true
  volumes:
    - /var/lib/postgresql/data
    - /usr/local/taiga/media
    - /usr/local/taiga/static
    - /usr/local/taiga/logs
db:
  image: postgres
  environment:
    POSTGRES_USER: taiga
    POSTGRES_PASSWORD: password
  volumes_from:
    - data
taigaback:
  image: htdvisser/taiga-back:stable
  hostname: dev.example.com
  environment:
    SECRET_KEY: examplesecretkey
    EMAIL_USE_TLS: True
    EMAIL_HOST: smtp.gmail.com
    EMAIL_PORT: 587
    EMAIL_HOST_USER<EMAIL_ADDRESS>    EMAIL_HOST_PASSWORD: yourpassword
  links:
    - db:postgres
  volumes_from:
    - data
taigafront:
  image: htdvisser/taiga-front-dist:stable
  hostname: dev.example.com
  links:
    - taigaback
  volumes_from:
    - data
  ports:
    - <IP_ADDRESS>:80:80

I checked that run all containers and I created a example project. Is all ok.
I created the rancher-compose file to upload my app. The process was well, but Rancher has created a data container for the other three but the containers did not have the same content
docker-compose.yml
postgres:
  environment:
    POSTGRES_PASSWORD: password
    POSTGRES_USER: taiga
  labels:
    io.rancher.sidekicks: data
  image: postgres
  volumes_from:
  - data
data:
  tty: true
  image: busybox:latest
  volumes:
  - /usr/local/taiga/logs
  - /usr/local/taiga/media
  - /usr/local/taiga/static
  - /var/lib/postgresql/data
taigafront:
  ports:
  - 85:80/tcp
  domainname: deploymentbox.com:85
  hostname: canonale
  image: htdvisser/taiga-front-dist:stable
  links:
  - taigaback:taigaback
  volumes_from:
  - data
  labels:
    io.rancher.sidekicks: data
taigaback:
  environment:
    EMAIL_HOST: mail.gmail.com
    EMAIL_HOST_PASSWORD: passw
    EMAIL_HOST_USER<EMAIL_ADDRESS>    EMAIL_PORT: '587'
    EMAIL_USE_TLS: 'True'
    SECRET_KEY: wonyu9ketZab
  domainname: deploymentbox.com:85
  labels:
    io.rancher.sidekicks: data
  hostname: canonale
  image: htdvisser/taiga-back:stable
  links:
  - postgres
  volumes_from:
  - data

rancher-compose
postgres:
  scale: 1
data:
  scale: 1
taigafront:
  scale: 1
taigaback:
  scale: 1

I tried to change the io.rancher.sidekicks labels and to join it all in one but  not ran

Can you post a screenshot of the running containers? (Or docker ps results)

By adding a sidekick label, you're essentially asking the service with a label to become a primary service and all sidekicks are secondary services. They are launched together and independently.
In your case to link everything to the single data container, the easiest solution is to make the container the primary service and the services as sidekicks.
The sidekick label asks Rancher to launch all containers together so if you want to share the data container, this will need to be the primary service. This is a great use case and I will add it to the documentation.
Also, please note that there was an issue with linking containers with sidekicks that was fixed in v0.37.1. I'd recommend upgrading your setup to that version.
postgres:
  environment:
    POSTGRES_PASSWORD: password
    POSTGRES_USER: taiga
  image: postgres
  volumes_from:
  - data
data:
  tty: true
  image: busybox:latest
  labels:
    io.rancher.sidekicks: postgres, taigafront, taigaback
  volumes:
  - /usr/local/taiga/logs
  - /usr/local/taiga/media
  - /usr/local/taiga/static
  - /var/lib/postgresql/data
taigafront:
  ports:
  - 85:80/tcp
  domainname: deploymentbox.com:85
  hostname: canonale
  image: htdvisser/taiga-front-dist:stable
  links:
  - taigaback:taigaback
  volumes_from:
  - data
taigaback:
  environment:
    EMAIL_HOST: mail.gmail.com
    EMAIL_HOST_PASSWORD: passw
    EMAIL_HOST_USER<EMAIL_ADDRESS>    EMAIL_PORT: '587'
    EMAIL_USE_TLS: 'True'
    SECRET_KEY: wonyu9ketZab
  domainname: deploymentbox.com:85
  hostname: canonale
  image: htdvisser/taiga-back:stable
  links:
  - postgres
  volumes_from:
  - data

@deniseschannon
Same use case in #2032. I think make data only container the primary service wouldn't work with loadbalancers?
In this example taigafront should be added to LB, but it's not a primary service.

@pwFoo I believe you just need to make one of the services the primary config. For example, if taigafront needs to be added to a LB, then it should be the container that has all the sidekick labels. Note: I haven't tested using a sidekicked service as a target service, so just going off of what makes sense.
The sidekick label is just telling Rancher that all these services need to be deployed together on 1 host and as 1 unit, so if you scale up the service, then all of the services would be scaled together.

But I will have two primary services :)

When using load balancers with services that have sidekicks, you need to use the primary service as
the target of the load balancer. A sidekick can not be the target.

For example:
Service 1: Apache (80/tcp)  <- needs to be primary because of LB
Service 2: SSH (22/tcp)  <- needs to be primary because of LB
Service 3: Storage (data only container, shared by Apache & SSH)

I updated rancher to 0.37.1 version (CATTLE_RANCHER_SERVER_IMAGE=v0.37.1) and I regenerated the container.
I tried to load this docker-compose.yml
postgres:
  environment:
    POSTGRES_PASSWORD: password
    POSTGRES_USER: taiga
  image: postgres
  volumes_from:
  - data
data:
  tty: true
  image: busybox:latest
  labels:
    io.rancher.sidekicks: postgres, taigafront, taigaback
  volumes:
  - /usr/local/taiga/logs
  - /usr/local/taiga/media
  - /usr/local/taiga/static
  - /var/lib/postgresql/data
taigafront:
  ports:
  - 85:80/tcp
  domainname: deploymentbox.com:85
  hostname: canonale
  image: htdvisser/taiga-front-dist:stable
  links:
  - taigaback:taigaback
  volumes_from:
  - data
taigaback:
  environment:
    EMAIL_HOST: mail.gmail.com
    EMAIL_HOST_PASSWORD: passw
    EMAIL_HOST_USER<EMAIL_ADDRESS>    EMAIL_PORT: '587'
    EMAIL_USE_TLS: 'True'
    SECRET_KEY: wonyu9ketZab
  domainname: deploymentbox.com:85
  hostname: canonale
  image: htdvisser/taiga-back:stable
  links:
  - postgres
  volumes_from:
  - data

The system not run. Taigafront container attempts to boot, 15 or 20 minutes after, the container is green. It is like all is ok but the app not run. This is the log

17/9/2015 8:55:392015/09/17 16:55:39 [emerg] 12#0: no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:55:39nginx: [emerg] no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:55:472015/09/17 16:55:47 [emerg] 13#0: no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:55:47nginx: [emerg] no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:56:032015/09/17 16:56:03 [emerg] 10#0: no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:56:03nginx: [emerg] no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:56:072015/09/17 16:56:07 [emerg] 10#0: no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:56:07nginx: [emerg] no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:56:232015/09/17 16:56:23 [emerg] 17#0: no host in upstream ":8000" in /etc/nginx/upstream.conf:3
17/9/2015 8:56:23nginx: [emerg] no host in upstream ":8000" in /etc/nginx/upstream.conf:3

In a few minutes, taigafront container is red one more time

Hi @canonale
I think your image image: tianon/true will be exiting because of a command true?
Docker data only container shouldn't run. So it should be fine with a stopped data container?
Example from docker docs:
docker create -v /dbdata --name dbdata training/postgres /bin/true

After executed / created it will be in stopped state and used via volumes-from.

Hello @pwFoo.
I tried it with tianon/true but is not correct. I replaced it for busybox:latest
With docker-compose the stack is run

@canonale I'm not exactly sure how your service is supposed to be configured, but the logs indicate it's something wrong in the stack configuration.
Maybe some port needs to be exposed between the images?

One thing to note, is that you can re-use the same data container by making the service 1 the primary container (with the labels for sidekicks) and the data container and service 2 sidekicks. This is instead of making the data container the primary one.
Example:
test-data:
  tty: true
  command:
  - cat
  image: ubuntu:14.04.2
  stdin_open: true
test1:
  tty: true
  image: ubuntu:14.04.2
  stdin_open: true
  labels:
    io.rancher.sidekicks: test-data, test2
  volumes_from:
  - test-data
test2:
  tty: true
  image: ubuntu:14.04.2
  stdin_open: true
  volumes_from:
  - test-data

But based on this issue, it sounds like it's a stack configuration issue and not a Rancher issue so I'm going to close it.


Update Github actions and add automatic updates

Update Github actions to their latest versions
setup Dependabot to automatically create PRs with GH actions version bumps

Update Github actions to their latest versions

Are there features or bugfixes that we need in these new versions? It just seems like we're pulling in the latest version for no reason. There are API changes for some of these (like setup-go does caching by default) that I think require more analysis.

setup Dependabot to automatically create PRs with GH actions version bumps

I'm not in favor of pulling in new deps just because they exist. I could be convinced to adopt a configuration that suggests updates for dependencies that have security fixes, but randomly pulling in the latest dependencies from the Internet is bad.


Correct how the all endpoint is specified (or remove it completely from the specs)

What does the /all endpoint presently return?
Without a filter it should return all entries of all entry types, using the jsonapi 'type' member to specify which entry_type each record is.
So, e.g.,
   /all?filter=id="_exmpl_42"

Looks for any entry in the database with the id _exmpl_42, regardless of which type it is.

I don't see a major reason to duplicate functionality between the all endpoint and just using an endpoint that specifies entry type, e.g.,
/structures/?filter=chemical_formula="H2O"
So, my suggestion is to go with specifying an All entry type for all records in the database and return this.

Old attempt at specification (new one in first comment):
What does the /all endpoint presently return?
Two alternatives have been proposed to resolve this problem.

"All" entry types which encompass all data in the database. The All entry type would then only have the
following properties:

Id                      (e.g., "exmpl_42")
creation_date   (e.g., "2018-06-14")
entry_type        (e.g., "structure")

One must specify and entry type, e.g.:
/all?filter=id="_exmpl_42";entry="structures"

This would then return a structure type entry.

One could also consider allowing both, i.e., all entry type if no entry type is specified.

Approved as specified in top issue description.

We're discussing now at the Optimade meeting that maybe, if we are not sure how the /all endpoint should be used, we should just remove this from the specs for now.


Searching in Swift?

Hi,
Been trying to get search to work in Swift. I've spent the last week or so figuring out how to scrape a lot of HTML and have about 220,000 documents in Lucene. Searching with Java works really well. Exactly what I need.
Now I'm trying to bring it to iOS with Swift. I've got the framework set up correctly, and the CLuceneSearchService class initializes fine.
func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {

        searchService = CLuceneSearchService(indexPath:  NSBundle.mainBundle().resourcePath!.stringByAppendingString("/LuceneIndexes"))
        if (searchService as BRSearchService?) == nil {
            print("unable to intialize search database")
        }

        let results:BRSearchResults = searchService.search("piano")
        NSLog("Results: %i", results.count())

        return true
    }

When this code runs, it always returns 0. I'm not sure if:

CLuceneSearchService isn't actually reading the imported indexes (I've checked that the path is correct and files are recognized to already exist)... How do I check how many documents CLuceneSearchService is looking at? IndexReader doesn't seem to be available?
If I need to recreate the indexes with iOS code and not Java code--although I thought the whole point was it wouldn't matter

Any pointers on why this isn't working? The term "piano" should hit many terms (134 hits in the Java code).
Thanks
p.s. Here's the Java code for the search:
public static void searchIndex(String searchString) throws IOException, ParseException {
        System.out.println("Searching for '" + searchString + "'");
        Directory directory = FSDirectory.getDirectory(INDEX_DIRECTORY);
        IndexReader indexReader = IndexReader.open(directory);
        IndexSearcher indexSearcher = new IndexSearcher(indexReader);

        Analyzer analyzer = new StopAnalyzer();

        QueryParser queryParser = new QueryParser(JSON_WORD_SEARCH, analyzer);
        Query query = queryParser.parse(searchString);
        Hits hits = indexSearcher.search(query);
        System.out.println("Number of hits: " + hits.length());

        Iterator<Hit> it = hits.iterator();
        while (it.hasNext()) {
            Hit hit = it.next();
            org.apache.lucene.document.Document document = hit.getDocument();
            String path = document.get(JSON_WORD_DISPLAY);
            System.out.println("Hit: " + path);
        }

    }

Ok--I think it has to do with the default field names that BRFullTextSearch has set. There's no easy way to change this if using CocoaPods--will recompile with a dependent project and use my own field keys and see if that'll work.

The problem actually was that the built-in search code was using the wrong analyzer. It seems really weird that I have to full-on edit the Framework to change these settings. Can they be changed anywhere in my code and leave the library as-is? The snowball analyzer is hard-coded into [CLuceneSearchService defaultAnalyzer] and search: has defaultAnalyzer: hard-coded in, so I'm guessing that it's not yet implemented. I propose these become settings that can be readily changed.
Once I changed this method to what I have here:
- (std::auto_ptr<Analyzer>)analyzerForLanguage:(NSString *)lang {
    std::auto_ptr<Analyzer> stopanalysis(new lucene::analysis::StopAnalyzer());
    return stopanalysis;

it worked perfectly. I also had to change the field keys. That seems like something that should be a no-brainer.
I do get that Lucene and BRFullTextSearch was built to used to both create and search documents. Creating an index from elsewhere and importing it into a project wasn't the first consideration--so I understand these design choices.

Hi @keehun,
Some parts of this API have not been exposed for extensibility or configurability yet, as you have discovered. This is more from time constraints rather than oversight. In your case, the defaultAnalyzer method can be overridden by subclassing CLuceneSearchService to return the Analyzer instance you'd like to use.
The generalTextFields internal array should be a configurable property on CLuceneSearchService, but as a work-around you can avoid using kBRSearchFieldNameTitle or kBRSearchFieldNameValue field keys in your BRIndexable implementations.
Thanks for your feedback!

@keehun I forgot to also mention, you can set
@property (nonatomic, getter=isStemmingDisabled) BOOL stemmingDisabled;

to YES to turn off stemming, which makes the Analyzer more similar to using a plain StopAnalyzer, that is a StandardTokenizer along with a LowercaseFilter and StopFilter.


此项目还在维护吗 好久没更新了

此项目还在维护吗 貌似好久没更新了
Hi ,Is this project still under maintenance? It seems that it hasn't been updated for a long time

Closing in favor of #1365


Allow polyfilling imperatively for a single style element

Description
This change provides an alternative way for authors to apply polyfill: instead of letting the polyfill to lookup stylesheets and
apply the polyfill, the second argument takes a <style> element and the function can apply polyfill based on its content.
This is particularly useful for components like custom elements, as often the stylesheets are added dynamically to the document, and the currently "auto" polyfilling makes it challenging to apply the changes at the right time.
Related Issue(s)
https://github.com/oddbird/css-anchor-positioning/issues/228

I'm okay with this approach. I wonder if we want to accept an array of elements, and we could also support <link> tags as well as <style>? Basically using the same functionality as the existing polyfill, but allowing users to opt into a specified list of CSS sources.

I think an array that supports <link> tags as well as <style> makes a lot of sense.
This does omit inline styles- could we add another boolean flag includeInline that defaults to true, and then adds the response of fetch:fetchInlineStyles()? Or since the inline style impact is scoped to just ones that include anchor, should we just always add the inline styles?
It would be nice to have a demo, but that's a bit of a challenge in the existing single page setup.

Thanks for the comments. I'll add them in.

I think an array that supports  tags as well as

I updated the code and it's ready for review:

Changed the argument of polyfill() to accept an object for configuration, with backward compatibility
You can pass in an array of elements for polyfilling, and imperative polyfill uses the same functions as auto polyfill
Added demo and tests

Also, maybe I should rename "imperative" to "manual"? Let me know if "manual" sounds better and less confusing.

Is it a legitimate use case for people to pass in explicit

Added includeInlineStyles: https://github.com/oddbird/css-anchor-positioning/pull/256/commits/798561f9dbe8d38ac5c740d3fb3aaafd2de0b0b3

Is it a legitimate use case for people to pass in explicit

If you click the imperative button, and then apply the polyfill to the whole page, the polyfill crashes. This is somewhat related to [BUG] Polyfill fails if a <link> fails to load or returns non-CSS content #255 as well as applying the polyfill to dynamic elements #91, so I'm not concerned here.

I'm seeing this too. I think it relates to #253, as the error I see seems to be when the polyfill tries to fetch the already-polyfilled style:
Security Error: Content at http://localhost:3000/ may not load data from blob:http://localhost:3000/8749e98f-f55a-4153-9249-f6bba301e298.

I'm not sure if there's an easy way to read/fetch a blob url, or whether we should explicitly just skip those links?

If you click the imperative button, and then apply the polyfill to the whole page, the polyfill crashes. This is somewhat related to [BUG] Polyfill fails if a <link> fails to load or returns non-CSS content #255 as well as applying the polyfill to dynamic elements #91, so I'm not concerned here.

I'm seeing this too. I think it relates to #253, as the error I see seems to be when the polyfill tries to fetch the already-polyfilled style:
Security Error: Content at http://localhost:3000/ may not load data from blob:http://localhost:3000/8749e98f-f55a-4153-9249-f6bba301e298.

I'm not sure if there's an easy way to read/fetch a blob url, or whether we should explicitly just skip those links?

Not quite a fix but this would at least let other styles being polyfilled:
try {
  // fetch css and add to array
  const response = await fetch(data.url.toString());
  const css = await response.text();
  return { ...data, css } as StyleData;
} catch {
  return { ...data, css: ''} as StyleData;
}

@jamesnw  @jgerigmeyer Thanks for the reviews, both. Have addressed all comments. Ready for another round :)

This works great! @marchbox I opened PR #259 to update the docs with the new configuration options- I'd appreciate your eyes on that to make sure it makes sense. Thanks!

Thank you! Will take a look at the documentation changes today.


Support for Take Sreenshot Options

Hi, right now the supported arguments for the Take Screenshot keyword are: filename, selector, fullPage.
It would be very useful to support some of the other arguments present in the Node.js version of playwright, specifically:

quality  The quality of the image, between 0-100. Not applicable to png images.
type <"png"|"jpeg"> Specify screenshot type, defaults to png.

Also, at the moment the keyword sometimes throws page.screenshot: Timeout 10000ms exceeded for big fullPage screenshots (I think because processing time), so maybe the timeout argument could be useful too.

timeout  Maximum time in milliseconds, defaults to 30 seconds, pass 0 to disable timeout. The default value can be changed by using the browserContext.setDefaultTimeout(timeout) or page.setDefaultTimeout(timeout) methods.

Link To Playwright API

@all-contributions please add vincenzo-gasparo for code.

@vincenzo-gasparo awesome work! Would like those enums also as Robot Framework will automatically typecheck strings from enums. But that can be another PR. This one is merged.

@all-contributors please add vincenzo-gasparo for code

@all-contributors please add vincenzo-gasparo for code

Wtf @all-contributors, please autofix your bugs!!!


Improving Contribution and Code Style docs

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
After going around in search of a doc on a Code Style adopted in the Pydantic code base I have some suggestions to make.

[ ] Have a link from pydantic.dev to the Contributing to pydantic doc. There could be a section of useful links at the bottom of the page with that link being one of them.
[ ] Update outdated make format doc in the ``. We use ruff instead of isort now.
[ ] Provide a Code Style policy for the entire code base in a separate section in contributing.md or in a separate doc file.
[ ] Specify an import organization policy in the Code Style doc. Consider for example imports in _internal/_validators.py. There are direct imports from typing and at the same type typing is imported as a module.
[ ] Maybe come up with some thing like import pydantic_core as core in the Code Style policy that should simplify the code while still providing an explicit namespace for the pydantic_core code.
[ ] Define the policy on quotes being used to define string literals. There is already skip_string_normalization=true defined for black. I suggest using ' for magic constants like dict keys, env var names, etc and " for human readable strings like console and error messages, logs, etc.

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Only some points from this issue are good for a first issue. I suggest working on those things separately creating new issues and referencing those here.

Should we close this, or what is relevant here? @lig

Hey @lig, I'd like to work on this issue.
Thank you

cc: @dmontagu @samuelcolvin

Going to close this for now. We've added some more docs on core schemas, which I think help to contextualize things for devs.
Additionally, our adherence to pre-commit checks somewhat self-enforces code style + import styles, so there's no point in us explicitly writing out all of these rules.
I would say, pre-pycon or any other sprints, it'd be worth revisiting optimizing the startup time with contributing + collecting a few good first issues to have ready.


Add Hanno Becker to GitHub

Please include Hanno Becker (AWS) in the PQCP org. He is going to join as maintainer of https://github.com/pq-code-package/mlkem-c-aarch64.
If you want to be able to assign bugs to someone, they only need Read access.
Please include:

GitHub ID to add: https://github.com/hanno-becker
Project to be added to: mlkem-c-aarch64

One of:

Team to be added to:

https://github.com/orgs/pq-code-package/teams/pqcp-embedded-maintainers-aarch64

Role:

Manage

See https://github.com/pq-code-package/tsc/pull/47#issuecomment-2097693415

I would like to self nominate becoming a member of this TSC. I would like to focus on areas related testing.

I would like to self nominate becoming a member of this TSC. I would like to focus on areas related testing.

could you file a PR, like #47 ?

I would like to self nominate becoming a member of this TSC. I would like to focus on areas related testing.

could you file a PR, like #47 ?

Seems like i can't/dont know how to create a branch nor PR. I can only create a fork.
So, maybe just add an issue? Or ask at the meeting tomorrow?


Regenerate SDK based on Pulumi v3 sdk/pkg

self merging - tests look good - linting error is due to unused go sdk funcs


Formal equiv diff ParameterInGenScopeInitializedWithLongConstant_top.sv

Test UHDM-integration-tests/tests/ParameterInGenScopeInitializedWithLongConstant/top.sv
./run_formal_verif.sh test=ParameterInGenScopeInitializedWithLongConstant_top.sv
The plugin AST is drastically different from the Yosys AST.
UHDM contains the correct representation of the gererate stmt and the parameter value.

ParameterInGenScopeInitializedWithLongConstant test now passes formal verification. Closing issue.


Issue while using shadcn-ui with React CRA

I'm trying to use a shadcn-ui component in my react app using CRA with typescript and tailwind CSS.
Below i have added the primary parts of the code.
tailwind.config.js
content: [     './pages/**/*.{ts,tsx}',     './components/**/*.{ts,tsx}',     './app/**/*.{ts,tsx}',     './src/**/*.{ts,tsx}',   ],
tsconfig.json
[{ "baseUrl": ".",     "paths": {       "@/*": ["./src/*"]     }   },   "include": [     "src",     "**/*.ts",     "**/*.tsx"   ]
components.json
{   "$schema": "https://ui.shadcn.com/schema.json",   "style": "default",   "rsc": false,   "tsx": true,   "tailwind": {     "config": "tailwind.config.js",     "css": "src/index.css",     "baseColor": "slate",     "cssVariables": true,     "prefix": ""   },   "aliases": {     "components": "@/components",     "utils": "@/lib/utils"   } }
usage
import { Button } from '@/components/ui/button'
Here is the folder structure

Error
Module not found: Error: Can't resolve '@/components/ui/button'

Use Path in tsconfig.json "paths": {       "@/*": ["./src/*"]     }

Use Path in tsconfig.json "paths": { "@/*": ["./src/*"] }

I've used it, please check the code I provided

You'd need to install and setup tsconfig paths with craco. Which means you'll have to eject your create-react-app setup. Personally, I'd advise you use Vite instead. Then you won't have this problem

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Fix out of bound enum conversion

This PR fixes Wenum-constexpr-conversion which is introduced in recent version of clang. Explciitly use integer instead of enum to store the device that may contain invalid options.

cc @Wheest background https://discuss.tvm.apache.org/t/tvm-web-build-error-and-unrecognised-target/14324

cc @Wheest background https://discuss.tvm.apache.org/t/tvm-web-build-error-and-unrecognised-target/14324

Cheers, pulling this PR allows me to run make in web/ without the error being triggered.


Verbose stops recording/reporting checks

Description

Verbose logging on fabric stops working completely all of a sudden after some arbitrary amount of time, in the order of seconds to minutes.
Reproduction steps

Install LP on fabric and enable verbose.
Wait for some arbitrary amount of time and do things that require permissions, no results yield.

Expected behaviour

Well it should keep reporting :full_moon_with_face:
Environment details

Server type/version<EMAIL_ADDRESS>-<EMAIL_ADDRESS>LuckPerms version: v5.2.90

Any other relevant details

Just an example, the first //wand reported fine, I waited a few minutes and it stopped working.

Sadly there aren't as many details I'd like to have in hand to report this other than "it doesn't work" :smile: but it happens with any check, including LP's own checks (most noticeably tab completion since it happens as you type).
This issue seems to be fabric specific, I can't seem to repro on any other platform (I have access to).

Thanks for reporting :)

Thanks for reporting :)


epiphany: 40.2 -> 40.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for epiphany is: "WebKit based web browser for GNOME"
meta.homepage for epiphany is: "https://wiki.gnome.org/Apps/Epiphany"
meta.changelog for epiphany is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3/bin/epiphany passed the binary check.

/nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3/bin/.epiphany-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 40.3 with grep in /nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3

found 40.3 in filename of file in /nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3

directory tree listing: https://gist.github.com/7eeca8f30bc2cc26862e82b3fb98e636

du listing: https://gist.github.com/00dc1860b0822166dea599d899b792ae

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
epiphany
gnome.epiphany
pantheon.elementary-gsettings-schemas

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A epiphany https://github.com/r-ryantm/nixpkgs/archive/271e13f9624caf0130ddeaa30d5bfb7b427f6ec5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3
ls -la /nix/store/nv3l7wqnbxigx6qvlcci1pf01byfdhb2-epiphany-40.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

epiphany
pantheon.elementary-gsettings-schemas

Maintainer pings
cc @hedning @jtojnar @dasj19 @maxeaubrey for testing.

Changes look okay:

40.3 - August 12, 2021

Use PDF.js only for GET requests (#1505)
Use AdGuard script to block YouTube ads (#1534)
Manually check adblock filter content type (#1543)
Fix UI process CPU usage issue (#1560)
Don't improperly lowercase bang searches (!988, Vanadiae)


refactor(ts): enable noImplicitAny on index.ts

Fixes #427 (1/21 files) :)

[x] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

@JustinBeckwith @callmehiphop Sounds good - I'll get npm run fix working properly,  I'll refine index.ts, and I'll submit a PR for something a bit more foundational. Thanks for taking the time to double-team this :)

This has sat dormont for a while, and I think its the last thing that should land.  I'm closing this PR out for now, but keeping the branch around.


Update jshint file and fix jshint errors

Also updated packages.

Coverage decreased (-0.08%) to 94.101% when pulling 645f1b8e51c2716efcda2f2ab20e335e1c281e3e on jshint into 223b7077b3dbfc91e39a3f551fef21ce68003a65 on master.

jsHint and tests pass, this looks good to me.


Blue-on-black text is hard to read

When editing a QSO, the changed fields change from white text on a dark gray background to dark blue text on a dark gray background.  The latter is really hard to read, and since it happens as soon as a single character is changed, it's hard to verify that you're tying the correct value.

Agreed. I was playing around with Angular Material dark theme, but it needs more work. aab15cbd66201785b6fce33822da1f4bb50636ad
Ideally I'd like to make the theme switchable between light and dark.


Upgrade disorder -> ambiata-disorder

Noticed that this was still on the old name for disorder when I did the EitherT change.
This also upgrades p to the latest.

:+1: on :green_apple:


Server list and main message place now left with discord grey

I think due to a discord update, first the server list on the right stopped following the wal colors, then now the main message place too, in the middle. They both have plain old discord grey. I tried looking up if I could see if they changed something but didn't end up understanding much. I'll see if I can find something on my own tinkering a bit.

Yeah, I'm getting it too, working on a fix right now. Should be done soon.

thank you, nice job, updated and works


[add] codeQL for releases done on main.

CodeQL will be added in a different PR that targets the dev branch.