State values are not beeing aknowledged after successful change in ems-esp or km200 by the adapter

Hi Thomas,
when changing a state value in ioBroker, the adapter does not acknowledge the new value in ioBroker when the change was successful in ems-esp or km200. As far as i can see this happens for all states.
Example:
When changing ems-esp.0.dhwCircuits.dhw1.singleChargeSetpoint (for km200) or ems-esp.0.dhwCircuits.dhw1.wwseltemp (for ems-esp) the value gets changed in ems-esp or km200 successfully! However, the adapter does not aknowledge the value. The value is displayed in 'red' in ioBroker. When hovering over the value with the mouse it is displayed as Aknowledged: false, From: Admin.0
Expected behaviour:
When changing a value in ioBroker without the 'aknowledged' checkbox set, the value needs to be aknowledged by the adapter after successfully sending it to km200 or ems-esp. The value will be displayed in 'green', then in 'white' after the adapter has aknowledged the value. When hovering over the value it should be displayed as Aknowledged: true, From: ems-esp.0 (instance ID of the adapter beeing 0)
Best Regards,
Michael

Expected behaviour:
When changing a value in ioBroker without the 'aknowledged' checkbox set, the value needs to be aknowledged by the adapter after successfully sending it to km200 or ems-esp. The value will be displayed in 'green', then in 'white' after the adapter has aknowledged the value. When hovering over the value it should be displayed as Aknowledged: true, From: ems-esp.0 (instance ID of the adapter beeing 0)

The adapter just react on any state-change done. The change can be initiated by VIS, the object-browser or a script / node-red.
The acknowledged flag is set from there. The adapter does not change it. When polling ems-esp or km200 only changes in state-value are written back to ioBroker.
So the behavior is intended and I do not know if I should change it. Why do you think it should be done?
btw: I want to avoid unnecessary updates by re-writing state values if not changed.

@tglynx I checked again. For km200 the values are overwritten and acknowledge is true. I will implement for ems-esp as well.

@tp1de i did update to 1.25 from 1.21 now.
The behaviour has changed as follows:
When changing ems-esp.0.dhwCircuits.dhw1.wwseltemp without ack (which is as you said the correct way to change a value to be picked up by an adapter), the value does no longer getting changed in ems-esp but is shown as follows:
Aknowledged: False
From: Admin.0
After some seconds the old value from ems-esp is written back and aknowledged by the adapter (from: ems-esp.0)
Aknowledged: True
From: ems-esp.0
Expected behaviour would be:
When changing ems-esp.0.dhwCircuits.dhw1.wwseltemp without ack the adapter would pick up the changed value and change it in ems-esp as the adapter will only pick up changes without ack.
After successfully changing the value in ems-esp (successfull webservice call) the adapter will update the value with ack.

Update: my fault… I think it is working now… I think I had browser caching issues…
I will check this in more detail tomorrow and let you know!
Thanks!!!

After successfully changing the value in ems-esp (successful webservice call) the adapter will update the value with ack.

I disagree. Ack is set when ems-esp or km200 confirms the changes. So after next poll.

I see, that is how it is implemented and how it is working right now in version 1.25.
Also I am fine with it for my current use case, so thank you very much!
However, it takes a while for the ack to come … I understand that this is because we are waiting for the poll.
I was just thinking if it would be a good improvement if the adapter would read back the value directly after it has been set to have the ack as fast as possible - i also understand that this may be lots of effort and could rise other issues (maybe timing related)… :)
so I agree, maybe it is the best to wait for the next poll to get the ack for the value.
thanks again!

Please note that since the adapter uses polling for both ems-esp and km200 and state changes are just sent using http api posts, it could happen that next poll still delivers "old" values and changes are only recognized by next poll read.
The adapter just waits for a successful http post and it could take some seconds (km200 up to 30 secs) until changes are really done and included in next poll. It's the same for mqtt discovery mode in homeassistant.

I noticed that in V 1.25 not all values are included in dhw1 compared to V 1.21.
All values are coming still coming in from ems-esp/api/boiler
Comparison:
V 1.21

V1.25

I noticed that, as wwcylmiddletemp was not getting updates anymore...

where is this state wwcylmiddletemp?
Are other states missing?
Is it in boiler? please post http://ems-esp/api/boiler

it is in boiler...
{   "wwsettemp": 11,   "wwseltemp": 40,   "wwtype": "layered buffer",   "wwcomfort": "eco",   "wwflowtempoffset": 40,   "wwmaxpower": 100,   "wwcircpump": "off",   "wwchargetype": "3-way valve",   "wwhyston": -6,   "wwhystoff": 0,   "wwdisinfectiontemp": 69,   "wwcircmode": "2x3min",   "wwcirc": "off",   "wwcurtemp": 18.5,   "wwcurtemp2": 9.4,   "wwcurflow": 0.0,   "wwstoragetemp1": 18.5,   "wwstoragetemp2": 9.4,   "wwactivated": "on",   "wwonetime": "off",   "wwdisinfecting": "off",   "wwcharging": "off",   "wwrecharging": "off",   "wwtempok": "off",   "wwactive": "off",   "ww3wayvalve": "off",   "wwmixertemp": 46.8,   "wwcylmiddletemp": 49.7,   "wwstarts": 1105,   "wwworkm": 11657,   "heatingactive": "off",   "tapwateractive": "off",   "selflowtemp": 45,   "selburnpow": 100,   "heatingpumpmod": 10,   "outdoortemp": -1.0,   "curflowtemp": 47.5,   "rettemp": 40.3,   "switchtemp": 47.5,   "syspress": 1.5,   "burngas": "off",   "burngas2": "off",   "flamecurr": 0.0,   "heatingpump": "on",   "fanwork": "off",   "ignwork": "off",   "oilpreheat": "off",   "heatingactivated": "on",   "heatingtemp": 75,   "pumpmodmax": 100,   "pumpmodmin": 10,   "pumpdelay": 3,   "burnminperiod": 10,   "burnminpower": 0,   "burnmaxpower": 100,   "boilhyston": -6,   "boilhystoff": 6,   "boil2hyston": 0,   "boil2hystoff": 0,   "curburnpow": 0,   "burnstarts": 3092,   "burnworkmin": 150234,   "burn2workmin": 0,   "heatworkmin": 138577,   "heatstarts": 1987,   "ubauptime": 762172,   "servicecode": "0Y",   "servicecodenumber": 204,   "maintenancemessage": "H00",   "maintenance": "date",   "maintenancetime": 6000,   "maintenancedate": "04.01.2024" }
Please check the first screenshot of my last post, i would say everything between wwactive and wwdisinfecting is missing currently.

I will have a look. But this will be my last change on the adapter. More than 600 users and some with exotic constellations which they want to be implemented. I do not use ioBroker anymore, since I moved to home assistant.
To keep it maintained eats a lot of time - even that I am retired.
I think that this error is related to the translation to km200 like structure for ems-esp.
Could you please install a second instance and run ems-esp without km200 structure. I think, that then the states should be in.

I restarted my ioBroker instance to test myself. Could you please test the latest Github Version.
This version works fine for me.

Hi Thomas, sad to hear that ... i was hoping to get around moving to home assistant as i already put so much effort in my iobroker config. i understand that all this is lots of effort for you - i am a software developer myself but my native language is c# so i have not much js experience - maybe this would be a good project to get into it? 🥇
I tested the newest github release and it is working again! Thank you so much!

I was using ioBroker since the start of the project. There are a lot of pro's using ioBroker. I am not a software engineer but I learned JS during the past years since retired. Compared to the time I did programming - during studying electrical engineering more then 40 years ago - in Perl / C++  I felt not comfortable with JS and the ioBroker adapter logic and setup. Debugging is a mess. OK I learned it as from an engineering point of view it is interesting, interpreter based  and quite flexible on different hardware.
I started with HA 3 months ago. HA is not so flexible in sense of implementing own logic like this adapter. But I found a way to implement my own logic with node-red (JS) without writing integrations.
HA is much faster and the dashboards are much easier to create with responsive UI. I do not like VIS which is not responsive to different screen resolutions on mobile, tablet and desktop. I decided to stay there. The ems-esp integration is done by mqtt discovery. For the km200 I migrated the adapter code to node-red within ha. For my other hardware there are good integrations available within HA. While using the HA VM installation the whole staff is easy to install, maintain and migrate to different hardware.
Same as on ems-esp where the 2 developers have a big job to maintain and support the different heating systems, it's the same for the Bosch systems with km200 / ip-inside. Not all hardware is actually supported there. And Bosch wants to close the local api access and move to cloud api with limited functionality or paid one for installers.
To keep track with all this requires a lot f time. The 1st km200 adapter was not developed further since 3 years. I believe a similar reason.

I released 1.26 now. I hope that this version is stable for everybody.


[Bug Report] InfiniteScroll not work with an async callback function

Hi, I am using InfiniteScroll directive and find it doesn't work well with an async callback function. An example is posted here, https://codepen.io/starkshang/pen/WNRpQab
I notice that the InfiniteScroll directive will check that whether the callback function is a function before trigger it.
// packages > infinite-scroll > src > main.js   line 111
if (shouldTrigger && isFunction(cb)) {
  cb.call(vm);
} else if (observer) {
  observer.disconnect();
  this[scope].observer = null;
}

And the function isFunction implement as follows,
// src > utils > types.js   line 13
export const isFunction = (functionToCheck) => {
  var getType = {};
  return functionToCheck && getType.toString.call(functionToCheck) === '[object Function]';
};

For an async callback, it is '[object AsyncFunction]', rather than '[object Function]'. So the InfiniteScroll directive cannot work with async functions directly.

Element UI version
2.15.1
OS/Browsers version
Edge
Vue version
2.6.12
Reproduction Link
https://codepen.io/starkshang/pen/WNRpQab
Steps to reproduce
using v-infinite-scroll="load" where load is an async function.
What is Expected?
An async callback function will be called with v-infinite-scroll directive.
What is actually happening?
As shown in example, v-infinite-scroll with synchronous function can normally load data, but it doesn't work with async function.

why close , this Bug not fix at all


feature/JFF-15/server_metadata

Had problems with the Formats type, had to change it to a mapped type to limit the input for the keys and even so I was getting an error during the build.

@hrehman-sphereon This is part of logo:
logo: OPTIONAL. A JSON object with information about the logo of the Credential with a following non-exhaustive list of parameters that MAY be included:
url: OPTIONAL. URL where the Wallet can obtain a logo of the Credential issuer.
alt_text: OPTIONAL. String value of an alternative text of a logo image.
description: OPTIONAL. String value of a description of the Credential.
background_color: OPTIONAL. String value of a background color of the Credential represented as numerical color values defined in CSS Color Module Level 37 [CSS-Color].
text_color: OPTIONAL. String value of a text color of the Credential represented as numerical color values defined in CSS Color Module Level 37 [CSS-Color].


[KOGITO-6801] Fixing classcast exception when using non string literal

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

(tests) - kogito-examples job #1235 was: UNSTABLE
Possible explanation: This should be test failures
Test results:

PASSED: 433
FAILED: 1

Those are the test failures:

org.kie.kogito.examples.demo.OutboxIT.(?)
java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 49257] should be listening)	at org.kie.kogito.examples.demo.OutboxIT.before(OutboxIT.java:81)Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 49257] should be listening)

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-examples/1235/display/redirect

(tests) - kogito-examples job #1234 was: UNSTABLE
Possible explanation: This should be test failures
Test results:

PASSED: 433
FAILED: 1

Those are the test failures:

org.acme.travel.tests.avro.quarkus.MultiMessagingIT.testProcess
org.opentest4j.AssertionFailedError: expected: <0> but was: <3>	at org.acme.travel.tests.avro.quarkus.MultiMessagingIT.testProcess(MultiMessagingIT.java:89)

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-examples/1234/display/redirect

@fjtirado can you add some tests? :)

Actually this failed when you use a not string literal as argument. Thats why was not detected before.

(tests) - kogito-examples job #1236 was: UNSTABLE
Possible explanation: This should be test failures
Test results:

PASSED: 433
FAILED: 1

Those are the test failures:

org.kie.kogito.examples.demo.OutboxIT.(?)
java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 49484] should be listening)	at org.kie.kogito.examples.demo.OutboxIT.before(OutboxIT.java:81)Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 49484] should be listening)

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-examples/1236/display/redirect

jenkins rerun kogito-examples tests

(tests) - kogito-examples job #1237 was: UNSTABLE
Possible explanation: This should be test failures
Test results:

PASSED: 433
FAILED: 1

Those are the test failures:

org.kie.kogito.examples.demo.OutboxIT.(?)
java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 49257] should be listening)	at org.kie.kogito.examples.demo.OutboxIT.before(OutboxIT.java:81)Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 49257] should be listening)

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-examples/1237/display/redirect


iPhone SE Gen 3 & iPod Air Gen 5

New models should be added.
I'll go ahead and add them if you all want to check the work...  Give me a little bit...

ok - see pull #74 & #75

@jminutaglio Great! Thank you for the pull request. I merged it so I guess we can close this issue right?

@Nirma  - cool - yes we can close.
FYI - may make sense to cut a release.  Current release version  is missing these obviously, and is missing the Sept '21 models that came out.   Meaning the source code is current, but if ppl are installing via Cocoapods they're behind...

Ok Sounds good!

Updated for iPad Air 5 - strings are 16 & 17 (not 17 & 18).
"iPad13,16" --> iPad Air (5th generation) Wi-Fi
"iPad13,17" --> iPad Air (5th generation) Wi-Fi + Cellular
Pulls #76 & #77
Also: the last release isn't showing in Cocoapods...

@jminutaglio I have published both on CocoaPods now 🙂


HIMS-222-1st person data are shown under the 2nd persons completed vi…

HIMS-222-1st person data are shown under the 2nd person's completed visits
This correction is for the bug that is reported by Dr.Malinda yesterday. But unfortunately, I couldn't test this with the real data since I couldn't map a formset to an institute in my local environment. When I check the method calls are performing as expected in the solution. @buddhika75 Can you please verify this then I can do the same for the other two tabs else can discard the code changes from this brance.

The error of not refreshing was due to the fact the visits were not made null on changing a client. I have corrected that error. These code changes are not necessary. Can we reverse these?

This was a bug introduced when changes were done to improve performance. The bug was corrected and available in the production server. You can check again. This was not there at the beginning. Extremely sorry for the issue. But no data has been affected. This leaves a good lesson that we have to make sure that every cycle of development needs to be checked for each function before deploying to production now onwards.

This bug was corrected in the master branch as a hot fix. This pull request can be ignored. Hope that is fine.

This bug was corrected in the master branch as a hot fix. This pull request can be ignored. Hope that is fine.

Yes, It's totally fine with me to close this pull request.


Review CLI docs

It has been suggested that our CLI docs are out of date. This issue is just a reminder to review and remedy where necessary.

to contrary - CLI is the most self-documenting thing and does not need docs beside docstrings? agile is less documentation

the time-saving thing is still to just delete. CLI relies heavily on the REST and the click library, the logic there is thin and evident.
tests are documentation

Tests are documentation for developers, we are talking about documentation for users: https://diamondlightsource.github.io/blueapi/main/how-to/run-cli.html

but here the users would be the support teams. they could read the python code, right?

Not wanting to get too far down a philosophical rabbit hole, but by that logic, libraries shouldn't have docs because "their users developers and developers can read code, right?". I can't say I agree, imagine trying to figure out how to use pydantic, say, without these: https://docs.pydantic.dev/latest/

it's an economic / praxeological, not philosophical question.
pydantic has a very high ratio of users to developers (millions to one) and high volume of developer input to user input ( thousands of hours to one).
our use case is different - support engineers (users) are around 2 or 3 to 1 compared to the blueapi team, and also users (software support engineers) will be expected to deal with various issues in the core code.

the time-saving thing is still to just delete

No. Time spent writing good documentation pays itself back manyfold over the course of a project.

CLI is the most self-documenting thing

I disagree that CLIs are self-documenting. There is value in having both a tutorial-style walkthrough and a detailed API reference. Imagine trying to figure out how to use ssh by just reading man ssh - it's a great technical reference for someone who already knows the basics, but there is value in tutorial-style walkthroughs too.

the users would be the support teams. they could read the python code, right?

I use many many CLIs each day. I've never read the source code behind 99.9% of them. blueapi should be no different, it should be possible for both a first time user to do the basics (via a tutorial-style walkthrough) and a more advanced user to get to the detailed options (via a detailed reference) without ever reading the code.

users (software support engineers) will be expected to deal with various issues in the core code

So make it easier for them by writing good documentation.

this took me 3 minutes and that is just the self-documentation from the code.
the point raised by OP was that it's difficult to keep docs up to date, not that it's difficult to make it good.
if docs are unreliable, people will checkout the code anyway.
regardless, there is no version 1.0 that is module - loadable (#402), so breaking changes are to be expected.
right now the project does not have too many users and developer effort is scarce - what little there is available is devoted to bugs and functionality.
Of course for 1.0 a small and easy to maintain online guide would be good


Android: Update the "browser" remote flag name

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3743   👈

This comment was auto-generated by Graphite.


Storage Class helm parameters

This PR adds parameters to simplify generating storage classes for CVMFS-CSI resources.  Specifically a simple flag to create the auto-mounter class and an array you can use to add repo specific classes.
It might be easier to review the commits individually.

@jcpunk Can you please squash the commits? Thanks!

Squashed.


Archive changes

This PR addresses #369 and #404
I've also renamed to semi-public archive to private archive in the code to avoid confusion. I wouldn't say it's a perfect name, but at least it's more distinct that semi-public.
I've left in the site-export functionality (the mechanism for filling the current page on the WP). Just for the transition period.

But it won't show up on the archive page:

I had this as well, it's a caching issue. Try opening the API endpoint in your browser and do a force refresh


fix(tests): Add page object model for URL tests

This PR contains Page object model for URL tests

@ldimaggi can you please review this !

@naina-verma snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1304-fabric8-ui.int.rdu2c.fabric8.io

[test]

[test]

@naina-verma snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1304-fabric8-ui.int.rdu2c.fabric8.io

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


wine{Unstable,Staging}: 6.13 -> 6.14

Motivation for this change
Upstream update.
Things done
$ NIXPKGS_ALLOW_UNFREE=1 nixpkgs-review rev wine-6.14
[...]
14 packages updated:
grapejuice lutris lutris lutris-original pipelight winePackages.unstable (6.13 → 6.14) wineUnstable (6.13 → 6.14) winePackages.staging (6.13-staging → 6.14-staging) wineStaging (6.13-staging → 6.14-staging) wine-staging (6.13-staging → 6.14-staging) wineWowPackages.unstable (6.13 → 6.14) wineWowPackages.staging (6.13-staging → 6.14-staging) yabridge yabridgectl
[...]
12 packages built:
grapejuice lutris lutris-free lutris-unwrapped pipelight wineStaging winePackages.staging wineUnstable wineWowPackages.staging wineWowPackages.unstable yabridge yabridgectl

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ ] Fits CONTRIBUTING.md.

Running this change for four days now without any issues. It fixes a nasty bug where wineserver runs one core at full load even when idle after a while. https://bugs.winehq.org/show_bug.cgi?id=51319

Should we merge anyway?

Reads like the bug is fixed in 6.14, not that it is in 6.14, so merging would be good.

Indeed.


Having troubles binding gamepad button to function as toggle.

Hello! I'm having a hard time, trying to bind r1 to function as right trigger toggle. Pretty sure it's me, but I can't figure out what am I doing wrong. I go to the profile, double click R1, check "toggle" checkbox, and click on "RB" image, then save the profile, and make sure that's one enabled in game. Pressing R1 still function as a single press, though :(
Help?
The game is Bayonetta, if it's relevant, and I'm trying to set up target lock as a toggle.

It doesn't seem like toggle works for gamepad to gamepad mappings, but only for gamepad to keyboard mappings. I wish it worked though I'm trying to do the same thing.


Integrated terminal loads old environment variables, not the current value in .env file

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.91.0
OS Version: Darwin arm64 23.5.0

Steps to Reproduce:
In our Remix project, we are using dotenv to load environment variables from the .env file. But if we were to log a process variable to the console:

when running the app through the VS Code integrated terminal, an old value will be logged
if we switch to another terminal, the correct value from the .env file will be logged

Similar issue were also reported at https://github.com/microsoft/vscode/issues/212606, but the issue was closed without conclusion.

We source the env of the terminal on startup of VS code. If you make a change, close VS Code, reopen it, and create a new terminal in VS Code, does it reflect that change?

Did restart VS Code, even restarted my laptop but the problem still persisted.


Ignore notAfter in certificates in the trust store

OpenSSL has ignored self-signed certificate signatures since 0.9.8m (see https://github.com/openssl/openssl/commit/1e53b797f65ef6d3c2eb1052797683fec27a9ff5).  Due to this, it's possible to artificially extend the lifetime of an expired root certificate in an OpenSSL client's trust store simply by locally modifying that certificate's notAfter date.  I posted a write-up<EMAIL_ADDRESS>that demonstrates how this technique is useful for working around the recent expiry of the "DST Root CA X3" root certificate.
What's the point of OpenSSL checking the notAfter timestamps in certificates that have self-signed signatures, given that these timestamps can be trivially modified?
I propose that OpenSSL should adopt the same behaviour as Android (explained by https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/).  i.e., Ignore the notAfter field in locally-trusted certificates, so that OpenSSL clients will never regard these locally-trusted certificates as expired.

Marking as inactive, to be closed at the end of the 3.4 dev cycle, barring further input


[Regression] Tooltip for Export button is broken

EPAM AI DIAL chat version
0.7.0
What happened?
On staging:

Expected as on UT now:

Confidential information

[X] I confirm that do not share any confidential information

Verified on staging successfully


Hide Scope behind App

This PR adds a Pool which helps to collect Callbacks and emit events from a single entity.
That is useful for a context implementation.

I think you forgot to push something. There is nothing called "pool" in this PR :laughing:

The first attempt was failed ) Callbacks are too narrow to create a pool of subscribers. But I've done did useful preparatory work and should merge it. After that I will try to rewrite main loop partially to Rust to replace callbacks with more effective structs and remove unnecessary closures.

bors r+

By the way I like how it looks now: https://github.com/DenisKolodin/yew/blob/992c4e21a72db8ff968f564fd33bd0858817c605/examples/two_apps/src/main.rs#L24


fix: 🐛 Add start_period to node container to fix startup issue

Description
Sometimes docker fails to start and errors as follows -
Step 11/11 : USER subquery
 ---> Running in 9e9957f585b2
Removing intermediate container 9e9957f585b2
 ---> dd7ccfd29456
Successfully built dd7ccfd29456
Successfully tagged polymesh-subquery_subquery-node:latest
Pulling graphql-engine (onfinality/subql-query:latest)...
latest: Pulling from onfinality/subql-query
ca7dd9ec2225: Already exists
6fb1b25da510: Pull complete
7604515c95e1: Pull complete
e6bf7dff8d85: Pull complete
738cd76cfa5e: Pull complete
59981c69dea0: Pull complete
Digest: sha256:6b8e2dc9db1bff423e4c177e96b88c97974f9bfdb40e104e33a1488bcb2c6fd6
Status: Downloaded newer image for onfinality/subql-query:latest
Creating polymesh-subquery_postgres_1 ... done
Creating polymesh-subquery_subquery-node_1 ... done

ERROR: for graphql-engine  Container "453e111ca854" is unhealthy.

This maybe due to initial migrations and other queries run to startup the container.
This PR adds a start_period of 30s to the node container so that retries are counted after this period of time.
Breaking Changes
NA
JIRA Link
DA-463
Checklist

[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 8.5.0-alpha.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 8.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update gradle-wrapper.properties

Hi,
This small PR adds the distributionSha256Sum property to gradle-wrapper.properties. It allows for verification of the downloaded Gradle distribution via SHA-256 hash sum comparison.
You can find some documentation about this security improvement here, and the sums for each version of gradle here.
Note that you need to update this property every time you change your version of gradle.

Thanks for writing in!
I'm not totally convinced of a security benefit here; we already use an https URL for the Gradle distribution to download, and it seems like if someone's environment is compromised enough to subvert that (like their system root CA list contains a CA willing to forge certs for an attacker) then there are probably lots of other ways to exploit that.
But I see how this approach could potentially help some things if everyone did it, so I'm willing to go along if we can maintain it without any ongoing manual work.
Starting from your branch, I just tried upgrading the Gradle version with the instructions in that same doc. It clobbered the hash, without adding a new one:
$ git di gradle/wrapper/gradle-wrapper.properties
diff --git android/gradle/wrapper/gradle-wrapper.properties android/gradle/wrapper/gradle-wrapper.properties
index 534fd3d0..1e70565b 100644
--- android/gradle/wrapper/gradle-wrapper.properties
+++ android/gradle/wrapper/gradle-wrapper.properties
@@ -1,7 +1,6 @@
-#Sun Mar 19 12:07:15 PDT 2017
+#Tue May 22 19:04:30 PDT 2018
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
 zipStoreBase=GRADLE_USER_HOME
 zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-3.3-all.zip
-distributionSha256Sum=71a787faed83c4ef21e8464cc8452b941b5fcd575043aa29d39d15d879be89f7
+distributionUrl=https\://services.gradle.org/distributions/gradle-4.2.1-bin.zip

Can you help us work out how to fix that?

Closing this PR since there's no work ongoing on it. I'd be open to a PR to do this in the future, if someone finds a way to fix the issue above.

I'm not familiar enough with that sorry


sample application

Hi,
I was looking for a sample application using mylar.
The following link https://github.com/gliesesoftware/mylar-encchat
doesnt seem to work. I found the link in https://atmospherejs.com/mylar/platform.
Is there a sample application which I could look at....
Thanks and Best Regards
Joseph

In general, we are not really maintaining these packages for now so unless you feel comfortable enough to figure out from examples @ http://css.csail.mit.edu/mylar/ then you are probably not going to be able to build anything with it.
Worth noting that there seems to be some recent development on this:
http://people.eecs.berkeley.edu/~raluca/verena.pdf


Optional not being observed

In the quickstart example in the README, the due field is optional but results in a 400 bad request if not passed
curl -v -H "content-type: application/json" -d '{"due":"2020-12-08T11:19:35.818445","task":"Build an example"}' localhost:5000/ works
curl -v -H "content-type: application/json" -d '{"task":"Build an example"}' localhost:5000 fails
Viewing on redoc shows the due field is required rather than optional.

Hmm, it might be clearer with Python3.10+ syntax due: datetime | None i.e. it must be supplied but can be supplied as None. To be fully optional it needs a default value i.e. due: Optional[datetime] = None (see querystring docs).
Actually maybe I should add a default value to the README?

Thanks for the clarification! I was working off README and Quickstart which didn't specify a default value. To save you the time, I searched through the docs and code and added default values using Optional[...] = None as that is that is used with other documentation and code files rather than the due: ... | None syntax in a pull request (#22).


Soft link CUDA Runtime & lazy import Jitify

This is a part of #7620. Soft link CUDART.
This PR also:

adds a debugging feature in SoftLink. When CUPY_DEBUG_LIBRARY_LOAD=1 env var is set, CuPy prints the diagnostic messages to stderr.
fixes to load NVRTC symobols in class NVRTCError.
closes #7834

CI will be added after implementing lazy import of Profiler.

Q: Don't we link to cudart statically?

Q: Don't we link to cudart statically?

Ah yes, I'll give it a try! 😄

Superseded by #7954


The problem is buying things with almost the same name

I want to buy dice from one mod, but he constantly buys ammo and I can't do anything about it...
018d74cf-29e8-6f15-3576-8074d0e20896

I entered the full name, it doesn't help


Simplify indexing

This removes some code that's no longer needed, thanks to JuliaLang/julia#10525. Hopefully, this will make it a little easier to extend the package in the future.
@timholy I assume that the method taking a CartesianIndex is an optimization. Is this somehow also provided by base Julia now?

It was more likely there to avoid an ambiguity warning. Should not be necessary anymore, I assume.
:+1:

There's still some work to do here, though, as noted in https://github.com/JuliaLang/julia/pull/12273#issuecomment-123996106. Now that I know that you (probably) don't need the method for something specific, I can just remove it if I find that there's another with cartesian indexes provdided by base :)


"Global" states, aka how to properly inject the language

Hello,
i'm facing following problem, i want to integrate the language into my url slug to have localized permalinks. So effectively "example.com/de/foo" shoud route to the german version of foo.
So i have written this root controller
$stateProvider.state('root',{
        url: '/:language',
        abstract: true,
        template: '<ui-view/>',
        controller: 'rootCtrl'
    });

This works but have the really annoying side effect that i now have to write
$state.go(root.somestate, { language: currentLanguage } )

in every single ui router link.
What I want is a "global" stateParam... so the router should recognize that i come from a /de state and i most certainly want to keep this param.
Could we integrate something like that in ui-router or is it already somehow possible and i'm missing something out here?
EDIT: I thought about that a bit more and try to make my question more specific. What I want is a feature where the ui-router remembers my parent state params. I think this is needed very often, not only when trying to implement localized URLs.

@l0rn The parent stateParam is kept. You shouldn't need to specify it while you are traversing between sub states (ex. root.someStateA -> root.someStateB). You should only need to include the language param if you are entering from a state that is not the root or a child (ex. login.success -> root.someStateA) because it won't already have resolved this information.
We do this a lot and it works for us. One thing to remember is that the language won't be accessible to anyone other than the root state. If you need to make it accessible then you will likely want to pull it out of stateParams and return it on the resolve.
$stateProvider.state('root',{
        url: '/:language',
        abstract: true,
        template: '<ui-view/>',
        resolve: {language: ['stateParams',function(stateParams){ return stateParams['language'];}]},
        controller: 'rootCtrl'
    });

@acollard wow, thanks. you just solved one of our biggest problems of our project. i actually googled a lot for this and never found a satisfying solution. I think this should be documented somehow since i'm most certainly not the only one looking for this behavoir. I would provide this language inheritance as example in the guide under "nested states". i start an approach when i get home.
many thanks again!

@l0rn Happy to help.


Error downloading Boruto (local variable 'rtmpDL' referenced before assignment)

anime-dl.exe -i "http://www.crunchyroll.com/boruto-naruto-next-generations/episode-3-metal-lee-goes-wild-732527" -u "" -p "" -r "1080p"
Trying to login...
Logged in successfully...
Grabbing Links for 1080p Streams.
Writing subtitles to files...
Writing subtitles to files...
Writing subtitles to files...
Writing subtitles to files...
Writing subtitles to files...
Writing subtitles to files...
Traceback (most recent call last):
File "anime_dl_main_.py", line 18, in
File "anime_dl_main_.py", line 69, in main
File "anime_dl\AnimeDL.py", line 27, in init
File "anime_dl\sites\crunchyroll.py", line 42, in init
File "anime_dl\sites\crunchyroll.py", line 215, in singleEpisode
UnboundLocalError: local variable 'rtmpDL' referenced before assignment
Failed to execute script main

Fixed.


other: update specs2-core from 4.12.1 to 4.12.2

Updates org.specs2:specs2-core from 4.12.1 to 4.12.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #33 (e3029ce) into master (f00acf1) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #33   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        29        29
===========================================
  Files              1         1
  Lines            114       114
  Branches           8         8
===========================================
  Hits             114       114

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 f00acf1...e3029ce. Read the comment docs.


Update EditBin target to use VsInstallRoot property

VS150COMNTOOLS is not defined in our MicroBuild environment.

Just so this doesn't get lost, we found that the VSTS MSBuild task doesn't use the Developer Console or something similar, so common environment variables are not set. VS140COMNTOOLS worked before because Visual Studio sets that machine-wide. With 2017 that is no longer the case since you can install more than one copy of Visual Studio. So in order to find VS I used the VsInstallRoot that MSBuild sets. To make things more complicated, our Jenkins CI build will build a copy of MSBuild and package it up as a "Bootstrap" MSBuild and then rebuild and run tests. That is a standalone environment and does not set VsInstallRoot like a normal copy of MSBuild would (we don't want Visual Studio instance assets to leak into our inner build).
I don't think there's a bug here, but it's not very straightforward!

@dotnet-bot test Windows_NT Build for Desktop please

@dotnet-bot test Ubuntu14.04 Build for CoreCLR please

@dotnet-bot test Ubuntu14.04 Build for CoreCLR please


espruinoctrl updates for Bangle.js 2

Disable not existing BTN3 on Bangle.js 2, set maximum transmit power

Thanks! It's surprising as I thought I'd used that on Bangle.js 2 recently :)


Incompatible with Intellij IDEA 2020.2 EAP

Short description
After upgrade to IDEA 2020.2 EAP plugin doesn't start.
It said "Incompatible (until build 201.SNAPSHOT < IU-202.4357.23)"
Expected behavior
Plugin works.
Version information

IDEA Version: 2020.2 EAP. Build #IU-202.4357.23, built on May 27, 2020.
JDK Version: OpenJDK 1.8.0_252
OS Type & Version: Windows 10
Lombok Plugin Version: 0.30-2020.1
Lombok Dependency Version: What version of lombok.jar are you using?

Steps to reproduce
Just upgrade to latest EAP IDEA via Toolbox.
Or install 2020.2 EAP manually.

Reinstalling plugin resolve this problem.


Package Review Base Page and Route

Description
This PR includes the following proposed change(s):

Add route for direct navigation to package review component page
Package review page and basic stories/tests

Screenshots

Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

storybook
local
jest

Does the change impact or break the Docker build?

[ ] Yes
[x] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

@sdevalapurkar-bcgov last action on this PR was 7 days ago. should we close?


silentRepeat() ends Conversation

Currently trying to use convo.silentRepeat() but it is not behaving as expected. Instead of simply waiting for new input from the user, it ends the conversation altogether. I have tried comparing it with convo.repeat() which works just fine (repeats the question and waits for a new response from the user).
This seems to be a bug.
Botkit Version: 0.2.2
OS: Mac OSX 10.11.6
info: [Start]  0  Task for  U1MBJHLQ1 in D1U5QGDGV
info: >   [Start]  0  Conversation with  U1MBJHLQ1 in D1U5QGDGV
info: ** API CALL: https://slack.com/api/im.open
info: >   [Start]  1  Conversation with  U1MBJHLQ1 in D1U5QGDGV
info: >   [End]  0  Conversation with  U1MBJHLQ1 in D1U5QGDGV

SILENT REPEATING

debug: No handler for conversationEnded
debug: No handler for end
info: >   [End]  1  Conversation with  U1MBJHLQ1 in D1U5QGDGV
info: [End]  0  Task for  U1MBJHLQ1 in D1U5QGDGV

https://github.com/howdyai/botkit/issues/318 seems to be having similar issues.

Let's continue the discussion in https://github.com/howdyai/botkit/issues/365

@peterswimm Did you mean the discussion is continued in #318 ? Is @mostr's reply there (from Sep 26) the recommended way of working around this?

@itamarro just merging two topics into one for more visibility! Did you try the suggested workaround?

Got it :) Yes, I did apply the workaround and it works for me. Just wanted
to be cautious and see if it's indeed the recommended way.
On Mon, Nov 28, 2016 at 7:38 AM, Peter Swimm<EMAIL_ADDRESS>wrote:

@itamarro https://github.com/itamarro just merging two topics into one
for more visibility! Did you try the suggested workaround?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/365#issuecomment-263303373, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACNpNuSEVJONsUOiur1W_xa4bKlFq7Qiks5rCvVhgaJpZM4JjecH
.

hi, what's the deal with this? Can we please make silentRepeat() work in an expected way?


Bump 1.0.4 - Improvements to ReadMe's, Server Infustructure

This PR adds a few improvements to the Frontend Package Server:

404 and 505 pages properly change the HTTP Status Code
robots.txt and sitemap.xml now accessible for Web Crawlers
Fixed Search Bar Text Color on GitHub Dark Theme
Remote & Local Caches to Featured Packages to speed up response times (Addresses #4 )
Tests Added to ensure Regex Accuracy
Handles Identifying the Author in all cases that have been identified
Better Handling at extracting the Repository URL
Relative Image Links translation now supports Current Directory References, Root Directory References, and Implicit Current Directory References
Additional Documentation Added
Bumps version to 1.0.4

Once this PR is merged this version will be pushed out to the cloud.

Merging PR and updating site


Update identities section in Communication Guide

Please come u with a draft for this.

What we should cover here:

DAPS / OAuth
X.509
And also how we could apply DID/VC7VP
describe also an abstract level.

@PeterKoen-MSFT  will provide a link to a document for DID/VC/VP from the EDC world

Hi, I now have a (likely incomplete) first draft, but I'm missing write access here.
I can fork IDS-G to my own account and PR from there, but I would prefer uploading my feature branch directly here.
@ssteinbuss or someone else with admin rights: Could you assign permissions so I can upload my branch?

Great to hear @milux  thx
You should have now write access to this repository.


SubmissionErrors Repository

Fix for #447

[x] Move SubmissionError out from SubmissionEnvelope module
[x] Fix Endpoint for POST data
[x] Add Endpoint for GET data
[x] Add SubmissionErrorService Unit Tests
[x] Add SubmissionErrors Repository
[x] Remove SubmissionErrors property from SubmissionEnvelope
[ ] Make the JSON return format nice and consistent.

I think that link already exists, but prior to my work was throwing an error when you navigated to it.
    private Link getSubmissionErrorsLink(SubmissionEnvelope submissionEnvelope) {
        return entityLinks.linkForSingleResource(submissionEnvelope)
                .slash(Links.SUBMISSION_ERRORS_URL)
                .withRel(Links.SUBMISSION_ERRORS_REL);
    }

Looks good. Should the Content-Type of the responses in SubmissionErrorController not be set to application/problem+json? Kinda defeat the purpose of adopting the standard if client cannot tell the response follows the problem details spec/structure. Or maybe this is implicitly set somewhere in the lib?
Two things:
- validation errors in MetadataDocument are contained in a list of Object. Does it make sense to have a ValidationError class extending the new IngestError, and use links to errors in a similar way rather than current embedded list?
- I am keen to see how we migrate this change. Do we have a procedure for migration? I am assuming we that to write a script that fetches submission envelope one-by-one, iterate over submissionErrors, for each error POST to submissionEnvelopes/{sub_id}/submissionErrors, and finally delete submissionErrors?  I may have to carry out something similar with the ValidationJob/Error changes.

Should the Content-Type of the responses in SubmissionErrorController not be set to application/problem+json?

That would be the return type of the errors generated by our api, rather than record or errors recorded by the API.

Validation errors in MetadataDocument are contained in a list of Object. Does it make sense to have a ValidationError class extending the new IngestError, and use links to errors in a similar way rather than current embedded list?

I think this makes a lot of sense.

I am keen to see how we migrate this change.

I've verified that the spring object just ignores any properties in Mongo that it wasn't expecting, so no issues will be encountered loading items that used to have submission errors. In production, none of the submission envelopes have submission errors. So no migration needed.

Yeah, on a more general aside, beyond what Spring gives us I very much think we want to write code that will tolerate unexpected information for precisely this kind of scenario.

Tested successfully on dev by deploying tag: c61d022

Tested successfully on dev by deploying tag: c61d022


Please adapt for mongo versions >3.0

Thanks for this library. could be possible to adapt it to be used with mongodb 3?, now it only works with mongodb 2.6.11, as latest release.
;; connect to mongodb 2.6.11
CL-USER> (with-mongo-connection (:host "<IP_ADDRESS>" :port 27018 :db "stackoverflow" )
			 (show :collections))
[{name : stackoverflow.system.indexes} ]
[{name : stackoverflow.queue2} {options : (autoIndexId : T) (flags : 1) } ]
[{name : stackoverflow.queue2.$_id_} ]
NIL

;; connection to mongodb 3.0
CL-USER> (with-mongo-connection (:host "<IP_ADDRESS>" :port 27017 :db "gravity" )
			 (show :collections))
NIL

I have same issue.  I tried the oldest available version homebrew which is v3.2, and I get no connection as above.  2.6 was end of life in 2016 and doesn't seem available. Is there another cl driver for mongo? I was following Lisp for the Web & now there seems no way to continue :(

I'll quote your edit because it's worth knowing for followers!

Update: Use SBCL! - cl-mongo works for me with that, using latest mongo-community.
I was on CCL when I had the problem above.

Update: Use SBCL! - cl-mongo works for me with that, using latest mongo-community.
I was on CCL when I had the problem above.

Can you be a little more specific here? Does latest really mean that this lib works with Mongo 4.2? What were all the features you tried? Queries, aggregation pipelines, collection-level operations...?

Mongo 3.6.6, SBCL 1.5.7 via roswell <IP_ADDRESS>
* (cl-mongo:with-mongo-connection (:host "<IP_ADDRESS>" :port 27017 :db "hub")
    (cl-mongo:show :collections))
NIL

Maybe use https://github.com/cmoore/cl-mango/ ? Last updated 8 days ago. Or not, it says it's for 2.x

A minimalist CouchDB 2.x database client.


[Possible bug] Wrong file paths in latest WoncerCMS

I noticed a weird thing when updating to the latest version of WonderCMS. Images that I previously could refer to by using just "/data/files/image.jpg" didn't show up. Instead the system tried to add "domain/page-name" to that automatically, so the full path would read "www.domain.com/page-name/data/files/image.jpg". Problem with this is that images don't get put into such subdirectories when uploaded. They appear in "data/files" as usual.
As an example I used this in my database file to specify unique backdrop images for each page for the parallax theme by using "background": "Image.jpg". I suppose I could create a new folder manually for each of my pages and upload the images there, but it seems like a complicated solution to something that is probably much simpler. So therefore I submit this as a bug report, in case this behaviour is unintended.
WonderCMS: 3.3.0
Theme: Parallax

Similar issue was reported here: https://www.wondercms.com/community/viewtopic.php?p=6061#p6061
Can you please try this change and see if it fixes the issue?

Open your index.php file and replace the whole parseurl() function.
Replace (starts on line 1970)

	public function parseUrl(): string
	{
		$page = $_GET['page'] ?? null;

		if (!isset($page) || !$page) {
			$defaultPage = $this->get('config', 'defaultPage');
			$this->currentPageTree = explode('/', $defaultPage);
			return $defaultPage;
		}

		$this->currentPageTree = explode('/', rtrim($page, '/'));
		if ($page === $this->get('config', 'login')) {
			return htmlspecialchars($page, ENT_QUOTES);
		}

		$currentPage = end($this->currentPageTree);
		return $this->slugify($currentPage);
	}

and replace the whole function with:
	public function parseUrl(): string
	{
		if (!isset($_GET['page'])) {
			$defaultPage = $this->get('config', 'defaultPage');
			$this->currentPageTree = explode('/', $defaultPage);
			return $defaultPage;
		}

		$this->currentPageTree = explode('/', rtrim($_GET['page'], '/'));
		if ($_GET['page'] === $this->get('config', 'login')) {
			return htmlspecialchars($_GET['page'], ENT_QUOTES);
		}

		$currentPage = end($this->currentPageTree);
		return $this->slugify($currentPage);
	}

Thanks again for really quick help!

Yes. I tried the Sky theme and the result is the same.
I tried changing this code but I'm afraid it didn't help.

@Imerion

Do you have these issues only on subpages?
You didn't have these issues in 3.1.0 and 3.2.0 - from which version did you update from?

No, it's on the normal pages. The site has no subpages at all.
I updated from 3.1.4, which worked fine.

Also, as mentioned in the forum post you linked, the problem doesn't appear on the start page, only on other pages. On the start page files are referenced from /data/files as before.

I'm trying to reproduce this issue was we speak.
Can you correct these steps if they are wrong?

Login to WCMS website.
Through the settings, upload an image.
Try linking to that image in a page (that is not homepage) with just "/data/files/image.jpg"?

Does this sound like the steps necessary to reproduce this?

Yes, that sounds correct. As an example, I have the following code in my theme.php file to add a small mail-icon to the menu. Before the mail icon showed up, but now it doesn't. (Other than on the start page that is.)

I could mail you the adress to the actual page if that would help.

@Imerion please do, you can do it to<EMAIL_ADDRESS>I'll be debugging this.

To make it easier, you can do a clean install and copy over the theme from your current website to the subfolder where you can check the 3.1.4 version.

I also updated the summernote editor plugin, simple statistics plugin and additional contents plugin, as well as the theme, but that was after updating to WonderCMS 3.3.0. So the problem appeared before I updated anything else.

While inspecting your website, it seems the mailbox icon would be fixed by just adding a "/" in the path, example:
changing
src="data/files/Mail_icon.png"
to
src="/data/files/Mail_icon.png".
as this is the correct path in relation to the domain.
Still not sure where the problem lies. Can you provide another example with other images?
I would be really interested to see how this worked on WonderCMS 3.1.4.

Right, that part with the mail icon was easy. :)
Perhaps the problem is with how the parallax theme handles backgrounds then. Because in my database.js I have an entry like this for every page:
"page": {
  "title": "Page name",
  "keywords": "keywords",
  "description": "Description",
  "content": "
Content here.<\/p>",
  "background": "image.jpg"
},

And here I can't really do:
"page": {
  "title": "Page name",
  "keywords": "keywords",
  "description": "Description",
  "content": "
Content here.<\/p>",
  "background": "/data/files/image.jpg"
},

Because that results in the image pointing to: https://www.pagename.com/page/data/files//data/files/image.jpg

@Imerion is there any chance you could pack up the theme in a ZIP file and send it over?
I'd like to compare the 3.1.4 and 3.3.0 changes to see what went wrong and how this worked before.

I have sent you archives with the theme before and after the update. I hope it helps. Sorry for all the trouble!

@Imerion can confirm I've received it and debugging this further.
Currently it does seem something in the index.php is affecting this. Will let you know back with some results.
Thanks for helping debug this, seems like we should be able to figure it out and push out a fix.

@Imerion found a fix you can apply immediately.
On line 2367, replace the line
		$parentSlug .= $item->slug . '/';
with
		$parentSlug .= $item->slug;
Will do some more testing to make sure subpages aren't broken, however this solved the issue you have.

That solution worked, thanks!
As the site doesn't use subpages this will solve my problem for now. But tell me if I can help you any further with debugging, and again I thank you for taking your time with this!

@Imerion most welcome, this isn't a full blown solution just yet. Will update the thread.
You're welcome and likewise, thank you as well for helping debug this and sending over the files.

@Imerion got a solution that fixes all issues and supports subpages.

Awesome! I can confirm it works fine here.

@Imerion thank you.
WodnerCMS 3.3.1 publishes and updates should be available with this fix for all WonderCMS users soon.
Glad to close this issue, feel free to repen it if necessary.


Cannot propose new LICENSE file in PR for repost without write permission despite forking

When trying to open a license pull request on projects that I don’t own, I have encountered the following error.

You’re making changes in a project you don’t have write access to. Submitting a change will write it to a new branch in your fork brylie/Dash-Fractal-Explorer, so you can send a pull request.

At that point, I am unable to propose the new file since the primary repository is still selected instead of my fork, which was automatically created. How can I select my fork instead of the primary repository so I can submit the pull request?
Steps to reproduce

choose a repository to which you don’t have wire access
copy the repository URL
choose a license on choose a license.com
paste the repository URL into the input: “Enter a GitHub repository URL”
review and submit the license template
on the “New File” screen, observe that the “Propose new file” button is deactivated and the primary repository is selected instead of your fork

Thanks, I'm able to reproduce this. Seems like step 6 is a behavior (presumably a bug) that did not occur at some point in the past. I'll see what I can figure out.
In the meantime you could just go to the target repo, click "add file", name the file LICENSE, paste in the relevant license text -- and the "propose new file" button will be green (also just tested). That's all the steps above should be a UI over.

This was fixed at some point in last 11 months. Closing now, feel free to reopen if it breaks or is still broken!


🚀 Feature Request: Add Filtfilt (scipy.signal.filtfilt equivalent)

🚀 Feature

Add utility filtfilt to torchaudio.functional. This utility applies lfilt twice: in forward and backward direction, so phase of resulting signal is preserved. This function exist for example in scipy (see their docs) and is frequently used in signal processing.
Motivation

I frequently need this function, so I've already wrote and tested it, so I would make a PR to include it to core library.
Pitch

Add bidirectional filtering function filtfilt commonly used in signal processing.

Hi @v-goncharenko
Thanks for the suggestion. I do not have anything against adding this to torchaudio, especially if it's well tested. @vincentqb your thoughts?
If your existing code is publicly available, can I take a look at it?
Adding code to torchaudio will likely to have different requirements for testing. You can read about it here. This case, we will need to add new type of test (spicy compatibility).

Question: the spicy doc says

The function sosfiltfilt (and filter design using output='sos') should be preferred over filtfilt for most filtering tasks, as second-order sections have fewer numerical problems.

What's your take on this one? I am not familiar with these functions so would like to hear your opinion.

Thanks for the suggestion. I do not have anything against adding this to torchaudio, especially if it's well tested. @vincentqb your thoughts?

Yup, I'm ok with having this in torchaudio too @mthrok :) As usual, testing will need to ensure that the implementation support batch, torchscript, and correctness. It may be a good idea to have some testing around numerical stability given @mthrok's observation.
@v-goncharenko, please feel free to open a pull request for this!

Adding code to torchaudio will likely to have different requirements for testing. You can read about it here. This case, we will need to add new type of test (spicy compatibility).

My tests aimed to check scipy compatibility. And of course I'm ready to write some more if needed.

What's your take on this one? I am not familiar with these functions so would like to hear your opinion.

Well, this requires sosfilt to be implemented, but now we have only lfilter, so this is topic for another issue and PR.

@v-goncharenko, please feel free to open a pull request for this!

Sure! Hope I'll have some time during this weekend.


The specified module 'Boxstarter.Chocolatey' was not loaded...How to solve it?

Hi,
I encounter the following error message in log file when I install flareVM. But this error doesn't block the installation process. I want to know how to solve the error message.

2020-09-19 21:38:17,143 1252 [DEBUG] - ---------------------------Script Execution---------------------------
2020-09-19 21:38:17,149 1252 [DEBUG] - Running 'ChocolateyScriptRunner' for flarevm.installer.flare v<IP_ADDRESS> with packageScript 'C:\ProgramData\chocolatey\lib\flarevm.installer.flare\tools\chocolateyinstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\flarevm.installer.flare', installArguments: '', packageParameters: '',
2020-09-19 21:38:17,162 1252 [DEBUG] - Running 'C:\ProgramData\chocolatey\lib\flarevm.installer.flare\tools\chocolateyinstall.ps1'
2020-09-19 21:38:18,413 1252 [ERROR] - The specified module 'Boxstarter.Chocolatey' was not loaded because no valid module file was found in any module directory.
2020-09-19 21:38:18,661 1252 [ERROR] - The specified module '\Boxstarter.Common\boxstarter.common.psd1' was not loaded because no valid module file was found in any module directory.
2020-09-19 21:38:18,681 1252 [INFO ] - VERBOSE: Loading module from path 'C:\ProgramData\FEVM\FireEyeVM.common\FireEyeVM.common.psm1'.

Can someone help me? Many thanks in advance !

@Wesly-Zhang, It looks like there was some installation issue with BoxStarter. MyGet has some network issues a few weeks back that breaks all of our installs. Can  you give it another try and let me know if  you still have error with BoxStarter?
Thank you,

Hi, @htnhan Thanks for replying me. It look like OK now.
Regards.


Create a module for the frontend of the endpoint function

Fixes #27

Codecov Report

Merging #33 (c3b6cf6) into main (2953bb3) will decrease coverage by 3.07%.
The diff coverage is 66.66%.

@@             Coverage Diff             @@
##              main      #33      +/-   ##
===========================================
- Coverage   100.00%   96.92%   -3.08%
===========================================
  Files            4        5       +1
  Lines           59       65       +6
===========================================
+ Hits            59       63       +4
- Misses           0        2       +2

Impacted Files
Coverage Δ

hvpy/facade.py
66.66% <66.66%> (ø)

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 2953bb3...c3b6cf6. Read the comment docs.


[FEAT] Create a new fun website

Is your feature request related to a problem? Please describe.
I'm frustrated with only two websites ......... dice generally have 6 sides don't they.
Describe the solution you'd like
More fun websites !!!!!!!!
Describe alternatives you've considered
Getting bored.

Hello, assign me to this issue.


feat: drop distributed Mito2 table

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Drop distributed Mito2 table.
If "engine = mito2" is in the table info, drop the Mito2 table. Otherwise drop the original Mito table.
Note that since the Mito2 region is not able to be actually created on Datanodes now, there are no complete drop Mito2 table tests. I only mock the region server's grpc interfaces in the unit tests. Once the region server is ready on Datanode, it's easy to really test it.
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)
#2254

@WenyXu PTAL

@waynexia PTAL


Fix bug when adding No Progress as a progress

Also updated class diagram for Student

Codecov Report

Merging #283 (bcb26ab) into master (1a5570d) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #283      +/-   ##
============================================
- Coverage     58.02%   58.01%   -0.02%
+ Complexity      679      678       -1
============================================
  Files           131      131
  Lines          2585     2584       -1
  Branches        273      272       -1
============================================
- Hits           1500     1499       -1
- Misses          986      987       +1
+ Partials         99       98       -1

Impacted Files
Coverage Δ

...main/java/tutoraid/model/student/ProgressList.java
72.91% <100.00%> (+1.48%)
:arrow_up:

src/main/java/tutoraid/model/student/Progress.java
66.66% <0.00%> (-6.67%)
: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 1a5570d...bcb26ab. Read the comment docs.


Add Capital (CALL)

Currency name: Capital
Symbol: CALL
Website: https://www.mycapitalco.in
Theme color: #fbb413
Logo (SVG): https://www.mycapitalco.in/assets/vectors/call.svg
Logo (AI): https://www.mycapitalco.in/assets/vectors/call.ai

Transparent is not your theme color. I would say your theme color is #fbb313 (yellow).

@sindresorhus My mistake, the theme color is: #fbb413


Please Read Concerning SSGI Implementation and Performance

You don't need to have SSAO or GTAO on since SSGI is meant to replace those AO solutions,. You can verify this in-game with the console.
The reason I bring this up is because if you leave SSAO/GTAO on, it will affect performance even though SSGI overrides those effects. That's just how the graphical pipeline is set up.
If the user is running both GTAO/SSAO and SSGI at the same time it will tank performance. You can test the performance gains in-game by using r.AmbientOcclusionLevels and setting it to 0 to disable AO in. You will see that you get a huge performance boost without any changes to graphical fidelity.
You can further test this by turning off SSGI using 'r.SSGI.Enable 0' in the console and turning r.AmbientOcclusionLevels to
turn the old AO on and off.
Below is a slider with to show there are no changes other than a huge performance boost (24FPS gain in this instance.)
SSGI+GTAO vs SSGI Only
This is with using:
@5120x2880
r.ssgi.enable=1
r.ssgi.quality=2
r.ssgi.halfres=1
GTAO was set to Full Resolution

Thanks for the Info.

can you make more openworld GTAO vs SSGI comparison screenshots? ty

Added an option to disable AO in v0.9.0.


Consider Prometheus integration

Export metrics in prometheus-compatible format
It would be great to have prometheus (https://prometheus.io) metrics exposed in lxd. It currently seems to be the most popular out there, but it's line based format for holding metric names + tags seems like a fairly future-proof choice.
I understand if lxd doesn't want to integrate with a particular piece of software, but if you're going to support monitoring, why not support a popular tool?
If there's interest, I'm happy to submit a PR.

For clarification I mean existing metrics from lxc info $name

This isn't something LXD can do. The metrics you see in "lxc info" are retrieved from the kernel at the time you make the API call. Those kernel calls are very expensive so doing that on a timer basis would be a very bad idea.
In most cases, what you want is to run something like telegraf inside the container, pushing to your prometheus. It's still not cheap as far as kernel resource consumption, but is already significantly better than asking LXD to attach/detach to containers constantly.

This seems out of scope for us and @stgraber has provided a nice alternative. Closing for now. :)


fix(jwt source): cookie from request

fix(jwt_source): JwtSource::Cookie should take the cookie from request (fixes #9)

the token cookie should be taken from request not from the tower-cookies middleware jar
dependency on tower-cookies is not anymore needed

See https://github.com/cduvray/jwt-authorizer/issues/9#issuecomment-1497269378


feat: Allow external iris for property and resource class when updating doap (DEV-4341)

deprecated: Deprecate endpoints for updating a Default Access Permission in favor of newly introduces PUT /admin/permissions/doap/:permissionIri endpoint
Deprecated endpoints:

PUT /admin/permissions/:permissionIri/resourceClass
PUT /admin/permissions/:permissionIri/property
PUT /admin/permissions/:permissionIri/group (deprecated only for DOAPs)
PUT /admin/permissions/:permissionIri/hasPermission (deprecated only for DOAPs)

Pull Request Checklist
Task Description/Number

Issue Number: DEV-
PR Type

[ ] build/chore: maintenance tasks (no production code change)
[ ] docs: documentation changes (no production code change)
[x] feat: represents new features
[ ] fix: represents bug fixes
[ ] perf: performance improvements
[ ] refactor: represents production code refactoring
[ ] test: adding or refactoring tests (no production code change)
[ ] deprecated: Deprecation warning (ideally referencing a migration guide)

Basic requirements for bug fixes and features

[ ] Tests for the changes have been added
[ ] Docs have been added / updated

Does this PR introduce a breaking change?

[ ] Yes

I have added a new endpoint PUT /admin/permissions/doap/:permissionIri which allows for updating an existing doap. This is deprecating existing endpoints as described above. I also updated the documentation.
Please have another review.

Forgot to ask. Should this PR be marked actually as deprecated instead of feat?


"Option: Vocals will not be separated" isn´t working

He Guys, after my first issues, which were solved quickly i play a bit here and there to see and understand different settings.
The tool is really great and maybe some input / questions will help to get it better and stable for further versions.
I tried to use "Option: Vocals will not be separated" by using mode --interactive. But after a while program still separate vocals from audio. Output says:
"Separating vocals from audio with demucs with model htdemucs and cpu as worker
Selected model is a bag of 1 models. You will see that many progress bars per track"
Isn´t it working or is it needed when setting Karaoke txt file?
Also some other outputs I,m not sure if they are okay if i need to do something / adjust on scripts
Loading whisper with model large-v2 and cpu as worker
Lightning automatically upgraded your loaded checkpoint from v1.5.4 to v2.3.3. To apply the upgrade to your files permanently, run python -m pytorch_lightning.utilities.upgrade_checkpoint E:\UltraSinger\.venv\lib\site-packages\whisperx\assets\pytorch_model.bin
Model was trained with pyannote.audio 0.0.1, yours is 3.1.1. Bad things might happen unless you revert pyannote.audio to 0.x.
Model was trained with torch 1.10.0+cu102, yours is 2.0.1+cpu. Bad things might happen unless you revert torch to 1.x.
Pitching with crepe and model full and cpu as worker
2024-12-28 16:10:40.250062: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
Keep going on, it is really a great tool

Thanks mate 😃
The --disable_separation is only for the pipeline. So whisper and crepe will use the full audio instead only the vocals.
It will still output seperate vocal and instumental files.
I think you want --disable_karaoke, which do not output instrumental and vocals files.
For those warnings. I know them. But downgrading these packages would lead to more issues 🤣


train error  ValueError: Caught ValueError in DataLoader worker process 0

非常感谢您公布成果，对我的学习提供了很大的帮助，很感激您的工作，我目前遇到了一些问题，我在执行
python tracking/train.py --script stark_s --config baseline --save_dir . --mode multiple --nproc_per_node 4 时，出现了错误，显示ValueError : Caught ValueError in DataLoader worker process 0
由于设备有限，训练集，我没有加上trackingnet，是否是我没有修改一些配置。望您有空帮我解答，再次非常感谢您。
Thanks for your good job！ I have tried to recurring your final results, but I failed。
when i use
python tracking/train.py --script stark_s --config baseline --save_dir . --mode multiple --nproc_per_node 4
There was an error
ValueError : Caught ValueError in DataLoader worker process 0
Due to limited equipment, I did not add trackingnet in training set, whether I did not modify some configuration.I hope you have time to help me out. Thank you very much again.

did u solve this error?

@Howdy-Personally yes，this is a parameter problem

I have met this problem. Could you tell me the reason of this problem?

@Howdy-Personally I would also kindly ask that you share the solution to the problem please :)


[WIP] Setting up CI for dotnet/core

Starting work to hook up CI Integration in to Jenkins.
Blockers right now:

[ ] non-existent / incomplete docker test script (on me @bryanar)
[x] Setting up push/pull webhooks on repository (on @terrajobst)
[ ] Approving pre-req PR #326 (on @mattellis)

@markwilkie

test ci please

test ci please

test this please


reorg of lysine/peptidyl-lysine acetyltransferase terms; NTR?

I got a bit confused trying to use the GO:0052858 and GO:0090595 terms.  As far as I can tell, there are two issues: whether one substrate is lysine vs. peptidyl-lysine, and whether the other substrate is acetyl phosphate vs. acetyl-CoA.
GO:0090595 is currently defined as using lysine rather than peptidyl-lysine; part of the definition is the MetaCyc reaction LYSACET-RXN, which is involved in lysine degradation.  However, in GO, this term has a bunch of histone acetyltransferase activity children, where peptidyl-lysine is modified.  This relationship seems wrong.
On the other hand, the GO:0052858 term is defined as having peptidyl-lysine as one substrate, but acetyl-phosphate as the other.  As far as I can tell from reading around the E. coli literature a bit, the peptidyl-lysine modification with acetyl phosphate occurs spontaneously and doesn't require an enzyme (though I may be wrong, now or in the future).
However, there is a peptidyl-lysine acetyltransferase enzyme (e.g. PMID 26251518 in E. coli, 12493915 in Salmonella) that uses acetyl-CoA as the donor.  This may also be the same kind of enzyme that modifies the histones, i.e. the histone acetyltransferase activity GO:0004402 + children terms may really belong there.  I realize that the E. coli enzyme currently has annotations to both GO:0052858 and GO:0004468, and both are wrong...
So my proposal: create a new term for peptidyl-lysine acetyltransferase using acetyl-CoA as the donor, and move the histone acetyltransferase terms to become children of that term (but please check that I'm not wrong about the histone stuff...).
Thanks,
Ingrid

Hi Ingrid,
I have created the suggested term and moved the histone and tubulin acetyltransferases as children of it. I can see no evidence that what you suggest is incorrect. Please let me know if you see any further issues.
[Term]
+id: GO:0061733
+name: peptide-lysine-N-acetyltransferase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: acetyl-CoA + lysine in peptide = CoA + N-acetyl-lysine-peptide." [GOC:dph]
+is_a: GO:0034212 ! peptide N-acetyltransferase activity
+created_by: dph
+creation_date: 2015-09-10T10:22:19Z
-David


Orphaned docker container continues to live on after daemon is killed

After upgrading to Docker 1.7.1 (from 1.5.0) I consequently killed/restarted the Docker daemon (through upstart: service docker restart) and started seeing strange behaviours when starting new containers on the new daemon. Most prominent was it that 50% of our requests to HAProxy were dropped with 503 errors, but with no logs or traces of this in the HAproxy container that we ran and exec'd into running docker exec. Here's an example of what we saw, port 1012 is just a random HTTP service under HAProxy:
# for i in {1..100}; do curl -I -s http://<IP_ADDRESS>:1012/ | head -n 1; done
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.0 503 Service Unavailable
HTTP/1.1 200 OK
HTTP/1.0 503 Service Unavailable

Now, after a good amount of debugging I traced the issue down after running the following command on the host system:
# sudo netstat -tulpn | grep 1012
tcp        0      0 <IP_ADDRESS>:1012            <IP_ADDRESS>:*               LISTEN      6256/haproxy
tcp        0      0 <IP_ADDRESS>:1012            <IP_ADDRESS>:*               LISTEN      3382/haproxy

The HAProxy container is running in host network mode, but I was not expecting to see two processes bound to port 1012 at all!
Using ps auxf I can see that PID 6256 is indeed running as a child of the docker daemon process, but 3382 is owned by PID 1 and seems to be the old HAProxy container from Docker 1.5.0. Is this the consequence of a potentially failed graceful shutdown of the docker container?

In any case, it all worked after I did kill 6284 which was the PID of the init system in the orphaned process (see screenshot).
Tips on how to avoid this happening again would be greatly appreciated, as the consequences in many cases are very subtle.

I can see this happening if HA Proxy became a zombie if the container was started and HA Proxy wasn't PID1 (And PID1 in the container didn't waitpid on it).
Also could be a bug in docker 1.5 with host networking mode...

HAProxy was started through "marathon" which in turn communicates with Mesos. Mesos is then the actual executor of the docker command, I reckon. In terms of config options, the only ones passed into Marathon+Mesos and thus the daemon were:
--volume /data/haproxy:/local/haproxy:ro and --net=host.
But as I'm using the phusion/baseimage image HAProxy wasn't PID1, and it could be that the /sbin/my_init didn't waitpid it. As I mentioned though it was started on a Docker 1.5.0 daemon, so for all I know (and if you say so) it could be related to a bug in the host networking mode on that version.
If you want you can close this, and I'll re-open it if I experience the same on 1.7.1? :)

Because of the recent changes with docker if you are still running into this issue please reopen it.
We now have features like live-restore that allows containers to live after the daemon is killed and the default handling for containers has been improved.
Thanks!


I wanna add tic tac toe game using html css and javascript for webdevelopment beginner projects

Initiative (Required)
Hacktoberfest 2024 🎃
Additional Info
This is a simple Tic Tac Toe game built using HTML, CSS, and JavaScript. The game allows two players (O and X) to play against each other on a 3x3 grid. The game detects the winner or a draw, and provides a reset option to play again.

I am the mentor of this project.
@rahul-chakradhari Hello Thank you for opening the pull issue and you can opening new issue by creating the new concept those are not exist in the project !!
@Kushal997-das kindly close the issue since it already exist in our project.


feat: Add ExponentialBackoffRetry and update eventHubs.maxEventBatchSize [PAGOPA-1845]

List of Changes

Add ExponentialBackoffRetry for retry When exceptions occur such as those related to the Throttling of requests to cosmos
Update host.json: decrease maxEventBatchSize for each dequeue from EventHub
Update LOG with more info :todo!:

Motivation and Context

Improve reliability and manual fault detection

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

resolved by https://github.com/pagopa/pagopa-biz-events-datastore/pull/74


[bug]: INFO:     <IP_ADDRESS>:17778 - "POST /api/v1/sessions/ HTTP/1.1" 422 Unprocessable Entity

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
No response
What version did you experience this issue on?
v3.0.0+a3
What happened?
When trying to generate a photo, the 'Server Error' is displayed in GUI and ' INFO:     <IP_ADDRESS>:17778 - "POST /api/v1/sessions/ HTTP/1.1" 422 Unprocessable Entity' in error log console.
Screenshots

Additional context
Windows 11, Edge Chromium, 64-bit.

Why closed as a problem is still present?

Closed because this is most likely a configuration error. There is insufficient information to reproduce the reported issue

Closed because this is most likely a configuration error. There is insufficient information to reproduce the reported issue

Error was active in  3.0.0-alpha 3 release and also after upgrading to alpha 4. After that I deleted the whole invokeai folder, reistalled Python and installed alpha 4 from zero. Now I have alpha 6 and problem is still present. At the moment I'm downloading models and will check for console error later.

We have plenty of people using the alpha without this issue - I'm not proposing that you aren't experiencing the issue, but without more information to reproduce it reliably on other systems, we're not going to be able to "fix" it.
An 'unprocessable entity" means that something that's being submitted to the graph/execution engine is invalid and not constructed correctly. We're planning on making this more explicitly detailed to provide visibility into what, exactly is invalid.
Can you share more about the settings you're using that result in this error?

LOL, I just had to download and install models...

That would do it. :)


Inconsistency in predicate-based map axioms when using MBQI

While investigating this Dafny issue, I discovered that Boogie seems to be generating map axioms when using the predicate-based encoding for polymorphic types that are inconsistent when MBQI (which is disabled by default) is enabled in the solver. Take the following Boogie program, distilled from the original Dafny example.
type ref;
type Field _;
type Heap = [ref]<alpha>[Field alpha]alpha;
function $IsGoodHeap(Heap) : bool;
function $IsHeapAnchor(Heap) : bool;
var $Heap: Heap where $IsGoodHeap($Heap) && $IsHeapAnchor($Heap);

procedure P()
{
    assert false;
}

When running with the various type encoding flags, and MBQI enabled, I get the following.
$ boogie issue-4053-pruned-prefix.bpl /proverOpt:O:smt.mbqi=true /typeEncoding:p

Boogie program verifier finished with 1 verified, 0 errors
$ boogie issue-4053-pruned-prefix.bpl /proverOpt:O:smt.mbqi=true /typeEncoding:a
issue-4053-pruned-prefix.bpl(10,5): Error: this assertion could not be proved
Execution trace:
    issue-4053-pruned-prefix.bpl(10,5): anon0

Boogie program verifier finished with 0 verified, 1 error
$ boogie issue-4053-pruned-prefix.bpl /proverOpt:O:smt.mbqi=true /typeEncoding:m
issue-4053-pruned-prefix.bpl(10,5): Error: this assertion could not be proved
Execution trace:
    issue-4053-pruned-prefix.bpl(10,5): anon0

Boogie program verifier finished with 0 verified, 1 error
$

Is there some reason it should be expected that these axioms are incompatible with MBQI? And is that why it's disabled by defalut?
Running various solvers on the generated SMT-Lib, several versions of Z3, CVC5, and Vampire all report unsat. This happens when enabling MBQI in Z3 or CVC5, and when using Vampire with its default flags. Using Z3 or CVC5 with MBQI disabled results in unknown.

The comment from @RustanLeino here suggests how to fix the issue.

Is there some reason it should be expected that these axioms are incompatible with MBQI?
I read the explanation by @RustanLeino. It sounds like the root cause is an inconsistency bug in the type encoding implemented in Boogie. The inconsistency remained hidden because of the incompleteness of quantifier reasoning in typical SMT solvers. Turning MBQI on reduces incompleteness in some examples and revealed the inconsistency.

And is that why it's disabled by default?
No. Z3 has many users. It's world does not revolve around Boogie and Dafny, as no doubt @NikolajBjorner will remind you. I suspect that the reason MBQI is turned off by default is that it is expensive.

The comment from @RustanLeino here suggests how to fix the issue.

Great! I am glad a fix has been discovered. I encourage the Dafny community to put up a PR so we can land the fix pronto. I also encourage the inventors of Boogie type encoding to think about whether other similar bugs are lurking in there. An old-fashioned method is a proof of soundness.

And is that why it's disabled by default?

No. Z3 has many users. It's world does not revolve around Boogie and Dafny, as no doubt @NikolajBjorner will remind you. I suspect that the reason MBQI is turned off by default is that it is expensive.

Oh, I meant that Boogie disables it by default. Z3 doesn't.

The comment from @RustanLeino here suggests how to fix the issue.

Great! I am glad a fix has been discovered. I encourage the Dafny community to put up a PR so we can land the fix pronto. I also encourage the inventors of Boogie type encoding to think about whether other similar bugs are lurking in there. An old-fashioned method is a proof of soundness.

I'm happy to take a stab at implementing @RustanLeino's suggested fix, and may be able to do some deeper soundness investigations a bit later.

Regarding Z3's default, here's my understanding:  By default, Z3's auto-config mode in on. In the auto-config mode, Z3 scrutinizes its input and determines what quantifier mode to use. In some cases, that mode may end up being MBQI. If you manually turn auto-config off, then Z3 defaults to MBQI. So, if you really don't want MBQI, you have to turn off both auto-config and smt.mbqi. Boogie does that.

I also encourage the inventors of Boogie type encoding to think about whether other similar bugs are lurking in there. An old-fashioned method is a proof of soundness.

Hehe. Of the two things I mentioned here, the missing parameter(s) of the type constructor seems like a coding bug. (I didn't study the Boogie code just now.) @pruemmer and my paper has all the parameters of Ctor (see section 2.0 of https://leino.science/papers/krml199.pdf).
The missing antecedent is a logic bug. Looking at the "Function axiom" paragraph of Section 3.0 of the paper, the bug seems to be that an \alpha could occur more than once among s_1, ..., s_n. Formula (0) fails to capture any correspondence between multiple occurrences of such an \alpha, which is the problem here. That is, the TypeMap2Store function should have signature
function TypeMap2Store<A, B>(m: [A]B, a: A, b: B): [A]B;

(Here, I declare TypeMap2Store using Boogie syntax, even though this particular function is one that is built-in in Boogie. And, for clarify, I wrote A and B for instead of \alpha_1 and \alpha_2.)

Ehm, z3 may not revolve around Boogie, but my world certainly revolves around Stan U R.

s that are inconsistent when MBQI (which is disabled by default) is enabled in the solve

oh that one. We hit this when trying Vampire many years ago.

An old-fashioned method is a proof of soundness.

you mean?

There is another type encoding method that is triggered by -typeEncoding:arguments. Is it possible that this bug is lurking there also?
If -typeEncoding:arguments is not used by anybody, should be consider deleting it?

As a side remark, our CAV 2021 paper (https://link.springer.com/chapter/10.1007/978-3-030-81688-9_33) generates proofs for a subset of polymorphic Boogie where -typeEncoding:predicates is used (Viper also uses -typeEncoding:predicates). The subset does not cover maps, but for the basic subset including type quantification and polymorphic functions the paper provides confidence that -typeEncoding:predicates is sound (note that the paper does not give a once-and-for-all proof but generates proofs for successfuls runs of Boogie for the concrete input programs). One could use this work as a starting point to increase confidence of the map encoding.
Regarding typeEncoding:arguments: I don't know the encoding in detail, but if I remember correctly, the encoding relies quite heavily on triggers. I'm not sure if the soundness also relies on triggers. If the soundness relies on triggers, then proving soundness of -typeEncoding:argument seems hard, because the Boogie semantics would have to depend on triggers and as far as I know there has not been much work on such a semantics (in our paper, triggers do not affect the semantics).
Just playing around a bit with typeEncoding:arguments I found one example, where the typeEncoding:arguments seems to have a bug (without using maps):
type Foo _;
type Bar _;

function elem<T>() : Foo T;

procedure p() {
    var y1: Bar int, y2: Bar int;

    //every type Foo T consists of exactly 1 element
    assume (forall <T> x: Foo T :: (x == elem()));

    //Bar int consists of at least two elements
    assume y1 != y2;

    /* we should not be able to prove false (there exists a universe that satisfies both assumptions) */
    assert false;
}

The type quantifier in the SMTLIB2 file is given by: forall ((x@@8 T@U) (T T@T) ) (! (= x@@8 (elem T), which is essentially saying that every type has only one element (it ignores the Foo type constructor). As a result, in theory the assert false at the end could be proved, because there is a universe where Bar int has at least two inhabitants (in practice the Boogie cannot prove it). I am not sure if this is a bug or if I am misinterpreting something.

One relevant snippet from the original paper:

It has to be noted that this second translation [the argument-based translation] crucially depends on the usage of an SMT solver with e-matching: such solvers are not able to exploit missing type guards, because typing information is inserted in expressions in such a way that triggers can only match on expressions of the right type. The translation trades generality for performance: while it is not applicable with most first-order theorem provers (e.g., superposition provers), the experimental evaluation in Section 4 shows a clear performance gain compared to the type guard translation from the previous section.

To me this sounds like a completeness question rather than a soundness one.

Is there a model theory of a logic with triggers?

Is there a model theory of a logic with triggers?

I have not explored the formal details of triggers much, but there is the paper "Reasoning with triggers (Claire Dross, Sylvain Conchon, Johannes Kanig, and Andrei Paskevich; SMT@IJCAR 2012)", which defines a semantics that takes triggers into account.

@atomb : Can I close this issue?

I think a different issue makes sense. I'll create one.


Update iban_rules.rb

because I want to read yaml without any modification of regexp as is on line 23

@iulianu pls merge :)