Fix CI (attempt #2).

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.78%. Comparing base (3fba00d) to head (71ef291).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #746   +/-   ##
=======================================
  Coverage   91.78%   91.78%
=======================================
  Files         121      121
  Lines       32496    32496
=======================================
  Hits        29827    29827
  Misses       2669     2669

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

https://github.com/llvm/llvm-project/issues/99453
Supposedly this was fixed, but it still failed for me. On my local setup, I manually downloaded llvm and set the environment variables to point to that. That might be more stable than relying on apt-get.

Hello, I think you might have confused our repo with LLVM's.
If not, we've also been affected by this problem but in x86_64, not ARM. The problem wasn't fixed by that issue, but there has been another one here https://github.com/llvm/llvm-project/issues/101201. I can confirm that this one fixes the packaging issues in x86_64 for some distros (at least for now). More specifically, the latest ubuntu LTS (ubuntu-latest in the CI) is fixed, while debian bookworm (debian:12 on Docker) isn't yet.


CI doesn't build per commit, but per branch.

If I have a PR from a branch to which I push two commits fairly close to each other, CI is triggered twice (which is expected), but ends up building using the most recent commit, because it does the checkout based on the branch and not based on the commit sha1.
This might be seen as an unexpected behavior when afterwards looking at the logs since the logs are posted as if the test run was made using a certain commit sha1, which isn't the one CI actually used.

Fixed


Support k8gb behind a reverse proxy

Problem
K8GB reads the IP addresses it exposes from Ingress.Status.LoadBalancer.Ingress or from Service.Status.LoadBalancer.Ingress for ingresses configured with Kubernetes Ingress or Istio Virtual Service resources, respectively.
However, in some setups the clients do not route their traffic to these IP addresses because the cluster is behind a reverse proxy.
Solution
To support this setup, K8GB should expose DNS records with the IP address of the reverse proxy. Since the address is unknown to the cluster, the K8GB administrator must provide it via configuration. This PR adds to K8GB the capability to read IP address from an annotation k8gb.io/exposed-ip-addresses on the GSLB resource.
Example
apiVersion: k8gb.absa.oss/v1beta1
kind: Gslb
metadata:
  annotations:
    k8gb.io/external-ips: "<IP_ADDRESS>"

Validation
A ValidatingAdmissionPolicy was added to the helm chart to validate the value of the annotation is a valid IPv4 IP address. If that is the not the case the following error is shown:
The gslbs "failover-playground-istio" is invalid: : ValidatingAdmissionPolicy 'validate-strict-exposed-ip-annotation' with binding 'enforce-strict-exposed-ip-annotation' denied request: The annotation 'k8gb.io/exposed-ip-addresses' must contain a valid IPv4 address

If the ValidatingAdmissionPolicy is disabled the controller will also reject the resource with the following error:
2024-10-31T14:02:36Z ERR github.com/k8gb-io/k8gb/controllers/logging/logr.go:72 > events: Reconciler error {"Gslb":"aba/failover-playground-istio","controller":"gslb","controllerGroup":"k8gb.absa.oss","controllerKind":"Gslb","name":"failover-playground-istio","namespace":"aba","reconcileID":"8523077b-b9bf-4206-922b-036eb8e21a7b"} error="getting load balancer exposed IPs (invalid IP address: <IP_ADDRESS>2)"

Note: with the current testing framework it is rather cumbersome to add a test where the errors above are verified. But if we agree to proceed with chainsaw it will be quite easy: #1758
Fixes #1275

I tested with the ingress local setup and set the annotation on both test-gslb1 and test-gslb2 local clusters.
k -n test-gslb get ing failover-ingress -o yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    k8gb.io/exposed-ip-addresses: <IP_ADDRESS>,<IP_ADDRESS>
  labels:
    app: test-gslb-failover
  name: failover-ingress
  namespace: test-gslb
spec:
  ingressClassName: nginx
  rules:
  - host: failover.cloud.example.com
    http:
      paths:
      - backend:
          service:
            name: frontend-podinfo
            port:
              name: http
        path: /
        pathType: Prefix
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>
    - ip: <IP_ADDRESS>

 k -n test-gslb get gslb failover-ingress -o yaml
apiVersion: k8gb.absa.oss/v1beta1
kind: Gslb
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"k8gb.absa.oss/v1beta1","kind":"Gslb","metadata":{"annotations":{},"name":"failover-ingress","namespace":"test-gslb"},"spec":{"resourceRef":{"apiVersion":"networking.k8s.io/v1","kind":"Ingress","matchLabels":{"app":"test-gslb-failover"}},"strategy":{"primaryGeoTag":"eu","type":"failover"}}}
  creationTimestamp: "2024-10-05T10:59:11Z"
  finalizers:
  - k8gb.absa.oss/finalizer
  generation: 2
  name: failover-ingress
  namespace: test-gslb
  resourceVersion: "53488"
  uid: b9237df5-8742-400b-9102-3d40e401ca4a
spec:
  ingress: {}
  resourceRef:
    apiVersion: networking.k8s.io/v1
    kind: Ingress
    matchLabels:
      app: test-gslb-failover
  strategy:
    dnsTtlSeconds: 30
    primaryGeoTag: eu
    splitBrainThresholdSeconds: 300
    type: failover
status:
  geoTag: eu
  healthyRecords:
    failover.cloud.example.com:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
  hosts: failover.cloud.example.com
  loadBalancer:
    exposedIps:
    - <IP_ADDRESS>
    - <IP_ADDRESS>

dig @localhost -p 5053 failover.cloud.example.com +short +tcp
<IP_ADDRESS>
<IP_ADDRESS>

The mechanics work as expected 👍
However, I have some design questions.
In case of Ingress, we are setting k8gb.io/exposed-ip-addresses annotation on the referenced Ingress resource - the one that is getting resourceRef in the main Gslb spec, e.g.
  resourceRef:
    apiVersion: networking.k8s.io/v1
    kind: Ingress
    matchLabels:
      app: ingress-referenced

At the same time in case of Istio scenario, we are setting the k8gb.io/exposed-ip-addresses annotation on the Service v1 kind and it is not obvious because what is getting referenced in Gslb spec in VirtualService resource, e.g.
spec:
  resourceRef:
    apiVersion: networking.istio.io/v1
    kind: VirtualService
    matchLabels:
      app: istio

So it looks like we have some form of implementation/abstraction leak here.
I have a slightly modified design proposal: what if we set k8gb.io/exposed-ip-addresses annotation on the main Gslb resource spec itself, this way we just override any referenced network resource and make it independent from the specific underlying referenced resource
apiVersion: k8gb.absa.oss/v1beta1
kind: Gslb
metadata:
  name: test-gslb-failover
  namespace: test-gslb
  annotations:
     k8gb.io/exposed-ip-addresses: <IP_ADDRESS>,<IP_ADDRESS>
spec:
  resourceRef:
    apiVersion: networking.k8s.io/v1
    kind: Ingress
    matchLabels: # ingresses.networking.k8s.io resource selector
      app: test-gslb-failover
  strategy:
    type: failover
    primaryGeoTag:

@abaguas What do you think?

I added it to the Ingress and Service resources because those are the ones carrying the IP address information. So we would override it there.
I agree with your point, in many cases the user won't know the technical details of the ingress or k8gb to know where to place the annotation. Setting it on the GSLB also avoid annotating a resource that we do not control, which may save us from unexpected corner cases. Let's proceed with your proposal

@abaguas could you please resolve the conflict? It looks like it happened after merging another PR :)

@abaguas could you please resolve the conflict? It looks like it happened after merging another PR :)

@ytsarev done


[Dynamics 365] [Channel Integration Framework] Opening certain entities with searchAndOpenRecords fails

Observed
When invoking searchAndOpenRecords for a "phonecall" entity,
Microsoft.CIFramework.searchAndOpenRecords("phonecall", "?$filter=activityid eq '{{ id }}'", false)

The search itself returns the correct record. However, instead of opening that record a "New Phone Call" form opens instead.
Expected
The existing "phonecall" entity should open if it exists
This is not limited to phone calls as I have also observed this with the "appointments" entity as well.

@louishawkins Thanks for creating this issue. I tried this myself and observed the same behavior. I've created a bug for the dev team to investigate this issue. Please stand by till further information on this.

@louishawkins This is indeed a product bug. Dev team will work on fixing it and the fixed API will be available for use soon.
Closing this issue now.


Workflow deletion stops working

Hi,
since a week, somehow the action stops working - it just runs through but does not delete the configured workflow states anymore. Before that, everything worked fine and my prior skipped and cancelled workflows for a certain branch were deleted as expected. With "dry: true" I also see no workflows to delete, even though there are many ones listed in github actions web ui (for that branch). There is no error output from your action step.
Looks like the obtained workflow list is always zero. I dont know if something on github has changed internally that results in that behavior for instance.
I appreciate any help. Thank you in advance.
This is my configured step:
      - name: Delete skipped and canceled workflows for this branch
        uses<EMAIL_ADDRESS>        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          run_conclusions: |
            cancelled
            skipped
          save_min_runs_number: 0
          save_period: 0
          branch: ${{ steps.branch-name.outputs.current_branch }}

CI output
Run<EMAIL_ADDRESS>with:
token: ***
run_conclusions: cancelled
skipped

save_min_runs_number: 0
save_period: 0
branch: hf_123_feature-x-setup
dry: false

Hello, @norman-kapschefsky.
Thank you for your issue.
I'll test the action and fix the problem but little later. The action is not my main work, it's like pet project with continuous support.

Hi @dmvict,
thank you for checking. I'm looking forward to that, but take your time 👍

@norman-kapschefsky
I've tested the action locally and have no failures.
Then I run the next action code on the real repository
      - name: Delete skipped and cancelled runs
        uses<EMAIL_ADDRESS>        with:
          token: ${{ secrets.PRIVATE_GITHUB_TOKEN }}
          run_conclusions: |
            cancelled
            skipped
          save_period: 0
          save_min_runs_number: 0
          branch : doc

The workflow successfully deleted skipped and canceled workflows on branch doc.
I suggest that your token have no permissions for deleting.
Please, try another token and give me report.

Hi, thank you for investing time into that.
I tried a lot of things today and had strange results. But at the end it seems that it has nothing to do with your action. I just found a related bug report. It seems that the api for obtaining the workflows is not working like it should be at the moment. Several people reported the last hours/days that with added filter options the api does not respond as expected. It basically returns 0 workflows (especially for new branches o.O - maybe their index is out of control).
https://github.community/t/bug-github-api-list-workflow-runs-returns-0-runs-even-though-there-are-runs/165080/12
I guess thats the real issue where we have to wait for an api fix. But anyhow, your code shouldn't have any problems so feel free to close my issue.
Thanks again for your quick response and your effort!

Hi, @norman-kapschefsky.
Your welcome. I'm glad that my results give some statistics for your research.
And, thank you for your report.


syncer(dm): fix unstable multi-schema change tests

What problem does this PR solve?

Issue Number: close #7513
What is changed and how it works?
After https://github.com/pingcap/tidb/pull/39248 is merged into TiDB, these multi-schema change tests should work as expected.
Check List
Tests

Integration test

Questions
Will it cause performance regression or break compatibility?
No.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note
None

/cc @lance6716

https://github.com/pingcap/tidb/pull/39248 has been merged into TiDB, these multi-schema change tests should work as expected.

/run-dm-integration-test

/cc @GMHDBJD

/merge

/check-issue-triage-complete

/run-dm-integration-test

/run-verify


inconsistant parameter number about resnet101

the resnet101 training output is:
Total #vars=446, #params=49326872, size=188.17MB

it shows that resnet101 have 49326872/1024/1024=47.04M params.
however, in resnet paper, resnet101 have 1.7M params.

If this is the number you're referring to, you're talking about completely unrelated things.

@michaelklachko
hi,  the params should include weight, bias(in conv), beta, gamma(in bn), those parameter number is unrelated to the dataset.
please kindly correct me if my understanding is wrong.

Those are two different network architectures.

😥 thank you @ppwwyyxx @michaelklachko


model.ckpt-180000.data-00000-of-00001.tempstate5599057054002993368 appeared

I am running a image resnet152 model in imagenet dataset, However, when 18W step, a strange file named model.ckpt-180000.data-00000-of-00001.tempstate5599057054002993368 appeared, then my validation is wrong like
OP_REQUIRES failed at save_restore_v2_ops.cc:134 : Unknown: output/checkpoint/model.ckpt-180000.data-00000-of-00001.tempstate5599057054002993368; Input/output error .
It troubled me many days , is there anyone meet the same problem? hope someone can help me. thank you!!

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.


Bug fix joining class instances

#36 Joining Class creating temp. duplicate instance for same class - This is fixed.
Problem Details:
After joining, email is getting added to classroom for added users. This will result in updated data set.
This updated data set was getting added on every new user joining. Fixed by proper handling of updated data set merging.

@aavishkarmishra : This bug is fixed now, Please have a look. I found this while I started working on this repo. So logged it as I didn't know the cause of this bug. But while working in edit & update flow - I found solution for this bug as well. So committed as a separate branch.
Please review.

@harshareddy794 , @mohit355 , @aavishkarmishra : Can you please review this

Thanks for your contribution 💯


fix subscription validation logic

The updated error message added in #105  was incorrect for the check.  Changing the check to look for an empty subscription id returns the behavior to the previous and includes the improved error message.

LGTM -- @smurawski we require all commits to be signed

@imiller31 I signed and signed off, so it should be covered now ;)
Thanks!


Problem with DallasTemperature and digitalWrite

Hi,
I'm trying to write simple thermostat, but found that after initializing DallasTemperature instance I can't write data into pin. I'm using RPi with Arduino UNO.
Code:
from nanpy import SerialManager, ArduinoApi, DallasTemperature
import time
import logging
logging.basicConfig(level=logging.DEBUG)

def main():
    connection = SerialManager(device="/dev/ttyACM0", baudrate=115200)
    a = ArduinoApi(connection=connection)
    a.pinMode(13, a.OUTPUT)

    sensors = DallasTemperature(2, connection)  # (*)
    # setResolution & requestTemperatures here

    while True:
        a.digitalWrite(13, a.HIGH)
        time.sleep(1)
        a.digitalWrite(13, a.LOW)
        time.sleep(1)

if __name__ == "__main__":
    main()

and last lines of the logs:
DEBUG:nanpy.serialmanager:sending:'DallasTemperature\x00'
DEBUG:nanpy.serialmanager:sending:'0\x00'
DEBUG:nanpy.serialmanager:sending:'1\x00'
DEBUG:nanpy.serialmanager:sending:'new\x00'
DEBUG:nanpy.serialmanager:sending:'2\x00'
DEBUG:nanpy.serialmanager:received:'0\r\n'
DEBUG:nanpy.serialmanager:sending:'A\x00'
DEBUG:nanpy.serialmanager:sending:'0\x00'
DEBUG:nanpy.serialmanager:sending:'2\x00'
DEBUG:nanpy.serialmanager:sending:'dw\x00'
DEBUG:nanpy.serialmanager:sending:'13\x00'
DEBUG:nanpy.serialmanager:sending:'1\x00'
^C

Afrter removing line (*) all works fine, diod blinks.

Have you edited cfg.h file including Dallas temperature library?

Hey @xaratt ,
I experienced the same problem with Raspbian yesterday, I found this workaround: https://github.com/nanpy/nanpy/commit/a272ed9b20a362fda86cb2cfb1a069bd0a58a6de
Please try installing Nanpy from source
git clone git@github.com:nanpy/nanpy.git
cd nanpy
python setup.py install
and try using rtscts parameter in SerialManager. You can find an example here:
https://github.com/DjangoBeer/minecraftpi-hack/blob/master/altimeter/altimeter.py
Let me know if it works, this fix will be included in the next release, Nanpy 0.9.4.

Too old... closing


[Bug]: Lightning invoice transaction is updated on Balance but no history in wallet transactions

Describe the bug
I shared ln invoice of 10k sats for testing . Transaction is success from other end and balance has updated on bitkit but there is no history on wallet transaction. Transaction happened on 27-03-2023 but didnt update on history.
Screenshots / Recording

Operating system
Android 11
Bitkit version
43
Log output
DEBUG (JS): setAccountStoragePath() success.
DEBUG (JS): readFromFile() success. "seed"
DEBUG (JS): initChainMonitor() success.
DEBUG (JS): initKeysManager() success.
DEBUG (JS): initNetworkGraph() success. "Rapid gossip sync Enabled"
DEBUG (JS): initUserConfig() success. {"channel_handshake_config":{"announced_channel":false,"minimum_depth":1,"max_htlc_value_in_flight_percent_of_channel":100},"manually_accept_inbound_channels":false,"accept_inbound_channels":true}
INFO (LDK): Successfully loaded channel b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef
INFO (LDK): Persistence of new ChannelMonitor for channel b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef completed
DEBUG (JS): initChannelManager() success. {"network":"mainnet","bestBlock":{"height":787232,"hex":"00e00020770522ca16c40f96ed374cf250c8b4cf1d380ef873530100000000000000000077132b2dba7dc845418147dff14d4367a310f14834f303802c9d0bd90a1af97ba29d4a6439c705177df1ba08","hash":"00000000000000000002c30e4c8bce762bdcb93f5e9fa559cb9c6dbc5fce3a67"}}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): updateFees() success. {"highPriority":42,"normal":35,"background":25}
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (LDK): Finished noise handshake for connection with 0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9
DEBUG (JS): addPeer() success. {"pubKey":"0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9","address":"<IP_ADDRESS>","port":9735,"timeout":4000}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "channel_manager.bin"
INFO (LDK): Received peer Init message from 0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9: DataLossProtect: required, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: supported, StaticRemoteKey: required, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, AnchorsZeroFeeHtlcTx: supported, ShutdownAnySegwit: supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: not supported, ZeroConf: not supported, unknown flags: supported
DEBUG (LDK): Generating channel_reestablish events for 0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9
DEBUG (LDK): Received channel_update for channel b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.
DEBUG (LDK): Reconnected channel b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef with no loss
DEBUG (LDK): Handling SendChannelReestablish event in peer_handler for node 0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9 for channel b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): readFromFile() success. "channel_manager.bin"
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): nodeId() success.
DEBUG (JS): version() success.
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
ERROR (JS): decode() failed: Error: decode_invoice_fail
DEBUG (JS): createPaymentRequest() success.
DEBUG (JS): addPeer() success. {"pubKey":"0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9","address":"<IP_ADDRESS>","port":9735,"timeout":5000}
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): nodeId() success.
ERROR (JS): decode() failed: Error: decode_invoice_fail
DEBUG (JS): createPaymentRequest() success.
DEBUG (JS): addPeer() success. {"pubKey":"0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9","address":"<IP_ADDRESS>","port":9735,"timeout":5000}
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (LDK): Marking channels with 0296b2db342fcf87ea94d981757fdf4d3e545bd5cef4919f58b5d38dfdd73bf5c9 disconnected and generating channel_updates.
DEBUG (JS): readFromFile() success. "channel_manager.bin"
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): nodeId() success.
DEBUG (LDK): New best block<PHONE_NUMBER>0000000001dccbda4a024ec361744df5f817be966bb0260ca51807 at height 787233 provided via best_block_updated
DEBUG (LDK): Updating claims view at height 787233 with 0 claim requests
DEBUG (LDK): Updating claims view at height 787233 with 0 matched transactions in block 787233
DEBUG (JS): syncToTip() success. {"header":"00002020673ace5fbc6d9ccb59a59f5e3fb9dc2b76ce8b4c0ec302000000000000000000ff25bd10771cf8d063a11fcb7817f204a99c3e9b3e87b80c68e490dd674700c61ca44a6439c705170e550f68","height":787233}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "channel_manager.bin"
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): decode() success.
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (JS): nodeId() success.
DEBUG (LDK): New best block<PHONE_NUMBER>0000000005b1d6c29b947000c76d2b0055cfb181c58a4af4a1ab8b at height 787234 provided via best_block_updated
DEBUG (LDK): Updating claims view at height 787234 with 0 claim requests
DEBUG (LDK): Updating claims view at height 787234 with 0 matched transactions in block 787234
DEBUG (JS): syncToTip() success. {"header":"00e0ff3f0718a50c26b06b96be17f8f54d7461c34e024adacbdc01000000000000000000385284f0e4866635b72e7a99bcc0e3026860bcccca178c8ed0b88bbfb604f4b9b4a64a6439c7051718fef165","height":787234}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "channel_manager.bin"
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (LDK): New best block<PHONE_NUMBER>0000000004dd71ead67d7409f5250583ca40efe940420b41f90917 at height 787235 provided via best_block_updated
DEBUG (LDK): Updating claims view at height 787235 with 0 claim requests
DEBUG (LDK): Updating claims view at height 787235 with 0 matched transactions in block 787235
DEBUG (JS): syncToTip() success. {"header":"002000208baba1f44a8ac581b1cf55002b6dc70070949bc2d6b105000000000000000000d47798baaeaaade41a32d365b1c260813899ff822af451e63e0f8ebe2206b54a18a74a6439c70517b15afa08","height":787235}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (LDK): New best block<PHONE_NUMBER>0000000004c3b04feb189b650aa7c8417837139a15a6b94bf159ac at height 787236 provided via best_block_updated
DEBUG (LDK): Updating claims view at height 787236 with 0 claim requests
DEBUG (LDK): Updating claims view at height 787236 with 0 matched transactions in block 787236
DEBUG (JS): syncToTip() success. {"header":"00e008281709f9410b4240e9ef40ca830525f509747dd6ea71dd04000000000000000000149bf8cb49c1d476230aec34ef39541db522753042becbc390ac251a7309fca5dca74a6439c7051758ecf2e6","height":787236}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (LDK): New best block<PHONE_NUMBER>000000000024f2dd576695b28671e8e535bb88a78977b1b16ffb5a at height 787237 provided via best_block_updated
DEBUG (LDK): Updating claims view at height 787237 with 0 claim requests
DEBUG (LDK): Updating claims view at height 787237 with 0 matched transactions in block 787237
DEBUG (JS): syncToTip() success. {"header":"00004020ac59f14bb9a6159a13377841c8a70a659b18eb4fb0c3040000000000000000001a9199409b28bdae8cfc59a3fe2bee214cd39a4b4ee693def55a5106db986d912da84a6439c70517265ad76b","height":787237}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): readFromFile() success. "channel_manager.bin"
DEBUG (JS): nodeId() success.
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (LDK): New best block<PHONE_NUMBER>00000000024cf9361967b17752a245dffe0f066cc9bc8ca95d40c4 at height 787238 provided via best_block_updated
DEBUG (LDK): Updating claims view at height 787238 with 0 claim requests
DEBUG (LDK): Updating claims view at height 787238 with 0 matched transactions in block 787238
DEBUG (JS): syncToTip() success. {"header":"0000c0205afb6fb1b17789a788bb35e5e87186b2956657ddf224000000000000000000002e0e365df6254d4356fca90209025213a7e123d970e4b14d5502713670d2aa6cbbaa4a6439c705172082ec2d","height":787238}
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): readFromFile() success. "channel_manager.bin"
DEBUG (JS): nodeId() success.
DEBUG (JS): listChannelFiles() success. "Files: 1"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "b83378164559cb9cb6eb310020143fbffaf255d0c1455ca3b216341d9c3836ef.bin"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "peers.json"
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): readFromFile() success. "broadcasted_transactions.json"
DEBUG (JS): readFromFile() success. "payment_ids.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]
DEBUG (JS): nodeId() success.
DEBUG (JS): readFromFile() success. "confirmed_transactions.json"
DEBUG (JS): readFromFile() success. "confirmed_outputs.json"
DEBUG (JS): listChannels() success. "Channels: 1"
DEBUG (JS): claimableBalances() success. [{"type":"ClaimableOnChannelClose","claimable_amount_satoshis":29396}]

Hi, I thank you for testing Bitkit and especially for letting us know about this bug. We will take a look at it.

unable to reproduce so far, made a few tx from Bitkit to Breez via LN, all worked, history is accurate in Bitkit.
I closed and re-opened the app, balance and history remain correct

https://github.com/synonymdev/react-native-ldk/pull/136

Leaving this open until the fix is in a Bitkit release


[SMALLFIX] Bump released version to 1.8.1 in master branch

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/532/
Test PASSed.


Images are not loaded in scrollable container

If you have a container on a page that has fixed size and overflow: scrolling;, images inside this container are not lazy loaded when you scroll just the container it self. If you first scroll the container and then the whole page => images are loaded.

Hi @peritpatrio, I must have lost this issue notification. Sorry about that.
To lazy load images inside a scrollable container, you must pass the scrollable container element in the container option of lazyload.
See the demos and the code here.

Thanks for the clarification!

First off: great work on this.  I just swapped out from Tuupola version and you are right - noticeable performance boost.
Is there a way to do lazyloading in two dimensions?  For example on this page, http://verlok.github.io/lazyload/demos/multiple_container.html the second "scrollable container" is below the fold, so it would be great to not have to load the images in the viewable part of this container until the y scroll pixel reaches it.  And then only load the images in the x dimension when the user scrolls horizontally to them.
For my application, I'm building a Netflix / iTunes style browse page where I have horizontally scrollable lists of images (that have overflow-x: scroll) but then there are many of these as you scroll down the main page.  I'd like to have the lazyload work in both dimensions.  How much effort would this be?

Thank you for the compliments, much appreciated.
But wait there, to do something like Netflix or iTunes, if you have many horizontally scrollable containers, in each container it should just work like in the demo you linked above, doesn't it?
Oh I see what you want to do. Doing that the user would download "only" the first 3 images for each horizontal container, but if you have many, you still load many images.
So you want lazyload to act horizontally in each horizontal scrollable container, and the ability to "activate" lazyload... lazily, so when they enter the viewport.
I'm pretty sure you can to this using my script without too many modifications, but I have to do some tests (and now I'm on holidays until Monday 25th July). The idea would be to use lazyload on each scrolling container and listening to some event it launches to activate a new Lazyload on the container itself.

Could you open a new issue titled "lazily load lazyload" with what you described here?

Thank you, @verlok! I posted the the new issue as you requested.


[QUEST] Ember Engines with package API

Ember Engines proved to be very useful composability primitive: it allows multiple logical applications to be composed together into a single one.
The first iteration of Ember Engines was impacted by the lack of Ember CLI public APIs. That led to quite a few API extensions and using public tree to produce engines files.
Moving forward, Ember Engines should take advantage of the new public package API that Ember CLI provides. Ember Engines will lean on build pipeline more and will only provide configuration for it. This will result into a more straightforward implementation as well as improve application build speed.
For more context, please read Ember Engines 1.0 roadmap.
Action plan

[ ] implement ember-engines packager

[ ] eager engines (bundled with vendor.js files)
[ ] lazy loading (bundled separately)

[ ] preserve current behaviour and ensure backward compatibility:

[ ] EmberEngine.extend
[ ] lazyLoading option
[ ] noManifest option
[ ] fastboot support
[ ] testing API (engineResolverFor, asset-manifest)
[ ] eager engines are bundled into the host application's vendor.js file
[ ] app folder should be ignored (files in this folder don't make much sense in the context of engines)
[ ] files inside addon folder will be bundled into engine.js file and will be processed as per addon behaviour
[ ] files in  public folder should appear at the root of the engine w/o transformation
[ ] asset-manifest.json must be generated, and a meta tag config should be inserted inside of the host application's index.html when lazyLoading option is enabled
[ ] import should work as expected

[ ] identify deprecated APIs if any:

[ ] _processedExternalTree is overriden
[ ] _concatStyles is overriden

[ ] identify missing APIs in ember-cli if any; take a closer look at the added ember-engines APIs and brainstorm if they are could be extracted/generalized:

[ ] treeForEngine
[ ] ancestorHostAddons
[ ] nonDuplicatedAddonInvoke
[ ] engineConfig
[ ] getAddonsConfig
[ ] updateFastBootManifest
[ ] getEngineConfigContents
[ ] useDeprecatedIncorrectCSSProcessing

[ ] address test failures

Run your application w/ experimental API

Clone ember-cli and ember-engines
yarn link ember-cli and ember-engines
Make changes to ember-cli-build as specified below
Run your application with EMBER_CLI_PACKAGER=true ember serve

The working version of how to use the new API within a host application:
'use strict';

const EmberApp = require('ember-cli/lib/broccoli/ember-app');
const mergeTrees = require('broccoli-merge-trees');
const packageEngines = require('ember-engines/lib/packager');

module.exports = function(defaults) {
  let app = new EmberApp(defaults, {
    package(fullTree) {
      // `dist/engines-dist` folder
      let enginesDist = packageEngines.call(this, fullTree);

      // regular `assets` folder
      let applicationDist = this.defaultPackage(fullTree);

      return mergeTrees([enginesDist, applicationDist], {
        overwrite: true,
        annotation: 'Application Dist + Engines'
      });
    }
  });

  return app.toTree();
};

Once and if we agree on the API above, we could work on providing a codemod which would allow mainless migration.

I imagine we’d also need to update the blueprints as part of this work? Both for in-repo engines (in this repo) and standalone engines (here).

@mike183 possibly! afaik, we use ManifestGenerator + a bunch of properties in engine's index.js file; if that were to change, we would need to update blueprints. I'm not sure it would right now. Or is there something else you were referring to?

@twokul I look forward to being able to help. Could we best describe each task? Packager API is still very private.

@twokul Sorry for the delayed response.
I had just assumed that with a codemod being mentioned that the required changes may also need to be made within the blueprint output?

@twokul how is it going from here? package API ready to integrate with ember-engines? I'd love to be able to help.

@twokul @dgeb @rwjblue @MelSumner how is it going from here? package API ready to integrate with ember-engines? I'd love to be able to help.

@rwjblue can you close this in favor of embroider?

@dgeb @stefanpenner can you close this in favor of embroider? we still do not know how code splitting and lazy loading will work in the ember.js ecosystem, it's very alpha with @ef4

Yes, embroider will soon provide our packaging (via webpack, rollup, etc), so it's probably best to close this issue to avoid confusion.


Warning in 0.18.1: no previous prototype for 'nsec_to_clock_t' [-Wmissing-prototypes]

Describe the bug
NOT a bug, just a warning that I caught that might turn into a build error depending on how the compiler feels on a particular day or config:
/usr/bin/x86_64-pc-linux-gnu-gcc-14 -Wp,-MMD,/tmp/portage/dev-debug/scap-driver-0.18.1/work/libs-0.18.1_build/driver/src/.ppm_cputime.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -march=native -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -O2 -fno-allow-store-data-races -fstack-protector -fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -fmin-function-alignment=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wenum-conversion -Wextra -Wunused -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-packed-not-aligned -Wno-format-overflow -Wno-format-truncation -Wno-stringop-truncation -Wno-override-init -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -Wno-unused-parameter -g -gz=zstd -DHAS_ACCESS_OK_2 -DHAS_CLASS_CREATE_1 -DHAS_DEVNODE_ARG1_CONST  -DMODULE  -DKBUILD_BASENAME='"ppm_cputime"' -DKBUILD_MODNAME='"scap"' -D__KBUILD_MODNAME=kmod_scap -c -o /tmp/portage/dev-debug/scap-driver-0.18.1/work/libs-0.18.1_build/driver/src/ppm_cputime.o /tmp/portage/dev-debug/scap-driver-0.18.1/work/libs-0.18.1_build/driver/src/ppm_cputime.c   ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --orc --static-call --uaccess   --module /tmp/portage/dev-debug/scap-driver-0.18.1/work/libs-0.18.1_build/driver/src/ppm_cputime.o
/tmp/portage/dev-debug/scap-driver-0.18.1/work/libs-0.18.1_build/driver/src/ppm_cputime.c:342:10: warning: no previous prototype for 'nsec_to_clock_t' [-Wmissing-prototypes]
  342 | uint64_t nsec_to_clock_t(uint64_t x) {
      |          ^~~~~~~~~~~~~~~

As far as I can see nsec_to_clock_t is only used in driver/main.c so maybe it would be better to move it there and make it static. Alternatively conjure up a prototype in some common header.
How to reproduce it
Should reproduce with any build using sufficient -Wwarnings.
Expected behaviour
No warnings.
Environment

OS:

Gentoo

Kernel:

Linux 6.11.6-rc

Installation method:

Build from source package (Gentoo ebuild).
Additional context
It seems I missed this in the previous release cycle - sorry!

Since nsec_to_clock_t already has a prototype in jiffies.h I found it easiest to just include it. :sweat_smile:
No more warning, builds & works fine.


make master the default branch

master-next is currently marked as the default branch.
https://github.com/open-power/eCMD/branches
Please change this to master.

Hi,
We have this set to master-next for the short term since anyone getting started we want to use eCMD 15.0.  Once the remaining work on 14.x (master) for current users is taken care of, we'll merge master-next to master and make master the default.
Any issue with that?  We're open to input on best practices.

If it was me, I would just call the 15.0 work master since that what you want people to use.  I'd have a second branch called ecmd-14.x that has that work and will be merged into master later.  I'd drop the name master-next as it doesn't make sense in this context (from what you wrote).

master is now the default branch


Bug: Supabase TPCH data loading timeout using Postgres Data Connector with Acceleration

Describe the bug
Supabase TPCH tables cannot be all successfully loaded using Postgres Data Connector with Acceleration. Only the first few tables are successfully loaded, while the rest are constantly retrying and have timeout errors:
Spice.ai runtime starting...
2024-07-11T22:54:06.157962Z  INFO spiced: Metrics listening on <IP_ADDRESS>:9000
2024-07-11T22:54:06.160867Z  INFO runtime::http: Spice Runtime HTTP listening on <IP_ADDRESS>:3000
2024-07-11T22:54:06.160888Z  INFO runtime::flight: Spice Runtime Flight listening on <IP_ADDRESS>:50051
2024-07-11T22:54:06.161185Z  INFO runtime::opentelemetry: Spice Runtime OpenTelemetry listening on <IP_ADDRESS>:50052
2024-07-11T22:54:06.161840Z  INFO runtime: Initialized results cache; max size: 128.00 MiB, item ttl: 1s
2024-07-11T22:54:06.820149Z  INFO runtime: Dataset customer registered (postgres:customer), acceleration (arrow), results cache enabled.
2024-07-11T22:54:06.821310Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset customer
2024-07-11T22:54:07.316753Z  INFO runtime: Dataset lineitem registered (postgres:lineitem), acceleration (arrow), results cache enabled.
2024-07-11T22:54:07.317910Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset lineitem
2024-07-11T22:54:08.343995Z  INFO runtime: Dataset orders registered (postgres:orders), acceleration (arrow), results cache enabled.
2024-07-11T22:54:08.345255Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset orders
2024-07-11T22:54:08.873880Z  INFO runtime: Dataset part registered (postgres:part), acceleration (arrow), results cache enabled.
2024-07-11T22:54:08.875030Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset part
2024-07-11T22:54:09.400861Z  INFO runtime: Dataset partsupp registered (postgres:partsupp), acceleration (arrow), results cache enabled.
2024-07-11T22:54:09.402467Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset partsupp
2024-07-11T22:54:36.822981Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset customer: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:54:37.738209Z  WARN runtime: Unable to get read provider for postgres: Unable to get a DB connection from the pool: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:54:37.951863Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset customer
2024-07-11T22:54:38.877397Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset part: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:54:39.600911Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset part
2024-07-11T22:54:41.288844Z  INFO runtime: Dataset region registered (postgres:region), acceleration (arrow), results cache enabled.
2024-07-11T22:54:41.290330Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset region
2024-07-11T22:54:41.384490Z  INFO runtime::accelerated_table::refresh_task: Loaded 5 rows (14.45 kiB) for dataset region in 94ms.
2024-07-11T22:54:42.189837Z  INFO runtime: Dataset supplier registered (postgres:supplier), acceleration (arrow), results cache enabled.
2024-07-11T22:54:42.191005Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset supplier
2024-07-11T22:54:42.737344Z  INFO runtime::accelerated_table::refresh_task: Loaded 10,000 rows (1.80 MiB) for dataset supplier in 546ms.
2024-07-11T22:55:07.953156Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset customer: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:55:09.576799Z  WARN runtime: Unable to get read provider for postgres: Unable to get a DB connection from the pool: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:55:09.602465Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset part: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:55:10.028093Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset customer
2024-07-11T22:55:11.493473Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset part
2024-07-11T22:55:11.756575Z  INFO runtime: Dataset nation registered (postgres:nation), acceleration (arrow), results cache enabled.
2024-07-11T22:55:11.758134Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset nation
2024-07-11T22:55:11.849261Z  INFO runtime::accelerated_table::refresh_task: Loaded 25 rows (19.55 kiB) for dataset nation in 91ms.
2024-07-11T22:55:40.029648Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset customer: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:55:41.495521Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset part: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:55:43.016348Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset customer
2024-07-11T22:55:44.632312Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset part
2024-07-11T22:56:06.627764Z  INFO runtime::accelerated_table::refresh_task: Loaded 800,000 rows (125.14 MiB) for dataset partsupp in 1m 57s 225ms.
2024-07-11T22:56:09.128350Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset lineitem: External error: Execution error: Failed to fetch batch: db error: ERROR: canceling statement due to statement timeout
2024-07-11T22:56:10.292257Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset lineitem
2024-07-11T22:56:10.566816Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset orders: External error: Execution error: Failed to fetch batch: db error: ERROR: canceling statement due to statement timeout
2024-07-11T22:56:11.768479Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset orders
2024-07-11T22:56:13.019095Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset customer: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:56:14.634144Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset part: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
2024-07-11T22:56:16.990559Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset customer
2024-07-11T22:56:20.195475Z  INFO runtime::accelerated_table::refresh_task: Loading data for dataset part
2024-07-11T22:56:46.992790Z  WARN runtime::accelerated_table::refresh_task: Failed to update dataset customer: External error: Execution error: ConnectionPoolRunError: Timed out in bb8
^C2024-07-11T22:56:49.208116Z  INFO runtime: Goodbye!

To Reproduce

Load TPCH data into supabase
Connect to Supabase using Postgres Data Connector with in-memory arrow acceleration
Run spice run

Expected behavior
Supabase tpch datasets should be successfully loaded using postgres data connector along with in-memory acceleration. If the data loading will be retried, the warning logs should display retry.
Spicepod
Output of the describe table
Output of explain query
spice, spiced, OS info

spice version: CLI version:     v0.15.2-alpha-rc.45513a3a Runtime version: v0.15.2-alpha-rc.45513a3
spiced version: v0.15.2-alpha-rc.45513a3a
OS info: Darwin Qianqians-MBP-2.home 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000 arm64

Have you tried this on the latest trunk branch?
Yes
If possible, run spiced with DEBUG log level
yes
Additional Context
Might be related to Supabase timeout setting: https://supabase.com/docs/guides/platform/custom-postgres-config#supported-parameters

Post investigation results here:

Spice OSS isn't holding on to any connection after fetching the data. Confirmed from the following observations

Number of active connections checked from CLI: run supabase inspect db role-connections, active connection is always 1 for junior_dev role used in testing

Logs in supabase: Socket closed after data loaded in Spice

Unload a dataset that is successfully loaded, the dataset that previously failed keep failing

Closed as not planned


SeisNoise.correlate corr_type arguments

Hello Timothy,
I'm trying to use arguments in corr_type's correlate function. I am particularly interested in using coherence and PCC. However, these do not work. For example:
C = correlate (FFT [jj], FFT [kk],maxlag, corr_type= "PCC")
I am also interested in using the phase-weighted stack in the next sentence:
stack!(C, allstack = true)
How include the argument?
Thanks for the feedback

Hello - thanks for pointing this out! Apologies, I believe the documentation is a little unclear here -  if you want to use the PCC, you need to use the phase function to create FFTData from RawData. Here is a MWE for using phase:
using SeisNoise, SeisIO
fs = 40. # sampling frequency in Hz
freqmin,freqmax = 0.1,0.2 # min and max frequencies
cc_step, cc_len = 450, 1800 # corrleation step and length in S
maxlag = 60. # maximum lag time in correlation
s = "2019-02-03"
t = "2019-02-04"
S1 = get_data("FDSN","CI.SDD..BHZ",src="SCEDC",s=s,t=t)
S2 = get_data("FDSN","CI.PER..BHZ",src="SCEDC",s=s,t=t)
R = RawData.([S1,S2],cc_len,cc_step)
FFT = phase.(R) # use phase function to get analytic representation
C = correlate(FFT[1],FFT[2],maxlag, corr_type="PCC")

I need to make a fix for the phase function, will get that out shortly. I can also have the correlate function automatically check if we should use the ifft or irfft in the correlate function based on the size of the input FFTData.
For the stack and stack! functions you would do:
stack!(C, allstack=true, stacktype=pws)

or you could just use the pws function:
pws(C, pow)

which will do the same thing.
Looks like I need to fix the docstring in stack!. to correctly use stacktype.

Thanks Timothy, functions are working


Installer <IP_ADDRESS> not open in Os X 10.11.6

Hi:
The version I had installed does not authenticate on flick due to a problem with SSL: SSL_ERROR_RX_RECORD_TOO_LONG.
Under the current version <IP_ADDRESS> and the installer does not open on my mac with OS X 10.11.6
The crash message is:
Time Awake Since Boot: 4400 seconds
System Integrity Protection: enabled
Crashed Thread:        0
Exception Type:        EXC_CRASH (Code Signature Invalid)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
kernel messages:
VM Regions Near 0x1034522b8 (cr2):
VM_ALLOCATE<PHONE_NUMBER>35f000-0000000100360000 [    4K] rw-/rwx SM=ALI
-->
STACK GUARD            00007fff5bc00000-00007fff5f400000 [ 56.0M] ---/rwx SM=NUL  stack guard for thread 0
Thread 0 Crashed:
0   dyld                          	0x00007fff6d622000 _dyld_start + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000000000000d  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000
rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x00007fff5fbffbd8
r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
rip: 0x00007fff6d622000  rfl: 0x0000000000000201  cr2: 0x00000001034522b8
Logical CPU:     0
Error Code:      0x0200003b
Trap Number:     133
I'm going to see if there is an intermediate version that works for me, but what is the problem, have the requirements changed, and now I need 10.12 or any other version higher than the one I have installed, 10.11?
I think I have installed it on another mac with Catalina (10.15) without problem, and your website still establishes a requirement of 10.6 so it should work or not?
Regards
Jose Luis

The problem seems to be related to the invalid signature, and the previous version <IP_ADDRESS> gives me the same error message. However, the version that I already have installed opens correctly, and does not install anything as it is identical.
Regards
Jose Luis

@MacTerrassa - can you please check if the workaround mentioned here helps?

Hello, the proposal to modify the authentication link manually from https to http, works correctly to identify from the previous version.
This fixes my problem with the old version I had installed that I couldn't get before.
However, the problem with the last two versions remains. I have downloaded the disk images again, to check if it was a failure in my previous download, and it keeps giving me the same error message in the signature. I can't install anything then. At least now I can try the old version again, a workaround. Thanks.

I have also tried to change in system preferences to allow the installation of applications from anywhere (third option),
since I normally use the second one: Mac App Store and identified developers, but it keeps giving me the same fault with the same message of Code Signature Invalid.
I understand that by declaring the seal invalid, it no longer allows its installation even allowing all installers.
Regards
Jose Luis

The installer: flickr downloadr (v<IP_ADDRESS>).dmg doesn't open under Mac OS 11.1.
It reports downloadr (v<IP_ADDRESS>).dmg is broken and can't be opened.
Any idea what to do?

In my case, and with 10.11 El Capitan, the zip is unzipped as a dmg image, and mounted on the desktop. What's not working is the app inside it - double-clicking it closes again and presents me with the system error message from my first message.
On another computer, with 10.15 Catalina, I have installed it without any problem. Although you might have to go to preferences> security> general and hit the unsafe app authorization button. Something that the system does not warn, you have to realize it and shortly after trying to run the application. Because after a few minutes, it disappears. Increasingly, Apple is promoting the total closure of its platform. And without taking into account the user at all, without the slightest notice of what the problem is. When I have had to update, I have been thinking about it a lot for that very reason. I didn't make the change from El Capitan to Catalina, because of the fear that these changes generate in me, which reduce usability so much. And I have not yet dared with Big Sur, and apparently, I may keep the new mac with Catalina until they force me.

I have tried the new versions, and all of them keep giving me the same problem, until <IP_ADDRESS> at least, I can open the dmg, but the application does not open and generates a message of "Code signature invalid".

I have tried the new versions, and all of them keep giving me the same problem, until <IP_ADDRESS> at least, I can open the dmg, but the application does not open and generates a message of "Code signature invalid".

@MacTerrassa - sorry, I was not able to test this out until now.
Looks like this is because of a change in Gatekeeper settings in macOS Catalina - it does not allow opening apps that are from unidentified developers like us.
The below link provides a workaround that helps going around this limitation in Gatekeeper - please consider using it and see if that helps:
https://apple.stackexchange.com/questions/372084/macos-catalina-app-is-damaged-and-cant-be-opened-you-should-move-it-to-the-t/372208#372208

@MacTerrassa - sorry, I was not able to test this out until now.
Looks like this is because of a change in Gatekeeper settings in macOS Catalina - it does not allow opening apps that are from unidentified developers like us.
The below link provides a workaround that helps going around this limitation in Gatekeeper - please consider using it and see if that helps:
https://apple.stackexchange.com/questions/372084/macos-catalina-app-is-damaged-and-cant-be-opened-you-should-move-it-to-the-t/372208#372208

Maybe I did not explain myself well: I am using El Capitan 10.11 and this is where I cannot open any version from the <IP_ADDRESS> to <IP_ADDRESS>. The last one that I can install and have installed is <IP_ADDRESS>
Anyway, I have tried the xattr command as indicated, and it gives me the same result: double click on the app within the disk image, it jumps to the dock, but closes immediately.
And the message has been closed unexpectedly, the report will be sent to Apple with the content of the initial message.
I understood that also, the application quarantine had no effect if you dragged it to the downloads folder or an external disk. It doesn't work for me either.

Maybe I did not explain myself well: I am using El Capitan 10.11 and this is where I cannot open any version from the <IP_ADDRESS> to <IP_ADDRESS>. The last one that I can install and have installed is <IP_ADDRESS>
Anyway, I have tried the xattr command as indicated, and it gives me the same result: double click on the app within the disk image, it jumps to the dock, but closes immediately.
And the message has been closed unexpectedly, the report will be sent to Apple with the content of the initial message.
I understood that also, the application quarantine had no effect if you dragged it to the downloads folder or an external disk. It doesn't work for me either.

In addition, precisely on another Mac that does have Catalina, I have not had any problem installing any of the versions that I have tried there. As I am not ahead, I do not know until which version I got there, but I think it is updated to the latest without any problem. I will check it again.

In addition, precisely on another Mac that does have Catalina, I have not had any problem installing any of the versions that I have tried there. As I am not ahead, I do not know until which version I got there, but I think it is updated to the latest without any problem. I will check it again.

The below link provides a workaround that helps going around this limitation in Gatekeeper - please consider using it and see if that helps:
https://apple.stackexchange.com/questions/372084/macos-catalina-app-is-damaged-and-cant-be-opened-you-should-move-it-to-the-t/372208#372208

I'm using 10.15 and this was super helpful to get the download running thanks.

Thanks for the link, but I repeat my words again:
In my new iMac with Catalina, I already installed the program correctly, without any problem to open the installer or the final program. What's more, now I see a new update, which I will try again tomorrow to install on Catalina.
My problem is with another previous iMac, which continues to work with El Capitan (mac os X 10.11) and which is the one that does not allow me to open the installer.
Neither by dragging the installer to the downloads folder, which is a trick for new systems and avoiding its controls (but in theory, not in El Capitan), nor to an external hard drive. In no case am I allowed to open it.
Neither by pressing control + open, nor by using the command mentioned in the link to change the quarantine attributes. Not doing it with xattred from Eclecticlight Software. Nor with some others that I found interesting to try. I have not managed to install it on El Capitan yet. Except for the old version that I mention above, and that can be motivated by some internal change that prevents it on the new versions.
Which? No idea. But it seems to me that if the problem was just quarantine or permissions, I wouldn't be able to install older versions either, as if I can install up to one version <IP_ADDRESS>

I just installed perfectly on my mac with 10.11.6 the latest version 3.4.01 from Flickr Downloadr. It seems they have finally fixed the problem.
I had not tried any of the intermediate versions I do not know if it has been in the last or any of these.
Thanks for fixing it.
Regards
MacTerrassa


Methods getName() and getDescription() in class ObjectDescriptor should be public

These methods are now package accessible instead of public accessible.

This issue should have been included in the djutils-base project, but has been solved.


Fix local anomaly when using normalize_repeats

@unmonoqueteclea, this changes should be used by our current running projects using anomalies. They should only affect corner cases, but still they might help.

corrected, let's wait for tests to pass


Show password not working on create account

When I check the box to "Show password" on the create account page, nothing happens (pw still obscured - screenshot). This is only happening on this page.

working as expected. closing.

Reopening for verification after git cherry-pick

working as expected. closing again.


Update to v0.14.0-rc3

Backlinking to purescript/purescript#3942

Superceded by #16. Sorry @paluh, I didn't realize this PR was already open.


test(x/twap): final manual geometric twap CLI test on v14.x branch

Acceptance Criteria

make sure works
make sure base / quote is right
try to do a large swap and see that the result changes

Testing strategy (WIP):

Create pool on fresh localosmosis built off of v14.x at this commit

osmosisd tx gamm create-pool --pool-file tests/e2e/scripts/geometricPool.json --from lo-test1 --keyring-backend test -b=block --chain-id=localosmosis

Supply: 1000000uosmo,2000000stake
Weights equal

Check that geometric twap is correct and matches arithmetic

base asset = uosmo, 2000000 / 1000000 = 2

Geometric
osmosisd q twap geometric 1 uosmo<PHONE_NUMBER> 1s

Arithmetic
osmosisd q twap arithmetic 1 uosmo<PHONE_NUMBER> 1s
arithmetic_twap: "2.000000000000000000"

base asset = stake,  1000000 / 2000000 = 0.5

Geometric
osmosisd q twap geometric 1 stake<PHONE_NUMBER> 1s
geometric_twap: "0.500000000000000000"

Arithmetic
osmosisd q twap arithmetic 1 stake<PHONE_NUMBER> 1s
arithmetic_twap: "0.500000000000000000"

Manual tests LGTM, please see testing strategy above ^


Wiki TOC links do not scroll page

Steps to reproduce

Create a wiki page that is longer than the container on the page.
Add a header near the bottom of the wiki page.
Add a TOC to the top
Save the wiki page
Click the TOC link to the bottom header

Expected
The wiki page should scroll to the appropriate section
Actual
Wiki page does not scroll, the containing web page jumps to the bottom.

Fixed by #2047

'K -- thanks -- noted as 'Pending Review'

Just an update that the fix is now in this PR: #2200


The statement needs a return

Thanks for the PR @williamle8300 . Good catch.
If you haven't done so yet, would you mind signing our CLA at http://rethinkdb.com/community/cla/ ?
Looking at the code we should also maybe use r.expr([...]) instead of r([...]) for consistency with other examples. @chipotle what do you think?

No I'm not gonna sign the CLA to make rethinkdb better. You don't have to merge my request under my handle. Feel free to make the change under @danielmewes.

Ok, I'll leave it to @chipotle to make the appropriate corrections to our docs.


v0.1 release

Initial release set as pull request for ease of code review tools

For initial release, I should add a few more built-in estimating equations. Below are the ones I want to add (and will require corresponding tests)

[ ] Ratio estimator
[ ] Instrumental variable (4 part version?)
[ ] Positive mean deviation
[ ] Robust linear regression
[ ] GLM
[ ] GEE

Adding 4PL, 3PL, and 2PL dose-response estimating equations. Further adding a 4PL EC estimating equation. It is just a transformation, so it generalized to each of the dose-response estimating equations. In the commits before this comment, but still needs to be tested

Need to add a few further items to this release:

[ ] Add weight optional argument for the built-in mean estimating equations
[ ] Add weight optional argument for robust regression
[ ] Add function to MEstimator to compute the CI for the user (easy to parse the theta and variance)


Remove Docker Compose make targets

We were only making a single reference to the services-start target in the README.md — and it was to test the Docker image.
Now we explictely tell developers to use docker-compose up application if they want to use Docker Compose to test the image they just built 😄

🦀 Requesting reviewers for this pull request:

@loboulet (contributor with 0 commits in the last 90 days and 22 commits overall)


Add ability to download report

Use Case
As the the report information created when uploading a puppetfile or viewing your downloads is tied to an individuals account, Its hard to keep track of the work undertaken to update modules if more than one person is working on it.
Describe the Solution You Would Like
To enable sharing with others, its would be useful to be able to download the report information created when uploading a puppetfile or viewing your downloads. A csv would be useful as this would help people track the updates they are performing over time, especially if a team of people are working on it
Describe Alternatives You've Considered
Taking a screen grab, or trying to copy the text on the page is troublesome and not useful
Additional Context
None

I second this request. It would be incredibly useful for our organization as well.

Hi @derek-robinson while I acknowledge and understand this request, I would like to understand the objective behind it. If the idea is to share the current state with team mates, we just released organizations on Forge, which basically allows admins to create groups on Forge and all the members will see the same view of the module estate.
This request is valid and will be looked at, but just sharing additional context as it might help you in making use of the feature we just launched

I need to export the list in a way that I can sort it and extract the ones I need for different use cases.
For example, if I need to make jira tickets for assigning the tasks out of updating to newer versions or making one for investigating deprecated modules.

I need to export the list in a way that I can sort it and extract the ones I need for different use cases.
For example, if I need to make jira tickets for assigning the tasks out of updating to newer versions or making one for investigating deprecated modules.


Amplify Push: Parameters must have values for environment variables

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
20.1.0
Amplify CLI Version
12.8.2
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
We created a new lambda function on an existing project using the same steps found here.
However, with one difference.  When we configured advanced settings we also included environment variables.
The issue is that after the function was created and pushed by another developer on our team, I can pull the new function using amplify pull, but when I try to push any other change using amplify push, it throws the following error:
🛑 The following resources failed to deploy:
Resource Name: customFunction (AWS::CloudFormation::Stack)
Event Type: update
Reason: Parameters: [envVarOne, envVarTwo, envVarThree] must have values
URL: ...

The developer who originally pushed the function has no issues pulling or pushing.  Only I do.
The following issues look very similar to these other threads I've seen, but the main difference I see is that the environment variables are causing the issue.
https://github.com/aws-amplify/amplify-cli/issues/9484
https://github.com/aws-amplify/amplify-cli/issues/11211#issuecomment-1284121725
Expected behavior
Create new lambda functions with environment variables, pull in those changes, and be able to push additional changes up.
Reproduction steps

Person 1: The same steps from here: https://docs.amplify.aws/javascript/build-a-backend/graphqlapi/connect-from-server-runtime/#utilizing-lambda-function-template-iam-authorization, but also include environment variables.
Person 1: Amplify push function
Person 2: Amplify pull
Person 2: (update something else within project, like api)
Person 2: Amplify push api
(Error)

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

The issue seems to have a similar behaviour as https://github.com/aws-amplify/amplify-cli/issues/13327.

Hey @neuquen, tried reproducing the issue with the steps provided, but was not able to reproduce the issue.

amplify init
amplify add api
amplify add function, selected the template and in advance setting added 2 environment variables
amplify push
pulled the backend into a new empty directory
modified the the api model
amplify push api
but did not observe any error.

Could check the issue linked in the previous comment and let us know the reproduction steps are similar in your environment.

@neuquen thank you for following up. Adding the pending-response tag.

We were able to replicate the issue again.  I'm including more verbose output from the interactive prompts, but it honestly seems to be the same steps as before.  This time around I included secrets as well as env variables.
One difference is that my colleague and I switched roles.  This time I added the new function (Person 1) and he tried to make the update and push (Person 2).
PERSON 1

amplify add function

? Select which capability you want to add: Lambda function (serverless function)
? Provide an AWS Lambda function name: TestEnvVariables
? Choose the runtime that you want to use: NodeJS
? Choose the function template that you want to use: AppSync - GraphQL API request (with IAM)

✅ Available advanced settings:
- Resource access permissions
- Scheduled recurring invocation
- Lambda layers configuration
- Environment variables configuration
- Secret values configuration

? Do you want to configure advanced settings? Yes
? Do you want to access other resources in this project from your Lambda function? Yes
? Select the categories you want this function to have access to. api
? Api has 3 resources in this project. Select the one you would like your Lambda to access <app-name>
? Select the operations you want to permit on <app-name> Query, Mutation, Subscription

You can access the following resource attributes as environment variables from your Lambda function
        API_<app-name>_GRAPHQLAPIENDPOINTOUTPUT
        API_<app-name>_GRAPHQLAPIIDOUTPUT
        ENV
        REGION
? Do you want to invoke this function on a recurring schedule? No
? Do you want to enable Lambda layers for this function? No
? Do you want to configure environment variables for this function? Yes
? Enter the environment variable name: firstVar
? Enter the environment variable value: firstValue
? Select what you want to do with environment variables: Add new environment variable
? Enter the environment variable name: secondVar
? Enter the environment variable value: secondValue
? Select what you want to do with environment variables: Add new environment variable
? Enter the environment variable name: thirdVar
? Enter the environment variable value: thirdValue
? Select what you want to do with environment variables: I'm done

You can access the following resource attributes as environment variables from your Lambda function
        ENV
        REGION
        API_<app-name>_GRAPHQLAPIIDOUTPUT
        API_<app-name>_GRAPHQLAPIENDPOINTOUTPUT
        firstVar
        secondVar
        thirdVar
? Do you want to configure secret values this function can access? Yes
? Enter a secret name (this is the key used to look up the secret value): firstSecret
? Enter the value for firstSecret: [hidden]
? What do you want to do? Add a secret
? Enter a secret name (this is the key used to look up the secret value): secondSecret
? Enter the value for secondSecret: [hidden]
? What do you want to do? I'm done
✔ Choose the package manager that you want to use: · NPM
Use the AWS SSM GetParameter API to retrieve secrets in your Lambda function.
More information can be found here: https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_GetParameter.html
? Do you want to edit the local lambda function now? No
✅ Successfully added resource TestEnvVariables locally.

amplify push function TestEnvVariables
NOTE: I have a couple pre-push hooks that run npm install on the overall project due to project-level overrides and lambda functions with npm dependencies.

----- 🪝 pre-push execution start -----
Running npm install...

added 334 packages, and audited 369 packages in 19s

26 packages are looking for funding
  run `npm fund` for details

8 moderate severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
----- 🪝 pre-push execution end -----

----- 🪝 pre-push-function execution start -----
Running npm install...
----- 🪝 pre-push-function execution end -----

    Current Environment: dev

┌──────────┬──────────────────┬───────────┬───────────────────┐
│ Category │ Resource name    │ Operation │ Provider plugin   │
├──────────┼──────────────────┼───────────┼───────────────────┤
│ Function │ TestEnvVariables │ Create    │ awscloudformation │
└──────────┴──────────────────┴───────────┴───────────────────┘
✔ Are you sure you want to continue? (Y/n) · yes

Deployment completed.

PERSON 2

amplify pull
(Updated a different, existing lambda function)
amplify push function differentLambdaFunction

🛑 The following resources failed to deploy:
Resource Name: functionTestEnvVariables (AWS::CloudFormation::Stack)
Event Type: update
Reason: Parameters: [thirdVar, secondVar, firstVar] must have values
URL: ...

Also, regarding https://github.com/aws-amplify/amplify-cli/issues/13327.  Unfortunately, I already removed the test function, so I no longer can view function-parameters.json, but I still have the output from a git diff for the other two files.
If this isn't helpful without also seeing the function parameters files, then we can try it again (but not until January).
team-provider-info.json:
+    },
+    "TestEnvVariables": {
+      "build": true,
+      "dependsOn": [
+        {
+          "attributes": [
+            "GraphQLAPIIdOutput",
+            "GraphQLAPIEndpointOutput"
+          ],
+          "category": "api",
+          "resourceName": "<app-name>"
+        }
+      ],
+      "providerPlugin": "awscloudformation",
+      "service": "Lambda"
+    },

...

+    "AMPLIFY_function_TestEnvVariables_firstVar": {
+      "usedBy": [
+        {
+          "category": "function",
+          "resourceName": "TestEnvVariables"
+        }
+      ]
+    },
+    "AMPLIFY_function_TestEnvVariables_s3Key": {
+      "usedBy": [
+        {
+          "category": "function",
+          "resourceName": "TestEnvVariables"
+        }
+      ]
+    },
+    "AMPLIFY_function_TestEnvVariables_secondVar": {
+      "usedBy": [
+        {
+          "category": "function",
+          "resourceName": "TestEnvVariables"
+        }
+      ]
+    },
+    "AMPLIFY_function_TestEnvVariables_secretsPathAmplifyAppId": {
+      "usedBy": [
+        {
+          "category": "function",
+          "resourceName": "TestEnvVariables"
+        }
+      ]
+    },
+    "AMPLIFY_function_TestEnvVariables_thirdVar": {
+      "usedBy": [
+        {
+          "category": "function",
+          "resourceName": "TestEnvVariables"
+        }
+      ]
+    },

backend-config.json:
"TestEnvVariables": {
+          "firstVar": "firstValue",
+          "secondVar": "secondValue",
+          "thirdVar": "thirdValue",
+          "secretsPathAmplifyAppId": "<app-id>",
+          "deploymentBucketName": "amplify-<app-name>-dev-155924-deployment",
+          "s3Key": "amplify-builds/TestEnvVariables-6b6a6443446a516c6568-build.zip"
         }

Hey @neuquen, thank you for the information. Does the person 2 pull the application from git repository with the team-provider-info.json?
The function env variables are maintained in the team-provider-info.json, when sharing the project do ensure the team member does also have access to team-provider-info.json via the version control system.

@ykethan, yes, we use version control and we include team-provider-info.json in our repo.  Can you give me an example of how the variables should be formatted in that file so that I can see if they show up properly in our project?

@neuquen the format does appear to be correct in team-provider-info.json, do let us know if this mitigates the issue
"function": {
        "tes2343f4": {
          "test": "test",
          "deploymentBucketName": "",
          "s3Key": ""
        }
      }

@ykethan, thanks for all the help.  The missing environment variables in team-provider-info.json ended up being the issue this whole time.
But that brings up one last question for me.  Why are environment variables generated locally for the person who created/updated the lambda function, but not updated when pulled by someone else?  The other values are pulled in (deploymentBucketName, s3key, secretsPathAmplifyAppId).  Why wouldn't the env variable names and values also be pulled in?

@neuquen Glad to hear you were able to mitigate the issue. To clarify the behavior, Amplify CLI currently does not zip team-provider-info.json  to the current-cloud-backend present on the S3 bucket. https://docs.amplify.aws/react/tools/cli/teams/shared/#sharing-projects-within-the-team
On a pull the variables such deploymentBucketName, s3key, secretsPathAmplifyAppId are rehydrated from the amplify-meta.json file from the current-cloud-backend which contain the references to the resources.


Add closure tree operations in 2.4.x

verify() and recover()

thanks ;)

It would be great to add a new tag


Queuing Code

Looking for queuing code to understand how that's working, or if its entirely up on AWS. Are there artifacts and instructions from AWS we can add here?

Queuing code is now pushed. It resides within the handleQueue directory (this used to be the insightNotifications directory, but that code has moved to the sendNotifications directory, along with some adjustments)


Add ability to filter displayed repos

Some GDS repos are linked to a large number of teams,
and thus show up on all those teams' fourth walls e.g.
gds-tech-learning-pathway. This commit adds functionality
to enable filtering of displayed repos using a comma separated
query param, to allow teams to only see repos they are
actively concerned with.
Usage:
https://alphagov.github.io/fourth-wall/?token=my-big-token&team=alphagov/my-big-team&fiteredrepos=my-undesired-repo-1,my-undesired-repo-2
I would have written some tests, but have neither time nor guile
enough to figure out how to run them. There's no guidance on this,
and no package.json to manage test dependencies. So trust me, this works.
Alternatively, check it locally before approving.

There are tests which can be run from testrunner.sh. But it looks like the tests only work on PhantomJS versions <2.0.0, which can’t be installed on OS X Yosemite or newer. So getting them working would need someone to setup Docker or a VM for this repo.
These changes look reasonable though, and solve a real problem. 👍 from me, but I don’t have merge rights for this repo.

Although, couple things:

adding to the documentation would be good
the parameter should be called filterRepo[] to match team[]: Given multiple times allows for more than one team…

@quis Thanks, yep have updated docs and changed query var format to match team


Lazy loading on safari

The docs mention that lazy hydration is implemented with requestIdleCallback but no version of safari supports this: https://caniuse.com/?search=requestIdleCallback
Does the framework adjust its behavior when running on safari or should we avoid using this option if we want to target iOS/Mac?

Interested to hear about this as well.

I think they use a simple polyfill for that, by looking at the code:
const requestIdleCallback = window.requestIdleCallback || ( cb => window.setTimeout(cb,1) );


PSProvideDefaultParameterValue is wrong.

This rule should not exist at all
Function parameters are always automatically defined in the local scope and initialized by PowerShell to $null -- even when they are part of an unused parameter set.
There is absolutely ZERO value, and nothing to be gained in setting them yourself -- unless you actually need them to default to something other than $null.

Signed.

Agree. Will change to rule to warn users if they provide a default value for a Mandatory parameter.

Be sure to check all parameter sets that parameter belongs to when creating
this rule.  Some parameters are mandatory in some parameter sets yet remain
optional in others.  In that scenario, it shouldn't warn if a default value
is provided.
The rule should only warn users when a parameter that is mandatory in every
parameter set where it is included is assigned a default value.
--
*Kirk Munro *
Poshoholic, Microsoft MVP
Blog http://poshoholic.com/ | Twitter http://twitter.com/poshoholic |
LinkedIn http://ca.linkedin.com/in/kirkmunro | GitHub
http://github.com/KirkMunro | Facebook
http://www.facebook.com/#!/kirk.munro
Need a PowerShell SME for a project at work? Contact me
http://poshoholic.com/contact-me/!
On Wed, Nov 18, 2015 at 3:53 PM, Raghu Shantha [MSFT] <
<EMAIL_ADDRESS>wrote:

Agree. Will change to rule to warn users if they provide a default value
for a Mandatory parameter.
—
Reply to this email directly or view it on GitHub
https://github.com/PowerShell/PSScriptAnalyzer/issues/362#issuecomment-157843257
.

Hang on, you're confusing me with #360
My point is that PSProvideDefaultParameterValue is always wrong.
It's not just wrong when the parameter is mandatory.

Raghu said they would change this rule such that it only warns when default parameter values are assigned to mandatory parameters.  I read that as saying that is all this rule would do, and suggested they only do that for parameters that are mandatory in every parameter set in which they are used.  Nothing else.  No default value checking for optional parameters.  Is that not what you meant Raghu?

Correct. Here is the PR with the change:
https://github.com/PowerShell/PSScriptAnalyzer/pull/382


Coordinator url changed to viridan. [API-1765]

Coordinator url changed to api.viridian.hazelcast.com

Linux test PASSed.


[1.16.5] Some Keys Resetting on Restart

Same issue as everyone else. I love this mod but I can't include it in my pack if it's not working properly.

same

Duplicate of https://github.com/GirafiStudios/MineMenu/issues/104


instance norm and reflection padding

Re-create the PR for instance norm and reflection padding.

Could you fix lint? The errors can be obtained by running make pylint

Please add tests.

@szha The original author seems to have disappeared. Would you like to take over?

Actually @zhanghang1989 will join us soon 😄

@piiswrong @szha Hi guys, sorry for the delay. I just made some changes.

@zhanghang1989 @szha
The instance norm operator needs an axis argument to be consistent with batchnorm
reflectionpad2d's input/output shape doc has wrong format


Morning Session Code Review

Highlights 🥇

Good job implementing the Figma design 👏
Clean code base 👍
Good job implementing interactions in your page i.e hover on the buttons and on the cards 💯

Suggestions

Consider deleting one of  your style.css files as it may seem confusing for someone who is reviewing your code

No linter errors found good work flow

Nice implementation of Figma design


"First this user must have [a] certificate issued..."

Added 'a' to the sentence "First this user must have certificate issued..." from the subsection "Normal Users"

/check-cla

/check-cla

/approve


AH00526: Syntax error on line 93 of /etc/apache2/modsec/owasp-modsecurity-crs/rules/REQUEST-903.9004-DOKUWIKI-EXCLUSION-RULES.conf: Error parsing actions: Unknown action: \ Action 'configtest' failed. The Apache error log may have more information.

Hello,
I'm using kali 2023.I am conducting an experiment on configuring the OWASP rule set in ModSecurity to prevent injection attacks, but I have encountered a problem
I downloaded libapache2-mod-security2，Rename modsecurity.conf-recommended to modsecurity.conf。
I renamed "crs-setup.conf.example" file to "crs-setup.conf". In the "rules" directory, I renamed below files too:
# mv REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf.example REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf
# mv RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf.example RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf

In apache2 configuration file/etc/apache2 / apache2. Add the code the conf：
<IfModule security2_module>
    Include modsec/owasp-modsecurity-crs/crs-setup.conf
    Include modsec/owasp-modsecurity-crs/rules/*.conf
</IfModule>

The crs-setup.conf file is also edited:
# sed -ie 's/SecDefaultAction "phase:1,log,auditlog,pass"/#SecDefaultAction "phase:1,log,auditlog,pass"/g' crs-setup.conf
# sed -ie 's/SecDefaultAction "phase:2,log,auditlog,pass"/#SecDefaultAction "phase:2,log,auditlog,pass"/g' crs-setup.conf
# sed -ie 's/#.*SecDefaultAction "phase:1,log,auditlog,deny,status:403"/SecDefaultAction "phase:1,log,auditlog,deny,status:403"/g' crs-setup.conf
# sed -ie 's/# SecDefaultAction "phase:2,log,auditlog,deny,status:403"/SecDefaultAction "phase:2,log,auditlog,deny,status:403"/g' crs-setup.conf

I also add a main.conf configuration file under /etc/apache2/modsec:
# Include the recommended configuration
include etc/modsecurity/modsecurity.conf
include owasp-modsecurity-crs/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf
include owasp-modsecurity-crs/rules/REQUEST-942-APPLICATION-ATTACK-SQLI.conf
include owasp-modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf
# A  rule
SecRule ARGS:testparam "@contains test" "id:1234,deny,log,status:403"

However, I still received an error in the service apache2 restart command:
oot@2cca78e9f6e3:/etc/apache2/modsec/owasp-modsecurity-crs/rules# service apache2 restart * Restarting web server apache2                                                                [fail]
 * The apache2 configtest failed.
Output of config test was:
AH00526: Syntax error on line 93 of /etc/apache2/modsec/owasp-modsecurity-crs/rules/REQUEST-903.9004-DOKUWIKI-EXCLUSION-RULES.conf:
Error parsing actions: Unknown action: \\
Action 'configtest' failed.
The Apache error log may have more information.

and this is the line 93 code :

I lack experience, please tell me what I should do?
thank you...

Or can you provide me with a classic tutorial on how to install ModSecurity on Kali Linux and configure it using the OWASP rule set?

Hi @jinji-lab,
thanks for reporting.
I have to tell you this is a very weird behavior.
First of all, please clarify what CRS version you use exactly. On the screenshot above I see the version OWASP_CRS/3.2.0, but as I see CRS 3.2 does not have ver action - see the mentioned rule.
Then I don't see why did you include same rule files twice. First when you set this line:
Include modsec/owasp-modsecurity-crs/rules/*.conf

and then when you include these:
include owasp-modsecurity-crs/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf
include owasp-modsecurity-crs/rules/REQUEST-942-APPLICATION-ATTACK-SQLI.conf
include owasp-modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf

Just a note: I think the best to load the modsecurity.conf first, and later the others.
 If that was the aim, then it's okay, I just want to notice you.
So because I don't have any idea what's going on here, could you make that rule as a comment (put a # to beginning of each lines of rule), and see what happens?

Or can you provide me with a classic tutorial on how to install ModSecurity on Kali Linux and configure it using the OWASP rule set?

Not a Kali Linux specified, but please see Coreruleset's documentation. This made for a newer version, but I hope you can find what you want.

Hey@airween,
Thank you for answering my questions.
I've figured out the steps and discovered while browsing blogs that the issue might have been caused by an incompatible version of Apache.
I eventually resolved the error and completed my experiment.
I apologize for the late reply and thank you again.

Hey @airween
Thank you for your patient response.
I've figured out the steps and discovered while browsing blogs that the issue might have been caused by an incompatible version of Apache.
I eventually resolved the error and completed my experiment.
I apologize for the late reply ,and thank you again.

Hi @jinji-lab,
thank you for letting me know this. Feel free to close this issue if you have no questions.


Update migration-api-whats-new.md

Category

[X] Content fix/update

What's in this Pull Request?
update regarding encoding invalid XML characters.

@andrewconnell  This is new feature that has already released; high priority.


Updated to version 4.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This is my fist contribution to a feedstock, I hope everthing is correct.

@conda-forge-admin, please rerender

Thanks a lot for this and sorry for missing it originally! 👍


DB query 6

GIVEN a command-line application that accepts user input
WHEN I choose to add an employee
THEN I am prompted to enter the employee’s first name, last name, role, and manager, and that employee is added to the database

completed


Parameters unnamed for PHDAUDIO_DMA_NOTIFICATION_CALLBACK

Parameters for PHDAUDIO_DMA_NOTIFICATION_CALLBACK are unnamed. It's safe to assume the first one is the context, but the second parameter is unclear what it's supposed to be.

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

ID: fe7b3c6c-c7ae-f9dc-ddaa-570cc1e88e66
Version Independent ID: 5fd0ee33-36b7-ce9a-55aa-b8db49ba6c22
Content: PHDAUDIO_DMA_NOTIFICATION_CALLBACK - Windows drivers
Content Source: wdk-ddi-src/content/hdaudio/nc-hdaudio-phdaudio-dma_notification_callback.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @DOMARS
Microsoft Alias: domars

@coolstar - Thanks for this issue. I believe we are having an issue with the publishing system not rendering the callback signature, and then as the field names don't match, not rendering the existing field descriptions that are in the topic.
As a work around, you can view the reference content in raw view. For this topic, for example:
https://raw.githubusercontent.com/MicrosoftDocs/windows-driver-docs-ddi/staging/wdk-ddi-src/content/hdaudio/nc-hdaudio-phdaudio-dma_notification_callback.md
That content shows the two (named) parameters.
-param Context:
Driver-specific context value used when registering the callback routine.
-param QPCDMANotificationTimestamp:
The QPC time when the IOC ISR handled the DMA interrupt.
I hope that we are able to restore the field level rendering as soon as possible, to avoid the use of the work around described above.


Add Beauchamp et al. paper and slides  (Ensemble-based 4DVarNet) from April 19

Yes sorry for that I made the update