Update Stakeflow.toml

Previous PR:
#2505 #1426 #763
Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

Successfully validated transactions.toml file for commit hash 570aa6c

Yeah this tries to add more than one toml. Try again

I've created a new one
https://github.com/anoma/namada-testnets/pull/3138


[feature]Fix issue #4985 and add createError method

Changes

Add exception handling function createError
This hooks.suppressCreateError is used to specify whether it is forbidden to throw exception information, the default value is true
Fix for issue #4985

Coverage decreased (-0.02%) to 88.502% when pulling e57bff0c0efe83425cf0a5a20928b76bf5838bfd on Alanscut:issue_4985 into 528ac2b6c4df4438c83d57fb73f06e3666ce2767 on moment:develop.

Merged in c8785e7d6acc94464b3d54c866b3f5a08d3df74e

Reverted in 0f0195f5049744d4b74bd0840501cb24b2cba949.
I looked carefully at all the places the new createError calls, and most of them didn't make any sense. I'm guessing the function that returns an invalid moment should be wrapped in this method. Then it can be made to either print, or throw, or do nothing (the default).


Create role nftables

Needs to do the following:

[x] Install nftables
[ ] Configure nftables.conf based on servers hosted
[ ] Configure fail2ban to use nftables

References:

https://wiki.nftables.org/wiki-nftables/index.php/Main_Page
https://home.regit.org/netfilter-en/nftables-quick-howto/
https://wiki.archlinux.org/index.php/nftables
https://people.netfilter.org/pablo/nft-tutorial.pdf
https://wiki.debian.org/nftables

Required nftables configuration for Fail2ban.
https://wiki.meurisse.org/wiki/Fail2Ban

Does nftables work with a nftables.d/* include?  I think so, don't remember, this is a note for later.


New changes on main branch necessitate MPI usage

Hi all,
I recently merged the main branch into the permanent_magnets branch (on July 1) and unfortunately this has broken some things. It appears that the new changes make it necessary to use MPI on any of the example scripts and my permanent magnet optimization scripts now (1) requires "srun python ..." instead of just "python ..." to properly function and (2) runs out of memory on a single Cori Haswell node when using the srun version. And because I am using the srun command the error is vague about where the out-of-memory occurs. Any suggestions for how to proceed? Can I adapt the MPI logging stuff to figure out why I am running out of memory?
Best,
Alan

The tests are not breaking on the CI. However the top level imports might have messed up something.  Are you using compiling your code on Cori?

Is it possible that the out-of-memory error comes from srun launching 32
copies of your script? Srun launches as many copies as the number of MPI
process specified in the job script, so I believe you should specify just 1
MPI rank per node.
On Sun, Jul 3, 2022, 2:22 PM Alan Kaptanoglu @.***>
wrote:

Hi all,
I recently merged the main branch into the permanent_magnets branch (on
July 1) and unfortunately this has broken some things. It appears that the
new changes make it necessary to use MPI on any of the example scripts and
my permanent magnet optimization scripts now (1) requires "srun python ..."
instead of just "python ..." to properly function and (2) runs out of
memory on a single Cori Haswell node when using the srun version. And
because I am using the srun command the error is vague about where the
out-of-memory occurs. Any suggestions for how to proceed? Can I adapt the
MPI logging stuff to figure out why I am running out of memory?
Best,
Alan
—
Reply to this email directly, view it on GitHub
https://github.com/hiddenSymmetries/simsopt/issues/242, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH4ZA2HQO2LSFPWH2ZEF3TVSHK53ANCNFSM52RCB7GA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks Matt, looks like this is it. What is confusing is that "srun python ..." runs fine on an interactive node but on a compute node I need "srun -n 1 python ...", and hopefully this means it is still utilizing the ntasks-per-node=68 in the openmpi parts of the code...


added python version

I was using python3 and was surprised when code broke. I thought others might have made the same mistake.

Thanks for adding this!


teste de imahgem

(https://github.com/user-attachments/assets/c6adc9cb-163b-49d8-b110-eb12f750faa1


Action failed with error: Service tier not recognizable in service

Using the sample from the readme with following action
        name: deploy to production with artifact
        uses: Azure/spring-apps-deploy@v1
        with:
          azure-subscription: ${{ env.AZURE_SUBSCRIPTION }}
          action: Deploy
          service-name: ${{ env.SERVICE_NAME }}
          app-name: ${{ env.APP_NAME }}
          use-staging-deployment: false
          package: ${{ env.ASC_PACKAGE_PATH }}/**/*.jar

Getting this error: Error: Action failed with error: Service tier not recognizable in service appname app serviceName.
Using Azure spring apps on Standard consumption & dedicated (preview)

Hi Brij. I think you use the consumption tier right? I am sorry that we don't support this preview tier in GitHub Action right now.
Would you mind try standard/basic tier? Thanks for your question!

Thank you for your response. The action worked with basic tier.
Meanwhile I'll use https://github.com/marketplace/actions/azure-cli-action as a workaround.

can we have the gist of your updated workflow file using the cli action, @brijshah27 ?

@exaucae I am using this
name: Azure CLI Action to deploy to dev with main branch
        uses<EMAIL_ADDRESS>        with:
          inlineScript: |
            az spring app deploy \
            --resource-group <rg-name>\
            --service <service-name>\
            --name <instance-name> \
            --artifact-path ${{ env.ASC_PACKAGE_PATH }}/backend/**/*.jar \
            --runtime-version Java_17 \
            --jvm-options='-Dspring.profiles.active=dev'

thanks, @brijshah27

Any idea when consumption tier will be supported ?


the error make my program crashed.

error: Fatal Windows exception, code 0xc0000005.
PhantomJS has crashed. Please read the bug reporting guide at
<http://phantomjs.org/bug-reporting.html> and file a bug report.

crash and i cannot catch error in catch or process.on('exit', ()=>
why???

This is not related to this project. It's probably a phantomjs error.

but why the catch code disabled?
try{
}catch(e

or
process.on('exit'  ,

the problems can cause programs to crash.

const page = await instance.createPage().catch(e => e);

is babel-flow compile leads to error?

await instance.createPage().catch(e => e); isn't right. You need to use try-catch. Sorry I can't help more. I am very busy with other stuff.


OCPBUGS 25307: Replace child /var/lib volume mounts with parent /var/lib mount

The child volume mounts for /var/lib are replaced with the parent /var/lib mount in order to increase support over older and newer OCP releases (note that OVN-IC was enabled with 4.14).
The commit was manually tested against the QE test bed (helix61). Below are sample output for validation.
Backup-agent job
sakhoury-mac:~ sakhoury$ oc -n openshift-talo-backup get jobs
NAME           COMPLETIONS   DURATION   AGE
test-agent     1/1           14s        66s

sakhoury-mac:~ sakhoury$
sakhoury-mac:~ sakhoury$ oc -n openshift-talo-backup describe job test-agent
Name:                     test-agent
Namespace:                openshift-talo-backup
Selector:                 controller-uid=18c605fd-5b83-4434-8eb8-3fccd667a690
Labels:                   job-name=test-agent
Annotations:              batch.kubernetes.io/job-tracking:
Parallelism:              1
Completions:              1
Completion Mode:          NonIndexed
Start Time:               Thu, 14 Dec 2023 11:48:31 -0500
Completed At:             Thu, 14 Dec 2023 11:48:45 -0500
Duration:                 14s
Active Deadline Seconds:  480s
Pods Statuses:            0 Active (0 Ready) / 1 Succeeded / 0 Failed
Pod Template:
  Labels:           controller-uid=18c605fd-5b83-4434-8eb8-3fccd667a690
                    job-name=test-agent
  Annotations:      target.workload.openshift.io/management: {"effect":"PreferredDuringScheduling"}
  Service Account:  backup-agent
  Containers:
   container-image:
    Image:      quay.io/sakhoury/cluster-group-upgrades-operator-recovery:4.15.0
    Port:       <none>
    Host Port:  <none>
    Args:
      launchBackup
    Environment:  <none>
    Mounts:
      /host from host (rw)
      /host/boot from host-boot (ro)
      /host/dev/log from host-dev-log (rw)
      /host/etc from host-etc (rw)
      /host/proc from host-proc (ro)
      /host/run from host-run (rw)
      /host/sys/fs/cgroup from sys-fs-cgroup (ro)
      /host/sysroot from host-sysroot (rw)
      /host/tmp from host-tmp (rw)
      /host/usr/bin from host-usr-bin (ro)
      /host/usr/lib from host-usr-lib (ro)
      /host/usr/lib64 from host-usr-lib64 (ro)
      /host/usr/libexec from host-usr-libexec (ro)
      /host/usr/local from host-usr-local (ro)
      /host/usr/share/containers from host-usr-share-containers (ro)
      /host/var/lib from host-var-lib (rw)
      /host/var/recovery from host-var-recovery (rw)
      /host/var/tmp from host-var-tmp (rw)
  Volumes:
   host:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
   host-boot:
    Type:          HostPath (bare host directory volume)
    Path:          /boot
    HostPathType:  Directory
   host-dev-log:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/log
    HostPathType:  Socket
   host-etc:
    Type:          HostPath (bare host directory volume)
    Path:          /etc
    HostPathType:  Directory
   host-proc:
    Type:          HostPath (bare host directory volume)
    Path:          /proc
    HostPathType:  Directory
   host-run:
    Type:          HostPath (bare host directory volume)
    Path:          /run
    HostPathType:  Directory
   host-sysroot:
    Type:          HostPath (bare host directory volume)
    Path:          /sysroot
    HostPathType:  Directory
   host-tmp:
    Type:          HostPath (bare host directory volume)
    Path:          /tmp
    HostPathType:  Directory
   host-usr-bin:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/bin
    HostPathType:  Directory
   host-usr-lib:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/lib
    HostPathType:  Directory
   host-usr-lib64:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/lib64
    HostPathType:  Directory
   host-usr-libexec:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/libexec
    HostPathType:  Directory
   host-usr-local:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/local
    HostPathType:  Directory
   host-usr-share-containers:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/share/containers
    HostPathType:  Directory
   host-var-lib:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib
    HostPathType:  Directory
   host-var-recovery:
    Type:          HostPath (bare host directory volume)
    Path:          /var/recovery
    HostPathType:  DirectoryOrCreate
   host-var-tmp:
    Type:          HostPath (bare host directory volume)
    Path:          /var/tmp
    HostPathType:  Directory
   sys-fs-cgroup:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/fs/cgroup
    HostPathType:  Directory
Events:
  Type    Reason            Age        From            Message
  ----    ------            ----       ----            -------
  Normal  SuccessfulCreate  0s         job-controller  Created pod: test-agent-prwzb
  Normal  Completed         <invalid>  job-controller  Job completed

Log for backup-agent pod:
sakhoury-mac:~ sakhoury$ oc -n openshift-talo-backup logs -f test-agent-prwzb
INFO[0000] Successfully mounted /host/dev/shm
INFO[0000] Successfully remounted /host/sysroot with r/w permission
INFO[0000] Successfully renamed /run/ostree-booted to /run/ostree-booted.tmp
INFO[0000] ------------------------------------------------------------
INFO[0000] Cleaning up old content...
INFO[0000] ------------------------------------------------------------
INFO[0000] Old directories deleted with contents
INFO[0000] Old contents have been cleaned up
INFO[0000] Available disk space : 39.67 GiB; Estimated disk space required for backup: 2.06 GiB
INFO[0000] Sufficient disk space found to trigger backup
INFO[0000] Upgrade recovery script written
INFO[0000] Running: bash -c /var/recovery/upgrade-recovery.sh --take-backup --dir /var/recovery
INFO[0000] ##### Thu Dec 14 16:48:37 UTC 2023: Taking backup
INFO[0000] ##### Thu Dec 14 16:48:37 UTC 2023: Wiping previous deployments and pinning active
INFO[0000] error: Out of range deployment index 1, expected < 1
INFO[0000] Deployment 0 is now pinned
INFO[0000] ##### Thu Dec 14 16:48:37 UTC 2023: Backing up container cluster and required files
INFO[0000] Certificate /etc/kubernetes/static-pod-certs/configmaps/etcd-serving-ca/ca-bundle.crt is missing. Checking in different directory
INFO[0000] Certificate /etc/kubernetes/static-pod-resources/etcd-certs/configmaps/etcd-serving-ca/ca-bundle.crt found!
INFO[0000] found latest kube-apiserver: /etc/kubernetes/static-pod-resources/kube-apiserver-pod-9
INFO[0000] found latest kube-controller-manager: /etc/kubernetes/static-pod-resources/kube-controller-manager-pod-6
INFO[0000] found latest kube-scheduler: /etc/kubernetes/static-pod-resources/kube-scheduler-pod-6
INFO[0000] found latest etcd: /etc/kubernetes/static-pod-resources/etcd-pod-3
INFO[0001] d0983475ecb5c60f8f198b6b18b25235c9e1909483376a3f57a635fa8bd617d6
INFO[0001] etcdctl version: 3.5.9
INFO[0001] API version: 3.5
INFO[0001] {"level":"info","ts":"2023-12-14T16:48:38.097653Z","caller":"snapshot/v3_snapshot.go:65","msg":"created temporary db file","path":"/var/recovery/cluster/snapshot_2023-12-14_164837__POSSIBLY_DIRTY__.db.part"}
INFO[0001] {"level":"info","ts":"2023-12-14T16:48:38.110616Z","logger":"client","caller":"v3@v3.5.9/maintenance.go:212","msg":"opened snapshot stream; downloading"}
INFO[0001] {"level":"info","ts":"2023-12-14T16:48:38.110663Z","caller":"snapshot/v3_snapshot.go:73","msg":"fetching snapshot","endpoint":"https://<IP_ADDRESS>:2379"}
INFO[0002] {"level":"info","ts":"2023-12-14T16:48:39.021653Z","logger":"client","caller":"v3@v3.5.9/maintenance.go:220","msg":"completed snapshot read; closing"}
INFO[0002] {"level":"info","ts":"2023-12-14T16:48:39.061314Z","caller":"snapshot/v3_snapshot.go:88","msg":"fetched snapshot","endpoint":"https://<IP_ADDRESS>:2379","size":"81 MB","took":"now"}
INFO[0002] {"level":"info","ts":"2023-12-14T16:48:39.061409Z","caller":"snapshot/v3_snapshot.go:97","msg":"saved","path":"/var/recovery/cluster/snapshot_2023-12-14_164837__POSSIBLY_DIRTY__.db"}
INFO[0002] Snapshot saved at /var/recovery/cluster/snapshot_2023-12-14_164837__POSSIBLY_DIRTY__.db
INFO[0002] {"hash":3892943378,"revision":1018454,"totalKey":6089,"totalSize":80580608}
INFO[0002] snapshot db and kube resources are successfully saved to /var/recovery/cluster
INFO[0002] Command succeeded: cp -Ra /etc/ /var/recovery/
INFO[0002] Command succeeded: cp -Ra /usr/local/ /var/recovery/
INFO[0004] Command succeeded: cp -Ra /var/lib/kubelet/ /var/recovery/
INFO[0004] ##### Thu Dec 14 16:48:41 UTC 2023: Backup complete
INFO[0004] ------------------------------------------------------------
INFO[0004] backup has successfully finished ...
INFO[0004] Successfully renamed /run/ostree-booted.tmp back to /run/ostree-booted

/test all

/test integration

/cc @jc-rh

/jira refresh

/cherrypick release-4.14


fix(concat): return type being wrapped in Iterable/Iterator

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (2c06573) compared to base (957b9c6).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #129   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           40        40
  Lines         1240      1240
  Branches       260       260
=========================================
  Hits          1240      1240

Impacted Files
Coverage Δ

src/types/index.ts
100.00% <ø> (ø)

src/ops/concat.ts
100.00% <100.00%> (ø)

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

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

Can you tell me what does it fix exactly, please? I cannot figure it out from the change...

The typing for concat was slightly wrong.
Before it was sometimes returning things along the lines of IterableIterator<SomeType> | SomeOtherType instead just SomeType | SomeOtherType.
This fix will remove any Iterable/Iterator wrapper around those types.


Feature/dsnd 498 transform charges

DSND-498:
Transform charges delta to charges API request

Addressed all the PR comments. Kindly have a look please.


Fixed for Django 2.1

Django versions from 1.10 to 2.1 are supported in an almost equal quality, but still less than it was with Django 1.9. (version that is currently unsupported)
Included the first two commits from #216

I think that this PR is roughly all for Django 2.0 / 2.1 that could be done fast and that is considered relative stable, in order to release a new version (next week?)

So, the Travis check above failed because of the continuing issues with making all the necessary Python versions available on Travis. I'll work on that independently.
But do we want to bother targeting Python 3.5 anymore? It seems everyone is finally getting onboard the Python 3 train around 3.6. Just a thought....

Ubuntu 16.04 LTS won't upgrade past python 3.5 with the official apt repos.  Not sure if that matters to you guys or not, but just thought I'd chime in with it.

@chromakey thanks, that sounds like a good enough reason to me to keep testing on it. I’m sure this is a simple issue, i just haven’t taken a deeper look yet

I found and I fixed now a bug in generator with StopIteration that was specific to Python 3.7. I had to start to check regularly also Python 3.7 therefore.
I test every last commit before push also with Python 3.5 and 3.7, but I temporarily replaced them in Travis by Python 3.6.
Please re-run Travis on the latest commit to see if the commit succeeded.

@hynekcer If you have a moment and could pull/push the additional commit I added at django-salesforce/django-salesforce@0ee92187, that will update the Travis config to use Xenial and re-add support for 3.5


118 auto placement and snapping

Say hello to RoadContainer snapping! Please review the requirements and the new capabilities and let me know if anything is missing or needed.
MAIN HILIGHTS:

Select RoadPoint and click "Roads>RoadPoint" to add a new RoadPoint and connect it to selected. (The remaining requirements were unclear. Please let me know if you want to add more to the "Roads>RoadPoint" feature.)
Select a RoadContainer or Nested Scene RoadContainer and LMB-drag it near some unconnected Edge RoadPoints. A snapping guide will appear between an Edge RoadPoint in the dragged container and the closest external Edge RoadPoint. Upon LMB-release, the container will snap to the target RoadPoint. Adjust plugin.ROADPOINT_SNAP_THRESHOLD to increase/decrease the snapping distance.

ADDITIONAL NOTES:
Implementation uses "_connect_rp_on_click" to create Inter-RoadContainer linkage when the selected container is snapped. But, that comes with some pros and cons.
On the pros side, if the snapped RoadContainer is moved, the user can click Update Roads and maintain the linkage to the snapped RoadPoint.
On the cons side, moving the snapped RoadContainer sometimes seems to leave open edge RoadPoints that don't remain linked. But, they can no longer be used in connections.
Sometimes, there is also a drawing issue that requires a delicate dance of Refreshing Roads and moving the RoadContainer around until everything redraws as expected.
There is also a separate intermittent drawing issue for the snapping guides. Sometimes, if the user drags really fast and then stops, the snapping guide may appear in what might be called the previous frame's position rather than the current frame's position. Additional dragging causes the guide to update as expected.
When snapping RoadContainers, there is a long pause upon LMB-release. Checked the timing of different phases of the commit proces and it only takes 6ms to perform the necessary transforms. So, it's unclear what is causing the actual pause. Let me know if you want me to dig deeper.

If you wish to simulate an Intersection and test:

Create a new "nested" scene with a RoadContainer as the root node
Create Edge RoadPoints for external connections (here's how)

Add a 2x2 Road

This adds two RoadPoints
A RoadPoint must be connected to another RoadPoint to be considered a valid "Edge"
In the future, the RoadIntersection object should take the place of the 2nd RoadPoint

Select one of the RoadPoints, and set its "terminated" property to "true"

Only un-terminated RoadPoints will be treated as Edges

Place as many of these 2x2 Roads as needed for external connections

Save and close the scene
Create a new "main" scene for testing

Add a RoadManager
Add a RoadContainer to the RoadManager
Add a 2x2 Road to the RoadContainer
Add the nested scene to the RoadManager
Save the main scene's default state so it can be restored quickly

Test snapping functionality

Drag nested scene towards RoadContainer in main scene

Snapping previews are displayed when RoadPoints are in close proximity

Release LMB when snapping preview hilights desired RoadPoints

Nested scene snaps into position

For kicks, try snapping two RoadContainers together or two Nested Scenes.
Also, try moving containers after linkage has been created and observe what works and what doesn't work.

Try using "Roads>Refresh roads" to update the scene afterwards

Great to have this hands on! I'm testing it out now, and already having a great time snapping road pieces together. Pretty solid, just a few comments so far from me:
A: Connection tool for snapping not always displayed
Maybe you are referring to this above, sometimes the snapping connection preview line doesn't display, even when the snapping itself still works in the end. Haven't debugged deeply, but I think my pressing undo in the video below is the culprit, though maybe there are other scenarios. The snapping indicator seems to forever not draw however, even after manually changing the export vars of the container to simulate clearing. Maybe we need to properly clear the properties set on undo/redo for the snapping?
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/8df0ecb7-e8aa-4de0-90ae-acd524b45ddb
B: Adding "next" roadpoint via selection

Select RoadPoint and click "Roads>RoadPoint" to add a new RoadPoint and connect it to selected. (The remaining requirements were unclear. Please let me know if you want to add more to the "Roads>RoadPoint" feature.)

As for the next RP on add, yes I think the change is useful, working nicely! My next question would be...
C: Snapping tool for RPs moved to overlap containers
How much of a challenge would it be to extend the snapping tool we have for RoadPoints (snapping to container edges) too? See an example here, where I'm looking to connect this existing RP to another RP on another (non-saved scene) container. So it's kind of like a shortcut to connect a dynamic (open scene) container's RP to another container, without having to use the connection tool (which would also create another RP in the process).
Demo of what I'm hoping could be able to do the appropriate snapping (and auto adjustment of the lane counts/widths/shoulders to match what we're snapping onto):
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/9ccd2516-e359-4158-8472-994314927e25
D: Eliminating extra RP added when connected via snapping
Finally, snapping a road container to an existing same-scene ("dynamic") container I think should result in modifying the point being snapped to, instead of creating a new one. I think that'll be more intuitive for users in the end. So it means the number of lanes on RP_002 in the video below would be modified (and width, shoulder) to match the edge of the SavedRoad I'm snapping. I'd say the reverse should be true based on my paragraph above, where you move a RoadPoint to overlap with an open edge of another container.
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/62980d92-79ca-4381-b579-d448665570fd
E: The "terminating" feature working
See here my little demo, works nicely! As you say, we'll change this to an intersection point in the future, but works for now. Only comment is that our "connection tool" (not to be confused with our snapping feature here) still picks up these point. But, since we're going to change it, I'd so don't worry about filtering out RPs for the selection tool, it's more a note to self in the future.
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/5da0b53f-111e-4368-92b1-d4a0f69e0168
(also posted to Twitter here)
Regarding the delay, I didn't notice it for my smaller 2-roadpoint snapping, but did notice it for my larger scene snapping. My gut tells me it's due to the transform on the container somehow triggering a rebuilding of all the geo for the container (which ideally, it should know it doesn't need to do). So I'm not worried about that in this PR, something for us to address separately.
Summary
Curious to hear what you have to say on each of the above, and then based on your response we can discuss priority (maybe we don't need to do all of this right now).

We need to clearly define how RoadPoint relationships work in the following connections:
1 RoadContainer to Roadcontainer
2 Nested Scene to RoadContainer
3 Nested Scene to Nested Scene
Important questions on this topic: Do we ever connect RoadPoints directly via their pt_inits? When do we add extra support RoadPoints? How do we clear support RoadPoints? How do we clear support data not stored in RoadPoints? Do we auto update lanes when snapping? Which lanes take precedence (selected or target RoadPoint)?
A: Connection tool for snapping not always displayed
What properties are set by "_connect_rp_on_click"? How do we clear them? The inner workings didn't make sense to me. But, I could see that there were 4 arrays roughly called "rp_locals". They were used for some connections and omitted on others. We could just refrain from using _connect_rp_on_click in certain situations and do more direct and traditional pt_init connections.
B: Adding "next" roadpoint via selection - Excellent!
C: Snapping tool for RPs moved to overlap containers
This sounds do-able. In theory, this blends in with the RoadContainer snapping. We simply ask: Is dragged object a RoadContainer... Is dragged object a RoadPoint. Snap this way if it's a RoadContainer. Snap this other way if it's a RoadPoint. We need clear requirements. Hence, it's important to answer all of the questions at the beginning of this list.
D: Eliminating extra RP added when connected via snapping
RoadContainer snapping employs the same behavior as the Connection Tool. Does the Connection Tool behave in the desired manner? Maybe we have a mix of scenarios and we need to define different behavior for each one.
E: The "terminating" feature working- Great!

Important questions on this topic: Do we ever connect RoadPoints directly via their pt_inits? When do we add extra support RoadPoints? How do we clear support RoadPoints? How do we clear support data not stored in RoadPoints? Do we auto update lanes when snapping? Which lanes take precedence (selected or target RoadPoint)?

In terms of the two modes/operations:

Snapping: Should never create new roadpoints, but instead the operation is the movement of "something" (for now, a container; in the future, could be RoadPoints as well)
Connection tool: Should never move roadpoitns

in the case of connection two RPs, nothing new should be created, it's just a connection
Between an RP of the active container, and an RP on another container, when creating a connection: this should always create a new RP, becayse we assume the two source RPs are not in the same location, and by definition of the conneciton too, we aren't moving any nodes, therefore to create a exactly aligned matching conneciton we have to create a new RoadPoint. This new roadpoint becomes the new "edge" roadpoint, and this is the one which is visualized as connected via the export vars on the parent container.

Supporting point (and something we should well document):

The edges of containers are by definition roadpoints with open connections; therefore a connection across a road container is really managed by the export vars on the road container itself, not by setting the paths of the RoadPoint within the respective containers.

Focus for this week:

Let's add the "unsnapping" tool, where when moving a RoadContainer which is connected to another road container, it will automatically disconnect on release, as well as visualize that it would be performing the disconnect using the red line drawing overlay (similar to the disconnect mode we see in the connect tool).

It might make sense to still account for the existing radius; if we don't exceed this radius, it should snap back into place (ie no change in the end). So underneath this radius, we can show the blue-gray indicator; outside this radius, it will show as red.

Look into what is allow the snapping tool to still snap even when the connection isn't actually open

To recreate: drag in a saved scene, snap connect one side. Then drag and connect the other side (without manually "disconnect", so in theory both sides are now somehow connected). Finally, drag one back to overlap the first initial connect RoadPoint, to find that it snaps without the visual

Let's see if we can fix some bugs by converting the initialized "" nodepath values of the container export vars (initially set in the cotnainer.update_edges, and anywhere else that we are "clearing" the, clear to a null instead of a "" (assuming it lets us). Failing that, we'll need to sprinkle some extra checks for val is null or val == ""

Let's do this in this branch for now. Out of scope for now:

Fixing the redo last
The RoadPoint snapping
Elimination of the extra roadpoint + live updating the lane counts (let's get things stable first).
Snapping disconnection with a same-scene container and another saved scene container.

Updates have been made to insure that connected Edges won't accept new connections. Unsnapping is also in an introductory state.
Keep in mind that these changes target primarily scene to scene connections versus RoadContainer to RoadContainer connections. Although, those do function. But, they might require some additional work to become fully fleshed out.
Made an executive decision regarding unsnapping scenes with multiple connections. Read on to learn more and feel free to make additional suggestions.
When unsnapping a scene with a single connection, a single blue or red line is shown to indicate whether the action will result in a snap or an unsnap.
When unsnapping a scene with multiple connections, a single blue or red line is shown as before. However, it only references the 1st connection in the list of connections. Other connections DO NOT display a line. However, they DO get unsnapped so that they're available for future connections.
This iteration uses the "_disconnect_rp_on_click" function. The main takeaway is that unsnapping a scene with multiple connections results in multiple undo points; one for each connection plus a translate. So, additional work will be needed if we want a singular undo point. At any rate, unsnapping feels pretty good so far!

Leaving an initial comment as I found one edge case; similar to RP's, we'll probably have to do a "cleanup routine" which requires doing checks for two container edges being mutually connected (and if not, resetting the one making the "false claim"), replicated here by duplicating a node that had one connection already.
Likely want to resolve this in the similar way as we have it for roadpoints, via their "_autofix_noncyclic_references". Does mean creating and then sprinkling around an equivalent _is_internal_updating var (not export var) on the container class. If we end up not needing, then great! That would actually be the best case scenario. The reason this is a problem for roadpoitns is because we have to do this cyclic check in the routine that runs immediately after any RoadPoint prior/next connection change, and thus could (without this internal flag) interrupted "internal" changes we were trying to do.
https://github.com/TheDuckCow/godot-road-generator/assets/2958461/828a9ea7-37d9-498c-8965-6fa7064ea241

This week's primary focus was to Move Connected RoadPoints when the user dragged a RoadContainer. Secondary focus was fixing references. This inquiry is about Moving Connected RoadPoints.
The request conflicts with the "Unsnapping" feature. Hence, we have to make some decisions about whether to treat a Scene Move as an Unsnap or a Move.
One approach is to always Unsnap Scene to Scene connections and always Move Connected RoadPoints. Users would simply need to employ the "Connection Tool" to Disconnect connected RoadPoints. For now, I'm working on that scenario.
In the scenario of moving a Scene connected to a "RoadContainer": The choice is arbitary. We could "Unsnap" or we could "Move Connected". But, we can't do both. Maybe we could Unsnap by default and Move Connected when user pressed "shift".
Assuming we used shift to Move Connected, then we would need to consider how that worked when two "Scenes" were connected. We could Move the Connected Scene along with the Selected Scene. But, that could potentially lead to a cascade of Scenes moving all at once. The safest bet would be to simply Unsnap the Connected Scene even though we're technically performing a "Move Connected" action.
Putting it all together: We could be Moving a Scene connected to both a RoadContainer and another Scene simultaneously. So, the default behavior would be to Unsnap everything. If user pressed shift, then we would Disconnect the two Scenes. But, we would Move the RoadContainer's connected point because shift was pressed.
Again, I am currently setting the behavior so that Scene to Scene connections are always Unsnapped and Scene to RoadContainer connections are always Moved. Please let me know if you want it to work differently.

When dragging a "Connected" Container, current behavior is to always Unsnap. Snapping is only available on "Unconnected" Containers. This provides behavior that is clean and concise. Containers are either Snapping or Unsnapping. Never both.
We cannot currently Snap a Container if it has a "Moving" RoadPoint because that makes it "Connected". However, we can modify the logic to ignore the Moving RoadPoints as long as we don't intend to Unsnap them. Hence, that is the assumption for the time being.

Hey @bdog2112 here's how I would think of it:

The request conflicts with the "Unsnapping" feature. Hence, we have to make some decisions about whether to treat a Scene Move as an Unsnap or a Move.

I'd prioritize like this:

Prefer "dynamic" movements where possible
Fall back to snapping/unsnapping if that's not possible.

So with that philosophy in mind, a few scenarios and how I'd consider treating them:

Moving a saved scene away from a saved scene: only unsnapping applies, as we assume we can't modify saved scenes
Moving a same-scene container (A) which is connected to another same-scene container (B):

These are BOTH dynamic elements, and so we have full flexibility.
If the user is moving container A, which means the entire container is visually selected, they probably expect all portions of meshes contained inside container A to be moved together. Therefore the result of moving container A is that the connecting edge roadpoint of container B gets moved (while container B as a parent remains unmoved, and the other RoadPoints of container B are left in place)

Moving a saved scene container A which is connected to the open-scene container B

Treated identically to the above scenario actually, container A can't be modified while container B can be, so the connecting roadpoint of container B is moved to keep up with the new location of Container A

Moving an open-scene container B which is connected to the saved-scene container B

We can't modify scene B, so our only option is to move container A as a whole, but then countering/inverting the movement of the ContainerA's connecting RoadPoint  to container B so that A.rp_edge visually looks like it's not moving (even though relative to its parent, it is in fact moving)

That's how I see the default behavior. Let me know if that clarifies everything, and likewise if you agree this feels intuitive enough.
That being said, your idea to have some modifier to "sever" the connections is interesting, such that we would always "unsnap" instead of "Move connected". It could eventually even be a UI setting tool to specify which behavior. I'd say, if it's not a huge amount of extra work, you could secondarily work on this such that when the user presses ALT, it would unsnap everything it's connected to. ALT I think is a more similar action for something like this, where shift or control tend to be used for snapping movement to grid intervals or for slowing/speeding up the movement (since this would be happening during the middle of a user doing a transform).
But still, I'd do so secondarily, let's get the base functionality of "prefer dynamic" working first. I could imagine we release first without this tool - May is getting away from us, and I'd like us to get some time on Wheel Steal's next milestone too.

That's how I see the default behavior. Let me know if that clarifies everything, and likewise if you agree this feels intuitive enough.

The above makes sense. It covers the simplest scenarios. Although, we still need to address the more complex scenario previously mentioned:
We have a Saved Scene connected to both a Saved Scene and a RoadContainer. Current behavior is to Snap or Unsnap. Not both. In this scenario, when the Saved Scene is dragged, everything Unsnaps.
In the future, we're saying to always move the RoadPoint from the RoadContainer (don't Unsnap it). So, the Saved Scene will always have a connection. Therefore, it can no longer be Snapped. I'm fine with that. Just want to make sure you're ok with it.
We need a consistent way to determine if we're Snapping or Unsnapping.

Snap if the dragged object has no connections (That's a no brainer.)
Also Snap if ___________________ (fill in the blank)
Unsnap if ___________________ (fill in the blank)

Fow now, when dragging a Saved Scene, I will assume that we always move the RoadContainer connections and we always Unsnap the Saved Scene connections. We will never Snap the Saved Scene connections as long as there is at least 1 RoadContainer connection.

Might be easier to talk over live later, but maybe this detail helps: with scenarios I listed in my prior post, I was assuming we would treat each connection independently. So in indeed you would have "both". That way, a complex case is just the simple case applied per connection. So one connection to a saved scene would unsnapped as a result (if the scene we are moving is also a saved scene), while another results in another RP moved in another container (if that connected container is in the open scene).

We will never Snap any open Edges if there is 1 or more RoadContainer connection. In order to Snap,, all Edges must be open.

This is also a good one to consider. We can also chat through this one, but I think it could work more nicely if we do allow snapping but only if either all edges are open, or if all of the used connections are to open scene containers (resulting in the edge roadpoints of those containers to also be moved as a result of the snapping).

Added drawing of Unsnapping lines for ALL containers.
Next up: Move connections to adjacent RoadContainers instead of Unsnapping them. i.e. When user drags Saved Scene 1 with a connection to Saved Scene 2 and a connection to a RoadContainer, Saved Scene 2 will show an Unsnapping line while the RoadContainer's attached RoadPoint will move along with Saved Scene 1. (Tricky. But, useful)

WIP diff: wip_diff.zip

Screenshot of resolved unsnapping line color issue. In this scenario, both lines should have been light blue.

As discussed today, while you work on resolving the placement of prefab scenes in Wheel Steal, I'm going to take over this branch to get it to a publishable state. I'll do a bit of an audit to see what remains here and then commence working on that.

This branch is basically done, I'm just challenging myself to improve the undo stack for the disconnection side of the picture so that the first undo of a disconnect does both the translation and property changes, instead of translation and then property changes (2 undo steps).
Because we are hooking on top of the built in translate, snapping and unsnapping via drag unfortunately have to chain before or after the built in undo redo, but as opposed to the move+snap being treated as one operation. Getting around that would probably mean inventing our own completely custom translation/rotation/scaling tool, which I want to avoid/one of the whole points of using RoadPoints as inheriting from spatials was to leverages the built in transforms.

Calling this good enough at this stage so we can merge. See the state of redo/undo here with the most recent logic, which reduces warnings on the do step (still some rogue over-warning during the undo steps). The undo sequence for disconnecting still has the wrong order of steps (translate happens is done first, and then the disconnection is done, which means undo first re-connects and then another undo step places it in the correct position) but we'd have to somehow trigger an operator before the internal move trigger ocurrs, which may not be feasible. So, good enough for now.
https://github.com/user-attachments/assets/ca6d2f5c-7490-435a-9b0a-b27458b541d9


Add a way to add WordPress

Hello,
as a WordPress developer, I face many core functions/class issues. I have been using VS Code for a long time. Some days ago I tried PHP Strom and saw in PHP Strom they have a setting option to add a WordPress files directory so the editor can check and go to functions/definitions easily. I am expecting something similar in VS Code.
Thanks

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


scroll down and top agian

when i scoll down effect very good , but when i scroll to top effect not again

What I believe DungBuiDeveloper said is that  while there are animations for when you first scroll to the component (i.e. Fade In), there doesn't seem to be  a way  to animate Component when you scroll away (i.e. Fade Out).
Is there a way for that to be done with react-reveal?

Was there ever a response / another post for this one?


Add HEWL example and documentation

Debugging efforts
As part of the debugging effort, I set up and ran a 60ns simulation of hen egg-white lysozyme (HEWL), using pdb structure 4LZT. This ran successfully. I've added this simulation input as an example in the protons/examples subdirectory.
I also tried running a separate simulation of a non-protonatable Crizotinib molecule, just to check if anything was off about ligand parameters. This ran successfully as well, so probably the ligand parameters on their own are not sufficient to cause crashes. I think most of the simulation instability might be due to bad structures.
I might try a system where I add Crizotinib to the HEWL system, just to see if there are some unexpected issues when combining the const-pH system with the small molecule.
Documentation update
While I was setting up the example system, I decided to document the procedure because it was something that was in the planning ( #54 ), and I was working out how to canonicalize the steps and make them easier to reproduce anyways.
I also did some restructuring of the documentation, to make it easier to read, and I also ended up refining some of the information in there.
You can preview the docs here: http://constph-openmm.readthedocs.io/en/todo-system-prep/

Current coverage is 81.00% (diff: 100%)

Merging #57 into master will decrease coverage by 0.08%

@@             master        #57   diff @@
==========================================
  Files             9          9
  Lines          1195       1195
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            969        968     -1
- Misses          226        227     +1
  Partials          0          0

Powered by Codecov. Last update 39b698b...9417faa


Issue 272 - fixes buttons in room 11 and Escoria icon being wrong

Fixes https://github.com/godot-escoria/escoria-issues/issues/272.
Adds "use" actions for all buttons in addition to existing "look" action. Sets default action on buttons to "use".
Also fixes the Escoria icon which somehow got changed incorrectly.

Thanks!


Re-capture updated image from VM created from an image?

I want to be able to fix a VM image by deploying it, changing it then re-capturing a new version back into my image gallery.  But when I create a VM from an image, using + create VM button in the image gallery, the image Capture button is disabled?  Also when I Capture an image the Start becomes disabled because the image has been generalized, so I can't update and recapture the original image either.  So it seems both "efficient pathways" to editing an image are cut off.  Why is that?  Having to setup a brand new VM from scratch every time is quite a hassle.

Never mind, I just had to "stop" the VM then the Capture button appears.  Just a bit different from when I created the VM in the first place Capture was enabled and Capture would automatically stop the VM...


Tag Cloud Widget: tags with several words

In some of my posts, I have tags with several words like Teoría de números, Fórmula de Legendre...
They appear, in the Tag Cloud widget, as teoría-de-números, fórmula-de-legendre... it would be possible that the text for the link in that area were the same as in the tag declaration?

Thanks for reporting this. In previous releases it was working fine.
It appears that there was a breaking change with taxonomies in Hugo 0.55: https://github.com/gohugoio/hugo/issues/5843
We can release an update get the previous functionality back.


v2.15.0 causes our make build to get stuck indefinitely

Dependencies are shown in the trace below:

[2023-05-08T11:22:01.407Z] + make make-docs

[2023-05-08T11:22:01.414Z] # mkdocs and dependencies installation

[2023-05-08T11:22:01.414Z] python3 -m venv python_deploy_docs

[2023-05-08T11:22:04.699Z] source python_deploy_docs/bin/activate;

[2023-05-08T11:22:04.699Z] pip3 install -r requirements.txt

[2023-05-08T11:22:04.958Z] WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3 install --user` instead.

[2023-05-08T11:22:04.958Z] Processing ./mkdocs-plugins/mkdocs-skip-drafts-plugin

[2023-05-08T11:22:05.216Z] Processing ./mkdocs-plugins/mkdocs-git-revision-date-plugin-master

[2023-05-08T11:22:05.474Z] Collecting Click==7.0

[2023-05-08T11:22:05.474Z]   Downloading Click-7.0-py2.py3-none-any.whl (81 kB)

[2023-05-08T11:22:05.474Z] Collecting Jinja2>=2.11.1

[2023-05-08T11:22:05.474Z]   Downloading Jinja2-3.1.2-py3-none-any.whl (133 kB)

[2023-05-08T11:22:05.474Z] Collecting livereload==2.6.0

[2023-05-08T11:22:05.474Z]   Downloading livereload-2.6.0-py2.py3-none-any.whl (22 kB)

[2023-05-08T11:22:05.732Z] Collecting Markdown==3.2.1

[2023-05-08T11:22:05.732Z]   Downloading Markdown-3.2.1-py2.py3-none-any.whl (88 kB)

[2023-05-08T11:22:05.732Z] Collecting MarkupSafe>=2.0.0

[2023-05-08T11:22:05.732Z]   Downloading MarkupSafe-2.1.2-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (26 kB)

[2023-05-08T11:22:05.990Z] Collecting mkdocs-material==8.5.6

[2023-05-08T11:22:05.990Z]   Downloading mkdocs_material-8.5.6-py3-none-any.whl (7.5 MB)

[2023-05-08T11:22:06.248Z] Collecting mdx_truly_sane_lists==1.2

[2023-05-08T11:22:06.248Z]   Downloading mdx_truly_sane_lists-1.2-py3-none-any.whl (5.0 kB)

[2023-05-08T11:22:06.506Z] Collecting pymdown-extensions==9.6

[2023-05-08T11:22:06.506Z]   Downloading pymdown_extensions-9.6-py3-none-any.whl (218 kB)

[2023-05-08T11:22:06.506Z] Collecting pyyaml>=4.2b1

[2023-05-08T11:22:06.506Z]   Downloading PyYAML-6.0-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (656 kB)

[2023-05-08T11:22:06.765Z] Collecting six==1.11.0

[2023-05-08T11:22:06.765Z]   Downloading six-1.11.0-py2.py3-none-any.whl (10 kB)

[2023-05-08T11:22:06.765Z] Collecting tornado==5.1.1

[2023-05-08T11:22:06.765Z]   Downloading tornado-5.1.1.tar.gz (516 kB)

[2023-05-08T11:22:07.331Z] Collecting python-frontmatter==0.4.5

[2023-05-08T11:22:07.331Z]   Downloading python_frontmatter-0.4.5-py3-none-any.whl (8.2 kB)

[2023-05-08T11:22:07.331Z] Collecting plantuml-markdown==3.4.2

[2023-05-08T11:22:07.331Z]   Downloading plantuml_markdown-3.4.2-py3-none-any.whl (10 kB)

[2023-05-08T11:22:07.331Z] Collecting mkdocs>=0.17

[2023-05-08T11:22:07.331Z]   Downloading mkdocs-1.4.3-py3-none-any.whl (3.7 MB)

[2023-05-08T11:22:07.590Z] Collecting GitPython

[2023-05-08T11:22:07.590Z]   Downloading GitPython-3.1.31-py3-none-any.whl (184 kB)

[2023-05-08T11:22:07.590Z] Requirement already satisfied: setuptools>=36 in /usr/lib/python3.7/site-packages (from Markdown==3.2.1->-r requirements.txt (line 5)) (49.1.3)

[2023-05-08T11:22:07.590Z] Collecting mkdocs-material-extensions>=1.0.3

[2023-05-08T11:22:07.590Z]   Downloading mkdocs_material_extensions-1.1.1-py3-none-any.whl (7.9 kB)

[2023-05-08T11:22:07.847Z] Collecting pygments>=2.12

[2023-05-08T11:22:07.847Z]   Downloading Pygments-2.15.1-py3-none-any.whl (1.1 MB)

[2023-05-08T11:22:07.847Z] Collecting requests>=2.26

[2023-05-08T11:22:07.847Z]   Downloading requests-2.30.0-py3-none-any.whl (62 kB)

[2023-05-08T11:22:08.106Z] Collecting plantuml

[2023-05-08T11:22:08.106Z]   Downloading plantuml-0.3.0-py3-none-any.whl (5.8 kB)

[2023-05-08T11:22:08.106Z] Collecting packaging>=20.5

[2023-05-08T11:22:08.106Z]   Downloading packaging-23.1-py3-none-any.whl (48 kB)

[2023-05-08T11:22:08.106Z] Collecting ghp-import>=1.0

[2023-05-08T11:22:08.106Z]   Downloading ghp_import-2.1.0-py3-none-any.whl (11 kB)

[2023-05-08T11:22:08.364Z] Collecting importlib-metadata>=4.3; python_version < "3.10"

[2023-05-08T11:22:08.364Z]   Downloading importlib_metadata-6.6.0-py3-none-any.whl (22 kB)

[2023-05-08T11:22:08.364Z] Collecting watchdog>=2.0

[2023-05-08T11:22:08.364Z]   Downloading watchdog-3.0.0-py3-none-manylinux2014_aarch64.whl (82 kB)

[2023-05-08T11:22:08.622Z] Collecting mergedeep>=1.3.4

[2023-05-08T11:22:08.622Z]   Downloading mergedeep-1.3.4-py3-none-any.whl (6.4 kB)

[2023-05-08T11:22:08.622Z] Collecting pyyaml-env-tag>=0.1

[2023-05-08T11:22:08.622Z]   Downloading pyyaml_env_tag-0.1-py3-none-any.whl (3.9 kB)

[2023-05-08T11:22:08.622Z] Collecting typing-extensions>=3.10; python_version < "3.8"

[2023-05-08T11:22:08.622Z]   Downloading typing_extensions-4.5.0-py3-none-any.whl (27 kB)

[2023-05-08T11:22:08.622Z] Collecting gitdb<5,>=4.0.1

[2023-05-08T11:22:08.622Z]   Downloading gitdb-4.0.10-py3-none-any.whl (62 kB)

[2023-05-08T11:22:08.880Z] Collecting charset-normalizer<4,>=2

[2023-05-08T11:22:08.880Z]   Downloading charset_normalizer-3.1.0-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (167 kB)

[2023-05-08T11:22:08.880Z] Collecting certifi>=2017.4.17

[2023-05-08T11:22:08.880Z]   Downloading certifi-2023.5.7-py3-none-any.whl (156 kB)

[2023-05-08T11:22:08.880Z] Collecting idna<4,>=2.5

[2023-05-08T11:22:08.880Z]   Downloading idna-3.4-py3-none-any.whl (61 kB)

[2023-05-08T11:22:09.138Z] Collecting urllib3<3,>=1.21.1

[2023-05-08T11:22:09.138Z]   Downloading urllib3-2.0.2-py3-none-any.whl (123 kB)

[2023-05-08T11:22:09.138Z] Collecting httplib2

[2023-05-08T11:22:09.138Z]   Downloading httplib2-0.22.0-py3-none-any.whl (96 kB)

[2023-05-08T11:22:09.138Z] Collecting python-dateutil>=2.8.1

[2023-05-08T11:22:09.138Z]   Downloading python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)

[2023-05-08T11:22:09.396Z] Collecting zipp>=0.5

[2023-05-08T11:22:09.396Z]   Downloading zipp-3.15.0-py3-none-any.whl (6.8 kB)

[2023-05-08T11:22:09.396Z] Collecting smmap<6,>=3.0.1

[2023-05-08T11:22:09.396Z]   Downloading smmap-5.0.0-py3-none-any.whl (24 kB)

[2023-05-08T11:22:09.396Z] Collecting pyparsing!=3.0.0,!=3.0.1,!=3.0.2,!=3.0.3,<4,>=2.4.2; python_version > "3.0"

[2023-05-08T11:22:09.396Z]   Downloading pyparsing-3.0.9-py3-none-any.whl (98 kB)

[2023-05-08T11:22:09.654Z] Using legacy 'setup.py install' for tornado, since package 'wheel' is not installed.

[2023-05-08T11:22:09.654Z] Using legacy 'setup.py install' for mkdocs-skip-drafts-plugin, since package 'wheel' is not installed.

[2023-05-08T11:22:09.654Z] Using legacy 'setup.py install' for mkdocs-git-revision-date-plugin, since package 'wheel' is not installed.

[2023-05-08T11:22:09.912Z] Installing collected packages: Click, MarkupSafe, Jinja2, six, tornado, livereload, Markdown, mkdocs-material-extensions, packaging, python-dateutil, ghp-import, pyyaml, zipp, typing-extensions, importlib-metadata, watchdog, mergedeep, pyyaml-env-tag, mkdocs, pymdown-extensions, pygments, charset-normalizer, certifi, idna, urllib3, requests, mkdocs-material, mdx-truly-sane-lists, python-frontmatter, pyparsing, httplib2, plantuml, plantuml-markdown, mkdocs-skip-drafts-plugin, smmap, gitdb, GitPython, mkdocs-git-revision-date-plugin

[2023-05-08T11:22:09.912Z]     Running setup.py install for tornado: started

[2023-05-08T11:22:10.478Z]     Running setup.py install for tornado: finished with status 'done'

[2023-05-08T11:22:14.665Z]     Running setup.py install for mkdocs-skip-drafts-plugin: started

[2023-05-08T11:22:14.665Z]     Running setup.py install for mkdocs-skip-drafts-plugin: finished with status 'done'

[2023-05-08T11:22:14.923Z]     Running setup.py install for mkdocs-git-revision-date-plugin: started

[2023-05-08T11:22:15.181Z]     Running setup.py install for mkdocs-git-revision-date-plugin: finished with status 'done'

[2023-05-08T11:22:15.181Z] Successfully installed Click-7.0 GitPython-3.1.31 Jinja2-3.1.2 Markdown-3.2.1 MarkupSafe-2.1.2 certifi-2023.5.7 charset-normalizer-3.1.0 ghp-import-2.1.0 gitdb-4.0.10 httplib2-0.22.0 idna-3.4 importlib-metadata-6.6.0 livereload-2.6.0 mdx-truly-sane-lists-1.2 mergedeep-1.3.4 mkdocs-1.4.3 mkdocs-git-revision-date-plugin-0.3 mkdocs-material-8.5.6 mkdocs-material-extensions-1.1.1 mkdocs-skip-drafts-plugin-0.0.1 packaging-23.1 plantuml-0.3.0 plantuml-markdown-3.4.2 pygments-2.15.1 pymdown-extensions-9.6 pyparsing-3.0.9 python-dateutil-2.8.2 python-frontmatter-0.4.5 pyyaml-6.0 pyyaml-env-tag-0.1 requests-2.30.0 six-1.11.0 smmap-5.0.0 tornado-5.1.1 typing-extensions-4.5.0 urllib3-2.0.2 watchdog-3.0.0 zipp-3.15.0

I can't unfortunately share our files because they include company private information but i can try minimize the project/content. Is there sth else you need other than the documentation file

v2.15.1 doesn't work either. i'm trying to create a minimal project to reproduce the issue but when i remove big chunk of the docs then the issue goes away, so i need to narrow down which file or files causes the issue. will continue with that on Monday

Yes, we noticed that triple quote make it work but still wanted to provide you the reproducible bug :)


Types from @figma/plugin-typings are not available when installed

👋  Loving this tool
I noticed that the page nodes I get back from getAllPages() are typed as any which I believe is because y'all are depending on ambient types from the @figma/plugin-typings existing which will not be the case when this library is installed externally.
I think the fix would be to make that a dependency of this package and import them over expecting them to be implicitly available through typeRoots

Upon further inspection it looks like those types are meant to be included this way... So maybe it just needs to part of the install instructions


training.plone.org is not automatically updated when changes are pushed to the repo

We totally need that.

I just send you a reply, I will look into it tomorrow and  the next days, to make sure that gets fixed asap.

We got it now. Yay GitHub Actions!


Rewrite tests to work on Rails 4.0, 4.1, 4.2, and 5.0

Right now the tests for bootstrap_form are hardcoded to work with Rails 4.0.0. As mentioned in #229, the tests break if one upgrades the Gemfile.lock to Rails 4.1 or newer. I think improving our testing is extremely important and should be our top priority before pursuing other features (e.g. Bootstrap 4 support).
Ideally our tests should pass on all supported versions of Rails, meaning 4.0, 4.1, 4.2, and 5.0.
Does anyone have suggestions for how we can accomplish this?
I will gladly accept a PR if you want to take a shot. Please make a proposal in this thread first before submitting a PR.

Rails 5 no longer outputs tag attributes in alphabetical order, so I think we need some kind of dynamic html matching (using nokogiri?). Also, additional tags are rendered in Rails 5, like an empty hidden input preceding a file input.
All the differences between output in Rails 4 vs 5 can be seen in the diff here: https://github.com/bootstrap-ruby/rails-bootstrap-forms/pull/269/files

I like the idea of using a HTML parser for matching expected output. Perhaps we could use rails-dom-testing, or nokogiri directly, as you mentioned.

rails-dom-testing seems suitable :)

The first paragraph of the rails-dom-testing README at https://github.com/rails/rails-dom-testing says that it only works on Rails 4.2 and above. The title of this issue includes Rails 4.0 and 4.1. Does that mean rails-dom-testing is out as an option?

@lcreid Yes, I would prefer to keep 4.0 compatibility if possible, so I guess that means rails-dom-testing is out.

I forked this project to https://github.com/lcreid/rails-bootstrap-forms. I used Nokogiri and equivalent-xml, and all the tests run green for Rails 4.0. It was way too easy, so I fear that I'm doing something wrong. Nevertheless, I'm willing to run with this for a while and see if you like what I'm doing, if you want to assign this issue to me.
I'll push what I've done so far to the explore branch of my project by the end of the evening Pacific Time, today (December 8).

I think equivalent-xml might be a good candidate. I've added it to #278, which tests with multi versions of rails already.

@koenpunt are we duplicating efforts here? What's the difference between #278 and #273 (this one)?

#273 is the issue, #278 is a pull request which I started like 5 months ago. And now that you suggested to use equivalent-xml I added your commit to that branch.

OK. I'm just trying to get an idea of how best I can help. I'll take a look
at your PR later today and see where we're at. Let me know if there are
specific tasks you'd like me to work on.
I haven't done any sort of testing of what I did to make sure the tests go
red when they should. That would be the next thing I would work on, if no
one else is actively working on either #273 or #278.
On Fri, Dec 9, 2016 at 6:48 AM, Koen Punt<EMAIL_ADDRESS>wrote:

#273 https://github.com/bootstrap-ruby/rails-bootstrap-forms/issues/273
is the issue, #278
https://github.com/bootstrap-ruby/rails-bootstrap-forms/pull/278 is a
pull request which I started like 5 months ago. And now that you suggested
to use equivalent-xml I added your commit to that branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bootstrap-ruby/rails-bootstrap-forms/issues/273#issuecomment-266030796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABigMM1Hknq3LZBIX0wA1D_KCuZEDsYpks5rGWosgaJpZM4JEirJ
.

--
Larry Reid
Principal Consultant, Jade Systems Inc
Mobile: +1<PHONE_NUMBER>
technopragmatica.blogspot.com | jadesystems.ca |
tecnopragmatica.blogspot.com

@lcreid As you now can see on #278 is that I'm actually done implementing. But an extra review is always good :)


Use Let's Encrypt for service certs

We currently use a (free) cert from GlobalSign for basically everything.
This is a big problem because:

It has to be manually renewed, yearly.
All services share a single certificate and private key: the IRC servers can impersonate the API or LDAP servers ...
The certificate and keys have to be copied over manually when spinning up new instances.

Because hashbang.sh is listed in the public suffixes list, www.#! still needs the GlobalSign certificate.  However, all other services can (and should) be modified to use Let's Encrypt:

IRC servers

[ ] services.irc.#!
[ ] *.irc.#!
the easiest is probably to use DNS-based validation for those (as the irc.#! domain is shared)

[ ] voip.#! currently uses an invalid certificate; there is no good reason for this.
[ ] What is even the status of the im.#!?
[ ] The AAA server, whether LDAP or the future userdb.
[ ] The mail server
Special care should be taken: the shell servers currently pin the certificate by fingerprint.

We have a hard deadline on this: the current certificate expires in a month (Monday, October 3.)

@hashbang/administrators Looks like nothing exists to simply acquire Let's Encrypt certs based on Docker metadata.
There are things that do this and HTTP(S) reverse proxy, but that's not what we want as the certs are not exposed.

To clarify, we're making a new Docker daemon for the following situation:

The Docker daemon starts a container that runs Let's Encrypt

This container has a mounted volume to store certificates
This container should have port 80 (I think?) available for verification we own the domain

Let's Encrypt, inside the Docker container, obtains a certificate and places them inside the mounted volume
The Let's Encrypt container exits
A service container (IRC, mail, #!, services.irc, etc.) starts up using the certificates as a mounted volume

@ChickenNuggers I'm not making a Docker daemon, and what you described doesn't handle cert renewal.
What I'm currently working on works as follows:

A small container periodically runs an ACME client.
The ACME client keeps certs up-to-date, and calls a custom hook when the certs change.
The hook dispatches a SIGHUP to the container running the matching service whenever the cert is updated.
The certs are kept in a volume that is mounted in the service's container.

There are two main possibilities for the domain validation: HTTP-01 or DNS-01.
We can use HTTP-01 initially, but:

DNS-01 doesn't require exposing the container to the outside;
HTTP-01 cannot easily handle cases like irc.hashbang.sh, where we A (and AAAA) records for several servers.

The whishlist for after v0 is:

using docker-gen to deduce the set of needed containers based on the currently-running containers and their metadata;
exposing one volume per service container, with only the keys of that service;
optionally using something like SoftHSM to expose a PKCS#11 device to the service container (i.e. letting it use the key but never actually exposing the private key).


Could not automatically download and install resource plugin 'pulumi-resource-upstash' at version v0.1.2

Diagnostics:
pulumi:providers:upstash (default_0_1_2_https_/github.com/upstash/pulumi-upstash/releases/download/v__VERSION_):
error: Could not automatically download and install resource plugin 'pulumi-resource-upstash' at version v0.1.2, install the plugin using pulumi plugin install resource upstash v0.1.2 --server https://github.com/upstash/pulumi-upstash/releases/download/v${VERSION}: error downloading provider upstash to file: failed to download plugin: upstash-0.1.2: 404 HTTP error fetching plugin from https://github.com/upstash/pulumi-upstash/releases/download/v${VERSION}/pulumi-resource-upstash-v0.1.2-darwin-amd64.tar.gz

Hello, @zhangpengchen have you tried the command
pulumi plugin install resource upstash v0.1.2 --server https://github.com/upstash/pulumi-upstash/releases/download/v0.1.2

It seems like you didn't change the version variable

@burak-upstash Thanks for the quick reply, the error message was triggered when I am running pulumi up.
If I ran pulumi plugin install resource upstash v0.1.2 --server https://github.com/upstash/pulumi-upstash/releases/download/v0.1.2 then of course there is no issue.

We have identified the issue, with the PR waiting, we will both update the pulumi version and fix this automatically downloading issue.

We have release v0.2.0, closing the issue for now.

Thanks @burak-upstash the new version works great


[FLINK-10055] incorrect in-progress file suffix in BucketingSink's java doc

What is the purpose of the change
Brief change log
Similar to the java doc of setPendingSuffix() and setValidLengthSuffix(), the java doc of setInProgressSuffix() should have a . in The default is {@code ".in-progress"}.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
none
Documentation

Does this pull request introduce a new feature? (no)

+1


Download Story Only?

Currently, you can run the --stories command to download stories alongside the posts. However, with all the 429 errors lately, I figured running for stories often, while running for posts more infrequently would help out.
Is it possible for Instaloader to run for stories only, or is there an existing command that has this? Thank you.

Yes, this is possible.
There is an old (no longer documented but still working) parameter  --stories-only but this is deprecated.
Instead use --stories in combination with --no-posts to exclude posts (introduced in version 4.1)
manual: https://instaloader.github.io/cli-options.html?highlight=posts#cmdoption-no-posts


D3D12Fullscreen is not fullscreen on a WARP device.

Unable to switch to fullscreen mode in a D3D12Fullscreen sample.
I'm using a WARP device (GTX470 is my board if anyone wonders).
m_swapChain->SetFullscreenState(!fullscreenState, nullptr) returns HRESULT 0x887a0004
Debug output is:
DXGI ERROR: IDXGISwapChain::GetContainingOutput: The swapchain's adapter does not control the output on which the swapchain's window resides. [ MISCELLANEOUS ERROR #80: ]
Is this behavior intended?

Yes, this is the intended behavior.  The swap chain must be using the adapter that is plugged into your display in order to do the fullscreen switch.  Unfortunately it appears that your GPU is a Fermi which does not have DX12 drivers so there is no way for you to try this out on your system.

Thank you for your attention!


remove version from docker compose

See #467
Closes #467

Pull Request Test Coverage Report for Build 4f1ea42d-a05f-416e-ae1b-9ee88cf066e4
Details

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

Totals

Change from base Build 47852424-f5f8-4ba1-b8c4-650803d7e5e0:
0.0%

Covered Lines:
3849

Relevant Lines:
4335

💛  - Coveralls

@rtholmes  - I think this is fine? Was there a (very old) reason to pin the version of docker compose?

@winstan I think it was just around pinning versions as much as possible to minimize the chance of variation between courses / terms. But if the field doesn't mean anything anymore it shouldn't matter!


Add timeouts to release artifact generation and the download doxygen step

What's the plan for this PR? Is it still active?

@danieljurek Did you and Wes discuss?  Should this PR be abandoned and closed?

Closing as we have not seen this error for a long time. If it returns we can revisit this. It would be nicer to use an approach to the timeouts based on average step and job running times.


Disable pointer events when button is disabled

Disable pointer events when <mwc-button> is disabled.
Approach copied from how Polymer implements similar functionality: https://github.com/PolymerElements/iron-behaviors/blob/master/iron-control-state.js#L76-L95
Fixes #148

@balloob Thanks!


2ds freezes when trying to go to http://dukesrg.github.io/2xrsa.html?arm11.bin

Everything succeeded up to this part:
Section III - Getting the OTP
go to http://dukesrg.github.io/2xrsa.html?arm11.bin on 3ds.
What is causing it to freeze? Thanks in advance!  Just fiddly, not a real issue.


Default plugins - Admin

Default plugins will be loaded internally not externally like other plugins.
We can also add the graph view in an extra tab.


Azure.Identity simplify exception messaging

Error messaging from authentication failures in Azure.Identity is in many cases too verbose. Nested exceptions and AggregateExceptions lead to duplicated information, and superfluous information being inserted into exception strings. This can often obscure the actual cause of the exception. This is especially true in error messages from the DefaultAzureCredential.
This change simplifies exception messaging across the library and removes the use of AggregateException as the inner exception of failures from the DefaultAzureCredential. Below are two examples of how this simplifies the exception messaging from the DefaultAzureCredential.
DefaultAzureCredential when no credentials are available
Without this update
// Message

The DefaultAzureCredential failed to retrieve a token from the included credentials.
  EnvironmentCredential is unavailable Environment variables not fully configured. AZURE_TENANT_ID and AZURE_CLIENT_ID must be set, along with either AZURE_CLIENT_SECRET or AZURE_USERNAME and AZURE_PASSWORD. Alternately, AZURE_AUTH_LOCATION ca be set.  Currently set variables [ AZURE_CLIENT_ID AZURE_CLIENT_SECRET ].
  ManagedIdentityCredential is unavailable No managed identity endpoint found..
  SharedTokenCacheCredential is unavailable No accounts were found in thecache.  To authenticate with the SharedTokenCacheCredential, login an account through developer tooling supporting Azure single sign on..
See inner exception for more detail.

// ToString

Azure.Identity.AuthenticationFailedException: The DefaultAzureCredential failed to retrieve a token from the included credentials.
  EnvironmentCredential is unavailable Environment variables not fully configured. AZURE_TENANT_ID and AZURE_CLIENT_ID must be set, along with either AZURE_CLIENT_SECRET or AZURE_USERNAME and AZURE_PASSWORD. Alternately, AZURE_AUTH_LOCATION ca be set.  Currently set variables [ AZURE_CLIENT_ID AZURE_CLIENT_SECRET ].
  ManagedIdentityCredential is unavailable No managed identity endpoint found..
  SharedTokenCacheCredential is unavailable No accounts were found in thecache.  To authenticate with the SharedTokenCacheCredential, login an account through developer tooling supporting Azure single sign on..
See inner exception for more detail. ---> System.AggregateException: The DefaultAzureCredential failed to retrieve a token from the included credentials. (Environment variables not fully configured. AZURE_TENANT_ID and AZURE_CLIENT_ID must be set, along with either AZURE_CLIENT_SECRET or AZURE_USERNAME and AZURE_PASSWORD. Alternately, AZURE_AUTH_LOCATION ca be set.  Currently set variables [ AZURE_CLIENT_ID AZURE_CLIENT_SECRET ]) (No managed identity endpoint found.) (No accounts were found in thecache.  To authenticate with the SharedTokenCacheCredential, login an account through developer tooling supporting Azure single sign on.) ---> Azure.Identity.CredentialUnavailableException: Environment variables not fully configured. AZURE_TENANT_ID and AZURE_CLIENT_ID must be set, along with either AZURE_CLIENT_SECRET or AZURE_USERNAME and AZURE_PASSWORD. Alternately, AZURE_AUTH_LOCATION ca be set.  Currently set variables [ AZURE_CLIENT_ID AZURE_CLIENT_SECRET ]
  --- End of inner exception stack trace ---
  --- End of inner exception stack trace ---
  at Azure.Identity.DefaultAzureCredential.GetTokenAsync(Boolean isAsync, TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 122
  at Azure.Identity.DefaultAzureCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 90
  at Azure.Identity.Tests.DefaultAzureCredentialTests.<>c__DisplayClass8_0.<<ValidateEnvironmentCredentialUnhandledException>b__0>d.MoveNext() in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\tests\DefaultAzureCredentialTests.cs:line 351
--- End of stack trace from previous location where exception was thrown ---
  at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted() in D:\a\1\s\src\NUnitFramework\framework\Internal\TaskAwaitAdapter.cs:line 95
  at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke) in D:\a\1\s\src\NUnitFramework\framework\Internal\AsyncToSyncAdapter.cs:line 60
  at NUnit.Framework.Assert.ThrowsAsync(IResolveConstraint expression, AsyncTestDelegate code, String message, Object[] args) in D:\a\1\s\src\NUnitFramework\framework\Assert.Exceptions.Async.cs:line 48

With this update
//Message

DefaultAzureCredential failed to retrieve a token from the included credentials. ( EnvironmentCredential authentication unavailable, environment variables are not fully configured. ManagedIdentityCredential not available, no managed identity endpoint found. SharedTokenCacheCredential authentication unavailable, no accounts were found in the cache. )

// ToString

Azure.Identity.CredentialUnavailableException: DefaultAzureCredential failed to retrieve a token from the included credentials. ( EnvironmentCredential authentication unavailable, environment variables are not fully configured. ManagedIdentityCredential not available, no managed identity endpoint found. SharedTokenCacheCredential authentication unavailable, no accounts were found in the cache. )
   at Azure.Identity.DefaultAzureCredential.GetTokenAsync(Boolean isAsync, TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 127
   at Azure.Identity.DefaultAzureCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 90
   at Azure.Identity.Tests.DefaultAzureCredentialTests.<>c__DisplayClass8_0.<<ValidateEnvironmentCredentialUnhandledException>b__0>d.MoveNext() in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\tests\DefaultAzureCredentialTests.cs:line 351
--- End of stack trace from previous location where exception was thrown ---
   at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted() in D:\a\1\s\src\NUnitFramework\framework\Internal\TaskAwaitAdapter.cs:line 95
   at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke) in D:\a\1\s\src\NUnitFramework\framework\Internal\AsyncToSyncAdapter.cs:line 60
   at NUnit.Framework.Assert.ThrowsAsync(IResolveConstraint expression, AsyncTestDelegate code, String message, Object[] args) in D:\a\1\s\src\NUnitFramework\framework\Assert.Exceptions.Async.cs:line 48

DefaultAzureCredential when authentication fails
Without this update
// Message

The DefaultAzureCredential failed due to an unhandled exception:  EnvironmentCredential failed with unhandled exception The authentication request failed due to an unhandled exception.  See inner exception for details..
  EnvironmentCredential failed with The authentication request failed due to an unhandled exception.  See inner exception for details..
See inner exception for more detail.

// ToString

    Azure.Identity.AuthenticationFailedException: The DefaultAzureCredential failed due to an unhandled exception:  EnvironmentCredential failed with unhandled exception The authentication request failed due to an unhandled exception.  See inner exception for details..
  EnvironmentCredential failed with The authentication request failed due to an unhandled exception.  See inner exception for details..
See inner exception for more detail. ---> System.AggregateException: The DefaultAzureCredential failed due to an unhandled exception:  EnvironmentCredential failed with unhandled exception The authentication request failed due to an unhandled exception.  See inner exception for details.. (The authentication request failed due to an unhandled exception.  See inner exception for details.) ---> Azure.Identity.AuthenticationFailedException: The authentication request failed due to an unhandled exception.  See inner exception for details. ---> Azure.RequestFailedException: Service request failed.
Status: 400 (Bad Request)

Content:
{"error":"unauthorized_client","error_description":"AADSTS700016: Application with identifier 'c0f6fc62-8bf3-449c-afc5-06f074e52af2' was not found in the directory 'a7fc734e-9961-43ce-b4de-21b8b38403ba'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.\r\nTrace ID: 88bac1cd-156e-44cb-8aee-7de442711300\r\nCorrelation ID: 3e26d973-b3cc-43bc-85f3-e9014aa6743b\r\nTimestamp: 2020-02-06 01:03:43Z","error_codes":[700016],"timestamp":"2020-02-06 01:03:43Z","trace_id":"88bac1cd-156e-44cb-8aee-7de442711300","correlation_id":"3e26d973-b3cc-43bc-85f3-e9014aa6743b","error_uri":"https://login.microsoftonline.com/error?code=700016"}

Headers:
Cache-Control: no-store, no-cache
Pragma: no-cache
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
x-ms-request-id: REDACTED
x-ms-ests-server: REDACTED
P3P: REDACTED
Set-Cookie: REDACTED
Date: Thu, 06 Feb 2020 01:03:43 GMT
Content-Type: application/json; charset=utf-8
Expires: -1
Content-Length: 779

  at Azure.Identity.AadIdentityClient.SendAuthRequestAsync(Request request, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\AadIdentityClient.cs:line 72
  at Azure.Identity.AadIdentityClient.AuthenticateAsync(String tenantId, String clientId, String clientSecret, String[] scopes, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\AadIdentityClient.cs:line 37
  at Azure.Identity.ClientSecretCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\ClientSecretCredential.cs:line 96
  --- End of inner exception stack trace ---
  at Azure.Identity.ClientSecretCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\ClientSecretCredential.cs:line 106
  at Azure.Identity.EnvironmentCredential.GetTokenImplAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\EnvironmentCredential.cs:line 209
  --- End of inner exception stack trace ---
  --- End of inner exception stack trace ---
  at Azure.Identity.DefaultAzureCredential.GetTokenAsync(Boolean isAsync, TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 120
  at Azure.Identity.DefaultAzureCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 90
  at Azure.Identity.Tests.DefaultAzureCredentialTests.<>c__DisplayClass8_0.<<ValidateEnvironmentCredentialUnhandledException>b__0>d.MoveNext() in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\tests\DefaultAzureCredentialTests.cs:line 351
--- End of stack trace from previous location where exception was thrown ---
  at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted() in D:\a\1\s\src\NUnitFramework\framework\Internal\TaskAwaitAdapter.cs:line 95
  at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke) in D:\a\1\s\src\NUnitFramework\framework\Internal\AsyncToSyncAdapter.cs:line 60
  at NUnit.Framework.Assert.ThrowsAsync(IResolveConstraint expression, AsyncTestDelegate code, String message, Object[] args) in D:\a\1\s\src\NUnitFramework\framework\Assert.Exceptions.Async.cs:line 48

With this update
// Message

DefaultAzureCredential authentication failed.

// ToString

Azure.Identity.AuthenticationFailedException: DefaultAzureCredential authentication failed. ---> Azure.Identity.AuthenticationFailedException: ClientSecretCredential authentication failed. ---> Azure.RequestFailedException: Service request failed.
Status: 400 (Bad Request)

Content:
{"error":"unauthorized_client","error_description":"AADSTS700016: Application with identifier '78e8f606-0950-4210-906d-1d321511c09d' was not found in the directory 'a7fc734e-9961-43ce-b4de-21b8b38403ba'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.\r\nTrace ID: 9f3624a7-49ca-4097-a339-780fd4e41600\r\nCorrelation ID: b1acfa40-06cc-42a1-a2f1-d35b94db3628\r\nTimestamp: 2020-02-06 01:13:33Z","error_codes":[700016],"timestamp":"2020-02-06 01:13:33Z","trace_id":"9f3624a7-49ca-4097-a339-780fd4e41600","correlation_id":"b1acfa40-06cc-42a1-a2f1-d35b94db3628","error_uri":"https://login.microsoftonline.com/error?code=700016"}

Headers:
Cache-Control: no-store, no-cache
Pragma: no-cache
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
x-ms-request-id: REDACTED
x-ms-ests-server: REDACTED
P3P: REDACTED
Set-Cookie: REDACTED
Date: Thu, 06 Feb 2020 01:13:33 GMT
Content-Type: application/json; charset=utf-8
Expires: -1
Content-Length: 779

  at Azure.Identity.AadIdentityClient.SendAuthRequestAsync(Request request, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\AadIdentityClient.cs:line 72
  at Azure.Identity.AadIdentityClient.AuthenticateAsync(String tenantId, String clientId, String clientSecret, String[] scopes, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\AadIdentityClient.cs:line 37
  at Azure.Identity.ClientSecretCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\ClientSecretCredential.cs:line 96
  --- End of inner exception stack trace ---
  at Azure.Identity.ClientSecretCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\ClientSecretCredential.cs:line 106
  at Azure.Identity.EnvironmentCredential.GetTokenImplAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\EnvironmentCredential.cs:line 172
  --- End of inner exception stack trace ---
  at Azure.Identity.DefaultAzureCredential.GetTokenAsync(Boolean isAsync, TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 118
  at Azure.Identity.DefaultAzureCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken) in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\src\DefaultAzureCredential.cs:line 90
  at Azure.Identity.Tests.DefaultAzureCredentialTests.<>c__DisplayClass8_0.<<ValidateEnvironmentCredentialUnhandledException>b__0>d.MoveNext() in d:\azure-sdk-for-net\sdk\identity\Azure.Identity\tests\DefaultAzureCredentialTests.cs:line 351
--- End of stack trace from previous location where exception was thrown ---
  at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted() in D:\a\1\s\src\NUnitFramework\framework\Internal\TaskAwaitAdapter.cs:line 95
  at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke) in D:\a\1\s\src\NUnitFramework\framework\Internal\AsyncToSyncAdapter.cs:line 60
  at NUnit.Framework.Assert.ThrowsAsync(IResolveConstraint expression, AsyncTestDelegate code, String message, Object[] args) in D:\a\1\s\src\NUnitFramework\framework\Assert.Exceptions.Async.cs:line 48

DefaultAzureCredential failed to retrieve a token from the included credentials. ( EnvironmentCredential authentication unavailable, environment variables are not fully configured. ManagedIdentityCredential not available, no managed identity endpoint found. SharedTokenCacheCredential authentication unavailable, no accounts were found in the cache. )

For me this is rather hard to read as a single line, I liked when messages were on separate lines
.

DefaultAzureCredential authentication failed.

Should we try and concatenate messages here?


Document the limitations of c3

C3 looks much easier to use than D3, but I'd like to know what that costs me. I don't see any explanation of C3's limitations on its website. It would also be nice to know in what ways C3 can interoperate with D3. Is it possible to create a C3 chart and then manipulate it with D3 in cases when C3's limitations arise?

Hi @fresheneesz!
You can most definitely manipulate C3 charts with D3; they're all just SVG elements. For instance, in AxisJS, I add titles after chart generation using D3. You can sort of use D3 to tweak things much like how you would use jQuery on the normal DOM (Technically, you could tweak the SVG with even jQuery, but I've always found D3 to work much better due to not having to dodge around issues caused by the SVG namespace.).
That said, IIRC (and it is pretty late here at the moment), C3's pretty much in its own scope, so it's not likely you can pass C3's scope to D3 and then have that take over a created chart. Further, any manipulations you do to the chart elements may get overwritten if you call .generate() again. I might be totally wrong about this though; @masayuki0812, any thoughts?
TBH, I generally find it easier to use CSS to modify C3 charts. Pretty much every element has a class attached, so they're really easy to tweak stylistically. I've even had some success replacing the requestAnimationFrame-based animations with CSS transitions (See #774).
In terms of general limitations — it's not very extensible at the moment (though we are working on a plugin architecture; see #351), so you're pretty much limited to pie/donut/line/bar/gauge charts currently. But that's kind of what it's for — comparing C3 to D3 is sort of apples-to-oranges; the latter is a library for attaching data to SVG elements, the former is a simplified abstraction of that library. I use both in my daily work — D3 when I want to create some weird new type of data visualisation, C3 for when I need to knock out an interactive bar chart in under five minutes. Given this, what might be a limitation in one context is a benefit in another.
Thoughts?

Thanks for the detailed response Ændrew. I guess for our case, I don't want to reinvent the wheel if I don't have to. So I guess the answer just might be to use c3 in one case and d3 in another. I'm also looking at Dimple and NVD3, which both advertise the ability to be used together with D3. I'm trying to evaluate what is right for us - and it would be much easier to do that if I know I can drop back down to the D3 level without starting from scratch. It sounds like that's essentially possible with any library that uses D3 (or any library that generates SVG?). So now I think we'll just have to decide which abstraction layer we like better out of C3, Dimple, and NVD3 and go with that.
As far as this ticket, I just want to reitterate that it would be nice to have some exposition about this in the docs. Thanks again!

@fresheneesz If it helps — NVD3 is a lot less abstracted than C3, in that it gives you models that you populate. It's like D3-Lite in many ways, IMO. Hadn't heard of Dimple before, but it looks similar to NVD3 in that regard.
I'm going to rename this to be a documentation issue — what's really needed is a wiki page with a table discussing the differences.

please throw in a compass chart a-la http://www.java2s.com/Code/Java/Chart/JFreeChartCompassDemo2.htm while youre at it :)

Hello Aendrew, I would like to understand  advantages and disadvantages between c3 and NVD3, I need to take a decision.

@rajzeshwars http://www.jsgraphs.com/

Thanks alan. It is a nice link. Is there a way to compare between c3 and NDv3?


[git] Migrate git method from Ruby to Python

With this PR all method are now handled with Python script. This is one more step to easily changing the releases JSON schema.
The Ruby code was kept as is so we can roll back to it if needed.

Checked by removing all releases JSON file, they were recreated without any noticeable modification.

Relaunch a last time without any cache before merging.

@captn3m0 FYI


add std.string.soundexer

Added soundexer() to replace soundex(). (soundex() is retained for backwards compatibility, but is rewritten as a wrapper around soundexer().)
soundexer():

accepts ranges as input
does not allocate memory
returns a static array that fits into a register, thus is efficient

This makes soundexer() into a more modern style 'reduce' algorithm.

lgtm after fixing the template constraint - thanks!

Auto-merge toggled on

nice, thx!


Min P generation parameter

Feature request
Hey! I've noticed that min_p parameter is now available in transformers but haven't found it in TGI. Are you planning to add it in the nearest future?
The parameter itself is very well described here
I have implemented it in TGI for myself locally and I would be glad to contribute by submitting a PR  :)

@avacaondata
so basically you need to add MinPLogitsWarper to /server/text_generation_server/utils/logits_process.py and the min_p parameter to NextTokenChooser class in /server/text_generation_server/utils/tokens.py
Then go over a ton of files and add the min_p parameter wherever needed. Here I would suggest you searching for one of the existing generation params like top_p and adding the missing lines of code for the new parameter min_p
After you done that, just build the image with the default Dockerfile and use it as you usually do
If you have any further questions, feel free to ask :)


posts is not iterable error

A build is getting the following error:
posts is not iterable
    /opt/build/repo/node_modules/netlify-plugin-ghost-markdown/index.js:100:9 onPreBuild
    internal/process/next_tick.js:68:7 process._tickCallback

It seems this would indicate that ghostContentApi.posts() return value is not always an array.

I think that might have just been me using the plugin wrong. Thanks thought 😅

@ehmicky thanks for the error reports! Keep an eye out as I just published a new version with my and your updates. I had to remove the default items in the manifest as they were erroring when I used netlify build

Thanks for fixing it! I actually saw it and marked those errors as solved :)
I will be notified if it was to be triggered again (but I think it won't) and will forward it.
For the netlify build error: this might be due to the @netlify/cli version you are using. The latest version might solve this problem.

I updated the CLI before starting this stuff so not sure why it was happening :/


Fix pixel neighbour definition for curved focal planes (with rectangular pixels)

As demonstrated in #963, the current definition of pixel neighbours is not robust for cameras with curved focal planes. This is because pixel separation changes with distance from the camera centre.
As the CTA cameras with curved focal planes are also the cameras with pixels aligned on a rectangular grid, this PR will address this issue by defining the neighbours based on the row and columns of the pixels instead of the coordinates.

I don't understand why the histogram approach does not exhibit the same problem as the radius approach. Both should suffer in the same way from changing pixel separations on a curved plain.
Maybe it's time to generalize CameraGeometry, maybe even subclass it to a FlatCameraGeometry and a CurvedCameraGeometry.
All the information necessary is contained in the simtel files and is available in the SimTelFile of the SimTelEventSource.

I don't understand why the histogram approach does not exhibit the same problem as the radius approach. Both should suffer in the same way from changing pixel separations on a curved plain.

It absolutely could for extreme curvatures, but there is more leeway with the histogram binnings, whereas the neighbour definition defines a single threshold.

Maybe it's time to generalize CameraGeometry, maybe even subclass it to a FlatCameraGeometry and a CurvedCameraGeometry.

I think this could be nice.
This was more intended as a quick, simple fix for a problem I identified, without too much overhaul of the geometry class. An improvement on the current way it's done.

I think I found a better solutiion using the kdtree, that is even more general.
I'll open another PR.

Can you explain the approach here? Why is it necessary to call histogram2d multiple times with weights and so on?

I bin the pixel positions onto a square grid. The bins of the square grid needs to be small enough so each pixel has its own bin, but not too small such that the change of the y (or x) pixel coordinate across a single row (or column) due to the focal plane curvature does not result in mistakingly assigning the pixel to a different row (or column).
Because of the module gaps, this will result in some empty bins, which should not be counted as its own row. This is the reason for the second pair of calls for histogram2d.
This part could probably be done better. The aim of this segment of code is to obtain an array of x coordinates for a row that fully spans the camera, and the an array of y coordinates for a column that fully spans the camera.

See my other approach in #1015

Doesn't this mean perhaps we should store the curved pixel positions in another coordinate system, so that their distances are not changing?

for instance the angular distance between pixels I guess doesn't change? or is it just the inter-module distances that change, and each module is a plane? I don't know enough about how the focal plane on those cameras is physically implemented.

Probably we need better documentation somewhere describing the curved planes

simtel files contain u v information for those pixels. I think Everythong we need to know is there.

contain z and angle

That's good to know - I though it was only z, which isn't enough.  However that means they are not stored as I thought they were (e.g. X-Y position on the focal plane, which might be curved), rather they are X-Y in real space, not accounting for the curvature.  To be certain, we should look in read_cta in simtelarray to see how the analysis is done there - I would have assumed they were in a system that makes the analysis the same for curved and flat planes, but if all coordinates are given, that may not be the case and a correction might be necessary.

I will close this PR as #1015 was merged.
Discussion of curved focal plane handling has continued in #1018.


Previous and next document

I'm wondering how best to add information about the previous and next post. I wanted to do it in the transform() function, but TypeScript throws errors when I try to return any retrieved document.
I have this code:
transform: async (document, context) => {
    const mdx = await compileMDX(context, document);

    const previous = context.documents(docs).find(() => {
      // find previous
      return true;
    });

    return {
      ...document,
      mdx,
      previous,
    };
},

The error is: transform implicitly has return type any because it does not have a return type annotation and is referenced directly or indirectly in one of its return expressions.
I'm not sure if it's a good idea to do this in the transform() function. Any ideas on how to do it properly to add information about the previous and next post?

Hi @Kuzry it is not possible to access the documents of a collection with in the transform function of the same collection.
The simplest thing which comes to my mind to implement previous/next is to do this in you application code. First you have to sort your collection, the you can search the index of the current document and calculate the next and the previous doc.
const index = sortedDocs.findIndex((doc) =>  doc._meta.path === currentDoc._meta.path);
const previous = sortedDocs[index - 1];
const next =  sortedDocs[index + 1];