WassersteinGAN triaining CelebA problem:MemoryError

when I run : python main.py --backend tensorflow --generator deconv --dset celebA --lr_G 1E-3 --lr_D 1E-3 --clamp_lower -0.5 --clamp_upper 0.5 --batch_size 512 --noise_dim 128
It traceback:
Traceback (most recent call last):
  File "main.py", line 85, in <module>
    launch_training(**d_params)
  File "main.py", line 11, in launch_training
    train_WGAN.train(**kwargs)
  File "/mnt/data1/daniel/codes/GAN/DeepLearningImplementations/WassersteinGAN/src/model/train_WGAN.py", line 47, in train
    X_real_train = data_utils.load_image_dataset(dset, img_dim, image_dim_ordering)
  File "../utils/data_utils.py", line 94, in load_image_dataset
    X_real_train = load_celebA(img_dim, image_dim_ordering)
  File "../utils/data_utils.py", line 83, in load_celebA
    X_real_train = normalization(X_real_train, image_dim_ordering)
  File "../utils/data_utils.py", line 16, in normalization
    X = (X - 0.5) / 0.5
MemoryError

Anybody help?

@tdeboissiere

Looks like you're short on RAM. In the load image dataset, you may choose to load only a fraction of the dataset in memory.
In the Colorful folder, there is code to load data on the fly. This removes the RAM limitation at the cost of slower training.

@tdeboissiere which code and how to use it?

In the README there : https://github.com/tdeboissiere/DeepLearningImplementations/tree/master/Colorful/src/model, you'll find the "training_mode" command line argument. From there you can trace back the code to load on the fly.


azure-functions-maven-plugin:1.9.0:package fails with NullPointerException

Plugin name and version

Plugin: azure-functions-maven-plugin:1.9.0
Maven version: Apache Maven 3.6.3

Plugin configuration in your pom.xml
Generated with maven archetype.
<plugin>
    <groupId>com.microsoft.azure</groupId>
    <artifactId>azure-functions-maven-plugin</artifactId>
    <version>${azure.functions.maven.plugin.version}</version>
    <configuration>
        <appName>${functionAppName}</appName>
        <resourceGroup>java-functions-group</resourceGroup>
        <appServicePlanName>java-functions-app-service-plan</appServicePlanName>
        <region>westus</region>
        <runtime>
            <os>linux</os>
            <javaVersion>11</javaVersion>
        </runtime>
        <appSettings>
            <property>
                <name>FUNCTIONS_EXTENSION_VERSION</name>
                <value>~3</value>
            </property>
        </appSettings>
    </configuration>
    <executions>
        <execution>
            <id>package-functions</id>
            <goals>
                <goal>package</goal>
            </goals>
        </execution>
    </executions>
</plugin>

Expected behavior
mvn azure-functions:package should package the function.
Actual behavior
Build fails with NullPointerException.
[ERROR] Failed to execute goal com.microsoft.azure:azure-functions-maven-plugin:1.9.0:package (default-cli) on project test: java.lang.NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.microsoft.azure:azure-functions-maven-plugin:1.9.0:package (default-cli) on project test: java.lang.NullPointerException
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    ....
Caused by: java.lang.NullPointerException
    at java.util.zip.ZipFile.<init> (ZipFile.java:233)
    at java.util.zip.ZipFile.<init> (ZipFile.java:177)
    at java.util.jar.JarFile.<init> (JarFile.java:348)
    at java.util.jar.JarFile.<init> (JarFile.java:319)
    at java.util.jar.JarFile.<init> (JarFile.java:285)
    at com.microsoft.azure.common.Utils.getArtifactCompileVersion (Utils.java:30)
    at com.microsoft.azure.maven.function.PackageMojo.promptCompileInfo (PackageMojo.java:378)
    at com.microsoft.azure.maven.function.PackageMojo.doExecute (PackageMojo.java:98)
    at com.microsoft.azure.maven.AbstractAzureMojo.execute (AbstractAzureMojo.java:448)
    ....

Steps to reproduce the problem

Create new project with maven archetype using default settings:
mvn archetype:generate -DarchetypeGroupId=com.microsoft.azure -DarchetypeArtifactId=azure-functions-archetype -DjavaVersion=11
Build the project: mvn clean package
Attempt to package the function: mvn azure-functions:package

Workaround
Downgrade azure-functions-maven-plugin to version 1.6.0

@EspenSchei Thanks for your report, I'm investigating this issue and will update here once there are updates

@EspenSchei Thanks for your report, I'm investigating this issue and will update here once there are updates

@Flanker32 I'm having the same issue with plugin version 1.9.2 -> the PR is merged, but the ticket is still opened, does this mean this isn't released yet? It's a blocker issue to package an Azure Function that you want to deploy using the Azure Functions GitHub Action (not using the plugin to deploy)

Having the same problem on 1.9.2

@itsandreramon the PR is merged, but I talked to the team and it’s not released yet.

@jdubois As mentioned in the issue description we have not experienced any problems  downgrading to 1.6.0 until the fix is released and deploy using the Azure Functions GitHub Action regularly.
Also if I understand the fix correctly I think the current version would work if you bind the the execution to maven's package lifecycle phase rather than running it separately, but I've not had the time or motivation to test out this theory.

Yes I confirm v1.6.0 works, but I wouldn’t recommend using it (for reasons I can’t detail publicly, unfortunately)

@jdubois @itsandreramon @sharebear Thank you al for your support. I'm sorry but the fixes is still not released, as a workaround, please use mvn package if you want to package the function,  I'll update here once the fix is released.

@jdubois @itsandreramon @sharebear Thanks again for your help, functions maven plugin 1.10.0 has been released with fix for this issue.


Create Snake Game Using Java

Thanks for your contribution🎉!
do share this repo with your friends also , i think you forget to add contributorList which is mention in the readme.md file please go through once follow the same for quick PR merge & if you like this repo give a star 🌟 to show your support it means a lot!


Update to work with latest Godot 4.0

These are the minimal changes to make the module compile with the latest Godot 4.0.
Feedback and testing is welcome.
I noticed that Godot replaced the HashMap implementation, and godot_box2d at some points depends on the ordering of elements in a HashMap; I don't know if this requires any changes on the godot_box2d side.

I cherry-picked all the later changes from the 3.x branch, so after some testing this should be good to merge.


Direct mode doesn't work with mobile Nvidia GPUs

Hello,
Direct mode feature doesn't work with Nvidia mobile GPUs using driver version upper to 367 series. It's a known issue reported in the documentation.
Oculus, OpenVR as well as Windows MR have working direct mode with those GPU with latest drivers. Maybe drivers have changed or have a new API to make it work again?

Are you trying to report the fact that it is still not working and ask for it to be fixed, or are you asking whether it may already be working on later drivers?
The DK2 and OSVR HDK are working on my laptop with a 2080 and a built-in Intel card, so unless you're having trouble on another machine I think I'll just remove the compatibility warning.

Hello,
Well I can't get dirtect mode to work on my laptop (which has an intel + nvidia 1060 6G). I searched on the docs and it's indicated that since drivers 367 it doens't work anymore, unless you disable the other GPU. I don't want to report the issue because it's an already known issue. However, I ask if it can be fixed because direct mode works with other VR vendors.
I tried to use the latest OSVR AIO installer + update the OSVR core with the latest version available [from here] and it's still not working.
I use a HDK 1.3 which has the latest firmware (2.0). So the question is, if it's not a bug on my side, do you think it can be fixed? Or if it's already fixed, how can I fix my computer to have direct mode ;)
Thanks.

I'll check next week when I get home and see if my HDK 2.0 works on the latest driver on a 1080 card in a laptop with the current OSVR source build against the latest nVidia VRWorks API.

Thanks. Is RenderManager logs something is direct mode fails to start?

Yes  Posting the program's output to the command line could help debug the issue.  There is also a DirectModeDebugging program that tries to make sure that the device can be recognized as a DirectMode-compatible device.

I'll post all log tomorrown, thanks!

I was able to get the HDK 2.0 running in DirectMode on an Alienware laptop with a GeForce 1080 and the built-in Intel graphics using the HDMI port.  This was running with osvrRenderManager.dll that was built against the latest VRWorks SDK.
I was also able to get it to run using a DLL made back in 2016.
It looks like the newer drivers are making things work for the HDK2.0.  It may be that the version 1.3 HDK did not have HDCP support, which I think is why nVidia removed support from these devices.  In that case, I don't know that there is anything we can do about it at this point.

Ok thanks


nodejs OAuthPrompt : No reply address is registered for the application

Versions
What package version of the SDK are you using. v4
What nodejs version are you using v8.12.0
What browser version are you using edge
What os are you using win10
Describe the bug
OAuthPrompt doesn't seem to handle the return url correctly

To Reproduce
Steps to reproduce the behavior:

Clone https://github.com/Microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/24.bot-authentication-msgraph
Create the AADV2 token and configure the OAuth on bot as per documentation instruction
Test in emulator

I'm not entirely sure whether I made a wrong step here, but I kept on getting the "No Reply Address is registered for the application". Or do I need to create a restify endpoint to handle the oauthcallback? Any guidance on this would be much appreciated.
Thanks

In your AAD app did you put in a reply url?

@jwiley84 for awareness

@JasonSowers its working fine on AADV1, I haven't checked V2 yet again.


feat: Added API to findAll documents

Codecov Report

Merging #47 (e5ec885) into main (8ce549c) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   94.57%   94.57%   -0.01%
==========================================
  Files           7        7
  Lines        1512     1530      +18
  Branches      223      227       +4
==========================================
+ Hits         1430     1447      +17
  Misses         81       81
- Partials        1        2       +1

Impacted Files
Coverage Δ

src/collection.ts
92.62% <100.00%> (+0.24%)
:arrow_up:

src/types.ts
94.44% <100.00%> (+0.01%)
:arrow_up:

src/utility.ts
98.49% <100.00%> (-0.29%)
:arrow_down:

Continue to review full report at Codecov.

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


nats-cluster pod Init:CrashLoopBackoff

Greetings!
I've recently upgraded my AKS Cluster(to 1.16.9) and after that the nats cluster pod is in state Init:CrashLoopBackOff.
I've installed the operator following your guide.
nats-cluster.yaml
apiVersion: nats.io/v1alpha2
kind: NatsCluster
metadata:
  name: platta-nats-cluster
spec:
  size: 2
  version: "1.3.0"

  pod:
    enableConfigReload: true
    enableClientsHostPort: true
    advertiseExternalIP: true

nats-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nats-operator
  # Change to the name of the namespace where to install NATS Operator.
  # Alternatively, change to "nats-io" to perform a cluster-scoped deployment in supported versions.
  namespace: nats-io
spec:
  replicas: 1
  selector:
    matchLabels:
      name: nats-operator
  template:
    metadata:
      labels:
        name: nats-operator
    spec:
      serviceAccountName: nats-operator
      containers:
      - name: nats-operator
        image: connecteverything/nats-operator:0.7.2
        imagePullPolicy: IfNotPresent
        args:
        - nats-operator
        # Uncomment to perform a cluster-scoped deployment in supported versions.
        - --feature-gates=ClusterScoped=true
        ports:
        - name: readyz
          containerPort: 8080
        env:
        - name: MY_POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: MY_POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        readinessProbe:
          httpGet:
            path: /readyz
            port: readyz
          initialDelaySeconds: 15
          timeoutSeconds: 3

Operator is running with no events.
Latest events from default namespace:
47m         Warning   BackOff                  pod/platta-nats-cluster-1            Back-off restarting failed container
<unknown>   Normal    Scheduled                pod/platta-nats-cluster-1            Successfully assigned default/platta-nats-cluster-1 to aks-nodepool1-87507524-vmss000002
41m         Normal    Pulled                   pod/platta-nats-cluster-1            Container image "connecteverything/nats-boot-config:0.5.2" already present on machine
41m         Normal    Created                  pod/platta-nats-cluster-1            Created container bootconfig
41m         Normal    Started                  pod/platta-nats-cluster-1            Started container bootconfig
12m         Warning   BackOff                  pod/platta-nats-cluster-1            Back-off restarting failed container
<unknown>   Normal    Scheduled                pod/platta-nats-cluster-1            Successfully assigned default/platta-nats-cluster-1 to aks-nodepool1-87507524-vmss000000
5m10s       Normal    Pulled                   pod/platta-nats-cluster-1            Container image "connecteverything/nats-boot-config:0.5.2" already present on machine
5m10s       Normal    Created                  pod/platta-nats-cluster-1            Created container bootconfig
5m10s       Normal    Started                  pod/platta-nats-cluster-1            Started container bootconfig
89s         Warning   BackOff                  pod/platta-nats-cluster-1            Back-off restarting failed container
43m         Warning   FailedToUpdateEndpoint   endpoints/platta-nats-cluster-mgmt   Failed to update endpoint default/platta-nats-cluster-mgmt: Operation cannot be fulfilled on endpoints "platta-nats-cluster-mgmt": StorageError: invalid object, Code: 4, Key: /registry/services/endpoints/default/platta-nats-cluster-mgmt, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 1d9deebd-e17a-4aa8-886e-26fbd68aac14, UID in object meta:
43m         Warning   FailedToUpdateEndpoint   endpoints/platta-nats-cluster        Failed to update endpoint default/platta-nats-cluster: Operation cannot be fulfilled on endpoints "platta-nats-cluster": StorageError: invalid object, Code: 4, Key: /registry/services/endpoints/default/platta-nats-cluster, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 8c825e0f-3f0b-4dc8-9d9d-6e9457943ee5, UID in object meta:

latest log lines from operator pod from namespace nats-io:
ime="2020-07-14T08:30:08Z" level=info msg="skipping reconciliation as there are 1 waiting pods ([platta-nats-cluster-1])" cluster-name=platta-nats-cluster namespace=default pkg=cluster

I have no idea what you guys need to solve out some problems so please let me know what I can provide you :)

For now, we decided to change back to normal clustering and skip the operator part. Will be messaging again once we try again and if it fails.


Persist redux state across refresh

Following this stackoverflow thread, we should probably use one of redux-persist or redux-storage.

This is somehow linked to https://github.com/luxons/seven-wonders/issues/10

This should be done after we are done with the definition of the state tree.
Persisting a changing tree will just burden us while we develop.

Refreshing actually closes the websocket connection with the server.
What we need is proper support for reconnection rather than client-side state storage.
Closing in favor of https://github.com/joffrey-bion/seven-wonders/issues/10


Add labelPosition to md-slide-toggle

Bug, feature request, or proposal:
Just as <md-checkbox> has labelPosition, I propose that the same property should be added to md-slide-toggle
What is the expected behavior?
When adding:
<md-slide-toggle labelPosition="before">Available Offline</md-slide-toggle>
The label would be before the toggle.
What is the current behavior?
The label-position does nothing, as it is not implamented.
What are the steps to reproduce?
Add above code into file. See the following:
http://plnkr.co/edit/8Z2V2T16tmMoIvY9np4t
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
What is the use-case or motivation for changing an existing behavior?
In order to provide more functionality and consistency in code
Which versions of Angular, Material, OS, browsers are affected?
@angular/common: 2.4.6
@angular/compiler: 2.4.6
@angular/compiler-cli: 2.4.6
@angular/core: 2.4.6
@angular/forms: 2.4.6
@angular/http: 2.4.6
@angular/material: 2.0.0-beta.1
@angular/platform-browser: 2.4.6
@angular/platform-browser-dynamic: 2.4.6
@angular/platform-server: 2.4.6
@angular/router: 3.4.6
@angular/upgrade: 2.4.6
Chrome: 56.0.2924.87
OS: Windows 10 Pro

Is there anything else we should know?

Thanks for the issue. This has been added recently in SHA https://github.com/angular/material2/commit/68a0c9044e701392f6fe52b6bdf81ce498b9cfab. It will be available in beta.2.

I apologize. Glad to see it's been added! Cheers!


Shared context between positive and negative prompts?

It looks like I can't define a variable in the positive prompt and access it in the negative prompt, am I mistaken?

Each prompt is handled separately so it isn't currently possible. It probably should be.

OK, thanks. I handled them together in the dynamic Javascript extension so the trick was more cutting off context than maintaining it. Different approaches I guess.

That's a pretty cool extension - just saw it now for the first time.

I also would like this feature. This would enable dynamic prompts to be used as a style randomizer, as styles include positive and negative prompts.


Cannot use higher priority tasks on STM32G030 with Embassy HAL

rt flag is enabled for embassy-stm32.
--> src/main.rs:30:1
 |
30 | #[app(device = embassy_stm32, peripherals = true, dispatchers = [TIM16, TIM17])]
 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ could not find `Interrupt` in `embassy_stm32`
 |
 = note: this error originates in the attribute macro `app` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing one of these items
 |
32 +     use crate::app::you_must_enable_the_rt_feature_for_the_pac_in_your_cargo_toml::interrupt::Interrupt;
 |
32 +     use crate::app::you_must_enable_the_rt_feature_for_the_pac_in_your_cargo_toml::interrupt::typelevel::Interrupt;
 |
32 +     use embassy_stm32::interrupt::Interrupt;
 |
32 +     use embassy_stm32::interrupt::typelevel::Interrupt;

Here is an example to try it out: https://github.com/andresv/stm32g030-rtic.
Maybe I am missing something obvious.

This can be resolved like this:
pub mod pac {
    pub const NVIC_PRIO_BITS: u8 = 2;
    pub use cortex_m_rt::interrupt;
    pub use embassy_stm32::pac::Interrupt as interrupt;
    pub use embassy_stm32::pac::*;
    pub use embassy_stm32::Peripherals;
}

#[app(device = pac, peripherals = true, dispatchers = [TIM16, TIM17])]
mod app {
...
}


How to process Batch Transfer?

I want to process multiple mints in one bitcoin transaction. For example, [(userA mint ordi), (userB mint sats)]. I put the commits of these two mint operations into the same bitcoin transaction through two inputs. Then reveal them in another bitcoin transaction. Can opi indexer distinguish the ordi and stats mint inscriptions and put them into which output of the reveal?

If you reveal two inscriptions in the same tx, I believe it will be labelled as "vindicated" by ord since they were cursed before and "vindicated" inscriptions are invalid by brc-20 rules. So, you should reveal a single mint inscription in a single tx.


Added ZDI mode

Hi Dean,
Maybe you have seen that I have added a ZDI monitor mode to my own hobby ElectronOS for AgonLight. On top of that I created a version of Dezog that enables you to connect to the AgonLight and step through code from the leisure of Visual Studio Code.
Don't know if you are interested but I ported this to the Agon VDP latest release. It's a compile switch so you can have all defaults still off.
To enter ZDI mode you press CTRL-Z via the USB serial terminal. The prompt changes from * to # indicating you are in ZDI mode. There are a number of one letter commands in this mode. 'h' is help and lists all options.
Let me know what you think of this.
Best regards,
Mario

this is awesome stuff
@breakintoprogram to see what this essentially enables, you should watch Mario's video: https://www.youtube.com/watch?v=SGg-DttBok0

Hi Steve, just committed my fixes that should resolve a couple of things you mentioned. Also just noticed you added a SERIALBAUDRATE define at the same time I made DEBUG_SERIAL_BAUDRATE for the same purpose.

Hi @S0urceror I've tweaked the VDP code slightly to compile with the latest Quark codebase and remove a couple of compilation errors. I'm getting the following error when I press Ctrl+Z:
(invalid EZ80 response, check ZDI connection: FFFF.FF)

I've tried this with and without my Zilog USB smart cable connected to the Agon ZDI port. It's an older Agon, not the Olimex version.
Any ideas?

Hi Dean,
The ZDI interface assumes GPIO26 and GPIO27 to be connected to TCK and TDI respectively. This replaces the functionality of the Zilog USB smart cable. Check here for more details: https://github.com/S0urceror/AgonElectronHAL
This enables you to enter an old-school hardware monitor styled after GDB. If you also enable the debug serial connection with the host pc you can also step through code with VSCode. (https://github.com/S0urceror/DeZog/tree/agonlight)
Btw. The original Agon and the Olimex version are easy to use like this. Just 2 Dupont cables and you’re done. With the 8 you unfortunately have do some soldering because the GPIO’s have been repurposed for the joystick interface and hidden behind buffer ICs.
Let me know if you get it working.
Regards,
Mario

On 8 Nov 2023, at 00:20, Dean Belfield @.***> wrote:
Hi @S0urceror https://github.com/S0urceror I've tweaked the VDP code slightly to compile with the latest Quark codebase and remove a couple of compilation errors. I'm getting the following error when I press Ctrl+Z:
(invalid EZ80 response, check ZDI connection: FFFF.FF)
I've tried this with and without my Zilog USB smart cable connected to the Agon ZDI port. It's an older Agon, not the Olimex version.
Any ideas?
—
Reply to this email directly, view it on GitHub https://github.com/breakintoprogram/agon-vdp/pull/93#issuecomment-1800391813, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGC6KEDBXM3E6NSYG7LMQTYDK64VAVCNFSM6AAAAAA43PGKP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBQGM4TCOBRGM.
You are receiving this because you were mentioned.


Test harness should check for running Timers and AnimationControllers

After running a widget test, we now clear out the widget tree and check that we
didn't leak any timers or animations.
Also, fix several bugs that this addtional check revealed.
Fixes #2481

@Hixie

lgtm, but looks like you missed one.

I worked around the issue in the stocks test.  I'm going to land this patch and then continue to investigate.


Not working m1 Ventura 13.1  OpenMTP-3.2.1

sysadmin ~/Downloads % /Applications/OpenMTP.app/Contents/MacOS/OpenMTP                                                                                (16:04)
[66323:1222/175510.724775:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
objc[66326]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x23dfaf110) and /Applications/OpenMTP.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x10b0753c8). One of the two will be used. Which one is undefined.
[66323:1222/175510.761373:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175510.775901:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175510.794891:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175510.828432:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175510.862929:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175510.896409:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
objc[66332]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x23dfaf110) and /Applications/OpenMTP.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x1098013c8). One of the two will be used. Which one is undefined.
[66323:1222/175510.931842:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175510.945500:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175510.965324:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175510.998948:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.033943:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.067477:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
objc[66339]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x23dfaf110) and /Applications/OpenMTP.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x1093d53c8). One of the two will be used. Which one is undefined.
[66323:1222/175511.101846:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.103019:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.135634:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.168835:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.203472:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.237968:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
objc[66346]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x23dfaf110) and /Applications/OpenMTP.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x1055b13c8). One of the two will be used. Which one is undefined.
[66323:1222/175511.272417:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.301360:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.306355:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.338666:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.371652:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.405954:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.439710:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
objc[66353]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x23dfaf110) and /Applications/OpenMTP.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x109e793c8). One of the two will be used. Which one is undefined.
[66323:1222/175511.473698:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.478685:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.507561:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.539897:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.575310:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.608920:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
objc[66362]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x23dfaf110) and /Applications/OpenMTP.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x1060753c8). One of the two will be used. Which one is undefined.
[66323:1222/175511.643667:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.653122:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.677814:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.712343:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.746592:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66369:1222/175511.763640:ERROR:gpu_init.cc(446)] Passthrough is not supported, GL is disabled, ANGLE is
[66323:1222/175511.765555:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.780936:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.817024:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.850255:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66374:1222/175511.874853:ERROR:gpu_init.cc(446)] Passthrough is not supported, GL is disabled, ANGLE is
[66323:1222/175511.876955:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.884711:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.917470:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.950791:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66323:1222/175511.984647:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.
[66379:1222/175511.986431:ERROR:gpu_init.cc(446)] Passthrough is not supported, GL is disabled, ANGLE is
[66323:1222/175511.988179:ERROR:gpu_process_host.cc(975)] GPU process exited unexpectedly: exit_code=9
[66323:1222/175511.988193:FATAL:gpu_data_manager_impl_private.cc(447)] GPU process isn't usable. Goodbye.
[1]    66323 trace trap  /Applications/OpenMTP.app/Contents/MacOS/OpenMTP
[66384:1222/175512.017828:ERROR:mach_port_rendezvous.cc(310)] bootstrap_look_up io.ganeshrvel.openmtp.MachPortRendezvousServer.1: Permission denied (1100)
[66384:1222/175512.018176:ERROR:child_thread_impl.cc(226)] Mach rendezvous failed, terminating process (parent died?)

Could you check if this helps?
https://github.com/ganeshrvel/openmtp/issues/276

it didn't help me ((( x64 version works fine
mtp-cli for arm the same works great

OpenMTP v3.2.10-beta.1 is now rolling out.
Note: This a pre-release version and it might be unstable. ⚠
Features

Fixes - the app crash on older versions of macOS
Fixes - the app crash caused while transferring files a large number of files.

If you are on an older version of OpenMTP and have frozen the auto-app update option for the sake of preventing the app crash, you may re-enable it from Settings > Updates > Automatically Check for Updates
Note: We have now officially retired the support for Kalam Kernel on macOS 10.13 (OS X El High Sierra) and lower. Though the "Legacy" MTP mode will continue working on these outdated machines.
Read more: https://github.com/ganeshrvel/openmtp/tree/release/3.2.10-beta.1#system-requirements-and-support
Download:

Apple Silicon (mac M1/M2): openmtp-3.2.10-beta.1-mac-arm64.dmg
Intel Silicon (Older mac): openmtp-3.2.10-beta.1-mac-x64.dmg

See if this helps?


add config hash to parameters

Hello!
I found that the parameter "build_requires_install_policy" spawns questions on installation. Since I didn't know why it has been set to "ask/yes" in the first place I made it as a configuration parameter so everything can be overridden in the config if necessary.
Cheers
Hannes

Thanks!


Don't exclude .git when copying to release

I would like to centralize my deployments around this, however we keep our dev as a working git repo for hotfixing. Dev wouldn't require rollback, but I would like to have a single deployment for dev, stage, and prod.

Hi
Sorry but I am 👎  on this, as the .git folder should not be accessible in any case in the servers
If your dev environment is a remote server I am afraid you will have to implement a post-deployment hook to copy the .git folder to current (the git contents are inside "{{ ansistrano_deploy_to }}/repo")

@ricardclau Can you elaborate why the .git folder should not be accessible in any case in the servers?

It should not be accessible via the browser (this is why it is not moved to the current folder)

Ok, I see, but this is a concern only when the root folder of the project is exposed to the webserver. Maybe we can have a new git-clone strategy for updating the code. What do you think about?

The "current" folder is exposed to the webserver in many projects. Maybe not with Symfony2 as you would expose current/public (or similar) but surely in other PHP projects where your index.php is in the root
I agree the current git strategy is not ideal (lack of submodules for instance) but I am totally 👎  on copying the .git folder with the rest of the code to the "current" folder.
And anyway, going to a remote dev server, hacking some code fix and pushing from there is not really good practice IMHO

It is a dev server, that is why we would do development on it. It isn't the primary development environment, but I see nothing wrong with using the development server for development.
I also don't see anything wrong with leaving this to a post hook either. It would be better if it where an option, so long as this isn't forced in a later version and my post hook will continue to work.
Lastly, I agree, the .git directory shouldn't be in the webroot. Mine is not, the webroot is in a subdirectory of the project, and I feel like this is a normal thing now. /projectroot/dist or /projectroot/bin for the webroot and /projectroot/src for the uncompiled source is the new norm for many languages and frameworks.

If after my last comment you are still -1 on this, then feel free to close. I think the post hook is a reasonable way to support this.

Closing as we are not going to support this any time soon


Navlinks doesn't change on mouse hover

Description
A slight colour in change on hovering the nav links would make it more appealing and attractive.
Screenshots

Additional information
No response

It's great having you contribute to Milan ! This is an auto-generated textThe maintainers/owner will look into the issue soon, add relevant tags and proceed further, please have paitence. Meanwhile feel free to support star the repo and share it with your friends. :nerd_face: :rocket:

This looks like a good addition, go ahead @imyoungsparda  !

I can do this you can assign this task to me

I can do this you can assign this task to me

Someone else is already working on the task as you can see.


Feature/add examples

Two examples are merged into one.
Now we got a class for Network (nodes and edges).
Network class can create interactive and static maps.
Arrows will be added into maps.

@jnnr okey, you can check now. For the plots following:
static: https://ibb.co/s9x1d91
interactive: https://ibb.co/NjLG1rQ

Thanks for your effort!

Allow to pass a dictionary that defines colors for different edge types instead of hardcoding.
The option to distinguish between elec and heat is nice. Default would be to display heating networks. Can you make the example a pure heating network?
Is there a possibility to make the background map in folium in greyscale? That makes it easier to see the network.


Analyse and propose a strategy to deploy SQL CLI workflows

Document possible ways to deploy SQL CLI workflows from within the Astro CLI.
The actual implementation will be part of #1166.
Acceptance criteria

[ ] Document open questions and possible solutions to implement flow deploy
[ ] Have the team review the proposal / agree

@dimberman to add a link to the doc


chore(deps): bump deps

Update:
@typescript-eslint/eslint-plugin from 4.29.3 to 4.33.0

also - there are four dependabots, is there a reason for only bumping one dependency?
Other 3 dependencies already bumped, I don't know why they are in PRs

hang on - the issue exists in the main branch too


Null check condition missing in the plugin

I am facing a crash in my app because of a missing null condition in your plugin.
You have to add the below condition at the top of your plugin so that the headless check is done before the plugin is used.
Check the registerWith (and associated plugin constructor) for usage of registrar.activity(). Plugin's should first do a != null check before using it
For example, flutter_statusbarcolor is not checking if registrar.activity() != null before using it.
It should be doing this:
fun registerWith(registrar: Registrar): Unit {
            val channel = MethodChannel(registrar.messenger(), "plugins.fuyumi.com/statusbar")
+            if (registrar.activity() != null) {
                  channel.setMethodCallHandler(FlutterStatusbarcolorPlugin(registrar.activity()))
+            }
        }

Add the two lines marked with + in your plugin.

Try 0.2.1 :)


Port all the CI Bells and Whistles Here Too

Basically the same as CMakePP/CMakeTest#45. This repo should have CI for:

[x] #73
[x] #75
[ ] building documentation

Has the "building documentation" task already been completed? We are using the reusable workflows available for documentation from CMakePP/.github now.

https://cmakepp.github.io/CMakePPLang/api/index.html doesn't show any API documentation at the moment.

Oh, I screwed up some of the paths in the reusable workflow when I was writing it. I figured out the issues and will fix them over there.

The API documentation is now showing up at https://cmakepp.github.io/CMakePPLang/api/index.html, so I think that is the last task complete here.


No error returned when an offer binds to an already in use address

The cli returns a success message while the node does not instanciate peerd correctly
swap-cli make --btc-addr tb1q935eq5fl2a3ajpqp0e3d7z36g7vctcgv05f5lf\
    --xmr-addr 54EYTy2HYFcAXwAbFQ3HmAis8JLNmxRdTC9DwQL7sGJd4CAUYimPxuQHYkMNg1EELNP85YqFwqraLd4ovz6UeeekFLoCKiu\
    --btc-amount "0.0000135 BTC" --xmr-amount "0.001 XMR"\
    --network testnet --arb-blockchain bitcoin --acc-blockchain monero\
    --maker-role Bob --cancel-timelock 4 --punish-timelock 5 --fee-strategy "1 satoshi/vByte"
Success: Public offer registered, please share with taker:  Offer:Cke4ftrP5A71LQM2fvVdFMNR4gmBqNCsR11111uMFuZTAsNgpdK8DiK11111TB9zym113GTvtvqfD1111114A4TTeE8U3z62MLUY8p46V7rJvc8BnpmHCqzcTFTHuwgzX4e111111111111111111111111111111111111111111AfZ113XRBtiBVC1P

Node
farcasterd -vv
[2022-06-08T09:54:17Z INFO  farcaster_node::config] Loading config file at: /home/joel/.farcaster/farcasterd.toml
[2022-06-08T09:54:17Z INFO  farcaster_node::service] New service farcasterd started
[2022-06-08T09:54:18Z INFO  farcaster_node::service] New service walletd started
[2022-06-08T09:54:18Z INFO  farcaster_node::farcasterd::runtime] Service walletd is now connected
[2022-06-08T09:54:42Z INFO  farcaster_node::farcasterd::runtime] Starting listener for incoming peer connections on <IP_ADDRESS>:9735
[2022-06-08T09:54:42Z INFO  farcaster_node::farcasterd::runtime] Connection daemon listens for incoming peer connections on <IP_ADDRESS>:9735
[2022-06-08T09:54:42Z INFO  farcaster_node::farcasterd::runtime] Public offer registered: 0x25ff…442c
[2022-06-08T09:54:42Z INFO  peerd] Local node id: 02de8fd55c1a4bec51ba245ecc814538d12af6665b175b13bc566920b705cd53ee
thread 'main' panicked at 'Unable to bind to Lightning network peer socket: Os { code: 98, kind: AddrInUse, message: "Address already in use" }', src/bin/peerd.rs:206:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

What triggered this double bind? Farcasterd should make sure that we only bind once.

This time it was another instance/application. (the docker-compose was using the default port and I created the offer on my machine, thus the double port usage)


Improve error messages for malformed json; use WARN if user container

Change error message of malformed json to a WARNing if it's not a managed container.  Otherwise, change error message to be something more diagnosable.
IPG 176

reviewed.


OCPP: Vehicle that had been manually assigned in the UI is assigned to different charger during identification phase

Describe the bug
On a setup with multiple vehicles and multiple chargers - but only one configured vehicle connected, the rest being guests - I had an issue where shortly after a restart, I had to manually assign the configured vehicle to its correct loadpoint.
Shortly after, evcc assigned that same vehicle to a different charger even though I had already manually assigned  it using the UI. In the UI, the vehicle appeared as assigned to two chargers simultaneously. I unassigned it from the wrong charger - while leaving it assigned in the correct one - and shortly afterwards it was automatically assigned to another charger. Again, it appeared as assigned to two chargers in the UI.
There seem to actually be two errors in this behaviour:

the manual vehicle assignment I did in the UI was ignored during vehicle identification phase, so the vehicle was reassigned to a different charger despite me having already assigned it manually;
on the side of the UI, the vehicle was treated as if it was assigned to two chargers simultaneously.

I'll leave a better description below along with the logs, as it's easier to explain the chain of events.
Steps to reproduce

Have multiple chargers
Have one connected configured vehicle, and other connected guest vehicles
After manually assigning the configured vehicles, evcc still assigned it to other chargers.

Configuration details
network:
  schema: http
  host: evcc
  port: 7070

interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/en/docs/reference/configuration/interval/

log: debug
levels:
  site: debug
  lp-1: trace
  lp-2: trace
  cache: error
  db: error
  ocpp: trace
  flobz: trace

site:
  - title: Something
    meters:
      grid: grid
    residualPower: 0
    maxGridSupplyWhileBatteryCharging: 0

meters:
  - name: grid
    type: template
    template: huawei-smartlogger
    usage: grid

    modbus: tcpip
    id: 11
    host: <IP_ADDRESS>
    port: 502

  - name: pv
    type: template
    template: huawei-sun2000-rs485
    usage: pv

    modbus: tcpip
    id: 1
    host: <IP_ADDRESS>
    port: 502

chargers:
  - name: charger1
    type: template
    template: pulsarplus
    timeout: 2m
    stationid: charger1

  - name: charger2
    type: template
    template: pulsarplus
    timeout: 2m
    stationid: charger2

  - name: charger3
    type: template
    template: pulsarplus
    timeout: 2m
    stationid: charger3

  - name: charger4
    type: template
    template: pulsarplus
    timeout: 2m
    stationid: charger4

  - name: charger5
    type: template
    template: pulsarplus
    timeout: 2m
    stationid: charger5

  - name: charger6
    type: template
    template: pulsarplus
    timeout: 2m
    stationid: charger6

loadpoints:
  - title: Garage Charger 1
    charger: charger1
    mode: "now"

  - title: Garage Charger 2
    charger: charger2
    mode: "now"

  - title: Garage Charger 3
    charger: charger3
    mode: "now"

  - title: Garage Charger 4
    charger: charger4
    mode: "now"

  - title: Garage Charger 5
    charger: charger5
    mode: "now"

  - title: Garage Charger 6
    charger: charger6
    mode: "now"

vehicles:
  - name: blc
    type: template
    template: flobz
    title: blc
    url: url
    vin: VIN

  - name: sfr
    type: template
    template: flobz
    title: sfr
    url: url
    vin: VIN

Log details
// Restarted evcc successfully

[site  ] INFO 2024/05/10 11:32:01 site config:
[site  ] INFO 2024/05/10 11:32:01   meters:      grid ✓ pv ✗ battery ✗
[site  ] INFO 2024/05/10 11:32:01     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2024/05/10 11:32:01   vehicles:
[site  ] INFO 2024/05/10 11:32:01     vehicle 1: range ✓ finish ✗ status ✓ climate ✓ wakeup ✓
[site  ] INFO 2024/05/10 11:32:01     vehicle 2: range ✓ finish ✗ status ✓ climate ✓ wakeup ✓
[lp-1  ] INFO 2024/05/10 11:32:01 loadpoint 1:
[lp-1  ] INFO 2024/05/10 11:32:01   mode:        now
[lp-1  ] INFO 2024/05/10 11:32:01   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/05/10 11:32:01   meters:      charge ✗
[lp-2  ] INFO 2024/05/10 11:32:01 loadpoint 2:
[lp-2  ] INFO 2024/05/10 11:32:01   mode:        now
[lp-2  ] INFO 2024/05/10 11:32:01   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-2  ] INFO 2024/05/10 11:32:01   meters:      charge ✗
[lp-3  ] INFO 2024/05/10 11:32:01 loadpoint 3:
[lp-3  ] INFO 2024/05/10 11:32:01   mode:        now
[lp-3  ] INFO 2024/05/10 11:32:01   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-3  ] INFO 2024/05/10 11:32:01   meters:      charge ✗
[lp-4  ] INFO 2024/05/10 11:32:01 loadpoint 4:
[lp-4  ] INFO 2024/05/10 11:32:01   mode:        now
[lp-4  ] INFO 2024/05/10 11:32:01   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-4  ] INFO 2024/05/10 11:32:01   meters:      charge ✗
[lp-5  ] INFO 2024/05/10 11:32:01 loadpoint 5:
[lp-5  ] INFO 2024/05/10 11:32:01   mode:        now
[lp-5  ] INFO 2024/05/10 11:32:01   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-5  ] INFO 2024/05/10 11:32:01   meters:      charge ✗
[lp-6  ] INFO 2024/05/10 11:32:01 loadpoint 6:
[lp-6  ] INFO 2024/05/10 11:32:01   mode:        now
[lp-6  ] INFO 2024/05/10 11:32:01   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-6  ] INFO 2024/05/10 11:32:01   meters:      charge ✗
[lp-1  ] DEBUG 2024/05/10 11:32:01 phase timer inactive
[lp-1  ] DEBUG 2024/05/10 11:32:01 pv timer inactive
[lp-2  ] DEBUG 2024/05/10 11:32:01 phase timer inactive
[lp-2  ] DEBUG 2024/05/10 11:32:01 pv timer inactive
[lp-3  ] DEBUG 2024/05/10 11:32:01 phase timer inactive
[lp-3  ] DEBUG 2024/05/10 11:32:01 pv timer inactive
[lp-4  ] DEBUG 2024/05/10 11:32:01 phase timer inactive
[lp-4  ] DEBUG 2024/05/10 11:32:01 pv timer inactive
[lp-5  ] DEBUG 2024/05/10 11:32:01 phase timer inactive
[lp-5  ] DEBUG 2024/05/10 11:32:01 pv timer inactive
[lp-6  ] DEBUG 2024/05/10 11:32:01 phase timer inactive
[lp-6  ] DEBUG 2024/05/10 11:32:01 pv timer inactive
[site  ] DEBUG 2024/05/10 11:32:01 ----
[lp-1  ] DEBUG 2024/05/10 11:32:01 charge power: 0W
[lp-2  ] DEBUG 2024/05/10 11:32:01 charge power: 0W
[lp-3  ] DEBUG 2024/05/10 11:32:01 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:32:01 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:32:01 charge power: 0W
[lp-6  ] DEBUG 2024/05/10 11:32:01 charge power: 0W
[ocpp  ] TRACE 2024/05/10 11:32:01 received JSON message from charger4: [3,"2201553130",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/05/10 11:32:01 TriggerMessage MeterValues for charger4: Accepted
[ocpp  ] TRACE 2024/05/10 11:32:01 received JSON message from charger4: [2,"1531310728","MeterValues",{"meterValue": [{"timestamp": "2024-05-10T09:32:00Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "3177228.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/05/10 11:32:01 sent JSON message to charger4: [3,"1531310728",{}]
[site  ] DEBUG 2024/05/10 11:32:02 grid meter: 16195W
[site  ] DEBUG 2024/05/10 11:32:02 grid currents: [33.6 11.6 22.6]A
[site  ] DEBUG 2024/05/10 11:32:02 pv power: 0W
[site  ] DEBUG 2024/05/10 11:32:02 site power: 16195W
[lp-1  ] DEBUG 2024/05/10 11:32:02 charger status: C
[lp-1  ] INFO 2024/05/10 11:32:02 car connected
[lp-1  ] DEBUG 2024/05/10 11:32:02 vehicle api refresh
[lp-1  ] DEBUG 2024/05/10 11:32:02 pv timer elapse
[lp-1  ] DEBUG 2024/05/10 11:32:02 pv timer inactive
[lp-1  ] INFO 2024/05/10 11:32:02 start charging ->
[lp-1  ] DEBUG 2024/05/10 11:32:02 wake-up timer: stop
[main  ] DEBUG 2024/05/10 11:32:02 vehicle status: C (blc)
[main  ] DEBUG 2024/05/10 11:32:02 vehicle status: A (sfr)

// blc vehicle is assigned to charger1 - which is expected, as it's the only configured vehicle with the status C. however, it is physically connected to charger5

[lp-1  ] INFO 2024/05/10 11:32:02 vehicle updated: unknown -> blc
[lp-1  ] DEBUG 2024/05/10 11:32:02 vehicle soc: 87%
[lp-1  ] DEBUG 2024/05/10 11:32:02 vehicle range: 298km
[lp-1  ] WARN 2024/05/10 11:32:02 charger logic error: disabled but charging
[lp-1  ] DEBUG 2024/05/10 11:32:02 charger enable
[ocpp  ] TRACE 2024/05/10 11:32:02 sent JSON message to charger1: [2,"2155845491","SetChargingProfile",{"connectorId":1,"csChargingProfiles":{"chargingProfileId":1,"transactionId":3,"stackLevel":0,"chargingProfilePurpose":"TxProfile","chargingProfileKind":"Relative","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":17}]}}}]
[ocpp  ] TRACE 2024/05/10 11:32:03 received JSON message from charger1: [3,"2155845491",{"status": "Accepted"}]
[lp-1  ] DEBUG 2024/05/10 11:32:03 max charge current: 17A
[ocpp  ] TRACE 2024/05/10 11:32:06 received JSON message from charger1: [2,"718504052","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:32:06 sent JSON message to charger1: [3,"718504052",{"currentTime":"2024-05-10T09:32:06Z"}]
[ocpp  ] TRACE 2024/05/10 11:32:12 received JSON message from charger6: [2,"1105221355","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:32:12 sent JSON message to charger6: [3,"1105221355",{"currentTime":"2024-05-10T09:32:12Z"}]
[ocpp  ] TRACE 2024/05/10 11:32:19 received JSON message from charger4: [2,"2076875234","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:32:19 sent JSON message to charger4: [3,"2076875234",{"currentTime":"2024-05-10T09:32:19Z"}]
[site  ] DEBUG 2024/05/10 11:32:31 ----
[lp-1  ] DEBUG 2024/05/10 11:32:31 charge power: 3910W
[lp-2  ] DEBUG 2024/05/10 11:32:31 charge power: 0W
[lp-3  ] DEBUG 2024/05/10 11:32:31 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:32:31 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:32:31 charge power: 0W
[lp-6  ] DEBUG 2024/05/10 11:32:31 charge power: 0W
[site  ] DEBUG 2024/05/10 11:32:31 grid meter: 16053W
[site  ] DEBUG 2024/05/10 11:32:31 grid currents: [33.9 11.8 21.8]A
[site  ] DEBUG 2024/05/10 11:32:31 pv power: 0W
[site  ] DEBUG 2024/05/10 11:32:31 site power: 16053W
[lp-2  ] DEBUG 2024/05/10 11:32:31 charger status: C
[lp-2  ] INFO 2024/05/10 11:32:31 car connected
[lp-2  ] DEBUG 2024/05/10 11:32:31 vehicle api refresh
[lp-2  ] DEBUG 2024/05/10 11:32:31 pv timer elapse
[lp-2  ] DEBUG 2024/05/10 11:32:31 pv timer inactive
[lp-2  ] INFO 2024/05/10 11:32:31 start charging ->
[lp-2  ] DEBUG 2024/05/10 11:32:31 wake-up timer: stop
[main  ] DEBUG 2024/05/10 11:32:31 vehicle status: A (sfr)
[lp-2  ] WARN 2024/05/10 11:32:31 charger logic error: disabled but charging
[lp-2  ] DEBUG 2024/05/10 11:32:31 charger enable
[ocpp  ] TRACE 2024/05/10 11:32:31 sent JSON message to charger2: [2,"3861516104","SetChargingProfile",{"connectorId":1,"csChargingProfiles":{"chargingProfileId":1,"transactionId":2,"stackLevel":0,"chargingProfilePurpose":"TxProfile","chargingProfileKind":"Relative","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":17}]}}}]
[ocpp  ] TRACE 2024/05/10 11:32:32 received JSON message from charger2: [3,"3861516104",{"status": "Accepted"}]
[lp-2  ] DEBUG 2024/05/10 11:32:32 max charge current: 17A
[ocpp  ] TRACE 2024/05/10 11:32:35 received JSON message from charger2: [2,"32748414","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:32:35 sent JSON message to charger2: [3,"32748414",{"currentTime":"2024-05-10T09:32:35Z"}]
[ocpp  ] TRACE 2024/05/10 11:32:50 received JSON message from charger5: [2,"1958103345","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:32:50 sent JSON message to charger5: [3,"1958103345",{"currentTime":"2024-05-10T09:32:50Z"}]
[ocpp  ] TRACE 2024/05/10 11:32:53 received JSON message from charger3: [2,"1211108051","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:32:53 sent JSON message to charger3: [3,"1211108051",{"currentTime":"2024-05-10T09:32:53Z"}]
[site  ] DEBUG 2024/05/10 11:33:01 ----
[lp-1  ] DEBUG 2024/05/10 11:33:01 charge power: 3910W
[lp-2  ] DEBUG 2024/05/10 11:33:01 charge power: 3910W
[lp-3  ] DEBUG 2024/05/10 11:33:01 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:33:01 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:33:01 charge power: 0W
[lp-6  ] DEBUG 2024/05/10 11:33:01 charge power: 0W
[site  ] DEBUG 2024/05/10 11:33:01 grid meter: 15443W
[site  ] DEBUG 2024/05/10 11:33:01 grid currents: [33.7 11.6 19.5]A
[site  ] DEBUG 2024/05/10 11:33:01 pv power: 0W
[site  ] DEBUG 2024/05/10 11:33:01 site power: 15443W
[lp-3  ] DEBUG 2024/05/10 11:33:01 charger status: B
[lp-3  ] INFO 2024/05/10 11:33:01 car connected
[lp-3  ] DEBUG 2024/05/10 11:33:01 vehicle api refresh
[lp-3  ] DEBUG 2024/05/10 11:33:01 pv timer elapse
[lp-3  ] DEBUG 2024/05/10 11:33:01 pv timer inactive
[main  ] DEBUG 2024/05/10 11:33:01 vehicle status: A (sfr)
[lp-3  ] DEBUG 2024/05/10 11:33:01 max charge current: 6A
[lp-3  ] DEBUG 2024/05/10 11:33:01 charger enable
[lp-3  ] DEBUG 2024/05/10 11:33:01 wake-up timer: start
[ocpp  ] TRACE 2024/05/10 11:33:06 received JSON message from charger1: [2,"229193316","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:33:06 sent JSON message to charger1: [3,"229193316",{"currentTime":"2024-05-10T09:33:06Z"}]

// here I manually unassign blc from charger1 and assign it to charger5 in the UI (since I know that's its correct position)

[lp-1  ] INFO 2024/05/10 11:33:12 vehicle updated: blc -> unknown
[lp-5  ] INFO 2024/05/10 11:33:12 vehicle updated: unknown -> blc
[ocpp  ] TRACE 2024/05/10 11:33:12 received JSON message from charger6: [2,"192677344","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:33:12 sent JSON message to charger6: [3,"192677344",{"currentTime":"2024-05-10T09:33:12Z"}]
[ocpp  ] TRACE 2024/05/10 11:33:19 received JSON message from charger4: [2,"157973909","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:33:19 sent JSON message to charger4: [3,"157973909",{"currentTime":"2024-05-10T09:33:19Z"}]
[site  ] DEBUG 2024/05/10 11:33:31 ----
[lp-1  ] DEBUG 2024/05/10 11:33:31 charge power: 3910W
[lp-2  ] DEBUG 2024/05/10 11:33:31 charge power: 3910W
[lp-3  ] DEBUG 2024/05/10 11:33:31 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:33:31 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:33:31 charge power: 0W
[lp-6  ] DEBUG 2024/05/10 11:33:31 charge power: 0W
[site  ] DEBUG 2024/05/10 11:33:31 grid meter: 15455W
[site  ] DEBUG 2024/05/10 11:33:31 grid currents: [33.7 11.6 19.5]A
[site  ] DEBUG 2024/05/10 11:33:31 pv power: 0W
[site  ] DEBUG 2024/05/10 11:33:31 site power: 15455W
[lp-4  ] DEBUG 2024/05/10 11:33:31 charger status: B
[lp-4  ] INFO 2024/05/10 11:33:31 car connected
[lp-4  ] DEBUG 2024/05/10 11:33:31 vehicle api refresh
[lp-4  ] DEBUG 2024/05/10 11:33:31 pv timer elapse
[lp-4  ] DEBUG 2024/05/10 11:33:31 pv timer inactive
[main  ] DEBUG 2024/05/10 11:33:31 vehicle status: C (blc)
[main  ] DEBUG 2024/05/10 11:33:31 vehicle status: A (sfr)

// blc vehicle is automatically assigned to charger4 even though I had manually assigned it to 5 in the UI
// in the UI, the same vehicle (blc) appears as assigned to both chargers 4 and 5 (I thought I had taken a screenshot but apparently didn't, sorry)

[lp-4  ] INFO 2024/05/10 11:33:31 vehicle updated: unknown -> blc
[lp-4  ] DEBUG 2024/05/10 11:33:31 vehicle soc: 87%
[lp-4  ] DEBUG 2024/05/10 11:33:31 vehicle range: 298km
[lp-4  ] DEBUG 2024/05/10 11:33:31 max charge current: 6A
[ocpp  ] TRACE 2024/05/10 11:33:31 sent JSON message to charger4: [2,"361345635","RemoteStartTransaction",{"connectorId":1,"idTag":"evcc","chargingProfile":{"chargingProfileId":1,"stackLevel":0,"chargingProfilePurpose":"TxProfile","chargingProfileKind":"Relative","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":6}]}}}]
[ocpp  ] TRACE 2024/05/10 11:33:32 received JSON message from charger4: [3,"361345635",{"status": "Accepted"}]
[lp-4  ] DEBUG 2024/05/10 11:33:32 charger enable
[lp-4  ] DEBUG 2024/05/10 11:33:32 wake-up timer: start
[ocpp  ] TRACE 2024/05/10 11:33:33 received JSON message from charger4: [2,"1690828371","StatusNotification",{"info": "","vendorId": "com.wallbox","vendorErrorCode": "","connectorId": 1,"errorCode": "NoError","status": "SuspendedEV","timestamp": "2024-05-10T09:33:32Z"}]
[ocpp  ] TRACE 2024/05/10 11:33:33 sent JSON message to charger4: [3,"1690828371",{}]
[ocpp  ] TRACE 2024/05/10 11:33:33 received JSON message from charger4: [2,"1557620404","StartTransaction",{"connectorId": 1,"meterStart": 3177227,"idTag": "evcc","timestamp": "2024-05-10T09:33:32Z"}]
[ocpp  ] TRACE 2024/05/10 11:33:33 sent JSON message to charger4: [3,"1557620404",{"idTagInfo":{"status":"Accepted"},"transactionId":1}]
[ocpp  ] TRACE 2024/05/10 11:33:36 received JSON message from charger2: [2,"1672033788","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:33:36 sent JSON message to charger2: [3,"1672033788",{"currentTime":"2024-05-10T09:33:36Z"}]
[ocpp  ] TRACE 2024/05/10 11:33:38 received JSON message from charger4: [2,"125929321","StatusNotification",{"info": "","vendorId": "com.wallbox","vendorErrorCode": "","connectorId": 1,"errorCode": "NoError","status": "Charging","timestamp": "2024-05-10T09:33:37Z"}]
[ocpp  ] TRACE 2024/05/10 11:33:38 sent JSON message to charger4: [3,"125929321",{}]

// here I noticed that blc had been wrongly assigned to charger4 and changed it to 'guest vehicle' in the UI
// in the UI, blc still appeared as assigned to charger5 so I didn't change that, since that was correct

[lp-4  ] INFO 2024/05/10 11:33:39 vehicle updated: blc -> unknown
[ocpp  ] TRACE 2024/05/10 11:33:43 received JSON message from charger2: [2,"337299670","MeterValues",{"meterValue": [{"timestamp": "2024-05-10T09:33:43Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "3997720.5"} ]} ],"connectorId": 1,"transactionId": 2}]
[ocpp  ] TRACE 2024/05/10 11:33:43 sent JSON message to charger2: [3,"337299670",{}]
[ocpp  ] TRACE 2024/05/10 11:33:50 received JSON message from charger5: [2,"1598022262","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:33:50 sent JSON message to charger5: [3,"1598022262",{"currentTime":"2024-05-10T09:33:50Z"}]
[ocpp  ] TRACE 2024/05/10 11:33:53 received JSON message from charger3: [2,"1696989972","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:33:53 sent JSON message to charger3: [3,"1696989972",{"currentTime":"2024-05-10T09:33:53Z"}]
[lp-1  ] DEBUG 2024/05/10 11:34:00 set max current: 7
[lp-2  ] DEBUG 2024/05/10 11:34:00 set max current: 26
[site  ] DEBUG 2024/05/10 11:34:01 ----
[lp-1  ] DEBUG 2024/05/10 11:34:01 charge power: 3910W
[lp-2  ] DEBUG 2024/05/10 11:34:01 charge power: 3910W
[lp-3  ] DEBUG 2024/05/10 11:34:01 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:34:01 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:34:01 charge power: 0W
[lp-6  ] DEBUG 2024/05/10 11:34:01 charge power: 0W
[site  ] DEBUG 2024/05/10 11:34:01 grid meter: 16985W
[site  ] DEBUG 2024/05/10 11:34:01 grid currents: [33.7 17.6 19.6]A
[site  ] DEBUG 2024/05/10 11:34:01 pv power: 0W
[site  ] DEBUG 2024/05/10 11:34:01 site power: 16985W
[lp-5  ] DEBUG 2024/05/10 11:34:01 vehicle odometer: 20358km
[lp-5  ] DEBUG 2024/05/10 11:34:01 charger status: C
[lp-5  ] INFO 2024/05/10 11:34:01 car connected
[lp-5  ] DEBUG 2024/05/10 11:34:01 vehicle api refresh
[lp-5  ] DEBUG 2024/05/10 11:34:01 pv timer elapse
[lp-5  ] DEBUG 2024/05/10 11:34:01 pv timer inactive
[lp-5  ] INFO 2024/05/10 11:34:01 start charging ->
[lp-5  ] DEBUG 2024/05/10 11:34:01 wake-up timer: stop
[lp-5  ] DEBUG 2024/05/10 11:34:01 vehicle soc: 87%
[lp-5  ] DEBUG 2024/05/10 11:34:01 vehicle range: 298km
[lp-5  ] WARN 2024/05/10 11:34:01 charger logic error: disabled but charging
[lp-5  ] DEBUG 2024/05/10 11:34:01 charger enable
[ocpp  ] TRACE 2024/05/10 11:34:01 sent JSON message to charger5: [2,"2504541038","SetChargingProfile",{"connectorId":1,"csChargingProfiles":{"chargingProfileId":1,"transactionId":1,"stackLevel":0,"chargingProfilePurpose":"TxProfile","chargingProfileKind":"Relative","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":32}]}}}]
[ocpp  ] TRACE 2024/05/10 11:34:02 received JSON message from charger5: [3,"2504541038",{"status": "Accepted"}]
[lp-5  ] DEBUG 2024/05/10 11:34:02 max charge current: 32A
[ocpp  ] TRACE 2024/05/10 11:34:06 received JSON message from charger1: [2,"1379493735","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:34:06 sent JSON message to charger1: [3,"1379493735",{"currentTime":"2024-05-10T09:34:06Z"}]
[ocpp  ] TRACE 2024/05/10 11:34:12 received JSON message from charger6: [2,"736529129","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:34:12 sent JSON message to charger6: [3,"736529129",{"currentTime":"2024-05-10T09:34:12Z"}]
[ocpp  ] TRACE 2024/05/10 11:34:19 received JSON message from charger4: [2,"837726995","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:34:19 sent JSON message to charger4: [3,"837726995",{"currentTime":"2024-05-10T09:34:19Z"}]
[site  ] DEBUG 2024/05/10 11:34:31 ----
[lp-1  ] DEBUG 2024/05/10 11:34:31 charge power: 3910W
[lp-2  ] DEBUG 2024/05/10 11:34:31 charge power: 3910W
[lp-3  ] DEBUG 2024/05/10 11:34:31 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:34:31 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:34:31 charge power: 7360W
[lp-6  ] DEBUG 2024/05/10 11:34:31 charge power: 0W
[site  ] DEBUG 2024/05/10 11:34:31 grid meter: 17172W
[site  ] DEBUG 2024/05/10 11:34:31 grid currents: [33.6 17.5 20.5]A
[site  ] DEBUG 2024/05/10 11:34:31 pv power: 0W
[site  ] DEBUG 2024/05/10 11:34:31 site power: 17172W
[lp-6  ] DEBUG 2024/05/10 11:34:31 charger status: A
[lp-6  ] INFO 2024/05/10 11:34:31 car disconnected
[lp-6  ] DEBUG 2024/05/10 11:34:31 set session soc limit: 0
[lp-6  ] DEBUG 2024/05/10 11:34:31 set session energy limit: 0
[ocpp  ] TRACE 2024/05/10 11:34:36 received JSON message from charger2: [2,"1384216857","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:34:36 sent JSON message to charger2: [3,"1384216857",{"currentTime":"2024-05-10T09:34:36Z"}]
[ocpp  ] TRACE 2024/05/10 11:34:41 received JSON message from charger1: [2,"1361675698","MeterValues",{"meterValue": [{"timestamp": "2024-05-10T09:34:40Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "1781453.5"} ]} ],"connectorId": 1,"transactionId": 3}]
[ocpp  ] TRACE 2024/05/10 11:34:41 sent JSON message to charger1: [3,"1361675698",{}]
[ocpp  ] TRACE 2024/05/10 11:34:50 received JSON message from charger5: [2,"1274163004","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:34:50 sent JSON message to charger5: [3,"1274163004",{"currentTime":"2024-05-10T09:34:50Z"}]
[ocpp  ] TRACE 2024/05/10 11:34:54 received JSON message from charger3: [2,"975891066","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:34:54 sent JSON message to charger3: [3,"975891066",{"currentTime":"2024-05-10T09:34:54Z"}]
[site  ] DEBUG 2024/05/10 11:35:01 ----
[lp-1  ] DEBUG 2024/05/10 11:35:01 charge power: 3910W
[lp-2  ] DEBUG 2024/05/10 11:35:01 charge power: 3910W
[lp-3  ] DEBUG 2024/05/10 11:35:01 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:35:01 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:35:01 charge power: 7360W
[lp-6  ] DEBUG 2024/05/10 11:35:01 charge power: 0W
[site  ] DEBUG 2024/05/10 11:35:01 grid meter: 17396W
[site  ] DEBUG 2024/05/10 11:35:01 grid currents: [33.5 17.5 21.6]A
[site  ] DEBUG 2024/05/10 11:35:01 pv power: 0W
[site  ] DEBUG 2024/05/10 11:35:01 site power: 17396W
[lp-1  ] DEBUG 2024/05/10 11:35:01 charger status: C
[ocpp  ] TRACE 2024/05/10 11:35:01 sent JSON message to charger1: [2,"1211089708","SetChargingProfile",{"connectorId":1,"csChargingProfiles":{"chargingProfileId":1,"transactionId":3,"stackLevel":0,"chargingProfilePurpose":"TxProfile","chargingProfileKind":"Relative","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":7}]}}}]
[ocpp  ] TRACE 2024/05/10 11:35:02 received JSON message from charger1: [3,"1211089708",{"status": "Accepted"}]
[lp-1  ] DEBUG 2024/05/10 11:35:02 max charge current: 7A
[ocpp  ] TRACE 2024/05/10 11:35:06 received JSON message from charger1: [2,"278220403","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:35:06 sent JSON message to charger1: [3,"278220403",{"currentTime":"2024-05-10T09:35:06Z"}]
[ocpp  ] TRACE 2024/05/10 11:35:12 received JSON message from charger6: [2,"529880554","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:35:12 sent JSON message to charger6: [3,"529880554",{"currentTime":"2024-05-10T09:35:12Z"}]
[ocpp  ] TRACE 2024/05/10 11:35:20 received JSON message from charger4: [2,"82991730","Heartbeat",{}]
[ocpp  ] TRACE 2024/05/10 11:35:20 sent JSON message to charger4: [3,"82991730",{"currentTime":"2024-05-10T09:35:20Z"}]
[ocpp  ] TRACE 2024/05/10 11:35:28 received JSON message from charger3: [2,"295268630","MeterValues",{"meterValue": [{"timestamp": "2024-05-10T09:35:27Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "3828525.1"} ]} ],"connectorId": 1,"transactionId": 1}]
[ocpp  ] TRACE 2024/05/10 11:35:28 sent JSON message to charger3: [3,"295268630",{}]
[site  ] DEBUG 2024/05/10 11:35:31 ----
[lp-1  ] DEBUG 2024/05/10 11:35:31 charge power: 1610W
[lp-2  ] DEBUG 2024/05/10 11:35:31 charge power: 3910W
[lp-3  ] DEBUG 2024/05/10 11:35:31 charge power: 0W
[lp-4  ] DEBUG 2024/05/10 11:35:31 charge power: 0W
[lp-5  ] DEBUG 2024/05/10 11:35:31 charge power: 7360W
[lp-6  ] DEBUG 2024/05/10 11:35:31 charge power: 0W
[site  ] DEBUG 2024/05/10 11:35:31 grid meter: 17077W
[site  ] DEBUG 2024/05/10 11:35:31 grid currents: [33.5 17.4 20.5]A
[site  ] DEBUG 2024/05/10 11:35:31 pv power: 0W
[site  ] DEBUG 2024/05/10 11:35:31 site power: 17077W
[lp-2  ] DEBUG 2024/05/10 11:35:31 charger status: C
[lp-2  ] DEBUG 2024/05/10 11:35:31 vehicle api refresh

// blc is once again automatically assigned to another charger, charger2, despite showing as already assigned to charger 5 in the UI - like before, it now appears as assigned to both loadpoint 2 and 5 in the UI

[main  ] DEBUG 2024/05/10 11:35:31 vehicle status: C (blc)
[main  ] DEBUG 2024/05/10 11:35:31 vehicle status: A (sfr)
[lp-2  ] INFO 2024/05/10 11:35:31 vehicle updated: unknown -> blc
[lp-2  ] DEBUG 2024/05/10 11:35:31 vehicle soc: 87%
[lp-2  ] DEBUG 2024/05/10 11:35:31 vehicle range: 298km

What type of operating system are you running?
Docker container
Version
evcc version 0.126.2

Again, it appeared as assigned to two chargers in the UI.

That would be a bug, but unfortunately it's not visible from the logfile.

@jduar if this is still an issue, a look at /api/state when this happens could help.


Clean up exec fifos on process exit

Fixes #22095
- What I did
Fixed cleaning up fifos for exec process on process exit. Previously cleanup only happened when container's main process exited.
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM

LGTM


Update identity.md  (Signed-off-by: Sampath Tilakumara<EMAIL_ADDRESS>

repeated word typo fixed.

Signed-off-by: Sampath Tilakumara<EMAIL_ADDRESS>

It's a read-only repository. Your PR won't be accepted, you can cancelled it in my opinion :) .

Thanks for the contribution! this is a read-only mirror. please read the contribution guide.


matrix: Fix test failure brought by the hint for usernames change.

Fixes a188a4e72a525847ded80eee6e864e43715e3bd7.

Awesome, thanks for fixing this! I'm going to merge this.


Corrected HTTP handling

Fixed #193.

Hi @brendandixon, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Closing. Travis is very confused. Will submit a new PR.


Updated .gitignore

Updated .gitignore to include elvish binary and common editor backup files.

Ignore this one, wasn't meant to include the commits from the other PR.


Getting 503 Service Unavailable after push

@kamleshdelat can you please provide additional context on your issue? Is there a specific document you are referencing or need help with?

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory: /tmp/bundle/gems/nokogiri-1.8.3/ext/nokogiri

/usr/local/.rbenv/versions/2.3.3/bin/ruby -r ./siteconf20180627-2122-1akgdcj.rb
extconf.rb
checking if the C compiler accepts ... yes
Building nokogiri using system libraries.
pkg-config could not be used to find libxml-2.0
Please install either pkg-config or the pkg-config gem per
gem install pkg-config -v "~> 1.1"

pkg-config could not be used to find libxslt
Please install either pkg-config or the pkg-config gem per
gem install pkg-config -v "~> 1.1"

pkg-config could not be used to find libexslt
Please install either pkg-config or the pkg-config gem per
gem install pkg-config -v "~> 1.1"

ERROR: cannot discover where libxml2 is located on your system. please make sure
pkg-config is installed.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/local/.rbenv/versions/2.3.3/bin/$(RUBY_BASE_NAME)
--help
--clean
--use-system-libraries=true
--with-zlib-dir
--without-zlib-dir
--with-zlib-include
--without-zlib-include=${zlib-dir}/include
--with-zlib-lib
--without-zlib-lib=${zlib-dir}/lib
--with-xml2-dir
--without-xml2-dir
--with-xml2-include
--without-xml2-include=${xml2-dir}/include
--with-xml2-lib
--without-xml2-lib=${xml2-dir}/lib
--with-libxml-2.0-config
--without-libxml-2.0-config
--with-pkg-config
--without-pkg-config
--with-xslt-dir
--without-xslt-dir
--with-xslt-include
--without-xslt-include=${xslt-dir}/include
--with-xslt-lib
--without-xslt-lib=${xslt-dir}/lib
--with-libxslt-config
--without-libxslt-config
--with-exslt-dir
--without-exslt-dir
--with-exslt-include
--without-exslt-include=${exslt-dir}/include
--with-exslt-lib
--without-exslt-lib=${exslt-dir}/lib
--with-libexslt-config
--without-libexslt-config
To see why this extension failed to compile, please check the mkmf.log which can
be found here:
/tmp/bundle/extensions/x86_64-linux/2.3.0-static/nokogiri-1.8.3/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in /tmp/bundle/gems/nokogiri-1.8.3 for
inspection.

@kamleshdelat This repo is specifically for Comments or issues across the Azure-Docs document Repo. Unfortunately the original issue or the response above does not provide us enough context to proceed. Can you please answer the following questions?

**Are you following directions from a particular doc (Yes/No) **
If Yes, Can you share the Link?
If No, can you please help us understand what you are trying to build and at what stage of development are you getting this error?
Additionally, the more human context you give us on what you are doing, the better we will be able to assist you

@amanarneja It's fix adding two germs
gem  'json', '1.8.6'
gem  'pkg-config','~> 1.1'

@kamleshdelat Not sure what that means. Can you please answer the questions from above so that we get more context ?

@kamleshdelat We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Security Questions

Can you please elaborate the following point and how it is done / controlled by marketing app?

The Marketing app infrastructure contains necessary precautions to minimize the impact of a possible DDoS attack.

If we host a marketing form on our website, is there a way to limit the filling of the form per "visitor" to avoid overloading the system with lead generations in D365?
Regards
Jaimie

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

ID: ecca0f6c-8f20-62d2-fa28-a45f7dd66427
Version Independent ID: ecca0f6c-8f20-62d2-fa28-a45f7dd66427
Content: Overview of real-time marketing forms
Content Source: ce/marketing/real-time-marketing-form-overview.md
Service: dynamics-365-marketing
GitHub Login: @petrjantac
Microsoft Alias: alfergus

Thanks for your comment, @jaimieji. This issue has been assigned to the doc author for review.

@jaimieji, There is a limit of 2000 requests / minute per Org. The limit for requests includes visits, lookup, captcha, submission. That should allow around 100 - 500 submissions / minute depending on the form.

Thank you. Is there a way to limit per submissions by "visitor" to avoid someone submitting more than once?

Limiting submissions by "visitor" is a more complex topic, as we need to first define how to recognize the "visitor". There are options like IP address, cookies, etc. But a typical DOS or DDOS attack can easily mimic multiple visitors. That's why we set the limit per Org and time, as that is the best practice. Could you please reach out to me over Teams? It would be easier to have a chat there if you would like to explore this topic deeper. Thank you, Petr

The topic in the documentation was about security. How we prevent DOS attacks.
Limiting submissions by "visitor" is a more complex topic, as we need to first define how to recognize the "visitor". Typical DOS or DDOS attack can easily mimic multiple visitors. Could you please reach out to me over Teams? It would be easier to have a chat there.


not seeing rg.xhr

Did it disappear in 3.5.0?

It disappeared between v2 and v3 as it was one of a few breaking changes. This pattern should suffice...
var xhr = new XMLHttpRequest();
xhr.addEventListener('load', function () { /*...*/ });
xhr.open('GET', url);
xhr.send();


Feature Request : Include standard Alexa cards

Would it be possible to include the standard Alexa cards  (timer, player, etc.)that are displayed in the companion app/firetv app ?
Maybe as an iframe by pulling data from the layla.amazon.com api?

https://www.amazon.com/gp/html-forms-controller/Display-Cards-for-Alexa seems like its limited to commercial use atm.

it's a cool idea, but you can just use iFrame to see the amazon alexa website.


[example] upgrade streamlit to 1.11.1

What happened？
There are 1 security vulnerabilities found in streamlit 0.73.1

CVE-2022-35918

What did I do？
Upgrade streamlit from 0.73.1 to 1.11.1 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How can we automate the detection of these types of issues?
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
The specification of the pull request
PR Specification from OSCS

Hi @ChengDaqi2023 Thank you very much for your contribution!


implement dynamic proto decoding

Bridges the expression language and wire-encoded bytes by translating proto-encoded bytes into go data structures given a proto descriptor.
Contributes to fixing #8146 and moving APAs out of process.
Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
If they are not already assigned, you can assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
ab797944c016f46fbc2275b0a76ee52ecebe02cf
link
/test istio-pilot-multicluster-e2e

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

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
ab797944c016f46fbc2275b0a76ee52ecebe02cf
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
20cce6d9a6418a3b2efd89dcf6a41d3d7e7f93d5
link
/test istio-unit-tests

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

@mandarjog @geeknoid PTAL. I separated out borrowed bits from the additions. The borrowed bits are mostly bit-level encoding/decoding routines, along with the coverage tests for the routines.

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
9064bb7598a2290fbc3cc3f3f9cabf7c37cb5bda
link
/test istio-unit-tests

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

Looks good.
Now next step is to house this map[string] interface{} in an attribute bag like struct I supposed.
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mandarjog
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [mandarjog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2a5ccfe241b299fe349fdf8bc0ac453778364476
link
/test istio-unit-tests

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

/test istio-unit-tests

@mandarjog re-LGTM please. Added a linter exception for lll.


PDK installation error

Description
I am having problems installing the PDKs it seems as thought it is trying to install the pdks to /home/username/OpenLane/pdks/skywater-pdk/ instead of  /home/username/OpenLane/pdks/sky130A, hence it gives me an error. Im not expert in linux at all so any help would be appreciated .
Thanks
Environment
`Kernel: Linux v<IP_ADDRESS>-microsoft-standard-WSL2
Distribution: opensuse-leap 15.2
Python: v3.6.10 (OK)
Container Engine: docker v20.10.12 (OK)
OpenLane Git Version: 2022.02.10_02.15.04
pip:click: INSTALLED
pip:pyyaml: INSTALLED
pip:venv: INSTALLED
PDK Version Verification Status: FAILED
/home/username/OpenLane/pdks/sky130A not found.
Traceback (most recent call last):
File "/home/username/OpenLane/dependencies/verify_versions.py", line 144, in verify_versions
raise Exception(f"{sky130_dir} not found.")
Exception: /home/username/OpenLane/pdks/sky130A not found.
Failed to compare PDKs.
Git Log (Last 3 Commits)
2f75eb2 2022-02-09T07:41:34+02:00 [BOT] Update netgen (#817) - Openlane Bot -  (HEAD -> master, tag: 2022.02.10_02.15.04, origin/master, origin/HEAD)
1860ec4 2022-02-07T22:27:50+02:00 add sky130hs/hd setup for gcd (#905) - Matt Liberty -  (tag: 2022.02.08_01.48.52)
5f7d5ca 2022-02-05T04:20:30+02:00 More ASAP7 Tweaks (#904) - Donn -  (tag: 2022.02.06_01.54.17)`
Expected behavior
Should install pdks to path /home/username/OpenLane/pdks/sky130A

@jimbo1990 Try this documentation https://github.com/The-OpenROAD-Project/OpenLane/blob/master/docs/source/manual_pdk_installation.md

We'd need the logs for make pdk as well, plus what steps you're executing exactly.
The PDK builds in two steps: skywater-pdk and then sky130 pdk. It will thus create multiple folders.

Alright, well, feel free to open another issue if you need one.

I am declaring the command for power ring in script file but after the floorplanning and placement. It must the power ring in my design.
But I found the design without power ring, Below message shown in the terminal.
Can anyone help me to understand this ?
Initialization of layers failed: Unable to open file: /home/shahid/.klayout/tech/sky130A/sky130A.lyp (errno=2)


feat(PeriphDrivers): Add OTP Powerdown feature for LP

Description
To disable the OTP for low power applications, due to design, there needs to be a 20HCLK cycle delay after the OTP controller powers down (OTP_CLKDIV.pd) and before the OTP peripheral clock is disabled.
Needs to be tested for ME55A2 LP measurements.
Checklist Before Requesting Review

[ ] PR Title follows correct guidelines.
[ ] Description of changes and all other relevant information.
[ ] (Optional) Link any related GitHub issues using a keyword
[ ] (Optional) Provide info on any relevant functional testing/validation.  For API changes or significant features, this is not optional.

/clang-format-run


a11y: Avoid forced focus changes that are not user-initiated

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

Tracking: W-7780319

@npsp-reedestockton If you don't mind, I assigned you as the reviewer to this PR since you have done most of the a11y related work items.

@andrewyu-salesforce Great solution, Andrew.  Works just as expected with VoiceOver.


server cpp: not all parameters from crazyflies.yaml might be set

When connecting to multiple Crazyflies, not all parameters that are specified in crazyflies.yaml are actually updated on all drones. This behavior is not deterministic and it seems like the first Crazyflie with connection attempts is more likely to have issues. It seems to be related to the ROS2 parameter callback which is not always called in that case.
To reproduce: connect to at least three drones and set about 30 params in crazyflies.yaml

A follow up question! Does this happen only with the cpp backend or also with the python backend?

I only tested with the cpp backend

ah oke good to know! I have tested this with multiple crazyflies with the cflib backend but never with 30 parameters. I think it is still okay but always good to check

I am unable to create this myself with both the cpp and the cflib backend, but the crazyradio was literally next to to crazyflies and I've only tried it about 3 times. But I think the solution you proposed is quite good anyway to set it two one crazyflie at the time.


Fixed #16735, #25871 -- Added aliasing and expressions support to QuerySet.values().

Fix https://code.djangoproject.com/ticket/25871.

@jarshwah Review?

Need some more test cases (thanks @MarkusH)

Adding an aggregate expression to values
Adding a grouping string, then aggregate to values (does it group by then aggregate, or does it add the aggregation before any grouping).

Sale.objects.values(sum_profit=Sum('profit'))

# should group by ID (no grouping)
Sale.objects.values('product__name', sum_profit=Sum('profit'))

Document that expressions added to values clauses are processed first, so any column names specified within the same values clause will NOT be grouped by. Any grouping needs to be written in a previous values call:
Sale.objects.values('product__name').values('product__name', sum_revenue=Sum('profit'))

# Is this different? Is the second product__name required? I think the below one will only return sum_revenue. Is that a problem?
Sale.objects.values('product__name').values(sum_revenue=Sum('profit'))

Code looks good to me. Docs might need a going over, but tests and logic look fine. Thanks!

Please add release notes for 1.11 and a .. versionchanged:: 1.11 annotation as described in the patch review checklist.

Unrelated to this patch, but after seeing the usage of assertSequenceEqual should we refactor the Django test suite to prefer that rather than assertQuerysetEqual with lambda o: o?

I see some failures on Oracle:
======================================================================
FAIL: test_values_expression_group_by (expressions.test_queryset_values.ValuesExpressionsTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tim/code/django/tests/expressions/test_queryset_values.py", line 39, in test_values_expression_group_by
    [{'firstname': 'Joe', 'sum_salary': 10}, {'firstname': 'Joe', 'sum_salary': 2}],
AssertionError: Sequences differ: <QuerySet [{'sum_salary': 2, 'firstname':[44 chars]e'}]> != [{'sum_salary': 10, 'firstname': 'Joe'}, [33 chars]oe'}]

First differing element 0:
{'sum_salary': 2, 'firstname': 'Joe'}
{'sum_salary': 10, 'firstname': 'Joe'}

- <QuerySet [{'sum_salary': 2, 'firstname': 'Joe'}, {'sum_salary': 10, 'firstname': 'Joe'}]>
+ [{'firstname': 'Joe', 'sum_salary': 10}, {'firstname': 'Joe', 'sum_salary': 2}]

======================================================================
FAIL: test_values_expression_group_by (expressions.tests.BasicExpressionsTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tim/code/django/tests/expressions/tests.py", line 86, in test_values_expression_group_by
    [{'firstname': 'Joe', 'sum_salary': 10}, {'firstname': 'Joe', 'sum_salary': 2}],
AssertionError: Sequences differ: <QuerySet [{'sum_salary': 2, 'firstname':[44 chars]e'}]> != [{'sum_salary': 10, 'firstname': 'Joe'}, [33 chars]oe'}]

First differing element 0:
{'sum_salary': 2, 'firstname': 'Joe'}
{'sum_salary': 10, 'firstname': 'Joe'}

- <QuerySet [{'sum_salary': 2, 'firstname': 'Joe'}, {'sum_salary': 10, 'firstname': 'Joe'}]>
+ [{'firstname': 'Joe', 'sum_salary': 10}, {'firstname': 'Joe', 'sum_salary': 2}]

Besides that, here are some edits for the first commit: http://dpaste.com/179M9QR
I thought the new tests would be better in a new file... feel free to propose an alternate organization if you have one in mind.

I fixed the Oracle test failure with an order_by() and merged the first commit in 39f35d4b9de223b72c67bb1d12e65669b4e1355b.
About the second commit to add aliasing, I'm not sure if I like it. Company.objects.values(salary=F('ceo__salary')) seems more readable than omitting the F() expression. Did you guys discuss the trade-offs of automatic aliasing versus explicit aliasing with F() as can be done without an additional patch?

I think we briefly discussed it, but didn't decide one way or another. Most expressions support string based values that automatically convert to F() internally. Aliasing was necessary to support other expressions - being able to close the aliasing ticket was just a byproduct of that.
Aliasing with F expressions is still possible though. I guess it comes down to whether we should throw an error if users try to use strings, or if we should automatically wrap them as an F expression.
I don't really have a preference.

I don't remember discussing it thoroughly either. I just added it because it was really easy and fixed the other ticket.

Closing per ticket, although it might be nice to add a more friendly error message for the values(foo='bar') case.


Audit fixes - teleportation

Overview
Implement Quantstamp Audit fixes for Teleportation.
Changes

withdrawBalance: Added balance > 0 check
Moved DisbursementSuccess event into else
Clearing transferredAmount & timeStamp as well on token removal

Please refer & feel free to leave feedback here:
https://docs.google.com/document/d/14KpepgI9qkYk45n1I3nXzlys1Yjbf-bdaHzCeUi906k/edit?usp=sharing
Testing
Tests run through.

@wsdt are we tackling 'best practices' and 'documentation' in the same pr?


Change type of HTTPBody.Length.known from Int to Int64

Motivation
The associated value of  enum case HTTPBody.Length.known was Int, and, on watchOS, Int = Int32, which is not ideal for a content length.
Modifications

(API breaking) Change type of HTTPBody.Length.known from Int to Int64.

Result
Can now express larger values for content type on 32-bit platforms.
Test Plan
Unit tests pass.
Related Issues

Fixes https://github.com/apple/swift-openapi-generator/issues/354.

Note
I have marked this PR as semver/major as it constitutes the first of the PRs we make in the run up to 1.0.0-alpha.1 and the release notes generator should therefore catch us from inadvertently cutting another pre-1.0 patch release.

@czechboy0 we discussed previously on the Github issue renaming this to ContentLength and contentLength to allow for a staged upgrade path, but given we are now about to break API for 1.0.0-alpha, I did not do this. Happy to reconsider. WDYT?

No let's just change the type, no need to stage this in. We'll be making more breaking changes before 1.0.0-alpha.1 anyway.


StopIteration raised every time

In /text/init.py
StopIteration gets raised every time
def _read(path, encoding="utf-8", comment=";;;"):
    """ Returns an iterator over the lines in the file at the given path,
        strippping comments and decoding each line to Unicode.
    """
    if path:
        if isinstance(path, str) and os.path.exists(path):
            # From file path.
            f = open(path, "r", encoding="utf-8")
        elif isinstance(path, str):
            # From string.
            f = path.splitlines()
        else:
            # From file or buffer.
            f = path
        for i, line in enumerate(f):
            line = line.strip(BOM_UTF8) if i == 0 and isinstance(line, str) else line
            line = line.strip()
            line = decode_utf8(line, encoding)
            if not line or (comment and line.startswith(comment)):
                continue
            yield line
    raise StopIteration

Experiencing the same issue. Works the second+ time it is used in an ipython shell for some reason.

Soo.. since it only fails the first time... One can throw a hack into files to get it to work. Here's the quick & dirty fix until this is resolved:

This issue is likely due to PEP-479 (https://www.python.org/dev/peps/pep-0479/)
This introduced a breaking change in the handling of "StopIteration" in generators that was activated by default in Python 3.7. In Python3.6, you would have seen a warning about the upcoming deprecation.
Someone should refer to PEP-479, in particular this section (https://www.python.org/dev/peps/pep-0479/#id38) to refactor this code. At first glance, I would bet that replacing raise StopIteration with return will do the trick.

Same here ..

Try this,
CFLAGS="-I$(xcrun --show-sdk-path)/usr/include" pyenv install -v 3.6.8
It didn't work with Python 3.7. Python 3.6 works for me.

This is incredibly annoying when parallelizing with joblib ...

Here's an easy workaround:
def pattern_stopiteration_workaround():
    try:
        print(lexeme('gave'))
    except:
        pass

def main():
    pattern_stopiteration_workaround()
    #Add your other code here

Basically, the pattern code will fail the first time you run it, so you first need to run it once and catch the Exception it throws.
It's worked well enough for my own scripts, but I don't know if it fixes every possible issue.
Ideally though, somebody should fork the clips/pattern project since it's no longer maintained.

Here's an easy workaround:
def pattern_stopiteration_workaround():
    try:
        print(lexeme('gave'))
    except:
        pass

def main():
    pattern_stopiteration_workaround()
    #Add your other code here

Basically, the pattern code will fail the first time you run it, so you first need to run it once and catch the Exception it throws.
It's worked well enough for my own scripts, but I don't know if it fixes every possible issue.
Ideally though, somebody should fork the clips/pattern project since it's no longer maintained.

If you use this method you should do 'except RuntimeError', in case you get any other error instead.


interpreters: bas: license update

Summary
revert the license to the original state and add it to LICENSE file
Impact
LICENSE
Testing
NONE

please ignore the nextyle errors
@acassis

Hmmm... Alan and I did talk to the author of BAS and he agreed to change the license to BSD.  Does that matter?  This was all done with discussions and agreements with the author.

me and Alan had a discussion about reverting the license yesterday
the best would be if we manage to contact the author and check if he wants to sign the SGA/ICLA


Extra credit (not higherorder)

The 1st option (not higher order functions) for extra credit. See exhibits.html
I didn't feel like putting in the effort for another featured animal. It felt redundant. The rest is there though

This is great, James!
Have you done much with document.createElement or document.appendChild before?
Those DOM methods can be a little annoying to work with, but they're not so bad if you become familiar with them and aren't afraid to write a few helper functions to make your life easier.
Good work on this extra credit! 👍


feat: archive issues

didnt see lukas' message

Our concern is that by just hiding issues we could lose trust of the students by making it possible that we delete any issue that might be a valid criticism against the student council.
We decided that before we introduce this feature, the archived issues should still be visible in a separate place on the site.
This way we will also be able to archive issues that are solved.

Also, the archive button should have a popup where you have to confirm.


Fix the bug of ImagePreviewer that the image does not follow the mouse when dragging。

{PR title}

Fix the bug that the image does not follow the mouse when dragging (Implement Image Moving by setting margin must be set up, down, left and right simultaneously).
Description
Original behavior: When drag the mouse (or touch) from the upper left to the lower right,  the image only moves half the distance.
Principle of bug : use Margin to move an image, need to set both left and right, up and down at the same time, for example: margin-left:100px;margin-right:-100px. Move 100px to the right, if only set one it will only move 50px.
After revision: Set the upper left and lower right simultaneously.

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