Prompts for video styling in a particular artist style?

I have been trying some video stylizations and find it hard to get the prompts to really influence the outcome.  The LORA selected seems much more influencial on the end result.
  If I set the head and tail prompts to "in the style of a painting by giger" and then set the prompts to
"0":"in the style of a painting by giger",
"500":"in the style of a painting by giger"

(500 so it is past the length of the frames to make sure they all get covered) the end result is nothing like giger.
If I try and change the prompts using brackets and weights like
(a highly detailed airbrush painting in the style of giger:1.0),((painted by giger:2.0))
that does not seem to help much if at all.  What is the purpose of the brackets and is doubling them up supposed to enforce the prompt?
I have tried different models and LORAs without much success.  The animation LORAs just give cartoonish results, the "realism" LORAs give big eyed asian girls.  No real giger influence.
Any tips on prompts to get the Video Stylization to be able to stylize a video based on an artist prompt?  The styling for movies using the cartoon LORAs are so temporally smooth and look great.  If only I could control other styles with the prompting?

https://github.com/s9roll7/animatediff-cli-prompt-travel/assets/118420657/5b1314c4-3572-4f00-abf9-0c6c261fd169
https://github.com/s9roll7/animatediff-cli-prompt-travel/assets/118420657/ba223d55-3106-472c-96c1-aaa1c7251e36
It is basically the same as using stable diffusion to output the desired picture.
Of course, if you want to output a picture like Giger's, you need to choose a model that understands Giger's picture.

So those 2 example movies are from using Video Stylizaation in AnimateDiff Prompt Travel to process a source video to lok like the giger aliens?  If so, please share the settings.
I am intrested in styling videos to look like the work of different artists.  So for giger I want to have that biomechanical look, not necessarily have just aliens.
If you (or anyone) can share some settings/models/promprs to get started that would be a big help.  Thanks.

Can you post the "source video" and "prompt.json" here?
I'm not sure what's failing and what you're struggling with.

I think I see my problem now.  I am not editing the prompts into the correct json file.  I put the prompts into the usual prompt_travel.json and not prompt.json for this specifc styling.  So I edit prompt.json with the giger prompt as the head and tail prompt as follows
    "head_prompt": "(painted by giger:0.99)",
    "tail_prompt": "(painted by giger:0.99)",

How exactly do head and tail work?  Are they added at the start and end of every prompt?
And that gives this result.  No change and is not in ther style of giger?
https://github.com/s9roll7/animatediff-cli-prompt-travel/assets/47686889/cfb40d9b-5f89-4581-950f-68fc686231cb

Are they added at the start and end of every other prompt?

yes

"path": "models\\sd\\majicmixRealistic_v5Preview.safetensors",
"lora_map": {
    "share/Lora/muffet_v2.safetensors": 1.0,
    "share/Lora/add_detail.safetensors": 1.0
},

I don't think this model and lora know the word "giger".

OK, that would make sense.
I cannot file the file muffet_v2.safetensors anywhere on my hard drive.
What would a good general model and lora be to use for more general prompts?  Is there a list of compatible LORAs that can be used?

i think you could use this model for giger
https://civitai.com/models/20846/biomechanicals-hr-giger
and/or use this lora
https://civitai.com/models/131840/gigercraftxs
https://civitai.com/models/20846/biomechanicals-hr-giger


fix interval end test error

This PR updates the last remaining place where interval.end is compared with a timestamp, which can cause timing-related test failures.

Codecov Report

Merging #2164 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2164   +/-   ##
=======================================
  Coverage   79.55%   79.55%
=======================================
  Files          85       85
  Lines        8814     8814
  Branches     1888     1888
=======================================
  Hits         7012     7012
  Misses       1541     1541
  Partials      261      261

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 018356b...b9120fe. Read the comment docs.


socketfuzzer/socketclient: migration honggfuzz_socketclinet.py to py3

Migration honggfuzz_socketclinet.py to python3, refactor to get closer with PEP8.

@robertswiecki Request for review.


Vscode latest broken after fedora update

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

VS Code Version: 1.82.2
OS Version: CPE OS Name: cpe:/o:fedoraproject:fedora:38
Kernel: Linux 6.4.15-200.fc38.x86_64

I updated the fedora as I got prompted there's an update
Right after that vs code just all blank

I tried command to kill code killall code then there was a popup

[dxlord.🐼.007] v4final$ killall code
[dxlord.🐼.007] v4final$ code --disable-gpu
[dxlord.🐼.007] v4final$
it worked

This is a better solution https://github.com/microsoft/vscode/issues/193165#issuecomment-1720758749

deleting ? ~/.config/Code/GPUCached do you think that's good idea, I don't think so may be I don't know
@mjbvz what do you think ?
flag or removing cache file

this fix fixed because i have to do this every time
[dxlord.🐼.007] v4final$ killall code
[dxlord.🐼.007] v4final$ code --disable-gpu
[dxlord.🐼.007] v4final$

/duplicate https://github.com/microsoft/vscode/issues/190437
Refs https://code.visualstudio.com/updates/v1_82#_update-highlights-for-chromium


1245 add poster and description to 3d files in model-viewer

Thank you for your contribution to the KodaDot NFT gallery.
👇  _ Do a quick check before the merge.
PR type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted screenshot of demonstrated change in this PR

https://user-images.githubusercontent.com/17953978/146504501-85c863d1-d338-4f50-8cb4-071ed526cbe3.mov
Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything works
[ ] I found edge cases

What's new?

[x] PR closes #1245, #1321
[x] model-viewer now shows poster while loading 3d file. in addition added description for screen readers

Had issue bounty label ?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI, a screenshot for others, is best to understand changes.

What if we could join it together with https://github.com/kodadot/nft-gallery/issues/1321 👀

What if we could join it together with #1321 👀

@yangwao sure thing, ill give it a shot

/giphy perfect!

/giphy perfect!

@yangwao bumped to latest version, safari should be fixed. can't do the AR stuff though 😢

Perfect, I’ve sent the payout https://kusama.subscan.io/extrinsic/0x57129d2181ee81d8f82e2643a2b5a857f57f7620942530eb8627310a88a1fe1d
Let’s grab another issue and get rewarded!
https://github.com/kodadot/nft-gallery/issues/


feat(config): add additional config parameters to Zooz Zen26 and Zen27 and update Zen76/77 parameter language

Adds missing config parameters to the Zooz Zen26 and Zen27 switches. Breaks out features by firmware version. Updates Zen76 and Zen77 parameter labels and descriptions to match the language used in the Zen26 and Zen27.

Oh, wow this is a lot. Will review tomorrow 👍🏻

I think I addressed everything above. I also updated the Zen34 config to match the guidance from the above comments, and added parameter 7 to the Zen76 and Zen77. The online docs don't list it as supported, but I checked with Zooz support, and they confirmed it is supported, and I was able to test it myself to verify.

@blhoward2 anything else you need changed?

Nope

thanks @mattstocum

I will work on updating some of the Zooz configs as I updated many of the OZW config files for them on behalf of Zooz a while back and I can say at a minimum the Zen26 and Zen27 updates here aren't entirely accurate.  For example the firmware should be listed as 2.03, not 2.3 as that is how Zooz themselves refer to it.  Also, I'm not sure where those parameters came from with this merge, but here's is the last update I made for the Zen26 in OZW; https://github.com/OpenZWave/open-zwave/blob/master/config/zooz/zen26.xml.
Any how, I'm excited to hopefully start moving my 150+ devices to ZwaveJS in the coming months and will do what ever I can to help contribute where I can.

Z-Wave JS removes the leading zeros from the version, so 2.3 is the correct value for the firmware version. With regards to the additional parameters for the Zen26 and 27 https://www.support.getzooz.com/kb/article/315-zen26-s2-on-off-switch-ver-3-02-advanced-settings/ and https://www.support.getzooz.com/kb/article/314-zen27-s2-dimmer-ver-3-01-advanced-settings/. I was planning on starting to work on additional Zooz devices and add the metadata for inclusion/exclusion, etc, to the devices I've already added. In the interest of not duplicating work, if you let me know which ones you were going to work on, I'll take them off my list.
On 2/9/2021 9:51:12 PM, bepsoccer<EMAIL_ADDRESS>wrote:
I will work on updating some of the Zooz configs as I updated many of the OZW config files for them on behalf of Zooz a while back and I can say at a minimum the Zen26 and Zen27 updates here aren't entirely accurate. For example the firmware should be listed as 2.03, not 2.3 as that is how Zooz themselves refer to it. Also, I'm not sure where those parameters came from with this merge, but here's is the last update I made for the Zen26 in OZW; https://github.com/OpenZWave/open-zwave/blob/master/config/zooz/zen26.xml [https://github.com/OpenZWave/open-zwave/blob/master/config/zooz/zen26.xml].
Any how, I'm excited to hopefully start moving my 150+ devices to ZwaveJS in the coming months and will do what ever I can to help contribute where I can.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [https://github.com/zwave-js/node-zwave-js/pull/1564#issuecomment-776401032], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AAADDGTM42NNEAHXQNAJ2TDS6HYCBANCNFSM4W7Q2Y6A].

Before you spend time adding the metadata, check whether the Zooz device is in the zwave alliance database. If it is, we'll parse those into the file automatically.

Some of them are, but what's in the alliance DB is pretty bad for Zooz. Does the automatic merge handle devices with multiple firmware revisions, like the Zen26/27?
On 2/10/2021 8:59:56 AM, blhoward2<EMAIL_ADDRESS>wrote:
Before you spend time adding the metadata, check whether the Zooz device is in the zwave alliance database. If it is, we'll parse those into the file automatically.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [https://github.com/zwave-js/node-zwave-js/pull/1564#issuecomment-776723859], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AAADDGU6EE7GDM4M4WAXLEDS6KGNVANCNFSM4W7Q2Y6A].

Yes to the extent they're there.


Backup feature: import-export json configuration of all projects

It would be great if we could export our projects configuration just in case something crashes.

Actually, you already can. The command Project Dashboard: Edit Projects opens the project data as a JSON file, which you can then just save anywhere. Importing works just the other way around: Copy the backup file's contents and paste it in the file opened by the command.
Is it that what you are looking for? :)

Actually, you already can. The command Project Dashboard: Edit Projects opens the project data as a JSON file, which you can then just save anywhere. Importing works just the other way around: Copy the backup file's contents and paste it in the file opened by the command.
Is it that what you are looking for? :)

Yeah that's just what I was looking for, Thanks!

No problem! Glad that I could be of help.
Just for your information: The file that is opened with this command isn't actually the real data storage, it's just a temp file for editing it. Depending on your settings, the project data is saved either in the vscode storage (globalState) or in your user settings.

I also noticed that, thanks!


Use case-insensitive to filter files in search panel in windows plataform

The Windows platform use case-insensitive system files, then it would be better to filter the files regardless of whether the files are in upper or lower case in search panel.
Maybe the best solution will be include the 'Match case' option in 'files to include' field. Seems more simplest for me and a platform indenpendent solution.

https://github.com/microsoft/vscode/issues/10633


[Bug]: Eltako FFKB uses not needed Sender ID

Contact Details
No response
What happened?
When a Eltako FFKB is added, a Sender ID is generated, but it is not needed because this device does not receive anything. When using this device for Window open and tilt detection of 20 Windows much Sender IDs are used.
Could I run in a Limitation with this behavoir?
Adapter Version
v0.6.4
JS-Controller Version
4.0.15
Node JS Version
v14.19.1
NPM Version
6.14.16
Operating System
Ubuntu
Relevant log output
No response
Anything else?

Same behavior for FTKB. It it the same sensor but with Solar Supply.

Can't confirm this.

I also tried reinstall Adapter, delete the device and add new. Same result.
Please try to fix.


Trouble opening in VS2015 update 3

Hi I'm having trouble opening this in vs 2015, update 3.
"vcxproj: The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?LinkId=659044&projecttype=8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942"
Any work around?

@clinton05 Hi! I'll look into it.

Thanks !


Make the to-Boolean coercion (conversion) of a zero (null) pointer, [IntPtr]::Zero / [UIntPtr]::Zero, evaluate to $false

Summary of the new feature / enhancement
0, across all numeric types,  is coerced to $false.
By contrast, a zero pointer is coerced to $true, which is surprising:
[IntPtr]::Zero -eq 0 # -> $true, as expected

# Note: The same applies to [UIntPtr]
[bool] [IntPtr]::Zero # -> !! $true
-not [IntPtr]::Zero   # -> !! $false

In other words: an [IntPtr] / [UIntPtr] instance is currently always coerced to $true,
whereas cocercing [IntPtr]::Zero /[UIntPtr]::Zero  to $false would be less surprising and allow for the usual shorthands (if ($someIntPtr) ... / if (-not $someIntPtr) ...
There should be no backward-compatibility concerns, because the current behavior makes it pointless to evaluate pointers in  a Boolean context (given that the result is always $true).
Proposed technical implementation details (optional)
No response

WG-Engine discussed this today (7/7/2022).
The WG believes this is a fix for consistency's sake which we decided was not compelling.  And given the lack of requests for this feature and a reasonable workaround ($ptr -eq [IntPtr]::Zero), we decided the requested enhancement is not worth pursuing.

Good point, @KalleOlaviNiemitalo, but to me your scenario perfectly exemplifies a bucket 3 change: a breaking change worth making for its benefits, given that it is unlikely that existing code is impacted.
@rkeithhill, the upcoming .NET 7+ change that @KalleOlaviNiemitalo points makes it even more compelling to fix the behavior of [IntPtr] and [UIntPtr], more fundamentally - see #17677
On a philosophical note re, re the proposed change not being compelling:
PowerShell has amassed a sizable collection of warts, some of which cannot be fixed if backward compatibility must be maintained.
Leaving warts that can be removed in place ensures that the pain of stumbling upon them is carried forward, tripping up not only newcomers, but even seasoned users who may have stumbled upon them before, but have forgotten about them.
A (reasonable) workaround being available is not sufficient to ease this pain.
(And that a fix wasn't requested doesn't mean that people haven't run into the problem or don't want a fix. Especially pre-open-source, PowerShell users were successfully trained to resign themselves to what they were given and to live with workarounds.)
For that reason, (not-too-breaking) wart removals are compelling in general, except perhaps if the implementation effort is too great, which I don't think is the case here.


python setup.py build not working

The bug
If we run python setup.py build we get an error ModuleNotFoundError: No module named 'setuptools_rust'
Note that if I run pip install --editable . that works.
@paulbkoch or @riedgar-ms is this something specific to my system or should we throw an error for the setup.py install route (and point people to pip or other pyproject.toml based package manager)?

Might just be a matter of adding setuptools_rust as a dependency? https://pypi.org/project/setuptools-rust/

I think Harsha is correct.

And other possibility is that something else in the optional [test] tag is installing setuptools_rust.  I haven't looked yet, but I have a hunch.

Ok, upon looking into this a bit more, it's actually quite painful to force that setup.py dependencies get installed before actually evaluating the rest of the setup script. I tried a combination of lazy imports and found out I really overestimated the setup_requires field...
Seems like pointing people towards pip is definitely an easier, more modern method. Implemented this in https://github.com/guidance-ai/guidance/pull/805


⚠ PrivateHD has degraded performance

In 41eb07d, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2362 ms

Resolved: PrivateHD performance has improved in 2b0c43c.


Document describing the affiliated package review process

Ready for initial review! (Template emails still need to be written, but the rest can be reviewed)
Preview here

@taldcroft - I've addressed your comments.

I made some tweaks to the language. I don't think it's anything substantive.

Thanks @kelle!

Had a quick look only - but was very happy with that (and hope that this will help clear the pipeline a bit - having a package waiting for review since April, I've got some personal stake there...)

This was approved by all coordinators and no objections from anyone on the list, so I'll go ahead and merge!


Unable to connect via TCP

Problem
Code in the sdk ignores the TCP support flag TXT record and always connects by UDP.
For instance:
https://github.com/project-chip/connectedhomeip/blob/a49c250c85b334f3f82239f4ca1d5d113373c0e8/src/controller/SetUpCodePairer.cpp#L190
https://github.com/project-chip/connectedhomeip/blob/a49c250c85b334f3f82239f4ca1d5d113373c0e8/src/controller/CHIPDeviceController.cpp#L563
I've tried to modify this and attempted to connect via TCP when this can be supported by both nodes, but this doesn't work.
Specifically, my modifications were:
diff --git a/src/controller/CHIPDeviceController.cpp b/src/controller/CHIPDeviceController.cpp
index 18642de99..9e3669830 100644
--- a/src/controller/CHIPDeviceController.cpp
+++ b/src/controller/CHIPDeviceController.cpp
@@ -566,8 +566,16 @@ Transport::PeerAddress DeviceController::ToPeerAddress(const chip::Dnssd::Resolv
     {
         interfaceId = nodeData.mInterfaceId;
     }
-
-    return Transport::PeerAddress::UDP(nodeData.mAddress[0], nodeData.mPort, interfaceId);
+    Transport::PeerAddress peerAddress;
+    if (nodeData.mSupportsTcp)
+    {
+        Transport::PeerAddress::TCP(nodeData.mAddress[0], nodeData.mPort, interfaceId);
+    }
+    else
+    {
+        Transport::PeerAddress::UDP(nodeData.mAddress[0], nodeData.mPort, interfaceId);
+    }
+    return peerAddress;
 }

 void DeviceController::OnNodeIdResolved(const chip::Dnssd::ResolvedNodeData & nodeData)
diff --git a/src/controller/SetUpCodePairer.cpp b/src/controller/SetUpCodePairer.cpp
index a53c4fdcb..3c32a0292 100644
--- a/src/controller/SetUpCodePairer.cpp
+++ b/src/controller/SetUpCodePairer.cpp
@@ -187,7 +187,15 @@ void SetUpCodePairer::NotifyCommissionableDeviceDiscovered(const Dnssd::Discover
     LogErrorOnFailure(StopConnectOverSoftAP());

     Inet::InterfaceId interfaceId = nodeData.ipAddress[0].IsIPv6LinkLocal() ? nodeData.interfaceId[0] : Inet::InterfaceId::Null();
-    Transport::PeerAddress peerAddress = Transport::PeerAddress::UDP(nodeData.ipAddress[0], nodeData.port, interfaceId);
+    Transport::PeerAddress peerAddress;
+    if (nodeData.supportsTcp)
+    {
+        peerAddress = Transport::PeerAddress::TCP(nodeData.ipAddress[0], nodeData.port, interfaceId);
+    }
+    else
+    {
+        peerAddress = Transport::PeerAddress::UDP(nodeData.ipAddress[0], nodeData.port, interfaceId);
+    }
     RendezvousParameters params        = RendezvousParameters().SetPeerAddress(peerAddress);
     OnDeviceDiscovered(params);
 }

This was at this rev:
commit d4d57f607f5cc67f349e8aa97a4443e5743595f7
Author: Michael Sandstedt<EMAIL_ADDRESS>Date:   Tue Jan 4 10:59:55 2022 -0600

    Fix ResolverProxy use-after-free in HandleNodeBrowse (#13291)

and with these node types:
commissioner: chip-tool on Darwin
commissionee: all-clusters-app/linux
Proposed Solution
Add missing TCP support to relevant platforms.

I believe TCP was considered optional in the SDK for v1.0, given UDP works with MRP. Tagging for post V1.0

This is a duplicate of https://github.com/project-chip/connectedhomeip/issues/23028


Release Camunda Modeler v3.3.0

What's inside

Improved participant navigation (https://github.com/camunda/camunda-modeler/issues/238)
Two-step copy and paste (https://github.com/camunda/camunda-modeler/issues/1421)

Tasks

[ ] put up code freeze appointment in calendar (include modeling, michael.schoettes, sre, and ilias.kourtoudis)
[ ] make sure dependencies are released (rm -rf node_modules && npm i && npm run all works)

bpmn-js, dmn-js, cmmn-js, *-properties-panel, *-moddle, ...

[ ] smoke test to verify all diagrams can be created
[x] update CHANGELOG before releasing (https://github.com/camunda/camunda-modeler/commit/4f216a855b1d6b95fd2aa1d277ef6ff1d396b9c4)
[ ] semantic release (npm run release), cf. release schema
[ ] wait for Travis to build the release
[ ] execute integration test on released artifacts

[ ] Works on Linux
[ ] Works on Mac
[ ] Works on Windows

[ ] trigger QA for fuzzy testing
[ ] publish release on Github Releases
[ ] write blog post on blog.camunda.org
[ ] trigger mirroring of release to https://camunda.org/release/camunda-modeler/ via Jenkins
[ ] update download version of Camunda Modeler at camunda.com
[ ] spread the word

[ ] send release notice email
[ ] tweet

[ ] close current milestone

Blocked by https://github.com/camunda/camunda-modeler/issues/1467

Waiting for https://github.com/bpmn-io/diagram-js/pull/403 to release the dependencies.

I'd like to see https://github.com/bpmn-io/diagram-js/pull/404 and https://github.com/camunda/camunda-modeler/pull/1475 merged before the release. @barmac  @nikku @pinussilvestrus What do you think?

Waiting for integration tests on Linux. @nikku Can you help out?

Yo.

Tested on Arch Linux, works as expected :muscle:.
Cut a v3.3.1 patch release to include latest fixes shipped with bpmn-js and diagram-js.


Create separate module to scrape Github

The mine-github module can be wrapped in its own PyPip package. This would make the code of iac-miner less verbose and more maintainable.

Solved with https://github.com/radon-h2020/radon-repositories-collector/commit/7fc139654ce1d269137b0476c9654f3e4331fc9e


Project view for multiplane-ophys

User story
Users want a "project view" page for multiplane-ophys that includes a table with metadata "data assets, columns would be things like asset ID, mouse ID, genotype, session type, acquisition date, processing date, pipeline version, etc."
Additional features might include links out or summary figures. Links could go to subject view and QC view as well.
Acceptance criteria

[ ] Project view for multiplane-ophys with specified tables, figures, links
[x] Address at qc.allenneuraldynamics.org/project_app?project=multiplane-ophys (or whatever the actual project name is in data_description)
[ ] Support file health checks in some way

Sprint Ready Checklist

[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
[ ] 6. Ticket is prioritized and sized

asset ID: s3 link?
mouse ID: subject.subject_id
genotype: subject.genotype
session type: session.session_type
acquisition date: session.session_start_time
processing date: processing.processing_pipeline.data_processes[0].start_date_time
pipeline version: processing.processing_pipeline.pipeline_version

Just realized this isn't the actual project name


Adds new statistics attributes for reaped connections

The two new statistics, connections_closed_max_lifetime and connections_closed_idle_timeout the total number of connections that were reaped due to reching the max lifetime or the idle timeout.

Thanks!


[Feat] Improve documentation for development purposes

Target Use Case
I am using @vis.gl/react-google-maps in a development environment to build and test features that require Google Maps integration. While the library works well, I believe the documentation could be improved to better support developers who are using it for development purposes. Specifically, more detailed guidance on setting up and configuring the library in a local development environment would be highly beneficial.
Improving the documentation for development purposes would help not only me but also other developers who are integrating Google Maps into their React projects. Clear and comprehensive documentation would reduce setup time, lower the learning curve, and prevent common issues that developers might face during the development phase.
Proposal
To enhance the documentation, I propose the following improvements:

Development Environment Configuration: Update the Getting Started guide to include a note that developers can set the apiKey to an empty string ("") during development to bypass the need for a specific API key. This allows for easier setup and testing without the concern of exceeding API key quotas.
Example:

GOOGLE_MAPS_API_KEY=""

import React from 'react';
import {createRoot} from 'react-dom/client';
import {APIProvider, Map} from<EMAIL_ADDRESS>
const App = () => (
  <APIProvider apiKey="">
    <Map
      style={{width: '100vw', height: '100vh'}}
      defaultCenter={{lat: 22.54992, lng: 0}}
      defaultZoom={3}
      gestureHandling={'greedy'}
      disableDefaultUI={true}
    />
  </APIProvider>
);

const root = createRoot(document.querySelector('#app'));
root.render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

Additional Troubleshooting Tips: Provide guidance on when it's appropriate to use an empty string for the API key and the limitations or caveats of doing so.

Example Projects: Consider including or linking to an example project in the documentation that uses an empty API key for development purposes. This project could serve as a quick-start template for new developers.
These improvements would streamline the setup process, making it easier for developers to start working with @vis.gl/react-google-maps in a development environment.

I appreciate the thoughts and the time you invested!
The documentation is certainly still in need of some more refinement and you point out an important topic we can do better at. We should definitely add some information on the topic of API keys, how to configure and use them and so on. While everything in that regard is covered in the official documentation by Google, I feel we could also have a condensed version of that in the getting started guide.
What I am a bit uneasy about is omitting the API key, since that is a violation of the Google Maps Platform ToS (Section 1.2), and we can't tell people to do that.
If your concern is about racking up costs for a map in your application while you are working on something different on the same page, you could also implement a placeholder that delays creating the map-instance until it's actually needed (or just in the dev environment or something like that). These are absolutely points we should mention in our documentation, add an example and so on.


Draft: Add CI for s390x and fix big-endian arch

Fix for 32bits words on big-endian arch.
Fixes #97

We need to fix the following files as well for the same issue:
* unicode-data-scripts/test/Unicode/Char/General/ScriptsSpec.hs

* unicode-data-scripts/lib/Unicode/Char/General/Scripts.hs

These are already fixed.

We may have problems in future if we forget to include MachDeps.h , this is a nasty thing that is not caught by any tool and can be easily missed. We can do two things to mitigate this:
* define a CPP macro for reading Word32 with endianness handling and then use that macro everywhere. That way we need to include MachDeps only in the file defining that macro. Both byteswap and narrowing can be included in that macro so we do not miss it anywhere.

* Add a CI for s390x. We can copy it from unicode-transforms repo.

I think the latter is better. I am giving a try.

@harendra-kumar there is an issue with the CI for GHC 8.0.2 and 8.2.2. It seems they are not supported anymore.

We need to fix the following files as well for the same issue:
* unicode-data-scripts/test/Unicode/Char/General/ScriptsSpec.hs

* unicode-data-scripts/lib/Unicode/Char/General/Scripts.hs

These are already fixed.

It see this in unicode-data-scripts/lib/Unicode/Char/General/Scripts.hs:
#ifdef WORDS_BIGENDIAN
#if MIN_VERSION_base(4,16,0)
            byteSwap32# (word32ToWord# (indexWord32OffAddr# addr# k#));
#else
            byteSwap32# (indexWord32OffAddr# addr# k#);
#endif

Don't we need a call to narrowWord here?

@harendra-kumar there is an issue with the CI for GHC 8.0.2 and 8.2.2. It seems they are not supported anymore.

The installation seems to be failing, not sure what's wrong. We can investigate if someone asks for it, otherwise let's ignore it for now.

After the experiment in #99, I think this is ready to merge if the relevant tests pass (let’s discard GHC ≤ 8.2). Keep in mind that we can fully test only against GHC 9.6. And GHC support for Unicode < 12.1 is not reliable, because there are some discrepancies (I checked manually some errors).

It seems you missed this https://github.com/composewell/unicode-data/pull/98#issuecomment-1336451077 . Can you please respond to this.

It seems you missed this #98 (comment) . Can you please respond to this.

I think I did. Are you using the latest version?

I think I did fix it. Are you using the latest version?

Looks like I missed it, maybe I did not pull it again or ignored the pull error.


Evaluator: Pass the current time to the policy rules script

Policy rules may require the current date and time as input, such as
e.g. checks for copyright year ranges. Constructor inject the date and
time into the script to avoid a direct dependency on the system time in
order not to sacrifice testability.

Constructor inject the date and time into the script to avoid a direct dependency on the system time in order not to sacrifice testability.

That's the rationale why you're not simply calling Instant.now() in the script itself, correct?

That's the rationale why you're not simply calling Instant.now() in the script itself, correct?

Yes.


Enter in someone's account after registration via social network

In yii forum I read next bug:
http://yiiframework.ru/forum/viewtopic.php?f=9&t=16660&p=152240#p152240

After registering via the social network (google), I was redirected to the link type http://yii2-user.dmeroff.ru/user/registration/connect?account_id=xxx in order to specify email.
If you manually change the ID to the address sooner or later get on someone's account, who do not have email. Pointing out some garbage - and I'm inside.

This has been fixed in master branch.


Typo in a script

There is a minor typo in one of the scripts:
https://play.onflow.org/5b5bd86b-3845-4c16-9a29-626ef6228846 for the script1
// Scripts must have the following signature: pub fun main()import HelloWorld from 0x02

Issue moved to onflow/flow-playground-tutorials #4 via ZenHub


[Question] Is there possibility to render values files?

Hi!
We use values files that are heavily use requiredEnv function.
Something like this:
gcp:
  enabled: false
  bucket: minio-backups-{{ requiredEnv "CUSTOMER" }}-{{ requiredEnv "SHARED_NAMESPACE" }}

After deploy we would like to have such values rendered, so after some time if we like to know what env was used for deploy we can just check the file.
I know that helmfile have "build" command but it render values into one big file, and than sort all top level keys in alphabetic order. Its little bit hard to search for needed key if you use many values files. For example I want to check all the keys from one file, than I need to take keys one by one and search them in this one big rendered file.
Is there possibility to render values files separately as they are presented on filesystem/values block?
As example, if I have next files:
    values:
      - ../environments/gke-dev/common.yaml.gotmpl
      - ../environments/gke-dev/backup.yaml.gotmpl
      - ../environments/gke-dev/shared-users.yaml.gotmpl
      - ../environments/gke-dev/shared-roles.yaml.gotmpl
      - ../environments/gke-dev/shared-resources.yaml.gotmpl
      - ../environments/gke-dev/shared-hosts.yaml.gotmpl
      - ../environments/gke-dev/shared-secrets.yaml.gotmpl
      - ../environments/gke-dev/shared-certs.yaml.gotmpl

And after apply/template I want to have them rendered in some folder like this(each one separate as the original):
./rendered_files
common.yaml.gotmpl.rendered
backup.yaml.gotmpll.rendered
shared-users.yaml.gotmpll.rendered
shared-roles.yaml.gotmpll.rendered
shared-resources.yaml.gotmpll.rendered
shared-hosts.yaml.gotmpll.rendered
shared-secrets.yaml.gotmpll.rendered
shared-certs.yaml.gotmpll.rendered

Maybe this future exist but I cant find it.

see: https://github.com/roboll/helmfile/issues/2148

Move to new repo


Add VersionName & VersionCode blocks

I have added two blocks to return the VersionName and the VersionCode of users' app.

@conorshipp could you explain when you'd want to use these two methods?
There are cleaner ways of writing the code also. You could define
String vname = "";

at the top of the method and then return it after the try_catch instead of having two returns.
The catch clauses (error handling) could do with a bit of thinking too.

I believe (not certain) that if you change Form you have to update a few more things (such as YaVersion and upgrade code).

could you explain when you'd want to use these two methods?

If, for example, a user creates an app with a settings screen, they might want to show the version name at the bottom of the screen, similar to Google's apps.

such as YaVersion and upgrade code
I'm still learning an don't really understand this.

This section of the docs may be helpful.


unit test with pytest added

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@faab381). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master     #1   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      4
  Lines             ?    128
  Branches          ?      0
=======================================
  Hits              ?    128
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

openid_wargaming/authentication.py
100% <ø> (ø)

openid_wargaming/verification.py
100% <100%> (ø)

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 faab381...0adbb1f. Read the comment docs.


Tests broken on master?

The tests from #8 failed in the same way as those from the unrelated #6. Furthermore, I get the exact same failures locally, even with master checked out. As far as I can see, the last travis ci pipeline on master ran 8 months ago. @jmagnusson can you please trigger a pipeline on master to see if it still passes?

@dimrozakis build retriggered - master is also failing.
Please see #10

see https://github.com/jmagnusson/sentry-dramatiq/issues/12


TAJO-1981: Invalid nulls sort order in VectorizedSorter

I'm sorry for a large patch. Here are the highlights of this patch.

Fix the problem of invalid sort order of nulls in VectorizedSorter
Change the name of nullFirst variable to nullsFirst
Change the string representation of SortSpec to print out the nulls order

Most changes of this patch is due to the changed string representation of SortSpec, and there are only very minor changes.
Please review this patch.

+1 LGTM!!


Update README.md

There is a generator provided by the library but it's missing from the documentation. I have added the installation generator to the readme file.

I wonder if are also using Solid Queue in the tests and how do it if that is the case, since I see that the generator also sets it up in the test environment. I would think that would be used ActiveJob::QueueAdapters::TestAdapter

Hey @jmarsh24, thanks for this! I'm not quite sure about the generator, in fact 😅 As @brunoprietog said, it's added to the test environment but we don't have yet a good way to start it and configure it for testing (even though it can be used for testing via an inline mode, but this is not quite fleshed out). I had wanted to keep the generator out of the first open-source release but I forgot to delete it. I'll do that instead.


Update fr-FR.json

some small changes

Pull Request Test Coverage Report for Build 754

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

Totals

Change from base Build 753:
0.0%

Covered Lines:
1253

Relevant Lines:
3643

💛  - Coveralls


how to config the root url?

I  install a nginx to load balance static resouce  with port  8080.
and the  above domain redirect my nginx  .
so when i open  http://aaa.hue.com   .   some times it redirect to http://aaa.hue.com:8080 .
how to  avoid this

e.g. http://gethue.com/i-put-a-proxy-on-hue/


Stagger start RKE2 server nodes

To avoid any race conditions and a lot of error logs of servers that can't start until the first server is healthy and learner promotions are completed we should block starting/restarting servers until they are showing Ready state.
A possible solution is polling something like this on the host in question until True is observed.
/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml \
--server https://<IP_ADDRESS>:6443 get no {{ inventory_hostname }} \
-o jsonpath='{.status.conditions[?(@.type=="Ready")].status}'

Hi,
I think there is another possible solution. An another point of view.
If I understand correctly, the idea is wait until the kubeapi is up and running ?
There is a more "ansible" approach I think with the module: ansible.builtin.wait_for
You can add :
- name: Wait for k8s apiserver
  wait_for:
    host: "{{ kubernetes_api_server_host }}"
    port: "6443"
    state: present
    timeout: 300

This is what kubespray seems to do that here:
https://github.com/kubernetes-sigs/kubespray/blob/33a60fe919b50a149ef6402f56e342989f6eea23/roles/kubernetes/client/tasks/main.yml#L44

This seems related to https://github.com/rancherfederal/rke2-ansible/issues/38.
I moved past this frustrating issue using @AYDEV-FR 's solution at the bottom of the rke2_server > first_server.yaml task, along with adding serial: 1 to the site.yml rke2_servers playbook. Thanks for that.
However, I think a watch script that isn't tied to a play might have more flexibility for re-use.

should be addressed in #54

@mddamato Yes, the introduction of the throttle directive here solved the problems we had with the 3rd server hanging on startup in a 3-server cluster deployment. Thanks.

You might wait until the necessary commit hits main before closing this issue.

I'm having the same issue right now. Why is this issue closed?
TASK [rke2_server : Start rke2-server] ***************************************** ok: [rkectlplane01] Wednesday 28 September 2022  00:46:09 +0000 (0:00:01.183)       0:00:36.379 ***  TASK [rke2_server : Wait for k8s apiserver] ************************************ fatal: [rkectlplane01]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for rkectlplane01:6443"} NO MORE HOSTS LEFT *************************************************************

@siulcode The error you posted shows that the server isn't starting properly but it's not enough information for me to go off of. Could you post the errors from the rke2 server logs or other applicable components?


incorrect DOM for  inside

program
use 5.012;
use Mojo::DOM;
my $dom1 = Mojo::DOM->new(join('', <DATA>));
my @d=@{ $dom1->find('div > p') };
say "found: ",scalar(@d);
my @pp=@{ $dom1->find('p > p') };
say "found: ",scalar(@pp);

__DATA__

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

test

prints 2 and 0. It should be 1 and 1.

The behaviour is correct.
Per the spec,
 elements cannot contain block-level elements, so your HTML code really ends up as

test
, thus giving the results you're seeing.

Thanks @zoffixznet.


UUID for MacOS-13 is randomly generated vs being preset on MacOS-12

Description
Using Azure pipeline, xcode provisioning profile requires some unique device Identifier included for the device used for testing. Thus, adding a specific demand with agent.Name while using macOS-12 works every time the pipeline runs by picking the same UDID. Having the same demands clause on macOs-13 would pick a random UDID for the selected agent. For example running the following pipeline which has demands clause
pool:
  name: 'Azure Pipelines'
  vmImage: macOS-12
  demands:
  - Agent.Name -equals Azure Pipelines 16

Would pick the same UDID:
"platform_UUID" : "4203018E-580F-C1B5-9525-B745CECA79EB",
"provisioning_UDID" : "4203018E-580F-C1B5-9525-B745CECA79EB"

However, when switching to MacOS-13 image. the same command causes a random UDID every time it is called.
Just wondering if there is any way to request the same UDID by selecting a different demand or requiring an image with a specific UDID?
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Current agent version: '3.220.0'
Is it regression?
MacOS-13
Expected behavior
To pick the same UDID every time the agent is selected
Actual behavior
New UDID is randomly generated
Repro steps
Description to reproduce the issue:
Run a pipeline with
pool:
  name: 'Azure Pipelines'
  vmImage: macOS-12
  demands:
  - Agent.Name -equals Azure Pipelines 16
- task: Bash@3
  displayName: Machine UDID
  inputs:
    targetType: 'inline'
    script: 'system_profiler SPHardwareDataType -json'

You get the same UDID
run the same with macOS-13. A new UDID is generated.

Hello @antonioalwan,
Case of different UDID values between macos-11/12 and macos13 is an architectural characteristic which is unlikely to change. I will close the issue for now, please feel free to reopen it if any additional concerns.

Hi @shamil-mubarakshin,
Can you please help me understand the architectural characteristic differences between macOS-12 -> 13 that prevents having a unique UDID?
For the context, Apple provisioning profile requires registration of multiple devices for running tests for our signed app. Our tests require keychain access. Without the ability to have affinity between agent.Name to UDID, then I don't think we'd be able to move forward utilizing macOS-13.
In fact, A similar issue was made for previous macOS versions before and was fixed. The issue is exactly the same what we're facing today while switching to macOS-13.
Really appreciate if we can have a solution here or understand what other developers are doing for such scenario?

@antonioalwan, thank you for providing additional information.
Architectural difference between macos-12 and 13 is moving from VmWare VSphere to Anka virtualization. https://github.com/actions/runner-images/issues/835#issuecomment-627896929 was more of a guidance, rather than a fix.
I will get in touch with infra team to address your concerns regarding UUIDs and get back with hopefully more info

@antonioalwan, after getting in touch with infra team, new virtualization has no such support yet.
While we understand your concerns, UUIDs staying same wasn't something guaranteed.
I will close this issue for now


arch/arm: Fix zero interrupt latency priority level

The zero interrupt priority is configured incorrectly and is blocked by irq_lock.
Setting it to the last of the reserved interrupt levels
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

Codecov Report

Merging #7747 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7747   +/-   ##
=======================================
  Coverage   55.01%   55.01%
=======================================
  Files         483      483
  Lines       53952    53952
  Branches    10495    10495
=======================================
  Hits        29682    29682
  Misses      19984    19984
  Partials     4286     4286

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 b1e06f2...d5f7884. Read the comment docs.

Also, use standard format for commit message, i.e. "arch: arm: ....."

OK, I did some more investigation and I think that thanks to @joerchan we might have spotted a critical bug here:
According to my understanding:
In ARMv7-M, ARMv8-M Mainline MCUs, Prio-0 is reserved for fault-priorities, and Prio-1 is reserved for Zero-latency IRQs (if configured so).
So then

all inline-comment text is wrong and confusing, and
irq_lock() definitely masks-out the zero-latency IRQs.

Looks good, now. @galak , could you take another look?

@galak Updated with your suggestion.

@joerchan can you please create an issue specific to this and add a "Fixes #" comment to this PR description?

Fixes #8073

@joerchan thanks!

Fixes #8073

Can you add in the commit message:
Fixes: #8073


Sort the imports and merge them

This PR sorts the imports by cargo fmt and merges them.
Also, I removed some places that were using core and replaced them with ark_std. Please check if it is correct.
By the way, there is pub(crate) use ark_std::vec::Vec in lib.rs. I don't understand why we still have to import it when it is no-std? @mmagician

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (main)
[ ] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Done! @Pratyush


#35638 Turn off by default Show values setting in autocompletion

Turn off by default the Show values setting, which turns on the proposals that require SELECT DISTINCT queries

Verified


Add a GitCommitDate property to ThisAssembly

Adds a ThisAssembly.GitCommitDate property, which contains the Git commit date from HEAD.

@AArnott So, I updated the PR to make sure the date is typed as a DateTimeOffset in the VersionOracle class, and a string representation of a long (the number of ticks since 1/1/0001) in the MSBuild tasks.
The AssemblyInfo file itself would need to invoke the constructor of DateTimeOffset with a const, something the code generators can't express yet.
I'll try to work on that in the coming days.

@AArnott OK - I converted the GitCommitDate to a read-only property of type DateTimeOffset. Can you have a look at the diff and let me know if you like the direction this is going?
Couple of questions:

It looks like the .NET code generators are used when building on .NET Framework and custom code generators when building on .NET Core. I'm not sure the .NET Framework code is being tested in CI. Is there a reason to keep both branches, or would it be OK to enable the .NET Core code path on .NET Framework as well?
I'm not sure the F# code generator is being tested. I don't know much about F#, is there a way to add F# equivalent of BuildIntegrationTests.AssemblyInfo?

We use CodeDom on .NET Framework to support as many languages as we can so long as a CodeDOM provider exists for it.
On .NET Core where those don't exist, we have to fallback to manual generators.
Due to the perf cost of CodeDOM, I actually think we recently switched to prefer the manual generators if we have them, and only fallback to CodeDOM on .NET Framework if we don't have a manual one. Is that not what's happening here?

I've updated the CodeDOM path, so hopefully we're good there.
PS - the Execute method on NET461 seems to always use CodeDOM (or error out in line 114 if CodeDOM doesn't support the current language)


Feature request: explicit React typings

I think that explicit addition of signals typings (like in ts-reset ) will have better DX.
For now typings not working for react. I can add this

All dom attributes can be preact signals, but by typings not.

I think i can fix it by redeclaring React interfaces

But it still will fall typechecks in html attributes and so on

I know how to solve it


Sweep2wake missings controls

Hello Yoinx. I have seen that missing controls in sweep2wake feature. Here I show you Flar2 xda post:

Sweep2wake

Sweep2wake allows you to turn on your phone by swiping your finger across the screen. There are four sweep actions that will work
Gesture........Value
Sweep right......1
Sweep left........2
Sweep up.........4
Sweep down....8
Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)
/sys/android_touch/sweep2wake

I had broken this before because Grarak didn't allow for the correct choices. (see the removal commit here: https://github.com/yoinx/kernel_adiutor/commit/d6cb731a891958e4d37246df540bf185384486f8)
This will allow for all of the options correctly: https://github.com/yoinx/kernel_adiutor/commit/bbb9deea14b2f7414d5ae6298830cc52ca19e56a
If you're not building for yourself, it'll be in my next build (should be in the next few days)

Ok, very thanks Yoinx. :)


Parse Migration: The job failed too many times and reached the max retry limit.

This was described as potentially a hardware issue by the Parse Migration guide: http://www.parse.com/migration
My collections aren't massive by any means (1,000-5,000 objects per class with about 10 classes). I'm using DocumentDB and Microsoft Azure on F1 (Free, 1GB). My data and storage usage hover at around 0.2 GB on Parse. Should I upgrade to a higher pricing tier? Would this fix the problem?

Hi @santafebound,
Thanks for reaching out.  This is a known issue with some migrations, a fix is expected to be deployed tomorrow EOD.  If the migration still fails at that point you should follow up.

@mamaso I'm having the same issue. Using mLab dedicated server with 40GB (migrating 3 GB).

Hi @sidan5 If you are using the mLab dedicated server for your MongoDB service, then you are not having the same issue.  This is explicitly for using DocumentDB as the MongoDB service.

Hi @santafebound the problem is that the free documentDB tier only allows 10 standard collections. So, the parse migration tool tries to add a new collection but it is not possible. You can verify this, by adding manually (within the azure portal) a collection - it will not work.

@adrianhall how can I tell my managed Parse to use a MongoDB from mLab? Is it enough to specify the connection string in the Application Settings (as the value for the Key DATABASE_URI)?

Yes, you can change the DATABASE_URI appsetting to whichever mongo provider you prefer.

Anyone find a solution to this?

@liambolling the problem for the original issue was the limited free documentDB tier (only 10 collections allowed). Just switch to a other tier or a hosted mongo-db for e.g. mlab.


Missed directories by ffuf but found by dirb (same wordlist of course)

Hi, i use ffuf since a long time but today when dealing with a CTF challenge i saw ffuf missed a directory when dirb found it.
ffuf -c -u http://challenge01.root-me.org/web-serveur/ch06/phpbb/FUZZ/ -w /usr/share/dirb/wordlists/common.txt
the install dir isnt found by ffuf but found by dirb

Just to let you know since that's weird

Hmm, that's weird. I tried to log in to the service and tested it out. I cannot reproduce this (ffuf consistently does find it for me).
The service does however enable access based on the source IP address when logging in and starting the challenge. I wonder if there was something wrong in that process when you ran the ffuf test.
I'm wondering this as in your screenshot you seem to have filtered out 403 responses, and the server definitely answers with 403 to everything if the ip based access is not enabled, while when it is, the typical answer for non-hits are just normal 404's.

I'm closing this issue now as there's no action points based on it. Feel free to comment in case I missed something here.


[*] Schema Versioning - .forestadmin-schema.json file is not versioned

The community reported that the schema is not versioned in this project.

On a side note, it could be great to have a fixed version of forest-express-... package in the package.json to prevent breaking change to happen to developers who want to test this project.

Hey,
Will the schema be versioned anytime?
Thanks


Testing dbus services / clients

I am probably missing something important but I can't seem to test dbus services and/or clients:
GLib.Error g-spawn-exit-error-quark: Error spawning command line “dbus-launch --autolaunch=180049aac266486c89ec8c79e659685e --binary-syntax --close-stderr”: Child process exited with code 1 thrown in resource:///org/gnome/gjs/modules/core/overrides/Gio.js (line 457)
    get session@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:457:24

It seems that is not possible to spawn/launch services from within flatpak-builder. I tried to reproduce the dbus-launch command and got this:
[📦 org.gnome.Sdk project]# dbus-launch --autolaunch=180049aac266486c89ec8c79e659685e --
Autolaunch requested, but X11 support not compiled in.
Cannot continue.

I also tried adding more permissions to test-args (e.g. --socket=session-bus, --filesystem=host, etc) , but didn't make any difference.
Any ideas?

It's even possible to launch a dbus session inside a Docker container? :thinking:

It should be possible if we run dbus-run-session before running the build, as we can't influence the test stage (it's run by flatpak). See https://gitlab.gnome.org/GNOME/citemplates/-/blob/master/flatpak/flatpak_ci_initiative.yml#L23-25 for the stuff we are currently missing.

I've started taking a crack at this one, since it would be cool to be able to run D-Bus tests. I've really just prepended  dbus-run-session to the command-line here, but without much luck. If anyone has any tips about how these pieces fit together I'd be happy to hear them :)
I've been able to confirm dbus-run-session is the parent process, as the error(s) now read...
Build failed: Error: The process '/usr/bin/dbus-run-session' failed with exit code 1

instead of...
Build failed: Error: The process '/usr/bin/xvfb-run' failed with exit code 1

As an interesting side-note, some of my D-Bus tests are wrapped in a python-dbusmock script and those work fine. That may be a usable workaround for the time being, but I'll be avoiding it personally.


refactor: move "dcore" binary target to a separate directory

Just to not complicate dependencies within deno_core library.
This crate is not publishable and is meant only for development
and testing.

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

Project coverage is 80.64%. Comparing base (acf6f62) to head (8999d88).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #630      +/-   ##
==========================================
- Coverage   80.65%   80.64%   -0.01%
==========================================
  Files          97       97
  Lines       23702    23702
==========================================
- Hits        19116    19114       -2
- Misses       4586     4588       +2

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


AG-Grid should be able to interract with fusion compact mode

Is your feature request related to a problem? Please describe.
Compact mode has no effect on ag-grid.
Describe the solution you'd like
I would like the option to have ag-grid toggle density based on Fusion compact mode. Not sure the event from the compact mode toggle is exposed to us anymore (?)
Describe alternatives you've considered
Making our own implementation of compact mode and therefore bypassing the issue (but not working with the fusion compact mode)

For now we don`t have a port for the "userconfig" from the previous FusionAPI, but there is a issue for persisting state in the framework, once that is complete, we can implement a user settings moudle
for now, this code will du what the previous hook did:
const settings = window['74b1613f-f22a-451b-a5c3-1c9391e91e68'].settings;
cosnt useCoreSetting = () => {
  const [state, setState] = useState(settings.core.toObject())
  useEffect(() => settings.core.on('change', setCoreSettings), [setCoreSettings]);
  return state;
}

const {displayType} = useCoreSetting();
if(displaytype === 'Compact'){
  ....
}

we will keep you updated, thanks for the suggestion

should be done in https://github.com/equinor/fusion-framework/issues/1258


Cleaned code and switched to .NET Framework 4.8

Cleaned some code, changed the .NET Framework version from 4.0 to 4.8 (through Visual Studio).
PS: Directory.Create() only creates a folder if it doesn't already exist. If statements with Directory.Exist are therefore not necessary if a folder is to be created if it does not already exist. I did not find tests for Electron.NET. Please verify that it works with .NET Framework 4.8 as well.

I merged a big PR from @theolivenbaum - please compare with the new source on our repo.


Change to correct thirdweb documentation link

The previous hyperlink point to the youtube channel which is incorrect

Hi @emilyJLin95, kindly review this PR, thanks :)


Programming languages - "Racket" Complete Resources

Pull Request
Description
@jfmartinz I have added the complete resources for Racket programming language please review and merge this pull request
Closes #1155
Type of change

[x] Adding a new Resource
[ ] Adding a new Category
[ ] Documentation enhancement or fixes
[ ] Website enhancement or fixes

Checklist:

[x] I read carefully CONTRIBUTING.md
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

@jfmartinz i made the changes requested please review and merge this pull request

You forgot Module Libraries. Make it h3

@jfmartinz done

@jfmartinz please add the level label


Renamed ioBroker.lgtv2011 to ioBroker.lgtv11

I had to rename ioBroker.lgtv2011 to ioBroker.lgtv11 because of npm package naming restrictions.


model.replace add @$el = @el

after call Model.replace(), @$el is not updated. This pull reques fix it.

in the controller constructor @$el is defined
@el  = document.createElement(@tag) unless @el
@el  = $(@el)
@$el = @el

The bug is weird in that I would expect it should be just a reference to @el and I would expect @$el to work just fine, but what is also odd is that it is never used elsewhere in the source. I am tempted to think @$el is just something that we should get rid of. Why are you using @$el instead of @el?

I just think, $el hint that $el is a jquery object

My leaning is to remove @$el unless anyone is strongly opposed for some reason. I just don't see it as useful and don't suspect it is widely used since it isn't wel documented or anyhting. Instead of adding code to fix the bug feels better to remove the source of the problem. I can create an entry in the notes for 1.4 release that this reference is deprecated.

It's also Good idea.


I want to know how can I increase the session timeout.

Right now the tunnel session ends in approx half hour, is there any way to increase it to 24hrs?

The timeout was probably due to the Nginx configuration.
Updated them to timeout in 1 day.
http {
        proxy_read_timeout 1d;
        proxy_connect_timeout 1d;
        proxy_send_timeout 1d;
        send_timeout 1d;
        ...
}

Please check now.


Identify expense type on submission

We need to differentiate between receipt reimbursement expenses and invoice expenses.
Add a required dropdown box on the new expense form next to 'category':
Expense Type

Reimbursement
Invoice

Add a ? help icon, and on hover show:

Select 'reimbursement' if you are asking to get paid back for a purchase you already made, and upload the corresponding receipt. Select 'invoice' if you are charging for your time, getting paid in advance, or do not have a receipt, and upload a corresponding invoice document.

FYI @pietgeursen and I decided this can just apply to expenses going forward, and for past expenses we'll have a third state ('undefined' or 'uncategorised'). The tax threshold measurement will take into account both 'invoice' and 'uncategroised' expenses.

If that text is too much for a hover, feel free to put it on the form page itself.

I just made it a bit shorter too.

This has already been implemented, but the help text part is missing. Should I raise a seperate issue for that? I do think it's needed because many people don't understand the difference, plus the words can be ambiguous across languages.

Closing this as the main feature has been deployed. Opened #2385 to address small improvements.


[fltk] build failure

Host Environment

OS: High Sierra 10.13.6 mac
Compiler:

To Reproduce
Steps to reproduce the behavior:
./vcpkg install fltk
Failure logs
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
Command failed: /usr/local/Cellar/cmake/3.20.5/bin/cmake --build . --config Debug --target install -- -v -j5
Working Directory: /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fltk/x64-osx-dbg
See logs for more information:
/usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fltk/install-x64-osx-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:104 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:44 (vcpkg_build_cmake)
ports/fltk/portfile.cmake:42 (vcpkg_install_cmake)
scripts/ports.cmake:142 (include)
Error: Building package fltk:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with ./vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: fltk:x64-osx
Vcpkg version: 2021-05-05-unknownhash
Additionally, attach any relevant sections from the log files above.
install-x64-osx-dbg-out.log
Additional context
fresh install of homebrew and vcpkg.

There are a couple of possibly related issues https://github.com/microsoft/vcpkg/issues/8627 https://github.com/microsoft/vcpkg/pull/11205 https://github.com/microsoft/vcpkg/issues/9321

One suggested solution is the usage of ninja 1.9 - how would I use that ?
Currently vcpkg is using an external ninja version - possibly from XCode.
-- Found external ninja('1.10.2').

Hi @zcream
Thanks for posting this issue.
/usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fltk/src/fltk-1-7591e64af8.clean/src/Fl_cocoa.mm:716:3: error: cannot find protocol declaration for 'CALayerDelegate'; did you mean 'NSDrawerDelegate'?
< CALayerDelegate >
  ^~~~~~~~~~~~~~~
  NSDrawerDelegate

/usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fltk/src/fltk-1-7591e64af8.clean/src/Fl_cocoa.mm:4879:30: error: use of undeclared identifier 'version'; did you mean 'Fl::version'?
    NSOperatingSystemVersion version = [[NSProcessInfo processInfo] operatingSystemVersion];
                             ^~~~~~~
                             Fl::version

Seems there is no CALayerDelegate found on your machine. CALayerDelegate is available on these
Availability

iOS 10.0+
macOS 10.12+
Mac Catalyst 13.0+
tvOS 10.0+

Please see https://developer.apple.com/documentation/quartzcore/calayerdelegate

I updated to Catalina 10.15 due to the warning of an older OS. I still get a build error - though for something different.
-- Generating configure for x64-osx
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:105 (message):
    Command failed: /usr/local/bin/autoreconf -vfi
    Working Directory: /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fontconfig/src/75c13b2421-12bdc6f9c0.clean/
    Error code: 2
    See logs for more information:
      /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fontconfig/autoconf-x64-osx-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:600 (vcpkg_execute_required_process)
  ports/fontconfig/portfile.cmake:26 (vcpkg_configure_make)
  scripts/ports.cmake:142 (include)

Error: Building package fontconfig:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: fontconfig:x64-osx
  Vcpkg version: 2021-05-05-unknownhash

Additionally, attach any relevant sections from the log files above.

Could you please provide the error log from /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/fontconfig/autoconf-x64-osx-err.log?

Hi. I gave up on Vcpkg in macOS and just used home-brew. Thanks.


Synthesis HD images

Hi,
I try to synthesis HD images (1024*1024) with your Deep Corr code but it is really slow. Moreover it seems that my GPU is not really used by MatConvNet during the iterations.
Do you know if I have to add some specific option to use the GPU or how I can speed up the algorithm ?

Yes, I already have compiled MatConvNet Mex files for GPU before writing the first message.
I think you are totally right, most of the time is spent on the LBFGS-B (not on GPU).
I didn't know that LBFGSB could be implemented to run faster on GPU. Do you know where I can find such package please ? I didn't find it on Mathworks.com.
Thanks.

I was looking into this in the past but never completed an integration:
https://github.com/nepluno/lbfgsb-gpu
On Wed, Aug 15, 2018, 17:00 Gonthier Nicolas<EMAIL_ADDRESS>wrote:

Yes, I already have compiled MatConvNet Mex files for GPU before writing
the first message.
I think you are totally right, most of the time is spent on the LBFGS-B
(not on GPU).
I didn't know that LBFGSB could be implemented to run faster on GPU. Do
you know where I can find such package please ? I didn't find it on
Mathworks.com.
Thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/omrysendik/DCor/issues/4#issuecomment-413206421, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMyWM6BY5iLA9-cZZwoLgblpsqirXWg5ks5uRCmJgaJpZM4V93x_
.

I will see if I can integrate it. Thanks.

Hi again,
It seems that the code don't use the GPU just by compiling the Mex files with the GPU option.
Moreover when I profile the code, LBFGS is not the bottleneck at all, it seems to be the correlation function.
I try to add some gpuArray in the code and to move the net from the CPU to the GPU but I got a lot of  different error most of the time, it seems to be due to the lack of memory on the GPU card.
Do you already have a version of the code using gpuArray ? Do you know how I could speed up the code ?
Best,


Auto-update image

I did some research, and it seems that the kamino tool previously used to smoketest VMSS image updates no longer works (AKS has bootstrapping implementation has changed under the hood, it seems).
FYI @clarkezone @trstringer @robmaynardjr


User Aptitude's Data

The user aptitude currently only gives us the email of the user. Can we request to include the full name and organization?

Hi, please include the Product Manager (Daren Barker) on how we can escalate this as an enhancement for Helps - this should be globally useful for all Loops and is critical for our endpoint to understand utilization data. Thank you!  -  Daren

@dannyAtOlive Thanks for your feedback! I'd like to create a ticket to better address that. May I know what is your name? I want to schedule a quick meeting with @fighthefire  regarding that request. Thanks!

Danny Betancourt (Developer) and Daren Barker (Product Manager)
Sent from my iPhone

On Dec 7, 2021, at 4:22 PM, Maggie Ma @.***> wrote:

@dannyAtOlive Thanks for your feedback! I'd like to create a ticket to better address that. May I know what is your name? I want to schedule a quick meeting with @fighthefire regarding that request. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Thanks for the info! I have create HELPS-2549 to address that! I'll DM you guys if we need to set up a meeting! Thanks!

Thanks for your suggestion! This feature has been released in Olive Helps v0.32.0 :)


UNA 11.0.1 Database Error occurs after upgrade to 11.0.1

Dear UNA Team,
I get this message daily after my system autoupgraded to 11.0.1.
I will be very grateful for your help
All the best
Finn Majlergaard
Database error in Educated Singles Club - For Elite Academic Singles Exclusively
Query:
SELECT sys_profiles.* FROM sys_profiles INNER JOIN sys_acl_levels_members AS tlm ON sys_profiles.id=tlm.IDMember WHERE 1 AND tlm.IDLevel IN (7,8) AND (tlm.DateStarts IS NULL OR tlm.DateStarts <= NOW()) AND (tlm.DateExpires IS NULL OR tlm.DateExpires > NOW()) AND sys_accounts.email_confirmed != 0
Mysql error:
Unknown column 'sys_accounts.email_confirmed' in 'where clause'
Location:
The error was found in getAll function in the file /home/educated/public_html/inc/classes/BxDolAclQuery.php at line 444.

Thank you for the report, this error has been fixed in 11.0.2
https://github.com/unaio/una/issues/2770

@EducatedSingles also please be careful with posting debug info it may contain some sensitive data.


How to format SQL file in place?

Currently I have a bunch of SQL files, but when I format using this tools, the output is directed to stdout. Is there a way where I can redirect the output to each respective files?
My current command uses glob:
npx sql-formatter **/*.sql

Thanks for the pattern, I use */  to format in place


Add option to quit immediately such as Q and do not route back to month view

Currently, I have it configured so that calcure goes directly to day event view by setting default_caledar_view in config.ini to daily. When I press q, it takes me to the monthly view. When I press q again, it asks me to confirm to exit.
I would expect to be able to quit immediately and that there is no need to be taken to the month view. Perhaps a Q command that does not ask for confirmation. I also find myself having to leave the application and open it up a lot, so maybe a command to reload data from the csv file could be useful.
Thanks!

Ah, yes, I forgot to fix that. I just fixed the quitting in the version 2.8.5, please check if that works for you.
pip install --upgrade calcure
About the reloading, I'll see how to better do that.
About quitting without confirmation, you can switch off confirmations in the config. But you'd like to have another button to quit without confirmation, right?

Okay, then I'll close this issue. Thank you for reporting.


[SPARK-24063][SS] Add maximum epoch queue threshold for ContinuousExecution

What changes were proposed in this pull request?
Continuous processing is waiting on epochs which are not yet complete (for example one partition is not making progress) and stores pending items in queues. These queues are unbounded and can consume up all the memory easily. In this PR I've added spark.sql.streaming.continuous.epochBacklogQueueSize configuration possibility to make them bounded. If the related threshold reached then the query will stop with IllegalStateException.
How was this patch tested?
Existing + additional unit tests.

Can one of the admins verify this patch?

Test build #99328 has started for PR 23156 at commit 72733c5.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99328/
Test PASSed.

cc @jose-torres @HeartSaVioR

Rather than controlling the queue sizes it would be better to limit the max epoch backlog and fail the query once that threshold is reached.  There already seems to be patch that attempted to address this https://github.com/apache/spark/pull/21392

@arunmahadevan don't fully understand your comment:

Rather than controlling the queue sizes it would be better to limit the max epoch backlog and fail the query once that threshold is reached.

I've written the following in the PR description:

If the related threshold reached then the query will stop with IllegalStateException.

AFAIK max epoch backlog == epochsWaitingToBeCommitted which is a queue,
but that's not the only unbounded part of EpochCoordinator (please see additional unit tests).
As a result I've limited partitionOffsets and partitionCommits as well.

@gaborgsomogyi what I meant was rather than exposing a config to control the internal queue sizes, we could have a higher level config like the max pending epochs. This would act as a back pressure mechanism to stop further processing until the pending epochs are committed. I assume this would also put a limit on the three queues.

Test build #99822 has started for PR 23156 at commit b0c5056.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99822/
Test PASSed.

I'd rather not jumping in something regarding continuous mode unless the overall design (including aggregation and join) of continuous mode is cleared and stabilized.

I thought this part is not affected. Who leads it? Asking it because haven't seen progress anywhere.

I think @jose-torres previously led the feature.

Ah, ok. This solution was agreed with him on https://github.com/apache/spark/pull/20936.

BTW, coming back to your clean up PR but it takes some time to switch context :)

@gaborgsomogyi No problem :) When you get some other times please take a look at my other PRs as well.

ping @jose-torres

cc @dongjoon-hyun

Thank you for ping me, @gaborgsomogyi . Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/7795/
Test PASSed.

Test build #102158 has started for PR 23156 at commit f6bc301.

Test build #102158 has finished for PR 23156 at commit f6bc301.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102158/
Test PASSed.

cc @vanzin

Standing here for long time and I think resolved all the comments. Can someone pick this up?

Test build #102657 has started for PR 23156 at commit 96152da.

Test build #102662 has started for PR 23156 at commit 43e61ef.

@vanzin thanks for your time!

Test build #102664 has started for PR 23156 at commit 9324c90.

Test build #102657 has finished for PR 23156 at commit 96152da.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102657/
Test FAILed.

Test build #102662 has finished for PR 23156 at commit 43e61ef.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102662/
Test PASSed.

Test build #102664 has finished for PR 23156 at commit 9324c90.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102664/
Test PASSed.

Test build #102746 has started for PR 23156 at commit 8a9b67f.

Test build #102746 has finished for PR 23156 at commit 8a9b67f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102746/
Test PASSed.

(The PR looks fine to me modulo @vanzin 's review comments - sorry I dropped it for so long.)

Test build #102820 has started for PR 23156 at commit d67db64.

Test build #102820 has finished for PR 23156 at commit d67db64.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102820/
Test PASSed.

Merging to master.


Add WebXR support

Hi, I'm new to three.js, and I like how you're creating interfaces and services for it.  I'm trying to port https://codelabs.developers.google.com/codelabs/ar-with-webxr/#6 to angular as way to learn webXR https://github.com/playground/angular-template-for-dummies/tree/web-xr, but I'm having trouble adding model to the scene.  Tried to debug it but it's not throwing any errors.  Thanks in advance for you help.

This would be a cool feature indeed!
I think you have to call .render on your Three.js THREE.WebGLRenderer instance after adding a child to the scene. We also do this in our model loaders, which in turn lead to THREE.WebGLRenderer.render being called.
Is it possible to test the WebXR API with a PC only, i.e. without a compatible device? I tried to enable the WebXR flags in Chrome Canary's chrome://flags section to no avail: this test site still shows "unsupported browser".

The demo on xr.plus looks very nice (checked on iPhone + Safari).  Very interesting.
Would need to setup a suitable VR development environment first.
Agree with ComFreek, the emulator/simulator which will allow to debug on Chrome (ideally without real VR device) could considerably speed-up things.

@ComFreek, currently one can only test in Chrome Canary behind a flag on a compatible device.  Would be ideal if there is an emulator for testing/debugging.   I will give .render a try sometime today.  Thanks.

@ComFreek with .render it is getting "WebGL: INVALID_FRAMEBUFFER_OPERATION: drawElements: cannot render to a WebVR layer outside of a frame callback"

Let's wait for answer at the linked issue. Unfortunately, "cannot render to a WebVR layer outside of a frame callback" also yields no helpful Google results. Do you know what the "frame callback" refers to?

@ComFreek actually, if look close enough and zooming in, something did get placed there.


Add institute of distance education balearic island

added the file with the data of the distance institute of the Balearic Islands

@JohnyFW First stage of verification passed, official domain is iedib.net as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


Bug: Log state not cleared before logging event in middleware

Expected Behaviour
I am currently using the injectLambdaContext middleware with the middy library to both clear persistent log state and log the invocation event. My lambda handler function puts a request ID on the logger for debugging purposes.
According to the docs, because I've set clearState to true, persistent attributes added inside the handler will NOT be cached. So, my expectation would be that the request_id attribute would never be shared between invocations (assuming each invocation contained a unique request_id).
Current Behaviour
I am seeing the initial event logged by the middleware including persistent attributes added from a previous invocation, despite clearState being set to true
Code snippet
const logger = new Logger({
    logLevel: 'DEBUG',
    persistentLogAttributes: {
        foo: 'bar'
    }
});

const lambdaHandler = async (event: { headers: {x-request-id: string } }, _context: unknown): Promise<void> => {
    logger.appendKeys({request_id: event.headers['x-request-id']});
    ...
};

export const handler = middy(lambdaHandler)
    .use(injectLambdaContext(logger, { logEvent: true, clearState: true }));

Possible Solution
It seems like the logEvent step occurs in the "before" middleware, here: https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/packages/logger/src/Logger.ts#L338 whereas the clearState step happens in the "after" middleware step here: https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/packages/logger/src/Logger.ts#L346, with the initialPersistentAttributes being used to override any existing persistent attributes set in a previous invocation.
Steps to Reproduce

Host a lambda behind API Gateway.
Invoke the lambda twice, each time using a unique x-request-id header in the request.
Observe via CloudWatch logs that the "Lambda invocation event" log line for the second invocation (assuming the second invocation was warm) has the first x-request-id header value in the request_id logger attribute.

AWS Lambda Powertools for TypeScript version
latest
AWS Lambda function runtime
16.x
Packaging format used
Lambda Layers
Execution logs
No response

I experienced the same just with a simple use of clearState: true.  I worked around with the following in the top of my Lambda handler:
logger.removePersistentLogAttributes(Object.keys(logger.getPersistentLogAttributes()))

NB: Only works for me because I don't set any 'initial persistent attributes'.

Hi both, thank you for the report.
I'll be looking at this tomorrow morning (EMEA timezone). I'll try to reproduce the issue and I'll either share a path forward or an explanation in case it's an intended behavior.

Hi, I've been trying to reproduce the issue following the steps described above and I was not able to.
To isolate the issue and provide a self-contained example, I have created this sample repo that has the similar components as the ones described in the "steps to reproduce" section of the OP (link to resources definition):

1 API Gateway
1 Lambda function with the code described below
1 Proxy integration that binds the function to a get method in a route

The code of the Lambda I used is this (link to repo):
import { APIGatewayProxyEvent } from 'aws-lambda';
import { Logger, injectLambdaContext } from '@aws-lambda-powertools/logger';
import middy from '@middy/core';

const logger = new Logger({
  logLevel: process.env.LOG_LEVEL || 'info',
  persistentLogAttributes: {
    version: 1,
  }
});

export const handler = middy(async (event: APIGatewayProxyEvent) => {
  logger.appendKeys({ request_id: event.headers['x-request-id'] });

  logger.info('Hello World!');

  return {
    statusCode: 200,
    body: JSON.stringify({
      message: 'Hello World!',
    }),
  }
}).use(injectLambdaContext(logger, { clearState: true, logEvent: true }));

While the command I used to make the requests to the API were these:
curl https://API_ID.execute-api.REGION.amazonaws.com/prod/test --header "x-request-id: $(uuidgen)"

Note that both API_ID and REGION were replaced with the ones of my deployment, while uuidgen is a command that generates an unique id each time it's run.
Based on the above, after making two requests these are the logs:

As you can see from the screenshots in my case the custom header x-request-id values in each requests are different and appear to be contained to the logs in its execution.
Also for the sake of completeness, I'm using the latest published version of the utility which is 1.5.1.
Could you please confirm that I'm understanding the issue and the steps correctly? If it appears so, could you please also try the sample I provided and check if you can observe the same behavior?

@dreamorosi My apologies, the repro steps are a bit more complicated than I laid out. Simply executing two requests synchronously won't cause the issue to appear. The issue seems to arise when multiple requests hit a warm lambda.
You can re-work the sample code as follows:

Thank you for clarifying, I have two notes:

The issue seems to arise when multiple requests hit a warm lambda.

You can see from the screenshots above that the second one is a not a cold start (first line of each log entry in the second screenshot).

Then, issue a single request to the lambda which will warm it up. Then, issue multiple requests in parallel to reproduce the issue with the shared logger instance.

Regardless of whether your code has async/await or promises, Lambda invokes your function one request at the time for each execution environment. This means that if you have two requests at the same time, or if the second request arrives before the first invocation has ended, Lambda will spin up two environments, both of which will have a cold start.
From the docs, in the lifecycle section, let's look at this diagram:

From left to right, the diagram represents two subsequent requests. When the first request arrives Lambda performs the "Init" phase, then it proceeds to the "Invoke" one. In this case, the subsequent request arrives sometime after the first function has already returned (first "Invoke" has ended), so another "Invoke" phase (the second) happens. Finally, the environment is shutdown.
If the second request arrived before the first "Invoke" had completed, which could happen when issuing parallel requests, then Lambda would have to spin up a second environment, which would result in a separate "Init" & "Invoke", completely independent from the first one.

I'm going to try updating my sample with your code & query the logs like you did to see if I can reproduce and get back to you.

Okay, I can reproduce the issue and I can do so even without the promise or async/await in the code:

Apparently the some of the persistent attributes seem to leak into the next invocation, but I'm able to reproduce this only starting from the second warm invocation onwards. Super weird, but interesting!
I'll continue investigating and work on a fix.

The decorator seems to not be affected by the issue:

import { APIGatewayProxyEvent } from 'aws-lambda';
import { Logger } from '@aws-lambda-powertools/logger';
import { LambdaInterface } from '@aws-lambda-powertools/commons';

const logger = new Logger({
  logLevel: process.env.LOG_LEVEL || 'info',
  persistentLogAttributes: {
    version: 1,
  }
});

class Lambda implements LambdaInterface {
  // Decorate your handler class method
  @logger.injectLambdaContext({ clearState: true, logEvent: true })
  public async handler(event: APIGatewayProxyEvent, _context: unknown): Promise<unknown> {
    logger.appendKeys({ request_id: event.headers['x-request-id'] });

    logger.info('Hello World!');

    return {
      statusCode: 200,
      body: JSON.stringify({
        message: 'Hello World!',
      }),
    }
  }

}

const myFunction = new Lambda();
export const handler = myFunction.handler.bind(myFunction);

A fix was released as part of the latest v1.6.0 release.

I believe we also ran into this, but I didn't have time at the time to investigate the root cause. So thank you so much for reporting and fixing.
At the time we overrode the addPersistentLogAttributes() method to clear out any existing keys matching the ones being added in this call.
This is what we added:
  // Override addPersistentLogAttributes() and not appendKeys() since the latter delegates to the former
  addPersistentLogAttributes(attributes?: LogAttributes | undefined): void {
    // I've found that attributes don't always get cleared consistently even when `clearState` is set to `true`
    // So we'll clear out any keys we're about to set to make sure
    if (attributes != null) {
      this.removePersistentLogAttributes(Object.keys(attributes));
    }

    super.addPersistentLogAttributes(attributes);
  }

We've upgraded to v1.6.0 but haven't yet removed this override, but once we have some time to test, we'll do so and retest as I think this PR should fix the issue we saw. If not, I'll create a separate bug later on.

@dreamorosi

If the second request arrived before the first "Invoke" had completed, which could happen when issuing parallel requests, then Lambda would have to spin up a second environment, which would result in a separate "Init" & "Invoke", completely independent from the first one.

Is this guaranteed that they are "completely independent"?  Quote from the original doc,
 After the function and all extensions have completed, Lambda maintains the execution environment for some time in anticipation of another function invocation. In effect, Lambda freezes the execution environment. When the function is invoked again, Lambda thaws the environment for reuse. Reusing the execution environment has the following implications:...
Does that mean there is a chance it will be reused? so they're not completely independent. If so, my question is if it is reused, then log context from the first request can still leak to the second request? if it is reset globally and the first request hasn't completed, first request's context will then be replaced by the second request.

Hi @Aaron-Zhao-Asurion, in Lambda each execution environment can only process one request at the time, this is guaranteed by the service. If a new request comes while the first one hasn't finished processing, Lambda will provision a new execution environment.
The only case in which Lambda will reuse the first execution environment is when the first request completed.


Add new Geode properties: ssl-client-protocols and ssl-server-protocols

These new properties have been added by this change: https://github.com/apache/geode/pull/7315

These new properties are required to dig certain versions of members out of a hole dug with SSLv2Hello as documented int GEODE-9991. I will be writing more details on the migration process. There is an SocketCreatorUpgradeTest that tests all the scenarios back to Geode 1.8.0. While this settings apply to all SSL protected components they are really only necessary for p2p communications.

@jdeppe-pivotal and @pivotal-jbarrett -
Looks like these new GemFire/Geode properties were added to the codebase on develop, implying these new properties will only be part of Apache Geode 1.15?  In which case, this will only apply to the SDG main-next branch and officially brought into SDG once SDG is rebased on Apache Geode 1.15.
Will these new properties be added (back ported) to Apache Geode 1.14 or 1.13, do you know?
I suspect since these property additions were prompted by the JDK version, and since both Apache Geode 1.13/1.14 are based on JDK 8 (default), with extended support for JDK 11, then perhaps not.  Although if you increase your JDK version range of support in Apache Geode 1.13/1.14, then maybe?

It has yet to be determined if these properties will be back ported to older releases. So far the changes are only in develop (1.16) and haven't been back ported to 1.15 yet either.

Geode support/1.15 branch was annulled and develop is 1.15, so this can be fixed in main-next already (independent of whether we decide to backport or not).  Make sure you are looking at Geode 1.15.0-build.1000 or later build.  The issue is not primarily motivated by JDK9+ work, but rather, by changes between JDK8 patches (e.g. someone upgrading from JDK 1.8.0_242 to 1.8.0_322)

This issue can only be resolved in SDG once the properties are added to the Apache Geode branch (e.g. develop) representing the next GA version (e.g. 1.15) after current (i.e. 1.14).
Technically, from SDG's POV, this means 1.15 build snapshots that are located here. Since this only recently changed, it was not actionable until now.
FYI, no other Spring Data (SD) module looks ahead, or builds on the underlying data store build snapshots like Spring Data for Apache Geode (SDG).  No SD module releases any version of the SD module: snapshot, milestone, release candidate, release, or otherwise on a non-released version of the underlying data store. So, this is rather an exception than the rule, and as such, these sort of tickets are not high priority relative to release deliverables. Effectively, what is currently in released versions of Apache Geode is what we build against and support, nothing more.
The only reason main-next exists in the first place, building SDG against the latest build snapshots of Apache Geode, is to prepare SDG for what is coming next, otherwise main-next is not strictly necessary for SDG development. It is not in our best interest to be chasing development-time activities in Apache Geode, which are subject to change, as this particular issue and the entire Apache Geode 1.15 development/release illustrates, which has been anything but predictable.
At any rate, this issues has been addressed now.


Implementation of relational operator for complex numbers in XLA

This is the suggestion to implement relational operators for complex numbers (<, <=, >, >=) as in numpy, i.e., the lexicographical order. In this PR only the ">" relation was implemented as feedback from the community is important to evaluate if this functionality is wished for and makes sense.
This could be leveraged for the implementation of np.unique in JAX as comparison and sorting of complex arrays is not supported by XLA but possible with numpy. Another usage could be an implementation of complex QR decomposition in JAX.
The remaining comparisons for complex numbers and tests for it, will be added if this functionality makes sense.

Matching numpy semantics makes sense to me, could we add tests?

@joschkabraun Can you please check @cheshire's comments and keep us posted. Thanks!

Okay, perfect! I’m currently working on it and will finish this weekend!

I have been looking through the code. Am I correct in assuming the tests for that should be placed into the file elemental_ir_emitter_test.cc?

@joschkabraun Can you please check @cheshire's comments and keep us posted. Thanks!

It has been 20 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@joschkabraun, Any update on this PR? Please. Thanks!

Unfortunately, I am currently very busy and seems advisable if someone else could take this over. I am sorry for answering so late!

@joschkabraun Thanks for the confirmation. Closing the PR.


[github actions] FINALLY fix the mysterious token error in github actions

This should finally (with high confidence) fix https://github.com/flutter/flutter/issues/141980, the mysterious error where git push sometimes fail.
Root cause:
When a pull request merges onto flutter's master branch, it is actually a merge from a branch on a flutter contributor's repository, to flutter's repository. Therefore, the actor of the pull request event, is the user that opened the pull request. And this actor would not have write access to repo and therefore the repo secret resolves to empty.
Therefore running your pull_request workflow when a pull request merges doesn't work because even though we are not running our workflows on a forked repository, the actor of the pull_request event comes from a forked repository, and secrets are not passed to this actor.
The correct way is using pull_request_target event instead of pull_request event. In workflows triggered by this event, GITHUB_TOKEN is granted read/write repository permission unless the permissions key is specified and the workflow can access secrets, even when the actor of the workflow trigger comes from a fork.
Note that workflows of this event runs in the context of the base commit and not the merge commit. But this doesn't matter for our use case since we are good with using the actions file from the base commit in the pull request event.
Tested:
I was finally able to reproduce the error by:

create a pull request under the username of different user other than the repository owner
merge and label the pull request, and use the token of this different user, but use it as repository secrets in the workflow
reproduced error

previously I wasn't able to reproduce this error on my personal repo because the actors in my tests are the same user.
Also tested on my personal repo, following the steps mentioned above, that using the pull_request_event type fixes the error. succeeded run
The Debug Process:
spent quite a while looking at other things during debugging, but they turned out to be unrelated. things that we experimented with are workflow conditions, ssh setup, git push url, manual trigger, workflow env, secret setup, dependency on market place actions (actions/checkout and peter-evans/create-pullrequest)

Why is this failing on Google testing?

Why is this failing on Google testing?

created b/322018010 earlier and passed it to current oncall. Yeah sorry I am aware that I have already declined a number of bugs outside my rotation recently, trying to catch up on projects at the moment