Strongly-typed contracts

Is there a way to currently (or in the future) make the contract aware of the functions it supports? Example:

Thanks to TypeChain we have a generated contract type which would be as follows for the example above:
start_time(
  overrides?: CallOverrides
): Promise<{
  0: BigNumber;
}>;

I'm thinking there might be a way to pass it to the Contract class if we make it generic — taking contract type as a type argument.

It would be great to see it natively supported by the package.
Till then, we can do like this:
const contract = new MulticallContract(address, ABI) as unknown as ContractType

It would be great to see it natively supported by the package.
Till then, we can do like this:
const contract = new MulticallContract(address, ABI) as unknown as ContractType

Will return value have type also in this expression?

It would be great to see it natively supported by the package.
Till then, we can do like this:
const contract = new MulticallContract(address, ABI) as unknown as ContractType

Will return values with typed in this expression when calling provider.all?

Sadly no. You'd have to provide the return datatypes manually to .all as shown above


feat: Add schema support to pgvector document store.

Proposed Changes:
Add schema support to the  pgvector document store.
You can now specify a schema for tables to be created in.
Manually tested these methods:

__init__
write_documents
delete_documents
filter_documents
delete_table

For manual tests, set the schema_name attribute, eg.:
document_store = PgvectorDocumentStore(
    schema_name="mysch",
    table_name="mytab",

    ...
)

Notes for the reviewer
The schema must already exist in the database.

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

@rblst the idea sounds reasonable.
Can you fix the failing tests?


Is there a way to let the prompt only show the first letter of each directory?

Is there a way to let the prompt only show the first letter of each directory?
e.g. /c/r/g/b/y/b/whiteif the working directory ls /color/red/green/blue/yellow/black/white,

You can use the shrink_path plugin and adapt your theme with it. See the README for details: https://github.com/robbyrussell/oh-my-zsh/blob/master/plugins/shrink-path/README.md .


remove not found tests for https://github.tools.sap/kc/kc/issues/412

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes https://github.tools.sap/kc/kc/issues/412
Special notes for your reviewer:
Release note:

partially remove non-existing tests

Hi @andrei-panov, is this PR ready for review or are you going to amend changes (I noticed that you pushed more test removals recently to this PR)?

Hi @dguendisch
Sorry for the noise but it's not ready yet. We discuss it yesterday and some more work required.

No prob, you can just file a draft PR in such cases (I converted this PR now into a draft, just convert it back when it's ready).

Hi @dguendisch, it's ready for review.

Please merge it if it's fine. I don't have permission.


Libsql transactions

This PR introduces transactions in libsql client using http+json. It introduces a Hrana concept of HttpStream, which is opened for sequential execution of subsequent requests.

If you don't mind guys, unless you have some strong opinions and must-fix remarks about existing code, we could resolve remaining questions in subsequent PRs. I don't think it's good to have this PR rot. I've created a #723 for topics opened but not covered here.


Why int16 for numbers?

Isn't js using up to 50ish bits for numbers?
All bit-operations use 32 bit, so why not int32?

because the main goal of this project is to support low power microcontrollers, and there are some 16-bit microcontrollers out there that don't support 32 bit numbers at all. JavaScript of course operates mainly on 32-bit numbers (and 64-bits are also supported in later versions of standard).


Two WLAN-Devices and two HMS-800W-2T on one Raspi #27

          Thanks.

But sorry, this doesn't work. Independent from the setting at "--local_addr" it requests server every time on wlan1 (<IP_ADDRESS> -> <IP_ADDRESS>) but sadly never wlan0 (<IP_ADDRESS> -> <IP_ADDRESS>)
Not working (wlan0, requests wlan1 instead):
./hoymiles-wifi --host <IP_ADDRESS> --local_addr <IP_ADDRESS> --as-json get-real-data-new
working (wlan1);
./hoymiles-wifi --host <IP_ADDRESS> --local_addr <IP_ADDRESS> --as-json get-real-data-new
Originally posted by @Jo-Bl in https://github.com/suaveolent/hoymiles-wifi/issues/27#issuecomment-2345712890

Thanks for the feedback. That is weird indeed.
What about if you enter a non existend interface, e.g. <IP_ADDRESS>? To you still get a response?

I'm only seeing your answer now, sorry.
I'm now using the two HMS-800W-2Ts with two Rasps.
But I was able to test it with only wlan0 and eth0 interfaces, if I remember correctly: Then no data query is possible with an incorrect IP. But if wlan0 and wlan1 are present, then a query with an incorrect IP is possible. As I said: I can't test that at the moment because I'm now working with two Rasps. Sorry.

Thanks for letting me know.
by the way: you can also connect the inverter directly to your WiFi router. So you can query both inverters with one raspberry too.

You wrote:

you can also connect the inverter directly to your WiFi router

Aha, how?
I do not found an option about that connecting to my router in the android app "S-Miles Installer"

I do not want any cloud between/around me and the inverters.
And - second - the inverters are never allowed to go online themselves.
The connection of Hoymiles(-support, - updater) to the inverters must remain prevented

Is this possible than, if the interters are connected to the router?

You can set the wifi network of the inverter via the set-wifi command. This allows you to connect the inverter to your main wifi. Then you can use the IP address from the main router to query your inverters as before.
To prevent the inverter from communicating with hoymiles servers you need to create a firewall rule in your router.
I have set up my inverter this way.
The only issue which arises from this setup is that the inverter sometimes is not reachable (presumably due to it trying to connect to the Hoymiles server at this time).
Also bear in mind: There might be some wifi stability issues if you have never update the firmware up until now (I'm working on an offline approach to do so, but it does not work as of this moment).

You can set the wifi network of the inverter via the set-wifi command.
I know that (thanks for implement this), but I don't want it.

Reasons:

To prevent the inverter from communicating with hoymiles servers you need to create a firewall rule in your router.
The only issue which arises from this setup is that the inverter sometimes is not reachable (presumably due to it trying to connect to the Hoymiles server at this time).
There might be some wifi stability issues if you have never update the firmware up until now

So I preferr AP mode and will stay on this mode for both inverters.

(I'm working on an offline approach to do so, but it does not work as of this moment).
Thanks for this!

I see makes sense :)
There are two reasons for the disconnects:

old firmware is buggy. You need to update to the latest firmware to improve WiFi stability
Offline mode, as described above.

2024-09-15T12:48:29|get-real-data-new|No response or unable to retrieve response for get-real-data-new
2024-09-15T12:49:23|get-real-data-new|{"deviceSerialNumber":.... 2024-09-15T12:50:11|get-real-data-new|{"deviceSerialNumber":... 2024-09-15T12:50:58|get-real-data-new|{"deviceSerialNumber":....
2024-09-15T12:51:45|get-real-data-new|No response or unable to retrieve response for get-real-data-new
2024-09-15T12:52:37|get-real-data-new|{"deviceSerialNumber":...
2024-09-15T12:53:25|get-real-data-new|{"deviceSerialNumber":...

2024-09-15T12:48:29|get-real-data-new|No response or unable to retrieve response for get-real-data-new 2024-09-15T12:49:23|get-real-data-new|{"deviceSerialNumber":.... 2024-09-15T12:50:11|get-real-data-new|{"deviceSerialNumber":... 2024-09-15T12:50:58|get-real-data-new|{"deviceSerialNumber":.... 2024-09-15T12:51:45|get-real-data-new|No response or unable to retrieve response for get-real-data-new 2024-09-15T12:52:37|get-real-data-new|{"deviceSerialNumber":... 2024-09-15T12:53:25|get-real-data-new|{"deviceSerialNumber":...

That looks a lot like the output I would expect if run in offline mode. So in the end it probably doesn’t really matter if you use AP mode or offline mode.

Yes.

Yes, I’m still investigating. Will probably run some tests on a rpi tomorrow.

Thank you

@Jo-Bl I begin to wonder whether this is an OS/underlying library issue.
When i was using eth0 and wlan0 I could switch between the interfaces using local_addr just fine. I also verified it setting special firewall rules in my router.
However, as soon as I also connected my Edimax USB adapter and set up wlan1 it would only allow connections via wlan1. When I tried to use the local_addr for eth0 or wlan0 I would not get any response.
According to the documentation, the use of local_addr, however, should be exactly what you are looking for.

I am also seeing a lot of these errors, when the edimax is connected:
https://github.com/raspberrypi/linux/issues/6049

@Jo-Bl I begin to wonder whether this is an OS/underlying library issue.
When i was using eth0 and wlan0 I could switch between the interfaces using local_addr just fine. I also verified it setting special firewall rules in my router.
However, as soon as I also connected my Edimax USB adapter and set up wlan1 it would only allow connections via wlan1. When I tried to use the local_addr for eth0 or wlan0 I would not get any response.
According to the documentation, the use of local_addr, however, should be exactly what you are looking for.

Sorry for not describing the behavior better (I was more interested in the data than in testing and trying it out): It is exactly as you describe and have tested it.

Right, I forgot to paste the link to the documentation:
https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.create_connection

I am also seeing a lot of these errors, when the edimax is connected:
raspberrypi/linux#6049

But it is possible to connect to two different (hoymiles-)APs with wlan0 and wlan1, only to sepatate them via IP does not work. Is there another way to do that? Via 'wlan0' and 'wlan1' or so?

Yes, it might be possible by directly creating a socket. However, this approach will only work for Linux based systems. The IP-based approach should look up the interface independed of the OS and select the appropriate interface automatically.
I can try to push an update today with this approach to see if it works.
By the way, just to make sure: I assume you set the IP-adddress manually right?  Because the hoymiles begins setting the IP at <IP_ADDRESS>. So if you have two different devices, both of them would try to assign the client the <IP_ADDRESS> IP.

First I let it be assigned automatically and that worked very well. (I got .150 from the first inverter and .151 from the second inverter).
When fetching on two interfaces didn't work and you then implemented --local_addr, I also tried with static IPs.

The IP-based approach should look up the interface independet of the OS and select the appropriate interface automatically.
Yes, this is like e.g. a linux app 'wol' do to select the interface, to send the magic packet.
On the oher hand ssh selects the interface according the routing table?


Update jekyll admin latest code into jekyll manager

Update jekyll admin latest code into jekyll manager
I wish to try jekyll-manager but it is on older version of jekyll. Also there are 200+ new commits in jekyll-admin.
So think it will be a good idea to sync changes.

@AquisTech Thank you for expressing interest in this project.
However, as you can see from the size of Git merge-conflicts, the code here is significantly different from that in jekyll-admin.
Functionality-wise there isn't much of a difference between the two projects.
The only notable difference being jekyll-manager exposes a couple of endpoints for themes and templates at source directory. All other features have been adapted into the parent project, jekyll-admin.

@AquisTech Thank you for expressing interest in this project.
However, as you can see from the size of Git merge-conflicts, the code here is significantly different from that in jekyll-admin.
Functionality-wise there isn't much of a difference between the two projects.
The only notable difference being jekyll-manager exposes a couple of endpoints for themes and templates at source directory. All other features have been adapted into the parent project, jekyll-admin.

@ashmaroli I saw a few nice features like the dashboard or drafts. Can you guide me on how to use them in jelyll-admin (if available there)
Also jekyll-manager is great and if in some way in terms if feature it has additional features like drafts then I would like to use it and if possible with latest jekyll.
I would not mind giving some support for updating dependency. Please advice

Jekyll Admin doesn't have the endpoint for a dashboard, but there is support for drafts

That said if you still wish to try this plugin out, you have the option to build the gem from source (if you're comfortable with managing Node dependencies and Ruby).

Jekyll Admin doesn't have the endpoint for a dashboard, but there is support for drafts

Thanks for the reference to Drafts feature.

That said if you still wish to try this plugin out, you have the option to build the gem from source (if you're comfortable with managing Node dependencies and Ruby).

I will fork and will give it a try


Release to npm from Travis CI / SPA-1413

Come up with a mechanism to release our libraries to npm from Travis CI using a specific set of branches or tags

After doing some research today, I realized Travis does not have support for npm deployments from a monorepo.
https://github.com/travis-ci/travis-ci/issues/3540
We need to find a way to leverage our existing scripts on a custom deployment from Travis or do our deployments from elsewhere


Add ( and ) to the list of chars in ignored lines.

Without this , lines containing only )?; were not ignored.
This removes around 150 lines detected as "uncovered" on wayland-rs.

Awesome, thank you very much :+1:


[BUG] Detect conda install even when using scikit-build, pick lib/ over lib64/

Description
As noted on this issue, rapids-cmake will always set the library directory to lib/ (even if the system's native library directory is lib64/) when installing under a conda environment, to appease cpython's requirement that third-party modules always be installed under lib/.
This is not happening for our stack on RHEL installations (installed libraries erroneously end up under $CONDA_PREFIX/lib64).
The underlying issue appears to be that we're using scikit-build, and that is setting CMAKE_INSTALL_PREFIX to _skbuild/<arch>/cmake-install (the artifacts eventually make it to $CONDA_PREFIX). CMake only activates the python compatibility mode when CMAKE_INSTALL_PREFIX is equal to $CONDA_PREFIX, and in this case it is not.
Some of our cmake files were calling include(GNUInstallDirs) before rapids_cmake_install_lib_dir(), but changing that order didn't help. We were eventually able to work around this issue by explicitly setting -DCMAKE_INSTALL_LIBDIR=lib, but it would be best if rapids-cmake could recognize that automatically.
Steps/Code to reproduce bug
Get on a RHEL system (or VM/container) and do:
# install conda
git clone https://github.com/nv-legate/legate.core.git
cd legate.core
./scripts/generate-conda-envs.py --os linux --python 3.9 --ctk none --no-compilers --no-openmpi --no-ucx
conda env create -n legate -f environment-test-linux-py3.9.yaml
conda activate legate
./install.py --verbose

The output libraries, e.g. liblgcore.so, end up under $CONDA_PREFIX/lib64.
Environment details

Environment location: We've encountered this on NERSC's Perlmutter, other users have reported this on local RHEL systems.
CMake version: 3.26.3

I am going to have to close this. The more generalized heuristic of presuming a conda location ( lib ) when on rhel + conda env variables is not possible.
That approach was originally used by me in CMake proper and broke numerous RHEL based distros ( https://gitlab.kitware.com/cmake/cmake/-/issues/22962 ) which provide conda for all users by default. In those cases all builds are 'inside' a conda env but not installing to the CONDA_PREFIX.
I don't think we can reliably say that scikit-build builds on RHEL with conda env variables means we are doing a conda build. As the fix for 22962 shows the CONDA_PREFIX on these machines is something like /usr and so we can't do something like see if we are using a conda provided compiler as on those machines we would yet again get a false positive.
Unless we can find a reliable heuristic for RHEL+CONDA we are going to have to explicitly specify the install lib dir in these cases.


Ammonite should be able to update itself

Since ammonite already utilizes ~/.ammonite directory, I think it could store it's binaries there, and be able to download it's newest version on its own, or with user's permission, straight after launching it.
Could be implemented either in ammonite itself or just in a bash script launcher as a wrapper to run ammonite, similarly to how sbt does this.

closing due to inactivity


fix: Adjust auction results for you tracking

The type of this PR is: Enhancement

This PR resolves CX-1617
Description
Rail header tap

{
  "context_screen": "Home",
  "context_screen_owner_type": "home",
  "action": "tappedAuctionResultGroup",
  "context_module": "auctionResultsRail",
  "destination_screen_owner_type": "auctionResultsForArtistsYouFollow",
  "type": "header"
}

Rail thumbnail tap

{
  "context_screen": "Home",
  "context_screen_owner_type": "home",
  "action": "tappedAuctionResultGroup",
  "context_module": "auctionResultsRail",
  "destination_screen_owner_type": "auctionResult",
  "destination_screen_owner_id": "315289",
  "horizontal_slide_position": 1,
  "type": "thumbnail"
}

Screen thumbnail tap

{
  "action": "tappedAuctionResultGroup",
  "context_module": "auctionResultsForArtistsYouFollow",
  "context_screen_owner_type": "auctionResultsForArtistsYouFollow",
  "destination_screen_owner_type": "auctionResult",
  "destination_screen_owner_id": "315289",
  "type": "thumbnail"
}

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Thanks 🎉


Update SignerId.cs

When there is reference equality, Equals() should return true. I encounter this issue when calling SignerInformationStore.GetFirstSigner().

Merged, thanks.


Simple entering of Greek characters

Coming from Mathematica background, I find it powerful to be able to quickly enter Greek characters via the key combination, e.g.,  ESC-f-ESC (for phi).
It would be great to have something comparable for working with Julia.

Just do \alpha and then tab. It's even easier since the keys are nearby and it matches TeX more closely.

I personally find this feature very useful. Perhaps the Greek alphabet could have a special shortcut like a key plus a single letter in the keyboard corresponding to the Greek letter (a = alpha, b = beta, ...).

Mathematica is less predictable since I've never thought the Euler constant is ee. Simplifications only make sense of you're used to  them. But \alpha always works and it's exactly the name everyone else uses. It matches LaTeX too so you already know the language.

The proposal seems to suggest an extension. It wouldn't affect the current behavior of \alpha.

Are you sure escape can be captured like that in Atom?

I am not sure about ESC but any unused key would do the trick.
On VIM for example we can also configure a sequence of key strokes to trigger the conversion to unicode. Mine for example has a sequence jj that behaves like ESC and switches the editor to normal mode. If I just press a single j and wait a bit, it doesn't take effect.

I think this could just be an Atom package, not necessarily part of Juno?

Good call, this could be implemented as an Atom package.

For reference, the LaTeX completions "in Juno" are actually a separate Atom package called latex-completions, so it could just be implemented similarly and then used with any language. That might be good code to look at to find out how to do it.

A compromise could be to give greek charcters a higher priority in the autocompletion list so you can always complete them after two typed chars.

Alright, I'll look into implementing that then.

atom-latex-completions version 0.3.4 has an option for this (enabled by default) -- with that it's always enough to the first two characters (usually one, but e.g. θ and τ both start with t so the extra char is required to disambiguate them) when you want to enter greek.

Thanks for updating and clarifying.


New  fonts

Hello
first thank you so much for this amazing addition
I am facing some issue in introducing new Arabic fonts
can you please elaborate more on that

Hi,
What sort of problem are you facing?
On Mon, 22 Jun 2020, 15:47 Mutaz-Midwam<EMAIL_ADDRESS>wrote:

Hello
first thank you so much for this amazing addition
I am facing some issue in introducing new Arabic fonts
can you please elaborate more on that
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mnarimani/RTLTMPro/issues/46, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHJU2XBSQHMKP2BJJMNYNDTRX44TBANCNFSM4OEPP6AA
.

Hello
In adding the new font, it did not make any error but the result was that I
can only use Enlgish and the Arabic letters were squares still.
Thanks
&
Regards,
Mutaz
On Mon, Jun 22, 2020 at 5:37 PM Moh Narimani<EMAIL_ADDRESS>wrote:

Hi,
What sort of problem are you facing?
On Mon, 22 Jun 2020, 15:47 Mutaz-Midwam<EMAIL_ADDRESS>wrote:

Hello
first thank you so much for this amazing addition
I am facing some issue in introducing new Arabic fonts
can you please elaborate more on that
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mnarimani/RTLTMPro/issues/46, or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AHJU2XBSQHMKP2BJJMNYNDTRX44TBANCNFSM4OEPP6AA
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mnarimani/RTLTMPro/issues/46#issuecomment-647559639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMZ3HTKSOZGPZV7TTEQ3BTRX5UCFANCNFSM4OEPP6AA
.

--
http://midwam.com/
mutaz basharahil
Developer
M: +966 55 742 9650 T:
+966 12 612 9687
F https://www.instagram.com/midwam/ https://www.twitter.com/midwam/
https://www.linkedin.com/company/9476506/
DISCLAIMER: This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error, please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named addressee
you should not disseminate, distribute or copy this e-mail.

@Mutaz-Midwam  To use new fonts with TextMeshPro, you need to create a font altas in the format that TextMeshPro understands. Follow the instructions here. This applied to any new font and is not specific to RTL fonts or RTLTextMeshPro.


add flag for limiting information

This PR modifies the response to be returned for list releases endpoint. The PR is aimed at improving the performance of list releases api . If the call is made from list releases page we can return limited information else the entire manifests and notes will be returned too
Signed-off-by: Kartikey Mamgain<EMAIL_ADDRESS>

Results from oc helm cli:
kmamgain@kmamgain-mac console % oc helm list --limitInfo=false
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
dotnet default 1 Fri Dec 30 05:35:26 2022 deployed dotnet-0.0.1
gitrel default 1 Fri Dec 30 05:37:49 2022 deployed gitlab-6.7.0 15.7.0
kmamgain@kmamgain-mac console % oc helm list --limitInfo=true
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
dotnet default 1 Fri Dec 30 05:35:26 2022 deployed dotnet-0.0.1
gitrel default 1 Fri Dec 30 05:37:49 2022 deployed gitlab-6.7.0 15.7.0
kmamgain@kmamgain-mac console %


Added Mime_Type property to MetaData model

Adding one property will resolve issues #126 and #69.

Thanks! :+1:


Moving enabling directorate page into archives

The following link is dead
https://canada-ca.github.io/PCTF-CCP/overview/pctf-overview.html
Now it seems to be ..
https://canada-ca.github.io/PCTF-CCP/
It is used in the ITVision.md file


The attribute 'rel' may not appear in tag 'div'

Ref : https://validator.ampproject.org/#url=http%3A%2F%2Flemontrend.com%2Fbeauty%2Fredken-heatcure-treatment%2Famp%2F.
http://lemontrend.com/beauty/redken-heatcure-treatment/amp/.
https://wordpress.org/support/topic/prohibited-or-invalid-use-of-html-tag-2/#post-8528933

Reviewed. Working fine


Visual creating new events in day/week view

It would be very nice if the q-calendar support visual creating new events like here
https://dhtmlx.com/docs/products/dhtmlxScheduler/.
Click on a start time.
Drag it downwards until the desired end time and release the mouse.
Is it possible to do this in q-calendar?

The event system is in dev-land, so up to the developer. This gives more freedom in look-and-feel. While the demo has drag-and-drop, it is by no means complete. It's meant as an example for those that look at the code.


Enable to migrate with application startup on k8s

AsIs
With multiple entries in Procfile, now we can call migrate/loaddata via buildpacks process with calling /cnb/process/migrate within the build artifacts on GKE.
But this makes Procfile command long ones, so that we should separate command in Procfile and call separately via initContainer with k8s deployment.
ToDo

Separate commands in Procfile
Add initContainer in manifests/django.yaml

(Optional) Acceptance criteria
Confirm djano pods will be runnnig without any error

With providing Secret resource to initContainer, we have been resolved this.
But for collectstatic, with /cnb/process/collect commands in Procfile, we have to consider several deployment options for storing collected files. Meaning, with current configuration initContainer & main container will not share any storage, so it is no meaning to run python manage.py collectstatic as initContainer.
For fixing this:
Option-1: Create PVC shared between collectstatic initContainer and main container, but this requires RWX volumes
Option-2: Revert Procfile with moving collect: command within web:

Because we have to run /cnb/process/collect on GKE every time after main code bases will be updated, for fixing collectstatic problem as temporary solutions, we would adopt Option-2 for now.
This is because, it is a bit hacky way to use RWX volumes between pods, or even though between containers in same pod. Meaning, we have to setup GCE volumes to provide NFS server and have to mount as NFS volumes for shares.

As we have updated Procfile commands with Option-2 described in previous comment, and confirmed that application Pod in GKE have been Running states, so close the issue for now.


Fix build errors "Name contains characters which can cause problems on Windows"

These errors appear during the build process. For example
zally-ruleset-zalando/src/test/kotlin/org/zalando/zally/ruleset/zalando/DateTimePropertiesSuffixRuleTest.kt: (17, 9): Name contains characters which can cause problems on Windows: "
zally-ruleset-zalando/src/test/kotlin/org/zalando/zally/ruleset/zalando/DateTimePropertiesSuffixRuleTest.kt: (46, 9): Name contains characters which can cause problems on Windows: "
zally-ruleset-zalando/src/test/kotlin/org/zalando/zally/ruleset/zalando/EnumValueTypeTest.kt: (13, 9): Name contains characters which can cause problems on Windows: "

I would love to take this up.

There are still warning messages related to Windows compatability.


wip - initial appveyor commit, copy the base yml and script to copy the needed pkgs

add appveyor support along with testing of modsec via the framework


Optionally reduce timestamp resolution for performance

Introduce a new useMicrosecondTimestamps() static method to Logger
that allows runtime selection of whether or not to create microsecond
resolution timestamps for log records.
Generating microsecond resolution timestamps by calling
microtime(true), formatting the result via sprintf() and then
parsing the resulting string via DateTime::createFromFormat can incur
a measurable runtime overhead vs simple usage of new DateTime to
capture a second resolution timestamp in systems which generate a large
number of log events.
The default behavior of generating high precision timestamps remains the
same, but may be changed in a future release. Users requiring high
precision timestamps are encouraged to explicitly call
Monolog\Logger::useMicrosecondTimestamps(true) in their setup code.
Closes #657

the reason the build failes is a issue with raven, not related to this PR which is fixed with https://github.com/Seldaek/monolog/pull/660

Ping! :)

Updated patch and description based on feedback from @Seldaek in https://github.com/Seldaek/monolog/issues/657#issuecomment-148472673.

@bd808 Sorry but would you mind making this flag and setter non-static? I think it was a mistake to have the timezone statically to be honest, and it'll be changed in 2.0, so let's not generate more BC breaks :) Aside from that it looks good so I can merge as soon as you let me know it's done.

@Seldaek changed from a static to a member variable.

Thanks!

Thank you very much, @bd808 and @Seldaek.


IndexedDB support

<EMAIL_ADDRESS>commented:

Greetings. IndexedDB support would be stellar. Thanks much, keep up the great work.
Historical note, there was a forum post from June 2012 on this, and the reply was to create a ticket. I have not found that ticket, and am creating it thusly. Thanks again.

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #992.
:star2:   3 people had starred this issue at the time of migration.

Any progress on this?

I'm currently writting my own indexeddbmock because I wanted to use PhantomJS for automating my tests. Currently I'm only able to mock the structure, but I'm working on the data now. If you are interested have a look at https://github.com/kristofdegrave/indexedDBmock

@JamesMGreene, I'm a little confused about the mention of waiting on WebKit, since as far as I can see, WebKit supports indexeddb.

Looks like indexeddb works now in phantomjs 2.0 and this can be closed.  I haven't tested it extensively, but it looks like as long as you set local-storage-path and local-storage-quota you can create, insert and query data properly.


OptiGUI

Mod name
OptiGUI
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/optigui
Other links
https://github.com/opekope2/OptiGUI
What it does
Optifine custom GUI support
Why should it be in the modpack
Optifine parity, better than #300 as it works directly
Why shouldn't it be in the modpack
Untested
Categories
Works like Optifine/Bedrock Edition/Forge/etc
Additional details
No response

Things seems to be working fine
I tested ender chest, small chest, large chest, and barrel
furnace, blast furnace, and smoker
dropper and dispenser
some villagers
Shulkers
https://www.planetminecraft.com/texture-pack/colourful-containers-dark-mode-gui-optifine-required/

Things seems to be working fine I tested ender chest, small chest, large chest, and barrel furnace, blast furnace, and smoker dropper and dispenser some villagers Shulkers https://www.planetminecraft.com/texture-pack/colourful-containers-dark-mode-gui-optifine-required/

You were faster than me 😝

Things seems to be working fine I tested ender chest, small chest, large chest, and barrel furnace, blast furnace, and smoker dropper and dispenser some villagers Shulkers https://www.planetminecraft.com/texture-pack/colourful-containers-dark-mode-gui-optifine-required/

You were faster than me 😝

speeeeed

I did some testing (with the same pack as @Uranite) and it seems to work perfectly!
More specifically (the GUI's that "only work with OptiFine", according to the description of the pack):
Villager GUI:

Dropper:

Ender Chest:

Chest:

Large Chest:

I'd say that it should be added right here and right now! :)

Also loading screen is broken with that texture pack

That's the resource pack I wanted to use when I switched to fabric+sodium. I didn't find the mod I needed so I coded my own.
Yes, I know Custom GUI exists, but its format lacks some Optifine features.

Also loading screen is broken with that texture pack

This is a bug of the Puzzle mod

@Uranite Thanks, reported to https://github.com/PuzzleMC/Puzzle/issues/29
cc @RaptaG

Added in 3.8.0


[Minor] Quantum Chemistry Doc Fix

https://docs.microsoft.com/en-us/quantum/libraries/chemistry/samples/loading-from-file?view=qsharp-preview
Fix the variable in the line “var jordanWignerEncoding = JordanWignerEncoding.Create(generalHamiltonian);”
We should be using the variable “hamiltonian” described above, not “generalHamiltonian” which is not initialized. :)

This seems to have been fixed in #436, though I'm not sure how the timing works - that PR has been merged to live branch in the end of May, while the issue is from August?


Shorten generated  test resource paths

Description
I ran into the windows path limit again and decided to make it less likely to be exceeded in future.
This change makes the file names for test resources even shorter and more readable but changing the from UUIDs to indexes.
Before submitting a PR:
We love getting PRs, but we hate asking people for the same basic changes every time.

[x] Push your changes to a branch other than master. Create your PR from that branch.
[x] Add JavaDocs and other comments
[x] Write tests that run and pass in CI. See CONTRIBUTING.md for details on how to capture snapshot data.
[x] Run mvn -D enable-ci clean install site locally. This may reformat your code, commit those changes. If this command doesn't succeed, your change will not pass CI.

I am afraid this is going to clash with #753, not sure how to fix.

You can delete the test resource files and regenerate them or leave them as is. The test resources you generated should still work, they just have a different naming convention.


Update README.md

fixing formatting

@leestott can you review, formatting was botched, hopefully this fixes it


Barrettcw

Update for cvc4 based on 1.5 pre-release used for SMT-COMP 2016.

Hi all - any reason why this pull request hasn't been picked up?  I have people asking me about cvc4 on brew.

This is the boneyard so we don't support formulae here.


Create .appveyor.yml

I now realize that this project is using azure pipelines. Is there any point to also leveraging appveyor?
see example output here

Closing this PR since we will only be using Azure for CI.


Create and edit a demonstration video of the AE2 minimum viable product (~5mins)

No video required - All will be done live in front of Martin and Nick on Thursday 16th May 2024 at 3pm.


[Feature Request] Release process automization

Currently, releases are very rare, as it is hard to pick points at which one deems that enough was added to justify a new release. This is very problematic, as during this development phase, many key features should arrive at the users hand asap. Building the library yourself shouldn't be a step in this process as a user.
In order to improve this process, automatic release functionalities might be added. These could be github actions, triggered for example by Pull requests.

471788679934d038a8546025acb1a099267d9b16


Debounce / throttle rendering

As far as I can tell, rendering is responding to page layout changes up to every 1ms.
Is there any way to throttle the rendering?
I think it should be max 60fps (~16ms frames)

Hey Adam! Do you have an example? Throttling rerenders is a great idea.

Suggest we use https://github.com/xnimorz/use-debounce once the component has been refactored to use hooks: #459


Logging

Currently, the only logging that is being done is sent to STDOUT, with no organized level of importance. A logging module would be desired, using a library with limited dependencies-- all we need is a few levels of severity to choose between, like Info, Warning, and Critical.
Instead of using putText, I would like to be able to write something like log Warning "log message".

Is this library a good fit http://hackage.haskell.org/package/tinylog ?

yeah, that actually looks pretty good!

Functionality added in #19


How crux is different from Constellation

It uses the same API for communicating with Quorum nodes.
It works in the same manner as Constellation with respect to storage and encryption, with the exception that the default datastore used is LevelDB instead of BerkeleyDB (although BerkeleyDB is supported).
It's been written in Go to enable a much larger community of developers to understand how the code works - Haskell presented challenges for a number of users.


Egui Template app has limited input options

After setting up an app using https://github.com/emilk/egui_template it seems that I am limited to the input data that egui itself uses (https://docs.rs/egui/0.6.0/egui/enum.Event.html). Is this an intentional limitation where I need to "eject" from using the App trait and setup things manually if I want more keybindings (ie ctrl-P)?

Good point - no I just hadn't thought that far ahead :)
I'll add Keys for  A-Z and 0-1 so you can make keyboard shortcuts for them!

Good point - no I just hadn't thought that far ahead :)
I'll add Keys for  A-Z and 0-1 so you can make keyboard shortcuts for them!


Change to factor in options to modal price calculation

Also consider curencies with different decimal quantities.
This also requires a change to themes/tastyigniter-orange -> _partials/cartBox/item_option_select.php
add
data-option-price="price; ?>" to line #14

Added the changes to the partials. The calculation seems to be a bit off when switching between options, it deducts only the option price instead of deducting option price * qty?

Oops. Updated.


Compiled wheels on PyPI would be really useful

The PyPI builds of mistralrs - https://pypi.org/project/mistralrs/ and https://pypi.org/project/mistralrs-metal/ and suchlike - currently only ship a .tar.gz file.
This means the user must have a Rust toolchain installed in order for pip install mistralrs-metal to work.
It would be great if you could publish compiled wheels for macOS and Linux (and Windows too if that works) to PyPI.
Here's a macOS Apple Silicon Python 3.10 wheel I built when I ran pip install mistralrs-metal just now:
https://static.simonwillison.net/static/2024/mistralrs_metal-0.3.1-cp310-cp310-macosx_11_0_arm64.whl
Anyone with Python 3.10 on macOS Apple Silicon should be able to install that like this:
pip install https://static.simonwillison.net/static/2024/mistralrs_metal-0.3.1-cp310-cp310-macosx_11_0_arm64.whl

GitHub Actions has macOS runners for Apple Silicon now so it should be possible to do this entirely in a GitHub Actions workflow.
I believe https://github.com/pypa/cibuildwheel is the best way to do this kind of thing, but I've not used it myself.

It looks like this repo is using both Rust and cibuildwheel in a GitHub Actions workflow to build wheels across multiple operating systems: https://github.com/google/flax/blob/c1046ad08f885e3ff35e6fdec2bd0b6495e04e22/.github/workflows/flaxlib_publish.yml#L11-L33

This is the simplest example I've found of cibuildwheel in action: https://github.com/adamchainz/time-machine/blob/2.15.0/.github/workflows/build.yml - it produces 55 wheels: https://pypi.org/project/time-machine/#files


model.validate() doesn't validate when offline. Expected behaviour?

Hey there, I've been scrounging your source code, and have had no luck in finding out why my callback won't get called when the server is offline. I'm getting a little adventurous with what I'm trying here. Trying to get a fully offline app going with Ground DB and astro as my model layer. So far everything is working, except when I'm offline my callback isn't run. I wasn't aware that your validation is being done server side.
  saveClicked() {
    let { shift } = this.state;

    var result = shift.validate(err => {
      if (err) {
      } else {
        let _id = Shifts.insert(shift.raw());
        FlowRouter.go('/');
      }
    });

Where shift is
Shift = Astro.Class.create({
  name: 'Shifts',
  fields: {
    title: {
      type: String
    },
    location: {
      type: String,
      optional: true
    },

Is this expected behaviour?

Strange order there...

I've tested it and it's working even when being offline. You are probably doing something wrong. If sever is not available it will still validate on the client and throw some errors or execute callback function if provided.

Should have mentioned I'm on rc.7 maybe things have changed a bit. I'll look in to it more, but I don't see any issue with it :P Thanks for the response.

I'm talking about rc.7. It works that way. It wasn't doing server validation in the same time in 1.2

Wow damn you're right, just tested in console and it was working. Strange behaviour then but definitely induced by me somehow...

In deed :). So closing it for now


Add various "Many" create/update/delete methods

Should solve: #47 #96  #98 #245

New deleteOrganizationMemberships method
New createOrganizationMemberships methods
New updateOrganizations methods
New updateUsers methods
New createOrUpdateUsers methods
[Breaking Change] permanentlyDeleteTicket(s) methods aren't calling anymore deleteTicket(s) because the deletion must be acked (and it's not necessarily immediate) before deleting them permanently
[Breaking Change] New integration tests + rework the model used to handle Async Jobs results ( https://developer.zendesk.com/rest_api/docs/support/job_statuses#job-statuses )

It's a draft, We have to add some tests

Replaced by #346 to have a build running on codeship


Updating missing Welsh translations

Updating Welsh translations for new screens
Updating previously missed Welsh translations
Updating Controller logic within amlBodyMembershipNumberController to only display dynamic AML name against error message (depending on which validation issue the user encounters)
Updating tests

CI: No security warnings found


Get track metadata?

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
"shaka-player": "^3.0.1",
Please ask your question
I want to read out the metadata from a video track:
async initialize () {
      if (!Player.isBrowserSupported()) {
        alert('Browser is not supported')
      }

      try {
        this.instance = new Player(this.player)

        await this.instance.configure(this.settings)
        await this.instance.load(this.data.stream_url)

        // Add sprite metadata
        const metadata = await this.instance.addTextTrack(
          this.data.sprites_url,
          'en',
          'metadata',
          'text/vtt'
        )

        await this.instance.selectTextTrack(metadata)
        await this.instance.setTextTrackVisibility(true)

        // Add listeners
        for (const listener of this.listeners) {
          this.player.addEventListener(listener, this.dispatchEvents)
        }
      } catch (e) {}
    },

The sprite file contains metadata:
WEBVTT

00:00:00.000 --> 00:00:05.000
{
    "x": 0,
    "y": 0,
    "width": 120,
    "height": 90
}

...

00:09:55.000 --> 00:10:00.000
{
    "x": 960,
    "y": 1080,
    "width": 120,
    "height": 90
}

It shows as subtitle textrack:
console.log(this.player.textTracks[0])
console.log(this.player.textTracks[0].cues)

TextTrack {kind: "subtitles", label: "Shaka Player TextTrack", language: "", id: "", mode: "showing", …}
activeCues: TextTrackCueList {length: 0}

Is this unsupported?
Thanks. :)

Sorry, turns out this was a CORS issue. :)


Update to Tool Management slides for Admin Training 2021

Some proposed updates to the toolshed/tool management slides:
Additions:

Three slides at the beginning talking about the tool panel and tool configuration files
Slide containing a screenshot of the toolshed
shed-tools install example slide
two slides on shed-tools test

Changes:

workflow-to-tools slide instead of workflow-install

Deletions:

run-data-managers slide
Dependency resolvers example
Slide about integrated tool panel (this is covered in added slides on tool configuration files)

Some slides have been rearranged as well.  The approximate running time is 20 minutes.
For things that I have taken out, I can easily put these back if they are missed.

Thank you @nsoranzo!

Thanks so much @cat-bro.
I'll rebase get the automated video going over in #2152.


code format does not meet dart format need

Steps to Reproduce

if I modify the framework or engine code,I use dartfmt in bin/cache/dart-sdk.old/bin/dartfmt to format my code ,the style changed a lot ,event if I just modify one line.I wonder the code style of flutter framework of engine. Can you export it to me?

Logs

Hi @mivanzhang
For questions like these, Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself, if you disagree please write in the comments and I will reopen it
Thank you

Thank you for your answer,  I got the solution from here https://flutter.dev/docs/development/tools/formatting , but this doesn't make any snesor ,if I use the command above to format  cache.dart, still lots of changes, I don't know how to get help or ask a question in other places

@mivanzhang neither the flutter tool nor the framework use Dartfmt, all of the code is hand formatter. This is explained in more detail in the style guide in the wiki, which at https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#formatting


[Feature Request] Option to Enable/Disable Identification of Error Points Using SavePoint Mechanism for SQL Updates in PostgreSQL

The SavePoint mechanism in PostgreSQL provides the capability to roll back to a stable state for error analysis when an SQL update fails. However, it requires that a transaction be present in the current context, which is not feasible in some projects.

Try 0.8.170


Biases for LSTM and GRU forget gates

The standard implementation of LSTM and GRU initialises the biases to zero.
The referenced literature Supervised sequence labeling with recurrent neural networks states that forget gate biases should be set to something positive and input gate biases should be set to something negative. However Keras doesn't provide an easy way to do it.
The rationale is that the network shouldn't forget past information until it has learnt to forget it, and that it shouldn't bring in new info unless it has learnt that it is good to add new info to its internal state. While that seems sensible I have little idea whether it is useful in practice.
The simplest solution would be to add default bias initializers to LSTM and GRU that set the forget biases to 1, the other gate biases to -1, and any other biases to 0?
If the idea seems good to you, I'll prepare a pull request.

This paper also shows how positive LSTM bias helps to improve the network performance.


Not an Issue - Thanks for an awesome tool

Hello, I really wanted to say how much I appreciate FDT and I couldn't find any place to do so, so forgive me for doing it this way.
FDT - unbelieveable transfer speeds, fantastic thank you so much developers!
2019-02-14 02:36:40 INFO lia.util.net.copy.monitoring.ConsoleReportingTask reportStatus Net In: 627.658 Mb/s  --  WooHoo!

I just also want to drop in and leave a thanks as well. I tried everything to speed up an rsync operation between two servers that had really bad routing. RSync was only giving me ~500Kb/s tops and even UDR only managed a tiny improvement: ~1MB/s.
Then I tried FDT and couldn't believe my eyes. FDT was able to achieve a consistent 8MB/s.
Truly a miraculous program.

Greetings From Gen.david jeffrey,please contact me at, (davidjeffrey801@gmail.com)or you you send me your email here to contact you OK

Greetings From Gen.david jeffrey,please contact me at, (davidjeffrey801@gmail.com)or you you send me your email here to contact you OK


[CI] Publish to npm on stable and master branches

I have another PR open which finally triggered builds. Turns out the way I was filtering out jobs was invalid, but Circle was not showing an error - it was dropping the build silently.

Yeah, I just found it - leaving comments there


Computed observables are not garbage collected and are always evaluated

Hi,
First of all, thanks a lot for making this library open source, I really like it, especially its API that I find really well designed. 🙌
I'd like to share what I think is an issue with the current implementation of computed() observables: because they are referenced by their dependencies (i.e. the observables on which .get() is called while the computed observable is evaluated), they won't be garbage collected even if they are no longer used. It will lead to memory leaks for any computed observables that do not have the same lifetime as the app.
Another related issue that could cause performance issues is that computed observables are re-evaluated whenever one their dependencies changes, even if they are no longer being observed. Because of that, computed() can't really be used to create computed observables dynamically.
Here is an example:
const users = observable<{ id: number; firstname: string }[]>([
  { id: 0, firstname: "John" },
  { id: 1, firstname: "Alice" }
]);

function getUserById(id: number) {
  return computed(() => {
    console.log(`Finding user with id ${id}`);
    return users.get().find((user) => user.id === id);
  });
}

export function UserProfile({ userId }: { userId: number }) {
  const user = useSelector(() => getUserById(userId));
  ...
}

Every time UserProfile gets re-rendered, it creates a new computed observable. These observables will never be garbage collected because they are referenced by users. Also, every time users is modified, all computed observables created since the launch of the app will be re-evaluated while only a single one is being observed for each mounted <UserProfile>.
Expected behavior:

Only computed observables that are being observed should be re-evaluated
Computed observables that are no longer referenced should be garbage collected

I've implemented my own observable library and I think the proper way to fix that is to "connect" computed observables to their dependencies only when they are observed (and disconnect them when it's no longer the case). This makes the implementation a bit complex to write. I believe this is also how Preact Signals are implemented

Yes you're right, we should have a way for computeds to disable themselves when there's no more listeners. They already activate lazily, so when the last listener is removed they could revert to an unactivated. However, it's not super simple because listeners are removed and added quite often when re-evaluating, so there would need to be a cleanup pass at the a batch. I'll look into that.
In your example though, it really shouldn't be creating a new computed every time. In fact you could just remove it and it should work as you expect. useSelector is kind of like a computed in itself - it will re-run whenever any accessed observables change and re-render the component whenever its returned value changes.
Example with just the computed removed:
const users = observable<{ id: number; firstname: string }[]>([
  { id: 0, firstname: "John" },
  { id: 1, firstname: "Alice" }
]);

function getUserById(id: number) {
  console.log(`Finding user with id ${id}`);
  return users.get().find((user) => user.id === id);
}

export function UserProfile({ userId }: { userId: number }) {
  const user = useSelector(() => getUserById(userId));
  ...
}

But it absolutely is a problem if a component has a useComputed and it unmounts. So we should definitely fix this.

In your example though, it really shouldn't be creating a new computed every time. In fact you could just remove it and it should work as you expect

Agreed, using computed() in this example was needlessly complex. But I think this usage of computed() should still be allowed as it has some benefits:

It could act as a memoization for complex computations (a bit like useMemo()). Not sure this is implemented currently.
It prevents some unnecessary re-renders. If I append a new user to users, I would expect UserProfile to not be re-rendered as the value of the computed observable won't change. It wouldn't be the case without computed() as users would be a direct dependency of UserProfile.

I just released version 3 alpha which includes computed auto-deactivating. They now only re-compute themselves while actively observed. Otherwise they are marked as dirty and will re-compute on the next get/peek.
So I’m going to close this issue as solved :). But please let me know if it doesn’t seem complete to you.


Proposal for the documentation

Looking at the entire documentation, I believe setting up a docs page like what kubernetes offers https://kubernetes.io/docs would help the community.
What do you think?
 Basem Vaseghi<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

Hi Basem!
Great idea, we already have a small piece of it: https://international-data-spaces-association.github.io/InformationModel/docs/index.html# is created from the IDS Information Model (https://github.com/International-Data-Spaces-Association/InformationModel/tree/develop/docs)
The layout could of course look better... But I like the idea to maintain the docs page also from open github repositories.

Hi,
this is definitely needed but might take some time. Let us keep this issue open and work on it.

This issue is addressed in the idsa repository. Nevertheless, IDS-G has to provide a strong reference to the documentation provided there. This is not addressed, yet.

This issue is solved with the docs section at the IDSA Homepage. At least as a starting point. We should continue to improve there. https://docs.internationaldataspaces.org/


WMTS requests ignored

Hi folks.
I've encountered problem with MapFish v 3.3.0....been solving the problem for almost 2 days and could't solved it yet.
I've got JSON config with defined WMS and WMTS layers that should be rendered on a pdf output. Everything seemed ok. I sent Ajax POST request on MapFish server, got JSON response object with status, download url and etc. When a print job was done the pdf output was available for download. After downloading the pdf output what I got was this:

Like seriously? Checked JSON config several times, compared with examples configs line by line. Everything seemed ok. Then I looked at the tomcat log file and tried to trace what is going on. It looks like the more "east" I went (zoomed or moved in the map layout) mapfish server stopped sending WMTS requests on Geoserver and all I got was a transparent background instead of processed WMTS layers. The funniest thing is that WMS layers got rendered correctly.
Projection is EPSG:102067 (Krovak East North). And yes, already put it in a epsg.properties file.
I'don't know what to do know? Is this issue only a problem of MapFish version? (the latest version of MF is 3.7.0). Anybody else has encountered this problem?
Thank you in advance!

Finally, my fault :). I swapped array values in a matrixSize property.


UI-Fabric for macOS?

I'm not sure if this is the right place to ask for this, but is UI Fabric for macOS planned any time soon? Thanks

Marco, there are plans (in a different team), but nothing concrete yet. Microsoft has enough Mac products (and Mac UI) to produce such a library, but no dates are promised.


Fail to install mozilla/sops

brew config output
HOMEBREW_VERSION: 3.1.10-12-g9657303
ORIGIN: https://github.com/Homebrew/brew
HEAD: 9657303ed2c484a4bd8f7527706940f9e4d43354
Last commit: 10 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: be0a915495ac97a9c3a3767bf7aeb81ff60f0d21
Core tap last commit: 79 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.pXb6SUPEpW/org.macosforge.xquartz:0
HOMEBREW_EDITOR: nvim
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: octa-core 64-bit kabylake
Clang: 12.0.0 build 1200
Git: 2.32.0 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 10.15.7-x86_64
CLT: <IP_ADDRESS>.29
Xcode: 12.4
XQuartz: 2.7.11 => /opt/X11

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed kegs have no formulae!
This means they were either deleted or installed with `brew diy`.
You should find replacements for the following formulae:
  python@2

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  node@10

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
  /Users/alwc/.pyenv/shims/python2-config
  /Users/alwc/.pyenv/shims/python3.6m-config
  /Users/alwc/.pyenv/shims/python3.7-config
  /Users/alwc/.pyenv/shims/python2.7-config
  /Users/alwc/.pyenv/shims/python3.7m-config
  /Users/alwc/.pyenv/shims/python-config
  /Users/alwc/.pyenv/shims/python3-config
  /Users/alwc/.pyenv/shims/pybind11-config
  /Users/alwc/.pyenv/shims/python3.6-config
  /Users/alwc/.pyenv/shims/pre-commit-validate-config
  /Users/alwc/.pyenv/shims/python3.8-config

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/python2.7/greenlet/greenlet.h

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  ctags
  python@2
  imath
  xpdf
  openexr
  kubernetes-cli

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I'm trying to install https://github.com/mozilla/sops via homebrew.
What happened (include all command output)?
$ brew install sops
==> Downloading https://ghcr.io/v2/homebrew/core/sops/manifests/3.7.1
Already downloaded: /Users/alwc/Library/Caches/Homebrew/downloads/0f6dc8cd3317e157e9e2fe9ebdbea40421232c4c77287e80ea349ad5ddb8735c--sops-3.7.1.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/sops/blobs/sha256:f95b128d36ffb171695376d011dbf1fc971117152367c109f6232949b45e710a
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:f95b128d36ffb171695376d011dbf1fc971117152367c109f6232949b45e710a?se=2021-06-08T10%3A40%3A00Z&sig=4IuK0lhTlhZgzjerGunAwlAu8aDg7N60Dho5eKMXI98%3D&sp=r&spr=https&sr=b&sv=2019-12-12
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
Warning: Transient problem: HTTP error Will retry in 2 seconds. 2 retries
Warning: left.
Warning: Transient problem: HTTP error Will retry in 4 seconds. 1 retries
Warning: left.
-=O=- #   #   #     #
curl: (22) The requested URL returned error: 502
Error: Failed to download resource "sops"
Download failed: https://ghcr.io/v2/homebrew/core/sops/blobs/sha256:f95b128d36ffb171695376d011dbf1fc971117152367c109f6232949b45e710a

What did you expect to happen?
I expect brew can successfully install sops.
Step-by-step reproduction instructions (by running brew commands)
brew install sops

A lot of things aren't working on GitHub at the moment. It may be related to the Fastly outage. Try again when that's been resolved.


RemoveSnapshot extraction to cli tool

RemoveSnapshot extraction to cli tool
Changed the way imports work by allowing optional restorePath option to be passed with restore files made by step 1 above.

How to run the tool in the tests section:
https://docs.google.com/document/d/1_VvoFoF7CUr-JmZX-P87goEnLeGyvqj4xipQOwK6Fq8/edit?resourcekey=0-QUIAOhP9FV_9A2IfsLhWnw&tab=t.0


Asura URL Update #3

Gotta love Asura

No idea why it's referencing #3 but I'll create a new PR if needed

No idea why it's referencing #3 but I'll create a new PR if needed

Remove #3 from your pr title


Add tokens to existing lock (MsgServer impl)

Codecov Report

Merging #488 (9dc42ed) into main (4b49edf) will increase coverage by 0.03%.
The diff coverage is 40.47%.

@@            Coverage Diff             @@
##             main     #488      +/-   ##
==========================================
+ Coverage   20.20%   20.24%   +0.03%
==========================================
  Files         163      163
  Lines       23358    23400      +42
==========================================
+ Hits         4720     4737      +17
- Misses      17878    17900      +22
- Partials      760      763       +3

Impacted Files
Coverage Δ

x/lockup/handler.go
0.00% <0.00%> (ø)

x/lockup/keeper/msg_server.go
0.00% <0.00%> (ø)

x/lockup/client/cli/tx.go
65.95% <70.83%> (+1.67%)
:arrow_up:

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 4b49edf...9dc42ed. Read the comment docs.

I suggest that for now we remove the new message, and just change the existing lock function to use AddTokensToLock internally. We can explore more once there are usecases that would need it, whether we should be supporting multiple locks per user-duration pair.


Datasource getActiveTablesAsync Method triggers an internal error

I used tableau log viewer to collect some of the log data:

Thanks for reporting @tjallingt, may I ask what underlying datasources you were connected to?

Oh I'm sorry i forgot to mention, this extension is running inside the superstore dashboard that is included in the tableau desktop installation

Thanks Tjalling. I've logged this internally and will have someone on the team investigate.


fix(icon): now getting from font awesome

now getting from font awesome
✅ Closes: COMUI-2683

The carets in the content search seem a little out of alignment on this branch.
This branch is shown on the left and the current WCL version is on the right:

This will be a v5 issue


Address issue #1122

Issue #1122
takes care of an inconsistency between _prepare_packed_dataloader
and _prepare_non_packed_dataloader
Fixes #1122

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Good point. I think ones_like requires a tensor as input so I just did ones(len(example))

Hi, I will revert this PR because it seems that now simple snippets do not work anymore
from datasets import load_dataset
from trl import SFTTrainer

dataset = load_dataset("imdb", split="train")

trainer = SFTTrainer(
    "facebook/opt-350m",
    train_dataset=dataset,
    dataset_text_field="text",
    max_seq_length=512,
)
trainer.train()

Let's figure out a more global fix. I will make a patch release

What is exactly the error it gives? In my modest PC I cannot run that snippet


CU-86a1hupze - Refactor test_function.py to use BoaTestConstructor

Summary or solution description
Refactored test_function file to use boatestconstructor in place of TestRunner for unit testing.
Updated boa-test-constructor dependency version and changed BoaTestCase with the new version fixes

Task linked: CU-86a1hupze Refactor test_function.py to use BoaTestConstructor

coverage: 92.102%. remained the same
when pulling 9bc223c8f480ad9d373ff96ba4ea7ead7b49e8cd on CU-86a1hupze
into 91503ec29a3724b77dd2517b24bcb142636eecbe on development.


Master branch don't have docs folder

Is docs folder is exclude by intend?

the master branch is in sort of an in-between state while work through the v3 api. in the mean time the v2 docs are at https://github.com/redux-loop/redux-loop/tree/v2.2.2/docs


Update Snownews links

Fixes #1607.

Coverage remained the same at 58.662% when pulling 3946468a6b37713fff386853412c5e2662602ebf on feature/relink-snownews into 614d5b7c8020d84957a4a821f161bc0f0d7a448c on master.

Thank you for taking a look Lyse!


PSA API fails with: oauth2: "invalid_grant" "grant is invalid"

Describe the bug
After some days or weeks the connection to PSA API breaks.
As a result, the SoC is unknown and planned charging does not work anymore.
Restart of cvcc solves the problem.
Is there a way to catch this and force a kind of re-authentication like a cvcc restart does?
Can I add even more details to the log beyond "Peugeot: trace"?
Steps to reproduce
No special steps, just wait and after few days it happens.

Car was connected with 21% SoC and initial query of the API seems to be fine.
5 minutes later the PSA API seems to report a timeout.
Same logs continue for about 3 hours without actually changing to the configured minimum SoC of 50%.
7.5 hours later there's a disconnect event without touching the car, but API error remains the same:

All logs are in attached file.
logs.txt
Configuration details
<details><summary>Konfiguration (/etc/evcc.yaml)</summary>

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: info
levels:
  cache: error
  peugeot: trace

interval: 10s # control cycle interval

sponsortoken: *****

meters:
- name: myPV
  type: template
  template: fronius-solarapi-v1
  host: fronius.f17a
  usage: pv
- name: myGrid
  type: custom
  power:
    source: mqtt
    topic: meter/energy/gridPowerCombined
- name: myHK
  type: homematic
  uri: homematic-raspi.f17a:2001
  device: NEQ0115240
  meterchannel: 2
  cache: 30s

chargers:
- name: myWallbox
  type: template
  template: go-e-v3
  host: go-eCharger_112810.f17a

vehicles:
- name: my208e
  type: template
  template: peugeot
  title: e-208
  user: *****
  password: *****
  capacity: 50

loadpoints:
- title: Garage
  charger: myWallbox
  vehicle: my208e
  mode: pv
  phases: 0
  mincurrent: 6
  maxcurrent: 16

site:
  title: F17a
  meters:
    grid: myGrid
    pv: myPV
    aux: myHK

# tariffs are the fixed or variable tariffs
# cheap (tibber/awattar) can be used to define a tariff rate considered cheap enough for charging
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price
    type: fixed
    price: 0.3205 # EUR/kWh Nov 2023
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.0943 # EUR/kWh
  planner:
    type: grünstromindex
    zip: *****

influx:
  url: http://influxCT.f17a:8086
  database: evcc # InfluxDB v2.x uses term `bucket` but for compatibility still named `database` here
  token: *****
  org: F17a

# mqtt message broker
mqtt:
  broker: ioBrokerVM.f17a:1883
  topic: evcc # root topic for publishing, set empty to disable publishing

# push messages
messaging:
  events:
    connect: # vehicle connect event
      title: "{{.vehicleTitle}} connected on wallbox {{.title}}"
      msg: |
        {{.vehicleTitle}} connected on wallbox {{.title}} at {{round (divf .pvPower 1000) 2 }} kW PV.
    disconnect: # vehicle connected event
      title: "{{.vehicleTitle}} disconnected of wallbox {{.title}}"
      #msg: Car disconnected after ${connectedDuration}
      msg: |
        {{.vehicleTitle}} disconnected of wallbox {{.title}} after {{.connectedDuration}} with {{round (.vehicleSoc) 0 }} % SoC.
        Charged {{round (divf .chargedEnergy 1000) 2 }} kWh with {{round (.sessionSolarPercentagei) 0}} % collected from the sun :-)
    soc: # vehicle soc update event
      title: SoC updated
      msg: "Battery charged to ${vehicleSoc:%.0f}%"
  services:
  - type: pushover
    app: *****
    recipients: *****
    - CcremovedremovedremovedOR4 # user key for all devices
    devices:
    - iPhone13

</details>

Log details
Restarting cvcc resolves the problem:

[main  ] INFO 2024/01/07 08:03:41 evcc 0.123.5
[main  ] INFO 2024/01/07 08:03:41 using config file: /etc/evcc.yaml
[main  ] INFO 2024/01/07 08:03:41 starting ui and api at :7070
[db    ] INFO 2024/01/07 08:03:42 using sqlite database: /home/marco/.evcc/evcc.db
[mqtt  ] INFO 2024/01/07 08:03:42 connecting evcc-412648543 at tcp://ioBrokerVM.f17a:1883
[mqtt  ] DEBUG 2024/01/07 08:03:42 tcp://ioBrokerVM.f17a:1883 connected
[mqtt  ] DEBUG 2024/01/07 08:03:42 tcp://ioBrokerVM.f17a:1883 subscribe meter/energy/gridPowerCombined
[peugeot] TRACE 2024/01/07 08:03:42 POST https://idpcvs.peugeot.com/am/oauth2/access_token
[peugeot] TRACE 2024/01/07 08:03:42 grant_type=password&password=***&scope=openid+profile&username=***
--
{"access_token":"1561db03-2b5e-419b-bff4-73cb88c199d6","refresh_token":"0de41a03-48cb-4696-ab8d-e907b514a557","scope":"openid profile","id_token":"eyAidHlwIjogIkpXVCIsICJraWQiOiAiU3lsTEM2Tmp0MUtHUWt0RDlNdCswemNlUVNVPSIsICJhbGciOiAiUlMyNTYiIH0.eyAiYXRfaGFzaCI6ICJtb0d0WGoxUExzQ3Nzel91VkxiR1hBIiwgInN1YiI6ICJBUC1BQ05UMjAwMDA3NjE1NzM0IiwgImlzcyI6ICJodHRwczovL2lkcGN2cy5wZXVnZW90LmNvbTo0NDMvYW0vb2F1dGgyIiwgInRva2VuTmFtZSI6ICJpZF90b2tlbiIsICJnaXZlbl9uYW1lIjogIk1hcmNvIiwgImF1ZCI6IFsgIjFlZWJjMmQ1LTVkZjMtNDU5Yi1hNjI0LTIwYWJmY2Y4MjUzMCIgXSwgIm9yZy5mb3JnZXJvY2sub3BlbmlkY29ubmVjdC5vcHMiOiAiZDUyMTg5NGItNzM3Mi00ZjMzLWI1NWEtNTk3OTkwZTBhZjZkIiwgInVwZGF0ZWRfYXQiOiAiMCIsICJhenAiOiAiMWVlYmMyZDUtNWRmMy00NTliLWE2MjQtMjBhYmZjZjgyNTMwIiwgImF1dGhfdGltZSI6IDE3MDQ2MTEwMjIsICJyZWFsbSI6ICIvY2xpZW50c0IyQ1BldWdlb3QiLCAiZXhwIjogMTcwNDYxMTYyMiwgInRva2VuVHlwZSI6ICJKV1RUb2tlbiIsICJpYXQiOiAxNzA0NjExMDIyLCAiZmFtaWx5X25hbWUiOiAiR2Vpc2xlciIgfQ.R9eQRdazeI6KlW4lkPei6Z95WQ93dnopok2tXR_iRitP_F8fhFeOrwDTJDwvzJ4t_v3OHHjVMEFQygkJ242pwV17ZTsLbaeUfIISkeE6hwfvC7HXmMCQApYAt2I4-F6aYObfkAvOSXcrv5ikYdOf509aOY36pVhlh53X3jCjk0w","token_type":"Bearer","expires_in":3599}
[peugeot] TRACE 2024/01/07 08:03:42 GET https://api.groupe-psa.com/connectedcar/v4/user/vehicles?client_id=1eebc2d5-5df3-459b-a624-20abfcf82530
[peugeot] TRACE 2024/01/07 08:03:43 {"_links":{"last":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles?pageToken=e15590d9a0ceccc82623bccdeb807eedAAAAAQAAAAEAAAABAAAAPAACMC0"},"self":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles?pageToken=e15590d9a0ceccc82623bccdeb807eedAAAAAQAAAAEAAAABAAAAPAACMC0"},"first":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles?pageToken=e15590d9a0ceccc82623bccdeb807eedAAAAAQAAAAEAAAABAAAAPAACMC0"}},"total":1,"totalPage":1,"currentPage":1,"_embedded":{"vehicles":[{"_links":{"collisions":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/collisions"},"alarms":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/alarms"},"callbacks":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/callbacks"},"alerts":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/alerts"},"trips":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/trips"},"self":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783"},"lastPosition":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/lastPosition"},"remotes":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/callbacks/{cbid}/remotes","templated":true},"telemetry":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/telemetry"},"user":{"href":"https://api.groupe-psa.com/connectedcar/v4/user"},"maintenance":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/maintenance"},"status":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/status"},"monitors":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/callbacks/{cbid}/monitors","templated":true}},"id":"17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783","vin":"VR3UHZKXZNT109814","brand":"Peugeot","pictures":["https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=001","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=002","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=003","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=004","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=005","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=006","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=007","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=008","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=009","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=010","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=011","https://visuel3d-secure.peugeot.com/V3DImage.ashx?client=miseco&back=0&format=png&version=1PP2A5ZESFB0A0D1&color=0MM60NSM&trim=0PD70RFX&OPT1=DLZ0&OPT2=DNA0&OPT3=DWY4&view=012"]}]}}
[lp-1  ] DEBUG 2024/01/07 08:03:43 charge total import: 3772.565kWh
[site  ] INFO 2024/01/07 08:03:43 site config:
[site  ] INFO 2024/01/07 08:03:43   meters:      grid ✓ pv ✓ battery ✗
[site  ] INFO 2024/01/07 08:03:43     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/01/07 08:03:43     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/01/07 08:03:43   vehicles:
[site  ] INFO 2024/01/07 08:03:43     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✗
[lp-1  ] INFO 2024/01/07 08:03:43 loadpoint 1:
[lp-1  ] INFO 2024/01/07 08:03:43   mode:        pv
[lp-1  ] INFO 2024/01/07 08:03:43   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2024/01/07 08:03:43   meters:      charge ✓
[lp-1  ] INFO 2024/01/07 08:03:43     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2024/01/07 08:03:43 phase timer inactive
[lp-1  ] DEBUG 2024/01/07 08:03:43 pv timer inactive
[lp-1  ] DEBUG 2024/01/07 08:03:43 guard timer inactive
[lp-1  ] INFO 2024/01/07 08:03:43 vehicle updated: unknown -> e-208
[site  ] WARN 2024/01/07 08:03:43 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2024/01/07 08:03:43 ----
[lp-1  ] DEBUG 2024/01/07 08:03:43 charge power: 0W
[site  ] DEBUG 2024/01/07 08:03:43 pv power: 0W
[site  ] DEBUG 2024/01/07 08:03:43 grid power: 529W
[site  ] DEBUG 2024/01/07 08:03:43 aux power 1: 0W
[site  ] DEBUG 2024/01/07 08:03:43 aux power: 0W
[site  ] DEBUG 2024/01/07 08:03:43 site power: 529W
[peugeot] TRACE 2024/01/07 08:03:43 GET https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/status?client_id=1eebc2d5-5df3-459b-a624-20abfcf82530
[peugeot] TRACE 2024/01/07 08:03:44 {"createdAt":"2024-01-06T17:23:00Z","updatedAt":"2024-01-06T17:23:00Z","lastPosition":{"type":"Feature","geometry":{"type":"Point","coordinates":[11.47108,49.0289,377]},"properties":{"createdAt":"2024-01-06T17:22:55Z","heading":101,"type":"Acquire","signalQuality":4,"fixStatus":"3D"}},"engines":[{"type":"Electric","speed":0,"gmpStatus":"Stopped","createdAt":"2024-01-06T17:23:00Z"}],"powertrain":{"createdAt":"2024-01-06T17:23:00Z","status":"Stopped"},"ignition":{"createdAt":"2024-01-06T17:16:33Z","type":"Stop"},"battery":{"voltage":86.5,"createdAt":"2024-01-06T17:16:33Z"},"privacy":{"createdAt":"2024-01-06T17:23:00Z","state":"None"},"lightingSystem":{"turn":[{"direction":"Right","position":"Front","status":"Off"},{"direction":"Right","position":"Rear","status":"Off"},{"direction":"Left","position":"Front","status":"Off"},{"direction":"Left","position":"Rear","status":"Off"}],"fog":[{"direction":"Left","position":"Front","status":"Off"},{"direction":"Right","position":"Front","status":"Off"},{"direction":"Left","position":"Rear","status":"Off"},{"direction":"Right","position":"Rear","status":"Off"}],"createdAt":"2024-01-06T17:23:00Z"},"service":{"createdAt":"2023-07-01T07:11:48Z","type":"Electric"},"safety":{"createdAt":"2023-07-01T07:11:49Z","beltStatus":[{"belt":"Omission","id":"Driver"},{"belt":"Omission","id":"Passenger"}],"autoECallTriggering":"NotDetected"},"environment":{"luminosity":{"createdAt":"2024-01-06T17:16:33Z","day":false},"air":{"createdAt":"2024-01-06T17:16:33Z","temp":4}},"odometer":{"createdAt":"2024-01-06T17:16:33Z","mileage":22000.2},"kinetic":{"createdAt":"2024-01-06T17:23:00Z","acceleration":0,"speed":0,"moving":false},"_links":{"self":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783/status?profile=endUser"},"vehicle":{"href":"https://api.groupe-psa.com/connectedcar/v4/user/vehicles/17f6bb30fd59de2fc077716f14303abafebda543c56c8a9929e12ca10e41671449ed72bc562b77af1561d157bef0feb79fd954380d4402fa06f139425b1afe77774eac2567255734cacdf5aaa64a172f8c4c1f3b596dd25345b99c707ba1b6783"}},"preconditioning":{"airConditioning":{"createdAt":"2024-01-06T17:16:34Z","updatedAt":"2024-01-06T17:16:34Z","status":"Disabled","programs":[{"enabled":false,"slot":1,"recurrence":"Daily","start":"PT6H30M","occurence":{"day":["Wed"]}},{"enabled":true,"slot":2,"recurrence":"Daily","start":"PT6H30M","occurence":{"day":["Tue"]}}]}},"energies":[{"createdAt":"2024-01-06T17:22:22Z","type":"Electric","subType":"ElectricEnergy","level":21,"autonomy":46,"extension":{"electric":{"battery":{"load":{"createdAt":"2024-01-06T17:22:22Z","capacity":34304,"residual":5344}},"charging":{"plugged":true,"status":"Disconnected","remainingTime":"PT0S","chargingRate":0,"chargingMode":"No","nextDelayedTime":"PT16H"}}}}],"preconditionning":{"airConditioning":{"createdAt":"2024-01-06T17:16:34Z","updatedAt":"2024-01-06T17:16:34Z","status":"Disabled","programs":[{"enabled":false,"slot":1,"recurrence":"Daily","start":"PT6H30M","occurence":{"day":["Wed"]}},{"enabled":true,"slot":2,"recurrence":"Daily","start":"PT6H30M","occurence":{"day":["Tue"]}}]}},"energy":[{"createdAt":"2024-01-06T17:22:22Z","updatedAt":"2024-01-06T17:22:23Z","type":"Electric","level":21,"autonomy":46,"charging":{"plugged":true,"status":"Disconnected","remainingTime":"PT0S","chargingRate":0,"chargingMode":"No","nextDelayedTime":"PT16H"}}]}
[lp-1  ] DEBUG 2024/01/07 08:03:44 vehicle odometer: 22000km
[lp-1  ] DEBUG 2024/01/07 08:03:44 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2024/01/07 08:03:44 charge total import: 3772.565kWh
[lp-1  ] DEBUG 2024/01/07 08:03:44 charger status: B
[lp-1  ] INFO 2024/01/07 08:03:44 car connected
[lp-1  ] DEBUG 2024/01/07 08:03:44 pv timer elapse
[lp-1  ] DEBUG 2024/01/07 08:03:44 pv timer inactive
[lp-1  ] DEBUG 2024/01/07 08:03:44 charger: guard elapse
[lp-1  ] DEBUG 2024/01/07 08:03:44 guard timer inactive
[lp-1  ] DEBUG 2024/01/07 08:03:44 charge total import: 3772.565kWh
[lp-1  ] DEBUG 2024/01/07 08:03:44 vehicle status: B
[lp-1  ] DEBUG 2024/01/07 08:03:44 vehicle soc: 21%
[lp-1  ] DEBUG 2024/01/07 08:03:44 vehicle range: 46km
[lp-1  ] DEBUG 2024/01/07 08:03:44 set my208e plan soc: 0 @ 0001-01-01 00:53:28 +0053 LMT
[lp-1  ] DEBUG 2024/01/07 08:03:44 available power -529W < 4140W min 3p threshold
[lp-1  ] DEBUG 2024/01/07 08:03:44 phase scale1p in 0s
[pushover] DEBUG 2024/01/07 08:03:44 sending to ***
[lp-1  ] DEBUG 2024/01/07 08:03:44 switched phases: 1p
[lp-1  ] DEBUG 2024/01/07 08:03:44 phase timer inactive
[lp-1  ] DEBUG 2024/01/07 08:03:44 pv charge current: 0A = 0A + -2.3A (529W @ 1p)
[lp-1  ] DEBUG 2024/01/07 08:03:44 pv enable timer reset
[lp-1  ] DEBUG 2024/01/07 08:03:44 pv timer inactive

What type of operating system are you running?
Linux
Version
0.123.5

Bitte trace log.

I don't think there's anything to do. We have a valid refresh token. Refresh fails with unspecified server timeout. Afterwards refresh totally fails with previously valid refresh token. My guess: PSA had a infrastructure hick-up and invalidated all tokens. Since we're not seeing this regularly wontfix.

Okay, ich schalte alles auf trace und warte ab bis es wieder auftritt.

Could you try finding a log that does not have a timeout error before? Or does it always happen together with a timeout error?

I have only the last 3 occurrences due to log rotate, and it is always after that same timeout error.
But I'll keep an eye on it in the future once it happens again.

Does it ever refresh successfully? Think it did in the original log. So not sure what is going on at PSA...

It did refresh a number of times until it broke after the timeout at 18:48.
164:Dec 31 16:09:25 evccCT evcc[581451]: [peugeot] TRACE 2023/12/31 16:09:25 grant_type=refresh_token&refresh_token=e33aab16-9fa8-4ce3-a541-66d2347c94f2
513:Jan  2 08:03:24 evccCT evcc[581451]: [peugeot] TRACE 2024/01/02 08:03:24 grant_type=refresh_token&refresh_token=75b2ed6d-c7bb-4cf2-abaa-e672408ad944
569:Jan  2 12:25:34 evccCT evcc[581451]: [peugeot] TRACE 2024/01/02 12:25:34 grant_type=refresh_token&refresh_token=938db208-5f60-4e5e-9a0b-d759c92ec5d5
589:Jan  2 13:26:14 evccCT evcc[581451]: [peugeot] TRACE 2024/01/02 13:26:14 grant_type=refresh_token&refresh_token=a768f870-794d-48b9-b72e-28b222e97c7a
611:Jan  2 14:26:54 evccCT evcc[581451]: [peugeot] TRACE 2024/01/02 14:26:54 grant_type=refresh_token&refresh_token=f8f4509d-c08a-44e8-bad1-f7ab3cd686fd
630:Jan  2 15:27:34 evccCT evcc[581451]: [peugeot] TRACE 2024/01/02 15:27:34 grant_type=refresh_token&refresh_token=ede69ae1-d561-4bc2-b812-196458426492
707:Jan  2 21:08:54 evccCT evcc[581451]: [peugeot] TRACE 2024/01/02 21:08:54 grant_type=refresh_token&refresh_token=114ddf61-dfa2-48fb-9388-44cdcbc22ae1
823:Jan  3 10:08:25 evccCT evcc[581451]: [peugeot] TRACE 2024/01/03 10:08:25 grant_type=refresh_token&refresh_token=614db5e4-f136-4bd3-8dba-89cb69c4e4a7
1171:Jan  4 07:36:26 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 07:36:26 grant_type=refresh_token&refresh_token=f913cd59-3f27-4b6e-b8b2-7a29cf6a57d9
1190:Jan  4 08:44:56 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 08:44:56 grant_type=refresh_token&refresh_token=f52be6f8-df9f-4b79-ac63-8704e90f76fe
1214:Jan  4 09:45:26 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 09:45:26 grant_type=refresh_token&refresh_token=fc524313-c258-40fc-a2e5-717145083d6f
1294:Jan  4 17:45:36 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 17:45:36 grant_type=refresh_token&refresh_token=5f825017-74d1-4fce-b414-6b8fccb15a0f
1318:Jan  4 18:48:25 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 18:48:25 grant_type=refresh_token&refresh_token=f1a7f686-f46a-4e4a-832c-a18d805b9f92
1324:Jan  4 18:48:35 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 18:48:35 grant_type=refresh_token&refresh_token=f1a7f686-f46a-4e4a-832c-a18d805b9f92
1332:Jan  4 18:48:56 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 18:48:56 grant_type=refresh_token&refresh_token=f1a7f686-f46a-4e4a-832c-a18d805b9f92
1342:Jan  4 18:49:25 evccCT evcc[593399]: [peugeot] TRACE 2024/01/04 18:49:25 grant_type=refresh_token&refresh_token=f1a7f686-f46a-4e4a-832c-a18d805b9f92```

This seems to indicate that refresh is working until PSA has a hickup. If this is a new problem let's monitor it for some time. If you're running on docker you could for example restart the container each night to trigger new login. If it persist we'll need to think about logging in again when refresh fails.

Good idea but this is a Proxmox LXC.
I will wait until it happens again and then look at the evcc API to see if anything indicates the problem. If so, I'll send a push message to myself to restart evcc.
If I figure out anything I'll update this ticket.
Thanks for your time looking into it 👍


Resample forces particle weights to uniform

In smc.py in the resample function new particles, and weights are requested from the resampler. However, several lines down the new weights are set to be uniform. This behaviour seems undesirable as the author of new resampler would expect their returned weights would become the new updater weights. For example Liu-West Resampler should just return the uniform weights itself.
    self.particle_weights, self.particle_locations = \
        self.resampler(self.model, self.particle_weights, self.particle_locations)

    # Possibly canonicalize, if we've been asked to do so.
    if self._canonicalize:
        self.particle_locations[:, :] = self.model.canonicalize(self.particle_locations)

    # Reset the weights to uniform.
    self.particle_weights[:] = (1/self.n_particles)

I will submit a small patch removing the above line.

I believe this is now fixed with merging in #73.


GO2 is crawling in Gazebo &  talker-listener program

Hi, thank you for sharing the code!
I followed your project to the step "Run: Go2 navigates 2 goal", and I got the same result as in your README, but I noticed that in Gazebo, the dog's posture is lying down, which means that the GO2 is crawling instead of walking. I want to know if I can make the dog stand up and walk.
In addition, if I want to connect with my real GO2 I may need a talker-listener program. Is there such a program in the project?
Thanks for sharing this code, it helps me a lot.

Hi @xutianzhuo,
I'm glad it was useful for you!
So in the gait.yaml file, the nominal_height parameter needs to be changed around .25.
I also later discovered that the odom_scaler parameter can be used instead of the modifications I made to the line 189, 190 of state_estimation.cpp needs to be reverted back to without the 2x multiplier. (Since odom_scalar does the same).
I also later discovered that depending on the computer (say RTF of .5 vs a RTF of 1) the robot behaves differently and therefore needs some more parameter changes in the gait.yaml file to tackle those issues.
(If it is working fine for you then nevermind that, else i shall elaborate further, and probably update the repo and readme accordingly)
About the hardware interfacing i haven't looked into it yet, therefore would be able to give the best answer. But i think you should look at the ROS2 repo of the oficial unitree go2 repos. I believe they have explained the hardware interfacing in that repo.
Regards
Arjun


Force instaling binary packages only

When you ask Nix to install a package, it will first try to get it in pre-compiled form from a binary cache. By default, Nix will use the binary cache https://cache.nixos.org ; it contains binaries for most packages in Nixpkgs. Only if no binary is available in the binary cache, Nix will build the package from source.

is it possible to force installing binary/pre-compiled packages only and fail if not found?
Basically, the opposite of this

You do this by adding some extra flag to nix commands
nix-build ... --builders '' --max-jobs 0

If you run nix-env --prebuilt-only when installing packages, it will fail if it cannot find the package from a binary cache, rather than falling back to compiling from src.  See nix-env --help for details.
A similar option does not exist on nix-build, as far as I can tell from reading the src.

thank you, nix-env --prebuilt-only --install did the trick.

@eadmaster i think you actually want --max-jobs 0 (poorly named)
❯ nix-build --no-out-link lolhello.nix --option max-jobs 0
these derivations will be built:
  /nix/store/vwrgdjl9h1h53ch2zh8cb18nd2raz8a7-lolhello.drv
these paths will be fetched (0.35 MiB download, 0.34 MiB unpacked):
  /nix/store/vgaqghyhgk3apb503q5483v8cmn32ggm-hello-2.3.tar.bz2
error: 1 derivations need to be built, but neither local builds ('--max-jobs') nor remote builds ('--builders') are enabled

I think a better name to mimic "substitute" should be present.


enhance: add support for azure deployment name mapping

#43
Add a configurable env variable to set the azure deployment name to be used in lieu of the model name. Migrate away from using the snapshotted fork of go-openai, and add a hack for passing temperature.

@keyallis thank you for this PR!
I tried use your changes already locally however I ran into the situation that gptscript is waiting for the model response "for ever":
[...]
{
  "completionID": "1",
  "id": "1",
  "level": "debug",
  "logger": "pkg/monitor",
  "msg": "messages",
  "parentID": "",
  "request": {
    "model": "gpt-4-turbo-preview",
    "messages": [
      {
        "role": "system",
        "content": "\nYou are task oriented system.\nYou receive input from a user, process the input from the given instructions, and then output the result.\nYour objective is to provide consistent and correct results.\nYou do not need to explain the steps taken, only provide the result to the given instructions.\nYou are referred to as a tool.\n"
      },
      {
        "role": "system",
        "content": "Say hello world"
      }
    ],
    "temperature": 1e-8
  },
  "time": "2024-02-27T17:02:22+01:00",
  "toolID": "examples/helloworld.gpt:1"
}
         content  [1] content | Waiting for model response...

Have you ran into this to sometimes?

Hey @danielhass, thanks for taking a look. I'm curious what variables you're setting when testing this? These are the ones I have set:
OPENAI_API_KEY
OPENAI_URL
OPENAI_API_TYPE
OPENAI_AZURE_DEPLOYMENT

If you don't have all of these set then it might not be picking up the changes included

Hey @danielhass, thanks for taking a look. I'm curious what variables you're setting when testing this? These are the ones I have set:
OPENAI_API_KEY
OPENAI_URL
OPENAI_API_TYPE
OPENAI_AZURE_DEPLOYMENT

If you don't have all of these set then it might not be picking up the changes included

@keyallis I used the following set of env vars:
export OPENAI_API_VERSION="2024-02-15-preview"
export OPENAI_AZURE_DEPLOYMENT="gpt-4"
export OPENAI_API_KEY="xxx"
export OPENAI_BASE_URL="https://xxx.openai.azure.com/"
export OPENAI_API_TYPE="AZURE"

@keyallis 💯 - changing to OPENAI_API_VERSION="2023-05-15" resolved the issue!
Shall we add this to the docs for the Azure variant?

@danielhass I've omitted mention of the OPENAI_API_VERSION in the getting started flow to keep it more general. If a value is not set for that field then it defaults to the value 2023-05-15.

@keyallis didn't know about the default. Makes total sense not do mention it in that case :+1:
Thanks for bringing this to gptscript!


Unified macros for defining static bignums

This looks good to me.  @dot-asm and @ekasper , what do you think?  I like that it replaces cut/paste with a unified approach.

While converting bn_consts might be good idea, bn_pack2 implementation is not right. It was already shown that packing by 0x##af is error-prone, see RT3165 and 2df9ec01d563f9cc2deab07e8c3391059d476592. On  we see mention of ##ULL in bn_pack2, but not here. ULL is getting archaic, but it seems that it was corrected already after feedback on the list[?].
As for "might be". What is suggestion for bn_const.c exactly? To replace call to BN_bin2bn with call to BN_copy or BN_dup. This means that we don't win anything in memory footprint (nor "protect" the said constants by placing them to read-only segment). But we loose something. Comparing RFC text and code (or re-pasting from RFC through regexp) text becomes more challenging than it is now. What I'm saying is that it makes lesser sense [to me] to change bn_const.c unless we win something tangible, e.g. ensure that BN_get_* callers can handle BN_FLG_STATIC_DATA and return pointers to the original data instead of making copies.
Then I would also be reluctant to accept patch verbatim, but re-implement constant transform part myself. Because eyeballing can't catch bit replacements.  I'm not saying that there are any, but it probably inappropriate to assume that there may not be one. Nothing personal @huangqinjin. Unless of course it's confirmed that changing any bit in any constant in question triggers 'make test' failure. And I can't confirm this. While unification is a worthy goal critical BN constants has this unpleasant inertia :-(

As per comments from @dot-asm, this patch is not accepted so closing.


DatePickerInput calls 'onClick' prop even if it's not passed to the component

Description
DatePickerInput component calls the onClick prop event if it was not passed in. This results in a TypeError: _onClick is not a function error in the console.
Is this a feature request (new component, new icon), a bug, or a general issue?
A bug.
Is this issue related to a specific component?
Yes. DatePickerInput
What did you expect to happen? What happened instead? What would you like to see changed?
onClick is not a required prop, it shouldn't be called if it wasn't passed to the component.
What version of the Carbon Design System are you using?
v5.31.0
What offering/product do you work on? Any pressing ship or release dates we should be aware of?
A new QRadar App. Initial version released in early April.
Steps to reproduce the issue
https://codesandbox.io/s/k0wqqw8k27
Additional information
Mari Johannessen looked into the issue on Slack and found a workaround by passing an empty onClick: onClick={() => { }}

Could we simply add a default prop?  onClick: () => {}?