random error when I try to build

Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Short description of the problem:
I am getting some random errors when I try to live reload in device or run or build for device.
ionic build android
ionic run android -l

What behavior are you expecting?
The same doesn't occur during ionic serve and I can see the app in browser.
But when I try to execute in device. it is very random, works sometimes, doesnt work sometimes. It shows a white screen for a long time and stuck there.
ionic build android
ionic run android -l

Which @ionic/app-scripts version are you using?
Your system information:
Cordova CLI: 6.3.1
Ionic Framework Version: 2.0.0-rc.0
Ionic CLI Version: 2.1.0
Ionic App Lib Version: 2.1.0-beta.1
OS:
Node Version: v6.7.0
App scripts:
"_from": "@ionic/app-scripts@latest",
"_id": "<EMAIL_ADDRESS>"_inCache": true,
"_installable": true,
"_location": "/@ionic/app-scripts",
"_nodeVersion": "4.5.0",
"_npmOperationalInternal": {
"host": "packages-12-west.internal.npmjs.com",
"tmp": "tmp/app-scripts-0.0.27.tgz_1475355475934_0.5256864109542221"
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)

looks like we cant have 2 terminals to simulate?
I had either
ionic server
or
npm run watch
which was giving this error.
Without parallel execution, I could get ngC compilation successfully.

Hello, thanks for using Ionic! This is caused by both your ionic build command and ionic serve both watching and writing files to the same directory at the same time. Im not sure if the use case of having ionic serve and ionic build or ionic run running at the same time is something we want to support, but i will leave this issue open for discussion. Thanks!

@balasivagnanam i am having the same error. I solved it by removing the .tmp folder manually.
Hope that helps!

Hello all! I am going to close this issue for now as I cannot repro anymore with the latest beta of app-scripts. We hope to release v0.0.37 today which as I said fixes this. Thanks!


More CodeAction moves in preparation for cohosting

Okay, I was wrong when I said the last PR was the final piece before cohosting actually gets implemented, but this one is, I swear!
Code actions have to run in devenv for Roslyn, so the main thing here is re-architecting so that the endpoints call the delegated servers, because calling into the service. Each commit is an isolated step on the way.

Thank you both


containerize bots + engine

TODO: container for python skeleton, send a message to server when engine is done?

need to fix messaging protocol


Visualise ESR raw indicator data by group

Job story
When I am viewing a single country (#1) ...
... I want to be able to explore the underlying raw indicator data visually for each sub-group ...
... so I can better understand how the implications for the individual population groups.
Additional considerations

Currently raw indicator data is not presented
For each score the immediate and long term target can be visualised
Sub-group data could have different group-specific immediate targets
Consider mobile support #13
Consider accessibility #15
Consider general design considerations #14
Consider shareability #27

Tasks

Consider chart options
Consider chart interactions

go back to aggregated indicator data (#5)
go back to dis-aggregated indicator scores (#24)

Job story
When I am viewing a single country (#1) ...
... I want to be able to explore the underlying raw indicator data visually for each sub-group ...
... so I can better understand how the implications for the individual population groups.
Additional considerations

Currently raw indicator data is not presented
For each score the immediate and long term target can be visualised
Sub-group data could have different group-specific immediate targets

Tasks

Consider chart options
Consider chart interactions

go back to aggregated indicator data (#5)
go back to dis-aggregated indicator scores (#24)

Not entirely clear how disaggregated data is provided
Option A: proper disaggregate


Enable caching for control flow paths that precede loops

This PR tweaks our control flow analysis logic for loops to ensure that caching of assignment nodes occurs in control flow paths that precede loops.

@typescript-bot perf test this
@typescript-bot test this

@typescript-bot perf test this
@typescript-bot test this

Optimized our flow assignment caching scheme for an overall ~2% reduction in check time. Now, we only cache when resolution of the cached value involves a recursive invocation of getFlowTypeOfReference (because only then is the operation potentially expensive). Also, by moving the caching logic into getInitialOrAssignedType we no longer need to compute and store a cache key.


NPM install for Angular 12 fails

Is this a regression?
No
Description
I cannot install this package for any Angular 12 project with the following command: npm install<EMAIL_ADDRESS>It works for on Angular 13 though.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/common
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@ngneat/elf-ng-router-store
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Please provide the environment you discovered this bug in
Angular 12.0.4
Typescript 4.2.4
rxjs 6.6.2
@ngneat/elf-ng-router-store 1.0.2

Anything else?
No response
Do you want to create a pull request?
No

check peer dependencies, please

Got it, thank you!


Add Metaverse module.

Extract from Web app.

Part of this work may have been done in the v2 SDK.


Zooming with mouse wheel gives black screen

Zooming in /out works hardly. Zooming with mouse wheel gives black screen and no further action is possible . System hangs

Hi Frans,
Can you provide a little more information on the OS and browser being used?
Do you also experience the same lagginess on iD (https://www.openstreetmap.org/edit) or is it specific to RapiD?
Thanks!

oeps. Overlooked your reaction, but the bug still exists.
It's happening on Firefox, even during the last revision.
version 79.0 (64-bit)
Other browsers like Chrome and Edge don't know that problem.
Zooming in with the mouse wheel results in a black screen , nothing else, zooming out doesn't help. The only thing that can be done is to close and restart iDeditor.
Zooming in and out with the + and - button in the editor works, but is not useful because you automatically grab the scroll button and the screen turns black again.
I can copy a black screen but that is not of any help

I closed this  by accident.

Hi Frans,
I would echo @jeffdefacto's question above- Do you use the regular iD editor, and if so, do you experience this same problem with it?
Other things to try:

open the web console with

Then, make the black screen bug happen in your firefox browser.
If there are any log messages/errors that occur, please save & send them by right-clicking one of the messages and selecting 'Select All', then copy/paste the log here.

Can you take a screenshot anyway, including the URL that you've navigated to using RapiD?


[SPARK-38075][SQL] Fix hasNext in HiveScriptTransformationExec's process output iterator

What changes were proposed in this pull request?
Fix hasNext in HiveScriptTransformationExec's process output iterator to always return false if it had previously returned false.
Why are the changes needed?
When hasNext on the process output iterator returns false, it leaves the iterator in a state (i.e., scriptOutputWritable is not null) such that the next call returns true.
The Guava Ordering used in TakeOrderedAndProjectExec will call hasNext on the process output iterator even after an earlier call had returned false. This results in fake rows when script transform is used with order by and limit. For example:
create or replace temp view t as
select * from values
(1),
(2),
(3)
as t(a);

select transform(a)
USING 'cat' AS (a int)
FROM t order by a limit 10;

This returns:
NULL
NULL
NULL
1
2
3

Does this PR introduce any user-facing change?
No, other than removing the correctness issue.
How was this patch tested?
New unit test.

Thank you, @bersprockets . Do you know when this bug started?

Not sure how far back, but at I can reproduce in 2.4.8, 3.1.2, 3.2.0, 3.2.1, and master.

Oh, never mind. I realized that the spark-shell add limit automatically. You're right. This is ORDER BY .. LIMIT issue.
spark-sql> SELECT version();
3.2.1 4f25b3f71238a00508a356591553f2dfa89f8290
Time taken: 0.208 seconds, Fetched 1 row(s)

spark-sql> SELECT transform(a) USING 'cat' AS (a int) FROM VALUES (1) t(a) ORDER BY a;
1
Time taken: 0.282 seconds, Fetched 1 row(s)

Thank you for updates, @bersprockets . After compilation, I'll merge this.

Merged to master/3.2. For 3.1, there is a conflict.

For 3.1, there is a conflict.

I will take a look at what needs to be done.


Launch token provider from security-secretstore-setup.

Replace the placeholder in security-secretstore-setup with
logic to invoke a user-defined process that creates
per-service tokens for the secret-store. At this time
only oneshot providers are supported:
security-secretstore-setup will launch the provider
and wait for it to run to completion.
The new code takes a Context object as input so that
it may be integrated with the new common bootstrap
handler (issue-1751).
Fixes #1798
Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>

Unit test instructions:
from internal/security/secretstore run go test
Integration test:
Expected output:
make: Entering directory ...
CGO_ENABLED=0 GO111MODULE=on go build -ldflags "-X github.com/edgexfoundry/edgex-go.Version=1.1.0" -o ./cmd/security-secretstore-setup/security-secretstore-setup ./cmd/security-secretstore-setup
make: Leaving directory ...
edgex-vault is up-to-date
Waiting for stack to come up...
Vault container id ed53514f4f4a
Vault root token is s.c4ceJsD1BjqJVqa2alrMvnKL
level=INFO ts=2019-09-25T00:38:02.194497751Z app=edgex-security-proxy-setup source=requester.go:40 msg="successfully loaded rootCA certificate."
level=INFO ts=2019-09-25T00:38:02.195735805Z app=edgex-security-proxy-setup source=tokenprovider.go:72 msg="Launching token provider /bin/echo with arguments -confdir res/token-file-provider"
level=INFO ts=2019-09-25T00:38:02.197696098Z app=edgex-security-proxy-setup source=tokenprovider.go:91 msg="token provider exited successfully"

Save the following script to cmd/security-secretstore-setup as integrationtest.sh and run it
#!/bin/sh -e

#
# Copyright (c) 2019 Intel Corporation
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
# in compliance with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software distributed under the License
# is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
# or implied. See the License for the specific language governing permissions and limitations under
# the License.
#
# SPDX-License-Identifier: Apache-2.0'
#

make -C ../.. cmd/security-secretstore-setup/security-secretstore-setup

cat <<EOH >docker-compose.yml
version: '3'
volumes:
  db-data:
  log-data:
  vault-config:
  vault-file:
  vault-logs:

services:

  vault:
    image: edgexfoundry/docker-edgex-vault:1.0.0
    container_name: edgex-vault
    hostname: edgex-vault
    networks:
      - default
    ports:
      - "8200:8200"
    cap_add:
      - "IPC_LOCK"
    command: "vault server -dev-listen-address=<IP_ADDRESS>:8200 -dev-kv-v1 -log-level=info"
    environment:
      - 'VAULT_ADDR=https://edgex-vault:8200'
      - 'VAULT_CONFIG_DIR=/vault/config'
      - 'VAULT_UI=true'
    volumes:
      - vault-config:/vault/config
      - vault-file:/vault/file
      - vault-logs:/vault/logs
...
EOH

docker-compose up -d

echo 'Waiting for stack to come up...'
sleep 5

vaultid=`docker ps | grep 'edgexfoundry/docker-edgex-vault' | cut -d' ' -f1`
echo "Vault container id $vaultid"

docker exec $vaultid cat /vault/config/pki/EdgeXFoundryCA/EdgeXFoundryCA.pem > EdgeXFoundryCA.pem
docker exec $vaultid cat /vault/config/pki/EdgeXFoundryCA/edgex-kong.pem > edgex-kong.pem
docker exec $vaultid cat /vault/config/pki/EdgeXFoundryCA/edgex-kong.priv.key > edgex-kong.priv.key

vault_token=`docker logs $vaultid 2>/dev/null | grep 'Root Token:' | cut -d ':' -f2 | tr -d '[:space:]'`
echo "Vault root token is $vault_token"

cat <<EOH > resp-init.json
{
  "keys": [
    "test-keys"
  ],
  "keys_base64": [
    "test-keys-base64"
  ],
  "root_token": "${vault_token}"
}
EOH

test -d testdata || mkdir testdata

cat <<EOH > testdata/configuration.toml

[Writable]
LogLevel = 'DEBUG'

[Logging]
EnableRemote = false
File = './logs/security-secretstore-setup.log'

[SecretService]
scheme = "http"
server = "localhost"
port = 8200
certpath = "v1/secret/edgex/pki/tls/edgex-kong"
cafilepath = "EdgeXFoundryCA.pem"
certfilepath = "edgex-kong.pem"
keyfilepath = "edgex-kong.priv.key"
tokenfolderpath = "."
tokenfile = "resp-init.json"
vaultsecretshares = 5
vaultsecretthreshold = 3
tokenprovider = "echo"
tokenproviderargs = [ "-confdir", "res/token-file-provider" ]
tokenprovidertype = "oneshot"
EOH

./security-secretstore-setup --confdir testdata --init=true

Codecov Report

Merging #1818 into master will increase coverage by 0.13%.
The diff coverage is 84.21%.

@@            Coverage Diff             @@
##           master    #1818      +/-   ##
==========================================
+ Coverage   38.04%   38.18%   +0.13%
==========================================
  Files         163      164       +1
  Lines       12574    12612      +38
==========================================
+ Hits         4784     4816      +32
- Misses       7531     7535       +4
- Partials      259      261       +2

Impacted Files
Coverage Δ

internal/security/secretstore/config.go
100% <ø> (ø)
:arrow_up:

internal/security/secretstore/tokenprovider.go
84.21% <84.21%> (ø)

Continue to review full report at Codecov.

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

Rebased.

Re-ported code on top of common-bootstrap version.

recheck


Request for tab numbering

Hi, does anyone know of an extension to give tabs a number tag, like this one but for Opera (running v52.0)? Is this a planned feature for this extension?
I would really like this as a workflow improvement since I use the ctrl+(No.) hotkey to switch between tabs, but when there are many tabs and it is past 10pm then my mental arithmetic is too slow :)

Hi @adigitoleo,
I like the idea of this feature, but I would not be willing to implement it. There is a lot of performance trickery involved in modifying the title of every tab and updating the title whenever a tab is inserted, removed or rearranged. I am able to update the counter icon of every tab by only updating what is seen on screen first—this same trick cannot be done with the titles.

I understand, in fact I have just switched to Vivaldi as my main browser since I was informed that they now have bookmark sync. Honestly opera is a bit lacking on the extensions side of things.
Anyway, good luck with your projects.

@adigitoleo You can use https://addons.mozilla.org/en-US/firefox/addon/tab-numbering/ (https://github.com/tuomassalo/tab-numbering) together with Alt+1 .. Alt+9 or install one of these:

https://addons.mozilla.org/en-US/firefox/addon/control-number-tab-switcher/
https://addons.mozilla.org/en-US/firefox/addon/ctrl-number-to-switch-tabs/


Add utilities needed for rsync-stunnel merge

This PR adds the utilities needed for rsync and stunnel pod merge task.

Removed procps as it is not required in accordance to the latest container bash script for rsync/stunnel, going ahead with the merge.


Speed for TV denoising CIL-Demo

I noticed the following problem:
Created a new conda env with the new C-library and test TV denosing demo.
Almost certain that builded correctly.
this is the output with the C-library

PDHG setting up
PDHG configured
     Iter   Max Iter     Time/Iter        Primal          Dual     Primal-Dual
                               [s]     Objective     Objective             Gap
        0       3000         0.000    1.26188e+04  -0.00000e+00    1.26188e+04
      500       3000         0.055    1.63708e+04   2.55575e+03    1.38151e+04
     1000       3000         0.056    1.38738e+04   9.07814e+03    4.79564e+03

this is the output without the C-library
PDHG setting up
PDHG configured
     Iter   Max Iter     Time/Iter        Primal          Dual     Primal-Dual
                               [s]     Objective     Objective             Gap
        0       3000         0.000    1.26188e+04  -0.00000e+00    1.26188e+04
/anaconda3/envs/ccpi_vaggelis/lib/python3.6/site-packages/ccpi/framework/framework.py:730: RuntimeWarning: invalid value encountered in true_divide
  out = pwop(self.as_array() , x2.as_array() , *args, **kwargs )
      500       3000         0.002    1.63708e+04   2.55575e+03    1.38151e+04
     1000       3000         0.002    1.38738e+04   9.07814e+03    4.79564e+03
     1500       3000         0.002    1.35840e+04   9.18389e+03    4.40006e+03
     2000       3000         0.002    1.29320e+04   9.05492e+03    3.87710e+03
     2500       3000         0.002    1.34574e+04   9.74938e+03    3.70806e+03
     3000       3000         0.002    1.29068e+04   9.69804e+03    3.20877e+03

which is faster per iteration.
Actually, had a look with the new implementation. Basically if we have backend='numpy' is faster

That does seem very slow! What size image is it on, I'll have a look.


Add a description of how the app uses third party sign-in

Codecov Report
Base: 88.18% // Head: 88.23% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (d8ba359) compared to base (4f16455).
 Consider uploading reports for the commit c1f9492 to get more accurate results

Additional details and impacted files
@@               Coverage Diff               @@
##           development     #165      +/-   ##
===============================================
+ Coverage        88.18%   88.23%   +0.04%
===============================================
  Files               52       52
  Lines             4029     4029
===============================================
+ Hits              3553     3555       +2
+ Misses             476      474       -2

Flag
Coverage Δ

unittests
88.23% <ø> (+0.04%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

api/cached_items.py
91.05% <0.00%> (+0.81%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Revoking certificate with server private key

I'm trying to revoke a certificate using the private key of the host/server. I load the certificate's PEM-encoded bytes from a file (and confirmed that that works), and when I do client.RevokeCertificate(certBytes), I get this error:
2015/10/20 23:33:12 The server returned an error while trying to revoke the certificate.
{"type":"urn:acme:error:malformed","detail":"No such certificate"}

The client is created not necessarily with the same email address as was used to obtain the certificate originally. How can I use the server's private key instead to revoke the cert?

Actually j/k. It's working now. Not sure what happened. Maybe some fairy dust landed on my Boulder instance :smile:


User Model Tests

Description
Completes User Story #48
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which maintains existing functionality)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Adds specs for

Get user by ID
Get all users
Update user style preference
Deletes a user

RSpec Results

All tests passing
User login test skipped for now


New Topic: Securing the KIC-kong

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
As a user, I'd like to know how to secure KIC-Kong communication with mTLS when using Gateway Discovery
Proposed Solution
No response
Additional information
No response
Acceptance Criteria

Provide instructions how to configure mTLS with Gateway Discovery
Instructions may be provided as a response to this issue and @Rajakavitha1 will port to the WIP KIC 3.0 branch in docs

https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/using-gateway-discovery/ mentions the following:
As Kong Ingress Controller and Kong Gateway deployments are separate, you should enable TLS client verification for the Admin API service so that no one from inside the cluster can access it without a valid certificate. This can be done by setting ingressController.adminApi.tls.client.enabled option in the Helm chart to true. It will create a CA certificate and a CA-signed certificate for the client, and respective Kubernetes TLS Secrets for both.
I'll test these instructions first

Looks to me as done.


After Update [1.11.4] no information is sent to broker

Hello,
After updated at 1.11 to 1.11.4, I lost information sent to broker, when I restore to 1.11, all work great .
What do you do to cause this effect ?
System : PROXMOX 8.2.4
HAOS :
Core 2024.8.3
Supervisor 2024.09.1
Operating System 13.1
user interface 20240809.0

This is a bug in TheengsGateway 1.5.0, caused by specifying more than 1 entry in Discovery Filters. Specify only 1 or none and it will work fine.

Hello,
Thank you for reply but I have only one entry |IBEACON] on field Discover Filter . I try delete filed but appear again after save.


Documentation of Send notifications User guide

Description
User guide communication the app owners responsibilities and guidelines for using Altinn Notifications should be documented.
We have some existing documentation, but this should be updated and moved to docs.
Existing doc: https://www.altinndigital.no/produkter/varsling/, https://altinn.github.io/docs/utviklingsguider/varsling/
This is not a task that needs to be completed by a developer on team core. Hoping product owner or another part of the business. Legal coaches etc. could support us in this delivery.
Documentation should be placed here User guide

Goal: Move existing doc to new structure.
Need legal opinion on various topics ("what is a notification", guidelines for SMS content).


WIP pass empty pre and post playbooks to bypass playbook support for now

Temporarily pass empty pre/post playbook services to allow UI to continue creating plans in the upstream code.
W.I.P. ⚠

fixes  #471 ?

Not yet ... still backend issues it seems...

@priley86 In this PR can you also include addressing the old vm_ids to the new config_info.actions.vm_id structure specified here https://github.com/ManageIQ/manageiq/pull/17674#issuecomment-403153681?
Thanks!

updated after testing w/ 17674 locally...

Changes in this PR have been included in the Gaprindashvili backport PR - https://github.com/ManageIQ/miq_v2v_ui_plugin/pull/518


route53 provider 'record replace' doesn't actually replace

If you attempt to use the 'replace' method for record entries it does not actually update/replace the entry but instead errors out saying that the record already exists. Either replace should be removed and force the 'add' and 'delete' functions or it should be updated to operate as the documentation would suggest as it reads:
replace
    creates or replaces data in a record set corresponding to name and
    type. sets ttl, if present

Instead you get:
;; error: Route53#changeBatch(String,List) failed with errors [Tried to create resource record set [name='blah.example.com.', type='A'] but it already exists]

crazy latency, but I plan to spend a bit of time in denominator. ping back if you'd still like this addressed!

I'm no longer using denominator myself personally as I've switched jobs but my employer is still utilizing the setup I had in place when I left and this did affect the environment.

confirmed

ok, so what happened here is that the record name was missing the trailing dot. there's possibly a way we can help prevent this, by trying to be more smart.
# doesn't work
denominator -p route53 ... replace --type A --name foobar.denominator.io -d <IP_ADDRESS>
# works
denominator -p route53 ... replace --type A --name foobar.denominator.io. -d <IP_ADDRESS>


docs(importing-resources): fix wording

About this change—what it does
Small fix for the importing docs. Mistype was carried over old documentation refactoring.

Hey, @Andor! 👋
Thank you for your contribution. I will run the checks now, let's see if there's any problem.
For now, I can see that you haven't used Conventional Commits in the title of your commit, could you please update it to docs(importing-resources): fix wording? Thank you!

@Serpentiel hey, thank you for quick feedback. PR is updated.


Update upgrading.rst (fix spelling, punctuation)

punctuation,
spelling (configuration, operation, formatter, persistence, etc.).

hello @oliwel ,
please review the changes.


Add KDF to mbedtls

We would like to use mbedtls' key derivation function implementation.

bors try

@johnkord @CodeMonkeyLeet Can you review this PR?

This seems good to me

@achamayou - If there any mbedtls functional tests that exercise this new functionality, can you please add those to the tests/mbed suite and ensure that they Pass? Thanks.

I think it's fine to unblock Coco, though we need to have the options we enable be reviewed again by the crypto folks. In particular, the SDL guidance has always been to use NIST SP800-108 for KDF which HKDF is slightly outside the scope of. We'll need an expert to verify whether mbedtls HKDF is compliant with SP800-56Cr1 though it looks pretty standard to me.
Side note: Akash has actually implemented SP800-108 under the common folder for the TrustZone folks, so that is actually available, at least internally in the SDK.

@anitagov I will have a look, and do what's necessary if there are tests.
@CodeMonkeyLeet If the implementation in common/ is accessible/public, we could use it instead, but we'd prefer not to implement our own KDF.

@anitagov there are tests, but unfortunately, neither they nor the hkdf implementation is in the current version of mbedtls that's in OpenEnclave, so this is blocked by https://github.com/Microsoft/openenclave/pull/1419
I will rebase and add the tests once this is in.

Is this still needed?

@johnkord yes, but until mbedtls is upgraded, this won't help. The feature was added in July '16 (https://github.com/ARMmbed/mbedtls/commit/656864b3605fde3d6ac127453a9442bb9a29e5cc#diff-ae73d78afdb2244b10fdbdd32337c0de), but OE currently uses 2.7.
2.7 is currently LTS, and will be until Feb 2021. Assuming that OE continues its policy of shipping against the mbedtls LTS, that will mean a 4.5+ year lead time on this particular feature.


XML files should be distributed with CocosSharp templates

The CocosSharp.dll does not have an accompanying .XML file for in-IDE documentation. If this were distributed then developers would be able to learn code faster by looking at the pop-ups that appear when typing methods, arguments, and classes.
I don't know if this is something that is a problem with NuGet or with the default templates.
The documentation seems to exist for much of CocosSharp code:
       /*
        ccpSegmentIntersect returns YES if Segment A-B intersects with segment C-D
        @since v1.0.0
        */

        public static bool SegmentIntersect(CCPoint A, CCPoint B, CCPoint C, CCPoint D)

Closed via commits https://github.com/mono/CocosSharp/commit/8b7b0c8010c2507fad87cc91e68429fb2d853d3d and https://github.com/mono/CocosSharp/commit/92189beedb5a25d4804144483c5ef2d482746208


Start in cardboard view right away

Is there a way to start in cardboard view right away (so you don't need to tap on the icon)?
Also:
Is there away to autoplay the media if it's a video (without a tap)?
Thanks!

Yes, and iOS uses this for its fake fullscreen mode. The param is start_mode=3. But please don't do this.

No, playback is gaited on user input (this is a browser level restriction). This is being lifted now for muted video, but no plans at the moment to make that apply to VR View.

Can you provide more info about where to find the param start_mode?  I did not find it in the documentation and i need to force it.

It's in the webvr-boilerplate project.


docs: Added back a post for auth0 in the readme

Description

readme: add back in post for auth0

Motivation and Context

Accidental removal in previous PR https://github.com/terraform-aws-modules/terraform-aws-atlantis/pull/188

Breaking Changes

N/A
How Has This Been Tested?

I have updated at least one of the examples/* to demonstrate and validate my change(s)
I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 3.24.0 :tada:


€ shortcut

Microsoft PowerToys version
0.72.0
Installation method
Other (please specify in "Steps to Reproduce")
Running as admin
None
Area(s) with issue?
General
Steps to reproduce
Hello, I have the problem that my € no longer works. In the shortcuts, I can't find the key combination with Alt Gr E
✔ Expected Behavior
Hello, I have the problem that my € no longer works. In the shortcuts, I can't find the key combination with Alt Gr E
❌ Actual Behavior
No response
Other Software
No response

The issue is caused by Mouse Without Borders, to be more specific by the CTRL+ALT+E shortcut.
This was supposed to be fixed by https://github.com/microsoft/PowerToys/pull/27442 but require to change or reset the shortcut.

/needinfo


Feature Request: Click on hidden number/action in chat while holding a key to unmystify it

I think it'd be helpful to have something so that when mystification is on such that players can't see the dc on something or what a special monster action does (it has a gm only/hidden outline), there's a way for gms to unmystify that as a one off if needed. Like how in a journal with hidden/gm passages there's a 'hide' button you can click next to it to turn it on and off, only for this it'd probably make more sense to allow us to click on the hidden number/box while holding a key to make it visible to all.

an easier suggestion would be to make the item reveal itself after a succesful check.


Equality documentation

@Masynchin Equality is true only if all the elements are same. I think the documentation is poor.
Originally posted by @kerelape in https://github.com/kerelape/reikai/issues/40#issuecomment-1193276240

@Masynchin can you help with this?


TMO Doti Added

Traffic management office Doti is added please review

Please only push one data field at a time! Cool btw


filter error: invalid comparison operator: glob

Falco (0.10.0) fails to start and falco -V complains with the following if the operator glob is used:
Error in filter.rel_expr() filter error: invalid comparison operator: glob

Sat Jun  2 23:46:22 2018: Runtime error: Error loading rules:C++ exception. Exiting.

Which is funny because I have found Falco supports glob by trying another invalid operator endswith:
Sat Jun  2 23:41:46 2018: Runtime error: Error loading rules:/usr/share/falco/lua/compiler.lua:390: Compilation error when compiling "evt.type in (open, openat) and fd.name startswith '/dev/snd/pcm' and fd.name endswith c and not allow_microphone_access": 78: syntax error, unexpected 'endswith', expecting 'pmatch', 'in', 'startswith', 'glob', 'icontains', 'contains', '>', '<', '>=', '<=', '!=', '==', '=', 'exists'. Exiting.

Possible duplicate of https://github.com/draios/falco/issues/337

From what I could gather, the pull request https://github.com/draios/sysdig/pull/653 failed to update userspace/libsinsp/lua_parser_api.cpp to include CO_GLOB.
This is most likely a bug in Sysdig.


v0 add autoquant

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 21.42857% with 11 lines in your changes missing coverage. Please review.

Project coverage is 72.40%. Comparing base (99339a9) to head (1adf829).

Files with missing lines
Patch %
Lines

...infinity_emb/transformer/quantization/interface.py
14.28%
6 Missing :warning:

...emb/infinity_emb/transformer/quantization/quant.py
0.00%
5 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

:exclamation:  There is a different number of reports uploaded between BASE (99339a9) and HEAD (1adf829). Click for more details.
HEAD has 5 uploads less than BASE

Flag
BASE (99339a9)
HEAD (1adf829)

6
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #402      +/-   ##
==========================================
- Coverage   78.62%   72.40%   -6.22%
==========================================
  Files          39       39
  Lines        3008     3019      +11
==========================================
- Hits         2365     2186     -179
- Misses        643      833     +190

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Consider removing lambda function in block process evolve for consistency

'is_censored': lambda p, _1, _2, s, _5: ('is_censored', check_for_censorship(p, s))
Would transform it into a formal function

sgtm


How can I render my page in the subfolder in 'pages' directory

My code:
server.get('/login', (req, res) => {
  app.render(req, res, '/user/login/', {})
})

My Folder structure:

Sorry for that.
It didn't support typescript without @zeit/next-typescript package.


Replacing with "opaque box"

Per https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/b/black-box
There are other mentions across the InterpretML release including inside the graphics, as was promoted in the Build conference.  I also suggest updating "glass box" to "transparent box" (since glass may be opaque, translucent or transparent)

@marktab : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Accessibility issues detected by axe automated check in browser

Describe the bug
axeDevTools detect 2 types of issues:

Unsupported aria attribute

alertdialog node needs an accessible name

To Reproduce
Steps to reproduce the behavior:

Go to: https://stackblitz.com/edit/vuepic-vue-datepicker?file=src%2Fcomponents%2FPlayground.vue
Open dev tools and run axeDevTools browser extension (tested in Chrome).

Expected behavior
No issues detected by the automated accessibility testing tool axe.
Desktop & mobile (please complete the following information):

Browser Version 128.0.6613.138
Library version "@vuepic/vue-datepicker": "^9.0.3"

Aide from colors that are easily changeable per design, other issues are reported specifically in stackblitz container. Low prior, but I doubt this will be worked on at all


[NFR]: Factory constructor - phpFclose protected

Remove the Factory constructor, make phpFclose protected

Resolved in 6af9f148c5dccdbbfbbccfffbb7953e0fbe958ce


replace equals/length checks by isEmpty

I noticed that quite often there happens a comparison .equals(""). However, this is not as performant as isEmpty (negligible, but whatever 🤓).
Additionally, I adjusted .length() == 0 by isEmpty as well. This is actually the same thing underneath, but isEmpty is more readable imho.
Nothing else changed in this PR.

Thanks, I have some bad habits while writing code :)

Don't we all? :)


WIP: docker in docker fix

Please note that - I'm not a JS dev, I actually haven't studied the whole project and the fix is something I really needed to make 'it work'. I believe it's not the best solution and I'm totally open to a discussion.
So the problem is that in CI I need to run sls deploy and the CI stage itself is running in a container. After some research, I found that the bindPath is assigned to its host $(pwd)$ value. The problem is, the 'docker container inside the CI docker container' thinks the host is the main CI container so the path is actually wrong. So I simply shared $(pwd) from the original host to the CI container as a host_pwd env variable and let the bindPath to take that value in case the dockerInDocker option is true.
In .gitlab-ci.yml
    - export host_pwd=$CI_PROJECT_DIR

and of course, the whole stage must be run in a container capable of running another container and in config.toml there must be docker socket specified.
and in serverless.yml
custom:
    pythonRequirements:
        dockerInDocker: true
        dockerizePip: true

What do you think?

I think a bind path option would be preferable. And you'd use it like:
custom:
    pythonRequirements:
        dockerizePip: true
        dockerBindPath: ${env:CI_PROJECT_DIR}

@kichik @heri16, this could also be a solution to weird windows bind paths (tho definitely still less user-friendly than the current solution)

Could be. In that case it would be cool if we can also have this as a command line argument. That's easier to do with different development environments.

@kichik any option can be a CLI option using serverless' variable system :wink:
custom:
    pythonRequirements:
        dockerizePip: true
        dockerBindPath: ${opt:dockerBindPath}

then use sls --dockerBindPath /foobar package

@sukovanej could you elaborate on what is meant by the bindPath is assigned to its host per value? Are you able to check the servicePath returned by the serverless framework inside your CI?

@dschep Yep, that seems like a better solution to me. 👍

@sukovanej I have the same issue - using dockerizePip in Gitlab CI, which itself runs docker-in-docker. Oddly, I only noticed a problem starting recently, when I upgraded the plugin from 3.0.7 to 4.2.4. Thanks for tracking this down and figuring it out.
Do you still plan to adjust this PR to implement a general bindPath option, or should I perhaps create a new one to do the same?
@heri16 it's possible that this is just a band-aid. I don't think I fully understand the problem yet, but I have observed the symptom:
Could not open requirements file: [Errno 2] No such file or directory: '/var/task/requirements.txt'

but I also recall other volume-related issues in this CI setup, so I'd need to dig some more to be sure that it's the same issue.

Is this issue solved? I'm facing the same problem to build in a docker in docker environment

Yup, same issue here when using Jenkins CI with docker in docker.

I’m going to help pull this over the finish line.  I will try to test this out more completely and add a test for it and recommend it’s merging when complete.  I think DID is quite critical for some folks ci systems.  I myself use kubernetes quite heavily.  I will test and fiddle with this today.  Might have a few more commits to this to add some tests and docs.   Cheers

@AndrewFarley I know DinD is not necessarily a recommended approach these days, but I agree; it still is critical in CI/CD systems such as Jenkins. In the case of Jenkins, the official tutorials still support it's usage. So it would be very helpful if serverless-python-requirements functioned out-of-the-box in CI environments that still leverage the legacy DinD approach. Thanks a ton for looking into this!

So, I hacked on this a bit this weekend and have some preliminary results.
First, the concept from this MR does work, the challenge is how to make it work reliably.  Let me discuss/debate/share some thoughts...
So, first assuming we have docker in docker support, means that I should be able to run the docker command from within docker so I can look-up information about the docker container I am in right now.  In order to do that I need to know what container ID I am running in, for that I found a neat cgroup trick I didn't know to lookup what container ID you have from within' the container..
With that above, I can query where the docker volume overlay is on the host and then can use this as a prefix for any bind url(s).  This will prevent what this MR's author had to do to make this MR work, which is to know the actual storage path of the host and set that as an environment variable.  In many cases, you won't know because it won't be hardcoded (eg: Kubernetes), and doing so is an undue burden on users.
So, I worked out a PoC doing exactly this and it seems to work reliably.  However... this is one of a multitude of use-cases and configurations of how docker would be setup.  Off the top of my head, an edge case that would fail is if any volumes are mounted which would contain the actual code that you plan to serverless deploy from.  Then your root overlay would not contain the serverless data, but the volume mount would.  I would need to add code to sift through the volumes mounted in the data from docker inspect and detect if the code you were trying to deploy is within' those volumes, and if so, use THAT as a file base instead of the root volume overlay from the trick above.  I'm thinking that I may need to add "two" new features, one to try to auto-detect the overlay/volume from the host and make it work magically, the second is to just allow you to specify what the volume will be if you know where the data volume is on the host.  The more I look at and think about this the more daunting of a task this becomes because I see all the edge cases and differing setups.
My goal, for any MR/PR I would create or approve for this would be such that...
• Docker in Docker works from a plain ubuntu 18.x instance just running Docker CE
• Docker in Docker works from AWS EKS Kubernetes (default config)
• Docker in Docker works from Google Cloud GKE (default config)
I probably won't have time to fiddle more until next weekend.  But will post here if/when I do.  Feel free to respond/comment if you have any input/ideas/support to anything I mentioned.

@AndrewFarley Thanks again for looking into this! I haven't dealt with Kubernetes, but In my opinion I don't think it is too unreasonable for the user to have to know the which volumes they have mounted on the host os. If it makes your life easier, it may be worthwhile bringing the discussion back to CI/CD, and consider the standard Docker configurations for the major CI/CD players.
From the Jenkins standpoint, I believe the user is utilizing bind mounts instead of volumes. On the host OS, there is both a DinD container running, and the Jenkins container running. The Jenkins container deploys one-or-many additional "Agent" containers which reference the mounted volumes containing the actual Serverless code to be deployed. The Serverless deployment is happening inside the Jenkins "Agent" container, and not inside the Jenkins container itself.
This is indeed difficult, because theoretically speaking you could be deploying Serverless code inside an arbitrary number of levels of nested Docker containers. I would just try and support the configurations adopted by the major CI/CD players instead of worrying about all potential DinD use cases. As DinD is slowly being replaced anyway by bind mounting the the Docker socket.

@ccampell I would disagree that DinD is being replaced by bind-mounting the docker socket; each approach has its advantages and disadvantages. The article you linked is over four years old, and DinD remains a "recommended configuration" for building docker images with Gitlab CI.

@brettdh Fair enough, that is a valid point! Here is a more recent article discussing the pros and cons of each approach. I'm inclined to agree with you, and amend my previous statement. I meant that for the particular use case of being able to run Docker commands from the confines of a containerized CI/CD system, from what I have seen, there is a general trend toward the transition of bind mounting the Docker socket and utilizing the sidecar pattern. But as always, nothing is strictly black and white, and your right there are advantages and disadvantages to each approach.

There's no reason to debate what the best/current/more secure practice of accomplishing Docker in Docker because this is out of the scope of this plugin.  This plugin will/does not care "how" you made your Docker CLI command work inside of Docker, that's on you and/or your admin to accomplish.
@ccampell To your point, I checked in a few systems that I manage and all of them you don't specify where your volumes/binds are mounted they are generated, and while I understand you do, my experience tells me this is unusual.  Additionally, most CI workflows (that I use) just check out the code whilst you are already inside your first Docker container, thus you don't know the mount ahead of time.  Having a workflow differently seems... odd to me, but I'm not debating that you can know the mount ahead of time.  Anyways, as I explained, I overcame that limitation/issue so it's a moot point.
I personally mostly run Kubernetes clusters for clients, and I heavily lean on GitlabCI personally, with the odd Jenkins setup or two and nowadays some Gitlab Actions as well, but to accomplish CI/CD for the serverless framework with this plugin for my clients I typically use an LambCI image directly as the image I start (typically inside Kubernetes) and then from in there install the Serverless framework, check out the code, and run this plugin which in that environment means I don't need Docker in Docker, I already have a comparable environment to AWS that I'm building in.  I've avoided needing to use DinD entirely which is why I never really thought this feature was needed.  In a sense, I still don't, but I don't want to generalise and assume.
In my research for solving all of this, I did stumble onto a DinD alternative which I think is very interesting and might handle this whole thing a LOT better, but it requires a lot more time investment than I'm willing to give.  I thought this might be interesting to you folks who do Docker in Docker and CI stuff: https://github.com/GoogleContainerTools/kaniko .  If that does what it says it does, I personally would probably shift most of my CI automation over from DinD to Kaniko simply for security purposes in any future CI setups of mine.  But, alas, imho that may be out of the scope of solving this direct issue, if only because I have no experience with that tool at this time.  Again keep y'all posted will have a branch you guys can try soon to get some feedback.

@ccampell  / @brettdh (or anyone) Want to test for me?  I tested via Docker via the mounted sock and via the DinD sidecar, both seem completely functional with or without caching.  There are no tests or anything, there is verbose logging as well.  I created a fork, you can use it with...
npm remove --save serverless-python-requirements
npm install --save github:andrewfarley/serverless-python-requirements#dockerindocker

From here, you either run git add/commit/push and let your CI do its thing depending how you have it setup, or just run serverless package to test out the packaging.  If you are in docker, it should detect docker-in-docker and detect the volume path and run properly.
I confirm this functional on...
• OS-X via /var/docker sock volume mount (wow, cool huh?)
• Linux Ubuntu 18.04 Test Server with Docker via .sock volume mount
• Linux Ubuntu 18.04 Test Server with Docker via dind sidecar
• Briefly worked on Kubernetes, but need to test more
Here's a snapshot of it working nicely on my Gitlab AWS autoscaling runners.  NOTE: This of course did not work before, it now works beautifully.

Feedback welcome!!!

I'm going to close this MR I've taken over the work and will finish it in #484.  Please continue the conversation and add comments over there.


Add Raw templates support

Spec Issue : https://github.com/ballerina-platform/ballerina-spec/issues/442
Make backtick strings usable for SQL parameters

@hasithaa , this is a blocker for SQL connector. We need this support for execute and batch execute operations as per doc - https://docs.google.com/document/d/1J_5gzUDopvqMJRGz04tCre79lwKLj0DtKumE7S34nlw/edit#.
I appreciate if this is added into the language ASAP. @niveathika please note.


[2.0] welcome.html is not being served correctly

On the new helm chart setup, content is being served on http://<host:port>/galaxy/ prefix. In this setting, adding a welcome.html page as describe in docker-galaxy-stable (as done here) produces that Galaxy points the browser to find the html in http://<host:port>/galaxy/web/welcome.html, however nginx seems to be serving the page in http://<host:port>/web/welcome.html.

I think that this is produced because the nginx in the container is configured to use directly / where as UWSGI is configured to use /galaxy. The problem, seems to be, is that nginx configuration happens at container build time, whereas UWSGI setup happens at runtime through environment variables.
Any opinions @bgruening ??

Ok, I think I have sorted this out by adding uwsgi variables support on the helm chart. Will PR soon after finishing tests.


@alloy => Bidder Details Request & Help Copy Changes

This is a WIP for these two issues:
Fixes #357
Work on #361
Still to do:

[x] Make "Send me my details" button and hook it up
[x] Maybe look into ways to lift some function calls into the RAC world
[ ] Actual API call (the API people are working on this right meow)
[ ] Figure out UI for between hitting "send" and getting API response
[x] Copy changes for Help menu

Went a bit nuts rewriting some code, but I like this a lot. Let me know if I can clarify anything.

@alloy Feel free to review/merge this if you like. I'll get around to calling the actual API once it's live.

Looks good :+1:


Allow measured templates to also work for Features

The Terrain Layer will also let you assign difficulty to a measured templates. You can use this for spells that set difficult terrain.
Unless I've missed something, or set it up wrong. it seems that measured templates that assign difficulty only work for spells--the terrain options do not appear on Features. Is it possible to include this on Features as well as Spells?

So I updated it to check and see if the "item" has an area effect.  And if it does, it will add the terrain controls.
That should be more accurate as any spell that doesn't have an area effect won't need the terrain controls.  And anything else that does have an area effect can now use it.
So if the feat has area effect, the terrain controls will show up.

Should be updated with the latest version.


need to add a cd src to https://dylancastillo.co/code-interpreter-chatbot-pyodide-langchain-openai/ ;-)

i ran the litestar command from the root, not realizign i needed to cd src and then run it while reading the blog post!   figured it out looking at the readme on the github repo...

Thank you. Just fixed it!


rollback add session status and can Roll back check

rollback add session status and can Roll back check
PR Checklist

[x] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes

@tdas can you help to merge this pr？

thank you @597365581 for your contribution.


prod build used in dev environments

If one imports from react-query via import webpack will use the module field which points to dist/react-query.min.mjs which uses the minified bundle.
This isn't an issue for source inspection since source maps are published but for react-devtools it means that components and hooks will have a minified names:
M is ReactQueryConfigProvider:

$ is usePaginatedQuery:

Package.json.module does not point to the minified file:

@tannerlinsley In ^1.2.0, yes. You seem to have changed this recently, thanks.


Multiple entrypoints on the same page causes chunks to be sourced multiple times

Description
When using multiple bundles on the same page, shared dependencies are included more than once. For example, when using a "global" bundle and a specific app on the same page, shared chunks between them are sourced multiple times. This is especially problematic when global libraries like bootstrap are in those shared chunks.
Expected
When rendering a template or set of templates (extension), shared chunks are sourced only once
Actual
Shared chunks are included on the rendered page more than once, breaking libraries that rely on only having one instance.
Basic example
Given 2 bundles global and pageapp and shared chunk chunk...
{% load render_bundle from webpack_loader %}
{% render_bundle 'global' 'js' %}
{% render_bundle 'pageapp' 'js' %}

output currently is
<script type="text/javascript" src="http://localhost:8001/chunk.js"></script>
<script type="text/javascript" src="http://localhost:8001/global.js"></script>
<script type="text/javascript" src="http://localhost:8001/chunk.js"></script>
<script type="text/javascript" src="http://localhost:8001/pageapp.js"></script>

I have the same problem, but it's independent of this module.
The output of webpack-bundle-tracker (the provided json file) contains the shared modules for the modules you use, and thus they will appear in the generated template, unfortunately. I'm trying to find a way for webpack to implement some kind of a singleton pattern to have the modules run only once even if they are included multiple times.

webpack-bundle-tracker is a library from django-webpack-loader team as well, so we could fix it if necessary.
However, I think the problem here is your use case. You have multiple entrypoints per HTML page. AFAIK, this is not recommended by webpack as explained here: https://github.com/django-webpack/webpack-bundle-tracker/issues/63#issuecomment-849666410
After PR https://github.com/django-webpack/django-webpack-loader/pull/232, this module tries to focus on including entrypoints (with all the chunks) in Django templates. To handle how chunks are divided between entrypoints, try a proper webpack config.
Have you tried the dependOn option + optimization.runtimeChunk: 'single' from Webpack 5? I think it enables you to separate your "global" entrypoint: https://webpack.js.org/guides/code-splitting/#prevent-duplication

Hey,
thanks for your elaborate response.
Yes I use runtimeChunk: 'single' already. My case is, I have a common.js module I include on every page (from the extended base template) , that has some initializations on the menu structure and some more smaller stuff. This common.js module also has a couple exports (utilities) that the entry points sometimes use. So the issue is, the common.js gets included many times, and in reality, as mentioned in the related issue, I only need a singleton-like pattern. At least, if it's not avoidable having it included many times, which by the looks of the generated JSON bundle report, seems to be the case.
As for using the dependOn option, I would avoid using it, since webpack should be able to do automatic tracing of what modules are used for every entry point by analyzing the provided code. I didn't really get why it was implemented in the first place, but that might be just me.

dependsOn

I'm currently using the chunks keyword, not depends on, however it still seems wrong to source a shared chunk more than once such as bootstrap.

singleton

I looked into this when I first identified the issue. Because of the minimal featureset of the Django template language, this is very difficult to do in a way that supports concurrent requests.

not recommended by webpack

I understand that, however Vue is intended to do things like this as part of its design philosophy. My use case involves a global, legacy code base using bootstrap. Individual pages are being replaced with vue in an effort to get away from jquery.

Could you please check for a similar behavior in https://github.com/jantimon/html-webpack-plugin ?
Does it automatically deduplicates common chunks when rendering the script tags inside a single html with multiple entrypoints? It seems to do so (see code below), but could you please test it?
https://github.com/jantimon/html-webpack-plugin/blob/2f5de7ab9e8bca60e9e200f2e4b4cfab90db28d4/index.js#L696-L700
If that happens with html-webpack-plugin, I guess we should implement something similar. If not, personally I don't think this is something django-webpack-loader should do.

@fjsj I think you're correct about the behavior of html-webpack-plugin.
I'll post this here in case it is helpful to someone. I just threw this together this morning, so I really wouldn't use this. I did not test that this works with keyword arguments or do any testing at all beyond the simple case. I wrote an additional template tag render_bundle_once that checks and sets a context variable that just stores a list of the script tags that have already been loaded on the page. Subsequent calls to render_bundle_once will omit script tags that were already written.
class RenderBundleOnceNode(template.Node):
    def __init__(self, bundle_name, extension=None, config='DEFAULT', suffix='', attrs='', is_preload=False):
        self.bundle_name = bundle_name
        self.extension = extension
        self.config = config
        self.suffix = suffix
        self.attrs = attrs
        self.is_preload = is_preload

    def render(self, context):
        tags = utils.get_as_tags(
            self.bundle_name, extension=self.extension, config=self.config,
            suffix=self.suffix, attrs=self.attrs, is_preload=self.is_preload
        )

        used_tags = context.get("webpack_loader_used_tags", [])
        if not used_tags:
            context["webpack_loader_used_tags"] = []
        new_tags = [mark_safe(tag) for tag in tags if tag not in used_tags]
        context["webpack_loader_used_tags"] = context["webpack_loader_used_tags"] + new_tags

        return mark_safe('\n'.join(new_tags))

@register.tag
def render_bundle_once(parser, token):
    try:
        tag_name, bundle_name, *options = token.split_contents()
    except ValueError:
        raise template.TemplateSyntaxError(
            "%r tag requires a bundle name" % token.contents.split()[0]
        )
    if not (bundle_name[0] == bundle_name[-1] and bundle_name[0] in ('"', "'")):
        raise template.TemplateSyntaxError(
            "%r tag's argument should be in quotes" % tag_name
        )
    option_names = ["extension", "config", "suffix", "attrs", "is_preload"]
    # TODO fix type of is_preload using template variable
    # TODO test that the kwargs work at all?
    kwargs = dict(zip(option_names, options))
    return RenderBundleOnceNode(bundle_name[1:-1], **kwargs)

This is awesome, a much better solution than me pestering the devs to implement the stuff in webpack!
I'm gonna give this a try and probably come up with improvements.

Thanks @TeamTeaTime
If I can read the code correctly, one can use render_bundle_once multiple times, but there will be no repetition of <script> tags for common chunks, is that right? You're using context, which seems the right way to do it (check https://stackoverflow.com/a/33564990/145349).
What @karolyi is asking for requires this context-global behavior of removing duplicates the already included script tags (by previous calls of render_bundle). I don't love this behavior, but since base templates are very common in Django, we may need it.
I was thinking instead on a render_bundle_once that accepts multiple entrypoints as argument (like a comma separated list, or even multiple first args). But this would prevent the use of render_bundle 'global' in the base template, since it would force the user to group the call of all entrypoints in a single render_bundle call, like render_bundle 'global' 'pageapp' 'js'.
So I think my suggestion above won't solve most use cases. If you really need this global behavior across multiple render_bundle calls, we can add a keyword argument to render_bundle to prevent duplication. Like:
{% load render_bundle from webpack_loader %}
{% render_bundle 'global' 'js' %}
{% render_bundle 'pageapp' 'js' skip_common_chunks=True %}

Please feel free to open a PR with this. In a future major version, we can make this default True.

I created a PR. Let me know what you think. I'm with you and I'm not sure it's a great idea to steer people toward including multiple bundles, but there are certainly cases where it could be easier than the alternative.

I'm not sure it's a great idea to steer people toward including multiple bundles

A good middle ground might be emitting a warning when the server is in develop mode.

Thanks. Closing now this issue.
Use the new parameter skip_common_chunks=True to avoid this issue. E.g.:
{% load render_bundle from webpack_loader %}
{% render_bundle "app1" %}
{% render_bundle "app2" skip_common_chunks=True %}

For more details, check the tests: https://github.com/django-webpack/django-webpack-loader/blob/1.4.0/tests/app/tests/test_webpack.py#L336


Update tmdb extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

The PR looks pretty cool, the only issue I have is that the results aren't cached with a CachedPromise, see here for example.
I would probably rewrite the fetchData functions to use the cached promises...

Brilliant, I'll add it in.

Looks good to me (apart from the pending cache change). Nice work!

OK - I think I got this right, but let me know if it's not the correct implementation.

Could you look at the review @joeynotjoe 🙂

@j3lte I appreciate the help, thank you! Hopefully it's correct now. @pernielsentikaer 👍

@Aayush9029 do you want to check this too?

LGTM


Unwind does not remove resource attributes associated during initial declaration.

Tested with chef-client 12.6.0/12.14.89 and chef-rewind 0.0.9.
We're trying to use unwind to remove some notifications from a declared resource, then redefining the resource with the correct attributes. However, the redefined resource still has the old notifications.
Our code looks like:
file '/tmp/unwind_example/bar' do
  action :nothing
end

# This will break because the containing directory doesn't yet exist
directory '/tmp/unwind_example' do
  notifies :create, 'file[/tmp/unwind_example/bar]', :before
end

# Lets fix the directory resource by unwinding and redefining it with a valid notification
unwind 'directory[/tmp/unwind_example]'

directory '/tmp/unwind_example' do
  action :create
  notifies :create, "file[/tmp/unwind_example/bar]", :delayed
end

However, this code fails to converge with Parent directory /tmp/unwind_example does not exist.
Here's an example cookbook showing this behavior.

For anyone else who runs into this, we were able to work around it by using delete_resource as in the following code.
More info here.
I initially thought that we couldn't use edit_resource or delete_resource because we aren't on chef-client 12.10+, but thanks to compat_resource, we can.


Debian{11,12}: socket bind deny policy loads but doesn't enforce rules

Debian 12 as a kvm based vm on ubuntu 22.04. Kernel 6.1.0-7-amd64.
Source code: demo_socket_listen

Same thing happens on debian 11 and amazon linux 2.

Corrections - amazon linux 2 is affected by different issue. It was fixed by https://github.com/deepfence/ebpfguard/pull/38. Debian 11 is confirmed though.

Checked default settings gcp k8s cluster today. Same stuff. According to k8s node serial console it's
Linux version 5.15.89+ (builder@localhost) (Chromium OS 14.0_pre445002_p20220217-r3 clang version 14.0.0.
Didn't set up ssh access so couldn't confirm output from say uname -r.


⚠ ClamAV has degraded performance

In 31af7ae, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: ClamAV performance has improved in 30b674e.


Cannot set class on TextInput input DOM element

What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
A TextInput when rendered creates something like

     <input type="text">

When setting class on the TextInput, like you would do in Tailwind, you might expect it to apply the classes to the input element (or at least have the option to do so with a similar class prop). However, it sets the classes on the first div element two layers up.
Workaround (For now)
You could use some of the classes svelteui is putting on the input, either in an external CSS selector or in a :global style tag e.g.

However I haven't tested if this classname will always be there in production
In which browser(s) did the problem occur?
No response
Steps To Reproduce
Use svelteui 0.9
Do you know how to fix the issue
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix
Yes
Relevant Assets
No response

Note that if you fall back to , which is of course documented with advise not to use directly, the last class name will be the variant, overwriting all other class set values as it appears last in the list. This forces the use of the headless variant.

Hi, sorry, this got forgotten.
I still have to check this out and see what can be the problem, but thank you so much for this bug report, really detailed.

Ended up reverting the change, if we want to change the style, it's better to use global stylings or the style API


ClickhouseLexer 增加ILIKE 函数

ClickhouseLexer增加ILIKE 函数，支持解析ILIKE 函数 #5900

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

请加上相应的单元测试代码


Dataclass traversal breaks delayed init and post_init

We use dataclasses.dataclass to instantiate resources. Since PR 4165, they are traversed and rebuilt on delayed. This causes:

not being able to delay __init__ and
re-invokation of __post_init__ .

from dataclasses import dataclass
from dask import delayed

@dataclass
class D:
    x: int
    y: float
    def __post_init__(self):
        print("getting expensive resource")
        self.z = self.x + self.y
    def __call__(self):
        print(self.z, "is ready")

d = D(1,1.0)
## getting expensive resource
d()
## 2.0 is ready

# Problem 1)

# Trying to instantiate a dataclass:
# AttributeError: type object 'D' has no attribute 'x' in delayed::unpack_collections
# because `is_dataclass` is True for D and instances of D
delayed(D)(1, 1.0).compute().z

# Problem 2)

# z is created twice
delayed(D(1, 1.0))().compute()
## getting expensive resource
## getting expensive resource
## 2.0 is ready

# z is created again
def operate_on(d: D):
    d()
    print("Thanks for", d.z)

delayed(operate_on, traverse=False)(d).compute()
## getting expensive resource
## 2.0 is ready
## Thanks for 2.0

dask 2.6 (and also on 2.2)
python 3.6.7 with dataclass backport
I think we can work around by delaying collections with dataclasses separately. However, I'm not sure if there are more elegant ways.
Passing traverse=False down to Delayed.__call__  is maybe one way, or discriminating between dataclasses with and without __post_init__ at some point.
(edits: wording and traverse=False for last example)

cc @aberres and @jcrist if you have thoughts.

Hmmm, interesting. Problem 1 is a bug and should be fixed. You can work around it for now by delaying a function constructor instead of calling delayed on the dataclass constructor itself.
Problem 2 is odd. We currently traverse dataclasses for sub-dask objects as we do for other simple python objects (tuples, lists, dicts, sets). The assumption being that dataclasses aren't expensive to reconstruct - they're just fancier namedtuples. To avoid traversal you can use traverse=False when wrapping an existing dataclass object (note, not the function that calls it). Given that people want the existing behavior, and theirs a (suboptimal) workaround for your use case I'm not sure if I this is something we can/should fix. Suggestions welcome.
Here's a working script that avoids both problems:
from dataclasses import dataclass
from dask import delayed

@dataclass
class D:
    x: int
    y: float
    def __post_init__(self):
        print("getting expensive resource")
        self.z = self.x + self.y

    def __call__(self):
        print(self.z, "is ready")

# Delay a function instead of the dataclass constructor
@delayed(pure=True)
def create_D(x, y):
    return D(x, y)

print("Problem 1")
d = create_D(1, 1.0).compute()

def operate_on(d: D):
    d()
    print("Thanks for", d.z)

print("Problem 2")
# Wrap the `D` object in a non-traversed delayed object first to avoid traversal
d_obj = delayed(d, traverse=False)
delayed(operate_on)(d_obj).compute()

Output:
$ python test.py
Problem 1
getting expensive resource
Problem 2
2.0 is ready
Thanks for 2.0

Thanks for the quick response.
I can make a PR for problem number 1. I'd suggest to have something like is_dataclass_obj in compatibility.py .
After all, explicitly delaying collections with dataclasses is not the worst. I imagine this to be a general use case tough, e.g. when some work like validation has been put into. Maybe mentioning that in the docs is best?


Artifact size failing in VMR in Centos9

Related to dotnet/source-build#4342
main build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2437624&view=ms.vss-test-web.build-test-results-tab&runId=53521223&resultId=100002&paneView=attachments
Most errors has been fixed in dotnet/installer#19570, except VerticalManifest.xml:
'VerticalManifest.xml' increased in size by more than 25%. It was originally 73620 bytes and is now 93949 bytes.

Thanks for the issue! Will update the baseline

Oh, there already is a PR with the update - https://github.com/dotnet/installer/pull/19588
Merged

Hi @oleksandr-didyk , this issue still exists, I noticed the artifact size of VerticalManifest.xml has been changed several times:
20240422.1: VerticalManifest.xml does not exist in baseline. It is 66136 bytes. Adding it to the baseline file.
20240423.1: VerticalManifest.xml does not exist in baseline. It is 73620 bytes. Adding it to the baseline file.
20240424.1: VerticalManifest.xml does not exist in baseline. It is 93949 bytes. Adding it to the baseline file.
20240425.1: 'VerticalManifest.xml' increased in size by more than 25%. It was originally 73620 bytes and is now 94088 bytes.
Do you have any suggestions about this?

Closing since the latest run on main is green


Remove unneeded permissions

I noticed that all browsers like brave, vivaldi, bromite and so on that are based on new chromium versions don't require contacts permission. Are contacts really needed for this new chromium based kiwi browser? I think it could be nice to remove unnecessary permissions if possible.

The contacts permission is upstream:
https://source.chromium.org/chromium/chromium/src/+/main:chrome/android/java/AndroidManifest.xml;l=59?q=android.permission.READ_CONTACTS&ss=chromium
On recent Android version, permissions are on-demand, so the contacts permission would trigger asking the user.
It's used in the contacts picker in Chromium: https://source.chromium.org/chromium/chromium/src/+/3fa1a096e48b6a6378831f8d5b61facdccd0045f


catching words not in the list?

it is catching words like "balls" that are not even in lang.json

nevermind i found it in badlist array


Why there are no alerts fired in this situation?

What did you do?
I have some metrics named start with responseTime_.*
The alert rule is
groups:
- name: automatic_flow_control
  rules:
  - alert: automatic_flow_control
    expr: deriv(label_replace({__name__=~"responseTime_.*"}, "metricname", "$1", "__name__", "(.*)")[30s:1s])>0.1
    for: 1m
    labels:
      serverity: warn
      annotations:
      summary: gateway limitation alert has invoked
      value: "value= {{ $value }}"

and the alert is well reload in the prometheus:

By clicking the expr it redirect to the graph page and showing the result graph.
Although graph shows there is at least one metric which has time intervals greater than 1m for sure (see the green line)

The alert rule is always pending and refreshing its Active Since but never fire at all, which makes the for 1m situation never reached. No debug log showing in both prometheus's log or alertmanager's log.
What did you expect to see?
Prometheus fire an alert
What did you see instead? Under which circumstances?
my test case describe can be seen in StackOverFlow
System information
windows 10 for test client and centos 7 for prometheus server
Prometheus version
prometheus, version 2.36.2 (branch: HEAD, revision: d7e7b8e04b5ecdc1dd153534ba376a622b72741b)
  build user:       root@f051ce0d6050
  build date:       20220620-13:21:35
  go version:       go1.18.3
  platform:         linux/amd64

Prometheus configuration file
global:
  scrape_interval: 5s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 5s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # scrape_timeout is set to the global default (10s).

# Alertmanager configuration
alerting:
  alertmanagers:
    - static_configs:
        - targets:
          - <IP_ADDRESS>:9093

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  - "alert_rules/gateway_flow_automatic_rule.yml"
scrape_configs:
  - job_name: "webgateway"
    scrape_interval: 5s
    metrics_path: '/actuator/prometheus'
    static_configs:
      - targets: ["<IP_ADDRESS>:8004","<IP_ADDRESS>:8005","<IP_ADDRESS>:8005"]
      #- targets: ["<IP_ADDRESS>:8004"]
  - job_name: "machine_actuator"
    scrape_interval: 5s
    metrics_path: '/actuator/prometheus'
    static_configs:
      - targets: ["<IP_ADDRESS>:13000"]

Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

#4836
issue 4836 has the same problem


Optimizing Python + Docker deploys using Pants

Description
This PR uses Optimizing Python + Docker deploys using Pants article to optimize our use of pants to build Docker images.
The PR also standardize use of environment variables by prefixing each one with TWOOPSTRACKER_, remove the mixing of twoops-tracker, twoops_tracker, etc. to just twoopstracker for package name.
Fixes #6
Type of change

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Chore (non-breaking change which does not add visible functionality but improves code quality)
[x] This change requires a documentation update

Screenshots
N/A
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

I think this is good to go now @kilemensi  @thepsalmist


Cleanup HTTPD Startup

Previously, an inability to grab port 8080 would hang the tests forever.

I didn't know if there was some magic associated with the port 8080 somewhere in the code so I just left it.

Hopefully not, since cci listens to whatever port is configured in the connected app callback URL


NIFI-2075: Addressing issues with Provenance Page

Fixing issue rendering event rows while visible in the shell.
Fixing issue go to/from the event table and lineage graph.
Fixing visibility of the event table header, search, and filter controls.

looks good....

Thanks @scottyaslan!


Improve Linter Generators

Several commits that incrementally improve the linter generation functionalities. Primarily, this change splits the linters generator into two new generators, one for linters written in JavaScript and one for linters written in Ruby. The JavaScript linter generator is now on by default, but the ruby linter is off by default.
Syntax:
--skip-js-linters (alias -j)
--ruby-linters (alias -L)
For the sake of passing linters, I have removed the sleep and bodyParser packages from client/package.json. I believe that these were only used by client/server.js for express middleware when implementing async functionality. Since the HelloWorld app does not have any async functionality, they were not needed. I have merely commented them out, however, along with the example commented-out async code.
Lastly, the missing Ruby linter configs have been added. These are verbatim what was currently in the tutorial app, and will probably need a quick review from @justin808 when he has the chance.

LGTM -- please rebase down to one commit
we should probably merge these without the --no-ff option from now on when squashed down to one commit
that requires doing this on the command line

@justin808 Just an idea before I rebase: I've done this thing before in my own repo where I do the --no-ff thing, but don't rebase. This way it will be obvious in the visual log that these commits are all bundled under a single overarching idea which is summarized by the merge commit. If you want to just stick to the main commits, you only read those ones in the leftmost column:


Adjust ping parameters to improve tor stability

Change Description
Here we do the following things to increase stability with tor peers:

Reduce maximum pong payload size to ease bandwidth consumption
Make PingManager.Stop infallible so that it doesn't pollute the logs with false errors in the case where we fail to send or receive the init message.
If we detect that the connection with our peer is over tor (heuristic), then we will triple the timeout parameters to give them more time to respond.

Steps to Test
Run this patch with a bunch of tor peers and see if it improves the long term stability of those peers.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[x] Tests covering the positive and negative (error paths) are included.
[x] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[x] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[x] Commits follow the Ideal Git Commit Structure.
[x] Any new logging statements use an appropriate subsystem and logging level.
[x] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[x]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

I ran this and it does indeed fix the problem I was seeing. Thank you!

I'm running this now, and so far so good! Will report back in the morning!

Not sure what to make of the unit-race CI check failing here.

Not sure what to make of the unit-race CI check failing here.

Appears to be a known flake.


added some API functions and database schema

Overview of tables and their attributes (for now):

Users - userId, username, password
Messages - messageId, content, roomid, userId
Rooms - roomId, roomName, createdByUserId
Room-User Mappings - userId, roomId

Overview of API functions (for now)):
User/Auth

[x]  register
[x]  login
[x]  logout

Rooms

[x]  create room
[ ]  edit room name
[ ]  delete room

Messages

[x]  get messages (latest 'x' messages)
[ ]  get messages (previous 'x' messages after the latest ones and so on)
[x]  get new message when in some room (over sockets)
[x]  post message (API/sockets)

User-Rooms

[ ]  get rooms
[ ]  join room
[ ]  leave room

Looks good. What's the purpose of the mappingUserToRoom Model though?

Looks good. What's the purpose of the mappingUserToRoom Model though?

It maps users to room and tells if the user is in any room (or can access any room). Like if a row in that table contains [userId: 'jack',  roomId: '123'], it means jack has access to room 123, if some user did not we would show a not found page for that room.


Reading UTCDateTime from before 1970 results in an exception.

Laravel-mongodb Version: 3.6.3
PHP Version: 7.3.15
Database Driver & Version: v4.0.16

Description:
Reading a date field with a value before January 1st 1970 results in a fatal exception:
ErrorException:  A non well formed numeric value encountered in vendor/nesbot/carbon/src/Carbon/Traits/Timestamp.php on line 50

Steps to reproduce
Create a record with a pre-1970 date in a date-casted field (like created_at):
db.users.insert({"email"<EMAIL_ADDRESS>"created_at": ISODate("1968-01-17T14:19:49.324Z")});

Then, try to read it as an Eloquent model:
$user = User::where('email', 'broken@example.com')->first();

print $user->created_at; // <-- ErrorException!

Expected behaviour
Dates, before or after 1970, should be correctly parsed into Carbon objects!
Actual behaviour
When trying to read a record with an UTCDateTime before 1970, the millisecond timestamp will be formed incorrectly. This causes the following error when trying to create the Carbon instance:
ErrorException:  A non well formed numeric value encountered in vendor/nesbot/carbon/src/Carbon/Traits/Timestamp.php on line 50

This seems to be because, for dates prior to 1970, both the timestamp (from U) and the milliseconds (from v) are provided as negative numbers, and so when concatenated they don't make sense (e.g. "-61724410-676" for January 1st 1968 rather than "-61724410676").
Logs:
[2020-04-22 19:45:50] local.ERROR: A non well formed numeric value encountered {"exception":"[object] (ErrorException(code: 0): A non well formed numeric value encountered at vendor/nesbot/carbon/src/Carbon/Traits/Timestamp.php:50)
[stacktrace]
#0 vendor/nesbot/carbon/src/Carbon/Traits/Timestamp.php(50): Illuminate\\Foundation\\Bootstrap\\HandleExceptions->handleError(8, 'A non well form...', '/home/vagrant/S...', 50, Array)
#1 vendor/laravel/framework/src/Illuminate/Support/DateFactory.php(217): Carbon\\Carbon::createFromTimestampMs('-61724410-676')
#2 vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(261): Illuminate\\Support\\DateFactory->__call('createFromTimes...', Array)
#3 vendor/jenssegers/mongodb/src/Jenssegers/Mongodb/Eloquent/Model.php(102): Illuminate\\Support\\Facades\\Facade::__callStatic('createFromTimes...', Array)
#4 app/Models/Model.php(165): Jenssegers\\Mongodb\\Eloquent\\Model->asDateTime(Object(MongoDB\\BSON\\UTCDateTime))
#5 vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(762): App\\Models\\Model->asDateTime(Object(MongoDB\\BSON\\UTCDateTime))
#6 vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(507): Illuminate\\Database\\Eloquent\\Model->asDate(Object(MongoDB\\BSON\\UTCDateTime))
#7 vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(357): Illuminate\\Database\\Eloquent\\Model->castAttribute('birthdate', Object(MongoDB\\BSON\\UTCDateTime))
#8 vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(323): Illuminate\\Database\\Eloquent\\Model->getAttributeValue('birthdate')
#9 vendor/jenssegers/mongodb/src/Jenssegers/Mongodb/Eloquent/Model.php(151): Illuminate\\Database\\Eloquent\\Model->getAttribute('birthdate')
#10 vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1525): Jenssegers\\Mongodb\\Eloquent\\Model->getAttribute('birthdate')
#11 app/Http/Transformers/Legacy/UserTransformer.php(37): Illuminate\\Database\\Eloquent\\Model->__get('birthdate')
#12 vendor/league/fractal/src/Scope.php(407): App\\Http\\Transformers\\Legacy\\UserTransformer->transform(Object(App\\Models\\User))
#13 vendor/league/fractal/src/Scope.php(346): League\\Fractal\\Scope->fireTransformer(Object(App\\Http\\Transformers\\Legacy\\UserTransformer), Object(App\\Models\\User))
#14 vendor/league/fractal/src/Scope.php(235): League\\Fractal\\Scope->executeResourceTransformers()
#15 app/Http/Controllers/Traits/TransformsResponses.php(33): League\\Fractal\\Scope->toArray()
#16 app/Http/Controllers/Traits/TransformsResponses.php(56): App\\Http\\Controllers\\Controller->transform(Object(League\\Fractal\\Resource\\Item), 200)
#17 app/Http/Controllers/Legacy/UserController.php(148): App\\Http\\Controllers\\Controller->item(Object(App\\Models\\User))
#18 [internal function]: App\\Http\\Controllers\\Legacy\\UserController->show('_id', '5ea05286d845374...')
#19 vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): call_user_func_array(Array, Array)
#20 vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\\Routing\\Controller->callAction('show', Array)
#21 vendor/laravel/framework/src/Illuminate/Routing/Route.php(219): Illuminate\\Routing\\ControllerDispatcher->dispatch(Object(Illuminate\\Routing\\Route), Object(App\\Http\\Controllers\\Legacy\\UserController), 'show')
#22 vendor/laravel/framework/src/Illuminate/Routing/Route.php(176): Illuminate\\Routing\\Route->runController()
#23 vendor/laravel/framework/src/Illuminate/Routing/Router.php(681): Illuminate\\Routing\\Route->run()
#24 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(130): Illuminate\\Routing\\Router->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
#25 app/Http/Middleware/RequireScope.php(22): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#26 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): App\\Http\\Middleware\\RequireScope->handle(Object(Illuminate\\Http\\Request), Object(Closure), 'user')
#27 vendor/dosomething/gateway/src/Server/Middleware/SetGuard.php(24): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#28 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): DoSomething\\Gateway\\Server\\Middleware\\SetGuard->handle(Object(Illuminate\\Http\\Request), Object(Closure), 'api')
#29 vendor/barryvdh/laravel-cors/src/HandleCors.php(36): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#30 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Barryvdh\\Cors\\HandleCors->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#31 vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(41): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#32 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\\Routing\\Middleware\\SubstituteBindings->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#33 app/Http/Middleware/ParseOAuthHeader.php(43): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#34 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): App\\Http\\Middleware\\ParseOAuthHeader->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#35 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(105): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#36 vendor/laravel/framework/src/Illuminate/Routing/Router.php(683): Illuminate\\Pipeline\\Pipeline->then(Object(Closure))
#37 vendor/laravel/framework/src/Illuminate/Routing/Router.php(658): Illuminate\\Routing\\Router->runRouteWithinStack(Object(Illuminate\\Routing\\Route), Object(Illuminate\\Http\\Request))
#38 vendor/laravel/framework/src/Illuminate/Routing/Router.php(624): Illuminate\\Routing\\Router->runRoute(Object(Illuminate\\Http\\Request), Object(Illuminate\\Routing\\Route))
#39 vendor/laravel/framework/src/Illuminate/Routing/Router.php(613): Illuminate\\Routing\\Router->dispatchToRoute(Object(Illuminate\\Http\\Request))
#40 vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(170): Illuminate\\Routing\\Router->dispatch(Object(Illuminate\\Http\\Request))
#41 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(130): Illuminate\\Foundation\\Http\\Kernel->Illuminate\\Foundation\\Http\\{closure}(Object(Illuminate\\Http\\Request))
#42 vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#43 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Fideloper\\Proxy\\TrustProxies->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#44 vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#45 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#46 app/Http/Middleware/LogMemoryUsage.php(22): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#47 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): App\\Http\\Middleware\\LogMemoryUsage->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#48 vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#49 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#50 vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#51 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#52 vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(63): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#53 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Illuminate\\Foundation\\Http\\Middleware\\CheckForMaintenanceMode->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#54 vendor/barryvdh/laravel-cors/src/HandlePreflight.php(29): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#55 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(171): Barryvdh\\Cors\\HandlePreflight->handle(Object(Illuminate\\Http\\Request), Object(Closure))
#56 vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(105): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request))
#57 vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(145): Illuminate\\Pipeline\\Pipeline->then(Object(Closure))
#58 vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(110): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter(Object(Illuminate\\Http\\Request))
#59 public/index.php(51): Illuminate\\Foundation\\Http\\Kernel->handle(Object(Illuminate\\Http\\Request))

Hi @DFurnes ,
There is not test for this case, so I have just created a pull request see #2027 . All test is successful. So I think you are not saving the date correctly.
Try to share the dump of $user or a screen from the record from a db client.

Thanks so much for the quick response & test case! I think this one is a little tricky – the bug only appears for me when I'm working with dates that have milliseconds on them.
I'll push up a test case to demonstrate what I'm seeing.

I've added a test demonstrating the issue I'm running into in 90f73d2c9b2acd7afc9c9e761e35c188036ab538.
As you showed in #2027, this bug does not occur for dates that don't have have milliseconds on them – so definitely an edge case, but unfortunately one that I ran into earlier today! 😅

Today i release new version 3.6.4

I saw the PR @DFurnes . Good job! Thanks

Thank you both for the quick responses & merge! Really appreciate it. 🙇

I released new version https://github.com/jenssegers/laravel-mongodb/releases/tag/v3.6.4


Test12

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

Summary by CodeRabbit

Optimizations

Preloading of evalWorker chunks added to improve performance in index.html.

Developer Experience

Removed outdated code and comments from CodemirrorTernService and TernWorkerService for cleaner and more maintainable codebases.
Logging added to getChunkUrls function for better debugging and tracking of chunk groups in index.html.

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview recreate=true

/build-deploy-preview skip-tests=true