Make updates for Linux

I spoke to @sgoggins about make install-dev on Linux. I only have the first change so far, but there are 2 more outstanding issues I want to address.
The first is installing it in a Python venv. In this case the venv takes over pip for one version of python, but make install-dev tries to install dependencies for both Python 2 & 3. Should this be addressed via separate build targets for Python 2 & 3 or is there a way of determining if python is running inside venv.
The second issue is npm install -g apidoc brunch yarn. This command requires root permission to run, which should be avoided ideally. My current solution is to omit the -g flag, installing the modules locally, but they don't appear on the path and can't be run as easily. I don't have an elegant solution for that particular problem.

Thanks!


How to start with image processing...

https://keras.io/examples/
https://docs.opencv.org/4.x/d2/d96/tutorial_py_table_of_contents_imgproc.html
https://www.tensorflow.org/tutorials/load_data/images
https://www.tensorflow.org/tensorboard/get_started
https://scikit-learn.org/stable/index.html
https://scikit-learn.org/stable/auto_examples/index.html

@cluedeke last 2 links in my opinion also interesting for you


Bump express to pick up path-to-regex

closes https://github.com/FlowFuse/node-red-dashboard/security/dependabot/47
Description

fixes dependency
Related Issue(s)

https://github.com/FlowFuse/node-red-dashboard/security/dependabot/47

There may be a follow up fix when NR pushes a new version


fix: ignore case when inferring file extension from codeSample lang prop

What/Why/How?
What
Ignore case when inferring file extension from codeSample lang property.
Why
Considering the following x-codeSamples operation definition:
@oas [get] /foobar
x-codeSamples:
  - lang: JavaScript
    source: |
       const foo = 'bar';

When establishing the sampleFileName, x-codeSample.lang is used to infer the file extension. The above will yield a filename getundefined since JavaScript is not lowercase.
How
The method langToExt shall convert lang to lowercase before attempting to infer the file extension against its map of known languages.
langToExt has been moved to utils to simplify unit testing.
Reference
sampleFineName
https://github.com/Redocly/redocly-cli/blob/4dc87c3f1820b0b21000708f53aa088afc99c3c8/packages/cli/src/commands/split/index.ts#L306-L312
langToExt
https://github.com/Redocly/redocly-cli/blob/4dc87c3f1820b0b21000708f53aa088afc99c3c8/packages/cli/src/commands/split/index.ts#L109-L121
Testing
Added unit testing around langToExt method.
Screenshots (optional)
n/a
Check yourself

[x] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[x] All new/updated code is covered with tests

Security

[x] Security impact of change has been considered

no impact

[x] Code follows company security practices and guidelines

Hi @patrick-medusajs,
Thanks for your contribution!
Will be published in the next release.

@AntonKozachuk, thank you for reviewing the PR.
Cheers!


Focus not on the ground?

Hi again! I'm trying to implement custom controls for my camera and for that I need to know where the camera is pointing at on the ground. My understanding was that the focus or target_focus contain this information, but when reading those properties I'm getting a point high above the ground (large y coordinate), even if I manually set the target focus to be at y = 0.0. It also changes when zoom is changed. I think it basically contains the current camera height. Is this intentional? Could you please advise how to get the coordinates on the ground?
My naive way of doing that is as follows, but it doesn't account for any ground topology.
let ground_focus = camera.focus.translation.xz().extend(0.0).xzy();

Hi! You're correct that the target_focus is automatically adjusted and reflect the camera's height. I'll need to think about this a bit more but a hacky way to get the actual focal point is to reverse engineer it by subtracting cam.height_max.lerp(cam.height_min, cam.target_zoom) from the Y coordinate of focus or target_focus. (That's the value added to the ground surface in order to follow the ground.)

I have pushed 0.4.2 which contains https://github.com/Plonq/bevy_rts_camera/pull/8. focus now isn't moved up to the camera's height and you can use it directly instead of subtracting the height from it.


Update to Ember 3.6

run ember-cli-update --to 3.6.0
move  ESLint config of node-tests into root config file
fix ESLint errors

This PR contains bump of ember-cli-babel from ^6.6.0 to ^7.1.2, which is a 💥 breaking change.
So the next release of ember-web-app will be a major bump.


Http2 push on sample app not working ?

I'm trying the sample app https://http2-push.appspot.com/ using Chromne Version 51.0.2704.103 (64-bit) on Ubuntu.
Although the Link header is present seems that nothing is being pushed.
I only see "quic/1+spdy/3" instead "h2".

This is a known issue with chromen atm. It's defaulting to the quic
protocol which doesn't yet support push. That'll be fixed soon.
On Wed, Jun 22, 2016, 5:57 AM Fábio Franco Uechi<EMAIL_ADDRESS>wrote:

I'm trying the sample app https://http2-push.appspot.com/ using Chromne
Version 51.0.2704.103 (64-bit) on Ubuntu.
Although the Link header is present seems that nothing is being pushed.
I only see "quic/1+spdy/3" instead "h2".
[image: http2-push-fail]
https://cloud.githubusercontent.com/assets/308613/16254237/335c689c-3814-11e6-91a7-2c0429cc84a9.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/http2push-gae/issues/20, or mute the
thread
https://github.com/notifications/unsubscribe/AAOigNDGMXN8ilKr0ug8iBlHNuUs8eesks5qOLKfgaJpZM4I7Yob
.

Weird, on another webapp also running on GAE assets are being pushed normally.

@ebidel  Any updates on this issue? Our team is trying to implement the PRPL pattern with a GAE server, and this is the only module that we know that enables HTTP2 Push

I believe the goal was to get quic + h2 push working this quarter, but now update (yet) on the GAE side of things.

@ciampo you don't need this module to do h2 push on GAE. That's a feature that the core service supports. Just construct the link preload header. All this module does is enable an easier way to construct that header and annotate server endpoints.

Right - so if I understand this correctly, this module makes it easier to implement server push on GAE, but we're waiting for the Google Cloud team to implement server push fully?

Google Cloud team to implement server push fully

It should be everywhere on Google's infrastructure. What service are you using that you're not seeing pushed results?

We're using standard Google App Engine, along with setting the link http header to set the pushed resources.
What I'm expecting is something similar to the Polymer Shop application (although this is running on Apache I believe):

Where as this is what we see on the demo page: (We're seeing the same results on our application).

Is this caused by the initial answer to this thread where push is not supported by QUIC in chrome at the moment? If so, is there any ETA on when this might be fixed?

Ah yes, that's https://github.com/GoogleChrome/http2push-gae/issues/20#issuecomment-227648157. It's supposed to be fixed this quarter :\ I believe https://bugs.chromium.org/p/chromium/issues/detail?id=622043 is the issue to follow. FWIW, I'm seeing "h2" request on that demo page, not quic.

Ah I see, thanks for your response @ebidel. It's interesting that you're getting h2 on that demo, whereas we're getting QUIC, I'm seeing this in canary too.
Hopefully a fix will come soon!

It's possible Chrome is still running experiments for different users. You can change the behavior in about:flags to enable/disable it. Mine is set to "default" in stable.

Yeah my settings in about:flags are also set to default too.
In the meantime, we've found it quite difficult to see if resources are being pushed to the front end outside Chrome, other than looking at the headers. Other browser dev tools don't seem to include it, or if they do, they keep it well hidden!
We came across a node module that Surma wrote, which reports the resources that are pushed. It's worked out nicely, if anybody else needs to check if they have their server pushing files correctly 👍

Take a look at chrome://net-internals/#http2 to very what push promises are being recv'd and accepted.

I still have this issue on my chromebook. Had to disable QUIC manually.

@ebidel I still have this issue as well.
https://bugs.chromium.org/p/chromium/issues/detail?id=622043 is fixed but Push / foo still does not show up in DevTools.
Do you know who we can ping?
cc @Deleplace

What do you see on https://shop.polymer-project.org/? I see h2 requests.
@paulirish might know from the Devtools side.

I also see h2 requests for https://shop.polymer-project.org/.

However for https://http2-push.appspot.com/ I see http/2+quic/44 requests without `Push / ...'


is.requiredAtLevel Trait Missing

I'm am testing against a local copy of CDM 1.6, with the updated java maven pom.xml for the 1.6 version.
Review is limited to the applicationCommon->foundation->crmCommon->CustomerInsights->segment.cdm.json file.
For the segmentId field, the is.requiredAtLevel trait is not present.
The current CDM Entity Navigator on GitHub (shows as version 1.3 under Resolved tab) shows the segmentId field with the is.requiredAtLevel trait specified as systemrequired.
I checked the 1.3 and 1.3.1 schema files, and the trait was not specified there as well.
Is this trait inferred from the entity type or other CDM references?
Thanks

Hello @cashel1,
during resolution the CDM SDK converts the references and applies the traits that comes from them on the attribute.
The segmentId attribute has a purpose identifiedBy from which the trait is.requiredAtLevel comes from.
Marking an attribute as with purpose identifiedBy means that that attribute is a kind of primary key of an entity so it's value is always required.

Need to double back here.  Forgot to update the client apis from elastic to open.


Can't open any file

Hello,
I was trying out your extension and I found out that clicking on a file doesn't open it in the editor. Also, the right-click doesn't show the contextual menu.
Is this expected behavior?

Hi
Thanks for reporting this issue.
I fixed the issue of clicking a file does not open it in the editor. Please upgrade the extension to 1.2.1 and give it a try. Let me know if it works for you. Thanks!
Context menu is not supported.


Modal with FloatingFocusManager and no autoFocus scrolling to top of page

Describe the bug
I'm using FloatingFocusManager with nothing on my modal that has autoFocus, yet the page scrolls to the top when the modal is opened—and scrolls back down when the modal is closed.
To Reproduce
I'm sorry that I cannot reproduce the problem in a codesandbox, but I'm sharing links to my code (hopefully the next best thing):

Here is my Modal component
And here is an example of how a component renders an instance of my Modal

Expected behavior
The page does not scroll when my Modal is opened
Video
https://github.com/floating-ui/floating-ui/assets/1420644/2cc5bc0e-3089-4be6-a3bb-608a079b0659
Context:

OS: macOS Sonoma 14.3
Browser: Brave
Version: @floating-ui/react v0.25.4

Additional context
I thought maybe it had something to do with conditionally rendering my modals from outside, but I tried moving the isOpen state management inside the modal with useState() but it didn't make a difference.

Version: @floating-ui/react v0.25.4

This is a bit old. What about the latest 0.26.13?
The lockScroll on FloatingOverlay could be a problem. What happens if it's removed? Without a minimal reproduction, it's hard to debug this though.

I updated to 0.26.13 and the problem persists. I've been able to track it down to either lockScroll or this CSS:
html, body {
  height: 100%;
}

The problem goes away if I either comment that CSS out, or remove lockScroll. Unfortunately I still can't reproduce it in a code sandbox because my project is so complex.

I just figured out the true problem:
html {
  overflow-y: scroll;
}

The sad part is that I have no idea why I ever added that (it was lurking at the bottom of my global CSS file). 🤦♂
Sorry for wasting your time, but if someone else runs into this hopefully they can learn from my mistake.

FWIW, I was able to reproduce it in this code sandbox:
https://codesandbox.io/p/sandbox/floating-ui-react-dom-template-forked-46xcfw?file=%2Fsrc%2Fstyles.css%3A2%2C5

It's probably good to mention this potential issue under a Troubleshooting section for FloatingOverlay docs then 👍

I quickly discovered why I had added that CSS! It prevents layout shift in scenarios like these:

A page goes from loading, where no scrollbar is present, to showing enough content that a scrollbar appears (see this example from Josh Comeau)
You simply navigate from a page in your app that has no scrollbar (not much content), to another page in your app that does have a scrollbar (and now your nav, for example, shifts the width of the scrollbar)

So now I've added the CSS back, along with this little "fix" at the top of my Modal component:
useEffect((): () => void => {
  document.documentElement.style.overflowY = 'unset'
  return (): void => {
    document.documentElement.style.overflowY = 'scroll'
  }
}, [])

I just stumbled upon this issue and realise its quite old, but just wanted to add that you can use scrollbar-gutter: stable; instead of setting overflow-y: scroll; to avoid layout shifts with the scrollbar.


[Cosmos] Throughput throttling is not always handled gracefully within the SDK

Package Name:

@azure/cosmos

Package Version:

3.6.3
Describe the bug
When there is not enough throughput provisioned in the target Cosmos DB and lots of items are created with the SDK, exceptions are getting thrown and item creations fail.
To Reproduce
Steps to reproduce the behavior:

Clone repro app from https://github.com/vjrantal/cosmos-typescript-bulk-import-throughput-optimizer and follow readme instructions to run
Set the configuration at https://github.com/vjrantal/cosmos-typescript-bulk-import-throughput-optimizer/blob/e9175d53434265d23c7b2980a544aef68095f9f4/optimizer.ts#L15-L17 to values such as:

    private itemsToInsert: number = 4000;
    private concurrency: number = 100;
    private throughput: number = 400;

Observe that at the end of the execution, console output indicates that there were failed insertions. If the error catched on this line https://github.com/vjrantal/cosmos-typescript-bulk-import-throughput-optimizer/blob/e9175d53434265d23c7b2980a544aef68095f9f4/optimizer.ts#L92 is printed, it looks something like this:
Trace: Error: Message: {"Errors":["Request rate is large. More Request Units may be needed, so no changes were made. Please retry this request later. Learn more: http://aka.ms/cosmosdb-error-429"]}
ActivityId: 186f1cad-1ef9-44e8-bb07-59f4bfd2ce3f, Request URI: /apps/0f64e4b3-cfc1-49b8-9acd-06e1a1bccf4d/services/7653f9ed-e620-4e41-9905-6ba7004c8eea/partitions/0b42aab2-d1b2-4b8e-b55c-b9136cbc8e75/replicas/132351600029032261p/, RequestStats:
RequestStartTime: 2020-05-29T04:32:27.3161193Z, RequestEndTime: 2020-05-29T04:32:27.3161193Z,  Number of regions attempted:1
ResponseTime: 2020-05-29T04:32:27.3161193Z, StoreResult: StorePhysicalAddress: rntbd://<removed>.documents.azure.com:14320/apps/0f64e4b3-cfc1-49b8-9acd-06e1a1bccf4d/services/7653f9ed-e620-4e41-9905-6ba7004c8eea/partitions/0b42aab2-d1b2-4b8e-b55c-b9136cbc8e75/replicas/132351600029032261p/, LSN: 4116, GlobalCommittedLsn: 4116, PartitionKeyRangeId: , IsValid: True, StatusCode: 429, SubStatusCode: 3200, RequestCharge: 0.38, ItemLSN: -1, SessionToken: , UsingLocalLSN: False, TransportException: null, ResourceType: Document, OperationType: Create
, SDK: Microsoft.Azure.Documents.Common/2.11.0

Expected behavior
Expected that the SDK handles retries gracefully and that all item creations eventually succeed. It is expected that creations happen slower if less throughput is provisioned but it is not expected that the creations fail.
Additional context
The same scenario was tested with the eqvivalent dotnet app https://github.com/Azure-Samples/cosmos-dotnet-bulk-import-throughput-optimizer and that app does not have this same issue. All creations succeed even if less throughput is provisioned.

Thanks for the detailed report! We do have code for handling 429 retries internally, but eventually, they will be yielded up to the consumer. We will investigate

@southpolesteve It might be that this issue comes down to the current default maxTries value that is set to 9 currently.
What we observed is that when the database starts to throttle, it suggests retry after values in the ballpark of < 500 ms. With 9  retries, this is consumed in < 4.5 seconds. This is a lot sooner than the default timeoutInSeconds which is set to 30 seconds.
As reference, the dotnet SDK has 120 retries by default.
One theory might be that perhaps with the 9 retries, the exponential nature of the retries doesn't yet kick in so the JS SDK ends up giving up relatively early. We have seen that sometimes the database returns retry after values as high as > 10 seconds but perhaps the JS SDK stops retrying before the retry after values starts getting increased?
One potential consideration would be to align the default values with how they are set in dotnet SDK.

I checked with the .NET team and they said the 120 retry account only applies to endpoint discovery. They also use 9 as the default for throttle retries https://github.com/Azure/azure-cosmos-dotnet-v3/blob/427a8994af4d7ad4f1aa6e9584d52b5f30f828e9/Microsoft.Azure.Cosmos/src/RetryOptions.cs#L22. I suspect there is something else different that is causing the behavior

I've added an item to address this when we do a v4 release (No ETA at this time)


Feature Request: Add "Report Generated: $DATE" text within the Spreadsheet and PDF

In the PDF, underneath the custom title it shows "MONTH YEAR". This should show the date that the report had been generated (MONTH DATE YEAR) for instances where the report is being generated more frequently than on a monthly basis.

Likewise within the excel spreadsheet - but also not as vital as with the PDF version.

Love this idea and definitely will be implementing it ASAP. An additional option can be passed as a flag to include the day as well as the month and year in the PDF.
Admittedly, I'm not as proficient with the pandas library as I probably should be. I'll try to figure out a way to get it added to the excel spreadsheet as well. Design-wise, were you thinking of having the spreadsheet have similar title and date formatting as the PDF?


Auto rebase pull-requests

When a GreenKeeper pull-request fails, sometimes is not due to the dependency itself but due to the project code itself (hidden bugs that appear with the new version of the dependency, working in parallel on several interdependent layered projects...) so when the main one got fixed, the failing GreenKeeper pull-request would work again. The same way that when a new dependency version appear and automatically close the pull-request for previous ones, GreenKeeper should monitor the project itself and rebase the pull-requests when they get updated on master branch, so they don't get stashed on old commits.

This is live. When a Greenkeeper PR gets merged we rebase older Greenkeeper PRs.


Legacy octal escape sequences cannot be used in an ECMAScript module

Error: Transform failed with 6 errors:
:654:46342: ERROR: Legacy octal escape sequences cannot be used in template literals
:655:747: ERROR: Legacy octal escape sequences cannot be used in an ECMAScript module
:851:714: ERROR: Legacy octal escape sequences cannot be used in an ECMAScript module
:851:1618: ERROR: Legacy octal escape sequences cannot be used in an ECMAScript module
:859:3806: ERROR: Legacy octal escape sequences cannot be used in template literals

Could you please provide a reproduction?


refactor: add flat theme

Add prefersColorScheme support (without breaking current layout).

wait https://github.com/netless-io/flat/pull/1315 merged


Fix Tinkoff link

The link in the user showcases currently links to https://docs.tofu.tf/en/tinkoff.ru because it is only relative.

Why do we need Tinkoff there at all?

Why do we need Tinkoff there at all?

We need all users that want to appear at docs page.
This is the users section, provided by the template


Synchronization playlist

Hello. I made a script to download a playlist with next parameters:
youtube-dl -i --format mp4 --yes-playlist --external-downloader aria2c -o '%(playlist_index)03d - %(title)s - %(id)s.%(ext)s' --include-ads --merge-output-format mp4 [playlist]
After several days I've faced a problem: playlist's author added a new video in the middle of the playlist and youtube-dl has to downloaded a half of the playlist again. But old files are stay and not removed.
How can I synchronize the playlist and already downloaded files without downloading downloaded files again, but renaming it to a new names? Thanks.

You can't.


[RDS] Creating a DBInstance will spin fail aksrt if it happens to try to create the instance before the DBCluster it's attached to

Describe the bug
Specifying a manifest of the form
kind: DBCluster
spec:
  dbClusterIdentifier: x
---
kind: DBInstance
spec:
  dbClusterIdentifier: x

will sometimes fail with a retry loop of the form (censored)
2022-01-20T23:43:28.306Z	ERROR	controller-runtime.controller	Reconciler error	{"controller": "dbinstance", "request": "x/some-instance-name", "error": "DBClusterNotFoundFault: The source cluster could not be found or cannot be accessed: some-cluster-name\n\tstatus code: 404, request id: guid"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.0/pkg/internal/controller/controller.go:258
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem

Steps to reproduce

Create a manifest that specifies both a provisioned aurora DBCluster and an instance DBInstance attached to it.
Observe that the ackrt will fail to create it due to idiosyncratically trying to create the DBInstance before the cluster.

Expected outcome
The runtime needs to try to create every resource scheduled, rather than giving up if any one fails. That way, create DBInstance gracefully fails only once, then creates the DBCluster, then succeeds in the DBInstance creation because the cluster now exists.
Environment

Kubernetes version 1.21
Using EKS (yes/no), if so version? yes 1.21
AWS service targeted (S3, RDS, etc.) RDS

Sorry, this was due to the cluster failing to be created

@doctorpangloss I am also facing the same, how did you resolve this?


Unable to retrieve Cosmos DB accounts

Storage Explorer Version: 1.7.0/20190228.2
Platform/OS Version: Windows 10/ MacOS High Sierra/ Linux Ubuntu 16.04
Architecture: ia32
Commit:
Regression From: Previous release 1.7.0(Preview)
Steps to Reproduce:

Try to expand one Cosmos DB account.

Expected Experience:
The cosmos db account can be opened successfully.
Actual Experience:
An error occurs.

This should have been fixed in Storage Explorer v1.7.0 release.


Update Dialog.react.js

This change will remove the ripple effect from the dialog. I believe the material design 2.0 that has been released recently does not say anything about the ripple effect on the dialog component. I have already asked for this change but it was not done earlier. And  this will take care of the input from the dialog.

Or how about we create a ripple Prop in  component that can be passed from the root component level.

Or one another suggestion could be to implement it like card component. Where if(onPress) then provide  else


Use tera as templating engine

Fixes #77

@Nukesor You could rebase this in order to make the CI happy.

I am quite confident with the test harness but I really need to test this manually before going further (just came back from vacation so now I have time :)).
Also @Nukesor can you make the commit a breaking change (feat!: ...) so the automatic bump will reflect that.
Last but not least the documentation website needs to be updated accordingly.

Actually the documentation is updated already, and after a quick test on my setup this works like a charm let's to this then.
Great work @Nukesor !


Ticket1158 onconnecting followup

From discussion in https://github.com/crossbario/autobahn-python/pull/1170


Warn when trying to build before having run npm install

This should prevent struggles like this one: http://stackoverflow.com/questions/35096635/error-in-building-graphiql/35470669#35470669

tl;dr: if you don't npm install before running npm run build, then the build will use any old version of Babel that it can find (say… version 6, installed globally).

This makes sense. I'll look into upgrading babel to the latest, but nonetheless this seems like a good warning. Thanks!


Update Versions

Backup and restore only works for fixed versions.
If you restore from a different version of jenkins, then jenkins overwrites the whole folder, deleting restored files. (Note: Happens on container restart)
Possible solution: Installing from rpm, this way possibly the home folder does not contain binaries. This is the case with current installing from war file.
Alternative solution: New script for only backup and restore of configurations.

RPM does not do any difference, binaries are still mixed with configuration files.

Restore file written, only configuration files, see: https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins are restored from archive.


Add Checksum to Image Display

Show the hash/checksum beneath the image download link when the mouse hovers of the download link.

@aparcar what do you think? Should we use "Checksum:", "Hash:" or even "SHA256:"?

Hi, can you please add a screenshot? Also it would be great if you could propose this to the OpenWrt repository here

I'd call it sha256sum which is the same as on downloads.openwrt.org. It both describes the used Algorithm and also is language independent, so we don't need to add it to the translations as all.

This is not a big thing but I'd rather keep the checksum variables descriptive, imagine we want to use sha3  or whatever else at some point...

"sha256sum:" as label is a good idea.

Thanks for the rework. Could you please create a PR here and to keep this repository in sync?

@aparcar I haven't merged this because I am not quite happy about this:

the design does look a bit odd, maybe it is just me
the hash blows up the overview.png without being able to remove easily them

What about reducing the font size of the hash? (Like in the patch i send you last week)

Looks better that way:

done


Arrows break item frames

Reopening of #85 as it does not appear to have been fixed in the latest build (12).

@inklit how are you testing?

No, I'm testing by using standing in an admin claim, and then shooting an arrow at an item frame inside of a claim directly perpendicular of the claim I'm standing in.
What is the command to set projectile-impact-entity to false for all stuff?
It is missing a target value, though I'm not neccesarily sure as to what the target should be.

It should be 'any'

Thanks, this works.


B #3241: show ipv6 address

this PR apply:
-master
-one-5.8-maintenance

Hello @jloboescalona2 and @tinova, this commit breaks dual stack, ipv4 with ipv6 setup. On network tab I can see only ipv6 addresses. in place where was IP4 is IP6_LINK now.


thousand separator not working in a number field within Laravel Backpack

Bug report
Could you help me review my code to ensure that the thousand separator is correctly applied to the number input field in Backpack for Laravel
CRUD::field([
'label' => 'Nilai Tagihan',
'type'  => 'number',
'name'  => 'nilai',
'thousands_sep' => '.',
]);
Has anyone experienced issues with the thousand separator not working in a number field within Laravel Backpack?

Hey @haniramadhan-kkp
The thousands_sep is an attribute of a number column type, not a number field.
Why? HTML number input doesn't support it.


Draci doupe II – Roll template bugfix

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: < Dračí doupě II >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: < ALTAR > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: < Dračí doupě > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

"\00BB" or "»" in content property breaks roll template for some reason

Character Sheet Info Roll20 Internal Use only.


Test on docker

Test on Docker

You can test using Docker container
You no longer need rbenv or even Ruby installed on your local machine
Docker works both on your local machine and Travis CI

Usage
See https://github.com/hasumikin/mrubyc/blob/hasumi/test_on_docker/doc/test.md
Example of results
Test that failed on purpose
https://travis-ci.com/github/hasumikin/mrubyc/builds/190626144
Test succeeded
https://travis-ci.com/github/hasumikin/mrubyc/builds/190626437

Thank you!


enable sourcemap for esbuild in development

+1, but blocked by https://github.com/evanw/esbuild/issues/157

Okay, it looks like there's a sourcefile value that we can use, but i still don't see it working correctly in the devtools.
Also, since most tools wont support this by default (and to not suprise existing users) we're going to want to add a devOptions.sourcemap option to turn this on.

@yuheiy are you able to get a working example (actually seeing this in your devtools) and then adding a sourcemap/sourceMap config value to enable this?

Yes. It works in my devtools!

Thanks again for submitting, but we're still not ready to add this yet (we do some wrapping of JS files after build,  so this PR would be broken without extra support).
Will close this for now and plan to tackle once the prioritized issue tracker is a little lighter.


AWS S3 uploading issue

Sometimes the debug log says an image is uploaded to S3, while it is not.

I have this issue when i create a bucket that is NOT us-standard region.
Despite setting the region in the config, it will only work with us-standard region buckets.
There is no error thrown by imager, the image seems to be uploaded but isnt actually there.

Having the same issue on 0.4.0 as well

Here is the detailed description of my issue.
I tried uploading the same image to the S3, but sometimes (around 1/5 chance) it fails. Upon investigation S3 returns Error 400 to Knox, but Knox does not throw Error, causing Imager to treat the case as normal.
Looks like it is the issue of Knox.


Remove Nix functions from the packages output

Nix flakes have a particular schema. Having non-derivations in packages
violates it, so this moves them to the more appropriate (although not quite
standard) lib output.

This is based on #84.
And you can see that it removes the two failing builds from that PR: https://garnix.io/commit/796f479fb7151baa0b26e805879f3442dfd7036c


Missing Meshtastic requirement

System Health details
..
Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
Installing via hacs, it seems like it doesn't install the Meshtastic python package
Reproduction steps
1.aaa
2. aa
3.
...
Debug logs
Logger: aiohttp.server
Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:448
First occurred: 8:50:07 PM (1 occurrences)
Last logged: 8:50:07 PM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
    return await self._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
    return await super()._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
    result = await self._flow_mgr.async_init(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1287, in async_init
    flow, result = await self._async_init(flow_id, handler, context, data)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1312, in _async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1499, in async_create_flow
    handler = await _async_get_flow_handler(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2964, in _async_get_flow_handler
    await _load_integration(hass, domain, hass_config)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2941, in _load_integration
    await async_process_deps_reqs(hass, hass_config, integration)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 575, in async_process_deps_reqs
    await requirements.async_get_integration_with_requirements(
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 54, in async_get_integration_with_requirements
    return await manager.async_get_integration_with_requirements(domain)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 170, in async_get_integration_with_requirements
    await future
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 159, in async_get_integration_with_requirements
    await self._async_process_integration(integration, done)
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 182, in _async_process_integration
    await self.async_process_requirements(
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 269, in async_process_requirements
    await self._async_process_requirements(name, missing)
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 307, in _async_process_requirements
    raise RequirementsNotFound(name, list(failures))
homeassistant.requirements.RequirementsNotFound: Requirements for meshtastic not found: ['meshtastic==2.5.4'].

Diagnostics dump
...

Can you please report what home assistant version you are using?
If you are familiar with python, can you try to manually to install the dependency and report any errors?
Use pip install meshtastic==2.5.4 or pip3 install meshtastic==2.5.4 (you might first need to switch to proper virtual envs when you are using them)
I'm aware of a dependency issue under certain conditions where the protobuf library that meshtastic requires is conflicting with versions from other packages required be home assistant (or integrations)

Looking at your code, this looks really nice! Having the ability to send messages to nodes is amazing!

As part of another dev setup, I came across this issue one again as well. With python 3.11 and homeassistant==2024.3.3, this can be reproduced:
2024-11-23 22:02:34.511 ERROR (SyncWorker_0) [homeassistant.util.package] Unable to install package meshtastic==2.5.4: /home/dev/.virtualenvs/homeassistant-meshtastic-root/lib/python3.11/site-packages/_distutils_hack/__init__.py:33: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
ERROR: Cannot install meshtastic==2.5.4 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
[notice] A new release of pip is available: 23.2.1 -> 24.3.1
[notice] To update, run: /home/dev/.virtualenvs/homeassistant-meshtastic-root/bin/python -m pip install --upgrade pip
2024-11-23 22:02:37.294 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'meshtastic': Requirements for meshtastic not found: ['meshtastic==2.5.4'].

Protobuf version that is conflicting with meshtastic is protobuf==4.25.1 in this case. Home assistant is hiding the details about dependency resolution conflicts.
Note that manual installation of meshtastic dependency with pip will uninstall older protobuf version and install new protobuf-5.28.3, this could have other unwanted side effects an breaking some parts of home assistant.
What I know is that meshtastic python lib code meshtastic.util.message_to_json does not work with older protobuf version due to changes in  https://protobuf.dev/news/v26/ (including_default_value_fields vs always_print_fields_with_no_presence), and that code is currently being used by this integration. I have a workaround for this in place, but still unclear if there are some other unforeseen side effects when running meshtastic code with older protobuf version. If you are using this custom component in a bigger home assistant installation, I'd recommend for the time being to try run with the older protobuf version instead the new one

Ive been playing around with the integration for the last day. I really like how integrated it is into the HA ecosystem, while not relying on MQTT.
Ive been experiencing dropouts in the connection like you mentioned, however the diagnostic information around this is a bit limited. Sometimes HA logging shows the traceback from a broken pipe. However sometimes there is no log, but I see that no new data being added (eg uptime stays static on the device with the serial connection).
Im running this integration against a RAK4631 connected via POE (ethernet). I assume one of the reasons for the broken pipe is when a different client makes a connection to the API (eg Meshtastic cli from a pc).
I saw how you patched the our_exit function to keep the library from exiting. It's unfortunate that the python library isn't more resilient.
Ill try set up a dev environment for properly debugging the integration as its currently running on my home "production"  HA system. This has a lot of potential, especially if BLE connections are added.

I made a mistake regarding my observation on the connection being dead without a log entry, it just seems like sometimes the uptime metric is delayed and the connection is intact.

Good news, the protobuf compatibility issue as been addressed upstream in https://github.com/meshtastic/python/commit/426795fccdab8f08e7e645dd3e3bf9dfa39e2dc0 and the required protobuf version has also been relaxed, so switching to the new version 2.5.5 will resolve compatibility issues with home assistant

Great to hear! I see you added changes to the dev branch. Is there a simple way to switch to this branch in HACS? I tried using the URL https://github.com/broglep/homeassistant-meshtastic?ref=dev but it seems to stay on main

The first alpha version is now in main, with that this issues here regarding meshtastic requirement should be resolved. If not, please re-open.
For non-issue related discussions I have enabled discussions on this repo.
If you encounter bugs with the new version, feel free to report them, pretty sure that whole integration is still far from stable and I don't have this new version running yet for an extended period of time. But should be a bit more robust now as heartbeat mechanism is in place and I have spend quite some time to get dropped connection detection & reconnection handling working


Move docker samples to .NET Core Tools 1.0.0

⚠ This is still WIP, do not merge yet!

Fixes #136.

[x] Move from project.json to .csproj.
[x] Update docker files to target SDK v1.0.0 v1.0.1
[ ] Give it a whirl and update the image on the README.

@tugberkugurlu,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Moved the dockerfiles too but I am getting the below error during image build:
Step 10/14 : RUN dotnet restore
 ---> Running in 3a0437643075
  Restoring packages for /app/IdentityServerWithAspNetIdentity.csproj...
  Restoring packages for /app/IdentityServerWithAspNetIdentity.csproj...
  Installing Microsoft.NETCore.Jit 1.0.4.
  Installing Microsoft.NETCore.Runtime.CoreCLR 1.0.4.
  Installing Microsoft.NETCore.DotNetHostPolicy 1.0.1.
  Installing Microsoft.NETCore.App 1.1.0.
  Installing NUglify 1.5.5.
  Installing BundlerMinifier.Core 2.4.337.
  Restore completed in 3.11 sec for /app/IdentityServerWithAspNetIdentity.csproj.
  Restoring packages for /app/IdentityServerWithAspNetIdentity.csproj...
  Installing Microsoft.NETCore.Jit 1.0.2.
  Installing Microsoft.NETCore.Runtime.CoreCLR 1.0.2.
  Installing Microsoft.Extensions.SecretManager.Tools 1.0.0.
  Installing Microsoft.NETCore.App 1.0.0.
  Restore completed in 415.86 ms for /app/IdentityServerWithAspNetIdentity.csproj.
  Installing Microsoft.IdentityModel.Logging 1.1.0.
  Installing Microsoft.IdentityModel.Tokens 5.1.0.
  Installing Microsoft.Extensions.Options 1.1.0.
  Installing Microsoft.AspNetCore.Cryptography.Internal 1.1.0.
  Installing System.IdentityModel.Tokens.Jwt 5.1.0.
  Installing Microsoft.AspNetCore.Cors 1.1.0.
  Installing Microsoft.Extensions.Caching.Memory 1.1.0.
  Installing IdentityModel 2.1.1.
  Installing Microsoft.Extensions.Caching.Abstractions 1.1.0.
  Installing Microsoft.AspNetCore.Cryptography.KeyDerivation 1.1.0.
  Installing IdentityServer4 1.0.0.
  Installing Microsoft.AspNetCore.Identity 1.1.0.
  Installing Microsoft.AspNetCore.Authentication.OAuth 1.1.1.
  Installing IdentityServer4.AspNetIdentity 1.0.0.
  Installing Microsoft.AspNetCore.Authentication.Google 1.1.1.
  Installing Microsoft.EntityFrameworkCore.InMemory 1.1.1.
  Generating MSBuild file /app/obj/IdentityServerWithAspNetIdentity.csproj.nuget.g.props.
  Generating MSBuild file /app/obj/IdentityServerWithAspNetIdentity.csproj.nuget.g.targets.
  Writing lock file to disk. Path: /app/obj/project.assets.json
  Restore completed in 4.71 sec for /app/IdentityServerWithAspNetIdentity.csproj.

  NuGet Config files used:
      /app/NuGet.Config
      /root/.nuget/NuGet/NuGet.Config

  Feeds used:
      https://api.nuget.org/v3/index.json

  Installed:
      29 package(s) to /app/IdentityServerWithAspNetIdentity.csproj
 ---> 4374fcbc6da7
Removing intermediate container 3a0437643075
Step 11/14 : ADD ./src/IdentityServerWithAspNetIdentity/ /app/
 ---> 284fc5ac5924
Removing intermediate container 05f179533907
Step 12/14 : RUN dotnet publish -c Debug -o out
 ---> Running in d08415194680
Microsoft (R) Build Engine version 15.1.548.43366
Copyright (C) Microsoft Corporation. All rights reserved.

/usr/share/dotnet/sdk/1.0.1/Sdks/Microsoft.NET.Sdk/build/Microsoft.PackageDependencyResolution.targets(154,5): error : Assets file '/app/D:/Dev/IdentityServer4.Samples/Docker/src/IdentityServerWithAspNetIdentity/obj/project.assets.json' not found. Run a NuGet package restore to generate this file. [/app/IdentityServerWithAspNetIdentity.csproj]
/tmp/.NETCoreApp,Version=v1.1.AssemblyAttributes.cs(4,20): error CS0400: The type or namespace name 'System' could not be found in the global namespace (are you missing an assembly reference?) [/app/IdentityServerWithAspNetIdentity.csproj]

Not entirely sure why. @MichaelSimons thoughts?

@tugberkugurlu, hmm, not knowing how you migrated the project, I quickly ran dotnet migrate myself.  Looks like you did the same as I came up with the same results - https://github.com/MichaelSimons/IdentityServer4.Samples/tree/msbuild-migration.  Everything built without error when I ran docker-compose build.  Do you have any old artifacts laying around that could be causing issues?  Have you run something like git clean -fdx to see if this helps?

Do you have any old artifacts laying around that could be causing issues? Have you run something like git clean -fdx to see if this helps?

Yes, that turned out to be the case 😞 thanks for checking it out 👍 I am looking into getting a dockerignore file now.

Looks like you did the same as I came up with the same results -

yep, I ran dotnet migrate on global.json file.

finished?

finished?

nope, hold your horses a little bit more.

@leastprivilege Works as expected AFA I can see. Good to merge now, :shipit:

thanks!!


Update maven-checkstyle-plugin to 2.17

Hi
Please, update maven-checkstyle-plugin to 2.17, cause:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.12:check (checkstyle) on project modernizer-maven-plugin: Failed during checkstyle configuration: cannot initialize module TreeWalker - Unable to instantiate RedundantThrows: Unable to instantiate RedundantThrowsCheck -> [Help 1]

RedundantThrows was removed with version 6.2 (see https://github.com/checkstyle/checkstyle/issues/473)  and its reference should be removed in src/main/resources/checkstyle.xml
Thanks in advance
Regards

Thanks for reporting this issue!  Please submit pull requests as well.


"Minified React error" when adding Education and Position

Education can not be added at all; Position can be added every other times.
Tested in Chrome and Edge.
react-dom.production.min.js:209 Error: Minified React error #310; visit https://reactjs.org/docs/error-decoder.html?invariant=310 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Yi (react-dom.production.min.js:154)
    at Gi (react-dom.production.min.js:156)
    at Object.useState (react-dom.production.min.js:167)
    at t.useState (react.production.min.js:25)
    at f (useTranslation.js:82)
    at m (index.js:30)
    at List.js:48
    at Array.map (<anonymous>)
    at ce (List.js:38)
    at Ki (react-dom.production.min.js:153)

This may be related to #309, or not, :-)

This should be fixed now :)


Log Sorting wrong

Bug Report
Doing some Bench-Testing I noticed that sometimes the sorting of the logs (presented in QGC) is wrong.

Could you take a screenshot of the corresponding SD card files?
That might help in locating the issue.

Yes, here they are:

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Since the last prerequisite is (clone of) this repository, by definition the user has the models.

Description

Since the last prerequisite is (clone of) this repository, by definition the user has the models.
How Has This Been Tested?

Checked https://github.com/adelton/opendatahub-ai-edge/blob/prerequisites/pipelines/README.md.
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/lgtm


Carthage Integration

I would like to be able to integrate DateTimePicker to my project via Carthage instead of Cocoa Pods, sadly right now this is not possible: Dependency "DateTimePicker" has no shared framework schemes
I'm not experienced enough to know if this is a complex task, but maybe you can look into this.

I would also like to use DateTimePicker, but cannot since I am using Carthage.

A bit late, but Carthage is supported in version 2.1.0 onward.


bundle inject must use options

User may want to add gem like this in the Gemfile :
gem 'bootstrap', '> 0', :group => [:development], :source => 'https://rubygems.org'

using this command :
$ bundle inject "bootstrap" ">0" --source=https://rubygems.org --group=development

currently we get this msg as output:
Unknown switches '--source=https://rubygems.org, --group=development'

I am working on this.

Great! Please support these options inside a new command named bundle add. The inject command was never intended to support options. Thank you. :)

@indirect do you want to approve  the bundle add RFC? This could serve as a really helpful guide.

I'd love for there to be more discussion on it! If anyone has ideas. I'm also super happy to have an implementation that we can try out and give feedback on 👍 So maybe we should consider the RFC "provisionally approved" and move forward from there.

Great, i'll go over it and add anything i can.

I have read bundle add discussions in PRs and RFC. I see some attr in bundle inject So I think inject must be for installing single gem with source and/or group options.
Using bundle add user must be able to add multiple gem with these options(it can have different source and group for each gem).

@Shekharrajak i would leave the adding multiple gems alone for now and just work on adding a single gem with options.

Thanks @indirect @colby-swandale for discussion. I have oped a PR https://github.com/bundler/bundler/issues/5456 . I am getting some error in testcases. I hope I will fix them soon.


New version availiable, updated as per instructions, getting this error.

I know last time i forgot to npm update but this time I did all the steps I promise..
/home/xxx/Desktop/mybots/live/poloLenderPro/node_modules/big.js/big.js:317
throw err;
^
BigError: NaN
at throwErr (/home/xxx/Desktop/mybots/live/poloLenderPro/node_modules/big.js/big.js:314:19)
at parse (/home/xxx/Desktop/mybots/live/poloLenderPro/node_modules/big.js/big.js:184:13)
at Object.Big (/home/xxx/Desktop/mybots/live/poloLenderPro/node_modules/big.js/big.js:90:17)
at currencies.forEach.currency (/home/xxx/Desktop/mybots/live/poloLenderPro/server/workers/poloLender/poloLender.js:803:17)
at Array.forEach (native)
at emitPerformanceUpdate (/home/xxx/Desktop/mybots/live/poloLenderPro/server/workers/poloLender/poloLender.js:798:16)
at Namespace.onBrowserConnection (/home/xxx/Desktop/mybots/live/poloLenderPro/server/workers/poloLender/poloLender.js:873:5)
at emitOne (events.js:96:13)
at Namespace.emit (events.js:188:7)
at Namespace.emit (/home/xxx/Desktop/mybots/live/poloLenderPro/node_modules/socket.io/lib/namespace.js:212:10)

Seems that it has to do with updated config.
Copied over this part and seems to have started fine now.
#Telegram bot token and your user Id
POLOLENDER_TELEGRAM_TOKEN=123456789:AAHIxxxxxxxxxxxxxZxxxxxxxxxxxxxxxkk
POLOLENDER_TELEGRAM_USERID=111111111
#Report interval in minutes for Telegram reports(default is 60 minutes)
POLOLENDER_TELEGRAM_REPORTINTERVAL=60

POLOLENDER_ADVISOR_TOKEN=dummyToken

Yea issue fixed. I think you need to add to your update instructions, to merge any config file changes as well. 👍
Nice update.

So far config files are backwards compatible and you only need to update if you need the additional features.


Show options for backing out/resetting migrations

Due to renaming and changes to my domain classes, I have confused EF Core so that it creates migrations that no longer makes sense when executing.
Eg. I get the error:
PM> update-database
Applying migration '20181010102432_stuck'.
Failed executing DbCommand (2ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
ALTER TABLE [Photo] DROP CONSTRAINT [FK_Photo_CubeObject_ObjectId];
System.Data.SqlClient.SqlException (0x80131904): 'FK_Photo_CubeObject_ObjectId' is not a constraint.
Could not drop constraint. See previous errors.
It somehow tries to remove a constraint it cannot find, thereby resulting in an error.
I would like to wipe all migrations and the database, and start from scratch, but and it should be as easy as to fire a command in the Package Manager Console, like: "Reset-Migrations" or "Reset-Database" (or some better naming), that would remove all migrations and wipe the database completely.
If you Google "How to reset EF Core" there are many possible solutions to this problem, but they require many manual steps.
I know that custom migration code would also be deleted, but that can be added back in manually (and it has probably changed).
I just think it's harder than it should be to reset the migrations and the database. I know many people who would like this feature.
Best, Peter.

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

ID: 6e28b0a8-b7e4-4c07-9e60-0df403bbee28
Version Independent ID: 12300b31-6f7b-b75c-970d-693365e77013
Content: Migrations - EF Core
Content Source: entity-framework/core/managing-schemas/migrations/index.md
Product: entity-framework
GitHub Login: @bricelam
Microsoft Alias: bricelam

Also, an initial migration could be added by default that made no changes to the database -this would be easier to reset to.

Also, if you (like me) were looking for a way to wipe the data and migrations, do the following:

Open the 'SQL Server Object Explorer' in Visual Studio.
There should be one called something like: "(localdb)\MSSQLLocalDB (SQL Server)...". Open that one, open Databases. You should be able to find the database in there. Open the your database there, then tables. Now delete all tables by right-clicking each one and clicking 'Delete'. Also 'dbo.__EFMigrationsHistory'.
Delete the 'Migrations' folder in your Solution.
Run 'Add-Migration ' in the Package Manager Console.
Run 'Update-Database' in the Package Manager Console.

This 5 step process is what I want in one command in PMC.

@PeterOeClausen Or you can:

Delete the Migrations folder
Run the command "drop-database" from the PMC

True, thanks for the tip :)
Maybe if you could add it to the Docs (if it's not already there somewhere), or make it easier to find :)
Eg. If you create another step called 'How to reset or clear your database and migrations':
https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/
While trying to find a solution for my problem, I found other developers searching for an easy way to do this:

https://weblog.west-wind.com/posts/2016/Jan/13/Resetting-Entity-Framework-Migrations-to-a-clean-Slate

https://stackoverflow.com/questions/16035333/how-to-delete-and-recreate-from-scratch-an-existing-ef-code-first-database

https://stackoverflow.com/questions/22680446/entity-framework-rollback-and-remove-bad-migration

So it may make sense to make it more visible in the docs?
Thanks for the help!

@PeterOeClausen This worked in EF6: Update-Database -TargetMigration:0 and this seem to be working in EF Core: Update-Database 0

@older That works to, but it attempts to roll back the migrations by running Down methods. If the migrations have been messed up (i.e. through bad hand edits) then this may not work, hence sometimes blowing away the database is more pragmatic.

@PeterOeClausen Or you can:

Delete the Migrations folder
Run the command "drop-database" from the PMC

Still would be nice if we have a command to do these steps for us. Something like reset-the-whole-world-for-me!

I like the way IdentityServer4.EntityFramework did it. They have a dropdb.bat, an updatedb.bat and a migratedb.bat. They also work with multiple db contexts.
DropDb
cd src\Host
dotnet ef database drop -c PersistedGrantDbContext
dotnet ef database drop -c ConfigurationDbContext
cd ..\..

MigrateDb
cd host
rmdir /S /Q Migrations

dotnet ef migrations add Grants -c PersistedGrantDbContext -o Migrations/IdentityServer/PersistedGrantDb
dotnet ef migrations add Config -c ConfigurationDbContext -o Migrations/IdentityServer/ConfigurationDb
dotnet ef migrations script -c PersistedGrantDbContext -o Migrations/IdentityServer/PersistedGrantDb.sql
dotnet ef migrations script -c ConfigurationDbContext -o Migrations/IdentityServer/ConfigurationDb.sql

cd ..

UpdateDB
cd host
dotnet ef database update -c PersistedGrantDbContext
dotnet ef database update -c ConfigurationDbContext
dotnet run /seed
cd ..

remove-migration -force


Fixes #1984: Remove repeated definition for tsconfig in TsJestGlobalOptions

Summary
Fixes #1984: removes redundant code (possible typo?)
Test plan
NA
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
NA

there's a difference in case tsconfig and tsConfig that i had missed


device name issue on emulator

BluetoothAdapter does not work well on emulator. for simplicity we can make use of MANUFACTURER and MODEL.
Best thing can be to make use of https://github.com/jaredrummler/AndroidDeviceNames
Here is reference discussion on stackoverflow http://stackoverflow.com/questions/7071281/get-android-device-name

@ankitpatial This doesn't have the same result. It just concatenates the Manufacturer and Model parameters that we already capture separately.
Just live with getting Unknown on emulators. It works on a handful of real devices I've tested.


Question about structuring projects

Thanks for your hard work, everyone!
In the fruit stand example, we create a pipeline by pulling in a JSON configuration file from the examples folder with the -f flag. :ok:
However, in a real setting, where is the recommended place to store these pipeline configurations? Should they be under version control?
Any advice about how you structure your pachyderm projects?

Storing them under version control is definitely a good pattern, that was a big part of our rational for having a simple text format for pipelines. I like to structure things like this:
project/
   pipeline.json # pipeline file
   Dockerfile
   <other things the Dockerfile uses>

If I need more than one docker image I put each of them in top level directories.

Thanks @jdoliner.
I'm not sure I fully understand.
What does /project correspond to? A git repository?
If yes, where would you subsequently mount the pachyderm filesystem?
So for example, if I have a project like this:
/project
   pipeline.json
   Dockerfile

Where would you mount the pachyderm filesystem? In a different folder?
Also, would there be a one->one mapping of pachyderm repos to git repos containing the pipelines?
Or would you have one git repo of pipeline files for n pachyderm repos?

Yeah, project would correspond to a git repo, and have a name that makes sense to you. So for example if I'm working on analyzing political speeches my git repo might be called speech-analysis.
I like to mount the pachyderm filesystem on ~/pfs, so in a different folder.
Having many pipelines / pachyderm repo in the same git-repo is probably the way to go. You normally need several pachyderm repos and pipelines to do something interesting and keeping them all in separate repos would quickly get unwieldy. Especially because the pipelines need to match, in the sense that what one pipeline outputs others must be able to consume. That could get tricky if things are spread across multiple repos.

A little supplement for Jdoliner's statement. I think that @rexmortus wonders where the data file is stored, or where the file system is mount, in Pachyderm. I recommend you to read my issue #780 to help understand the structure of Pachyderm if it is necessary. A refactor would be finished in v1.2.0 to correct the problem.  A small advice that you can divide you issue into several parts, and each part can be related to one specific topic with some running results. It would be helpful for us to understand your problem.


endpoint: Limit proxy completion timeout to proxy updates

Wait for proxy redirect completion before generating policies that redirect traffic to proxy redirect ports, to prevent traffic loss.
Reduce the proxy completion timeout to 10 seconds again, since policy regeneration is now excluded from the timeout.
To avoid traffic loss, wait for the new policy to be computed and compiled into BPF before deleting obsolete redirects, to make sure no packets are redirected to those ports.
Replace the tracking of redirects to delete with a tracking of the redirects that have been realized, to simplify the logic.
Fixes: #2788
Fixes: #2796
Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

test-me-please

test-me-please

test-me-please

test-me-please

@aanm, @raybejjani, I moved the e.removeCollectedRedirects(owner) call after e.runInit(...). I use a separate WaitGroup in order to exclude the call to runInit from the timeout. Let me know whether that looks ok.

I simplified the implementation following @jrajahalme's advice. I replaced Endpoint.proxiesToRemove, which (incorrectly) tracked the redirects to remove, with Endpoint.realizedRedirects, which tracks the redirects that have been configured in the proxy. realizedRedirects is protected by the build mutex, like proxiesToRemove was.
@aanm @raybejjani @jrajahalme please review again.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


FileNotFoundError

Dear,where is the 'Holopix50k/annotations/val_annotations.json'?    I only get Holopix50k/annotations/all_annotations.json  after I run the command 'sh download_data.sh'.

Thank you for your reply！
Yes, I am running the latest script, but the error message shows no /annotations/all_ annotations. json.I also checked that it was not. I am running sh Download_ data. Is this  correct ?
是的，我运行的是最新的脚本，但是报错显示没有/annotations/all_annotations.json .我也检查了，确实找不到那个json文件，我是运行sh download_data.sh下载的数据集，请问这是正确的吗？ @yaochx

@lw0210 Hi, the val_annotations.json of Holopix50k is not supplied. Please remove all datasets without val_annotations.json in https://github.com/aim-uofa/AdelaiDepth/blob/6309e00ae56b8fc74a52431f76d8e18633351c70/LeReS/Train/tools/train.py#L256.  I will fix the bug right now.

Thank you！I'll try it as you say.
谢谢！我按你说的来操作一次.

Thank  you！I'll try it as you say.
谢谢！我按你说的来操作一次. @guangkaixu


New optional annotation on attributes

As requested at #1843 by @R4PaSs, a new annotation optional is now available on attributes.
class A
    var x: Int = 99 is optional
   # Because of `optional`, the automatic signature of the A constructor is `init(x: nullable Int)`
end

var a = new A
print a.x # outputs 99
var b = new A(4)
print b.x # output 4

In the model, the optional annotation only affects the signature and the behavior of the setter.
It transforms the argument to a nullable one and use the provided value if null is given as a parameter.
The nullable parameter is then propagated to the automatic constructors in the usual way.
Basically, the previous example is equivalent to having written:
class A
    var x: Int is noautoinit
    fun x=(x: nullable Int) is autoinit do if x != null then self.x = x else self.x = 99
end

I really like seeing this :)
Though there's the re-assignation issue which might surprise some people, though this could be fixed later if no real solution emerges soon.
:shipit: !

+1


added_0933

IMPORTANT: Please do not create a Pull Request without an issue.
All Submissions:

[x] I have read the CONTRIBUTING document.
[x] My code is written in Python3 and is ending with .py
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] I have checked that my submission does pass the test on LeetCode.com
[x] Does your filename follow the naming Conventions?
[x] Have you linked your PR to an Issue?

Closing issues
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
fixes #147

Can anyone contribute or the ones who are actually assigned?

@TanayKulkarni Prefered the assigned one - as long as there is everything correct like in the Contribution Guidelines (Checklist) --> eg. Issue linked, name, passes test and so on
For the Issue #147 you are assigned - so I wait for your PR


fixes #260 with valid property for gallery sort order

This simple fix deals with the invalid-sort-order string in gallery.js

Just checking to see if anything else is needed on this PR, or if it's good to go as-is, for merging.

Hey @dmakogon thanks for this! Going to merge it in now. 👍


github open-issues badge showing "unknown"

Check the following badge:
https://badgen.net/github/open-issues/papb/better-promise-error-log

It shows "github | unknown", instead of the expected "open issues | 0".
What could be causing this?

Could it be because there are no issues at all on the repository (none open and none closed as well)?

Oops, that's a bug 😅

Should be fixed by now :D


remove unused file test/run.sh.

#57
thanks you!

@mushroom528 Thanks for the PR! Looks good to me. Merged.


scheduler does not conform to the outside parent div

Checklist

[X] I've verified that I'm running react-big-schedule version 4.2.0 or higher

Describe the bug
The scheduler does not conform to the outside parent div no matter what I try, the second issue is that when I change the viewType, from day to week or month, the entire scheduler expands outside the div and will  not look functional.
Currently the scheduler does not conform to the outside div:

If I change to week:

If I rerender the component it reshapes itself back to a normal size, but its still not conforming to the outside div.

I have tried the

responsiveByParent route https://github.com/hbatalhaStch/react-big-scheduler/issues/26
https://github.com/react-scheduler/react-big-schedule/issues/52
Which is running react not in strict mode, my production version has the same identical issues.
besidesWidth: window.innerWidth <= 1600 ? 100 : 350, // you need to add this

None have worked so far, from my understanding it seems that the resource table have a dynamic width that increases its size dependent on the width rather than the events table.
What could it be and what should I be trying? I would really like this to work in my application.
Reproduction Link/Code

  const schedulerParentRef = useRef();
  var today = new Date();
  var date = today.getFullYear() + "-" + (today.getMonth() + 1) + "-" + today.getDate();
  let schedulerData = new SchedulerData(
    date,
    ViewType.Day, // Change the status of daily, weekly or monthly
    false,
    false,
    {
      eventItemPopoverPlacement: "bottomRightMousePosition",
      responsiveByParent: true,
      besidesWidth: window.innerWidth <= 1600 ? 100 : 350,
      startResizable: false,
      endResizable: false,
      schedulerContentHeight: "100%",
      weekCellWidth: 80,
      dayCellWidth: 40,
    }
  );
  schedulerData.setResources([]);
  schedulerData.setEvents([]);

  useEffect(() => {
    dispatch(initialiseViewModel(schedulerData));

    return () => dispatch(reInitialiseViewModel());
  }, [date, dispatch, initialiseViewModel, reInitialiseViewModel]);

  const changeDate = (e) => {
    setDateState(e);
  };

  const getResources = useCallback(() => {
    getAuthorization()
      .get(`company/get_companyschedule_recources?assigned_to=${DropDownValue}`)
      .then((res) => {
        setResources(res.data.message ? [] : res.data);
        dispatch(setAPIDetailsUser(res.data.message ? [] : res.data));
        getEvents(); // Get events after resources have been set
      })
      .catch((err) => {
        console.log("Error in getting schedule", err);
      });
  }, [dispatch, DropDownValue]);

  const getEvents = useCallback(() => {
    getAuthorization()
      .get(`company/get_companyschedule_events?assigned_to=${DropDownValue}`)
      .then((res) => {
        setEvents(res.data.message ? [] : res.data);
        dispatch(setAPIDetailsUserEvents(res.data.message ? [] : res.data));
        setDataLoaded(true); // Set dataLoaded to true after both resources and events are set
      })
      .catch((err) => {
        console.log("Error in getting schedule", err);
      });
  }, [dispatch, DropDownValue]);

  //Set Scheduler Data
  useEffect(() => {
    if (dataLoaded) {
      viewModel.setResources(Resources);
      viewModel.setEvents(Events);
      dispatch(setViewModel(viewModel));
      setDataLoaded(false); // Reset after processing the loaded data
    }
  }, [dataLoaded, Resources, Events, DropDownValue]);

  useEffect(() => {
    setDataLoaded(false); // Reset the dataLoaded state before fetching
    getResources();
  }, [DropDownValue, getResources]);

  const prevClick = (schedulerData) => {
    schedulerData.prev();
    schedulerData.setEvents(Events);
    dispatch(setViewModel(schedulerData));
  };

  const nextClick = (schedulerData) => {
    schedulerData.next();
    schedulerData.setEvents(Events);
    dispatch(setViewModel(schedulerData));
  };

  const onViewChange = (schedulerData, view) => {
    schedulerData.setViewType(view.viewType, view.showAgenda, view.isEventPerspective);
    schedulerData.setEvents(Events);
    dispatch(setViewModel(schedulerData));
  };

  const onSelectDate = (schedulerData, date) => {
    schedulerData.setDate(date);
    schedulerData.setEvents(Events);
    dispatch(setViewModel(schedulerData));
  };

  const eventClicked = (schedulerData, event) => {
    setOpen(true);
    getAuthorization()
      .get(`company/schedule_view/${event.id}/`)
      .then((res) => {
        setScheduleDetails(res.data);
        setDateState([new Date(`${res.data.start_date}`), new Date(`${res.data.end_date}`)]);
      })
      .catch((err) => {
        console.log("Error in getting schedule details", err);
      });
  };

  const ops1 = (schedulerData, event) => {
    setOpen(true);
    getAuthorization()
      .get(`company/schedule_detail/${event.id}/`)
      .then((res) => {
        setScheduleDetails(res.data);
      })
      .catch((err) => {
        console.log("Error in getting schedule details", err);
      });
    // alert(
    //   `You just executed ops1 to event: {id: ${event.id}, title: ${
    //     event.title
    //   }}`
    // );
  };

    return (

      {displayTimeline && (

          <Scheduler
            parentRef={schedulerParentRef}
            schedulerData={viewModel}
            prevClick={prevClick}
            nextClick={nextClick}
            onSelectDate={onSelectDate}
            onViewChange={onViewChange}
            eventItemClick={eventClicked}
            viewEventClick={ops1}
            viewEventText="Details"
          />

      )}

Steps to reproduce

view scheduler and notice that its not the right size
click on week and it jumps outside of the div

Operating System
windows
Browser
firefox
React version
^18.0.2
react-big-schedule version
^4.2.5
Additional Information
No response

Hi @AsifDaum which package are you using. Its of our or hballtalblhaStch library.
Can you try to create a bug in code sandbox if possible

I was using your library, but the problem was consistent across both. I actually found out what the issue was anyway:
One developer had set global css to the scheduler which caused it not to render properly, by simply removing this I was able to get it to a more manageable state.
/* @media screen and (max-width: 900px) {   .scheduler-view{     width: 820px !important;   } } */ /* .scheduler-view{   width: 55vw !important; } */ /* table#RBS-Scheduler-root{   width: 100% !important;   margin: 0px !important; } */
I uncommented it out and that caused it to render properly, but the bug that was mentioned by:
https://github.com/react-scheduler/react-big-schedule/issues/52
appeared, where the window had to be resized for it to conform to the layout on first render.
I have bypassed this temporarily by doing the following:
`  useEffect(() => {
const triggerResize = () => {
window.dispatchEvent(new Event("resize"));
};
// Initial dispatch to ensure correct rendering
triggerResize();

// Optionally, you may want to set up a small delay before triggering the resize,
// to ensure all rendering processes have completed:
setTimeout(triggerResize, 100);

// Clean up if needed when component is unmounted or relevant dependencies change
// return () => {
//   // Any cleanup code here
// };

}, []); // Empty dependency array means this useEffect runs once, similar to componentDidMount
var today = new Date();
var date = today.getFullYear() + "-" + (today.getMonth() + 1) + "-" + today.getDate();
let schedulerData = new SchedulerData(
date,
ViewType.Day, // Change the status of daily, weekly or monthly
false,
false,
{
eventItemPopoverPlacement: "bottomRightMousePosition",
besidesWidth: window.innerWidth <= appSideBarStatus ? 70 : 360,
startResizable: false,
endResizable: false,
schedulerContentHeight: "100%",
}
);
schedulerData.setResources([]);
schedulerData.setEvents([]);
useEffect(() => {
dispatch(initialiseViewModel(schedulerData));
return () => dispatch(reInitialiseViewModel());

}, [date, dispatch, initialiseViewModel, reInitialiseViewModel]);`
I added a resize event to make it adjust to the layout after its first render.
I had to also use the besidesWidth to ensure it fit the space correctly, its not perfect since I have a toggle-able sidebar but its working fine for now. Once you guys have corrected its layout issues then I think i'll be able to remove that stuff.

We will try to solve the issue but not sure how much time it will take as I am also busy with some work so.


Fix softtabstop rendering

Thank you for your attempt to fix #6 via #7. Unfortunately, the logic isn't quite that easy. So, I eventually get to implement this myself :-)

With soft tabstops, as much indent as possible is rendered with tabs, and the remainder with spaces. So, an indent of 5 x 4 = 20 is done via 2 * tab (16) + 4 * space, considering the 'tabstop' and 'softtabstop' values.
Add rainbow_levels#is_indented_with_softtabstop() and check that before rainbow_levels#is_indented_with_tabs() in rainbow_levels#get_pattern().

Ah! Now I got what you meant ... I didn't fully understand issue #6 until seeing your code.
Thank you very much! 🖤 ❤ 💛


Update to thread warnings.

A few small updates from #772

Now I have to do something like:
        return environment.databaseClient.importData(imports)
            .receive(on: environment.mainQueue)
            .fireAndForget()

just to avoid this warning. That doesn't make any sense to me, should this really include fireAndForget effects?

That doesn't make any sense to me, should this really include fireAndForget effects?

Unfortunately we think it must. As brought up in #772, when an effect's completion runs on the wrong thread, there is the possibility for there to be a runtime crash, so one must be diligent when working with background threads in general, even during fire-and-forget.

Even when I am not mutating anything or doing any logic after (e.g. map)? If that's the case, how about TCA doing that for us always? It sounds like it's necessary no matter what..

I find the new behavior surprising as well. The description of the original PR https://github.com/pointfreeco/swift-composable-architecture/pull/772 said:

Any async Effect (including fireAndForget) could result in a runtime crash when updating internal state like effectCancellables

So at present would a fireAndForget effect only cause problems if it's also cancellable? Could we check if self?.effectCancellables[uuid] != nil before performing the thread check?
https://github.com/pointfreeco/swift-composable-architecture/pull/773/files#diff-50345ad35b59a32af74fda59695df9c6b1826302d5b41e5d8fbe47477917cc5dR393
More broadly, I feel like having to worry about scheduling back into the system breaks the semantics of 'fire and forget' (at least how I understood it). Related, if a fireAndForget is cancellable is it really fireAndForget?

I know it sounds counter-intuitive, but even .fireAndForget effects must receive on the main queue. Such effects clearly don't emit anything, and so it seems unnecessary, but these effects call their receiveCompletion on the same thread as receiveValue, and that's why this becomes problematic.
If you look at the implementation of Store.send you will see that in the receiveCompletion block we do some work to clean up cancellables:
https://github.com/pointfreeco/swift-composable-architecture/blob/86bcd083a1048452007561e28b6adf97c81fba2d/Sources/ComposableArchitecture/Store.swift#L390-L394
Note that this work has nothing to do with cancelling effects via the .cancellable(id:)/.cancel(id:) APIs. The cancellables in the above code snippet are there by virtue of the fact that we must subscribe to the effect returned to us by the reducer, and therefore we must keep around a cancellable.
So, even if you previously were not seeing crashes in your application's due to data races, the fact is that the possibility was always there. Effects completing on different threads will eventually cause a problem, even if they are "fire-and-forget", and this is why we'd like to warn loudly if we detect it.
Having said all of that, it does sound like we have room for improvement in the docs. Perhaps we should detail all of this information in the docs for .fireAndForget as well the Store/ViewStore docs. In the future we hope to leverage DocC to provide definitive sources for this kind of information.

Right on, thanks @mbrandonw. Agreed this is totally a mental model and docs issue. I'd include some info in the error message from this change as well. I'll update my app shortly and see if anything else comes up as I transition to this new understanding.

I’m still curious if TCA can do this automatically behind the scenes, since it’s apparently needed for pretty much every case.

Unfortunately there is no way to do that really. The simplest way to do that would be to chain on a .receive(on: DispatchQueue.main) to every effect returned to us from the reducer, but that can cause a lot of subtle problems. Alternatively, we could try introducing locks to protect the data in the store, but that will not be as efficient and can lead to all new problems.
As documented on the store we take a strong stance on not baking any threading/locking into the library at all. We feel the simpler approach is to make users of the effects be explicit with how they behave.
It's unfortunate that this change has caused disruptions, but we feel it's for good reason! In the future we'll try to do a better job of communicating this change to the community with better documentation, blog posts, etc.

@mbrandonw quick note while I'm updating my app -
I added a receive(on:) to every fireAndForget and now I'm getting new failures from TestStore.assert - An effect returned for this action is still running. It must complete before the end of the test. which is great - I previously thought it was convenient but also odd that these effects go untracked.
Without diving into the internals of TestStore, I'm wondering if there's some more structure we could add to this whole thing such that the error could be "the effect [id]" instead of "an effect"
Would combining the need to receive and name each effect provide some clarity all around? For example:
return environment.service.execute()
  .receive(id: myId, on: environment.mainQueue)
  .fireAndForget()

Similar to to how cancel works now, but now for all effects. I wonder if this could simplify the mental model overall, since the rule would be to identify and schedule any effects that complete on a different thread.

Thanks for the update @rcarver, it's good for us to know what the knock-on effects are of this change.
One thing that comes to mind with your situation is whether or not it is appropriate for you to use an immediate scheduler. Then you wouldn't need to worry about the completion. Are you using a test scheduler specifically because time is involved? If the only asynchrony in your effects is just simple .receive(on:)s then you could potentially simplify your tests with an immediate scheduler.
And as for identifying effects. It may not be clear at first, but the line the test failure points to is the action that kicked off the effect which is still running. So hopefully that should narrow down which effects could be causing this because you only have to look up that action in your reducer.
Adding an explicit identifier to the effect is interesting, and something we've actually explored a ton to help out with debugging. However, we don't feel we have yet solved the ergonomics around it. You end up having to thread the information through many layers, and it's quite easy to lose the information (basically every time you erase the effect). We want to spend more time thinking about it, but it's a hard problem.

thanks @mbrandonw I'll try the immediate scheduler, that should simplify at least a few cases. I did know about the error line which is great - hopefully tracking down the rest of these failures will be easy enough.


Provide reftest coverage to verify pull request #1948

Summary
This PR addresses the following issues:

[ ] Bug #1881 - icon rendering bug report
[ ] PR #1948 - existing attempt to resolve #1881

Icon rendering for FontAwesome 5 appears troublesome in html2canvas at the moment.
Icons that render correctly as glyphs in an interactive Firefox or Chrome browser session have a tendency to appear as unicode placeholder rectangles when rendered by html2canvas.
This pull requests adds test coverage to verify the fix from #1948.
Test plan (required)
A reftest is added which illustrates the problem.
After each set of commits, a screenshot will be added in a comment displaying the output at the end of the following commands:
$ npm run build
$ npm run karma
$ firefox 'tmp/reftests/text-fontawesome!-Firefox-68.0.png'

Code formatting
:heavy_check_mark:
Closing issues
Verifies #1948, enabling it to fix #1881.

Test Results
As of commit ae0bd29d37109023897514ef854cc54452f39eed

Test Results
As of commit 5211ab4065f675d6b3a0896eaabef45fdca4f29f

Test Results
As of commit 5fdf88135eca7ae9bc280047ef55b3a45851658c

NB: I'm not sure how the Twitter icon rendered correctly in the test results from https://github.com/niklasvh/html2canvas/commit/5fdf88135eca7ae9bc280047ef55b3a45851658c.
As far as I can tell, fa-square-o has been removed from Font Awesome 5.

Test Results
As of commit 59f802e31e02225568552b00b7a61bd2334d14d1

Hrm.  Even though my local build of https://github.com/niklasvh/html2canvas/commit/59f802e31e02225568552b00b7a61bd2334d14d1 failed to render correctly as shown in comment https://github.com/niklasvh/html2canvas/pull/2202#issuecomment-613886128, the Azure Pipelines build shows a successful result:
https://dev.azure.com/niklasvh/html2canvas/_build/results?buildId=276&view=artifacts&type=publishedArtifacts shows the published artifacts, and we are interested in the ReftestResults download.
Here is the Firefox Stable image from that file:

:heavy_check_mark:

Test results in the ReftestResults download seem inconsistent across master and this branch, regardless of whether the propoed fix from issue #1948 is applied.
For example, icon rendering succeed in master @ c366e8790d346ea981b24b7425aef6bf6d7ebcec (where the fix is not yet applied).
In https://github.com/niklasvh/html2canvas/pull/2202#issuecomment-613886128 there appeared to be an icon rendering failure @ https://github.com/niklasvh/html2canvas/commit/59f802e31e02225568552b00b7a61bd2334d14d1 despite the fix being applied.
This could use a little more investigation.

(for safety in case of any possible merges, I'm removing the fix from this branch and leaving only the test coverage in-place)

:warning: Let's not do this until an issue with the current certificate for https://use.fortawesome.com/ is resolved.
Ref: https://news.ycombinator.com/item?id=22899738


[Auengine] corrected extractions logic

The way the video download url was been extracted was
not working well so i change it for it to extract the
correct url

The test video is an episode from an anime, I doubt they have the rights to distribute it.
We must find one video that doesn't infringe copyright, otherwise we'll have to remove the extractor.

Thanks, merged.
As @jaimeMF mentioned, the extractor is danger of removal and will be removed within 10 days if a valid example URL cannot be found.

about my editor sorry. About the extractor i am acctually working on a project based on this wonderfull project and in an attempted to get a passing build i decided to work on all the failing extractors and send you guys a pull request as a way of contributing back to the project that is helping me. Thanks guys


false positive for RF101, RF102, RF103

When I run repo-review locally on my python project, I get the following error:
Ruff:
├── RF001 Has Ruff config ✅
├── RF002 Target version must be set ✅
├── RF003 src directory specified if used ✅
├── RF101 Bugbear must be selected ❌
│   Must select the flake8-bugbear B checks. Recommended:
│
│
│    [tool.ruff.lint]
│    extend-select = [
│      "B",  # flake8-bugbear
│    ]
│
├── RF102 isort must be selected ❌
│   Must select the isort I checks. Recommended:
│
│
│    [tool.ruff.lint]
│    extend-select = [
│      "I",  # isort
│    ]
│
├── RF103 pyupgrade must be selected ❌
│   Must select the pyupgrade UP checks. Recommended:
│
│
│    [tool.ruff.lint]
│    extend-select = [
│      "UP",  # pyupgrade
│    ]
│

IMO, this is a false positive, since I have
[tool.lint.ruff]
select = [
    "B",
    "I",
    "UP"
    # ...
]
# ...

in my pyproject.toml.

I just realized that there was a bug in my config and everything works correctly!


Error after Update to HA Core Update 2024.8.0

Checklist

[X] I have updated the integration to the latest version available
[X] I have checked if the problem is already reported

The problem
Getting this error after updating HA Core 2024.8.0
Logger: homeassistant.setup
Source: setup.py:269
First occurred: 8:36:14 AM (1 occurrences)
Last logged: 8:36:14 AM
Setup failed for custom integration 'mqtt_vacuum_camera': Requirements for mqtt_vacuum_camera not found: ['pillow==10.3.0'].
What version of an integration has described problem?
2024.06.3
What was the last working version of an integration?
2024.06.3
What vacuum model do you have problems with?
Xiaomi 1C
Please firmware installed on your Vacuum.
No response
What type of platform you use?
Intel NUC (or generic x86_64)
What version of Home Assistant do you use?
2024.8.0
What type of installation are you running?
Home Assistant OS
Logs or Errors shown in the HA snapshots (please enable the Debug Mode) text will be auto formatted to code.
Logger: homeassistant.setup
Source: setup.py:269
First occurred: 8:36:14 AM (1 occurrences)
Last logged: 8:36:14 AM

Setup failed for custom integration 'mqtt_vacuum_camera': Requirements for mqtt_vacuum_camera not found: ['pillow==10.3.0'].

Function, that in your opinion is creating the issue.
None
Additional information
No response

@duffmiester intereating behavior of pip and Home Assistant.
Do not understand why, but an easy fix is to change in the Manifest >=10.3.0 to 10.4.0
When I tested it in my PI it works on the beta.. meaning why == is coming out I don't really know.

Okay I did setup also on the main instance that never used Pillow 10.4.0 and it looks Home Assistant did boot the Camera correctly so @duffmiester sorry but you might need to update the camera too as you are running 2024.06.3 to 2024.08.0 this should solve your issue.

@duffmiester converting this "issue" to "discussion" as it isn't I guess an issue ;)


[GOBBLIN-1363] Fix minor mistakes in the Getting-Started guide

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1363

Description

[x] Here are some details about my PR, including screenshots (if applicable):

Fixed the following mistakes/obsolete descriptions in the Getting Started document.

JDK version that Gobblin requires
Gradle task name for Findbugs
Broken links to other pages
Wrong download URL for avro-tools

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No additional test, since it's just a documentation fix. Instead, I ran mkdocs locally and made sure the document was fixed as expected.
Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3204 (11f2192) into master (2fa3553) will decrease coverage by 4.28%.
The diff coverage is n/a.

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

Codecov Report

Merging #3204 (11f2192) into master (2fa3553) will decrease coverage by 4.28%.
The diff coverage is n/a.

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


Fill plot area when using min/max down sampling

Can be achieved by painting trapezoids between the plots like this:
fn create_filled_segments(line1: &[[f64; 2]], line2: &[[f64; 2]]) -> Vec<Polygon> {
    let mut segments = Vec::new();

    for i in 0..(line1.len() - 1) {
        // Create a trapezoid between line1[i], line1[i+1], line2[i+1], and line2[i]
        let mut points = Vec::new();
        points.push(line1[i]);
        points.push(line1[i + 1]);
        points.push(line2[i + 1]);
        points.push(line2[i]);

        // Create a polygon for this segment
        let polygon = Polygon::new(PlotPoints::new(points))
            .fill_color(Color32::from_rgba_premultiplied(100, 40, 50, 0))
            .stroke(Stroke::NONE);
        segments.push(polygon);
    }

    segments
}

The issue is already reported at egui_plot: https://github.com/emilk/egui_plot/issues/36


test: adding flexibility to PIE string

this test has been failing locally for me for ages.  I assume Position-Independent Executable  is also a PIE file :-)


small graph / large graph viz choice

Add a check on the graph to make sure it has locations on all vertices before using the large visualization
and add forcing features.
see implementation in java for reference.

any progress on that?


Division by zero

Code:
2 / 0;
Current:
Fatal error: Uncaught exception 'php\lang\JavaException' with message 'java.lang.VerifyError: Operand stack underflow
Exception Details:
  Location:
    $php_module_***_class0.hide$7(Lphp/runtime/env/Environment;[Lphp/runtime/Memory;)Lphp/runtime/Memory; @9: pop
  Reason:
    Attempt to pop empty stack.
  Current Frame:
    bci: @9
    flags: { }
    locals: { '$php_module_***_class0', 'php/runtime/env/Environment', '[Lphp/runtime/Memory;' }
    stack: { }
  Bytecode:
    0x0000000: 2bb2 0022 0432 b600 2857 b200 2eb0
'

Proposed:
RuntimeException: Division by zero in #file on line #line

Fixed.


Make merge_sort_slices MergeSortSlices public

In OLAP database system, sort/merge_sort is not just for one column.
The unit of sort compute is block, we should make merge_sort_slices public, then we can take the indices from the block to build new blocks.

We also need materialize_merge_indices to reuse the iterator to sort other arrays.


Create a View for SizedBox

I have chosen not to set the background and border properties, as those are moreso styling properties - in our current state, we seem to be much preferring only specifying layout values

Hmm, is that in the flex example? Hopefully I'll be able to reproduce on Monday.

Yes, it is.

I've not been able to reproduce this on my machine. I don't have a Mac to test it with


feat: Use the latest version of Virgil

Preview https://excalidraw-git-new-virgil-excalidraw.vercel.app
Source: https://github.com/excalidraw/virgil

[ ] Backwards compatibility with the old exported SVGs

On the other hand, woff2 seems to look a bit worse on Windows (Windows 10) than ttf. 🤔

On the other hand, woff2 seems to look a bit worse on Windows (Windows 10) than ttf.

Don't see any difference on Windows 7/10. You may be seeing https://github.com/excalidraw/excalidraw/issues/2717 caused by different positioning/scroll on each of your scenes.

The difference is probably insignificant, but subjectively small font looks better to me on excalidraw.com than in this PR. It doesn't depend on focusing/selecting, so I don't think this is #2717.

Your pic on my screen looks better with the PR version (which doesn't mean anything), but I'm the last one to say "I'm not seeing it" since I was just unsuccessfully persuading a colleague that the text is blurry on low-DPI screens :).

The current version is a bit blurry, yes, but in a good way =)

Not a fontexpert.. but from a quick research.. woff2 seems like the latest and greatest, and has a smaller footprint. Maybe I messed up in the export (didn't have many options to be honest)..
https://caniuse.com/woff2

I'm not an expert either, so okay, let's use woff2. At least until we find an expert who can tell us the truth.

Let's do it!


setup-data-dir.sh: fallback to the mkdir/chmods if the rkt.conf doesn't exist

This is a follow-up for 65fc1fb935acda
Fixes:
$ sudo bash -x rkt-v1.18.0/scripts/setup-data-dir.sh
...
+ systemd-tmpfiles --create /usr/lib/tmpfiles.d/rkt.conf
Failed to open '/usr/lib/tmpfiles.d/rkt.conf', ignoring: No such file or directory

$ echo $?
1

@evverx thanks for this PR! I think that your patch is needed, however we have a bigger issue here as we should check for /usr/lib/tmpfiles.d/ and copy rkt.conf in there if it exists, before calling /usr/lib/tmpfiles.d/rkt.conf. Can you please add that logic into the same snippet too?

@lucab, thank for the review!

as we should check for /usr/lib/tmpfiles.d/ and copy rkt.conf in there if it exists

I think the setup-data-dir.sh-script shouldn't install rkt.conf.
Maybe, systemd-tmpfiles <parent-dir-of-the-script>/init/systemd/tmpfiles.d/rkt.conf?

@lucab, I added https://github.com/coreos/rkt/pull/3335/commits/94e588777cacf91dd9a82ad489a8261c8cdf5d77
What do you think?

I think the setup-data-dir.sh-script shouldn't install rkt.conf.

Fair enough, I think we are indeed fine with your further proposal. Could you please just squash the two commits together?

@lucab, done


feat: impl total staking amount hooks

Proposed Changes

implemented total staking amount hooks

Implementation

It was a bit larger than the Component I was thinking of. I've described my idea of Component design below, so please check it out and let me know what you think.
atoms
Unit (abstracted data)

molecules
TotalStakingAmount (define specific data / use Unit atoms)

StakeCard

WithdrawCard

organisms
AssetOutline

PossessionOutline

PropertyOutlineList & PropertyOutline (both are in the same directory)

PropertyHeader

MainHeader

and then, pages are laid out using organisms.

I agree with you.
I refactored and commit some codes.


Add TypeScript to "Getting Started"

Child of #1772
@kaiwalyakoparkar

@kaiwalyakoparkar please comment on this issue so I can assign it to you.

hey @svrnm 👋 kindly assign this issue to me

Done

Hey @svrnm can you please tell me the file location I need to update (The previous issue has been been updated hence I lost track of file I need to update

https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/docs/instrumentation/js/getting-started
Most important one is nodejs. You can do browser as well.

@svrnm perfect! few more things.

The content written on the page is just for nodejs. Do I need to change that to be generic to ts as well?
How do I check out if the tab thing is working (The default vs code preview does not render it as tabs)

Yes, make sure that it works with TS as well. So if you need additional dependencies then list them. This means also the shell code will need tabbing.
After cloning and pulling the repo on your local machine run npm run serve. This will start a local dev copy for you with auto refresh etc.

Done!