Daz to UE5 Crash

Reported to Daz Support - after a couple of go arounds they tell me that Daz Support does not support the Bridge plugin. Told me to got to the Daz github. Hope this is the right place. Here's where the issue stands
daz to ue bridge is crashing with the following exception -
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll" at 0033:0000000072293A64, QIODevice::isTextModeEnabled()+4 byte(s)
I am running the latest version of the bridge from David's site v<IP_ADDRESS> (both the UE and DAZ side with manual installs) My gpus are rtx 3080s running latest nvidia studio driver (5.26.98 11/16/22)
After the crash the .dtu .fbx and .csv files are created but the .dtu is zero bytes and the .csv file has no data only headers. I'm attaching my test files. Can't send the .dtu because it's zero byte but I did open it in visual studio and it is empty.
second post- after the boilerplate reinstall suggestion.
I have installed the latest ,dll (dzunrealbridge.dll.v2<IP_ADDRESS>.zip)
and unreal parts of the plugin. I have done both a manual install and an install from within the popup in daz. Both types of install result in a failure as described (see original). I've done another complete reload and reinstall - same results as originally reported.
Update
Tried rolling back nvidia driver to previous versions - no help
I'll include the full crash report with this.
I've included the full crash report.
Thnaks
BD
DAZStudio_error_report_221201-060009.zip

Confirmed that DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll" at 0033:0000000072293A64, QIODevice::isTextModeEnabled()+4 byte(s) is directly related to "Export Material CSV" checkbox enabled.  Please verify if crash occurs or does not occur when "Export Material CSV" is unchecked.  Thanks

Daniel
Looks like that is the problem. I am able to export from DAZ and import into UE 5.1 with box unchecked.
BD

Thanks for confirmation.  CSV crashfix will be included in the next update (mid-January).

Hi.
I am also having this issue. I am using 4.27.
I get the same QtCore4.dll error message. Can also confirm that unchecking Export csv avoid the issue.
Is there a fix for this yet?
Thanks


How to use a debugger like Intellij with YCSB.

I am unable to edit configurations and run Intellij on YCSB. Is any debugger suggested. Its very difficult to go through the code without a debugger.

What's the specific problem you run into when trying to use intellij?

I don't know what edit configurations are as it says no main class specified. Can you tell me procedure to debug YCSB with Intellij


Extensions update not working

Source information
Bato.to
Source language
English
Steps to reproduce
Just appeared on my extendions to be updated list
Expected behavior
Should update and removed from the list
Actual behavior
Try updating but dont finish and keeps on the list
Tachiyomi version
0.15,3
Android version
11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.14.7.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

I have the same issue

I have the same problem but it's every extension.
The only solution I've found is uninstalling the extension and reinstalling it.
This happens for EVERY update for every extension in this repo.


[Fix bug 1262166] Retire custom_update_phonebook basket api call.

Coverage increased (+0.02%) to 92.558% when pulling e75f057f31b6ae000b0bae456131b3657b4d4047 on johngian:1262166 into 5db27d78c5db43e86a1bd895ab83289d8d430545 on mozilla:master.

@akatsoulas r?

lgtm r+ :+1:


Fix Composer 2 compatibility

When installing this plugin with Composer 1, the following deprecation notice is output:

Deprecation Notice: Class cavellblood\sunsettosunset\assetbundles\SunsetToSunset\SunsetToSunsetAsset located in ./vendor/cavellblood/craft-sunset-to-sunset/src/assetbundles/sunsettosunset/SunsetToSunsetAsset.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0.

Composer 2 was released on October 24, and is now the default version that will be installed, so it’s critical that this gets resolved ASAP, or people will start getting Class not found errors.
To fix, run the following command:
> git mv src/assetbundles/sunsettosunset src/assetbundles/SunsetToSunset

Then commit your change and tag a new release.
(Note that you must use the git mv command, as Git tends to not notice case-sensitive file renames otherwise.)

Thanks @brandonkelly! Fixed in 2.1.3.


[Automation] Smithy Version Bump - 1.45.0

Automated pull request to bump Smithy version from 1.44.0 to 1.45.0

Looks like an issue with brew not being updated.


contact_groups option in _load_default_config

I noticed the default services were not getting the contact_groups value I set in the default_contact_groups attribute.
I fixed the problem by replacing default_contact_groups by contact_groups in the nagios_host and nagios_service options.

LGTM! Thanks for fixing


GPL-726 Whats of value in this LH box then?

User story
GPL-726 | As Process Improvement I would like a LIMS feature for the new cherrypicking process where Sample Management staff can scan a Lighthouse Lab box and see how many plates are in the box, as well as how many plates have metadata, in order to prevent lab staff starting to process plates that are not ready to be cherrypicked.
Who are the primary contacts for this story
Scott T (R&D)
Lesley S (R&D)
Danni W
Ian J
Acceptance criteria
To be considered successful the solution must allow:

[x] Do a quick mock up for Scott T (Proposer) & Danni W (User)
[ ] read 2D barcodes of Lighthouse boxes
[ ] list the plates in the box, indication plates with plate map data or not with tick/cross (maybe color signpost also green/red)
[ ] plates with plate map data to top panel, those with no plate map data to bottom
[ ] for each plate show the number of positives on the plate (sort plates by occupancy?) *1
[ ] display summary below panel eg  'Total of 80 plates in box; 75 plates with plates maps, 5 without'
[ ] Handle following error gracefully; a) Box barcode unknown b) Box empty
[ ] Be able to scan the contents of a plate individually (sometimes the user would want to check plates scanning them one by one to take the decision by plate)

*1 It maybe more truthful to display the number +ves that can be picked (eg not high Ct or Cambridge controls) however if this introduces significantly more work just do the positives
Dependencies
This story is blocked by the following dependencies:

#<issue_no.>
sanger/#<issue_no.>

Additional context
Assumption this woudl be new UI in http://lighthouse-ui.psd.sanger.ac.uk/, called the 'Box buster'?
This story deprecates https://github.com/sanger/lighthouse-ui/issues/31

Mock up sent to Danni Scott on 5th for feedback
GPL-726 - Whats in the box.pdf

Mockup converted into actual component (None of the interactivity in place, this is all hard-coded at the moment). Still a bit of work to get true-false reading as Yes-No as well.


questions about gt_bev_mask's generate

Great works! But I have some questions,as the picture shows,
what is the purpose of these flip and rotate operation?
why we need them?
I'm quite confused ,looking forward to the author's answer,thanks!

The result of GetBEVMask is the supervision signal for BEV Features. After cv2.fillPoly(), the coordinate system of the numpy matrix differs from that of the BEV features, requiring us to transform it to match the BEV feature coordinate system.


bpf2c_plugin doesn't support --elf argument

Describe the feature you'd like supported
The bpf_conformance_runner.exe passes --elf to the plugin if --elf is specified as an argument to bpf_conformance_runner.
However the plugin has no such option and reports an error.
Proposed solution
Implement the argument
Additional context
No response

PR #3182 upgraded bpf_conformance to 0.0.5 which resulted in this issue.


WIP: add ci workflow

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhangrenyu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add conditional::Vary

Implements the Vary header. Ref #99. Depends on #220, #224. This is actually the final conditional header, heh.
Vary takes a HeaderName as an input, so made it so it can take both header names and string literals for convenience. I think this should work reasonably well. Thanks!

The VaryDirective struct isn't needed; but that matches the rest of the directives and we can fix that in a follow-up PR.


Image alt tag accessibility fix

Similar to https://github.com/google/web-stories-wp/pull/1340, fixes #1128

Seems like this bug is #1128
Any chance you could also fix the other fields I reference in the ticket?

Closing as I'll move the changes to https://github.com/google/web-stories-wp/pull/1340


feat: form({ onChange })

This PR makes it possible to pass an onChange callback to a form construction.
This change makes it possible to override default behaviour of useGitForm:
const cms = useCMS()

useRemarkForm(node, {
  onSubmit(data) {
    return cms.api.git.writeToDisk({
      fileRelativePath: values.fileRelativePath,
      content: toMarkdown(values),
    })
  },
  onChange: null,
})

This makes it so:

The form does not write to disk onChange
Pressing Save writes to disk

Effectively disabling the "live" preview mode which causes problems for users with slow builds.

Addresses #1140

Really? Did you test it?
As far as I can tell, this is essentially a refactor

lol didn't test, just saw the description and got excited to link the issue 🤠


Add an inverse to Changed and Added filters

Allows exclusive access based on Changed or Added component, similar to With and Without.
See https://github.com/bevyengine/bevy/pull/7264#discussion_r1073382489
This is very niche, but might help squeeze out some perfs.
What solution would you like?
Add a NotChanged<T> and NotAdded<T> component that returns all entities that their Changed and Added counterparts do not return.
Am I missing something? It seems possible to discriminate based on those filters. Though it would likely require modifying the AccessSet content.
What alternative(s) have you considered?
I added a changed: Query<(), Changed<Transform>> parameter, and call !changed.contains(&entity).
Additional context

https://github.com/bevyengine/bevy/pull/7264#discussion_r1073382489

Should we consider a generic Not<>? I don't know how feasible this is though.

Should we consider a generic Not<>? I don't know how feasible this is though.

Probably would just be a simple Not<T: ReadOnlyWorldQuery> that just inverts the output on filter_fetch.

I took a stab at Not<T> in #7271, but ran into some issues I could not resolve. matches_component_set has different "negation behaviours" for With(out) and Added/Changed: for With(out), it must be negated; for Added/Changed, it must not be. If individual implementations were implemented for the four "inner" filters, Or then becomes impossible to generically negate as it's possible to mix With(out) and Added/Changed within an Or. One possible solution moving forward is to have an additional trait that defines the negation behaviour.
My implementation also had Not<Added<T>> imply With<T>, which is not a logical negation of Added<T>.

As a user-story, today I tried to do something like the following in order to filter out all the entities that had a component added in the same frame.
Query<&T, Without<Added<T>>>

I was somewhat surprised that this was not supported.

Having set-like operations defined on Query could also be useful to solve similar problems instead with run-time compositions, i.e.
fn system(
  a: Query<Entity>
  b: Query<Added<&T>
) {
  // set difference; C is the set of all entities that satisfy A but
  // with the entities that satisfy B removed
  let c: Query<Entity> = a - b;
}

NotChanged<T> and NotAdded<T> return all entities that Changed<T> and Added<T> do not.

Changed<T> and Added<T> have an implicit With<T>. Inverting their output won't change that. They'll return the entities that have a T that wasn't recently changed or added. Their inverses should not include entities matched by Without<T>.

My implementation also had Not<Added<T>> imply With<T>, which is not a logical negation of Added<T>.

This would be much clearer if Added<T> and is_added were named New<T> and is_new (which is what it means). IMO if you ask for "entities whose T is not new", it doesn't make any sense to include entities that don't even have T.
It's not the complementary set of entities, but the implied With<T> is intuitive.


[BugFix] Fix SinkIOBuffer use-after-free in execution queue

Fixes #25245
This PR does the following:

move the closing logic of SinkIOBuffer to FileSinkOpeartor::close
use atomic<bool> _is_closed to enforce calling SinkIOBuffer::close exactly once

The purpose is to keep SinkIOBuffer alive until the pipeline is being cleansed.
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

This PR is problematic for introducing block operations in the pipeline execution thread, superseded by https://github.com/StarRocks/starrocks/pull/26028


Debuggers should not debug visualstudio_py_testlauncher.py

Whenever the legacy debugger (attach TCP, PID?) or new debugger (run with debugging or attach TCP) debugs the unit tests, it will also debug visualstudio_py_testlauncher.py. Change it so that this script is not debugged.

For this it should just go into do not trace list. You can set this using setDebuggerProperty, but the patterns are not additive. This means when you call this API it will apply your filter but will remove the ones it added.
@int19h we might need to clean that code as well. As you suggested we might want to do glob patterns, and make it additive patterns.

Actually, can you try using the rules for the attach request. That should address this for the most part. If tracing is absolutely not needed then we could look at an API for this.

"rules": [
    {"path": "<extension dir path>/**", "include": false},
]

This will allow you to ignore all files in the directory.


Fix the Cookiemals Cookie bug

Fixes #6
Context: In the JSON, it said Cookiemals Cookie, which is incorrect. This pull request corrects it to just Cookiemals.

i thought i remembered fixing this but apparently not


Operator SDK Version 1.34.1 Fails to Scaffold Ansible Projects

Bug Report

What did you do?
Run The below
mkdir memcached-operator
cd memcached-operator
operator-sdk init --domain example.com --plugins ansible

What did you expect to see?
A fully scaffold project
What did you see instead? Under which circumstances?
The SDK errors
INFO[0000] Writing kustomize manifests for you to edit...
Error: failed to initialize project: unable to scaffold with "base.ansible.sdk.operatorframework.io/v1": error updating init manifests: error updating kustomization.yaml files: remove config/default/kustomization.yaml patch and vars blocks: unable to find the content to be replaced

Environment
Operator type:

/language ansible

Kubernetes cluster type:

$ operator-sdk version
operator-sdk version: "v1.34.1", commit: "edaed1e5057db0349568e0b02df3743051b54e68", kubernetes version: "1.28.0", go version: "go1.21.7", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)
Any
$ kubectl version
NA
Possible Solution

Additional context

Updating the ansible version and releasing operator-sdk did not fix this issue, since the root cause analysis seems to be incorrect. The issue is that operator-sdk pulls in a newer dependency of kubebuilder then the ansible plugin is expecting, see dep here.
If one updates this to the version that operator-sdk is running v3.13.1-0.20240119130530-7fba82c768f8, all of the tests fail with the same reason as operator-sdk does.

Same issue here:
FATA[0000] failed to initialize project: unable to scaffold with "base.ansible.sdk.operatorframework.io/v1": error updating init manifests: error updating kustomization.yaml files: remove config/default/kustomization.yaml patch and vars blocks: unable to find the content to be replaced

$ operator-sdk version
operator-sdk version: "v1.34.2", commit: "81dd3cb24b8744de03d312c1ba23bfc617044005", kubernetes version: "1.28.0", go version: "go1.21.10", GOOS: "linux", GOARCH: "amd64"

I was able to install an earlier release locally and continue. Hope this gets resolved soon though.

The root cause is fixed in 1.34.3 of the ansible-plugin
https://github.com/operator-framework/ansible-operator-plugins/releases/tag/v1.34.3

I confirm it works now on macOS with operator-sdk 1.35 and kustomize 5.4.2. Thank you very much!


Create ChatSupport.jsx

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #498
Type of change
Please mark with an X the type that applies:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactor code
[x] Documentation update
[ ] Other (mentioned in the issue number)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce them. Please also list any relevant details for your test configuration.
Test A: Describe here
Test B: Describe here (if required)
Screenshots and Videos
Please provide screenshots and videos of the changes you made.
Checklist
Please mark with an X the items that apply:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

I will work more on it


Trigger fails to compile with filter predicate (Query API)

I have an issue with filter predicate functions.
I execute a pre trigger via the .NET SDK.
The following code throws an exception:
function () {
    var item = __.request.getBody();
    __.filter(function (cat) {
        return item.categoryIds.indexOf(cat.id) > -1;
    }, { }, function (err, feed, options) { });
}

The exception:
Encountered exception while compiling Javascript. Exception = Error: Expected '}'\\r\\nSource information: line: 9, column: 6, source line:\\r\\n})();

function () { is line 1 here and item.categoryIds is an empty array [] but considering the nature of the exception this doesn't matter.
However this code works perfectly:
function () {
    var item = __.request.getBody();
    __.filter(function (cat) {
        return [].indexOf(cat.id) > -1;
    }, { }, function (err, feed, options) { });
}

Apparently using variables out of the predicate function prevents compiling also this issue happens with post triggers.
However the crazier thing is that I'm doing similar things in stored procedures and they all work perfectly.
I can make it work using queryDocuments() and the following query:
SELECT * FROM c WHERE c.type = 4 AND ARRAY_CONTAINS(' + JSON.stringify(item.categoryIds) + ', c.id)
But I believe the exception wasn't supposed to happen !

This looks like a bug.... we are investigating and will report back soon.

We've confirmed there is a bug with how scripts are serialized on our backend. We are working on the fix.


[resource manager] add template deployment sample

copy from:

https://github.com/Azure-Samples/azure-sdk-for-go-samples/blob/master/_quickstarts/deployments.go
https://github.com/Azure-Samples/resource-manager-go-template-deployment/blob/master/example.go

to: https://github.com/Azure-Samples/azure-sdk-for-go-samples/tree/master/resources

Fixed in


Add S3 ACL support.

For writes, this adds support for "x-amz-acl" headers as well as "x-amz-grant-*" headers. For reads this adds support for the ?acl endpoint. ACLs aren't actually enforced.

This is great, thanks!

A big thanks for this changeset (and moto in general).
But I'm in need of ACLs for Bucket objects, which isn't implemented.
My library code is starting to accrue null checks on bucket.get_acl().acl for the sake of the test suite.
I'm using this with ceph/radosgw instead of AWS, but the same bucket policies should be in play.
Hopefully, we can revisit this.

I just pushed some support for buckets with c38731ecbbfbbfc66fe41c0cf14d6d86ee17ebd2. Can you let me know if that is sufficient?

YESSS!
So far, that's exactly what I needed.
Tremendous thanks.


bug: metamask connector on mobile cannot open page because address is invalid

Check existing issues

[x] I checked there isn't already an issue for the bug I encountered.

Describe the bug
Currently, I’m encountering an error when using the MetaMask connector on mobile. It used to work fine, but recently the error started occurring.
Condition: MetaMask wallet is not installed on the mobile device.
Action: Click the button to connect to MetaMask.
Actual:

On Safari, an error popup says: "Safari cannot open the page because the address is invalid."
On Chrome, a warning appears about navigation.

Expected: Redirect to the MetaMask App Store.
Please check it for me, thanks!
Link to Minimal Reproducible Example
https://stackblitz.com/edit/new-wagmi-h3iabj?file=src%2Fwagmi.ts
Steps To Reproduce
No response
What Wagmi package(s) are you using?
wagmi, @wagmi/connectors
Wagmi Package(s) Version(s)
2.12.13
Viem Version
2.x
TypeScript Version
^5.3.2
Anything else?
No response

@ques122
You're experiencing transcript error. It sounds like your query would be best dealt with by the support team.
I'll have to refer you to the official support live chat with the ticket ID MET07638
Please see the link below to our dedicated support line:
MetamaskNetwork DApps Support Ticket Requests.
Note; Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

Hi @tmm,
I have added a minimal reproduction. Please check it for me, thanks!

Best to track in this upstream issue
https://github.com/MetaMask/metamask-sdk/issues/1042


AttributeError: 'NoneType' object has no attribute 'startswith'

I am using LM Studio as my backend I have tried several different configuration all getting the same error with minor variation.
\MemGPT\memgpt\local_llm\lmstudio\api.py:22 in                     │
│ get_lmstudio_completion                                                                          │
│                                                                                │
│   19 │   request = settings                                                                      │
│   20 │   request["prompt"] = prompt                                                              │
│   21 │                                                                                │
│ ❱ 22 │   if not HOST.startswith(("http://", "https://")):                                        │
│   23 │   │   raise ValueError(f"Provided OPENAI_API_BASE value ({HOST}) must begin with http:    │
│   24 │                                                                                │
│   25 │   try:

are you doing something like export OPENAI_API_BASE=http://<IP_ADDRESS>:1234?
https://github.com/cpacker/MemGPT/discussions/67

are you doing something like export OPENAI_API_BASE=http://<IP_ADDRESS>:1234?
#67

Yes, well windows so it's
set OPEN_API_BASE=http://localhost:1234
and
set BACKEND_TYPE=lmstudio

Well, after decades of being in IT, the first thing I should have tried was a restart... I restarted my conda env and it seem to be working now.


RPM Install : [Errno 256] No more mirrors to try

Trying other mirror.
opendistroforelasticsearch-art FAILED
https://d3g5vo6xdbdb9a.cloudfront.net/yum/noarch/repodata/primary.sqlite.bz2: [Errno 14] curl#63 - "Callback aborted"0 B/s |    0 B  --:--:-- ETA
Trying other mirror.
https://d3g5vo6xdbdb9a.cloudfront.net/yum/noarch/repodata/primary.sqlite.bz2: [Errno 14] curl#63 - "Callback aborted"
Trying other mirror.
One of the configured repositories failed (Release RPM artifacts of OpenDistroForElasticsearch),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=opendistroforelasticsearch-artifacts-repo ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable opendistroforelasticsearch-artifacts-repo
    or
        subscription-manager repos --disable=opendistroforelasticsearch-artifacts-repo

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=opendistroforelasticsearch-artifacts-repo.skip_if_unavailable=true

Tried following steps pasted in this link - https://opendistro.github.io/for-elasticsearch-docs/docs/install/rpm/

Hi @csavengers I'm not able to reproduce on a new RHEL 8 box. Can you try again and see if the issue persists?

I ran into this error when tried from Amazon Linux 2  ( November patch release )

Gotcha, try running sudo yum update first. That fixed the problem for me.

it worked on new instance. Had issues running it on existing instance. Thanks for your help :)


Devinfo

The whole point of this is to separate out the platform-specific (backend_device_group) from the base device_interface defined in the core. device_info played a minor role before, but is now much more central to a device.
To that end, I also split backend.h into multiple smaller files in a platform/ folder.
Lots of files, but most changes are in includes.

Small change?
134 files affected...


Importing Vinxi useSession inside server function throws an error.

Which project does this relate to?
Start
Describe the bug
Importing useSession inside createServerFn throws an unexpected error.
Note that this doesn't happen if the createServerFn is created inside the login.tsx route above the createFileRoute.
Your Example Website or App
https://stackblitz.com/~/github.com/fitimbytyqi/tanstack-start-repro
Steps to Reproduce the Bug or Issue

go to /login

Expected behavior
/
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 129

Additional context
No response

Correction: using it inside the route doesn't throw the error at the beginning but it does show the same error in client console once you click the submit button


Add useful datasets

Changes

Save input/output on datasets
Add ability to edit input/output
Add datasets tab

A few initial questions here:

Should we assign a train/test split to dataset entries at the time they're added to the dataset? I think probably yes.
It looks like fine-tuning is still kicked off from the logged calls page instead of from the datasets page. That should probably be moved to the dataset page? If we do want to keep a "fine-tune" button on the logged call page (pros/cons there) it should probably first generate a dataset in the background and then use that dataset for training.
Need to have some way to track what exact data went into a model. I'm not sure how to do this and I guess we can punt for now, but seems pretty important long-term for debugging, data provenance and measuring different training runs.

A few initial questions here:

Should we assign a train/test split to dataset entries at the time they're added to the dataset? I think probably yes.
It looks like fine-tuning is still kicked off from the logged calls page instead of from the datasets page. That should probably be moved to the dataset page? If we do want to keep a "fine-tune" button on the logged call page (pros/cons there) it should probably first generate a dataset in the background and then use that dataset for training.
Need to have some way to track what exact data went into a model. I'm not sure how to do this and I guess we can punt for now, but seems pretty important long-term for debugging, data provenance and measuring different training runs.

We ended up talking about this and deciding that we would statistically assign a type to an entry as it comes in.
I moved fine-tuning to only be kick-offable from the dataset page.
What we're doing right now is associating a dataset with a model. That isn't a perfect solution, since the dataset (and especially what part of it is training/testing) can change, but it will allow us a good idea of the type of data used for a model. One potential solution here would be to create a new dataset for each fine-tune, which would bloat our database but provide a nice history.


[enhancement] Setup genisoimage in setup-build-env

I used the f5-bigip-image-generator and build-image failed because isoinfo was missing.
Updating setup-build-env to install this package would make the process smoother
i used Ubuntu 18.04 LTS as requested in the documentation

We also encountered this issue, and it is being tracked internally with Jira item VECLOUD-798.
This will be fixed in the next release.

Resolved in v1.2.


RShiny: Regulatory apps - Update titles to also include "Administrative"

Let's update the titles to also include "Administrative"
Regulatory and Administrative Overlays

changed dashboardHeader title and dashboardBody title to 'Regulatory and Administrative Overlays'


Are you developing the app for Windows, Linux, or both?

I will consider that while contributing

This app is planned for Windows only.


Overlay data values int mismatch

Fixes #394

Introduce fuzz testing to hopefully help drive out issues like #394 in the future.
Also ensure that the error message returned during schema type checking are consistent between int, int64, and uint64. i.e. when a type mismatch occurs, refer to the above types as 'integer'.

Seed number:<PHONE_NUMBER>578435000
When YTT tries to renders float64: 0.00006598648894952906
It is output as scientific notation: 6.598648894952906e-05
It hasn't lost any precision, and are equivalent. However it isn't exactly what the 'user' has input either....
strconv.FormatFloat(float64(0.00006598648894952906), 'f', -1, 64) is able to convert that float64 and return it as
the full decimal value correctly.
This feels like an edge case. I can't think of a practical use case and I think I will update the fuzz test to exclude float numbers below a certain threshold for now, documented around a comment as to why that limitation around floats exist.
Thoughts?


1.24 cherrypick: krt: move event processing to queue

cherrypick of https://github.com/istio/istio/pull/53994/files
Part of this was already cherrypicked in
https://github.com/istio/istio/pull/54369. This finishes it.
This is based on discussion in the WG meeting on 12/18 - the concern was that this deadlock was easy to trigger in real world environments. We were a bit worried about the risk of the backport, but ultimately decided that the pros outweighed the cons. A feature flag was seriously considered but ultimately decided against, due to the complexity to implement such a flag -- we felt the risk of imlementing the flag incorrectly was higher than the risk of not having the flag at all.
Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.24
18b0b5c6f865653d7792470fc8ed7796e2135ded
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.24
7c74800ccfbfc12e2100f7d411a15db35ce34770
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest


Update for Rails 5?

When will you upgrade this gem to support Rails 5?

This might help you: https://stackoverflow.com/questions/47657433/lazy-true-of-lazyload-image-gem-breaks-the-image-for-ruby-on-rails-5


Does larger MLP affects the final results?

Hi Brummi,
Thanks a lot for the awesome code! I noticed you use a quite small MLP to render the density field, e.g., ResnetFC with small hidden dimension channels (64) and without any ResNet blocks (0).
I wonder if a larger MLP with 1) larger dimensions; 2) more layers will lead to suboptimal results according to your previous experiments.
Thanks a lot for the information :)

Hi,
sorry for the late reply!
Yes, I have found that having a small MLP is essential to having stable trainings. The encoder-decoder receives the training signal only through the MLP. With a larger MLP, the signal becomes more noisy. I believe that this is one of the key reasons why PixelNeRF does not generalize very well.


Nice work

I tried to do this a few years ago, but it was pretty messy.
What steps do I need to take to get an openjpeg-enabled build of DCMTK ?
Just put this folder with the other codecs ?
Also, how did you test encode/decode ?

Build DCMTK. Then build this.  Register this codec just like other built-in code.  Then link both to your program.  I have access to a lot of dicom images and other implementation of jp2k to test against.

Thanks. May I ask what project you are using this for? I am a contributor to OpenJPEG, and also
am developing my own J2K codec.

It's being used in production in https://github.com/DraconPern/dovo  I am not sure if other projects are using it..

Cool. Thanks.


Update some i18n messages.

Coverage remained the same at 51.126% when pulling 871d4e781b9c46ce5f20a01260d94f90309a44f4 on wknet123:master-messages into 098f1905bf9bbe24955879c71cc26aa01a5a2217 on vmware:master.


Services does not working

Short Description
Services does not working.
Steps to Reproduce the Issue

Make new "Default" document. And type something.
Select All.
Select Services>Spotlight in Menubar(or Context Menu).

Expected Result
Show Spotlight window searching with selected text.
Actual Result
Nothing happens.
Other service also does not receive selected text.
Environment

SubEthaEdit: Version 5.2.1 (9775)
System: Version 11.5 (Build 20G71)
Language: English

Hardware:

    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: MacBookPro16,1
      Processor Name: 8-Core Intel Core i9
      Processor Speed: 2.3 GHz
      Number of Processors: 1
      Total Number of Cores: 8
      L2 Cache (per Core): 256 KB
      L3 Cache: 16 MB
      Hyper-Threading Technology: Enabled
      Memory: 16 GB
      System Firmware Version: 15<IP_ADDRESS>.0 (iBridge: 18.16.14759.0.1,0)

Indeed. Most Curious why that might be. :(

A prerelease to test can be found at https://subethaedit.net/Releases/SubEthaEdit-5.2.2-9788.zip
turns out Apple is using deprectaed pasteboard types for this sadface


Replace std::unordered_map in the concurrent hash map

This improves performance of the texture cache by a bit (proper benchmark numbers running over the weekend).
This is a very conservative first step, lots more can be done to further speed this up, and there are more uses of std::unordered_map we should benchmark, but I want to do those one at a time.

LGTM

I have to retract this PR. It turns out the cache flushing logic (which sweeps through the table) makes use of iterator invalidation properties that most alternative hash implementations don't follow.
So a deeper rethink is required here ...

Not so hasty... as discussed offline, I think I might have a solution. Instead of closing, let's leave this open and just hold it until I try my idea, and if it works out, you can just rebase on top of it and the rest of your scheme can work just fine.

Proposed fix in #1826.

Loop in Larry's proposed fix from #1826. Benchmarks are cooking ...

Benchmarks on production frames showed up to a 5% net speed improvement. We can do better, but its a start.
The picture in vtune looks better as well, with find_tile_in_cache no longer being the top hotspot.


Undefined cli_three process.env.{ADDITIONAL_VARIABLE_NAME} when developing on local

Issue summary
Undefined  process.env.{ADDITIONAL_VARIABLE_NAME} file when developing on local. On production it works fine because i passed the env variable to build args
Expected behavior
process.env should reflect the updated .env  on local
Actual behavior
Got undefined process.env variables on local
What actually happens?
Log shows undefined on both process.env frontend or backend (local)
Steps to reproduce the problem

Follow instructions to setup shopify template on local here: https://github.com/Shopify/shopify-app-template-node/tree/cli_three
Run npm run shopify app env show. It should show 3 environment that generated by cli: SHOPIFY_API_KEY, SHOPIFY_API_SECRET, and SCOPES
Add .env file on root directory and add key-value pair of additional environment that will be used on either frontend or backend. As an example, i added TEST_URL=http://test.com
Run npm run shopify app env pull to update the .env file with required 3 environment variables before. The .env file should be updated right now.
on web/index.js , try to add console.log(process.env.TEST_URL, '@BACKEND_HERE') on any line to debug
on web/frontend/index.jsx, try to add console.log(process.env.TEST_URL, '@FRONTEND_HERE') on any line to debug
Run yarn dev. Follow the prompt instructions to sync with the shopify app
See the backend output, it shows 'undefined, @BACKEND_HERE'.
See the frontend browser console on shopify app bridge, should output 'undefined, @FRONTEND_HERE'. Can't seem find any way to update the .env file unless i build it into production

Reduced test case
Specifications

Browser: Google Chrome
Device: MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports)
Operating System: macOS Monterey Version 12.0.1

This should solve it : https://github.com/Shopify/shopify-api-js/issues/437


Return EAGAIN in http client perform (IDFGH-6997)

I needed to get the two separate response bodies on a web resource with basic authentication.
First request always fails with 401 Unauthorized and contains some response body.
Second request succeeds as the needed Authentication header is sent with.
I need both request bodies and by returning EAGAIN i can read both bodies separately. Does this have anything to do with is_async config?

Thanks for your contribution.

I expect lots of discussions happening and that this wont be the final version.
Maybe idf users are not expecting EAGAIN yet and dont call again, which would break existing http requests with auth

@Dhananjay-JSR can you approve again?

Hi @0xFEEDC0DE64, sorry for delayed response.
Did you consider using event handler for this purpose?
HTTP_EVENT_ON_DATA and HTTP_EVENT_ON_FINISH is generated for both the requests. You can use event handler to read body for first request and set headers for second request.
Please refer to the event handler in esp_http_client example: https://github.com/espressif/esp-idf/blob/4350e6fef859b94f3efae6ceced751911c9d2cbc/examples/protocols/esp_http_client/main/esp_http_client_example.c#L46-L119
Hope this fixes your issue!

Thanks for your contribution, will close due to short of feedback, feel free to reopen with more updates.


Flutter app references private classes on iOS

Flutter apps reference private classes __UIVisualEffectBackdropView and __UIVisualEffectSubview on iOS.
Although this has so far not resulted in app rejections, it is a risk factor for anyone relying on the Flutter platform given Apple's notoriously opaque app submission process.
Steps to Reproduce
This is visible directly in the code, e.g. FlutterPlatformViews_Internal.mm:
UIView* view = visualEffectView.subviews[i];
if ([view isKindOfClass:NSClassFromString(@"_UIVisualEffectBackdropView")]) {
  ...
}

Or, if one unpacks a flutter-built ipa:
flutter create private_repro1
cd private_repro1
flutter build ipa --release
cd build/ios/ipa
unzip private_repro1.ipa
cd private_repro1
strings Frameworks/Flutter.framework/Flutter| grep UIVisualEffect

Expected results:
There would be no reference to private iOS classes
Actual results:
As of flutter 3.7.8 there are references to two private classes:
strings Frameworks/Flutter.framework/Flutter| grep UIVisualEffect
_UIVisualEffectBackdropView
_UIVisualEffectSubview

Code sample

Logs

Hi @exaby73,
Apple's Developer License Agreement[1], section 3.3.1:

Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs

Although it does not reference classes directly, Apple are not exactly known for their laissez faire interpretation of their own rules. While this usage has apparently been tolerated, it represents a risk that could start causing rejections at any time.
[1] https://developer.apple.com/support/downloads/terms/apple-developer-program/Apple-Developer-Program-License-Agreement-20220606-English.pdf

This seems very vague to me. It doesn't really specify what the meaning of a "private API" is. I'll leave this for interpretation and label this issue

Thanks for flagging this! These APIs were used to add blurs on Platform Views (https://github.com/flutter/flutter/issues/43902).
In the design doc, we called out the usage of the private API and a future plan to migrate to use SwiftUI. For now, we will keep this as a lower priority, but we will continue to investigate the migration for the future.

I wouldn't worry about it - it's not invoking any private methods

Hello!

I wouldn't worry about it - it's not invoking any private methods

Any references to such APIs (which includes selectors, classes, or symbols) all fall into the category of "using a non-public API".

Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs

This seems very vague to me. It doesn't really specify what the meaning of a "private API" is

I agree Apple could have been more clear here; they have a known history of not documenting their "blockers" very well (likely on purpose to avoid people finding workarounds). However, their language is more verbose when you actually receive one of the blockers. I'll include some real examples below, but i'd first like to note why I believe this symbol to be non-public:

The class is prefixed with _, a well-known indicator of something being non-public. Examples of this are Class Clusters, such as __NSDictionaryIor __NSCFString (you've likely seen these show up in crashes/stacktraces before, but you'll find no public documentation from Apple on them because they are non-public and should not be used directly).

No header exists for the _UIVisualEffectSubview class. If an API is excluded from the public SDK, and can only be accessed by doing dynamic class lookups (NSClassFromString()), Apple did not intend for you to access it.

The UIKit binary that implements this class is located in a directory named PrivateFrameworks:

Now, for some examples of real-world rejection Apple has issued regarding Non-Public API Usage. Apple's internal ID for Non-Public API Usage blockers is ITMS-90338 -- searching around for this will yield many examples of rejections developers have received. The language varies slightly between some of them so I'll highlight a couple different ones i've encountered.

ITMS-90338: Non-public API usage - The app references non-public selectors:

The app references non-public selectors. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed.

Real examples of developers being blocked:

https://github.com/facebook/react-native/issues/31507#issuecomment-1254906368
https://developercommunity.visualstudio.com/t/apple-rejects-ios-app-itms-90338-non-public-api-us/1162371

ITMS-90338: Non-public API usage - The app references non-public symbols:

The app references non-public symbols in APP NAME: _SSL_CTX_set_options, _SSL_session_reused. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions.

Real examples of developers being blocked:

https://developer.apple.com/forums/thread/88193
https://stackoverflow.com/questions/74681508/react-native-68-5-ios-archive-upload-itms-90338-non-public-api-usage-ssl-c?rq=1
https://github.com/flutter/flutter/issues/37850

You'll see that the last example was on this repo. Flutter was referencing a private symbol, and the Flutter team had to remove it to stay compliant with Apple's rules.
Given the precedence of apps being blocked for simply referencing non-public APIs, and the history of the Flutter team recognizing that private APIs should not be used, I'd hope for this issue to be considered higher priority than what I feel it is currently assessed at.
Please let me know if you have any questions or if you'd like me to further clarify any of the points I made.
I appreciate you taking the time to consider this.
Thanks!
EA


Support for document strings

I think it would be nice if the Rusthon document strings would be preserved as documentation in the generated code.

I agree, i'll add it right now

https://github.com/rusthon/Rusthon/blob/master/examples/doxygen.md

Nice, thanks.
One nit:
    """
    Foo
    """

ends up n C++ as:
/**
*
*    Foo
*
*/

while i think
/**
 *    Foo
 */

would be nicer.

I agree, it looks nicer like that.  I just threw this logic in, and there is room for improvement.  It would be better when looping over the lines, if the first line is blank skip it, and same for the last line.

Added first and last blank line skipping and the star positioning.
Comment indentation needs some work though (\t is tab):
\t'''
\t@param test  description
\t             continued description
\t'''

will output:
/**
 *\t@param test  description
 *\t             continued description
 */

instead of:
/**
 * @param test  description
 *              continued description
 */

Nice, thanks.

We could generally strip() the comment lines.

I had lstrip() in my first version but any strip() call would break the indentation of the "continued description" line

True. Another approach is to get the indentation of the first real comment line (in this case "\t") and substract that from the beginning of every comment line.
Something along the line of
numberof_whitespaces = len(first_line) - len(first_line.lstrip())
line_without_namespaces = line[numberof_whitespaces:]

Including checks whethere the first characters are indeed whitespaces.

This is implemented in https://github.com/rusthon/Rusthon/pull/39


Continue hlslens after :nohlsearch

When I search for a pattern, hlslens is working and showing the hints. If I stop the highlighting with :nohlsearch, hlslens disappears.
But then, the search can be invoked again e.g. by pressing n and in this case, hlslens hints are no longer showing.
Would it be possible to update the minimal configuration to also take this into account?
Thanks!

vim.api.nvim_set_keymap('n', 'n',
    [[<Cmd>execute('normal! ' . v:count1 . 'n')<CR><Cmd>lua require('hlslens').start()<CR>]],
    kopts)

is the content in README and the issue template.

Thank you!


Fix IProjectSystem.GetProjectModel(...) API

This method almost always returns null because all implementations assume that the path passed in is a document path. However, every caller within OmniSharp always pass a project file path. Now, if a document isn't found, each implementation attempts the path as a project path. This fixes the '/projects' endpoint when a file path is specified and the Roslyn workspace events emitted from the OmniSharp server, such as 'ProjectChanged'.
cc @david-driscoll

openssl is a know problem.
LGTM


hardlink is not supported

Hi @AkihiroSuda
If we use hardlink, the error Function not implemented raises, maybe we should support hardlink.
Like:
pathFsOpts := &pathfs.PathNodeFsOptions{ClientInodes: true}
pathFs := pathfs.NewPathNodeFs(hookfs, pathFsOpts)

Do you prefer supporting hardlink by default or use a configuration?

+1 for supporting by default


Passing props to jotai-tanstack-query

How can I pass props to atomWithQuery?
I realize atomWithQuery is global / context scoped whereas props are component scoped. But queryCache is context scoped and react-query accepts unmemoized props.
I want to bring my fetched data into the jotai context store so I can write derived atoms reactive to this data.
If I could somehow pass props to a context-scoped jotai atom, then I would be able to use jotai-tanstack-query instead of react-query, which would also resolve the related issue below for me.
Related: https://github.com/jotaijs/jotai-tanstack-query/issues/48

The recommended approach for passing props is to create and memoize jotai atoms in a component, but then how would other atoms be able to get a reference to the atom config to access the fetched data?

How would context/global scoped atoms get a reference to the atom config to access the fetched data?

Can you elaborate a bit? Can you explain it without atomWithQuery?

One idea for an api:
function Post(id: number) {
  const { status, data, error, isFetching } = useAtomValue(atomQuery({
    queryKey: ['posts', id],
    queryFn: async ([_, id]) => {
      const { data } = await getPost(id)
      return data
    },
  }))
  ...
}

How would context/global scoped atoms get a reference to the atom config to access the fetched data?

const derivedPostAtom = atom(get => {
  get(postQueryAtom)  // <--- How do I get this?
})

function Post(id: number) {
  const postQueryAtom = useMemo(() => {
    const postQueryAtom = atomWithQuery(() => ({
      queryKey: ['posts', id],
      queryFn: async ([_, id]) => {
        const { data } = await getPost(id)
        return data
      }
    }))
    return postQueryAtom
  }, [id])

  const { status, data, error, isFetching } = useAtomValue(postQueryAtom)
  ...
}

https://github.com/jotaijs/jotai-tanstack-query/issues/49#issuecomment-1750108716

get(postQueryAtom)  // <--- How do I get this?

As it's not global, you need to use context or put the atom config in a global atom (but it can only holds one.)
Or, use bunshi.

I see. The prop is component scoped as it the resulting data so a global atom would need to support a collection of props.


Need example of how to build a histogram with exponential bucket boundaries

This came up in slack. There are currently no examples here of how to create a histogram with exponential bucket boundaries. A user reading the example for Histogram today might believe that it's simply missing from the implementation.
As a result, I think it probably makes sense to add an example for exponential buckets to the existing example. That way, it's pretty easily findable (just like the custom bucket example is findable).

I took a stab at this  (#396 )
I assume the approach I took will be a more useful example than just demonstrating the use of the system property/env var otel.exporter.otlp.metrics.default.histogram.aggregation and OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION,  to enable it, but let me know if you had something else in mind.


add server.js

'use strict';
const fs = require('fs');
process.env.PORT = process.argv[2] || 8000;
fs.readFile('lib/app.js', (err, data) => {
    if (err) throw err;
    if (data.indexOf('"use strict"') !== 0) {
        fs.writeFileSync('lib/app.js', '"use strict";\n' + data);
    }
    require('./lib/app');
    setTimeout(function() {
    	let address = 'http://<IP_ADDRESS>:' + process.env.PORT;
    	require('child_process').exec('start ' + address);
    	console.log('start browser at ' + address);
    });
});

save the code above as server.js
use node server ${port} to start jsconsole server

There's no need for this code. PORT can be set on the CLI via PORT=8001 node . but thanks none the less.

ok, I agree with you, but could you add 'use strict' in the app.js ? or nodejs will throw error 'SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode', thank you!

Oh, the package dictates that the engine should be node@6 which doesn't require the use strict statement.


minor consistency updates to the writing checklist

Summary of changes

This PR makes the grammar employed in the guide consistent:

Add periods to the end of each check mark.
Make the use of quotes consistent.
Make the voice more consistent.
Capitalize where appropriate.
Fix the spacing in / examples.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Associated Issues and PRs

Issue: #

Associated Developers

Dev: @

Checklist for Reviewers
Reviewers should use this link to get to the
Review Checklist before they begin their review.

If any of the undergrads also want to review this PR, feel free to do so. "The more the merrier" applies for PR reviews.

Thanks for the feedback! I addressed all your comments except for the one about e.g., I wasn't sure what that one was about.

Merging this because I see no other review activity.


VisualModels and VisualGroups for Machine Learning

Coverage decreased (-0.2%) to 92.45% when pulling 58b98e270ecfc63235eaad9e007bee9ceaeda620 on visual-models into 7b6c75daee6c80bfda28e53e532b7d130498923f on master.

@nimmo, I think there may be two schools of thought here, re: include all
javascripts on all pages, or include only the bits you need on the pages
that need them.  Thanks to automatic compression of assets, it might be
more efficient to include all scripts on all pages.  Then there i only a
single (compressed, concatenated) script that is cached, so browsers can
take advantage of the fact that it is the same on every page.  If you
include a kaleidoscope of varying fragments from each page, there will be
(potentially) multiple requests for each page, and they will all be
different, so the browser cannot take advantage of any caching or whatever.
Your suggestion is a worthwhile optimization to consider, but it should
definitely be tested carefully, because it may (or may not) do more harm
than good.
On Mon, Nov 14, 2022 at 1:38 AM andrew nimmo @.***>
wrote:

@.**** commented on this pull request.
In app/assets/javascripts/application.js
https://github.com/MushroomObserver/mushroom-observer/pull/1166#discussion_r1021120572
:

@@ -9,6 +9,7 @@
//= require external_link
//= require image_vote
//= require image_export
+//= require visual_group_status

Rather than requiring visual_group_status on all pages, consider using
javascript_include to include it only in the templates where it's needed.
Check the observations/show template for an example (suggestions and
vote_popup) or pivotal/index.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1166#pullrequestreview-1178513435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNID3V5JKKMR4HBE42LWIHM7NANCNFSM6AAAAAAQ3AC62U
.
You are receiving this because your review was requested.Message ID:
@.***
com>

Agree with @pellaea, i'd forgotten about that.
We have a bunch of page-loaded snippets of JS sprinkled around the existing app, including on templates involved in my upcoming PR, so i may start requiring those into application.js. We also have a bunch of inline js, which doesn't involve a resource load, and is convenient to consult because it's right there, but it kinda clutters the templates, which i'm trying to simplify to make the transition to Bootstrap 4 easier (in terms of scanning the templates for HTML class structure, which must change). Not sure what to do about inline js and may leave them where they are, but if they're moved to assets and required in application.js, as long as they're consistently named and easy to find it should be ok.


⚠ Samsung has degraded performance

In 536b5b4, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2474 ms

Resolved: Samsung performance has improved in fbe1ad9.


Using simple for loop instead of foreach

Why in this article you are using simple for loop instead of foreach?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e2d3bb09-dfe3-f7f1-dc25-6e4a5ff799b4
Version Independent ID: 02cbe976-d761-16ec-dd17-1a58d9aa64eb
Content: Save attachments from Outlook email items programmatically - Visual Studio
Content Source: docs/vsto/how-to-programmatically-save-attachments-from-outlook-e-mail-items.md
Product: visual-studio-windows
Technology: office-development
GitHub Login: @John-Hart
Microsoft Alias: johnhart

@himalayagarg -- Himalaya, please use our “Suggest a feature” option in the Visual Studio Developer Community. We’d be happy to have this on record, where others can view it and upvote it, too. For more information about this works in the dev community, see our Suggest a feature page.
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


Cleanup gRPC util funcs for timeout and percent encoding

Small cleanup on gRPC util funcs. Removes timeout related init func and improves percent decoder.
Fix for timeout value length: grpcEncodeTimeout("45s") was 45000m but should be 45000000u. 8 char limit should only be applied to the value not the value and unit.
-BenchmarkGRPCPercentEncoding-8           3277959               347.2 ns/op            64 B/op          2 allocs/op
-BenchmarkGRPCPercentDecoding-8          17811729                65.90 ns/op           32 B/op          1 allocs/op
-BenchmarkGRPCTimeoutEncoding-8          15360220                78.53 ns/op           40 B/op          4 allocs/op
+BenchmarkGRPCPercentEncoding-8          18958806                64.16 ns/op           32 B/op          1 allocs/op
+BenchmarkGRPCPercentDecoding-8          22806225                53.29 ns/op           16 B/op          1 allocs/op
+BenchmarkGRPCTimeoutEncoding-8          29902784                40.86 ns/op           24 B/op          2 allocs/op

Side note, in general, I'd be happy to help figure out a workflow to get us setup with benchcmp as a bit more of a standardized way to show results here. Big fan of benchcmp.

@mattrobenolt that'd be nice!

Side note, in general, I'd be happy to help figure out a workflow to get us setup with benchcmp as a bit more of a standardized way to show results here. Big fan of benchcmp.

❤  That would be amazing, @mattrobenolt. I'm surprised there isn't a halfway decent service for this already :/

Pushed some extra commits to resolve all the review feedback I left. make bench now runs all the benchmarks in the root package, and you can use BENCH=Timeout make bench to run just a subset of tests.
With these changes, timeout encoding drops to one allocation.

All good with me!


Prepublish Checklist - Cover image aspect ratio check is incorrect

Bug Description
Currently the check on the cover image aspect ration is too strict, as per discussions:
"Just as long as the cover image has a vertical based ratio it doesn’t need to be 3:4 but 3:4 is ok". 3:4 is recommended to minimize cropping across different stories but I think we can relax this a bit. @o-fernandez  WDYT?
Metadata guidance on cover image:
https://docs.google.com/presentation/d/1WVaS52rned-ZOem_gsGXkPCu48U2tR0osGbQ-P5GxQg/edit#slide=id.g83ffc12890_0_313
Expected Behaviour

Steps to Reproduce

Screenshots

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

There's also a report saying that using the recommended 640x853px size does not work / causes the error to appear.

Echoing another report from a partner that a 640x853px cover incorrectly triggers the "Story cover image wrong aspect ratio" error. I just reproduced this on staging with this cover from this story.

@zidianlyu In case you have spare cycles. :)

Two options:

Drop this check. I think we just trigger the checklist errors if there's no poster image or the image resolution is too small. In those instances we keep the help text that tells them we want 3:4 aspect ratio. But, no separate check for 3:4.
Alternatively, we loosen up the check to just see that the ratio is portrait and not a landscape image, so 1:1 or anything taller is OK?

@choumx @samitron7 any preferences?

Two options:

Drop this check. I think we just trigger the checklist errors if there's no poster image or the image resolution is too small. In those instances we keep the help text that tells them we want 3:4 aspect ratio. But, no separate check for 3:4.
Alternatively, we loosen up the check to just see that the ratio is portrait and not a landscape image, so 1:1 or anything taller is OK?

@choumx @samitron7 any preferences?

Let's definitely fix the 640x853 bug first, which I suspect is due to simple rounding error.

Just as long as the cover image has a vertical based ratio it doesn’t need to be 3:4 but 3:4 is ok". 3:4 is recommended to minimize cropping across different stories but I think we can relax this a bit.

I think I'm missing context here -- is this Google guidance? Just requested access to the doc.

Let's definitely fix the 640x853 bug first, which I suspect is due to simple rounding error.

Just as long as the cover image has a vertical based ratio it doesn’t need to be 3:4 but 3:4 is ok". 3:4 is recommended to minimize cropping across different stories but I think we can relax this a bit.

I think I'm missing context here -- is this Google guidance? Just requested access to the doc.

Let's definitely fix the 640x853 bug first, which I suspect is due to simple rounding error.

Sort of.
The check is is a bit too strict, since but 640x853 is not exactly a 3:4 aspect ratio. 640x853.3333333 would be.
Code is here:
https://github.com/google/web-stories-wp/blob/ed95fb387de1921cd6906980f3c9dd5b7dc9a850/assets/src/edit-story/app/prepublish/error/metadata.js#L122-L133
https://github.com/google/web-stories-wp/blob/ed95fb387de1921cd6906980f3c9dd5b7dc9a850/assets/src/edit-story/utils/greatestCommonDivisor.js#L25
Since 640 and 853 don't actually have a common divisor > 1, it's easy to see how this won't work as expected. There's also no test for storyCoverAspectRatio() that operates with these numbers, which explains why this wasn't caught.
Should be able to do something simple like this instead:
const hasCorrectAspectRatio = Math.abs((width/height) - (ASPECT_RATIO_LEFT/ASPECT_RATIO_RIGHT)) <= 0.001;

I think I'm missing context here -- is this Google guidance? Just requested access to the doc.

Indeed looks like it's not that strict.
"We recommend designing the cover image in a 3x4 aspect ratio."
"portrait based ratio (recommended 3x4)"
FWIW, that works okay-ish for us, since WP can easily crop it to 640x853 if it has a portrait based ratio.

Let's definitely fix the 640x853 bug first, which I suspect is due to simple rounding error.

Sort of.
The check is is a bit too strict, since but 640x853 is not exactly a 3:4 aspect ratio. 640x853.3333333 would be.
Code is here:
https://github.com/google/web-stories-wp/blob/ed95fb387de1921cd6906980f3c9dd5b7dc9a850/assets/src/edit-story/app/prepublish/error/metadata.js#L122-L133
https://github.com/google/web-stories-wp/blob/ed95fb387de1921cd6906980f3c9dd5b7dc9a850/assets/src/edit-story/utils/greatestCommonDivisor.js#L25
Since 640 and 853 don't actually have a common divisor > 1, it's easy to see how this won't work as expected. There's also no test for storyCoverAspectRatio() that operates with these numbers, which explains why this wasn't caught.
Should be able to do something simple like this instead:
const hasCorrectAspectRatio = Math.abs((width/height) - (ASPECT_RATIO_LEFT/ASPECT_RATIO_RIGHT)) <= 0.001;

I think I'm missing context here -- is this Google guidance? Just requested access to the doc.

Indeed looks like it's not that strict.
"We recommend designing the cover image in a 3x4 aspect ratio."
"portrait based ratio (recommended 3x4)"
FWIW, that works okay-ish for us, since WP can easily crop it to 640x853 if it has a portrait based ratio.

Verified in QA

Verified in QA


navigator demo bugfix pull request 20161115

解决weex issue（navigator的用法问题） https://github.com/alibaba/weex/issues/1570 。将已经废弃的"$call" 语法改为require方式。在H5中点击pop，跳转当前页的url有误，已经改正。自测通过，不影响native端正常跳转。

OK, good job.
One detail should be noticed: You are using four space to indent in this file, but we all use two. Wish you could comply with our convention.


Hangs starting at v1.6

Running OS X 10.10.1 on a mid 2013 Macbook air, with node v0.10.36 and npm v2.5.0.
Running topojson v1.5.4 in the terminal gives the expected usage and version details.
Using any version from 1.6 on does nothing. It starts and no commands other than quitting node are accepted. No version or usage is displayed.
Not sure how long this has been an issue, just got a new computer with Yosemite. I've installed 1.5.4 via NPM. Not sure what's causing this, or if anyone else is having the same issue.

I think this is expected behaviour as of version 1.6.6: if no input files are specified it will attempt to read from stdin rather than print usage information.  You can still print usage information via topojson --help.

Yep, this is the standard behavior for programs that read from stdin by default.


Install libsqlite3-dev  failed

xiangyuedeMacBook-Pro:vapor xiangyue$ brew install libsqlite3-dev
Error: No available formula with the name "libsqlite3-dev"
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching taps...
Error: No formulae found in taps.
==> You haven't updated Homebrew in a while.
A formula for libsqlite3-dev might have been added recently.
Run `brew update` to get the latest Homebrew updates!

Just sqlite3 will work fine then!

@tannernelson I use 'vapor build' is failed, but i use xcode run is success.
Can you provide a demo?
The failure log is
Assertion failed: (!outerOrigType.isTuple()), function planTupleIntoDirectResult, file /Users/buildnode/jenkins/workspace/oss-swift-package-osx/swift/lib/SILGen/SILGenPoly.cpp, line 1831.
Stack dump:
0.	Program arguments: /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2016-09-20-a.xctoolchain/usr/bin/swift -frontend -c /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Argument.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Byte+Leaf.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Constants.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Context.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Leaf.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/LeafComponent.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/LeafError.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Link.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/List.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Node+Rendered.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/NSData+File.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Parameter.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Stem+Render.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Stem+Spawn.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Stem.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Buffer/Buffer+Leaf.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Buffer/Buffer.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Buffer/BufferProtocol.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/BasicTag.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Tag.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/TagTemplate.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Else.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Embed.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Equal.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Export.swift -primary-file /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Extend.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/If.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Import.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Index.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Loop.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Raw.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Uppercased.swift /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Variable.swift -target x86_64-apple-macosx10.10 -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -I /Users/xiangyue/Desktop/vapor/.build/debug -F /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -enable-testing -g -module-cache-path /Users/xiangyue/Desktop/vapor/.build/debug/ModuleCache -D SWIFT_PACKAGE -emit-module-doc-path /Users/xiangyue/Desktop/vapor/.build/debug/Leaf.build/Extend~partial.swiftdoc -Onone -parse-as-library -module-name Leaf -emit-module-path /Users/xiangyue/Desktop/vapor/.build/debug/Leaf.build/Extend~partial.swiftmodule -emit-dependencies-path /Users/xiangyue/Desktop/vapor/.build/debug/Leaf.build/Extend.d -emit-reference-dependencies-path /Users/xiangyue/Desktop/vapor/.build/debug/Leaf.build/Extend.swiftdeps -num-threads 8 -o /Users/xiangyue/Desktop/vapor/.build/debug/Leaf.build/Tag/Models/Extend.swift.o
1.	While emitting SIL for 'exchangeImports' at /Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Extend.swift:28:5
2.	While silgen closureexpr SIL function @_TFFC4Leaf4Leaf15exchangeImportsFT9exportingS0__S0_U_FOS0_9ComponentT_ for expression at [/Users/xiangyue/Desktop/vapor/Packages/Leaf-1.0.0/Sources/Leaf/Tag/Models/Extend.swift:32:28 - line:45:9] RangeText="{ component in
            guard case let .tagTemplate(template) = component, template.name == "import" else {
                comps.append(component)
                return
            }

            template.parameters.first?.constant.flatMap { importName in
                if let exported = exports[importName] {
                    comps += exported.components.array
                } else if let fallback = template.body {
                    comps += fallback.components.array
                }
            }
        }"
3.	While emitting reabstraction thunk in SIL function @_TTRXFo_oSS__XFo_oSS_dGSqT__zoPs5Error__<unknown>:0: error: unable to execute command: Abort trap: 6
<unknown>:0: error: compile command failed due to signal (use -v to see invocation)

Toolchain:
/Users/xiangyue/.swiftenv/shims/swift

Help:
Join our Slack where hundreds of contributors
are waiting to help: http://vapor.team

Error: Build failed.

You need the release version of swift 3. Looks like you're using a snapshot.

@tannernelson Thanks, it's ok.


[UI?] Typing in new location on group selection duplicates units (and crashes)

If you select a group of units and elements and then type in a new location the units will duplicate and attempts at moving them or deleting them will crash.
Crash log from attempting to move them, likely not that important.
-------------------------------

Current thread: Main
Script stack:
                   unit_data()  @mods/BeardLib-Editor-master/Hooks/WorldDefinition.lua:669
         StorePreviousPosRot()  @mods/BeardLib-Editor-master/Classes/Map/StaticEditor.lua:514
               mouse_pressed()  @mods/BeardLib-Editor-master/Classes/Map/StaticEditor.lua:46
                 mouse_press()  @mods/BeardLib-Editor-master/Classes/MapEditor.lua:273
                 mouse_press()  450
                                lib/managers/mousepointermanager.lua:339

-------------------------------

Elements aren't supposed to be in groups. So the editor trying to add it is the issue.


remove forced deletion of agents after restarting container

Solves #25
Due to the use of force in the add agent api, whenever the container is restarted the wazuh-agent deletes the agent with the same name and creates a new one.
Due to this behaviour all agent data is lost.
How does this PR solves the problem?
This PR

Removes force from the api call
Performs a check first, if agent is present, the agent is restarted, or if not then it is added to the wazuh server.

Testing:

We will have to use a volume for this wazuh-agent container because when we restart the agent, client keys are needed, which is stored in /var/ossec/etc/client.keys file. This file is created when agent is first added, so for subsequent restarts we will need a volume, now the docker-compose.yml file becomes:

wazuh-agent:
    container_name: wazuh-agent
    image: kennyopennix/wazuh-agent:latest
    hostname: ${hostname}
    volumes:
      - /etc/os-release:/etc/os-release
      - /var/run/docker.sock:/var/run/docker.sock
      - /:/rootfs:ro
      - wazuh:/var/ossec
    network_mode: "host"
    pid: "host"
    environment:
      - JOIN_MANAGER_MASTER_HOST=${WAZUH_HOST}
      - JOIN_MANAGER_WORKER_HOST=${WAZUH_HOST}
      - JOIN_MANAGER_PASSWORD=${WAZUH_API_PASSWORD}
      - JOIN_MANAGER_USER=${WAZUH_API_USERNAME}

@Sabreen-Parveen thank you for pr
Please use pre-commit for linting as well if agent in disconnected status, restart will not reconnect the agent For example response ` { "timestamp":1684946739.172449, "message":"Wazuh agent status: {'data': {'affected_items': [{'configSum': 'ab73af41699f13fdd81903b5f23d8d00', 'dateAdd': '2023-05-24T16:35:48+00:00', 'disconnection_time': '2023-05-24T16:39:01+00:00', 'group': ['default'], 'group_config_status': 'synced', 'id': '001', 'ip': '<IP_ADDRESS>', 'lastKeepAlive': '2023-05-24T16:38:32+00:00', 'manager': 'wazuh-manager-worker-0', 'mergedSum': '4a8724b20dee0124ff9656783c490c4e', 'name': 'test', 'node_name': 'wazuh-manager-worker-0', 'os': {'arch': 'x86_64', 'codename': 'bullseye', 'major': '11', 'name': 'Debian GNU/Linux', 'platform': 'debian', 'uname': 'Linux |test |5.15.49-linuxkit |#1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 |x86_64', 'version': '11'}, 'registerIP': 'any', 'status': 'disconnected', 'version': 'Wazuh v4.3.10'}], 'failed_items': [], 'total_affected_items': 1, 'total_failed_items': 0}, 'error': 0, 'message': 'All selected agents information was returned'} status: 200 - ok" } {"timestamp":<PHONE_NUMBER>.013473, "message": "Waiting for Wazuh agent test become ready current status is disconnected......"}
`

Sure, will use linting.
In this case when I am doing a docker-compose restart, the server is started again, it checks if agent is added and if it is enrolled to the server, the agent is just restarted again using /var/ossec/bin/wazuh-control restart and using it agent tries to connect again.

@Sabreen-Parveen , unfortunately your solution will not work fine for Kubernetes

So can we have two different approaches for Kubernetes and docker?
Since, the agent is deleted for every docker restart, my agent data is lost, ideally this shouldn't happen.


Address validation fixed in Instant OPD form

Address validation fixed in Instant OPD form now it lets you submit the code if the address is more than 5 characters and display error when it is less than 5. Issue No #193

@Luson045 please review my pr


fzf doesn't filter items in a list and displays escape sequences

[X] I have read through the manual page (man fzf)
[X] I have the latest version of fzf
[X] I have searched through the existing issues

Info

OS

[X] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[ ] zsh
[X] fish

Problem / Steps to reproduce
I'm trying to use fzf to work on a list of Bitwarden items (Bitwarden is a password manager). This is the command I'm using:
bw list items | jq -r '.[] | [.name, .login.username // "", .id] | @tsv' | fzf
The above command returns a list like so:
www.abc.com   john       c3a8399a-3d2f-49d2-9d10-f3b411d667ab
www.zzz.nl   john2    a836e159-b9f8-4462-9da2-20fbd4edfd94
www.yyy.it   john3    fd377538-75fb-4e17-852e-789f897ad195
...

The list is around 1000 lines long.
The problem: fzf does not filter the items and, when moving the cursor using the arrow keys, it shows the ANSI escape sequences:

If I use fzf in other contexts (for instance the fzf fish plugin or something like git branch | fzf), it works correctly.
I have verified the above behaviour with 2 terminals, kitty and uxterm.
Additionally, if I redirect the output of the bw + jq command to a file and then open it with fzf, it works fine.
bw list items | jq -r '.[] | [.name, .login.username // "", .id] | @tsv' > items.txt
less items.txt | fzf

Closing the issue. The solution is to use the --sync flag to wait for the bw command to complete.


(BOLT-786) Change bolt-server port to 52658

This sets the bolt-server port higher since it's an internal tool

I've also updated https://confluence.puppetlabs.com/display/ENG/Choosing+a+port+for+services

Because this is in the dynamic port range, I'm concerned about it possibly conflicting with a port that might be open for some outbound connection. Not sure whether that's a realistic concern or not?

On CentOS 7 and Ubuntu 18.04, the dynamic range appears to be 32768-60999. So, using that and PE's traditional ActiveMQ setting (61613), maybe we should use 62658.

Waiting for CLA signature by @lucywyman
@lucywyman - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

Found by catting out /proc/sys/net/ipv4/ip_local_port.


Try joinCohorts using real db

13/11/2023 (prior to adding more arguments): Worked fine against CPRD GOLD dataset


Running rails test with JUnitTestReporter doesn't generate a file

When I run the following:
rails test test/some-test.rb
Everything works as expected.
When I run:
rails test
No file is generated in test/reports.
require 'minitest/reporters'
Minitest::Reporters.use!(
  [Minitest::Reporters::SpecReporter.new(color: true), Minitest::Reporters::JUnitReporter.new(single_file: true)],
  ENV,
  Minitest.backtrace_filter
)

Using minitest 1.4.2

This issue is pretty old, and I'm not able to reproduce. I will close for now, but I'm happy to take another look if this is still an issue and reproduction steps can be provided.


PoW mining error

Test:

Created two testnet nodes
Started PoW mining on one node
Error log:

2017-06-26 18:14:45 CreateNewBlock: Failed to detect masternode to pay
2017-06-26 18:14:45 CreateNewBlock(): total size 1000
2017-06-26 18:14:45 ERROR: CheckTransaction() : txout.nValue negative
2017-06-26 18:14:45 ERROR: CheckBlock() : CheckTransaction failed
2017-06-26 18:14:45 QuarkMiner runtime error: CreateNewBlock() : TestBlockValidity failed
Notes:

This is block 1 on testnet (before PoS and Masternode payments start), so PoW should work as usual
Masternode payments should start at a specific future block (add new nMasternodePaymentStartBlock in chainparams)

same error for me

Hey,
I think this is something related to miner.cpp file. Please check the code present in that. Here is the link which can point out if there is any different. Add the code which are in read. and remove those which are in green.
https://github.com/birake/birakecoin/commit/a31ee1889197b3344af7f0b205eb95dda3d2c90f
The above link is from BirakeCoin.
Let me know if this solves the issue.

Please check above message and let me know if that solve the issue.

Test:

Created two testnet nodes
Started PoW mining on one node
Error log:

2017-06-26 18:14:45 CreateNewBlock: Failed to detect masternode to pay
2017-06-26 18:14:45 CreateNewBlock(): total size 1000
2017-06-26 18:14:45 ERROR: CheckTransaction() : txout.nValue negative
2017-06-26 18:14:45 ERROR: CheckBlock() : CheckTransaction failed
2017-06-26 18:14:45 QuarkMiner runtime error: CreateNewBlock() : TestBlockValidity failed
Notes:

This is block 1 on testnet (before PoS and Masternode payments start), so PoW should work as usual
Masternode payments should start at a specific future block (add new nMasternodePaymentStartBlock in chainparams)


Php8.2

Problem

Description of why you made this PR

Solution

And how do you fix that problem

PR Status

[ ] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!testme

@ericgaspar I didn't notice you've also added an upgrade to php 8.2. The problem is lionwiki is not compatible with php 8.2. It works with 8.1 (but with a few problems), and the best is with php 7.4
After the upgrade, the home page of the wiki is totally blank (the linter test cannot see this it seems). I'll reverse it to php 7.4 because it breaks all current installations.

it's a plugin located into plugins which causes the error, I'm investigating it

it should be fixed now

there are still problems with php8.2, requiring users to manually update some configuration files. It's better to stay with php7.4


Fix nil pointer exception in spanner_store.go

This is a fix for issue https://github.com/cloudstateio/cloudstate/issues/533.

I was able to reproduce the problem.  This fix made it go away.

Tests failed with


update lodash version

This PR is related to this issue I was having: https://github.com/istarkov/google-map-react/issues/113
Turned out this issue was specific to my building process (some weird bug), but I think that'd be good to update lodash version to 4.x

@istarkov code updated.

Thank you!!!

@istarkov could you please tell me when you publish this update?
I'll update my package.json as well :D

Wait for npm install :-) will finish.

<EMAIL_ADDRESS>

thanks!


Retention policies and documentation

The pull requests corrects the way retention policies were handled before. A working example is added to the README.md. In order to make it easier to differentiate between purge jobs, garbage collection and retention policies a description where to find each in the Web UI is added.

I've tested this in our local environment. The retention policy was created. It looks like I cannot edit it. Is this expected?
I'm also not able to add another rule to the project which already has a (provisioned) retention policy.
Maybe this happens since the policy was provisioned?
Also no schedule is visible:

If I try to add a retention policy manually to another project, I'm also not able to change the policy. But I can create further policies.
Maybe the Harbor API can help here?

I've tested this in our local environment. The retention policy was created. It looks like I cannot edit it. Is this expected? I'm also not able to add another rule to the project which already has a (provisioned) retention policy. Maybe this happens since the policy was provisioned?

Now this is definitely unexpected. After closer inspection this looks like an error of the Web User Interface as the following error regarding internationalization appears in the Web Debug Console.

However, after manual deletion of all retention policies these errors don't appear anymore and additional retention policies can be added (manually). Which hints, that there is a wrong parameter in the used retention policy.

I could confirm that something was wrong in the previous retention policy. Harbor API seems to accept faulty / incomplete retention policies without returning any kind of error.
The precious retention policy definition
{
  "scope": {
    "level": "project",
    "ref": 2
  },
  "rules": [
    {
      "template": "always",
      "tag_selectors": [
        {
          "decoration": "matches",
          "pattern": "master"
        }
      ],
      "scope_selectors":  {
        "repository": [
          {
            "kind": "doublestar",
            "decoration": "repoMatches",
            "pattern": "**"
          }
        ]
      }
    }
  ],
  "trigger": {
    "settings": {
      "cron": "0 0 0 * * *"
    }
  }
}

is accepted by Harbor API and partially shown in the Web UI. But it leads to the previously mentioned problems like not being able to edit and add new retention policies.
The new retention policy definition
{
  "algorithm": "or",
  "scope": {
    "level": "project",
    "ref": 2
  },
  "rules": [
    {
      "action": "retain",
      "template": "always",
      "tag_selectors": [
        {
          "decoration": "matches",
          "kind": "doublestar",
          "pattern": "**"
        }
      ],
      "scope_selectors":  {
        "repository": [
          {
            "decoration": "repoMatches",
            "kind": "doublestar",
            "pattern": "**"
          }
        ]
      }
    }
  ],
  "trigger": {
    "kind": "Schedule",
    "settings": {
      "cron": "0 0 0 * * *"
    }
  }
}

works as expected and is correctly displayed in the Web UI. It is possible to edit this retention policy and also to add new ones.
Unfortunately, the documentation of harbor only describes how to use the Web UI and what parameters can be added to retention policies in the /devcenter. I didn't find a documentation of what values are valid for which parameters.

I could confirm that something was wrong in the previous retention policy. Harbor API seems to accept faulty / incomplete retention policies without returning any kind of error.
The precious retention policy definition
{
  "scope": {
    "level": "project",
    "ref": 2
  },
  "rules": [
    {
      "template": "always",
      "tag_selectors": [
        {
          "decoration": "matches",
          "pattern": "master"
        }
      ],
      "scope_selectors":  {
        "repository": [
          {
            "kind": "doublestar",
            "decoration": "repoMatches",
            "pattern": "**"
          }
        ]
      }
    }
  ],
  "trigger": {
    "settings": {
      "cron": "0 0 0 * * *"
    }
  }
}

is accepted by Harbor API and partially shown in the Web UI. But it leads to the previously mentioned problems like not being able to edit and add new retention policies.
The new retention policy definition
{
  "algorithm": "or",
  "scope": {
    "level": "project",
    "ref": 2
  },
  "rules": [
    {
      "action": "retain",
      "template": "always",
      "tag_selectors": [
        {
          "decoration": "matches",
          "kind": "doublestar",
          "pattern": "**"
        }
      ],
      "scope_selectors":  {
        "repository": [
          {
            "decoration": "repoMatches",
            "kind": "doublestar",
            "pattern": "**"
          }
        ]
      }
    }
  ],
  "trigger": {
    "kind": "Schedule",
    "settings": {
      "cron": "0 0 0 * * *"
    }
  }
}

works as expected and is correctly displayed in the Web UI. It is possible to edit this retention policy and also to add new ones.
Unfortunately, the documentation of harbor only describes how to use the Web UI and what parameters can be added to retention policies in the /devcenter. I didn't find a documentation of what values are valid for which parameters.

Thanks for your investigation @peters-david!
In some cases the examples in the Swagger UI of the Harbor API might be helpful.
Or creating a retention-policy from within the UI and get them from the API to see the json object generated.
But just as thoughts.

I tried explicitly setting the id for each project, but that doesn't work.

One optional thought:
Since there could be multiple retention policies for multiple projects:
Should we print a line for each created/updated retention policy as we did for e.g. projects?

@peters-david One optional thought: Since there could be multiple retention policies for multiple projects: Should we print a line for each created/updated retention policy as we did for e.g. projects?

A line with reference to the project id is now printed for each retention policy.


cherry-pick #1528 (bump kind node version) to main

This PR takes #1528 (which is a fix for our integration tests) that went to next and cherry-picks it over to main in order to resolve CI failures blocking other PRs from being merged.

I'm not sure this is the ONLY commit we need to fix the integration tests though: we also need the updated KIND version itself which was a few days ago.

I'm not sure this is the ONLY commit we need to fix the integration tests though: we also need the updated KIND version itself which was a few days ago.

I've cherry-picked 2 more commits that update kind. Let's see if that's enough.


Update financial-intuition.xml

Adding XML info for 3 new episodes.

Additions

Removals

Changes

How to test this PR

Screenshots
Notes and todos

Checklist

[ ] PR has an informative and human-readable title

PR titles are used to generate the change log in releases; good ones make that easier to scan.
Consider prefixing, e.g., "Mega Menu: fix layout bug", or "Docs: Update Docker installation instructions".

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code follows the standards laid out in the CFPB development guidelines
[ ] Future todos are captured in comments and/or tickets
[ ] Project documentation has been updated, potentially one or more of:

This repo’s docs (edit the files in the /docs folder) – for basic, close-to-the-code docs on working with this repo
CFGOV/platform wiki on GHE – for internal CFPB developer guidance
CFPB/hubcap wiki on GHE – for internal CFPB design and content guidance

Front-end testing

Browser testing
Visually tested in the following supported browsers:

[ ] Firefox
[ ] Chrome
[ ] Safari
[ ] Edge 18 (the last Edge prior to it switching to Chromium)
[ ] Internet Explorer 11 and 8 (via emulation in 11's dev tools)
[ ] Safari on iOS
[ ] Chrome on Android

Accessibility

[ ] Keyboard friendly (navigable with tab, space, enter, arrow keys, etc.)
[ ] Screen reader friendly
[ ] Does not introduce new errors or warnings in WAVE

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Does not introduce new lint warnings
[ ] Flexible from small to large screens

@niqjohnson tagging you into this PR. note that this shouldn't go live until 4 PM EST alongside the podcast pages/files themselves

To my eye this is good to go at (or after) the 4PM official publication of the files onto the website


Turn off Windows Test step (#18684)

Turn off Windows Tests in release branch since agent pool is expired.

merging to fix build break.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14797

Relevant Lines:
29111

💛  - Coveralls


Update Supabase Compose to Newest Images

Update Supabase Compose to Newest Images used at Supabase self host
Added some commented lines in Auth section for common Oauth variables

This will be fixed in the upcoming version.

This will be fixed in the upcoming version.


Wrong result when applying aggregation function on series with * and where clause

There is an error with the result of aggregation on series with * and where clause.
Data:

Select result:

The value of count(root.ln.wf02.wt02.temperature) should be 21 but it turned out to be 5 according to result of the select count(temperature) from root.ln.*.* where temperature > 50.0. The error also happened with regard to the avg function.

i just do what you do, but i can't find this wrong
update your iotdb version and try again

i just do what you do, but i can't find this wrong
update your iotdb version and try again

I have updated my iotdb code to the latest version lol. It seems that you do not have data in root.ln.wf01.wt01.temperature, root.ln.wf01.wt02.temperature, root.ln.wf02.wt01.temperature? I initialize my data in this way and have 4 time series:

you are right, it seems bug

It seems that there is not an approach to selecting the count of data points whose value > 50 of each timeseries respectively in one sql?
As far as I know, you are right.

Maybe you can try select temperature from root.ln.*.* where temperature > 50 align by device.
Align by device will process the measurement and filter by each device respectively, the sql above will be turned to four sub-query and concat the result finally:
select temperature from root.ln.wf01.wt01  where temperature > 50
select temperature from root.ln.wf01.wt02  where temperature > 50
select temperature from root.ln.wf02.wt01  where temperature > 50
select temperature from root.ln.wf02.wt02  where temperature > 50
But it uses the relation table structure, which is different from ordinary query.


Refactor Name trait

Refactor Name trait to better handle qualified names.

Just closed and reopened to trigger a CI build.

Great Work @anfark! @phischu could you maybe check whether this might be problematic with your LLVM branch?

@anfark It looks like you changes broke some things. Could you check the errors in the CI build? If you have any questions, feel free to ask.


[WIP] New store group

#141 #151
What is this?
A new StoreGroup implementation that is inspired by CQRS.
I've tried this implementation in https://github.com/azu/almin-cqrs-example/pull/2
Why it is needed?
From #141

We have two StoreGroups.

https://github.com/almin/almin/blob/master/src/UILayer/StoreGroup.ts

Always Async
Cache State

https://github.com/almin/almin/blob/master/src/UILayer/QueuedStoreGroup.ts

QueuedStoreGroup work as Sync or Async.
QueuedStoreGroup prefer strict design than ./StoreGroup.js
QueuedStoreGroup not allow to change stores directly.
Always change stores via execution of UseCase.
QueuedStoreGroup has not cache state.

StoreGroup feature depended on application architecture.
Two StoreGroup make user confuse.

We will provide a single StoreGroup in the future.
Existing two StoreGroup(StoreGroup/QueuedStoreGroup) will be separeted packages.
It reduce file size and make almin simple.
Current Status

[ ] Add StoreGroup implementation as optional to almin
[ ] Add tests
[ ] Store manage changing of state. shouldStateUpdate(prevState, nextState)

Peff
$ NODE_ENV=production node index.js
0.9 x 583 ops/sec ±23.68% (26 runs sampled)
current x 631 ops/sec ±20.88% (32 runs sampled)
# CQRSStoreGroup