JSON Response Performance

I have a JSON response, about 700,000 characters. I stringify it, then compress. The compression takes about 11s.
However, when I paste that same stringifed text into a textbox, grab the .value, then compress, it only takes about 1s.
Any idea why?

My first guess is that the extra 10 seconds are spent outside the compression. Can you make a jsfiddle out of it so that I can see your code in action?

I have a jsfiddle that grabs data from a source and then compresses it.
One of the URLS (static json file) compresses very quickly (< 1000ms).
The dynamic url compresses much slower (~7500ms).
Switch between the two URL variables to see the difference.
http://jsfiddle.net/theur7nd/2/
Thanks for your help.

I've slightly modified your jsfiddle to add the size of the input: http://jsfiddle.net/u52ujty5/
What I see from my computer (Chromium - Linux) :

With dynamicEndPoint: Done in: 508 for 867331 bytes
With staticJSONFile: Done in: 507 for 785159 bytes

This looks pretty reasonable to me... Firefox exhibits the same behavior.
What is the config you're using? (OS/browser)

OOI, the URL for the dynamic end point has ?time=?time= ... I assume that this has no effect.

I see similar results now as well.
Thanks for your time on this. You know, our API team actually updated the dynamic response within the last few days and now instead of 30s, it's almost instant, I think when it was taking 30s to pull the response, that's when the compression was taking 10s longer, not sure why.

Allright, thanks for the feedback.


No matching distribution found for tensorflow==1.11.0 (from keras-pandas)

System information:
- OS Platform and Distribution: Ubuntu 16.04.6 LTS
- Python version: Python 3.7.2, Anaconda 4.6.14
- Exact command to reproduce: pip install -U keras-pandas

Problem description
Hi there,
I'm trying to install keras-pandas but I get this error:
ERROR: Could not find a version that satisfies the requirement tensorflow==1.11.0 (from keras-pandas) (from versions: 1.13.0rc1, 1.13.0rc2, 1.13.1, 2.0.0a0)
ERROR: No matching distribution found for tensorflow==1.11.0 (from keras-pandas)
I believe this happens because pip does not support tensorflow 1.11.0 anymore.
Does anyone have a solution for this or has faced a similar problem?
Thanks in advance

Same issue here, unforunately haven't found a workaround yet.

Python 3.7.3
MacOS 10.14.5

pip3 install keras-pandas --upgrade
ERROR: Could not find a version that satisfies the requirement tensorflow==1.11.0 (from keras-pandas) (from versions: 1.13.0rc1, 1.13.0rc2, 1.13.1, 1.14.0rc0, 1.14.0rc1, 1.14.0, 2.0.0a0, 2.0.0b0, 2.0.0b1) ERROR: No matching distribution found for tensorflow==1.11.0 (from keras-pandas)

@scrusi @simosini You need tensorflow version 1.11.0 for keras-pandas. Downgrade from python 3.7 to 3.4 (or anything below) and install tensorflow 1.11.0.
I suggest you do this using a virtual environment.


[SD-App] Please add @vcraftjp's M5Stack_Particle_demo

https://github.com/vcraftjp/M5Stack_Particle_demo

The app has been scheduled for rebuild

Compilation of this package failed, it has been labeled as invalid until the source of the problem is identified and addressed

Compilation of this package failed, it has been labeled as invalid until the source of the problem is identified and addressed


Custom Post Type not showing post.next and post.prev

Very strange thing.
I have custom post type with 3 posts in it. Trying to make next-prev navigation for single.twig but
receiving empty array for each of this posts:
[_next:protected] => Array        (             [0] =>          )     [_prev:protected] => Array         (             [0] =>          )
Same code for other wordpress site on same server with custom post type works works like it should!
single.php is default:
$context = Timber::get_context(); $post = Timber::query_post(); $context['post'] = $post; Timber::render( array( 'single-' . $post->ID . '.twig', 'single-' . $post->post_type . '.twig', 'single.twig' ), $context );

Same behavior for standard Post type.

Maybe bug in Polylang, after adding new language, activated translation for custom post type and re-saving all posts problem gone!


IIS Reverse Proxy URL with a plus symbol results in 404

Gitea version (or commit ref): 1.11.0+2-g8efd6b32e
Git version: Git-Scm v2.25.0.windows.1
Operating system: Windows Server 2012 R2
Database (use [x]):

[ ] PostgreSQL
[X] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant (Windows host/IIS Reverse Proxy vs. Unix host)

Log gist: Not Available

Description
If there is a file in repo that contains a "+" symbol, the path will not be found, and will result in an IIS 404, not a Gitea 404. If you rename the file to have an underscore in place of the plus sign (rename the file and git push), the file will download just fine.
Example
I want to download a file located at https://git.my.domain/username/Gitea4Windows/media/branch/master/v1.12/1.12.0+dev-283-gad2642a8a.7z. It will result in IIS 404, not a Gitea 404 screen. If the file was named 1.12.0_dev-283-gad2642a8a.7z, the file would start downloading as expected.
Screenshots
N/A
Likely culprit

How IIS determines the URL string with a "+" symbol in the URL string.

Other
Gitea was compiled with/using the following:

Go v1.13.7 (DL)
Gnumake v4.3 (DL)
Nodejs v13.8.0 (DL)
Npm v6.13.6 (Included with Nodejs)
Git-Scm v2.25.0.windows.1 (DL)

Compiled from source and built using git clone https://github.com/go-gitea/gitea.git&&git checkout release/v1.11&&TAGS="bindata sqlite sqlite_unlock_notify" make build
IIS reverse proxy to localhost on custom port

Just looking for guidance on how to maybe URL escape this if it is an IIS issue.

Check https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/requestfiltering/#attributes

allowDoubleEscaping
If set to true, request filtering will allow URLs with doubly-escaped characters. If set to false, request filtering will deny the request if characters that have been escaped twice are present in URLs.


Explanation of printout/log

Could you briefly explain "Batch", different "loss" and "acc" in the printout?
# more print here
Batch[395/6920] - loss: 0.693503  acc: 56.2500%(9/16)
Batch[400/6920] - loss: 0.729841  acc: 37.5000%(6/16)
Dev  Accuracy:  Evaluation - loss: 0.655496  acc: 62.3853%(544/872)
Test Accuracy:  Evaluation - loss: 0.660529  acc: 61.3399%(1117/1821)
The Current Best Dev Accuracy: 64.7936, and Test Accuracy is :62.8226, locate on 10 epoch.

# more print here
Batch[425/6920] - loss: 0.726647  acc: 50.0000%(8/16)
Batch[430/6920] - loss: 0.720713  acc: 43.7500%(7/16)Model_count 40

Specifically, why it stops at Batch[430/6920] in each epoch? And which "Test Accuracy" should I take at then end of 10 epoch?

FYI, here's my config.cfg (I only select settings that are different from default):
[Model]
CNN = False
LSTM = True

[Optimizer]
Adam = False
SGD = True

[Train]
device = 0
cuda = True
epochs = 10
log_interval = 5

These are some of the problems with the output format


Rails asset pipeline import doesn't work on CDN file

I am in the process of updating my react-rails gem to the most recent version (2.4.4) which only supports React 16.  I updated react-slick as well, but it wasn't working right away.
The issue appears to be the results of this call in the asset pipeline which loads the javascript obtained from the CDN: //= require groups/includes/react-slick.min.
This loaded Slider as an object, and I had to include a var Slider = Slider.default call before I could use Slider.  This is a breaking change and it took me a while to discover this workaround, so I thought I would bring it up here.

We were using es5 module.exports for exporting the slider. Now we're using ES6 module export default statement.
You'll be able to use it with any of the following statements:
import Slider from 'react-slick'
const Slider = require("react-slick").default


Added Bosnian provider

Signed-off-by: Mirza Pasic<EMAIL_ADDRESS>

No feedback, closing.


Change More Info dropdowns back to previous names

CMI Tutorial -> Tutorial
Qiita Tutorial -> Help

This was fixed and deployed in the release-candidate, if it needs more changes please open a new issue.


Add common info to state write

@mobilutz : Thanks for the fixes!
I actually removed my usual instance and created a new one with the adapter from this branch. This worked fine of course :)
The documentation is not really clear how you specify the type when it's basically a mixed type. I understand that the combination of common.type and other attributes could suffice for ioBroker.
I'll try out the new changes soon and report back.

I installed the latest version of this branch and unfortunately, this crashes completely and does not come up anymore:
freeathome.0 | 2022-08-13 14:00:07.059 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
freeathome.0 | 2022-08-13 14:00:07.058 | info | terminating
freeathome.0 | 2022-08-13 14:00:07.051 | error | Cannot convert undefined or null to object
freeathome.0 | 2022-08-13 14:00:07.050 | error | TypeError:  Cannot convert undefined or null to object    at Function.keys  (<anonymous>)    at Freeathome.registerAllDevices  (/opt/iobroker/node_modules/iobroker.freeathome/main.js:44:24)    at  processTicksAndRejections (internal/process/task_queues.js:95:5)
freeathome.0 | 2022-08-13 14:00:07.050 | error | unhandled promise rejection: Cannot convert undefined or null to object
freeathome.0 | 2022-08-13 14:00:07.049 | error | Unhandled  promise rejection. This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch().
freeathome.0 | 2022-08-13 14:00:06.980 | info | Starting free@home API

I currently do not see any property or object which is accessed in comparison to before.
Can it be that with the newest commits it initially goes further and then a device fails which was previously untouched.
Unfortunately, I don't know which device that might be...
Sorry for being so unhelpful.

@guerda I removed some code.
Could you try again.
Looking at the error code you posted, I am certain that it is not related to this change!

Thanks, @mobilutz !
It still immediately crashes, now with different errors.
2022-08-29 10:44:11.247 - info: freeathome.0 (19300) starting. Version 0.0.11 (non-npm: mobilutz/ioBroker.freeathome#refs/heads/ll-add-common-info) in /opt/iobroker/node_modules/iobroker.freeathome, node: v14.19.2, js-controller: 4.0.23
2022-08-29 10:44:11.295 - info: freeathome.0 (19300) Starting free@home API
2022-08-29 10:44:13.145 - info: freeathome.0 (19300) undefined is not a valid state value for id "freeathome.0.undefined.deviceId"
2022-08-29 10:44:13.147 - info: freeathome.0 (19300) undefined is not a valid state value for id "freeathome.0.undefined.deviceId"
2022-08-29 10:44:13.147 - info: freeathome.0 (19300) undefined is not a valid state value for id "freeathome.0.undefined.deviceId"
2022-08-29 10:44:13.150 - error: freeathome.0 (19300) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-08-29 10:44:13.151 - error: freeathome.0 (19300) unhandled promise rejection: Cannot read property 'serialNumber' of undefined
2022-08-29 10:44:13.152 - error: freeathome.0 (19300) TypeError: Cannot read property 'serialNumber' of undefined
at FreeAtHomeApi.addDeviceToioBroker (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:71:37)
at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:65:22)
at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:91:29)
at Client.emit (events.js:412:35)
at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:28
at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-08-29 10:44:13.152 - error: freeathome.0 (19300) Cannot read property 'serialNumber' of undefined
2022-08-29 10:44:13.154 - error: freeathome.0 (19300) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-08-29 10:44:13.154 - error: freeathome.0 (19300) unhandled promise rejection: The id is empty! Please provide a valid id.
2022-08-29 10:44:13.157 - error: freeathome.0 (19300) Error: The id is empty! Please provide a valid id.
at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/utils.js:114:19)
at Freeathome.setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:3181:23)
at FreeAtHomeApi.addDeviceToioBroker (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:72:22)
at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:65:22)
at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:91:29)
at Client.emit (events.js:412:35)
at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:28
at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-08-29 10:44:13.158 - error: freeathome.0 (19300) The id is empty! Please provide a valid id.
2022-08-29 10:44:13.158 - error: freeathome.0 (19300) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-08-29 10:44:13.159 - error: freeathome.0 (19300) unhandled promise rejection: The id is empty! Please provide a valid id.
2022-08-29 10:44:13.160 - error: freeathome.0 (19300) Error: The id is empty! Please provide a valid id.
at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/utils.js:114:19)
at Freeathome.setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:3181:23)
at FreeAtHomeApi.addDeviceToioBroker (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:72:22)
at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:65:22)
at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:91:29)
at Client.emit (events.js:412:35)
at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:28
at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-08-29 10:44:13.160 - error: freeathome.0 (19300) The id is empty! Please provide a valid id.
2022-08-29 10:44:13.161 - error: freeathome.0 (19300) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-08-29 10:44:13.161 - error: freeathome.0 (19300) unhandled promise rejection: The id is empty! Please provide a valid id.
2022-08-29 10:44:13.162 - error: freeathome.0 (19300) Error: The id is empty! Please provide a valid id.
at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/utils.js:114:19)
at Freeathome.setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:3181:23)
at FreeAtHomeApi.addDeviceToioBroker (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:72:22)
at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:65:22)
at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:91:29)
at Client.emit (events.js:412:35)
at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:28
at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-08-29 10:44:13.162 - error: freeathome.0 (19300) The id is empty! Please provide a valid id.
2022-08-29 10:44:13.173 - info: freeathome.0 (19300) terminating
2022-08-29 10:44:13.174 - warn: freeathome.0 (19300) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-08-29 10:44:13.738 - error: host.0bec687dd865 instance system.adapter.freeathome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-08-29 10:44:23.728 - info: daikin.1 (17604) Daikin Device initialized with Error :Error occured: Error while communicating with Daikin device: EHOSTUNREACH
2022-08-29 10:44:23.729 - info: daikin.1 (17604) Retry init in 60 seconds

During the installation, the following warnings came up:
npm WARN deprecated<EMAIL_ADDRESS>Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410

npm WARN deprecated<EMAIL_ADDRESS>Potential security vulnerability fixed in 0.13.1 - see https://github.com/xmppjs/xmpp.js/pull/936

npm WARN deprecated<EMAIL_ADDRESS>Critical security bug fixed in v0.12.1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):

Maybe this is less important and can be tackled later.

@guerda I finally got around to creating a dedicated testing instance inside docker to test out my changes.
I added this branches adapter, and did not see any errors.
I will merge this, and update the adapter.

Sounds good, I assume it is a config error on my installation.


front page row alignment

The Issue
row doesnt adjust for smaller app window sizes and chops off end of last cards
Steps to reproduce

open the app
shrink it a little or a lot
scroll the end of row and it starts cut it off

Expected behaviour
cards should adjust and not be cut off
Actual behaviour
cards dont adjust and get cut off
System Configuration

LBRY Daemon version:
LBRY App version: v0.17.0
LBRY Installation ID:
Operating system: windows

Screenshots

while this is definitely a valid issue, it is going to be handled via the homepage redesign https://github.com/lbryio/lbry-app/issues/849


Update the document when few documents hash changes

Describe the bug
https://www.linkedin.com/feed/update/urn:li:activity:7255292022444478465?commentUrn=urn%3Ali%3Acomment%3A(activity%3A7255292022444478465%2C7255646446870278145)&replyUrn=urn%3Ali%3Acomment%3A(activity%3A7255292022444478465%2C7255673413741006850)&dashCommentUrn=urn%3Ali%3Afsd_comment%3A(7255646446870278145%2Curn%3Ali%3Aactivity%3A7255292022444478465)&dashReplyUrn=urn%3Ali%3Afsd_comment%3A(7255673413741006850%2Curn%3Ali%3Aactivity%3A7255292022444478465)
To Reproduce

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. macOS, Linux]
JS Runtime / Framework / Bundler (select all applicable)
[x] Node.js
[ ] Deno
[ ] Bun
[ ] Next.js
[ ] ESBuild
[ ] Rollup
[ ] Webpack
[ ] Turbopack
[ ] Vite
[ ] Waku
[ ] Edge Runtime
[ ] AWS Lambda
[ ] Cloudflare Worker
[ ] Others (please elaborate on this)
Version latest

Additional context
Add any other context about the problem here.

I read the source code and we have exactly same logic as python. So I think this is not a bug


HDDS-11023. Recon Disk Usage null conditions not handled properly for…

What changes were proposed in this pull request?
To avoid null conditions on Disk Usage page
Please describe your PR in detail:
When Recon was intializing on Disk Usage page we were getting failures as values are not mapped properly so to avoid such conditions added checks.
What is the link to the Apache JIRA
(https://issues.apache.org/jira/browse/HDDS-11023)
How was this patch tested?
Manually
Before this PR

With this Patch

@devabhishekpal @dombizita @devmadhuu @ArafatKhan2198
Can you review this pr

Thanks @smitajoshi12 , the patch looks good to me now.
Please do take a look at @ArafatKhan2198's comment for replica=false and raise the JIRA.

@devabhishekpal
It is already raised

Thanks for working on this patch, @smitajoshi12 I appreciate you catching this issue and implementing the necessary changes. However, I believe we can present the information displayed to the user about Namespace initialization in a much clearer way, as the Namespace can be in initialization mode for two specific reasons:

The metadata is too large and is taking time to initialize.
The OM snapshot has not yet been fetched from the OM.

It's important for the user to know that there is no problem with the data; rather, there is just a delay in building the NSSummary. Instead of having the user click the "Show Metadata for Current Path" button, we should display a pop-up message. This message should not be an alert but a simple notification indicating that the state is initializing and that they need to wait.
Additionally, the error message shown in the screenshot can be improved to something more user-friendly like:
"Metadata Initialization: The metadata is currently initializing. Please wait a moment and try again later.”

Thanks for working on this patch, @smitajoshi12 I appreciate you catching this issue and implementing the necessary changes. However, I believe we can present the information displayed to the user about Namespace initialization in a much clearer way, as the Namespace can be in initialization mode for two specific reasons:

The metadata is too large and is taking time to initialize.
The OM snapshot has not yet been fetched from the OM.

It's important for the user to know that there is no problem with the data; rather, there is just a delay in building the NSSummary. Instead of having the user click the "Show Metadata for Current Path" button, we should display a pop-up message. This message should not be an alert but a simple notification indicating that the state is initializing and that they need to wait.
Additionally, the error message shown in the screenshot can be improved to something more user-friendly like:
"Metadata Initialization: The metadata is currently initializing. Please wait a moment and try again later.”

@ArafatKhan2198
Completed  Changes suggested by you attached screenshot with Info Notification

@devabhishekpal Can you please go through your comments and resolve them if they have been fixed in the patch.

@ArafatKhan2198
Completed all changes can you look merge this PR.

@SmitaJoshi12 Most of the changes look good, but I noticed something odd while testing this patch on a cluster. When there is supposed to be no data in the cluster except for a volume named S3V, clicking the "Show Metadata" button should display the NSSummary for the root ("/") path. However, we're encountering an error instead. I'm not sure if this issue was introduced by this patch, but could you please look into it as well?

@smitajoshi12 Most of the changes look good, but I noticed something odd while testing this patch on a cluster. When there is supposed to be no data in the cluster except for a volume named S3V, clicking the "Show Metadata" button should display the NSSummary for the root ("/") path. However, we're encountering an error instead. I'm not sure if this issue was introduced by this patch, but could you please look into it as well?

@ArafatKhan2198  Checked Old code for variable syntax name is same.
Might be issue API Response and UI Code are different for handling syntax summaryResponse.objectInfo.replicationConfig.replicationFactor if you have response can you share with me.

@smitajoshi12 Most of the changes look good, but I noticed something odd while testing this patch on a cluster. When there is supposed to be no data in the cluster except for a volume named S3V, clicking the "Show Metadata" button should display the NSSummary for the root ("/") path. However, we're encountering an error instead. I'm not sure if this issue was introduced by this patch, but could you please look into it as well?

@ArafatKhan2198 @devpalabhishek Optional Chaining not working summaryResponse.objectInfo?.replicationConfig?.replicationFactor !== -1 Instead -1 need to check conditions for undefined also
{ "path": "", "type": "ROOT", "countStats": { "numVolume": 1, "numBucket": 0, "numDir": 0, "numKey": 0 }, "objectInfo": { "metadata": null, "name": null, "quotaInBytes": 0, "quotaInNamespace": 0, "usedNamespace": 0, "creationTime": 0, "modificationTime": 0, "acls": null }, "status": "OK" }

@ArafatKhan2198  Thanks for pointing out undefined condition. In Latest commit I. have handled both undefined and -1 condition from API response.


feat: add pete911/jwt

pete911/jwt: jwt cli to decode and encode jwt tokens
$ aqua g -i pete911/jwt

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ jwt
jwt utilities

Usage:
  jwt [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  decode      decode jwt token
  encode      encode jwt token
  help        Help about any command
  version     jwt cli version

Flags:
  -h, --help     help for jwt
      --silent   suppress logs (warn, debug, ...)

Use "jwt [command] --help" for more information about a command.

Thanks!

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.137.0


Toc with mulitple pages

Hey, I'm trying to make a pdf with multiple pages where the TOC can be anywhere, so i add multiple pages to the pdf and at some point i add the TOC ($pdf->addToc())
For a simple test i tried to use this
$pdf->addPage("
H1

h2

H22
");
$pdf->addPage("
H23
");
$pdf->addToc(array('toc-header-text' => 'Kazalo'));

The result is not what i'd expect

The 2nd h2 was added as a new h1 in the new page.
Is there any way to fix this?

This is nothing we can fix here. It's an issue of wkhtmltopdf itself.


Inconsistent SKU quantities

As mentioned in https://github.com/OpenBazaar/openbazaar-go/pull/1728#issuecomment-536868986, seeing inconsistent SKU quantities from GET /ob/listing/:slug and GET /ob/listing/ipfs/:hash.

The two endpoints are intended for local and remote listing lookup. We also removed publishing the inventory to the network because it was unreliable. Due to these two things, the remote lookup routine (specifically GET /ob/listing/ipfs/:hash) will never have the correct quantity value as the data isn't there to be included.
We have three options for proceeding on this:

Go back and fix the inventory publishing to be reliable and include the data
Improve GET /ob/listing/ipfs/:hash to check if the hash is a local listing and return the local inventory result (understanding this will not fix the case where the hash is of a remote listing).
Accept this shortcoming with the expectation that inventory has "failed" and we'd rather remove it than attempt any improvement at this time.

How should we proceed? @drwasho @jjeffryes @cpacia

There was a lot of discussion about how the inventory might be improved. From this discussion I think it's clear that remote inventory is not considered during the buyer's checkout process today and is probably something we can resolve after the ETH release.
This will no longer be a launch blocker and can be reconsidered later.


Remove description, add fields to proposal for notification template

Remove description from Presentation model
Add speaker and additional_speakers to the notification template context
Change subject to a template so we can render variables
Added the ResultNotification model to admin
Pin Django version in requirements

How to test:

Create a notification template in /admin/ with variables in both the subject and the body.
With recent copy of the database, in admin interface go to MiniConf Proposals and select 200, OpenRadio MiniConf
Remove pending speaker and change additional speaker from Ben to 'Al Furnace' (my test account going to my gmail)
In the review page for the miniconf, bring up the Open Radio miniconf
change the status from 'undecided' to 'accept'
Click Result Notification
Select the template you made from the list and tick the miniconf, click next
Review the template, click next

Should have the following result:

In admin interface, you should see a new entry in ResultNotification in the Reviews section
In admin interface you should see a new Presentation in the Schedule section

You can keep sending out result notifications by using the above method, even if a notification has already been sent.

Otherwise looks good! Go for it.


arkade: 0.9.23 -> 0.9.27

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/alexellis/arkade/releases.
meta.description for arkade is: Open Source Kubernetes Marketplace
meta.homepage for arkade is: https://github.com/alexellis/arkade
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.27 with grep in /nix/store/88rglmqcvpasc9883h14d9c4drgrzj3b-arkade-0.9.27
found 0.9.27 in filename of file in /nix/store/88rglmqcvpasc9883h14d9c4drgrzj3b-arkade-0.9.27

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
arkade

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

arkade

Maintainer pings
cc @welteki @techknowlogick for testing.

Result of nixpkgs-review pr 250695 run on x86_64-linux 1

1 package built:

arkade

Needs a rebase because of merge conflict 👀

closing in favour of https://github.com/NixOS/nixpkgs/pull/250806


Config functions need updating

EDMC version 5.0.0-beta1 changes config.py significantly. config.get() and config.getint() are now depreciated. Instead, config.get_str() and config.get_int() respectively should be used instead.
Simply changing the name of the functions would be the easy solution but would prevent the plugin from being used on older versions. I could use a try except to still allow the plugin to be used on both old and new versions...

There's a function to check the core EDMC version. I could use that instead of try except.


feat: add prometheus to docker-compose

Problem
We'd like to make prometheus stats available to
devs when testing locally.
Solution
Add Prometheus server to docker-compse.
This makes the dashboard available on localhost:9090.
Please test it out! It's super cool :)

How to use Prometheus
Ask Infra, I'm a prometheus noob. But here's a screenshot:

If you click the "world" button you can select from available metrics. Then click "execute"

Hmm I'm not sure it works properly on my machine, as I don't have many proposed metrics, and some are empty (such as "up"). Did you add the ocaml_gc_major_words yourself?

@aguillon the GC stuff comes from https://GitHub.com/marigold-dev/prometheus-web

@ulrikstrid: my bad, it wasn't working but now it is.


Installed integration in November and worked perfectly. When I updated to  HA 2024.12 a number of entities became unavailable, in particular the climate (thermostat) entities.
Tried uninstalling and reinstalling.
Any suggestions?
I activiated debug logging and have attached text file.
flair debug log.txt

Can you provide screenshots of the Flair "devices" in Home Assistant and point out the specific entities that your issue is with? This will help me focus in on the data within the debug log.

Hi,Have attached some screen shots.Below is explanation of setup.Have 1 Flair Bridge 4 Flair Pucks.Each Puck in a roomRooms1. Andrea Bedroom - 1 vent2. Guest Bed Room - 1 vent3. Study - 1 vent4. Living - 4 vents (Living Left, Living Right, Kitchen, LandingIn each Device - Room - all 4 entities are unavailable.Device Pucks  1 entity unavailable (13 available) eg.  number.andrea_bedroom_temperature_calibrationDevice Vent  - all entities available - 8.Allan Rich0418 176 @.*** 19 Dec 2024, at 4:58 PM, Dr. Drinovac @.***> wrote:
Can you provide screenshots of the Flair "devices" in Home Assistant and point out the specific entities that your issue is with? This will help me focus in on the data within the debug log.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Can you retry doing that on GitHub itself. Replying by email seems to have messed up formatting and no screenshots included.

But just to give you preliminary findings - all of your room climate entities are unavailable because your structure mode is set to manual according to the debug log. If you go to the flair app, you'll notice that you can't set a room temperature when your mode is Manual instead of Auto.
If you check the documentation on github, I make note of why the entity is unavailable in certain scenarios.

To you and yours as well!


How to associate custom extension with content type? e.g file.njs enable for Javascript/Nodejs debug

Prerequisites

[x] Can you reproduce the problem with Debug -> Reload Without Extensions?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?
[x] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
Please include the OS and what version of the OS you're running.
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)

Description: It would seem the file extension drives the debug and helpers that are engaged when a file is opened (Is this accurate?). I searched in the app and online but could not find a way to associate a custom extension with content type. Any nudge is appreciated.
Version: Release 1.11 build 1.11.0-17524 (release 86b5e2d4e)  - Linux

@rudyrockstar Brackets does not have yet have support for debugging NodeJS apps. What you see in the menu Debug->Enable Node Debugging is to debug the Node portions of Brackets that are internal to Brackets.Hope that answers your question.

Thanks


Publish to Microsoft Store

Notes:

Only possible if packaged as MSIX.

See:

How to publish your MSIX package to the Microsoft Store?

Depends on #25.

The Microsoft Store is a pain and a failure. No one cares about this.


[8.x] Add setKeysForSelectQuery method and use it when refreshing model data

This PR is in reference to https://github.com/laravel/framework/issues/34954.
It adds two methods to the base Model class: setKeysForSelectQuery() and getKeyForSelectQuery(). These methods are then used in fresh() and refresh() instead of the existing setKeysForSaveQuery() and getKeyForSaveQuery().

Thanks for the PR. Isn't this a breaking change?

@GrahamCampbell I don't think it is, no. This just addresses a change that was made in #34836. Prior to that, the setKeysForSelectQuery() method was not being called on fresh() or refresh(). That was (for me, anyway) a breaking change. And it seemed semantically incorrect, since refresh() and fresh() are not save queries. @driesvints and @taylorotwell seemed to agree in thread #34954.

I think this looks okay but will need @taylorotwell to verify it.

@GrahamCampbell @adamthehutt @driesvints This is indeed a BC, because this breaks refresh and fresh and pivots and morphpivots again (which my original PR intended to fix). I just composer updated and have tests that are suddenly failing


fatal error C1002: compiler out of heap space in pass 2 when build pip-package for tensorflow 2.9.3 and python 3.9.1 on Windows 10

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.9.3
OS platform and distribution
Windows 10  Version 22H2 (OS Internal Version 19405.3803)
Python version
3.9.1
Bazel version
5.4.1
GCC/compiler version
MSVC 2019
The Path Environment for compiler  is
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\bin\Hostx64\x64
CUDA/cuDNN version
cuDNN 8.1 for Cuda 11.2
Cuda was installed from cuda_11.2.0_460.89_win10.exe
Cudnn for cuda 11.2.0  is from cudnn-11.2-windows-x64-v<IP_ADDRESS>.zip
GPU model and memory
NVIDIA GeForce RTX 3080 ti  12288MiB
Nvidia Driver Version is  546.33
The driver was installed from 546.33-desktop-win10-win11-64bit-international-nsd-dch-whql.exe
Current behavior?
**build tensorflow_cc.dll for tensorflow 2.9.3 ** successfully.
but bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings --local_ram_resources=2048 //tensorflow:tensorflow_cc.dll
**build tensorflow_cc.lib for tensorflow 2.9.3 ** successfully
but bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings --local_ram_resources=2048 //tensorflow:tensorflow_cc_dll_import_lib
**build cpp headers for tensorflow 2.9.3  ** successfully
but bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings --local_ram_resources=2048 //tensorflow:install_headers
but bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings --local_ram_resources=2048  //tensorflow/tools/pip_package:build_pip_package failed because compiler out of heap space in pass 2
try again with more local RAM resources but failed for the same reason
but bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings --local_ram_resources=4096  //tensorflow/tools/pip_package:build_pip_package failed because compiler out of heap space in pass 2
Standalone code to reproduce the issue
but bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings --local_ram_resources=4096 //tensorflow/tools/pip_package:build_pip_package

Relevant log output
**Latest logs are:**
注意: 包含文件:      D:\ndev\tf293_build\hu3sahy6\execroot\org_tensorflow\third_party\eigen3\unsupported\Eigen\CXX11\src/FixedPoint/MatVecProduct.h
注意: 包含文件:     external/mkl_dnn_v1/include\dnnl.h
注意: 包含文件:      D:\ndev\tf293_build\hu3sahy6\execroot\org_tensorflow\external\mkl_dnn_v1\include\oneapi/dnnl/dnnl.h
注意: 包含文件:       bazel-out/x64_windows-opt/bin/external/mkl_dnn_v1/include\oneapi/dnnl/dnnl_config.h
注意: 包含文件:        D:\ndev\tf293_build\hu3sahy6\execroot\org_tensorflow\external\mkl_dnn_v1\include\oneapi/dnnl/dnnl_types.h
注意: 包含文件:       bazel-out/x64_windows-opt/bin/external/mkl_dnn_v1/include\oneapi/dnnl/dnnl_version.h
注意: 包含文件:     .\tensorflow/core/platform/dynamic_annotations.h
注意: 包含文件:      .\tensorflow/core/platform/platform.h
注意: 包含文件:      .\tensorflow/core/platform/default/dynamic_annotations.h
注意: 包含文件:  .\tensorflow/compiler/xla/service/cpu/runtime_lightweight_check.h
D:\ndev\tf293_build\hu3sahy6\execroot\org_tensorflow\external\eigen_archive\Eigen\src\Core\products\GeneralBlockPanelKernel.h(2073) : fatal error C1002: 在第 2 遍中编译器的堆空间 不足
Target //tensorflow/tools/pip_package:build_pip_package failed to build
INFO: Elapsed time: 14994.948s, Critical Path: 2927.75s
INFO: 9275 processes: 66 internal, 9209 local.
FAILED: Build did NOT complete successfully

My configure:
D:\NDev\tensorflow-2.9.3>python ./configure.py
You have bazel 5.4.1 installed.
Please specify the location of python. [Default is C:\Users\Administrator\AppData\Local\Programs\Python\Python39\python.exe]:
Found possible Python library paths:
C:\Users\Administrator\AppData\Local\Programs\Python\Python39\lib\site-packages
Please input the desired Python library path to use.  Default is [C:\Users\Administrator\AppData\Local\Programs\Python\Python39\lib\site-packages]
Do you wish to build TensorFlow with ROCm support? [y/N]: N
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.
Do you wish to build TensorFlow with TensorRT support? [y/N]: n
No TensorRT support will be enabled for TensorFlow.
Found CUDA 11.2 in:
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2/lib/x64

C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2/include

Found cuDNN 8 in:
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2/lib/x64

C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2/include

Please specify a list of comma-separated CUDA compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus. Each capability can be specified as "x.y" or "compute_xy" to include both virtual and binary GPU code, or as "sm_xy" to only include the binary code.
Please note that each additional compute capability significantly increases your build time and binary size, and that TensorFlow only supports compute capabilities >= 3.5 [Default is: 3.5,7.0]: 8.6
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is /arch:AVX]:
Would you like to override eigen strong inline for some C++ compilation to reduce the compilation time? [Y/n]:
Eigen strong inline overridden.
Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]: n
Not configuring the WORKSPACE for Android builds.
Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
    --config=mkl            # Build with MKL support.

    --config=mkl_aarch64    # Build with oneDNN and Compute Library for the Arm Architecture (ACL).

    --config=monolithic     # Config for mostly static monolithic build.

    --config=numa           # Build with NUMA support.

    --config=dynamic_kernels        # (Experimental) Build kernels into separate shared objects.

    --config=v1             # Build with TensorFlow 1 API instead of TF 2 API.

Preconfigured Bazel build configs to DISABLE default on features:
    --config=nogcp          # Disable GCP support.

    --config=nonccl         # Disable NVIDIA NCCL support.

@tricoffee If you're using an older version of the C++ compiler, consider upgrading to a newer version that may have better memory management. Please delete any existing build files and directories to ensure a fresh start. We recommend you to upgrade the TF version instead of the older version. Kindly let us know the update on this?
Thank you!

Upgrade the TF version to 2.1.0 with python 3.10.1 build complete successfully

@tricoffee Thank you for the update!
Could you please make this issue to closed status if it is resolved?
Thank you!

build tensorflow_cc.dll with tensorflow-2.10.0 with python 3.10.1 Linking tensorflow/tensorflow_cc.dll failed: (Exit 1120): link.exe failed: error executing command  @sushreebarsa


chang viewport adapting algorithm.

intro
Request to enable viewport adapting algorithm changing for weex-vue-render. The previous way to adapt different screens is by setting viewport meta in the head. The compatibility in some devices is un-tested and the implementation for this meta in some browsers is not so reliable. What's more, some user-defined components in this changed viewport environment is not working correctly, since those components assume current viewport is a more common value, like device-width, and they draw UI depending on this.
So this pr solved this problem by introducing realtime recalculation for component's styles, which are scaled-up/down value to adapt current device-width, to enable the consistency in all the devices with varies of screens. This pr also solve the problem that the scale values used in  dom.scrollToElement and animation.transition wouldn't adapt to different screens.
This pr also enable runtime autoprefix for styles, which means users don't have to put $processStyle or autoprefixer in their vue-loader config. The render will do this for users automatically and they don't have to worry about it.
changelog:

change viewport adapting algorithm by recalculating styles during runtime.
discard $processStyle and autoprefixer config for vue-loader.
add test cases.

in <style> element,88px will computed to 44px in iPhone6.but inline-style dose not work,and import style like <style src="../style/main.css"></style> dose not work too.

@dongnaebi can you give me a simple demo to show this error with inline style ? I tested in a simple case and got no error found, maybe you have something not mentioned in this case to get this style computing error ? BTW, import src is not valid to use in weex, since it's not a scoped style. You can only use <style scoped> tag in weex.

@MrRaindrop sorry,弄反了，is <style> tag dose not computed.
it's not an error,is inconsistent performance.
I was test it in npm package v0.11.5:
http://dotwe.org/vue/cf99c75bbadfa61c4ae151b4c430ffb4

here somthing I found.
my viewport is <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
if change it to 0.5,it's work fine,but weex.config.env.deviceWidth will be 1500,some calculations based on deviceWidth will be large.

This branch has changed viewport adapting algorithm. So the npm version is out dated (BTW, the latest version on npm is 0.11.2) when this branch is merged, and the device-width will be the viewport size consistently (e.g. 375 for iphone6).
@dongnaebi  In your case I suggest you don't change your viewport. If you want to use a scale based on your design width, such as 750px, you can use <meta name="weex-viewport" content="750">. This would be ok.
You can specify your viewport width to 750px with <meta name="weex-viewport" content="750">. This meta works for all the 0.11.x version of weex-vue-render, what is changed is the adapting algorithm. You shouldn't set the viewport meta as device-width and xx-scale=1 since the env.deviceWidth and env.deviceHeight will be calculated relying on this. What you can change is the weex-viewport meta.

OK,thanks,good man


Making the Duotone Icons only two layers

It would be great if the Duotone icons could be simplified into only being 2 layers. Otherwise when we override stroke width and colour and swap an instance the part of the icons often does not receive the override.

We're considering adding an option to import icons pre-flattened in the next release. This should provide the experience you're looking for. See #10


@microsoft.graph.downloadUrl of copied files does not work initially

Category

[ ] Question
[ ] Documentation issue
[X] Bug

Expected or Desired Behavior

Create a folder with a few plain text files under any SPO site's Documents libary.
Create another folder and copy all the files from the previous folder to the new folder using OneDrive's copy functionality.
Downloading any of the copied files using @microsoft.graph.downloadUrl prepared the the OneDrive Graph API
The file is received and it has the correct content

Observed Behavior
The HTTP response from 3. is 200 but the Content-Length header is set to 0 and no HTTP body is received. This only happens once, and a retry will download the file successfully.
Steps to Reproduce
As described above. Try downloading the files from the second folder and most of the time the first downloading attempts will return no body, Content-Length: 0, and 200 OK. The issue will eventually disappear, likely forever as populating some metadata happens lazily after the first download attempts.

Thanks for your feedback.
Could you please clarify whether the copy in step (2) has completed?
If it has completed, could you please provide a request-id and date/time for requests (3), and ideally (4)?
I'll tag so that our helpful bot will provide more information about request ID's.


Articles webcomics uri

Type

🐛 Bugfix
Value
As much as I can see this is an abstraction, I'd probably like to bring it back in once we have answered the couple questions below.
Now using the same URLs for /webcomics and /articles.
This has two reasons:

So we don't have to think about URIs just yet
I can hijack Wordpresses email / RSS functionality until we figure out what to do with the followers on that platform.

Checklist
All

[x] PR labelled and assigned
[x] Any introduced code complexity has been flagged

If this doesn't make sense as to why I am doing this, come grab me.


UDF for crystallinity map calculation

Returns crystallinity map.
Calculates coefficients for each frame: low values for frames (only zero order peak) which belong to amorphous regions, high values for crystalline frames (zero order peak+periodic non zero order peaks)

Thanks, merged!


Normalize whitespace.

Use 4 spaces consistently. Also, change .editorconfig to reflect this.
See https://github.com/cloudflare/CloudFlare-Wordpress/pull/76/files?w=1 for the non-whitespace diff.

Our editor config is based off the WordPress coding standards:
https://make.wordpress.org/core/handbook/best-practices/coding-standards/
They use tabs which is why we use tabs.
https://core.trac.wordpress.org/attachment/ticket/26429/.editorconfig.patch

But you don't use tabs consistently either.
On Sep 23, 2016 00:56, "John Wineman"<EMAIL_ADDRESS>wrote:

Our editor config is based off the WordPress coding standards:
https://make.wordpress.org/core/handbook/best-practices/coding-standards/
They use tabs which is why we use tabs.
https://core.trac.wordpress.org/attachment/ticket/26429/.
editorconfig.patch
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/CloudFlare-Wordpress/pull/76#issuecomment-249040030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtQNfCLV59oQJG_hUDr1fAU_VqJIhks5qsvmRgaJpZM4KCeRB
.

I know.  We try to format to PSR-2 but WordPress doesn't conform to PSR-2 so it sorta messes everything up.

Idiotic standard if you ask me let alone they still use SVN.
Oh well, just thought I'd make things consistent and trim trailing spaces
too along the way.
On Sep 23, 2016 00:58, "John Wineman"<EMAIL_ADDRESS>wrote:

I know. We try to format to PSR-2 http://www.php-fig.org/psr/psr-2/ but
WordPress doesn't conform to PSR-2 so it sorta messes everything up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/CloudFlare-Wordpress/pull/76#issuecomment-249040486,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtTquYpN2FOOLtIZBYnwzosWFrxC1ks5qsvoMgaJpZM4KCeRB
.

Agreed.  We're debating internally whether to drop support for their .editorconfig and just move back to PSR-2.  We were trying to do things "the wordpress way" as much as possible but sometimes it doesn't seem worth it.
3.0.0 of this plugin had a script that would deploy from git to their SVN too but it was buggy so now we're back to doing manual SVN deploys.
But yeah we rely heavily on composer and PHP namespaces so thats why we now only support PHP 5.3.10+.  The main benefit of this is we can avoid all the WordPress best practices that exist to help you avoid all the global namespace conflicts.


Development without restarting a docker container

Hi guys! This is a great resource overall.
One thing is missing for me.
I want to provide a better development experience for my team using .net core and docker-compose.
Could you provide instructions for setup dotnet watch along with docker containers which won't require restart docker-compose stack each time the code has changed?
Thanks!

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

ID: 1b69a4b5-2003-e7a5-97a3-59e3737ea1ef
Version Independent ID: 0df5f0d7-a2b4-e9b3-9f34-d66cedf418a3
Content: Development workflow for Docker apps
Content Source: docs/standard/microservices-architecture/docker-application-development-process/docker-app-development-workflow.md
Product: dotnet
GitHub Login: @CESARDELATORRE
Microsoft Alias: wiwagn

@CESARDELATORRE @richlander can you comment on this request?

You could start only specific containers when using docker-compose, too.
Like:
$ docker-compose up yourService
to start just yourService and all dependencies required by it.
So if yourService depends on a sql container, the above command would start both the containers.

Hi @roussakov,
I might be getting you wrong but, the way I see it, that could actually hinder your team's work, because every time you execute docker-compose up it's a several minutes wait (>15 min on eShopOnContainers).
I'm a compulsory Ctrl-S maniac so it just would do for me.
Am I missing something here?
Would a CI/CD pipeline that triggers on push to dev branch make more sense?
Hope this helps.

Docker-compose up takes 15 min just the first time you need to compile everything and create all the Docker images. If you just update a single image Docker-compose up takes just 2 minutes or so.
Another approach if you already chose Kubernetes is to use Azure Dev Spaces and deploy a single service to a cluster that already has the rest of the services deployed.

Closing this issue now, as there doesn't seem to be much to add, but feel free to comment.
Will reopen if needed.


About contract action log in cleos

$ cleos multisig propose test '[{"actor": "tequan1", "permission": "active"}]' '[{"actor": "tequan1", "permission": "active"}]' eosio.token issue '{"to": "tequan2", "quantity": "1000.0000 EOS", "memo": ""}' -p tequan2
executed transaction: 4215db090f2e56f4d665296d493b3531ab9c5823715a0776de80fcc0938bf13b  200 bytes  571 us
#    eosio.msig <= eosio.msig::propose          {"proposer":"tequan2","proposal_name":"test","requested":[{"actor":"tequan1","permission":"active"}]...
warning: transaction executed locally, but may not be confirmed by the network yet    ]

like that ,I want to see  complete info about #    eosio.msig <= eosio.msig::propose          {"proposer":"tequan2","proposal_name":"test","requested":[{"actor":"tequan1","permission":"active"}]...
do not ...

you can comment  if( args.size() > 100 ) args = args.substr(0,100) + "..."; of  print_action  in cleos/main.cpp.

Please use -j option

thank you
@firesWu  @taokayan


If an @api-type that doesn't allow options has options, throw an exception.

Throw an exception when options are supplied to a @api-type annotation that doesn't allow options.

@api-type no longer exists.


Order of sensitivites

PyBaMM version - 21.12:
Python version - 3.8.10:

Describe the bug
The order of sensitivities seems to not align correctly when there are multiple sensitivities. The example below shows the sensitivity of terminal voltage SPM to D_n in two cases. Case 1 where only D_n is an input and Case 2 where D_n and b_n (negative electrolyte bruggeman coefficient) are inputs. In Case 2, it appears that the sensitivites of the terminal voltage w.r.t D_n and b_n have been switched. Seems likely a switching of order in either the building of the sensitivity rhs or when extracting from casadi.
To Reproduce
import pybamm
import numpy as np
import matplotlib.pyplot as plt

# Case 1
chemistry = pybamm.parameter_sets.Ecker2015
parameter_values = pybamm.ParameterValues(chemistry=chemistry)
parameter_values["Negative electrode diffusivity [m2.s-1]"] = "[input]"

model = pybamm.lithium_ion.SPM()
sim = pybamm.Simulation(model, parameter_values=parameter_values)

inputs = {
    "Negative electrode diffusivity [m2.s-1]": 1e-13,
}

t_eval = np.linspace(0, 30, 1000)
sim.solve(t_eval=t_eval, inputs=inputs, calculate_sensitivities=True)
sol1 = sim.solution

# Case 2
chemistry = pybamm.parameter_sets.Ecker2015
parameter_values = pybamm.ParameterValues(chemistry=chemistry)
parameter_values["Negative electrode diffusivity [m2.s-1]"] = "[input]"
parameter_values["Negative electrode Bruggeman coefficient (electrolyte)"] = "[input]"

model = pybamm.lithium_ion.SPM()
sim = pybamm.Simulation(model, parameter_values=parameter_values)

inputs = {
    "Negative electrode diffusivity [m2.s-1]": 1e-13,
    "Negative electrode Bruggeman coefficient (electrolyte)": 1.5,
}

sim.solve(t_eval=t_eval, inputs=inputs, calculate_sensitivities=True)
sol2 = sim.solution

# Plot
fig, ax = plt.subplots(2, 1, figsize=(16, 9), sharex=True)
ax[0].plot(
    t_eval,
    sol1["Terminal voltage [V]"].sensitivities[
        "Negative electrode diffusivity [m2.s-1]"
    ],
    label="sol1 D_n",
)
ax[0].plot(
    t_eval,
    sol2["Terminal voltage [V]"].sensitivities[
        "Negative electrode diffusivity [m2.s-1]"
    ],
    linestyle="--",
    label="sol2 D_n",
)

ax[1].plot(
    t_eval,
    sol1["Terminal voltage [V]"].sensitivities[
        "Negative electrode diffusivity [m2.s-1]"
    ],
    label="sol1 D_n",
)
ax[1].plot(
    t_eval,
    sol2["Terminal voltage [V]"].sensitivities[
        "Negative electrode Bruggeman coefficient (electrolyte)"
    ],
    linestyle="--",
    label="sol2 b",
)

ax[0].grid()
ax[1].grid()

ax[0].set_xlabel("Time [s]")
ax[1].set_xlabel("Time [s]")

ax[0].legend()
ax[1].legend()

plt.show()

Expected behaviour
The sensitivity of terminal voltage w.r.t D_n should be independent of the number of other inputs.
Screenshots
Plot generated by above example.

Some further information:
Placing a debug on line 241 of solution.py (end of _extract_explicit_sensitivites) and then printing np.max(sensitivity["Negative electrode diffusivity [m2.s-1]"]) gives a large number greater than zero which corresponds to the sensitivity of the diffusion coefficient. So it seems to be giving the correct order at this point. Looks that the ordering issue arises somewhere within ProcessedVariable


When input is a tensor, the 'axis' is not type checked in tf.concat

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
TF2.8
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Axis must be in the range [-rank(values), rank(values)) written on documentation [https://tensorflow.google.cn/versions/r2.4/api_docs/python/tf/concat#args]. When input is a list of tensor, axis will validate the range. However, when input is a single tensor, axis won't check the range.

Standalone code to reproduce the issue
import tensorflow as tf
t1 = [[[1, 2], [2, 3]], [[4, 4], [5, 3]]]
t2 = [[[7, 4], [8, 4]], [[2, 10], [15, 11]]]
res = tf.concat([t1, t2], -100)
print(res)
'''
tensorflow.python.framework.errors_impl.InvalidArgumentError: ConcatOp : Expected concatenating dimensions in the range [-3, 3), but got -100 [Op:ConcatV2]
'''

Above code will check the validity of axis, but the following code wont.

import tensorflow as tf
results={}
try:
  arg_0 = tf.saturate_cast(tf.random.uniform([2, 4], minval=-256, maxval=257, dtype=tf.int64), dtype=tf.int64)
  axis = -200
  results["res"] = tf.concat(arg_0,axis=axis,)
except Exception as e:
  results["err"] = "Error:"+str(e)
print(results)
'''
{'res': <tf.Tensor: shape=(2, 4), dtype=int64, numpy=
array([[ 140,  236, -151,   66],
       [ 154,   28,  -82,   23]])>}
'''

Relevant log output
No response

I was able to reproduce the issue with Tensorflow 2.8.2 and 2.9.2. Please find the gist here. Thank you!

Our concat "op" requires there be 2+ tensors, and that is where the error checking happens.  If there is only one tensor input, we simply return it and the operation becomes a noop.  It would probably be wasteful to force an additional check/assertion here.

@cantonios So should the documentation separately state the value of axis in the case of only one input tensor? Or add an example to illustate what will happen when input is one tensor.

Why?  I don't think we want it officially part of the API that the axis is ignored when inputing a single tensor.  It is still a user error.  It just is not worth us checking for it since doing so only adds overhead, and we return the correct result if the specified axis was any valid value.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


PP sorting order for upgrades bar not working

Cookie Clicker version: 2.031
Cookie Monster version: 2.031.4
So the option to sort upgrades according to PP does nothing at all. It's probably because of the new update, problem wasn't present yesterday.
Not sure if it's save specific, but here's mine: [encoded data, 7124 characters]%21END%21

Your save seems to work for me. In your current save Cursors and Grandma's are actually number 1 and 2 and as third it shows Antimatted condensers. This makes it seem as if there is not sorting by PP, but it actually does (you can test this by changing to buy 10 or buy 100).
If this is not the case could you check if the console is throwing any errors?

Upgrades, not buildings

Oh I'm sorry! Misread that part. I'll have another look!

Found the bug and think already know what is wrong, sorry for the confusion.
Should be an easy fix, expect a hot fix somewhere tonight!

Ok, thanks!

This has been fixed!


[Feature] Upload progress indicator for artifact upload

Is your feature request related to a problem? Please describe.
When adding a directory to an artifact, it finishes very quickly, e.g.:
wandb: Adding directory to artifact (./../data/COCO/annotations)... Done. 2.5s
However, then the files still need to be uploaded. This is not clear, and it is impossible to see how long it will take to finish.
wandb: Waiting for W&B process to finish, PID 249... (success).
Describe the solution you'd like
Add a progress indicator when uploading/syncing files.

any news about the feature?

this is still a thing?
would be nice to have an upload bar.
using it to upload datasets before training on cluster.
this is the first indicator I'm getting that tells me the artifacts tooling is not a wandb prio and not ideal for our team going forward.

I have raised this feature request once again with our team. This thread will be notified if there are any updates

Hey folks, sorry for the delay, the feature turned out to be surprisingly tricky but we just shipped it in 0.16.2! Here is the PR for reference: https://github.com/wandb/wandb/pull/6497


open edx: dates tab doesn't show all course dates by default

Steps to Reproduce

View a course in Open edX LMS
Click on the dates tab

Expected Behavior

The page will display all important dates in the course including start/end dates and deadlines by default without having to set a flag for each course (see notes below)

Actual Behavior

By default, the dates page will only list the start and end dates
We are currently overriding this functionality by setting a waffle flag as follows:

Go to waffle flag course overrides in the LMS admin: /admin/waffle_utils/waffleflagcourseoverridemodel/
Click Add Waffle Flag Course Override
Add a new flag

Waffle flag: course_experience.relative_dates
Course id: [the course id]
Note: [optional]
Override Choice: force on
Enabled: [checked]

Once set, all dates will appear on the dates tab

Related Issues
https://github.com/mitodl/mitxpro/issues/2330
Screenshot or Screencast

@briangrossman could you please add more details about it? I have tried out different things but could not find that which dates are you referring to here except start or end dates.

@umarmughal824
Sure. Here's some additional info.
In the screenshot above (in the overall description), you can see that the only dates that are shown on the dates tab are the start and end dates.

Here's a screenshot for a date tab for a course that has the course_experience.relative_dates flag (mentioned above) set. Note that it includes the start date, end date, and all the due dates in the course.

Due dates can be set for subsections by clicking on the settings gear for a subsection in the course outline

The key point is that these due dates are not appearing on the dates tab by default. We need to set the course_experience.relative_dates for each course to get them to appear. Ideally, this would work by default without having to set a flag for each individual course.
Hope this helps!

@briangrossman we can define a globa waffle flag for all the courses where it will automatically shows all the dates against each course.
For global waffle, we could go to admin/waffle/flag/

@umarmughal824 Sorry it took me so long to test this. It works great!
I'm closing this. Thanks!


[9.x] Fail queued job with a string message

A shortcut so you can fail a job with a string message instead of manually instantiating an Exception.
class MyJob implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable;

    public function handle()
    {
        // Before:
        $this->fail(new \Exception('Whoops!'));

        // After:
        $this->fail('Whoops!');
    }
}

This seems nice but at least IMO it would be better to throw a custom exception instead of a generic one

The report() and throw_if() helpers can also receive a string message (see https://github.com/laravel/framework/pull/35890). The only difference is they can also receive the FQN of an exception class, like this:
throw_if($hasError, LogicException::class);

Supporting $this->fail(LogicException::class) is probably a good idea to keep things consistent.


Add conditional attr_accessible

For those of who are still on Rails 3 for at least another couple of months.

Reopened with a rebase in #17


[SFT] Fix sft issues

What does this PR do?
This PR fixes minor issues with SFT (in fact I forgot to push the last changes before merging #323 )
cc @lvwerra

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Support VirtualizedList

Great repo!
Could you add support for VirtualizedList?

Yeah shouldn't be too hard. I will try to add it this week or next week :)

Yeah shouldn't be too hard. I will try to add it this week or next week :)

@pdpino  VirtualizedList is a little complicated apparently. Turns out ref setting is not as easy as FlatList/ScrollView. Will need some more digging!! Will get back

I see, thanks for the update!

Hi @vishalnarkhede, just wondering if this is still on your near-term todo list or if you can share some context for someone looking to take this on otherwise. Thanks!


Upgrade django-ckeditor to remove warning

This will just neutralize the warning message, since upgrade to last ckeditor is not really possible. As reported in https://github.com/django-ckeditor/django-ckeditor/issues/761
Whatever, the patch would be easy as upgrading to 6.7.1 here:
https://github.com/sveetch/cookiecutter-bireli/blob/b077e896c0954a52224a842109d2465796f949cc/{{ cookiecutter.project_name }}/composition_repository/ckeditor/requirements.txt#L1
I'm not sure about the CMS ckeditor, i did not see anything about this in changelog but we don't have the warning on it, so it would be nice to just check.

Done in 0.3.13-pre.2


Check if a file contains a string

Simple functions to check if a file contains a string.
I test this checking if a log file contains an email text, but can be used to other scenarios.

Would rather you just include this helper yourself.


CCLayerPanZoom drifts towards anchor point after pinch zoom

Zooming in and zooming out both translate a CCLayerPanZoom layer and its children slightly closer to the CCLayerPanZoom's anchor point, rather than the center of each pinch. I've been able to replicate this behavior with several different CCSprites and CCTMXTiledMaps, as well as an unmodified CCLayerPanZoomTestLayer.
Set a CCLayerPanZoom's anchorPoint to (0,0), add a CCSprite to a CCLayerPanZoom, and repeatedly pinch in and out over the sprite, and the CCLayerPanZoom will drift away from the sprite, towards the lower left corner. Set the anchorPoint to (1,1) and it will drift towards the upper right.

I'm having this issue too with a CCTMXTiledMap within a normal CCLayer. Just repeat zooming with the pinch gesture over and over in small steps and the view will move slowly to the left lower bottom.
Anyway, thanks for this great controller, I appreciate your work very much.


thrift proxy: emit stats when there's a route miss or cluster not found

We currently just reply with exceptions:
https://github.com/envoyproxy/envoy/blob/master/source/extensions/filters/network/thrift_proxy/router/router_impl.cc#L215
I'll send a PR to emit stats as well.
cc: @fishcakez @zuercher

Handled via #9203.


python311Packages.airium: init at 0.2.6

Bidirectional HTML-python translator.
https://gitlab.com/kamichal/airium
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3459

Result of nixpkgs-review pr 285101 run on x86_64-linux 1

2 packages marked as broken and skipped:

python312Packages.airium
python312Packages.airium.dist

2 packages built:

python311Packages.airium
python311Packages.airium.dist


[Suggestion] AutoMessage Function about AnnoucementSystem

What kind of issue is it (Question, Bug, Suggestion, etc)?
Suggestion
In which Minecraft Server Software did this occur?
Bungeecord / Spigot / Sponge
Sugestion:
A Automessage Function to Inform Players on the MC Servers of very importent Annaouncements (Like Server Changes or whatever) from the own Nameless Website
I think a seperat Category in the Announcements can be used for this.

Gonna be added when the new api is out :)!!


rados_ioctx_t should be the same as the one ceph-rados gives

Hi there!
I must say your lib came just at the right time for me!
My issue:
I have the following code:
let rados = connect_to_ceph(
    &std::env::var("CEPH_USER").expect("Missing CEPH_USER"),
    &std::env::var("CEPH_CONF_PATH").expect("Missing CEPH_CONF_PATH")
).expect("Ceph connection should have been made");
let rados_ctx = get_rados_ioctx(
    rados,
   &std::env::var("CEPH_POOL").expect("Missing CEPH_POOL")
).expect("Ceph ioctx");

let rbd = Rbd;

rbd.list(rados_ctx).expect("Failed to get image list").iter().for_each(|img| {
    println!("{}", img);
});

The rust compiler gives the following error:
error[E0308]: mismatched types
  --> src/main.rs:39:14
   |
39 |     rbd.list(rados_ctx).expect("Failed to get image list").for_each(|img| {
   |              ^^^^^^^^^ expected enum `std::os::raw::c_void`, found enum `libc::c_void`
   |
   = note: expected type `*mut std::os::raw::c_void`
              found type `*mut libc::c_void`

I managed to quickfix by using std::mem::transmute. But I guess you need to import the right rados_ioctx_t type or define it otherwise in ceph-rust.

Ah yeah that's annoying isn't it?  I ran into this also and meant to fix it but got sidetracked.  Let me push a change to the ceph library this morning.

While you're waiting I got around this by doing:
 let ceph_conn = connect_to_ceph("admin", "/etc/ceph/ceph.conf")?;
    let ioctx = ceph::ceph::get_rados_ioctx(ceph_conn, "glance")?;

    let img = ceph_rbd::rbd::RbdImage::open_read_only(
        ioctx as *mut c_void,
        "04cea186-1f26-49ab-938c-6725f202bf2a",
        "",
    )?;
    let start_time = SystemTime::now();
    let s = img.stat()?;
    ...

@judu that should fix you up. Pull the latest version of ceph-rbd.  Also FYI sravanthi is going to submit a PR today to fix a bug we have in the library.  It's a pretty bad one.  The Drop impl that I made for RbdImage causes the program to crash with a mutex lock assertion error.  We'll have this fixed up shortly.  Thanks for using the library!  Really love seeing people use my work.  Let me know if you run into other issues.  This library is only lightly tested at the moment.

I'm going to close this for now.  Let me know if you still have trouble.

@judu FYI this new release changes a lot of stuff with ceph and ceph-rbd however it's a LOT faster now that you can share Rados between threads.  I have an example program for ceph-rbd if you'd like see here: https://gist.github.com/cholcombe973/c459113cb489bf8394d65675def32de8

That's nice! I'm not really in need for speed, but still, it's nice :)
I'll check that new release this weekend!


m_len check in rsa_sign()

Technical check of the expected length of m_len in rsa_sign(). I have added a look up on the hash function id using EVP_get_digestbynid(), then a comparison of m_len against the result of a call to EVP_MD_size().
Fixes #14594

Probably not worth doing this for master since the API is deprecated..

Closed (and reopening) commit to remove the "cla required" tag.

The cla check did not recognize the anonymized e-mail used in the commit.


Possibility to delete own watering entries

It should be possible to delete own watering entries (e.g. when accidentially assigned to wrong tree)

Delete watering:
https://user-images.githubusercontent.com/994131/162630522-b3e9e84f-e7fe-4477-9398-86d84a4cdacc.mp4

DONE: https://github.com/CodeforLeipzig/leipziggiesst/commit/2f056415773f53ba03d30e2269f402160640d10d


Error when linking more than a single solidity library to the same contract

Given a contract that uses more than a single external solidity library (ie a library with non-internal functions, that needs to be linked), zos push fails to deploy them since linking fails.
The reported error is the following, since zos does not check that all pending links have been replaced before deploying (see #250):
[Error] Error: Contract deployment failed with error: The data field must be HEX encoded data.

This happens because Contract#link in zos-lib iterates over the set of libraries to replace, but sets the linkedbytecode to the result of replacing the library by its address on the original bytecode, and not on the linkedbytecode being accumulated. This causes only the last library to be actually linked.
  instance.link = function(libraries: { [libAlias: string]: string }): void {
    Object.keys(libraries).forEach((name: string) => {
      const address = libraries[name].replace(/^0x/, '');
      const regex = new RegExp(`__${name}_+`, 'g');
      instance.schema.linkedBytecode = instance.schema.bytecode.replace(regex, address); // Should be replacing over linkedBytecode, initialized to bytecode!
      instance.schema.linkedDeployedBytecode = instance.schema.deployedBytecode.replace(regex, address); // Same here
    });
  };

We may wanto to solve https://github.com/zeppelinos/zos/issues/712 together with this issue.

While the fix here seems trivial I'm having a hard time writing a regression test - do these libraries need to be completely external to the project(e.g., other zos packages)?

do these libraries need to be completely external to the project (e.g., other zos packages)?

@siromivel not necessarily: any two Solidity libraries in the project will do. The catch is that they must have external methods - a library whose all its functions are internal (such as OZ's SafeMath) does not need to be linked and thus fails to trigger this bug.


Fixed useNativeDriver warning

#131 Fixed useNativeDriver warning

@oblador could we please merge this?

@oblador any dates on when this will be merged?

@oblador any dates on when this will be merged?

This worked like a charm, please merge this!


Web5 Quickstart doesn't yet deliver for users

We have content and tech work to do here.
The Quickstart must address the why and the how of Web5.

Quickstart should be able to be completed as promised in in 5min
Starts from a template
Nails the "why" of Web5 and a Personal Data Store for users of your (as an app dev) app

The Why
What is the value prop of Web5? Why a paradigm shift into a personal data store? How is this a fundamental building block for making a whole new class of decentralized applications that preserve users' privacy?
Right now the message is centered on the CRUD operations involved.
The How
I don't believe the Quickstart in its current form can get the user what's promised in 5min. Have any of us on the team run through this to try it out? I did this evening, and I had to:

Pull from prior knowledge in software development
Use other tools to bootstrap a project; we don't mention how to make this new project in the Quickstart
Refer to Devin's full example app quite a bit; the code we put in the Quickstart is only the Web5-specific code; the user is left to figure out if they should put these in functions, and how to display the return values on the page.
...and this all took me much longer than 5min.

The Web5 Quickstart starts with an installation section:
npm install @tbd54566975/web5

This assumes the user has a current project, and that they're using NPM. How is a new user to create this project? What assumptions have we made about that user's expertise with coding and their ability to start a new project? (This will be handled by #408)
In short, following the instructions on the Quickstart exactly as written does not give the user everything they need to get a working application. Some of it can be pieced together through prior knowledge and by referring to Devin's fully working application example -- but there are omissions in the Quickstart instructions which may put a user in a dead end. There are no functions mentioned; no HTML for input fields or writing return values.
I'd be surprised if anyone on the team can follow the Quickstart and get a working Web5 application in 5 minutes as promised. And this has to work for relative newcomers to front end coding; assume the requisite experience to meet the "5min" bar is the equivalent of one semester of software development coursework in JavaScript.

I think there's been some duplication of work in creating all these great demos. There wouldn't really be a Web5 app, that would be a DWA that works with Web5 components. The DWA building docs aren't ready yet according to https://areweweb5yet.com/ There are several ways that a DWN can be utilised and set up. The dwn-sdk is for creating any type of DWN. The Web5-js can create a personal datastore DWN for testing (in the browser or running on a local computer). The dwn-js repo will also set up a personal datastore DWN for testing, and a more robust version is in dwn-server with some hosted DWNs available for testing. What Web5-js does is provide a simple way to talk to a DWN (any type) as this is time consuming to code the queries routing manually. It can create DIDs but there is a separate ecosystem for storing and managing these (wallets, SSI repos). You would use dwn-sdk to make a reusable one, and there is the upcoming Electron standalone DWN coming soon.
So maybe it's better to see this as a 5 minute Quickstart to communicate using Web5, and use a hosted DWN (with the tenant locked to the owner to stop anyone else writing to it). The visitor to this page then creates a DID, sends a message to the hosted DWN by a provided DID and then a message is returned to say something like congrats or well done. Then the visitor can at least know what a DID is and how it can be used instead of a server address to access someone else's info.

also see my comments
https://github.com/TBD54566975/developer.tbd.website/issues/392#issuecomment-1507997361

@csuwildcat recommending @dcrousso may work on a "starter template", based on this:
https://github.com/pwa-builder/pwa-starter
That'd give new users a starting point to Web5-ize from.

I guess the best thing we can do to close this out is find someone to run through these steps and see how far they get?
I think the starter template @ALRubinger would be really helpful.
I also can't help but feel like no one would actually want to use this quick start to continue building a whole app. These days, I personally would reach for something like Next.js or Vite. I think that we should consider having templates based on things like that.

@dayhaysoos Spot on - and @csuwildcat has elevated "starter template" for Phase 3. I agree that'll be really helpful - removes all the need for:

Us to explain boilerplate and add to conceptual weight of the Quickstart
Reader to have to spend time making boilerplate.

A clean starting point for them plus a Quickstart that's about how to Web5-ize it is a great flow for now. And opens us up to an app to get people started later. For now templates are great.

Slating as TODO for Phase 3 and self-assigning; open to pairing w/ interested/available parties on it. @chris-tbd @bobbilee19 @angiejones @EbonyLouis

Template to help with the first setup is in #408

@bobbilee19 and I gonna pair on driving this one to the finish :)

@bobbilee19 and I will center this work in upstream branch issue-398-quickstart-upgrades

Deploy preview for the branch noted above is here.

@bobbilee19 has come across some errors during the upgrade process. We looped in OSE to get help on this which allowed us to get through a few errors but we need to reconvene to wrap things up.

Encompassed by a series of changes done coordinated @bobbilee19, advised by @angiejones and I, and now in main.


Let user hide filter area on demand

this is related to the whole Side panel?...We are adding columns via this...the only use case I see is to hide it when creating the figures out of Taggle

yes, I'll close this issue for now.


Distributed: support configurable higher level of isolation

Today while a transaction runs distributed, there could be dirty reads during the propagation of a transaction commit or rollback. It would be nice having a configurable setting to avoid this making all the reads perfectly consistent.

Just a quick note: I'm not sure exactly what you have in mind, but it would be ideal if this setting could be selected on a per-connection or per-request basis. If that's not easily done for this time around, at least a per-database or per-class basis would be better than a global setting.
PS - In my particular case, the client is orientjs.


which version or why solve error?

I try reverse engineering. I do not know version.
old deploy here
http://dsalodki.westeurope.cloudapp.azure.com/
I try use browser sources in new web application.
Error: (SystemJS) XHR error (404 Not Found) loading http://localhost:5001/app/theme/components.js
Error: XHR error (404 Not Found) loading http://localhost:5001/app/theme/components.js
Error loading http://localhost:5001/app/theme/components.js as "./components" from http://localhost:5001/app/theme/nga.module.js
Windows 10
node --version
v8.11.3
npm --version
5.6.0
can you say version ng2(x)-admin or/and how to correct error above?
see attached nga.module.ts
nga.module.zip

Hey @dsalodki, it is most likely ng2-admin, but which particular version is very hard to tell. I presume you don't have the complete source code?

I have not sources only can open browser console and have deployment


VirtualScroller not working with DataTable

Hi, I'm sorry to insist, but I'm stuck, I don't know what is wrong. Virtual Scroll works with DataTable on Primevue here: https://primevue.org/datatable/#virtualscroll, but does NOT work with Tailwind Primevue here: https://tailwind.primevue.org/datatable/#virtualscroll. Try it out here: https://stackblitz.com/edit/9ywajd-dnq98z?file=src%2Fmain.js, adding app.use(PrimeVue, { unstyled: true, ripple: true  }); breaks the virtual scroll on the table.
I can use VirtualScroller alone with or without unstyled: true, but not DataTable with virtual scroll.
On https://github.com/primefaces/primevue-tailwind/issues/108, you suggested to use pt. I can pass styles, yes, but the functionality is not there.
I would greatly appreciate your advice on how to use VirtualScroller with DataTable.

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Any updates? Virtual Scroll still does not work with DataTable on Tailwind Primevue.

Same issue here.
To be more precise, in my case it seems to work on Chrome, but not on Firefox. Nothing appears (same as the example on the doc https://tailwind.primevue.org/datatable/#virtualscroll.
In comparison with the styled version, I notice a missing style display: flex in <tbody data-pc-section="virtualscrollerspacer"></tbody>.
I tried to add it via Pass Through and it seems to work. At least something appears on Firefox.
<script setup>
const passThrough = {
  virtualScrollerSpacer: {
    class: 'flex'
  }
}
</script>
<template>
  <DataTable :pt="passThrough" :value="virtualValue" scrollable ...>
    ...
  </DataTable>
</template>

Indeed VirtualScroller + DataTable work on Chrome, but NOT on Firefox.

Adding another voice to this.  Firefox (version 126) on Mac, using the tailwind datatable page (https://tailwind.primevue.org/datatable/#virtualscroll) and the datatable is blank.  This makes virtual scrolling unusable.

any news?

As of v4.1.1, the new Tailwind styles have been rewritten using the preprocessor approach with @apply instead of pass-through. As a result this issue is not relevant any more.
New Website is live.


Compile will fail if assembly name and project name doesn't match

In AnalyzerResultExtensions.cs at row 107 you set assembly name to the project file name. I guess this is true for 99% of the cases but I have found solutions where they have a project name and then a different assembly name (not sure if they just forgot to change or if it's intended).
Maybe you should take the extra mile to actually check the assembly name just to be safe? Right now you will get a lot of conflicts later on because dependencies expect a certain name but we call it something else.

Does it actually crash if they're different? The ProjectInfo requires an assembly name so we have to give it one, but I'm not sure what it's used for besides that.
To a large extent I don't think it matters in this case - that code is creating a ProjectInfo instance for Roslyn to use while generating the workspace. The expectation (at least my intent) was that this workspace was primarily for analysis purposes, not compiling back to disk. To be honest, I'm not sure you even could use it to reliably compile a project - the main Buildalyzer does that via shelling out to MSBuild to avoid all the little gotchas (and there are a lot).

It doesn't crash but later on if you do a commit/emit from a project in the created adhocworkspace it will complain about references.
But yeah it depends a lot on the goal and if this project is mostly for analyze then it doesn't really matter. But I have actually had a lot of success with compiling the projects back to disk (where MsBuildWorkspace would fail) so even if this isn't your intent it actually work pretty nice 👍


[MultiSig Toolkit] - User can create multisig address on multisig-toolkit app

Request:
As a Sui MultiSig Toolkit  user, I want to create a multisig address with Sui Pubkeys, Weights for each key, and a threshold for the multisig address.
There should exist a 'Create MultiSig Address' Tab in the MultiSig toolkit that allows users to setup a multisig address for use.
Context:

Sui Multisig Toolkit codebase: https://github.com/MystenLabs/sui/tree/c05689a4efd7d693076e22949f2565842dc61aea/dapps/multisig-toolkit
Sui MultiSig docs

@jnaulty still relevant? If not let's close it!


Investigate/fix cardinality behavior in Source Generation

closing as the https://github.com/Azure/azure-functions-dotnet-worker/issues/1204 is done.


Duplo 11508 RDS Secret Manager attribute fix

Overview
Bug fix for setting store_details_in_secret_manager attribute
Summary of changes
Setting and reading value for store_details_in_secret_manager for  duplocloud_rds_instance
This PR does the following:

setting store_details_in_secret_manager from DuploRdsInstance.StoreDetailsInSecretManager in rdsInstanceToState()
setting DuploRdsInstance.StoreDetailsInSecretManager from store_details_in_secret_manager in rdsInstanceFromState()

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[ ✓] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-11508 TF: RDS Save Password in SecretsManager Doesn't actually work


Error building/serving the nuxt project after importing the nuxt-security module

Hello, i was trying to import the module inside my project but after importing the module i always seem to be getting the following error.

This error happens in my own project but also when i setup a completely empty nuxt project with nothing in it.
// https://v3.nuxtjs.org/api/configuration/nuxt.config
export default defineNuxtConfig({
  modules: ["nuxt-security"],
});

{
  "private": true,
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "devDependencies": {
    "nuxt": "3.0.0-rc.12"
  },
  "dependencies": {
    "nuxt-security": "^0.5.0"
  }
}

Hey @mikeschepers4
Are you using Static Site Generation or SSR?

This is really strange, I have just tested it out on a same project and it works (the only difference is that I am using yarn I believe)

Package.json:
{
  "private": true,
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview"
  },
  "devDependencies": {
    "nuxt": "3.0.0-rc.12"
  },
  "dependencies": {
    "nuxt-security": "^0.5.0"
  }
}

Nuxt.config.ts
export default defineNuxtConfig({
    modules: ['nuxt-security']
})

It seems to happen both in ssr and static site generation. I tried to make a stackblitz but there it doesnt happen.
I think it might have something to do with the operating system since my error complained about a bad character sequence. (the error is in my screenshot above). Could windows have something to do with it?

these are the lines that are causing the issue on my system

adding .replace(/\/g, '/') after every resolve call seems to fix the build. i will let you know if everything works as i expected

I see, quite strange. I will ask around in the nuxt community. From what you say, this bug can be caused by nuxt itself.

I think the problem lies in this file here the resolve methods dont seem to normalize the paths correctly for windows at least.
The output seems to be like this: C:\rovict\nuxt-app\node_modules\nuxt-security\dist\runtime\server\middleware\requestSizeLimiter
Whilst you need this output on windows: C:/rovict/nuxt-app/node_modules/nuxt-security/dist/runtime/server/middleware/requestSizeLimiter

Yes, exactly. It can be resolved in this project by using pathe instead of path. We can probably also normalise in addServerHandler etc. in kit.

@danielroe so should I update the module itself to use pathe instead of path or will this be something included in the next version of kit?

You should use pathe anyway.

Ok, so I will replace this for the next version. Thanks for the help!

@mikeschepers4 I will release the new version in the upcoming days with this fix and few other smaller functionalities.

Amazing! I'll keep an eye on it. Thanks for the quick response!

Hey @mikeschepers4
I have released a new version with the fix for that. Could you please check if it works right now? :)

Just updated the module to check. there still seems to be an issue. I'll look into this a bit deeper. (tested with a newly created nuxt app)

@mikeschepers4
I see, maybe then changing the path to pathe is not enough. Let me know please after you do some more testing. Unfortunately I do not have a Windows device so I cannot really test it out (almost like blind coding). I can also release a quick patch version to make it work

Or for each middleware replace handler: resolve(runtimeDir, 'server/middleware/rateLimiter') with handler: normalize(resolve(runtimeDir, 'server/middleware/rateLimiter'))

Any news @mikeschepers4 ? 🙂

Sorry ran out of time to test it last week. will test today :)

Ive not been able to find a solution. I think it may have something to do with the way nitro is referencing the given paths. ill look further once i have some time again

@danielroe Could you take a look at that? Maybe this is an issue in the nitro?

hey @mikeschepers4
Have you managed to test it out more?

Sorry no. I think a potential fix would be to make use of relative paths instead of absolute paths. But i dont know how easy that would be to integrate in this solution.
Or Nitro needs to make a fix to handle absolute paths correctly on windows machines.
I sadly dont have a lot of time at the moment to work that out myself

@danielroe @pi0
I managed to test it out on an old Windows laptop and the issue is appearing when I want to push Nitro plugin from module:
https://github.com/Baroshem/nuxt-security/blob/1c93c65bb53eb9607df1c8ab970f79f74d68c13e/src/module.ts#L34
Other URL;s are working correctly. Is it caused by this? https://github.com/nuxt/framework/pull/8626/files
I have updated the package to work with 3.0.0-rc.13 version but the issue is still there

In dev mode this likely needs to be a file URL not a path. Fancy testing that? If so, we can likely fix in Nuxt itself.

Related to https://github.com/nuxt/framework/issues/8461

I tested it by sending even a simple path to the plugins array, it still shouts that it is not correct.

I believe this is an issue on the nitro side as other handlers are working correctly, only the one that is being pushed to nitro plugins array is failing.
For all users facing the problem. When you set hidePoweredBy to false in your nuxt.config.ts your project will work fine and you can use it as a workaround now until a proper fix will be published. It will disable this plugin for now but will make your app working.

Can confirm that your workaround is working. thanks :)

Guys,
Daniel is already working on fixing this issue on the nitro side. I will make sure to update nuxt to a newer version once it is released. For now, make sure to use this workaround -> https://github.com/Baroshem/nuxt-security/issues/42#issuecomment-1311727911

Hey folks,
I have tested solution from @pi0 and it seems to be working now. Please test it out in your environment and let me know if there are any issues. Sorry that it tooked so long and hope that you will be still using the module :)


Confusing name?

The project name is very similar to another Rust project https://github.com/jwilm/alacritty

I already responded in https://www.reddit.com/r/rust/comments/5u8jp1/alacrity_a_reverse_proxy_written_in_rust/ddt6mda/ saying I would change it.


⚠ Bofrost.gr has degraded performance

In 35c4ce4, Bofrost.gr (https://www.bofrost.gr) experienced degraded performance:

HTTP code: 200
Response time: 12465 ms

Resolved: Bofrost.gr performance has improved in 97d18c6 after 2 days, 6 hours, 24 minutes.


Go client swallows alerts on error

I'm submitting a ...

improvement request (usability, performance, tech debt, etc.)

Traffic Control components affected ...

Traffic Ops Client (Go)

Current behavior:
When the Traffic Ops API response to a request made by the Go client is >= 300 and != 304, the body of the response is read into the content of a returned error - and behind the scenes the body is also closed. This makes it difficult to write client methods that actually return error alerts, since the normally used methods employed by writers of a new client method will all exhibit this behavior.
It's not that it's impossible, it's just not possible using the common RawRequest, makeRequestWithHdr, post/put/get/etc. methods.
New behavior:
The client should return an error like "Traffic Ops responded with 400 Bad Request" and leave the alerts to the actual returned Alerts.
I'm not sure if this can actually be done in the APIv3- client(s), since the tests check for alert text in the errors, which might mean that it's expected behavior on which clients depend. But it can safely be done in the new APIv4 client, since nobody's using that.
Minimal reproduction of the problem with instructions:
Use a client method that results in an error, notice that no alerts are returned.

This was fixed in #5747