Extend Twilio Message Length

Twilio supports messages up to 1600 characters in length. This patches the previous hardcoded 160-char length in the Agent to be 1600 characters.
This addresses https://github.com/huginn/huginn/issues/2755
I tested it out a few times with SMSes to myself. They were:

Emitted by my Huginn's Twilio Agent as 212 character strings
Segmented by Twilio into two separate messages
Re-concatenated on my device by the carrier (or OS?)

Either way, they came through as expected in a single message. Please review and test out a bit more though :)
https://support.twilio.com/hc/en-us/articles/360033806753-Maximum-Message-Length-with-Twilio-Programmable-Messaging
Most carriers will concatenate messages into a single message on the device https://support.twilio.com/hc/en-us/articles/223181508-Does-Twilio-support-concatenated-SMS-messages-or-messages-over-160-characters-

Awesome, thank you for the contribution and the detailed explanation!


amplify status TypeError: Cannot read property 'lastPushTimeStamp' of undefined

Describe the bug
Receives "TypeError: Cannot read property 'lastPushTimeStamp' of undefined" when trying to call "amplify status" or "amplify push".
To Reproduce
Steps to reproduce the behavior:

Uninstalled entire node and npm environment first, hoping that would resolve the issue.
npm install -g @aws-amplify/cli
Checked Version to confirm<EMAIL_ADDRESS>amplify configure
amplify init
amplify status or amplify push

TypeError: Cannot read property 'lastPushTimeStamp' of undefined
at getResourcesToBeCreated (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\src\extensions\amplify-helpers\resource-status.js:120:69)
at getResourceStatus (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\src\extensions\amplify-helpers\resource-status.js:213:30)
at Object.showResourceTable (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\src\extensions\amplify-helpers\resource-status.js:269:13)
at Command.run (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\src\commands\status.js:5:27)
at Runtime. (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\gluegun\build\runtime\run.js:90:58)
at step (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\gluegun\build\runtime\run.js:32:23)
at Object.next (C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\gluegun\build\runtime\run.js:13:53)
at C:\Users*\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\gluegun\build\runtime\run.js:7:71
at new Promise ()
at __awaiter (C:\Users****\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\gluegun\build\runtime\run.js:3:12)
Expected behavior
Amplify status would allow me to see changes and push allows me to push. From both machines flawlessly. Currently am unable to test on my desktop.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10 64-bit
Browser: Chrome

Additional context
I  use a desktop and laptop for this project. They have two different access account and I utilize CodeCommit between them.

Update: I think... I fixed it. I managed to find my way to the amplify-meta.json file and noticed that some functions and a table were missing the timestamp. I also didn't need them anymore so I deleted from the file correctly. Everything is working so far!


perf(linter): [DO NOT MERGE] performance investigation of the css semantic model

Summary
memo: https://github.com/biomejs/biome/tree/main/xtask/bench#analyzer-benchmark

Test Plan

I found the bottleneck and resolved in my local machine. I'll create another PR.


Add initial CSS Variables and Map placeholder component

What this does
Adds initial baseline styles, and an index page, for the static overhaul of the Caselaw Access Project website. Specifically:

Adds a web component, caselaw-map, to test out how well global css variables will apply to encapsulated web components. The web component also includes some placeholder text that will be removed when we pull in actual CAP data.
Adds global CSS variables:

Colors
Fonts
Spacing
Typography

Adds css reset in wc-base.js
Adds all font families
Adds baseline index.html, with some CAP metadata (no open graph images just yet)

What it should look like

Implementation notes

There are a lot of files added, but fear not: most of them are fonts!
The caselaw-map component uses Lit primarily for easier readability. Lit is a minimal, well-documented library maintained by Google, and incorporated into design systems including Adobe's Spectrum Web Components, IBM's Carbon Web Components, and JSTOR'S Pharos Design System.
By default, all web components that are scaffolded using Lit's base element use the Shadow DOM. This can be disabled, but it would mean that we couldn't natively scope CSS to a web component, which I think is one of the big benefits of them. I really appreciate the readability of being able to see JavaScript, HTML, and CSS in the same view/same file for a component.
The CSS Reset is an exported module in wc-base.js so that it can be shared between all web components, following Lit's code example. .
CSS Variables don't need to be encapsulated in the same way because CSS Variables bleed through the Shadow DOM by design

How to test

Check out the remote fork and try to run the website locally. There shouldn't be any dependencies to install.

I've been using the Live Server extension to spin up the website, but because all the files are static, you should also be able to load the index.html file itself in whatever way is most convenient for you.

Check:

Does the gradient display?
Do the fonts load?

You may see a difference in font appearance between Firefox and Arc/Chrome. As far as I can tell, anti-aliasing fonts inside of a web component is not considered valid in Firefox, which is a bit confusing, because it is considered valid in Firefox for non-web components.

Thanks @matteocargnelutti that's great to hear!


Use .gitattributes file to normalize the source code commited

As we use on https://github.com/jhipster/generator-jhipster/blob/master/.gitattributes to control a few aspects of the committed source code.
Example:

Contributors on windows may commit files with crlf instead of lf line terminators.

docs: http://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes

@dgomesbr open the codereview


feat(schema): Name and Email now required

Why is name unique?

It's a bad variable name and is supposed to represent username


Update Docs, Publish through Multiple API Gateways

Fixed with https://github.com/wso2/docs-apim/pull/142 and https://github.com/wso2/docs-apim/pull/546


Does CVE-2024-43788 actually affect Webpack 4?

I see CVE-2024-43788 was patched in Webpack 5, and the CVE shows that Webpack 4 and below are affected, but are Webpack 4 and below actually affected? I don't see any code in Webpack 4 that looks like the patch that was applied to Webpack 5.

We're not going to backport this, and a general rule is to use the lts of webpack.

I'm not expecting for it to be backported, but can you confirm that it actually does affect Webpack 4 and below? If it does affect Webpack 4, I will be looking to create a patch for myself, since moving to Webpack 5 isn't an option for me.

webpack@4 doesn't have CVE-2024-43788, only webpack@5 affected

webpack@4 doesn't have CVE-2024-43788, only webpack@5 affected

In that case, let's get the CVE updated. I have requested a change to the GitHub Advisory Database: https://github.com/github/advisory-database/pull/4750.

@bradbm We're not actively adding code to the v4 version. Check out the releases page for the last commit hash.


Add support for Sphere schema

99% of the changes in this PR are related to the work done when investigating the SideFX problem with importing crowd agent (USDSkel stuff). It consists of:

Adding support to import Sphere schema (SphereSample, SphereImporter)
Handling skinned primitive that inherits skeleton data from parents but don't define those themselves (SkeletonImporter)
Intruder change: Make the ImporterMesh Sample works in edit mode.

I'm not confident with all the changes so be critical!

LGTM!


Can't mark text for copy-paste

Can't select text using the mouse for copying.
This seems to happen anywhere that isn't inside an editable text area, e.g. all labels.
Expected outcome
I can mark text just like anywhere else in my PC using the mouse.
Actual outcome
Marking text is impossible, can't copy it.
Versions
App: <IP_ADDRESS>
Chrome: 49.0.2623.112 m
OS: Windows 7
Steps to reproduce

Open ARC
Go to Socket
Open a websocket to some server
Send a message
Receive a message
Attempt to mark and copy either message

Hi,
Thank you for issue report.
I'll try to fix it in next update.


Conjur Helm Chart supports configuring Conjur with TLS

As a Conjur operator, I want to be able to configure OS Conjur to support TLS, so that I can use authn-k8s, which requires mTLS.
GIVEN a Kubernetes environment
WHEN I deploy OS Conjur using the Helm chart
THEN Conjur is configured with nginx to support TLS
mTLS is needed to support authn-k8s authentication within the same cluster between the Conjur OSS (master) instance and clients (conjur-authn-k8s-client) sidecar or init container using service accounts.
Estimate: 2 days
Confidence: medium

More info: "it's a single instance of OSS that can communicate with a k8s authn client deployed to a pod"
Expectation (from the info we have right now) is that this mTLS is intra-cluster rather than the larger inter-cluster setup.

Finally can get back to this. I will be trying to implement something like https://github.com/conjurinc/openshift-conjur-oss-deploy or https://github.com/conjurinc/container-appliance in the helm chart to move us forward with internal mTLS.
The story size is definitely not 2 days so I will update the estimate as well.
CC: @garkler


A first stab at making octokat.js work in browserify

This doesn't work yet, and it's not really clear if it can
work frictionlessly with other modules.
In the gentlest least-trolling way possible I definitely volunteer
to help with a port to JavaScript if you want to go that way.

Number #19 is a more reasonable approach.


DeathStalker Chroma regions not being set?

I am having difficulties with setting color regions for the DeathStalker Chroma. Lighting works for other keyboards like the BlackWidow.
Here's a link to the issue a user with a DeathStalker created.  https://github.com/antonpup/Aurora/issues/286

Checked out the issue posted on your project. It might require the use of the grid reference instead of targeting the keys. Chroma SDK has two Custom effects for keys. CHROMA_CUSTOM uses a grid reference (eg. 1,1) where as CHROMA_CUSTOM_KEY uses the RZKEY keymaps.
I don't have a deathstalker chroma, but I'll try and get hold of one. In the meantime, you may need to work with the user to fully test this.

Saying that, I noticed the user said they couldn't see any colours when setting the whole keyboard, which is definitely strange. Unless, it could be that CHROMA_CUSTOM_KEY is not supported on the deathstalker...
I've noticed we use CHROMA_CUSTOM_KEY for grid too, which may in this case be incompatible with the deathstalker.

Any advancements on this?

I can confirm that DeathStalker will not respond to .SetAll() commands

I think I know why, will have a look.
Sent from my iPhone

On 22 Jan 2017, at 12:36, Roxas Keyheart<EMAIL_ADDRESS>wrote:
I can confirm that DeathStalker will not respond to .SetAll() commands
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I now have a Deathstalker Chroma so I can investigate this further.

So I've done some initial investigation now I've been sent a Deathstalker, and it turns out Colore is setting position incorrectly so there's some fixes on the way!
However, I have highlighted to Razer that we cannot use CHROMA_CUSTOM_KEY with the Deathstalker, which is inconsistent with the rest of the devices.

Fix being tracked in #243.
This will make it a bit cumbersome to make effects that work on all keyboards, as the Deathstalker will need special treatment. One way to do it in the proposed solution is to send off a copy of the CUSTOM_KEY non-Key array to a CUSTOM effect. But without querying for the connected device there is no smooth way to use key effects on devices that support it, and fall back internally on the grid effect if keys are not supported.

Implemented now. Use the IsDeathstalkerConnected property on IKeyboard to check for Deathstalker presence and then utilize the SetDeathstalkerZoneAsync and SetDeathstalkerAsync methods to set zone colors. SetAllAsync now works on the Deathstalker as well.


Intellisense not working as expected

Hello,
when typing something like File. I would expect the intellisense popup to appear with all members for File and then as I proceed to type see the list gradually be narrowed down to the matching members. Well, just like in Visual Studio.
However the popup won't appear automatically after typing . and the only way I can get it to show is by pressing CTRL + Space. Also the list won't narrow down as I continue typing and I have to manually scroll through it to select the member I want.
Here's a video that illustrates what I mean:
https://github.com/oleg-shilo/cs-script.npp/assets/15066925/a07438f3-e29b-45ba-821a-32f813d9fba0
Is this how this plugin is supposed to work or is there something wrong? I didn't change any of the settings and it's a fresh install of notepad++ without any other plugins running.
For what it's worth I'm using plugin version <IP_ADDRESS> (x64) and notepad++ version v8 (x64) as suggested in #71 because I'm wanting to target the .NET Framework.
Thanks for any help!

Thankyou @megakraken,
No, it's not how it's supposed to work. Unfortunately, some Notepad++ internal changes interfere with the plugin's business logic.  It might be happening again as I have updated N++ and started having the same problem.
Thank you for reporting. I will have a look at i.

The things are happen to be more complicated.
While the loss of input focus indeed prevents keystrokes from going to the plugin it is actually Scintilla who is a suspect here (or NPP/Scintilla interop).
For whatever reason the SciMsg.SCN_CHARADDED notifications are coming with the char pointer set to zero.

Fortunately, it's possible to find out what character was typed by other means but.... it is not very elegant.
Though the user experience will remain the same.
I will publish the update in a day or two.

Reopening after an accidental closing.
Done fix is available in the latest release v<IP_ADDRESS> (Releases page)
The release has also been published on nppPluginList but the next release of the plugins updates up to the N++ team.
If you do not want to wait for the next N++ release, you can update the plugin from the Plugin-settings page.
The release source is:

x64:  https://github.com/oleg-shilo/cs-script.npp/releases/download/v<IP_ADDRESS>/CSScriptNpp.<IP_ADDRESS>.x64.zip
x86:  https://github.com/oleg-shilo/cs-script.npp/releases/download/v<IP_ADDRESS>/CSScriptNpp.<IP_ADDRESS>.x86.zip

@rdipardo, thank you so much for a detailed explanation. It makes perfect sense.
I will update the struct ScNotification as you suggested.
It's great to have you in this conversation. It's not the first time you have assisted me with the intricacies of the Scintilla interface.
Greatly appreciated.

It makes perfect sense.

If only the people who made Plugin.NET so popular had thought so, too 😔. Somebody had the bright idea of making plugins "easy" to develop. The ironic truth is there's nothing easy about safely marshalling .NET objects into C-like structures. By now there must be thousands and thousands of .NET plugins on end-user PCs, silently writing out of bounds every time Scintilla emits a notification...


feat: Create LoadBalancerEditor component

Fixes: #520
https://github.com/KaotoIO/kaoto-next/assets/265462/68c2ed5b-dead-4073-b13f-1a5198d6bb8c

Great @igarashitm 💪.
This is not related to this PR but what do you think about moving these custom forms to the Form folder instead? I'm not suggesting to do it in this PR, but rather want to know your opinion first.

Sounds good to me :+1:


Deleting points is probelmatic when POWO or analysis polygon is switched on

Move users defined points to the top of the stack to they are easily selectable. Work around is to switch these off. but not idea

The only solution I can think of here is to switch off analysis and powo polygons when this button is selected. But to make this work, it would be sensible to add a powo map switch @stevenpbachman what do you think?


[FALSE-POSITIVE]

Domains or links
[Please list any domains and links listed here which you believe are a false positive.](https://bridgechurch.tv/)
More Information
How did you discover your web site or domain was listed here?
Incorrectly marked as Phishing on Phishtank or OpenPhish?
Have you requested removal from other sources?
Please include all relevant links to your existing removals / whitelistings.
Additional context
Hi there!
Requesting for Block-list removal review after Sucuri cleanup.
URL: https://bridgechurch.tv
Thank you!
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

Can't help you as you have a huge problem as you supports web censoring against Humans free rights to democracy and freedom


v2 support?

when the cosyvoice2 is very welcomed, will this repo support speech_tokenizer_v2?

I just don't notice the update! Good work!


[Feature Request] Gitea as Git source

Self explanatory. Not a must-have immediately but would be cool to have :)

Thanks for the PR, I will add support for Gitea for sure!
I'm closing this as it's a duplicate of #130 . :)

Thanks for the PR, I will add support for Gitea for sure!
I'm closing this as it's a duplicate of #130 . :)
This is not a copy at all


Generated  models and request builders

This pull request was automatically created by Azure Pipelines. Important Check for unexpected deletions or changes in this PR.

@andrueastman @irvinesunday I think we've had an undesired change in the metadata processing this week:
The select/expand/orderby query parameters are now enums. This is not only breaking, but it also impacts the size of the SDKs, and is incomplete (with expand/select one can also do nested selects/expands and those are not reflected)
see this:
export const GetExpandQueryParameterTypeObject = {
    Asterisk: "*",
    SharedCookies: "sharedCookies",
    Sites: "sites",
} as const;
export const GetOrderbyQueryParameterTypeObject = {
    Id: "id",
    IdDesc: "id desc",
    Description: "description",
    DescriptionDesc: "description desc",
    DisplayName: "displayName",
    DisplayNameDesc: "displayName desc",
    LastModifiedBy: "lastModifiedBy",
    LastModifiedByDesc: "lastModifiedBy desc",
    LastModifiedDateTime: "lastModifiedDateTime",
    LastModifiedDateTimeDesc: "lastModifiedDateTime desc",
    PublishedBy: "publishedBy",
    PublishedByDesc: "publishedBy desc",
    PublishedDateTime: "publishedDateTime",
    PublishedDateTimeDesc: "publishedDateTime desc",
    Revision: "revision",
    RevisionDesc: "revision desc",
    Status: "status",
};

in b/packages/msgraph-sdk-admin/admin/edge/internetExplorerMode/siteLists/index.ts

@andrueastman @irvinesunday I think we've had an undesired change in the metadata processing this week: The select/expand/orderby query parameters are now enums. This is not only breaking, but it also impacts the size of the SDKs, and is incomplete (with expand/select one can also do nested selects/expands and those are not reflected)
see this:
export const GetExpandQueryParameterTypeObject = {
    Asterisk: "*",
    SharedCookies: "sharedCookies",
    Sites: "sites",
} as const;
export const GetOrderbyQueryParameterTypeObject = {
    Id: "id",
    IdDesc: "id desc",
    Description: "description",
    DescriptionDesc: "description desc",
    DisplayName: "displayName",
    DisplayNameDesc: "displayName desc",
    LastModifiedBy: "lastModifiedBy",
    LastModifiedByDesc: "lastModifiedBy desc",
    LastModifiedDateTime: "lastModifiedDateTime",
    LastModifiedDateTimeDesc: "lastModifiedDateTime desc",
    PublishedBy: "publishedBy",
    PublishedByDesc: "publishedBy desc",
    PublishedDateTime: "publishedDateTime",
    PublishedDateTimeDesc: "publishedDateTime desc",
    Revision: "revision",
    RevisionDesc: "revision desc",
    Status: "status",
};

in b/packages/msgraph-sdk-admin/admin/edge/internetExplorerMode/siteLists/index.ts

I don't think we've made any updates to the conversion lib between Tuesday and now as well as Metadata updates.
Currently looking into this. This is most probably caused by a change in Kiota.

closing since we know where the impact is coming from, will queue another generation

I don't think we've made any updates to the conversion lib between Tuesday and now as well as Metadata updates. Currently looking into this. This is most probably caused by a change in Kiota.

I am so sure I posted a follow up message about the root cause here. But it's not here (and I can't find it)


configs folder is not deleted when building ISO

The configs folder is not deleted and is present on the packaged ISO.

This is actually an issue with tools/runch. I'll add a handler to it so this doesn't happen anymore.


Problem with ShellyPlusPlugExporter image

I have been using the exporter for Shelly Plus Plugs since some months. After pulling latest image sha256:3cc8698c84ee350b55691de79391fc37f7024bc068801463986cc5277607e003, on x86_64, container exits with following error:
# docker run --name ShellyPlusPlugExporter -d -p 10009:10009 -v ./shelly:/Config lukassoo/shelly-plus-plug-exporter:latest
b74878846b8b3973afe293026b7ce6d806e7cca3ad597149334a11becb0e9f86
# docker logs ShellyPlusPlugExporter
exec /usr/bin/dotnet: exec format error

Please let me know if any further details are needed.

It seems an ARM executable was pushed to the "latest" docker tag somehow.
I have re-built the image, pushed it, and pulled it on another machine and it appears to be working now.
I am unsure as to how this happened 🤔
The build process is automated and the issue should be present in all exporters if it were there.
I am still manually pushing the built images but they already have tags set so swapping on accident should not be possible.
I hope there isn't a rare race condition hiding somewhere.
@dtolgyg Let me know it the image now works as intended once more.

Hi,
I have tested the new image, and indeed it works again.
Thank you, for addressing this issue so quickly.


proposal: cmd/link: create an information section with eface type struct addresses

Unlike iface, which has itab structure and we could get to type struct (runtime/type.go), eface doesn't have one and the code (compiled with pic) gets type address directly, using lea instructions on x86.
Example : lea 0x100050(%rip), %rax # 200500 <type.*+0x1234>
To handle it I propose to create an information section (debug type, that could be stripped) with an array of eface type structures, so it could be easily found in a binary file.
This information is required for further handling of Golang executables by post-link-optimizer tools like Bolt to make it possible to read actual information about eface types and account it during further basic blocks reordering.
Golang support for Bolt was announced here: https://github.com/facebookincubator/BOLT/issues/154#issuecomment-842143948
Currently, we are close to upstream Golang support in Bolt, but it requires changes described in this proposal.

This proposal has been declined as retracted.
— rsc for the proposal review group


chore(main): release 2.4.28

:robot: I have created a release beep boop
2.4.28 (2024-11-25)
Feature Improvements

改进文件编译 (3175c3b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rainbowwarmth/KazuhaBot/releases/tag/v2.4.28 :sunflower:


It does not work but it is a Virus

No, it's not a virus. It just hasn't been updated for 7 months.

Same it won't work

same not working

not virus

its not a virus lol bozo


Support focusNode and textEditingController parameters for Autocomplete (as passthrus to RawAutocomplete)

Use case
It can be useful to have the ability to create (and control) the focusNode and textEditingController of an Autocomplete widget.  The underlying RawAutocomplete widget supports accepting these as optional parameters.
Proposal
I propose to adding the focusNode and textEditingController parameters supported by the RawAutocomplete widget to the material Autocomplete widget and passing these through to the RawAutocomplete constructor.
I understand that I can re-implement the Autocomplete widget myself, and I have done this on multiple occasions - and I am sure that I am not alone.

There is also a related use case here: https://github.com/flutter/flutter/issues/140662#issuecomment-1994590242

https://github.com/flutter/flutter/pull/146995 would have resolved this but was incomplete. If anyone would like to work on this and resolve the outstanding feedback it is there.


[MODIN]: Add time results verifier for getting started notebook

Existing Sample Changes
Description
The notebook is supposed to show the performance improvement after switching from stock Pandas to Modin, it compares the execution times of Pandas and Modin in various scenarios. The previous version of the notebook didn't imply that the Modin could be slower than Pandas anyhow and so confused users if such happened.
The changes in this PR introduce a time verifier, that compares Modin and Pandas execution times and prints a note if Modin appears to be slower with the possible reasons for it (poor CPU performance, old Modin version, silly environment variables).
Fixes Jira MODIN6-135.
External Dependencies
The changes do not add any new dependencies.
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] Implement fixes for Jiras

How Has This Been Tested?

[x] Command Line

As there are no automatic test cases for jupyter notebooks in the repo, the changes have been tested manually:

Create an environment with Modin installed if you don't have one:

conda create -n test_env "python>=3.8.1" -c conda-forge
conda activate test_env
pip install modin[all]

Install requirements for the notebook:

cd path/to/getting/started/notebook
pip install -r requirements.txt

Run the notebook:

ipython IntelModin_GettingStarted.ipynb

Verify that the last line of the output is "[CODE_SAMPLE_COMPLETED_SUCCESFULLY]"

Would also like to get a review from Modin folks: @Garra1980 @YarShev @vnlitvinov

@praveenkk123, The sample's tests in CI are failing at the importing Modin step. It seems that the failure doesn't correlate with the changes in this PR as it doesn't change any notebook's dependencies.
Moreover, I found that the previous PR to the Modin's samples also had red CI. Do the CI for Modin samples is broken? Is it a known problem?

Converting PR to draft until #863 is merged into master


Update cats and other versions

Current coverage is 77.40%

Merging #192 into master will not affect coverage as of 4fcf54b

Powered by Codecov. Updated on successful CI builds.


Precompiled binaries fail on RedHat 4.1.2-54

Using the normal binaries I get:
$ ./stack
./stack: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory

Using the CentOS 6.x binaries, I get:
$ ./stack
./stack: /lib64/libpthread.so.0: version `GLIBC_2.12' not found (required by ./stack)
./stack: /lib64/libc.so.6: version `GLIBC_2.10' not found (required by ./stack)
./stack: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by ./stack)
./stack: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by ./stack)

Not sure if there's anything that can be done about this. Any chance of reducing the dependencies of stack, e.g. by linking in more stuff?
I appreciate this system is ancient, and understand you may not want to bother fixing it.

You can compile stack as a static binary. Unfortunately glibc can't be linked statically, so you should use some other C library like musl. After that will "weight" tens of megabytes, but it will work anywhere.

I meant to raise this against stack, but had the wrong tab open. Now reraised properly: https://github.com/commercialhaskell/stack/issues/1721. Thanks for the feedback @vasiliyl, I've copied it to Stack.


Endline Normalization and bugfixing

I've fixed various bugs in Lombok :

In classes with already defined factory methods and constructors, but a "staticConstructor" is also included, then lombok does not generate any method (see ValueStaticConstructorOfOverriden test cases).

After running Spotbugs over Lombok, I found the error VA_FORMAT_STRING_USES_NEWLINE in various calls, and I fixed it.

I normalized some files (https://help.github.com/en/github/using-git/configuring-git-to-handle-line-endings)

Please, take these PR in account.

I can't accept this PR. The stylistic changes (specifically, normalizing the line endings) is not okay; the noise in the tracker is not worth it, and git already takes care of this. The VA_FORMAT_STRING_USES_NEWLINE spotbugs error is in our opinion incorrect; java will render just \n fine on windows terminals, it's \n on all other OSes worth talking about, and having 'stable' output is on its own useful as well.
Your [1] item is not entirely clear to me; the fact that your file update there also looks like every line changed means you're making it very hard for me to diff this. I'm guessing that's referring to a bug whereby asking lombok to generate a static constructor may cause issues if you already have it?
Thanks for the effort, but by bundling these things into one package I can't accept this :(
I'd prefer it if it went like this:

file a bug for that staticonstructor thing with a clear example of how current master branch lombok gets it wrong,

file a PR with a fix, where the diff lists only actually changed lines (so don't autoformat the entire file, or change the line ending on every line).

I'm going to deny this PR; I've looked at ValueStaticConstructorOfOverriden and it seems like the bug report you're trying to fix here is that lombok will attempt to generate the static method even if it is already explicitly there.
That's not a bug, it's intentional: If you go out of your way to explicitly tell lombok to generate a method by some certain name, then lombok is going to do what you asked it to. Lombok only silently does nothing in specific cases where it makes sense (such as not generating an already-existing getter, but only if the lombok annotation that would generate it is also doing other things (such as Getter on an entire class, or @Data). Where convenient lombok will recognize the problem and generate a more specific and clear error message, but in this case that's not worth the maintenance burden.


Deye SUN-12K-SG02LP1-EU not showing data for PV3 (MPPT3)

Description
Hello I'm using the Deye SUN-12K-SG02LP1-EU inverter which is having 3 MPPTs where 1 & 2 are working just fine with this great integration, but 3 is not showing at all and I have no entities for it. I'm using the deye_hybrid.yaml I also tried with auto and I selected 3 MPPT during setup but no luck. Everything else is working perfectly apart from the missing MPPT 3 (PV3) What can I do ?
Reproduction Steps
add solarman integration for SUN-12K-SG02LP1-EU inverter with the deye_hybrid.yaml config
Log
`Logger: homeassistant.components.number
Source: helpers/entity_platform.py:764
integration: Number (documentation, issues)
First occurred: 8:42:00 PM (2 occurrences)
Last logged: 8:42:00 PM
Platform solarman does not generate unique IDs. ID Deye_2990981151_Battery Generator Charging Current already exists - ignoring number.deye_battery_generator_charging_current
Platform solarman does not generate unique IDs. ID Deye_2990981151_Battery Grid Charging Current already exists - ignoring number.deye_battery_grid_charging_current
Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:764
integration: Switch (documentation, issues)
First occurred: 8:42:00 PM (1 occurrences)
Last logged: 8:42:00 PM
Platform solarman does not generate unique IDs. ID Deye_2990981151_Generator already exists - ignoring switch.deye_generator
`
Version
24.11.02

Hi @peyanski, can you show me attributes of Device sensor?

feat: Add MPPT 3 & 4 for Deye Hybrid

Hi @peyanski, can you show me attributes of Device sensor?

sure, I'm attaching screenshots but if you prefer something else just let me know

it seems that is working now! Too bad that I have no Sun at the moment to confirm it. Many, many, many thanks!

Can you click on sensor named "Device" to show it's details and then click on "Attributes" at the bottom of that popup window?

Hi,
I have the same inverter ( for Deye SUN-12K-SG02LP1-EU-AM3) , and I see that the value multipliers are wrong for some power measurements (some powers appear divided by 10)
I propose attached definition that works fine for me (including MPPT3 data)
is it possible to add this definition file?
deye_sg02lp1am3.zip

Can you click on sensor named "Device" to show it's details and then click on "Attributes" at the bottom of that popup window?

Sure, now I got it

Hi, I have the same inverter (Deye SUN-12K-SG02LP1-EU-AM3) , and I see that the value multipliers are wrong for some power measurements (some powers appear divided by 10) I propose attached definition that works fine for me (including MPPT3 data) is it possible to add this definition file? deye_sg02lp1am3.zip

indeed some power values (like grid power and load power are divided by 10). To sort this out I created a sensor templates like this {{ int(states('sensor.deye_grid_power'))*10 }} but if this is added in the definition like @vinste suggested will be better

Okay so which sensors are incorrect?

`      - name: "Grid L1 Power"
l: 1
class: "power"
state_class: "measurement"
uom: "W"
rule: 2
registers: [0x00A7]
icon: "mdi:transmission-tower"
  - name: "Grid Power"
    l: 1
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00A9]
    icon: "mdi:transmission-tower"
    attributes: [inverse]

  - name: "External CT1 Power"
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00AA]
    icon: "mdi:transmission-tower"

  - name: "External CT2 Power"
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00AB]
    icon: "mdi:transmission-tower"

  - name: "External Power"
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00AC]
    icon: "mdi:transmission-tower"

  - name: "Load L1 Power"
    l: 1
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00B0]

  - name: "Load L2 Power"
    l: 2
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00B1]

  - name: "Load Power"
    l: 1
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    registers: [0x00B2]

`
Each of these require a scale 10

Great, thanks.
Still, I do not know if these modifications concern all other deye hybrid inverters.
Deye SG04lp3 and SG01hp3 are deye hybrid inverters too, but with different registers definition than SG02lp1 or what is named "hybrid" in your deifinitions.
To be on the safe side for the ones using the deye_hybrid definition, you might consider defining a SG02lp1 dedicated definition file.

Yes they have their own profiles.
There is now autodetection in place using register number 0:

String Inverter: deye_string.yaml
Single-Phase Hybrid Inverter: deye_hybrid.yaml
Microinverter: deye_micro.yaml
LV 3-Phase Hybrid Inverter: deye_sg04lp3.yaml
HV 3-Phase Hybrid Inverter: deye_sg01hp3.yaml
HV 3-Phase Inverter 6-15kw: deye_sg01hp3.yaml
HV 3-Phase Inverter 20-50kw: deye_sg01hp3.yaml

fix: Platform solarman does not generate unique IDs

Hey guys (@peyanski and @vinste)! You have both this exact device model including power rating?

Hey guys (@peyanski and @vinste)! You have both this exact device model including power rating?
Edit: It looks like that not every deye_hybrid.yaml compatible device needs that * 10 scaling... bruh.

Hey @davidrapan thanks for your efforts it is working flawlessly now for our models but that seems to hurt other the other hybrid inverters. What if we leave the SG02LP1-EU with a dedicated definition file? That will sort this issue, actually all issues. What do you think?

I'd rather not give up on that autodetection. I'll try to figure out if there is any way of differentiating the devices first.

I wonder if it depends on Rated Power? Solarman App has to be able to detect it too so there needs to be some way.

It could depend on generations (SG01, SG02,... SG05), or on rated power, or on firmware version, or on family (SUN-7.6/8/10/12K-SG02LP1-EU-AM2/AM3 for instance)
It might depend on rated power, but then not only, as sg01hp3 also exist in 12k rated power, but does not have scale 10...

sg01hp3 in fact does have different scaling than sg04lp3 that's why there are different files for them but in their case they also differentiate in have separate Device type so for them it's easy.
SG02 is in range above 6kW w/ 3 MPPTs and SG03 equal or lower than 6kW w/ 2 MPPTs. I guess it will be good starting point even so SG05 rated power has wider range but also w/ 2MPPTs.

v24.12.06_4:

feat: Add scaling modifier + Reverted Deye Hybrid scaling

And check that new checkbox in inverter configuration to switch to scale: 10. This will very probably change in the future but I had to fix it for now somehow. 😉

Hi,
With 24.12.08_5, when I check the « mod » switch, power is not scaled by ten.
Moreover, some values are not available anymore, such as grid voltage and output voltage.

Which ones exactly are gonne?

fix: Entity descs mod overwritten during autodetection

Which ones exactly are gonne?

Grid voltage and output voltage

They are relevant only when you have more than 1 phase.

Then where can I get grid power and voltage?

You have:

Grid Power
Grid L1 Voltage
Power
Output Voltage

I now have Grid power.
Still, from what I understand, all L1 and L2 values are normally the values for the two other phases in a 3 phase system (otherwise you would have L3 values), or for split phase Systems.
Grid voltage /current and power, as well as output voltage/current and power are the standards in a single-phase system.
now there is a mix of L1 voltage and L1 current but no L1 power, and power but no voltage or current
Here is a picture of what is populated in Deye application for a single-phase system.

Yes, and because in Single Phase you have e.g. Grid L1 Power = Grid Power I left just Grid Power.

Yes, but then why keep Grid power and not Grid voltage?
Now, there is a mix of split phase values (L1/L2) together with single phase ones (no L1 nor L2 mentioned):
grid power=grid L1 voltage x grid L1 current, but grid L1 power, grid voltage and grid current doesn't exist
In a single phase system, grid power= grid voltage x grid current
In a split phase system, grid L1 power = grid L1 voltage x grid L1 current and grid L2 power = grid L2 voltage x grid L2 current

Because Grid Voltage is voltage between L1 and L2.

Full list (structure) of phase sensors is:

L1 Voltage, Current and Power
L2 Voltage, Current and Power
Then there is Power w/o L mentioned which is SUM of L1 and L2 Power

Single/Split-Phase sensor visibility reasoning:

Case A) Single Phase:

L1 Voltage and Current
Power as sum

Case B) Split Phase:

L1 Voltage, Current and Power
L2 Voltage, Current and Power
Power as sum

This way no matter single/split phase you always have sensor which always refers to sum power (and it doesn't matter if you also use L2 or not) - change from single to split phase only adds new sensors and doesn't change anything.
So @vinste, if you think that there is better way tell me and we can change it. 😉

Thanks David for your concern.
Actually, I do not really understand what these L1 values measure as it does not seem coherent:  if grid power=grid L1 current x grid L1 voltage,  L1 current is wrong on my system, as well as in my exemple hereunder, Load power should be 0 as nothing is connected to load.

There is one remaining issue too: battery current scale is wrong too, it should be 10 times more.

Single Phase: Grid Power = Grid L1 Current * Grid L1 Voltage
Split Phase: Grid Power = Grid L1 Current * Grid L1 Voltage + Grid L2 Current * Grid L2 Voltage

The original request for * 10 was just for Load and Grid Power and I don't have device which uses this profile so @peyanski? Can you confirm that for battery?

Single Phase: Grid Power = Grid L1 Current * Grid L1 Voltage

As you can see in my screen dump, grid L1 current is unfortunately wrong, as well as load power

Do you have the scale modifier enabled in the options?


Issue 554 ownerreferences namespaces

@rgodfrey The second commit is just picked from master to get a jenkins build.

@rgodfrey Looks like the test failure cause is that this feature only works on OpenShift >= 3.6

Even though its supported in kubernetes 1.5, its not enabled in OpenShift 1.5: https://github.com/openshift/origin/issues/11951


Migrate to a smaller linux distro to reduce docker image size

Consider https://github.com/iron-io/dockers/tree/master/java/java-1.8 or something similar as suggested in the comments to http://tomaszdziurko.pl/2016/01/dockerizing-spring-boot-application/

#96

From 400MB to 200MB :)
https://hub.docker.com/r/tdziurko/jvm-bloggers/tags/

Looks good :)


Cursor Jump noted in python scripts

Is anyone else noticing this?
I spun up a brand new CentOS server in AWS and noticed that after I start typing import
#!/usr/bin/env python

i

my cursor jumps here the first column of the second line:
#!/usr/bin/env python
#    <-- (That is supposed to be the cursor)
i

I have also tried typing def with similar results.  I do not note this behavior with plain text files that I create.
I am currently running CentOS 7 with vim 7.4
21:41 Ansible (AWS): ~/ # cat /etc/*release
CentOS Linux release 7.4.1708 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.4.1708 (Core)
CentOS Linux release 7.4.1708 (Core)
21:42 Ansible (AWS): ~/ # git --version
git version <IP_ADDRESS>
21:42 Ansible (AWS): ~/ # vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug  2 2017 00:45:39)
Included patches: 1-160
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
-balloon_eval    +float           +mouse_urxvt     -tag_any_white
-browse          +folding         +mouse_xterm     -tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
-clientserver    -hangul_input    +netbeans_intg   +title
-clipboard       +iconv           +path_extra      -toolbar
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             +rightleft       +windows
+diff            +menu            +ruby/dyn        +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/etc"
 f-b for $VIMRUNTIME: "/usr/share/vim/vim74"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -g -pipe -Wall -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-z,relro -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,--enable-new-dtags -Wl,-rpath,/usr/lib64/perl5/CORE  -Wl,-z,relro  -L/usr/local/lib -Wl,--as-needed -o vim        -lm -lnsl  -lselinux  -lncurses -lacl -lattr -lgpm -ldl   -Wl,--enable-new-dtags -Wl,-rpath,/usr/lib64/perl5/CORE  -fstack-protector  -L/usr/lib64/perl5/CORE -lperl -lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
21:42 Ansible (AWS): ~/ #

Any ideas of how I can correct this?

i have the same error

Same issue here.

It must be a supporting plugin issue. I see that this vimrc was last committed to on Feb 13, 2016.  I guess that we could start disabling plugins that could be the issue until we happen across it.
(ಥ﹏ಥ)

I was able to fix it for now with  UnBundle 'klen/python-mode' in my .vimrc.local and then run vim +BundleInstall! +BundleClean +q.  Hopefully "klen/python-mode" gets fixed for this issue soon (or we figure out a setting to fix it).  Let us know if anyone has luck with a permanent fix.  Thanks


Does it has BigDecimal in mruby?

I found that in some circumstances I need highly precise decimal type for calculation. So does Mruby support BigDecimal or does it has Mruby gems to support that? thanks!! If not, what should I do the achieve that?

There is a gem to add bignum support.
https://github.com/chasonr/mruby-gmp-bignum/ or https://github.com/chasonr/mruby-bignum/
Read the readme on how to use it, because it either needs a forked mruby version or you have to use special functions to to math on them.

@Asmod4n Thank you very much. However, as my understandings, the gem does not support the BigDecimal. For example, if I want "123456789.123456789 + 123456789.123456789", it should be "246913578.246913578". But for now I got "246913578.246913". Am I correct?

if you want to use + - * / you have to read the readme of the gem.
It should work with 123456789.123456789.to_bn + 123456789.123456789 but i haven't use those gems yet.

Since there are external mrbgems to implement bignum, and the ISO standard does not require bignum, I suggest we close this issue as wontfix.

Just to clarify: the Bignum gems implement integer arithmetic, not decimal floating point as torsakch seems to want. They could be used as a basis for a BigDecimal class, but they do not provide BigDecimal themselves.


bug: Navbar is overlapped to the status bar

Type: bug
Ionic Version: 2.x
Platform: mobile webview
The navbar is overlapped to the status bar when display in Ionic View.

Image attached

Hello @dennyoon , thanks for opening an issue with us! Is this with the latest conference app? Could you do a git pull and try again please?

Hello @jgw96, I've re-clone the repository already, and it's still the same in Ionic View. Perhaps it's kind of Ionic View bugs or Ionic2 setting?

I have the same problem.

Thanks for the issue! There is an issue to fix this in Ionic View with a temporary work around: https://github.com/driftyco/ionic-view-issues/issues/164


Issue with FileAgnt.exe mentioned in To create a sample SCIM endpoint section

There has been lot confusion around the step 7 mentioned in this section - https://docs.microsoft.com/en-us/azure/active-directory/active-directory-scim-provisioning#getting-started-1 of document which state to use FileAgnt.exe. However, it seems that is not correct, it need to be Filesvc.exe. There have been Stack Overflow thread - https://stackoverflow.com/questions/49412093/azure-ad-synchronization-using-scim-and-asp-net-web-services
MSDN Forum Thread - https://social.msdn.microsoft.com/Forums/en-US/31f99699-7b4f-4f8c-bfd4-9c95bdac70fb/ad-automatic-provisioning-using-scim-services?forum=WindowsAzureAD
GitHub Sample Issue - https://github.com/Azure/AzureAD-BYOA-Provisioning-Samples/issues/13
raised by customers around this document. Please check on it.

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

ID: 45cb3eec-7693-4e22-bcde-3f85d5a4be14
Version Independent ID: 506c3302-e823-8f1e-d547-083ef0b664df
Content: Automate provisioning of apps using SCIM in Azure Active Directory
Content Source: articles/active-directory/active-directory-scim-provisioning.md
Service: active-directory
Product: unspecified
GitHub Login: @asmalser-msft
Microsoft Alias: asmalser

@asmalser-msft Please check on this issue as customers have raised it in multiple online forum. I have verified one part of it where using - FileAgnt.exe http://:9000 TargetFile.csv seems to be wrong as when we build solution and run it, below is the result. It seems Filesvc.exe need to be run in this step. Please clarify and make required changes to document.

Acknowledged. A pull request with a fix has been submitted. #please-close

https://github.com/MicrosoftDocs/azure-docs-pr/pull/42681


Search bar

Correctly switches fragments upon selecting the search bar and saves submitted search queries

[x] New feature (non-breaking change which adds functionality)
[x] Complete, tested, ready to review and merge
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] There are no merge conflicts

Getting 2 warnings:

[kapt] Incremental annotation processing requested, but support is disabled because the following processors are not incremental: androidx.room.RoomProcessor (DYNAMIC).
Parameter 'view' is never used, could be renamed to _

Both warnings are cleared


Connection Diagram for DMD + Raspi

@ranranking I remember seeing a little diagram on your screen that showed the flowchart of raspi, imswitch and camera. Should we add this here?
https://opensimmo.github.io/docs/Electronics

yeap, should we add it now or after the paper

Now is fine in my opinion :)

i pushed it here https://github.com/openSIMMO/openSIMMO.github.io/blob/main/docs/IMAGES/SIMMO_Hardware.pdf


Replace stake/unstake in protos with a single tickets spending call

We don't stake/unstake anymore now we instead need to lock tickers in a Proto and track time, after X period (as propagated from ETH contract -> pallet assets) we burn them/remove them from the Proto. To refresh users need to literally spend again tickets.

This is what I did

@sinkingsugar , isn't this done?

Yeah curate but I don't think it's 100% complete.

I would close this ticket, as curate function has been done, and specify what is still needed in other issues, ok?
I already created #200 as a starter.


Rebuild after files change

Rebuild if any file cc read/check has changed

How is this different from https://github.com/rust-lang/cc-rs/issues/765?

Thanks this is a duplicate


Proposal: Add cassandra username and password config values to docker/config_template.yaml

We're currently overwriting the config_template in our own docker image, but we wouldn't have to do this if these keys were in the config_template.yaml file.
Here's what I propose the keys should look like:
user: {{ default .Env.CASSANDRA_USER "" }}
password: {{ default .Env.CASSANDRA_PASSWORD "" }}
It looks like in this pull request https://github.com/uber/cadence/pull/299/files#diff-ba4cd460bd2d61f93b2b4bc4f8750faa we're already looking for these values and only adding authentication when they're set so this shouldn't affect other users that are not using authentication.

Also consider the change in start.sh that makes the connection to the database.
cqlsh -u $CASSANDRA_USER -p $CASSANDRA_PASSWORD --cqlversion=3.4.4 $server

@kfoxb @nhernandez2 PR is out. Feel free to give some comments :D

@longquanzheng Our company has switched to using Temporal actually since I opened this, so I probably won't be able to test it. It is exactly what I was looking for though, thank you for implementing it.

@kfoxb Temporal already implement it? I also added a ticket for this. https://github.com/temporalio/temporal/issues/513

It's merged in master and will be included in the coming release.


Fix handling of TrackEvent.Ended

Track wasn't unpublished because it was not sent in the event.

This is occurss again! TrackEvent.Ended not fires.
In this commit https://github.com/livekit/client-sdk-js/commit/8a6fbba98c072836d54f0aee6b002f25f4f38b7a the track is not passed anymore. Some reason for that?


image, svg support?

Hello,
Does just-the-docs support adding images, svgs and other assets?
Thanks,
Sachin

@sdole this is supported via Jekyll's standard way of including assets in markdown.


How to build without fontawesome pro licence?

I'm keen to build this extension myself to get a better idea of how it works and possibly add some additional features, but it seems I need an auth token for the fontawesome library? Do I actually have a to purchase it to build this extension? Why do I even need fontawesome, not clear why this extension would require something like that...

BTW I removed the references to fontawesome pro (it seems you're only using it for some icons), but now when running npm run build I get
...\github\blmage\duolingo-solution-viewer\node_modules\rollup\dist\shared\loadConfigFile.js:480
? (await import(url.pathToFileURL(fileName).href)).default
^^^^^^
SyntaxError: Unexpected token import
at createScript (vm.js:80:10)

Installed latest nodejs and now it gets stuck on
src/ui.js → dist/src/ui.js...
It was there a good 15 minutes, I killed it and reran "npm run build" but is just stuck there again.

Left it running a couple of hours and finally got this:
<--- Last few GCs --->
[13572:03E2FCA8]  5547895 ms: Mark-sweep (reduce) 1012.4 (1025.0) -> 1011.4 (1026.0) MB, 3411.1 / 0.0 ms  (average mu = 0.102, current mu = 0.027) task scavenge might not succeed
[13572:03E2FCA8]  5551672 ms: Mark-sweep (reduce) 1012.4 (1025.0) -> 1011.4 (1026.0) MB, 3684.3 / 0.0 ms  (average mu = 0.063, current mu = 0.025) allocation failure scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00FCE5C9 v8::internal::Heap::PageFlagsAreConsistent+2169
2: 00FC4651 v8::internal::Heap::CollectGarbage+1985
3: 00FC2D03 v8::internal::Heap::AllocateExternalBackingStore+1155
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
...

Do I actually have a to purchase it to build this extension?

I must admit that I completely overlooked this when switching to the Font Awesome Pro packages, given all the benefits, and the fact that I did not really expect contributions (thanks for considering to!).
Sorry, I don't have an answer right now, but I'll be thinking about it to try and find the best solution.

It was there a good 15 minutes, I killed it and reran "npm run build" but is just stuck there again.

There is probably an unresolved import that remains somewhere.

Why would an unresolved import cause that? E.g. before commenting out the references to FontAwesome pro I simply got errors that the import couldn't be found...
Do you have instructions for building at all?
Get Outlook for Androidhttps://aka.ms/ghei36

From: blmage @.>
Sent: Thursday, May 6, 2021 10:06:41 PM
To: blmage/duolingo-solution-viewer @.>
Cc: wizofaus @.>; Author @.>
Subject: Re: [blmage/duolingo-solution-viewer] How to build without fontawesome pro licence? (#155)
Do I actually have a to purchase it to build this extension?
I must admit that I completely overlooked this when switching to the Font Awesome Pro packages, given all the benefits, and the fact that I did not really expect contributions (thanks for considering to!).
Sorry, I don't have an answer right now, but I'll be thinking about it to try and find the best solution.
It was there a good 15 minutes, I killed it and reran "npm run build" but is just stuck there again.
There is probably an unresolved import that remains somewhere.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/blmage/duolingo-solution-viewer/issues/155#issuecomment-833469908, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABI5UAKB5TKGXFFUXDFFY3TTMKA5DANCNFSM44GBTGKQ.

Weird, I cleaned out the node_modules folder and now I'm getting "'rollup' is not recognized as an internal or external command"

It looks like faKey, faThumbtack, faArrowFromLeft and faArrowToRight, are the only icons you needed from fontawesome pro - for now I've assigned this with existing free icons, cleaned out node_modules, rerun npm install and npm run build and it seems to have built successfully...

Alright, got it building and installed using 'npm run build-debug' and adding the 'dist' folder as an unpacked extension to Chrome - it's definitely doing something (some of my console.log statements are executing) but it's not actually working, there's no solution lists getting loaded etc.

It's failing in sendMessageToBackground, chrome.runtime.sendMessage is setting chrome.runtime.lastError to { "message": "The message port closed before a response was received." }.

BTW one thing I did notice is that it seems that from
"compactTranslations":["朝、鳥の声がしました。","[あさ/朝][、/は][とり/鳥]が鳴いて[い/][ました/た]。","[あさ/朝][、/は][とり/鳥]の[こえ/声/鳴き声]が[しました/した]。","[あさ/朝][、/は][とり/鳥]が鳴[きました/いた]。"],
it generated 264 "accepted solutions" - it's not clear on what basis it decides to split them up.  But obviously it's using additional information as at least some of the listed accepted solutions used Japanese characters not in that list.

Why would an unresolved import cause that?

I'm not sure, but it's probably due to one of the Rollup plugins. Anyway, every time the build process hangs, it's because I forgot to npm i or to remove an obsolete import.

I can see now you're not using 'compactTranslations' at all, but the 'grader' information, which seems inordinately convoluted!

This seems to be especially true for solutions written in non-Latin alphabets, but so far it's been hard for me to figure out why / if it contains mostly irrelevant or redundant values / if there's anything we can do about it (I don't know or learn any of the corresponding languages) - your feedback would be very valuable here!
For example, I had not yet considered this until now, but would parsing the compactTranslations strings give solution lists that are sufficiently exhaustive? Knowing that this could be a perfect fallback for when a solution graph contains too many vertices.
Also, I remember finding "normalization data" in the localStorage, which seems to correspond to pairs of equivalent strings for non-Latin alphabets (again). Could most of the solutions actually correspond to different but equivalent combinations of (non-)normalized tokens?
You can run this code in the console if you want to take a look at it for Japanese e.g. :
JSON.parse(window.localStorage.getItem('duo.clientSideGradingConfig')).language_data['ja'].normalization_data;

BTW don't suppose you've figured out a way to detect the URL of the discussion page? Each exercise seems to have an ID associated with it but I can never find it searching with DevTools among any of the source/network traffic/console output etc.

The extension used to send requests to this URL (the same that is used when the "Discuss" button is clicked):
https://www.duolingo.com/sentence/[discussion_id]?learning_language=[locale]&ui_language=[locale]

in which discussion_id corresponds to the id value that can be found in the exercises, but to prevent being detected as a bot by the API, it now detects requests to this URL instead (used in forum comments):
https://forum-api.duolingo.com/comments/[comment_id]

knowing that it can then use the sentence_id (= discussion_id) and sentence_language from the result to find back the right exercise.

But that's my point, I can't find the discussion_id anywhere in DevTools etc when I search for the specific value.  I can see you have a reference to "discussion_id" in the code (const FIELD_DISCUSSION_ID = 'discussion_id'), so I'll try adding up some specific output to the console log.

Ok I get "commentId" logged out when I load the comments page.  In fact it seems Duo doesn't even know what the "commentId" is when showing an exercise in a lesson, but uses some sort of redirection mechanism to bring up the forum page, which I'm trying to work out (actually it's not working for me at all at the moment for some reason).

Which information do you have and what are you trying to find?

Actually I tried with Edge (which doesn't support the plugin obviously), and I can see from its network traffic that when it fetches https://www.duolingo.com/sentence/[discussion_id]?learning_language=[locale]&ui_language=[locale] the response does include the comment_id (in property id of the returned JSON object). Odd that searching network traffic doesn't find it though.

Basically I was just hoping to enhance the plugin to dump out useful summary information to the log about each lesson as I did it, and the forum discussion URL was one of the ones I definitely wanted, as often the "discuss" link doesn't even work.

BTW deleting the _pxhd cookie in Chrome solved the 502 issue, Discuss button is now working.

Interestingly if I click on the 'discuss' icon for an exercise that has no comments yet, it navigates to this URL instead:
https://www.duolingo.com/new-comment?fromLanguage=en&learningLanguage=ja&sentenceId=7ff8ee49b6b07b8976362d0c7052ae4e
Visible in the browser address bar.  And it seems there is no commentId assigned.


rsync processor cannot be used with a mix of short and long arguements e.g. -Phav --delete

Mixing short and long arguments results in an unrecognised argument error as the whole argument string is sent as one argument. This is mostly fine except if you need to use delete as there is no short argument for delete.

Fixed with 988332d3bb700b0e5c4231c16dfe39527c68a9a5.


New App Submission

App Logo (Required)

App Details (Required)
Type: Dapp
Name: BITPIF
Homepage Url: https://bitpif.com/
Chains supported: Ethereum
App Url (Required - at least one)
Browser Url: https://bitpif.com/
iOS Url:
Android Url:
Mac Url:
Windows Url:
Linux Url:
Mobile Linking (Optional)
Deep Link:
Universal Link: https://bitpif.com/
Desktop Linking (Optional)
Deep Link:
Universal Link: https://bitpif.com/
Metadata (Optional)
Short Name:
Primary Color:
Secondary Color:

Added on commit acb901a04ba401a0df54f59a117e48124bf38d21


Fixes #8: fixing lint tests in louis-crawler

issue #8

@melanie-fressard my request to you yesterday was to look into if these functions are separately tested in ailab-db, not so much to fix them because I'm already working on this in PR #4
close this PR and check if there is test coverage for these functions in ailab-db.

Just saw this, will do.
Corrected a few things (connection not closed, unused imports...)

For what I've seen, ailab-db test these functions :
link_pages, fetch_crawl, fetch_crawl_row, fetch-chunk_row, and fetch_chunk_id_without_embedding
the first 2 cover the same kind of tests as the file tests/test_goldie.py
Otherwise there is no coverage of louis-crawler in ailab-db

For what I've seen, ailab-db test these functions : link_pages, fetch_crawl, fetch_crawl_row, fetch-chunk_row, and fetch_chunk_id_without_embedding
the first 2 cover the same kind of tests as the file tests/test_goldie.py
Otherwise there is no coverage of louis-crawler in ailab-db

So we do need to test all functions within the ailab-db package as we also need to make sure these functions are maintained when we make breaking changes to the schema.
Commenting out tests is not a fix,  to help out here you can check you can develop your own test suite within ailab-db to preserve the function contract but update the implementation to work with the updated schema. Keeping in mind that we want to match the ailab-db Python versions functions with the schema.

For what I've seen, ailab-db test these functions : link_pages, fetch_crawl, fetch_crawl_row, fetch-chunk_row, and fetch_chunk_id_without_embedding
the first 2 cover the same kind of tests as the file tests/test_goldie.py
Otherwise there is no coverage of louis-crawler in ailab-db

So we do need to test all functions within the ailab-db package as we also need to make sure these functions are maintained when we make breaking changes to the schema.
Commenting out tests is not a fix, to help out here you can check you can develop your own test suite within ailab-db to preserve the function contract but update the implementation to work with the updated schema. Keeping in mind that we want to match the ailab-db Python versions functions with the schema.

So am I supposed to close this PR or do I still work on it to provide new tests instead of the one I commented out ?
Also, I will create a new PR on ailab-db to update tests regarding new schema, is it correct ?

So am I supposed to close this PR or do I still work on it to provide new tests instead of the one I commented out ?

Yes, close this one.

Also, I will create a new PR on ailab-db to update tests regarding new schema, is it correct ?

Yes.

As discussed, will create a PR on ailab-db that will address test coverage for crawler functions.


UI Glitch - Request Money Screen

https://cdn.discordapp.com/attachments/899274784720977920/916395668657037312/RPReplay_Final1638556046.mov

That's implemented as well.


xsimd: 7.5.0 -> 8.1.0

Description of changes
Update the package.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg build arrow-cpp

I noticed that the arrow package doesn't use this xsimd any more, so no need to wait for that build.
nixpkgs-review successfully built python310Packages.xtensor-python python39Packages.xtensor-python xsimd xtensor.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1129

Can you take a look at the Darwin build failures?

Filed https://github.com/xtensor-stack/xsimd/issues/807 . It looks like similar tests were already failing on macOS and is manually disabled, let's wait a little bit to see if we should also disable the newly failed test cases in 8.1.0

Disabled the problematic test suite (which is already failing in earlier versions), now this PR should be good to merge

@tobim can you take another look?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1149


nl folder contains 3 files incomplete

Need to check each of 3 files & update as needed:
https://github.com/hotosm/learnosm/blob/gh-pages/_posts/nl/0200-12-30-BeginnenmetOSM.md
https://github.com/hotosm/learnosm/blob/gh-pages/_posts/nl/0200-12-31-IntroductieinOpenStreetMap.md
https://github.com/hotosm/learnosm/blob/gh-pages/_posts/nl/0200-12-29-GettingStartedWithJOSM.md
The pull request on these reads ' add 3 chapters in dutch (not live since the content is not completely…
… translated); minor change in language for front and beginner intr
This is from February 2013
It would be good for these to be assessed & perhaps the nederlands section of the site could then go live. Seems a pity they have sat here unused all this time

cleaning up old issues which had been solved in the meantime
the Dutch part of the website is active


cpp-hocon: 0.2.2 -> 0.3.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/puppetlabs/cpp-hocon/releases.
meta.description for cpp-hocon is: " A C++ port of the Typesafe Config library"
meta.homepage for cpp-hocon is: "https://github.com/puppetlabs/cpp-hocon"
meta.changelog for cpp-hocon is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.3.0 with grep in /nix/store/9vxyqhd35rmdpmwz8bpxvikq5a0n00wl-cpp-hocon-0.3.0

directory tree listing: https://gist.github.com/833fdc6a98056600e93b3833275da8a8

du listing: https://gist.github.com/d23251851a0f9b458d2ef6fa3dacae17

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cpp-hocon
facter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9vxyqhd35rmdpmwz8bpxvikq5a0n00wl-cpp-hocon-0.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cpp-hocon https://github.com/r-ryantm/nixpkgs/archive/c271dab10a5e10a23002be62395a0aa2feca9418.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9vxyqhd35rmdpmwz8bpxvikq5a0n00wl-cpp-hocon-0.3.0
ls -la /nix/store/9vxyqhd35rmdpmwz8bpxvikq5a0n00wl-cpp-hocon-0.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

2 packages built:
- cpp-hocon
- facter

Maintainer pings
cc @womfoo for testing.

@GrahamcOfBorg build facter


Fix imports

Thank you for the template.
Really helped me getting started.
I have imported the sass folder into a dummy Jekyll and the compiler displayed some warning about imports.
Seems to behave the same when compiling it with vite.

Hi, @erizo-dev! Happy to hear that it helped! I will take a look what seems to be the problem, and hopefully fix it in a few days.


Add necessary changes for conda build x86_64 including support for DALI TF plugin

Signed-off-by: Joaquin Anton<EMAIL_ADDRESS>

@aalugore Could you please merge this PR so that it appears in your DALI PR? Thanks


Remove brittle unit-test.

The removed test only checks if certain substrings are present. The golden testing automatically adds these tests for any usecase. Therefore, this test is not needed anymore.
The usecase for implementing non-specific current, will add a version of a passive current; and test the values against the analytical reference.
Ions are already covered by the ionic usecase.
Array variables are covered by the cnexp_array usecase.
Parameters coved by the parameters usecase.
Simple ODEs are covered by cnexp_* usecases.

While developing NRN support in NMODL, these tests are very annoying. I can never find the difference; and it's completely redundant with #1131.


Add admin command to truncate pulsar topics (partitions)

requirement: set infinite retention on a namespace and then manually truncate the topic.

truncate the topic by message id
delete all the messages older than time X

@sijie its kinda put an expired tag on one message or lot of message directly?

After discussing with @sijie #9514 is not implementing what we want here, we want to able to truncate the topic which is actually delete ledger from BK for given topic.
Should reopen it.

I can work on a solution for it.

related to https://github.com/apache/pulsar/issues/9597


[Dockerized Jenkins] Fix build of dockerized jenkins (fixes #24053)

Most recent Jenkins images (jenkins/jenkins:lts) do not contain install-plugins.sh anymore, causing the build to fail.
 > [3/9] RUN /usr/local/bin/install-plugins.sh < /usr/share/jenkins/ref/plugins.txt:
#5 0.195 WARN: install-plugins.sh has been removed, please switch to jenkins-plugin-cli

The lastest image I was able to use without changing the Dockerfile is jenkins/jenkins:2.346.1-lts
See https://github.com/jenkinsci/docker/blob/master/README.md#usage-1 for how to use jenkins-plugin-cli:
RUN jenkins-plugin-cli -f /usr/share/jenkins/ref/plugins.txt

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @lgajowy

R: @damccorm


The fence code between two pictures cannot be displayed

Describe the bug
The fence code between two pictures cannot be displayed on the Google Chrome browser.
The content of the markdown is as follows.

123
456
789

===========================================================

Reproduction
N/A
System Info
valxy 0.16.3
pnpm 8.14.0
git 2.14.3
firefox 115.6.0esr
chrome 120.0.6099.131

Used Package Manager
pnpm
Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

This is a very interesting case.
After you remove the float: left of the image, it should display normally.

I recommend you use the grammar of markdown: ![image](https://xxx) to display image.

If you want to align left img tag, you can write like this:
<img src='https://yunyoujun.cn/images/avatar.jpg' alt="image" class="m-unset!">

m-unset! will unset default margin. (align center)

Because float behaves differently in chrome and firefox. I think it might be a browser bug.
I don‘t have some solutions at the framework level.


Demo: Use same C++ standard as cxxbridge

The demo code is currently set up to set the C++ standard by setting it in build.rs a la
    cxx_build::bridge("src/main.rs")
        .file("src/demo.cc")
        .flag_if_supported("-std=c++14")
        .compile("cxxbridge-demo");

However, cxx.h|cc are compiled with the CXX crate feature settings, i.e. cxxbridge_flags::STD. ffi tests already use the feature flag.
We shall align the demo's build.rs to use cxxbridge_flags::STD so that we only have to declare the feature in demo's Cargo.toml.
While we're at it, it would be great to not having to set flag_if_supported(cxxbridge_flags::STD) when using cxx_build. cxx_build could directly set the feature flags. This makes the cxx_build usage less error-prone for cargo-based builds as it automatically ensures that custom FFI code and cxx.h|cc is compiled with the same features. Especially once we add C++17 features such as string_view support, or any other potential future feature such as absl, folly, or gsl support.
This is not an issue for bazel or buck builds.
Pull request incoming.

@dtolnay Just to double check. Was expecting to see this issue closed with "not at this time" due to the outcome of PR #324.
Oversight, or would you like a pull request that does the change in demo's build.rs to?
 cxx_build::bridge("src/main.rs")
        .file("src/demo.cc")
        .flag_if_supported(cxxbridge_flags::STD)
        .compile("cxxbridge-demo");

I would prefer not to do this at this time, so I'll go ahead and close the issue. Thanks anyway!


URLSearchParams for QS parsing

Fixes  #21841
Internal Review Topic (links to section)

@guardrex thanks for updating this.
If I might suggest a "more involved" approach (but a bit cleaner).
QueryString.js
export createQueryString = (string queryString) => new URLSearchParams(queryString);

QueryStringUtils.cs
ValueTask<IJSObjectReference> CreateQueryString(string queryString)
{
  await EnsureInitialized();
  await Module.InvokeAsync("createQuerystring", queryString);
}

async ValueTask EnsureInitialized()
{
  Module = await JSRuntime.InvokeAsync<IJSObjectReference>("import", "QueryString.js");
}

And then they can do whatever they want with the instance

The advanced (more involved) approach is covered at ...
https://docs.microsoft.com/en-us/aspnet/core/blazor/call-javascript-from-dotnet?view=aspnetcore-5.0#blazor-javascript-isolation-and-object-references
... and isn't really necessary to tell devs how to parse qs values. I recommend that we don't pollute the content :smile:. I think we just need to tell them what to do here for qs parsing and cross-link.
btw - The JS interop topics haven't been reached on the UE passes yet. There will be a lot of nice content and example updates to those topics when I reach them, including that section :point_up:. I hope to reach them within a few weeks 🤞🍀.

Ignore the 🤖 Cyberdyne Systems Snippet Builder 5000™ 🤖 choking 💥. It doesn't pertain to this PR, and I'll fix it separately.


ClassMetadataInfo uses deprecated doctrine/common class

BC Break Report

Q
A

BC Break
yes

Version
2.6.2

Summary
After upgrading to 2.6.2, which included an upgrade to doctrine/common:2.9.0, PHPUnit now fails with:
  1x: Doctrine\Common\ClassLoader is deprecated.
Previous behavior
No deprecation errors were shown from using non-deprecated methods
Current behavior
Doctrine\Common\ClassLoader is deprecated
/Users/simon/projects/stokl/backend/vendor/doctrine/common/lib/Doctrine/Common/ClassLoader.php:7
/Users/simon/projects/stokl/backend/vendor/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataInfo.php:1028
/Users/simon/projects/stokl/backend/vendor/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php:266
/Users/simon/projects/stokl/backend/vendor/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php:245
/Users/simon/projects/stokl/backend/vendor/doctrine/persistence/lib/Doctrine/Common/Persistence/Mapping/AbstractClassMetadataFactory.php:305
/Users/simon/projects/stokl/backend/vendor/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php:78
/Users/simon/projects/stokl/backend/vendor/doctrine/persistence/lib/Doctrine/Common/Persistence/Mapping/AbstractClassMetadataFactory.php:183
/Users/simon/projects/stokl/backend/vendor/doctrine/persistence/lib/Doctrine/Common/Persistence/Mapping/AbstractClassMetadataFactory.php:89

How to reproduce
This is from in a test case in a Symfony application
    $entityManager =
      $kernel->getContainer()->get('doctrine.orm.entity_manager');

    $metadatas = $entityManager->getMetadataFactory()->getAllMetadata();

Hi,
thanks for a prompt testing of 2.6.2! Here's a quick fix: #7307
Note that the deprecations in doctrine/common are silent (using @) so nothing is really broken - your tests are explicitly using an unsilencer.
Your tests should be using weak_vendors mode for the Symfony's PHPUnit listener to ignore deprecations coming from vendor/ (those not triggered by your code). Otherwise your tests may start failing unexpectedly anytime and you won't be able to fix them as the code in question is out of scope.
Given the above, I am not convinced this would justify a 2.6.3 hotfix release. @Ocramius your thoughts?

I was not aware of that option. Certainly makes this less urgent! Thanks for telling me about it :)

How would you silence the deprecation in the Symfony WDT?

It shouldn't be triggered in first place, vendor deprecations are not fault of your code and should be ignored. If this is the default behavior of Symfony WDT, then it's wrong behavior.
Either way this issue isn't the appropriate place to discuss configuration of Symfony or related issues. See https://github.com/symfony/symfony/issues/27936.

Closing here as resolved, fix will be released in 2.6.3.


Merge pull requests or just state this is abandoned in the README.md

People are doing pull requests, but you are just plainly ignoring everything. Which is fine, but right now your dependencies are broken. If you are not going fix this, just tell the world you are not maintaining this module so people wont waste time on this.

It's fine for anyone to ignore pull requests, issues, comments, etc.. It would be nice if the README explicitly stated that the project is no longer being actively maintained, but that's fairly obvious given the evidence (of no recent activity).
For anyone interested, there are several forks for this project:

Network Graph · marcelog/logger_logstash_backend

Many include new commits to update dependencies, some remove Timex completely, among other potentially interesting or useful changes.

Here's a fork that's published on Hex and includes several changes:

prima_logger_logstash_backend | Hex


Default templates

Edit, preview, set as default, delete and clone to other voucher template, Add new options for,

[x] Estimates (standard  English and Arabic)
[x] Sales order (standard, grand)
[x] Delivery challans (Standard template)
[x] Invoices (Retail invoices, standard E-invoice, Standard templates, Standard Arabic e- invoice templates,  standard Arabic template, simplified templates)
[x] Sales return ( standard templates(English, Arabic), Simplified E-invoices, Standard E-invoices)
[x] Purchase order (Standard templates)
[x] Retainer Invoices (Standard templates)
[x] Payment receipts (elite templates) clone function only to Retainer payment receipts
[x] Retainer payment receipts (elite templates) clone function only to payment receipts
[x] Customer statements (standard templates)- only need edit, preview options
[x] Bills (Standard templates (English and Arabic)) In self billed invoices- (standard invoices)
[x] Vendor credits (Standard templates)- only need edit, preview options
[x] Vendor payments (Elite- only edit options)
[x] Vendor statements (Standard- only edit options)
[x] Journals (Standard- only edit options)
[x] Quantity adjustments (Standard- only edit options)
[x] Value adjustments (Standard- only edit options)

For first release

[x] Estimates (fields like Zoho)
[x] Sales order (field like standard Zoho)
[x] Delivery challans (field like standard Zoho)
[x] Retail and standard templates (fields like Zoho)
[x] Sales return,invoice standard template (fields like zoho) 💯
[x] Purchase order (fields like zoho)
[x] Retainer invoices (fields like zoho)
[x] Payment receipts, vendor payment and retainer payment receipts ( you can create any custom templates)
[x] Customer Statement, vendor statements (modifications)
[x] Bill, vendor credits standard (fields like zoho) 💯
[ ]

Completed


Different sizes of sidebar buttons

Hello developers, it would be interesting to implement the option to shrink the buttons on the side configuration tab. It could add an optional method where you would have some options like: big, medium, small, extra small. This function would not only be aesthetic, but for those who, like me, work with two open codes, would gain a few more pixels of space in the development area.
functions that are available through extensions such as Open In Browser or Live Server could be added as a fixed feature of Visiual Studio.

Please upvote https://github.com/microsoft/vscode/issues/82996


Add ability to setup redirects from within an Amplify project

Is your feature request related to a problem? Please describe.
AWS Amplify framework offers a clean way to store all the frontend and backend settings and code in one place: the git repo of a project.
Deploying the project with the AWS Amplify console should not break that pattern.
When a project requires redirects this redirect cannot be defined from within the project but only added manually (or declared in CloudFormation using a distinct source code repository).
This is a pain when working with multiple environment and team (with many Amplify env) because everyone needs to manually add the redirect and edit the redirect when there is a change.
Describe the solution you'd like
I like to have a file somewhere in an AWS Amplify project that the Amplify Console read to setup redirect rules.
Additional context
This is a bit sad, because when you deploy with the AWS Amplify CLI to a hosting S3AndCloudfront you don't have the problem. You can declare your redirections in the behavior of the Cloudfront distribution in the hosting CloudFormation files.
Since AWS AMplify console do not use hosting S3AndCloudfront definition, these settings are lost.

@xavierraffin this is on our roadmap to support this year. Please track #18. Closing this as a dupe.


:bug: No Task Customization for Sending Tasks Under Linux

Hello, thank you for developing :heart:
Under Ubuntu 20.04 LogSeq v0.8.11
My JSON settings are:
{   "apiToken": "916e3b2d821b18d15366563a9538b1303aeeec79",   "pullDefaultProject": "---",   "pullDefaultAppend": true,   "addParentBlock": true,   "clearTasks": false,   "sendDefaultProject": "---",   "sendDefaultDeadline": false,   "sendDefaultLabel": "---",   "appendLogseqUri": "Link description",   "appendTodoistUrl": "Append link",   "appOrWebLink": "WebLink",   "disabled": false }
When I attempt to send tasks, there is no pop-up window asking for the due date, project, priority.
I have tested this with the same settings on LogSeq v<IP_ADDRESS> under Windows and it works correctly as expected there, just not working with Ubuntu.
Thanks again.

Same thing is happening with Todoist on Windows 11.

Uninstalling and reinstalling the plugin worked for me...However, now the plugin is rejecting my API key, even though I can confirm I can pull information using the key with a curl command.

OK, with release of plugin 4.4.3. reinstall, the API is recognized again and the pop-up menu is back. Thanks @hkgnp !!!!

Wow that's fast! Sounds great!


Use SPDX license identifier

Use the SPDX license identifier for Apache-2.0 instead of the whole license file inside the project metadata. This will make it easier to correctly identify the project license. See also PEP-639 which is close to being finalized.
https://spdx.org/licenses/
https://github.com/home-assistant-libs/zwave-js-server-python/blob/11652fd1045661d6e0485cb78437084d22e49a07/LICENSE#L1-L3

Use the SPDX license identifier for GPL-2.0-or-later

We use Apache 2.0.

Use the SPDX license identifier for GPL-2.0-or-later

We use Apache 2.0.

Sorry, copy-paste error in the PR description. The file change is correct though.

How compatible is this with our current license validation in Home Assistant core? I know there was some work done already to replace the text variable with classifies in 3rd party libraries.

How compatible is this with our current license validation in Home Assistant core?

It's fully compatible. The current implementation just looks for "Apache License" and similar (which is obviously part of the full license text) but it also checks the SPDX identifier "Apache-2.0".
I found this as part of an effort to improve the license check in Core. See https://github.com/home-assistant/core/pull/123119 for details.

I know there was some work done already to replace the text variable with classifiers in 3rd party libraries.

That was a mistake IMO. License classifier have several shortcomings compared to full license expressions so I believe the latter will be the future, especially with PEP 639 finally being finalized after such a long time.
Anyway, I don't yet plan on updating opening PRs in other projects, besides this one. I'd appreciate your feedback on https://github.com/home-assistant/core/pull/123119. Maybe we can discuss it there further if there are open questions?

License SPDX identifiers sounds good. But until the PEP is accepted I don't think we should try to change libraries in one way or the other. I think we should try to be as forgiving as possible in our core license validation. If we can detect a valid open source license that's enough and we shouldn't try to nudge libraries until there's a clear path forward as stipulated by the PEP.

License SPDX identifiers sounds good. But until the PEP is accepted I don't think we should try to change libraries in one way or the other.

The current status https://discuss.python.org/t/pep-639-round-3-improving-license-clarity-with-better-package-metadata/53020/80 from the PEP-Delegate. They are only discussing one last implementation detail around the supported glob syntax for license-files. Everything else looks good.

we shouldn't try to nudge libraries until there's a clear path forward as stipulated by the PEP.

I'd slightly disagree here. For example, as mentioned in https://github.com/home-assistant/core/pull/123119, poetry will auto-add the Other/Proprietary License license classifier if no valid SPDX license is detected. Just from looking at the classifiers alone it isn't clear what the intent here would be ['Apache Software License', 'Other/Proprietary License'].
As mentioned, I won't go around opening PRs for it. However, I still think this particular one is still fine to merge as is 😄

PEP 639 has been provisionally accepted. It'll still take some time before the build backends fully support it though. However, changing the license text to the SPDX identifier should be fine now. Saw you also merged a similar PR in another project: https://github.com/MartinHjelmare/aiovlc/pull/268

That project is using poetry which documents that the SPDX identifiers should be used for the license field. I think we should wait until the PEP is fully accepted until we move forward here.

That project is using poetry which documents that the SPDX identifiers should be used for the license field.

BTW: Both (poetry and setuptools) output to the same project metadata field: License-Metadata.

The setuptools documentation doesn't clarify what way to identify the license is preferred and the Python Packaging User Guide prefers the classifiers. Until this is spelled out better (accepting the PEP will do that), we should wait.


Fix - String Interpolation Leaks

This PR fixes memory leaks that were occurring in the string interpolation for the description and debugDescription implementations in the Timeline struct. None of these changes "should" be necessary, but unfortunately are at the moment. The main change was to switch over from string interpolation to string concatenation. I've been debugging with the sample project provided in #1232 and everything seems to be resolved with these changes.

👍
Though, perhaps make a TODO or otherwise indicate that the code should be moved back to interpolation when the leaks are fixed. Also, was there a bug filed with Apple for this issue? Radar or Swift project would work.

I agree @jshier. I put together the Rdar-StringInterpolationMemoryLeak project and filed rdar://26761490 with Apple. I also added NOTEs to the code and added the rdar to the README in 6c1cbdd7.


Python-etcd does not like keyword arguments

This fixes a current FV failure.

LGTM.  Any adjustment we can make to the UTs to catch future versions of this bug?  I think we mock out the client so presumably we can set the signature of the write method.

@fasaxc I've added a UT catch as well.


Mobile responsive input[type=date] support phone

Please see https://github.com/niftylettuce/bootstrap-datepicker-mobile.  We should document this on the ReadMeDocs maybe?

In order to be compatible with the html5 native datepicker, it has to submit the date in yyyy-mm-dd format...could we possibly modify it prior to submit, or provide an option (inputFormat, submitFormat)?
It would be super helpful if this datepicker knew when it should be used as a fallback...

:+1: for providing a format option + fallback to input type date for mobile devices.

@PrplHaz4  @korun @acrobat @AlexVPopov Want to bring up a point that iOS Safari seems to not support min and max attributes for  type=date.  So for date range picking, it's not going to work.


Suggestion: Have You Considered Comparing Moxin-LLM with CT-LLM and MAP-Neo?

Dear Moxin-LLM Team,
I hope this message finds you well. Your contributions are highly valuable to the community, and I appreciate the effort you have put into this project.
I was wondering if you have considered comparing your model to other similar works such as MAP-Neo and CT-LLM. These models, like yours, contribute precious training resources to the open-source bilingual language model community. A comparison could provide interesting insights and further highlight the strengths of your model.
Thank you once again for your outstanding contributions. I look forward to seeing your future advancements in this area.
MAP-Neo: MAP-Neo (map-neo.github.io)
CT-LLM: Chinese Tiny LLM (chinese-tiny-llm.github.io)
Best regards,
M-A-P Team

Many thanks for the suggestions. We will look into this.


[Feature Request]: Specify pipx version

Requested Feature
Given the application scenario of devcontainers, it should be possible to create identical environments from the same json file, so specifying the version of pipx should bring this goal one step closer, which will avoid upstream software compatibility modifications that would break devcontainers, like this https://github.com/pypa/pipx/issues/1444

This project is not associated with the devcontainer project and appears to have been abandoned https://github.com/devcontainers-contrib/features/issues/628 . The official project has removed all devcontainer-contrib features from their listing. https://github.com/devcontainers/devcontainers.github.io/issues/451. There is a fork that is being worked on to update and maintain the features https://github.com/devcontainers-extra/features


Flag for right join of the -c list

We have the --intersection flag which gives us the intersection between  the -c (compared) list and the -m (main) list.

It would be cool to have a flag to give us what the -c (compared) list contains that the -m (main) list does not.

Presently this is what we have:
$ ./ghosts -c https://raw.githubusercontent.com/AdAway/adaway.github.io/master/hosts.txt -unique
----------------------------------------
Base hosts file summary:
----------------------------------------
Location: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
Domains: 76,464
Bytes: 2.3 MB
----------------------------------------
----------------------------------------
Compared hosts file summary:
----------------------------------------
Location: https://raw.githubusercontent.com/AdAway/adaway.github.io/master/hosts.txt
Domains: 8,774
Bytes: 320 kB
----------------------------------------
Intersection: 8,722 domains
unique in comparison list: [8272590.fls.doubleclick.net ....SNIP.... wizzogames-sdk.wappier.com]

Which, cosmetics aside, is perfect.

Closing!


CrMi measure isSymmetric() method needs improving

I.e:
    @Override
    public boolean isSymmetric() {
        // TODO: This rather depends on the parameterisation
        return false;
    }

Fixed as of commit 32e9371


Fix InhibitIPv4 nil panic

- What I did
When I upgrade the docker of my laptop from 19.03 to the latest master branch, docker.service startup failed with panic:
Feb 27 01:44:56 localhost systemd: Starting Docker Application Container Engine...
Feb 27 01:44:57 localhost dockerd: panic: interface conversion: interface {} is nil, not bool
Feb 27 01:44:57 localhost dockerd: goroutine 1 [running]:
Feb 27 01:44:57 localhost dockerd: github.com/docker/docker/vendor/github.com/docker/libnetwork/drivers/bridge.(*networkConfiguration).UnmarshalJSON(0xc0006ee410, 0xc00097b1e0, 0x189, 0x189, 0x7f9979d15510, 0xc0006ee410)
Feb 27 01:44:57 localhost dockerd: /go/src/github.com/docker/docker/vendor/github.com/docker/libnetwork/drivers/bridge/bridge_store.go:201 +0xb9a
Feb 27 01:44:57 localhost dockerd: encoding/json.(*decodeState).object(0xc000c2b550, 0x55f9eff967c0, 0xc0006ee410, 0x16, 0xc000c2b578, 0xc00051537b)
Feb 27 01:44:57 localhost dockerd: /usr/local/go/src/encoding/json/decode.go:667 +0x220d

and this PR will fix it.
- How I did it
There is no "InhibitIPv4" field in the json string of Bridge before PR #2317, so I just add a nil check before the type cast

@arkodg pls ignore the second review request, mistake 😭

I see the related change is only on master, so  no need to backport to 18.09 or 19.03