Trusted network removed, login gets stuck for previous authentication

Home Assistant release with the issue:

0.77.3
Last working Home Assistant release (if known):
Never
Operating environment (Hass.io/Docker/Windows/etc.):

Hassbian
Component/platform:

User/authentication platform
Description of problem:
I've been playing around with adding a trusted network for my config, but I've been having issues because of NGINX/proxy.  I therefore have abandoned this approach.  However, I did authenticate some clients using the trusted network option, but now that I've removed it, when I try to resolve the frontend it just spins at "Loading Data."  I have to clear cookies/cache in order to get back to the log in.
Perhaps there needs to be some kind of timeout for the login, or at least a way for something like this where the user gets deleted/login approach no longer works it can fail gracefully and go back to the log in screen.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

It should be fixed in 0.78, please try to upgrade.


Fix startup of components in HA

There is some weird concurrence/async problem during startup: The data is pulled in before the sensors are created. So there is no data on startup and you have to wait until the 5 minute refresh kicks in. Not a major issue but also not very nice.

fixed, i hope :wink:


This SDK not work with Azure China Azure Data Explorer

Describe the bug
the client create api nowhere to specify the cloud china, it always using the global azure login endpoint.
To Reproduce
Steps to reproduce the behavior: using the china adx cluster address do connection
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

To work with other clouds use the environment variable :
AadAuthorityUri
For example for public cloud - set AadAuthorityUri to https://login.microsoftonline.com/


HTML contains stray  due to binding approach

The library currently takes the HTML of the editor and binds it to the Angular variable.  This results in some internal Trix HTML comments being added to the HTML ( - see below).  A better way is to use Trix to serialize the editor state into HTML:
Replace: ngModel.$setViewValue(element.html()); with ngModel.$setViewValue(Trix.serializeToContentType(element[0], "text/html"))
The HTML output changes from this:

Test

Now works correctly!

Bold and great once again.

to the nicer:

Test

Now works correctly!

Bold and great once again.

I am new using to angular trix. I am having some trouble in retrieving the data from the database. As shown above when I save the content from the editor to database it is saving fine but when I retrieve instead of the data what I saved, HTML tags are applying.
For example: in the editor if save Sample content as bold and when I reload the page after saving it is displayed as
Sample content
 but I just need Sample content in bold. Please help me in fixing this issue.

See this: https://github.com/basecamp/trix/issues/249


Use "main" instead of "master" for creating repos

I think we should stop creating repos with the main branch named "master" and use "main" instead. But you will have to account for both if you open an old repo in an Arcade version that uses "main."

Related: https://github.com/microsoft/pxt/pull/7231


补充ch信息

This PR is for:

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


Going through list and dropping more non-relevant items

I was able to get the list of records down to 3500 or so. Could keep filtering, that's still a lot!

Okay. And that is on top of the search terms I added. We could go on a little more. I guess that will save us some time in the end because 3500 is also some files to review. I can give et another go for 1 hour more during next week.


[Bug] API requests for Resellerclub registrar not working

Describe the bug
domain registration and other api requests for domain services are not working  for resellerclub registrar, beleive it or not, i trired all possible scenerios, ip is whitelisted on resellerclub account, still getting the error ,
HttpClientException: HTTP/2 500 returned for "https://httpapi.com/api/domains/available.json?domain-name=google&tlds=com&suggest-alternative=false&auth-userid=$user-id&api-key=$api-key",
i also tested the same with admin demo at https://demo.fossbilling.org/admin , not working.. i also mentioned the issue in discord community ,, i got random reply .. HTTP 500 is an internal server error on the endpoint - make sure you have the correct URL, auth, allowed IP, etc. , but tried to find the correct url , auth , , but didnt found in the code... this issue need to be resolved immidieatly, because no one can order hosting or other product without domain .. domain services are important ..
for a clue, i tried to resolve the issue with resellerclub support team , they replied that your api request url parameter is wrong, have the URL has %22. at the end, which is causing the issue , if anyone can resolve it asap, will be appreciated
How to reproduce
need to fix the api request with resellerclub api format , ,
resellerclub api guide --
https://manage.india.resellerclub.com/kb/answer/751  -- all api requests,
https://manage.india.resellerclub.com/kb/answer/764  -- domain check api
Expected behavior
should be resulted in domain available or not , invalid domain, also should not disclose the user-id and api key on any type of error, because it is a secret information of site owners, currently when it is showing an error, it is also displaying the user-id and pai key . in that error,
Screenshots
No response
FOSSBilling version
0.4.3
Module version
No response
Device
No response
Information
i also tested the same with admin demo at https://demo.fossbilling.org/admin , not working.. i also mentioned the issue in discord community ,, i got random reply .. HTTP 500 is an internal server error on the endpoint - make sure you have the correct URL, auth, allowed IP, etc. , but tried to find the correct url , auth , , but didnt found in the code... this issue need to be resolved immidieatly, because no one can order hosting or other product without domain .. domain services are important ..
for a clue, i tried to resolve the issue with resellerclub support team , they replied that your api request url parameter is wrong, have the URL has %22. at the end, which is causing the issue , if anyone can resolve it asap, will be appreciated
Additional context
for a clue, i tried to resolve the issue with resellerclub support team , they replied that your api request url parameter is wrong, have the URL has %22. at the end, which is causing the issue , if anyone can resolve it asap, will be appreciated

does any body resolve these issues or just waste of time

does any body resolve these issues or just waste of time

Yes, 155 bug reports have been closed (some of these were duplicates, but almost all were actual bugs that got resolved).
The issue with this one is that FOSSBilling is made up of volunteer contributors and the only one of us who has access to/uses Resellerclub has been unavailable due to personal / family reasons

still it is crucial part for domain services , please try to resolve it ..
i will definitely thinking to contribute any amount i can afford , once it
is usable for me ,. right now i cant use fossbilling only because of this
issue .. thanks for replying btw..
On Mon, Jul 17, 2023 at 5:14 AM Belle Aerni @.***>
wrote:

does any body resolve these issues or just waste of time
Yes, 155 bug reports have been closed (some of these were duplicates, but
almost all were actual bugs that got resolved).
The issue with this one is that FOSSBilling is made up of volunteer
contributors and the only one of us who has access to/uses Resellerclub has
been unavailable due to personal / family reasons
—
Reply to this email directly, view it on GitHub
https://github.com/FOSSBilling/FOSSBilling/issues/1267#issuecomment-1637218939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHDKIYALSYYKVFWFADY3I3XQR4GRANCNFSM6AAAAAAYQIO4NE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
mainpal

still it is crucial part for domain services , please try to resolve it .. i will definitely thinking to contribute any amount i can afford , once it is usable for me ,. right now i cant use fossbilling only because of this issue .. thanks for replying btw..
…

Feel free to hire somebody or look at it your self if there are questions feel free to ask

still it is crucial part for domain services

Even with a working domain registrar, domain registration / services within FOSSBilling are very lacking and are fundamentally flawed in some ways. It's not really something we'd recommend using anyways.
FOSSBilling is still considered pre-production software. If someone is going to use it, the assumption should be one of the following:

A) That they are capable of software development so that they may fix issues or implement features if there is urgency for them.
B) They have a developer who may handle the situation described in A
C) They are willing to hire someone (a freelancer perhaps) using money they save by not needing to pay for the software to handle the situation described in A
D) They use it with the expectation that there will likely be issues & issues may or may not be resolved quickly.

If none of those situations apply to you, I would suggest watching the repository on GitHub for releases and waiting until we get closer to or reach version 1.0.0 which will be the point where we consider FOSSBilling to be production ready.

Thanks for the tip!
On Tue, Jul 18, 2023 at 5:03 PM Belle Aerni @.***>
wrote:

still it is crucial part for domain services
Even with a working domain registrar, domain registration / services
within FOSSBilling are very lacking and are fundamentally flawed in some
ways. It's not really something we'd recommend using anyways.
FOSSBilling is still considered pre-production software. If someone is
going to use it, the assumption should be one of the following:

A) That they are capable of software development so that they may
fix issues or implement features if there is urgency for them.
B) They have a developer who may handle the situation described in A
C) They are willing to hire someone (a freelancer perhaps) using
money they save by not needing to pay for the software to handle the
situation described in A
D) They use it with the expectation that there will likely be issues
& issues may or may not be resolved quickly.

If none of those situations apply to you, I would suggest watching the
repository on GitHub for releases and waiting until we get closer to or
reach version 1.0.0 which will be the point where we consider FOSSBilling
to be production ready.
[image: image]
https://user-images.githubusercontent.com/17304943/254248986-339d39e6-ed44-4871-a004-f0b5094500d1.png
—
Reply to this email directly, view it on GitHub
https://github.com/FOSSBilling/FOSSBilling/issues/1267#issuecomment-1640047356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHDKI3J4R4DINGK52ELUVTXQZX7LANCNFSM6AAAAAAYQIO4NE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
mainpal

I could not repeat this bug. Once I had allowlisted my FOSSBilling server the domain check lookup worked without error.
We have written extensively for the Logicboxes API so happy to look at any other issues reported with this extension.


Problem implementing pdf_viewer in st.tabs

I'm quite new in Streamlit and as stated in the title I have been facing problems trying to implement the pdf viewer in my project. My solution has a set of st.tabs and I need to display a different pdf on each one of them but for now when I run my code it only renders the one from the tab that is open when the app is refreshed, when I switch tabs the rest remain blank.
When I use an st.markdown with an iframe () it works but only on Firefox but not on Chrome or Edge.

Hi @OliverPSZ, could you please share a working example?

Hi @lfoppiano , having a similar issue here
I have a set of references in one tab and, based on the selected reference, a second tab should display the associated pdf and page.
the code goes something like this
ref, docs = st.tabs(["References","Docs"]) with ref:     #logic to select a reference with docs:     page=st.session_state.page     pdf_viewer(st.session_state.document,                        pages_to_render=[page-1,page,page+1],                        width=1000)
As of now this doesn't work
BUT
If I modify something in the code and click "rerun" while being in the correct tab it works as expected
is there a workaround ?

I think the issue is that the document is not attached to the children of the correct tab. One workaround, I think, would be to have the "doc" tab selected when you call the pdf_viewer(), so that the viewer is correct when rendered. An alternative would be to display the references on 1) a different columns instead of tabs, or, 2) in the sidebar.
I'm not sure how much users like to click back and forth on the tabs when they have to inspect multiple references. But this is just my humble opinion. 😅
The problem comes on a problem I have encountered a few times already, which is on how to calculate correctly the height of the pages, when the tab of the pdf is not visible everything gets to 0 and the pages are not shown.

I'm closing this as it's a duplicate of #56


Sensors for AC activity

If possible, I would like to monitor when the AC is actively running, at what speed (for variable ACs), energy use, etc
My central AC has sensors for hvac_action and hvac_fan which tells me when the unit is running and it's been helpful at detecting issues and monitoring energy use during my electric provider's on-peak hours.

Is this information is available?

Agreed, this would be a nice enhancement.
First, to support this we need to know if the device sends this information or not.

How can I test that?

 I'll take a look at these in a few days.

I haven't found any references to the necessary functionality to implement this features so I'll be closing it.


Remove api trt deps

mmdet apis is being used during training by mmdet codebase. However the training env does not support tensorrt yet. Hence this dep needs to be removed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 5 committers have signed the CLA.:x: meremeev:x: siddharthanpr:x: mprannoy:x: ramchandra-karandikar:x: thomashuang1You have signed the CLA already but the status is still pending? Let us recheck it.


upgrade: provider 5.0->6.0, flutter_statusbarcolor_ns 0.3->0.4

Hi, updated stacked_themes: provider and flutter_statusbarcolor_ns. The test has passed successfully!
Because stacked_themes >=0.2.4 depends on provider ^5.0.0 and stacked >=2.2.7+1 depends on provider ^6.0.0, stacked_themes >=0.2.4 is incompatible with stacked >=2.2.7+1.

@FilledStacks Hey Dane, could you please merge this


Fix shift clicking on Add Sun/Environment to Scene buttons

Believe this fixes: https://github.com/godotengine/godot/issues/73467
Only tested on Linux
First is a single click, second is shift click.
Screencast_20240905_013752.webm

Thanks!

Cherry-picked for 4.3.1.


Add storage repository data resource

This is to implement #15.
Todo

[x] Write docs for the new data source
[x] Run make testacc a final time
[ ] Get feedback on the data resource to make sure it the use cases from #15

I haven't heard of any feedback from #15. I'm going to move forward with this change and we can revisit other improvements to it later.


macOS-bundler: unmount old dmg when building

When (re)building the binarys the Build-Script will fail if the previouly build .dmg file is still mounted.
Steps to reproduce the behavior:

Build the binarys
Open the .dmg file
Close the file (Closing won't actually unmount it)
Build again

Expected behavior
I think there should be an exception preventing this.
Either it should check if previously the created .dmg is still mounted and exit with corresponding error-message or (better) it should try to unmount it.
While building the script will actually mount the new .dmg file and unmount it again. So unmounting it with the same process as in  tauri/tooling/bundler/src/bundle/templates/dmg/bundle_dmg Line 360 should be possible as long as names dont change.
# unmount
echo "Unmounting disk image..."
hdiutil detach "${DEV_NAME}"

OS: macOS 11.2.3 / M1
Node: 15.12.0
NPM: 7.6.3
Rustc: 1.51.0

Do you think you can make a PR fixing this? 🥺


dfu/mcuboot: solution for Set pending: don't crash when image slot corrupt

This is the Mirror issue.
Related to https://github.com/JuulLabs-OSS/mcuboot/pull/414 discussion.

cc @utzig @ccollins476ad

Is this still relevant?  The upstream issue has been closed.

Not an issue


The CSS color-scheme property shouldn’t be unknown

The CSS color-scheme property is incorrectly reported by this plugin as being unknown:

In fact, this is a standard CSS property:

https://www.w3.org/TR/css-color-adjust-1/#propdef-color-scheme
https://web.dev/color-scheme/#the-color-scheme-css-property

After digging around some more, it seems this is related:
https://github.com/microsoft/vscode-css-languageservice/issues/223

Closing as this package has been deprecated in favor of the official styled-components/typescript-styled-plugin fork
After updating to that fork, follow up in the styled-components repo if this is still an issue


fix set_day method

The method receives in decimal the value to be set as the day of the month, but the ds3231 module expects it in bcd format.
Using the write_register_decimal method, can be written in the correct format.

Nice find, thanks! There are a couple of warnings and a problem with the MSRV that have appeared and I need to fix beforehand. I will merge this afterwards.

coverage: 89.841%. remained the same when pulling 7f318d80eadbcd0cb0944d3460545b43c774fb41 on kirbylife:fix-set-day-format into de0231b958bd670f945fb9f44358989650c0b70a on eldruin:master.

I have published this in version 0.5.1.


feat: no longer read the obsolete internal setting in orgs.yaml

Remove code that checked obsolete internal setting
Tweak the wording of cla check messages

@feanil this is ready to go.


Proposal: Provide a "Plugin" Architecture to Load components-contrib Components

Hosting Componets on its own repository is a good idea.
Unfortunately, the dependency between this project and the components repository causes that the daprd binary
to be re-linked and rebuilt for each new component added.
The use of interface as a way of communication between daprd and components is a good starting point.
Would it make sense to change the existing design for a more flexible design like a "Plugin" based design?
At least two approaches come to mind:

Go plugin / shared memory model

Hashicorp's Go Plugins / Multi-process RPC model

Go Plugin / Shared memory model
Pros:

Has the benefits of less external dependencies as it's built-in in Go

Extensible

Cons:

Less Stable (a plugin could bring the entire daprd process down)

Hashicorp's Go Plugins / Multi-process RPC model
Pros:

Stable. Plugins don't bring down the daprd process.

Extensible

Cons:

Multi-process communication could be challenging.

In any event, I'll be more than happy to collaborate on either approach. :)

Hey @robertojrojas, we've indeed looked at these options and came to similar conclusions regarding the pros and cons.
Plugins are a general "problem" in Go.
RPC plugins in general have one major drawback, which is added latency and reduced throughput, and thus would be unsuitable for Dapr.
Go Plugins seem like the way to go, but they currently do not run on Windows, which would make it very hard for contributors and developers running on Windows to use Dapr.
By using interfaces we're already setup for Go Plugins, but we can't make the jump without dropping Windows support, which is problematic.
You can read here about other current problems with the Go Plugins design.
That said, it's a point in time thing and will most probably be resolved by the Go team going forward.
In the meanwhile, rebuilding Daprd for new components is consistent with how we'd integrate with components had they been Go Plugins, that is, in an incremental manner. At the very least it was shown to be working well over the past 2 weeks, adding a lot of components contributions to the Dapr runtime.
In addition, and this cannot be neglected, it provides us with the best possible performance, by leveraging native Go in-proc calls.
What I would really like to see is a way for us to provide the means (via a tool or Makefile) to build Dapr with zero or more components by selection.

@yaron2  cool that you guys already looked into this. 👍

Now that Wasmer has WASI support, it may be feasible to load components written in another language and compiled t WASM. I might have a little experiment to see if this is doable.


'Locking issue' with ConcurrencyMode.Optimistic at RedisDatabaseContext

Contact Details
No response
Version
8.x (develop, pre-release)
On which operating system(s) are you experiencing the issue?
Windows, Linux
Using which broker(s) did you encounter the issue?
RabbitMQ, In-Memory
What are the steps required to reproduce the issue?
1. Implement SAGA with Redis persistence
2. Set ConcurrencyMode = Optimistic
3. Set MessageRetry with Immediate

What is the expected behavior?
I expect that RedisDatabaseContext should not create lock when calling update but  I got "MassTransit.MassTransitException" with  message Unable to lock saga.
public async Task Update(SagaConsumeContext context)
{
var instance = context.Saga;
        IAsyncDisposable updateLock = (_options.ConcurrencyMode == **ConcurrencyMode.Optimistic**)
            ? updateLock = await Lock(instance, context.CancellationToken).ConfigureAwait(false)
            : null;

        try
        {
            instance.Version++;

            var deserializer = context.SerializerContext;

            var existingInstance = await Get(deserializer, instance.CorrelationId).ConfigureAwait(false);
            if (existingInstance.Version >= instance.Version)
                throw new RedisSagaConcurrencyException("Saga version conflict", typeof(TSaga), instance.CorrelationId);

            await Put(deserializer.SerializeObject(instance).GetString(), instance.CorrelationId).ConfigureAwait(false);
        }
        catch (Exception exception)
        {
            throw new SagaException("Saga update failed", typeof(TSaga), instance.CorrelationId, exception);
        }
        finally
        {
            if (updateLock != null)
                await updateLock.DisposeAsync().ConfigureAwait(false);
        }
    }

What actually happened?
With 'optimistic' concurrencymode , I expect that we should not lock the redis and using SAGAVersion to validate the racing condition.
But I look at the code and wonder why we need to lock the redis if the ConcurrencyMode is Optimistic.
public async Task Update(SagaConsumeContext<TSaga> context)
        {
            var instance = context.Saga;

            IAsyncDisposable updateLock = (_options.ConcurrencyMode == ConcurrencyMode.Optimistic)
                ? updateLock = await Lock(instance, context.CancellationToken).ConfigureAwait(false)
                : null;

If we can't lock this redis, the default RetryPolicy in RedisSagaRepositoryOptions will be used to create delay message , right ?

public class RedisSagaRepositoryOptions<TSaga>
        where TSaga : class, ISaga
    {
        public RedisSagaRepositoryOptions(ConcurrencyMode concurrencyMode, TimeSpan? lockTimeout, string lockSuffix, string keyPrefix,
            SelectDatabase databaseSelector, TimeSpan? expiry)
        {
            ConcurrencyMode = concurrencyMode;

            LockTimeout = lockTimeout ?? TimeSpan.FromSeconds(30);

            LockSuffix = string.IsNullOrEmpty(lockSuffix) ? "_lock" : lockSuffix;

            KeyPrefix = string.IsNullOrWhiteSpace(keyPrefix) ? null : keyPrefix.EndsWith(":") ? keyPrefix : $"{keyPrefix}:";

            RetryPolicy = Retry.Exponential(10, TimeSpan.FromMilliseconds(100), TimeSpan.FromSeconds(10), TimeSpan.FromMilliseconds(918));

Related log output, including any exceptions
{"@t":"2023-07-12T03:16:27.9988253Z","@mt":"Retrying {Delay}: {Message}","@l":"Warning","@x":"MassTransit.MassTransitException: Unable to lock saga: Phatra.AlgoTrading.LimitOrder.States.OrderDetailState(f9b4f509-617a-4440-8f56-0e451073fe63_lock)\n   at MassTransit.RedisIntegration.Contexts.RedisDatabaseContext1.SagaLock.<Lock>g__LockAsync|6_0()\n   at MassTransit.Policies.PipeRetryExtensions.Retry[T](IRetryPolicy retryPolicy, Func1 retryMethod, CancellationToken cancellationToken)","Delay":"00:00:01.0950000","Message":"Unable to lock saga: States.OrderDetailState(f9b4f509-617a-4440-8f56-0e451073fe63_lock)","SourceContext":"MassTransit.ReceiveTransport"}
Link to repository that demonstrates/reproduces the issue
No response

You'll need to submit a complete repository reproducing the issue, the fragments above don't really point a clear picture of what you are experiencing.


Preference system similar to Stremio's in lib/db

It would work like
db.findOne({  imdb_id: ...},[
   { tag: "hd", min_avail: 2 } // prefer HD torrents if they have at least 2 availability
], function(err, torrent) { /* receive torrent */ })

It must be default behaviour to prefer 720p and 1080p torrents if their availability is at least 2

@jaruba and @sammuel86  - thoughts?

looks cool, but what if there is no quality tag for the torrents? will all of them simply be ignored with this query?

oh, i just realized it was a dumb question. :)

LEt's still answer it - most torrents will be quality tagged, but those which aren't, simply won't be regarded as "preferred" but would still get selected if no preferred torrent is found.

obviously.. :8ball:

I'm thinking that it would be awesome if quality-grouping was applied to the results of .db.find().

IMO this should be a separate function. Most of the code to do this stuff is the stremio add-on in the repo, using output from db.lookup + db.get (essentially a db.find, but without getting all torrents at once), getting the picked file (the file in the torrent which corresponds to the query) and deciding if it contains a preferred tag (such as hd) in the .tag array.
Let's summarize how we imagine this and merge with the simplify API issue and roll out the events API and this at the same time as 0.2 release?
IMO if we have db.findOne(query, preferred), grouping by quali won't be necessary

Actually this is implemented in the addon


For CI Test: Refactor/load

What does this PR do?

Fixes # (issue)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In in short, see following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

Codecov Report

Merging #7 (5f47685) into master (41c9bee) will decrease coverage by 46.78%.
The diff coverage is 20.00%.

@@             Coverage Diff             @@
##           master       #7       +/-   ##
===========================================
- Coverage   90.38%   43.60%   -46.79%
===========================================
  Files         116      116
  Lines        8831     8717      -114
===========================================
- Hits         7982     3801     -4181
- Misses        849     4916     +4067

Flag
Coverage Δ

cpu
43.60% <20.00%> (-46.79%)
:arrow_down:

pytest
43.60% <20.00%> (-46.79%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ghtning/trainer/connectors/checkpoint_connector.py
22.22% <20.00%> (-64.79%)
:arrow_down:

pytorch_lightning/trainer/training_loop.py
20.00% <0.00%> (-76.43%)
:arrow_down:

...er/connectors/logger_connector/logger_connector.py
18.35% <0.00%> (-75.11%)
:arrow_down:

pytorch_lightning/callbacks/lr_monitor.py
23.52% <0.00%> (-74.12%)
:arrow_down:

pytorch_lightning/utilities/model_utils.py
26.66% <0.00%> (-73.34%)
:arrow_down:

pytorch_lightning/core/step_result.py
14.58% <0.00%> (-72.18%)
:arrow_down:

...ightning/trainer/connectors/optimizer_connector.py
29.03% <0.00%> (-70.97%)
:arrow_down:

...torch_lightning/trainer/configuration_validator.py
30.00% <0.00%> (-70.00%)
:arrow_down:

...ch_lightning/trainer/connectors/model_connector.py
23.33% <0.00%> (-70.00%)
:arrow_down:

pytorch_lightning/utilities/data.py
31.25% <0.00%> (-68.75%)
:arrow_down:

... and 74 more

Continue to review full report at Codecov.

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


Singularity should be able to handle registration, re-registration, and leadership changes without aborting

@wsorenson thoughts on tackling this? or are we happy with our abort strategy?

End-user opinion: the aborts are worrying but once you learn to stop fretting they really do not present any sort of urgent problem to us.

fixed in https://github.com/HubSpot/Singularity/pull/2032


Dartpad on Safari doesn't show flutter

This was working earlier this week on Wednesday, May 8th. I noticed it not working yesterday, May 9th.
When I try to run any flutter code in dartpad, it doesn't show anything.
What happened?
When I attempt to run any flutter code, it says it compiles, but then shows nothing. This does work in the other browsers though. I will also note that pure dart code also runs just fine.
Steps to reproduce problem
The code that I am attempting to run is the code that is generated when you click New -> flutter.
This is very reproducible, and have reproduced it on two different machines running safari. (a laptop and a Mac mini) All you have to do is try to run flutter code.
Additional info
Browser
Browser: Safari
Version: Version 17.4.1 (196<IP_ADDRESS>.14)
Are you using any extensions/plugins that affect website behavior
(particularly those that affect iframes, such as ad blockers)?
Not using any extensions
Are there any warnings or errors in your browser's JavaScript console?
If so, paste them below:
[Error] Not allowed to load local resource: blob://nullnull/main.dart.js.map
[Error] Not allowed to request resource
[Error] Cannot load blob://nullnull/main.dart.js.map due to access control checks.

Machine
Operating system: Mac
Version: 14.4.1 (23E224)
Your code
What code was in the editor, if any, when the failure occurred? You
can paste it in below:
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: Text('Hello, World!'),
        ),
      ),
    );
  }
}

DartPad's output
Did DartPad print anything to the console pane? If so, paste it below:
None
If you were running Flutter code, you can also paste an image of the
Flutter output directly into this bug report.
None
https://github.com/dart-lang/dart-pad/assets/145144088/ba71aa52-1838-46c1-af53-ae7b3152ef48

Same problem on macOS and Firefox 125.0.3

Thanks for filing an issue, this is fixed by https://github.com/dart-lang/dart-pad/pull/2965


Missing 1st gen Surface Laptop

Picking apart the 1st gen Surface laptop driver MSI installer it is only checking for:
SystemSKUs=Surface_Laptop

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

ID: 84214a7c-c350-e7df-b096-8509be06d4fe
Version Independent ID: a07d3fed-001f-4230-c5f7-c3a6caad3223
Content: System SKU reference (Surface) - Surface
Content Source: devices/surface/surface-system-sku-reference.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

Maybe I am misunderstanding your description, but is this something that can be corrected in the documentation?
Or does it affect the driver package file contents?

Sorry, to clarify:
The documentation currently does not contain any information for the first gen Surface Laptop, it only has the second and third gen Surface laptop devices.

@nixtar : Thank you for reporting this issue. Your suggestion has been followed up in Pull Request #6383 by @MaratMussabekov and the changes will migrate to the docs.microsoft.com pages within a few days.

@nixtar - Thank you for submitting feedback.
From our understanding, the issue has been resolved based on this merged commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/478792e9e8ca776076b12bf329f458565eef6c44.
Thank you for your contribution to make the docs better! Much appreciated!


allpix CMakeLists.txt cannot check ROOT compiled C++ version

CMake cannot check ROOT C++ compiled version using build flags:
mauricio.donatti@s-det05-l:~/allpix/allpix-build$ cmake -DCMAKE_INSTALL_PREFIX=../allpix-install/ -DCMAKE_BUILD_TYPE=DEBUG . ../allpix-squared/
-- Git project directory is dirty:
 fatal: not a git repository (or any of the parent directories): .git.
-- Building Allpix^2 version v3.1.0-2-ga552a3f89-dirty.
-- Building "DEBUG"
-- Installing to "/home/ABTLUS/mauricio.donatti/allpix/allpix-install"
-- Unit tests: 20 examples
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- Could NOT find Doxybook2 (missing: DOXYBOOK2_EXECUTABLE)
-- Could NOT find Pandoc (missing: PANDOC_EXECUTABLE)
-- Could NOT find Latexmk (missing: LATEXMK_EXECUTABLE)
-- Could NOT find Lualatex (missing: LUALATEX_EXECUTABLE)
-- Could NOT find Biber (missing: BIBER_EXECUTABLE)
CMake Error at CMakeLists.txt:200 (MESSAGE):
  Could not deduce ROOT's C++ version from build flags: -pipe -fsigned-char
  -pthread

-- Configuring incomplete, errors occurred!
See also "/home/ABTLUS/mauricio.donatti/allpix/allpix-build/CMakeFiles/CMakeOutput.log".
See also "/home/ABTLUS/mauricio.donatti/allpix/allpix-build/CMakeFiles/CMakeError.log".

Current implementation checks ROOT_CXX_FLAGS env variable. It would be better to check ROOT_CXX_STANDARD as shown in ROOT documentation.
This issue has been found on Ubuntu 22.04:
mauricio.donatti@s-det05-l:~/allpix/allpix-build$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

closed by a58d8509b8da04264dd4c2c54d2c12024ce7f038.
View https://github.com/allpix-squared/allpix-squared/pull/49


Add initial, basic end-to-end test of the toolkit

so that we can be somewhat assured that it's working.
I think we'd want to make some sample specs to check assignments against, and we'd probably want to use the --no-check flag to prevent network usage.
Um. I don't think we want to use SD's specs, because then we'd be providing sample homeworks.
Maybe we'd just use the hw1 spec, since that's "type in this code".

Closed by #47


Where the req type is defined when do backward?

Hi,
In Backward definition, if OpReqType &req is not what I want, how I can change it and where? @mli @piiswrong
Thanks

it's specified by grad_req in symbol.bind

rnn_cell_demo.py does not have mx.sym.bind to be called. Is there any example python to verify the grad_req of param and statecell can support kWriteTo?

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Rename submodule to not start with a period

GitHub doesn't deal well with submodule names that start with a period. In particular, it causes all calls to its create tree API endpoint to 422 with a GitRPC::BadGitmodules error.
The name of a submodule is simply for convenience, so there shouldn't be any reason to prefer starting it with a period to not.

That's weird - thanks for your help in debugging!

Pull Request Test Coverage Report for Build 545

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

Totals

Change from base Build 544:
0.0%

Covered Lines:
857

Relevant Lines:
1007

💛  - Coveralls


Relationship result sorting

This allows relationship results to be sorted by defining the following in the options:
"sort": {
    "field": "my_field",
    "direction": "asc"
}

You can add Closes #3617

Done


modulesync 4.0.0

modulesync 4.0.0

Not sure why PostgreSQL doesn't start on Ubuntu 16.04. It may be due to PIDFIle. https://github.com/voxpupuli/puppet-jira/pull/326 also broke Ubuntu due to bashisms. The next failure on Ubuntu 18.04 is that it doesn't recognize openjdk 11. Looks like the default version doesn't support that but recent ones do.
For now I'm giving up on this and someone who actually uses the module needs to step in.

Not sure why PostgreSQL doesn't start on Ubuntu 16.04. It may be due to PIDFIle. #326 also broke Ubuntu due to bashisms. The next failure on Ubuntu 18.04 is that it doesn't recognize openjdk 11. Looks like the default version doesn't support that but recent ones do.
For now I'm giving up on this and someone who actually uses the module needs to step in.

This is the only remaining issue preventing the tests from passing. PostgreSQL on Ubuntu 16.04 starts but systemd hangs at "activating":
root@ubuntu1604-64-1:~# systemctl status<EMAIL_ADDRESS>●<EMAIL_ADDRESS>- PostgreSQL Cluster 9.5-main
   Loaded: loaded<EMAIL_ADDRESS>disabled; vendor preset: enabled)
   Active: activating (start) since Sun 2021-02-14 07:56:53 UTC; 37s ago
  Process: 6281 ExecStart=/usr/bin/pg_ctlcluster --skip-systemctl-redirect %i start (code=exited, status=0/SUCCESS)
   CGroup<EMAIL_ADDRESS>           ├─6286 /usr/lib/postgresql/9.5/bin/postgres -D /var/lib/postgresql/9.5/main -c config_file=/etc/postgresql/9.5/main/postgresql.conf
           ├─6288 postgres: 9.5/main: checkpointer process
           ├─6289 postgres: 9.5/main: writer process
           ├─6290 postgres: 9.5/main: wal writer process
           ├─6291 postgres: 9.5/main: autovacuum launcher process
           └─6292 postgres: 9.5/main: stats collector process

Feb 14 07:56:53 ubuntu1604-64-1 systemd[1]: Starting PostgreSQL Cluster 9.5-main...
Feb 14 07:56:55 ubuntu1604-64-1 systemd[1]<EMAIL_ADDRESS>New main PID 6286 does not belong to service, and PID file is not owned by root. Refusing.
Feb 14 07:56:55 ubuntu1604-64-1 systemd[1]<EMAIL_ADDRESS>New main PID 6286 does not belong to service, and PID file is not owned by root. Refusing.

root@ubuntu1604-64-1:~# ll /run/postgresql/9.5-main.pid
-rw-r--r-- 1 postgres postgres 5 Feb 14 07:56 /run/postgresql/9.5-main.pid

root@ubuntu1604-64-1:~# cat /run/postgresql/9.5-main.pid
6286

:shrug:

We have a pidfile workaround in our templates which uses an older version of Ubuntu 16.04 but I'd prefer to drop Ubuntu 16.04. It's going EOL soon anyway.

This is green, but care should be taken. https://github.com/voxpupuli/puppet-jira/pull/345 is included and I've included an alternative to https://github.com/voxpupuli/puppet-jira/pull/341 as well.

@kenyon thoughts?

Looks good to me. Rebased on current master. Updated the Jira version in the alternative commit to #341.


Add a Gitter chat badge to README.md

OWASP/NodeGoat now has a Chat Room on Gitter
@ckarande has just created a chat room. You can visit it here: https://gitter.im/OWASP/NodeGoat.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

The badge is already added, I thin we can close this issue.

You right right.. Closing it..thanks


TypeError: Cannot read property 'borders' of undefined

Describe the bug
A message error "TypeError: Cannot read property 'borders' of undefined" is raised when a demo file is selected on URL https://xlayers.dev/#/upload
To Reproduce

Go to 'https://xlayers.dev/#/upload'
Click on 'Select a demo file'
Scroll down to 'any demo file'
See error

Expected behavior
I suppose to open the demo file
Screenshots

Sketch (please complete the following information):

version: N/A

Desktop (please complete the following information):

OS: WIN10
Browser: chrome
Version:  86.0.4240.111 (Official Build) (64-bit)

Thanks for reporting this issue. We will investigate it and keep you posted.

I can investigate if you want :innocent:

Go ahead @anediaz 😊 I will assign the issue to you. Thank you for looking into this.

@yamne-it  Did you found any solution ? Its still not working :-(

@yamne-it  Did you found any solution ? Its still not working :-(

@yamne-it  Did you found any solution ? Its still not working :-(

I have reported this issue and I haven't tried it again. I was waiting for some feedback since reading the comments above, @anediaz is looking into it.
I suppose she will get back to us when she found the bug or maybe what I was doing wrong 😀

@yamne-it  Did you found any solution ? Its still not working :-(

I have reported this issue and I haven't tried it again. I was waiting for some feedback since reading the comments above, @anediaz is looking into it.
I suppose she will get back to us when she found the bug or maybe what I was doing wrong 😀

Hello,
I'm sorry, I haven't had the time to look at this issue.
If you want to look at it you are welcome.
I'll try to look at it as soon as possible :-)

Hello,
I'm sorry, I haven't had the time to look at this issue.
If you want to look at it you are welcome.
I'll try to look at it as soon as possible :-)

Hello,
I've tried to reproduce the bug locally but I can't, I mean, everything works well.
I've tried with a macOs and with Ubuntu, and I don't see the message.
However, when I check in 'https://xlayers.dev/#/upload', it is present.
@nasiruddin-saiyed can you give me more information of the way to reproduce it please?
Thank you in advance,
Ane

Hello,
I've tried to reproduce the bug locally but I can't, I mean, everything works well.
I've tried with a macOs and with Ubuntu, and I don't see the message.
However, when I check in 'https://xlayers.dev/#/upload', it is present.
@nasiruddin-saiyed can you give me more information of the way to reproduce it please?
Thank you in advance,
Ane

Hello @anediaz,
Sorry for late response,
It's throwing error in
libs/css-codegen/src/lib/css-parser.service.ts
while extracting borders from styles.
Attached image shows the exact line of error.

Note: This error appears in production on few components while selecting any of the existing demo files. I've upload image while debugging.

Hello @anediaz,
Sorry for late response,
It's throwing error in
libs/css-codegen/src/lib/css-parser.service.ts
while extracting borders from styles.
Attached image shows the exact line of error.

Note: This error appears in production on few components while selecting any of the existing demo files. I've upload image while debugging.

Thank you @nasiruddin-saiyed for all this information!
As I can't see the bug in my local machine your explanation will help me a lot!
I'll try to work on it the next days, and I'll let you know.
Thank you :-)

Thank you @nasiruddin-saiyed for all this information!
As I can't see the bug in my local machine your explanation will help me a lot!
I'll try to work on it the next days, and I'll let you know.
Thank you :-)

Hello @nasiruddin-saiyed,
I have looked at the code and tried to debug the file you mentioned. I've selected one by one all the existing demo files but I can't reproduce the bug.
I don't know why sometimes styles is undefined, as it respects SketchMSLayer interface.
Everything looks good for me, so the only idea I have to avoid displaying this message is replacing this :
const obj = (current as any).style.borders;
by this:
const obj = (current as any).style && (current as any).style.borders;
In libs/css-codegen/src/lib/css-parser.service.ts
What do you think about it?

Hello @nasiruddin-saiyed,
I have looked at the code and tried to debug the file you mentioned. I've selected one by one all the existing demo files but I can't reproduce the bug.
I don't know why sometimes styles is undefined, as it respects SketchMSLayer interface.
Everything looks good for me, so the only idea I have to avoid displaying this message is replacing this :
const obj = (current as any).style.borders;
by this:
const obj = (current as any).style && (current as any).style.borders;
In libs/css-codegen/src/lib/css-parser.service.ts
What do you think about it?


Polyglot failover increase the number of shards to have ~15-30 seconds downtime during failover

Polyglot failover increase the number of shards to have ~15-30 seconds downtime during failover
Currently we see ~85 second and we cannot tell if there is a problem with the client or the server.
The idea is to see that the downtime during failover does not come from the client

added tests with 10 shards cluster


Adding new maintainers

Description
Adding @tandonks @shiv0408 @soosinha to maintainers list.
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@bowenlan-amzn @Hailong-am @RamakrishnaChilaka
Please provide your approval on this PR. (Also, please leave it open after approval)

Pending GitHub Request: Pending GitHub Request: https://github.com/opensearch-project/.github/issues/248


pull request for e2e test at 11/20/2016 05:26:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Tech support] How to get filename after a download has completed (Python)

[x] I've verified and I assure that I'm running youtube-dl 2018.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

Hello,
I want to download audio files using Python (using --extract-audio) and then get the final filename after youtube-dl / ffmpeg are done with it.
Example
subprocess.run([
                'youtube-dl',
                '--extract-audio', '--restrict-filenames',
                '-o', DL_DIR.joinpath(f'{song.spotify_id}.%(ext)s'),
                song.youtube_id
            ])

output-
[youtube] mMoVvCEYMKM: Downloading webpage
[youtube] mMoVvCEYMKM: Downloading video info webpage
[youtube] mMoVvCEYMKM: Extracting video information
[download] /home/dev/Projekt/encadio/downloads/English/4gLuKrWf0Ub3nwrRB0yJk7.m4a has already been downloaded
[download] 100% of 3.27MiB
[ffmpeg] Correcting container in "/home/dev/Projekt/encadio/downloads/English/4gLuKrWf0Ub3nwrRB0yJk7.m4a"
[ffmpeg] Post-process file /home/dev/Projekt/encadio/downloads/English/4gLuKrWf0Ub3nwrRB0yJk7.m4a exists, skipping

Now how do I know what the final filename (or just the file extension) was, after the download finished?
I could also do this, as suggested by readme
with youtube_dl.YoutubeDL(ydl_opts) as ydl:
    ydl.download(['https://www.youtube.com/watch?v=BaW_jenozKc'])

But I couldn't find the final filename in ydls attributes.
I could have my application work by just searching using song.spotify_id, but that seems a little janky?

Sorry, my bad. Didn't see the full example.
It's available like this
    def my_hook(d):
        print(d['filename'])

    ydl_opts = {
        'format': 'bestaudio',
        'progress_hooks': [my_hook],
    }
    with youtube_dl.YoutubeDL(ydl_opts) as ydl:
        ydl.download(['https://www.youtube.com/watch?v=BaW_jenozKc'])

please a complete example, I need to understand it completely

Just import youtube_dl I guess..

Well, well, you go there, rather I wanted to know what more options it offers, for example:
I want to download the subtitle
as after download, I convert to mp3 or other audio formats

Never tried doing subtitles, will try..
If you convert to other format, d['filename'] returns the filename for converted format


ApprovalBundle for Kimai 2

Hi Katja,
this PR brings the ApprovalBundle to the new major version of Kimai.
The changes took around 10 hours and I has to adjust so many different things, while also fixing a couple of bugs on the fly ... I know this is a terrible PR to review, due to the size, sorry 🤷

Annotation were replaced by Attributes
jQuery was replaced with Vanilla JS
Bootstrap 5 classes are used
Some of the PHP code was upgraded to 8 (e.g constructor promotion)
Adjusted code for compatibility with Kimai 2
Renamed translation files for better compatibility with different tools (and XLIFF standard)
Using core settings to fetch "user working hour" definition, which allowed to remove a lot of the settings

Do you think we can incorporate that PR and release it under a new major version?
Edit 1: Ups, I just saw the existing v2 branch... so sorry... I wasn't aware it existed ... I did not use any code from there.
Edit 2: I merged your latest changes and the new "overtime for all" report as well
Cheers
Kevin

ping @vitormattos and @sammaclennan - can you help testing this branch, to give Katja and myself some more confidence in the changes?
As I have written in the inital PR description, I did not see your WIP branch, which I am super sorry for 😢 but now it is too late and it seems we did the changes twice. To make it up to you: the bundle seems to work (at least in my Kimai 2 development environment).

Hi @kevinpapst,
thanks for this huge PR and also for enhancing the source. This enables me to learn more, so the source gets better and better. Give me a few days for the review - somehow these days are busy 🎅. As we had been working on the update in the other branch - the review should be not too tough.
As I plan for a longer time to support both versions (my customer stays with v1, many others use and want v2) - I will maintain two versions in two branches - v1 with priority. I had been initially thinking of supporting the V2 in a branch and stay with main in V1. It might make sense to switch though. Can the marked place reference the plugin-support for both versions using two different links (one main branch, one feature branch)?
Thanks and have great Christmas Days!

For the general workflow I would recommend:

to create a branch for v1 before merging this one
mention this branch and explain the different version in the README
create new releases for both branches under different major version and mention the supported Kimai version in the release notes

We can link wherever you want from the store, the current link points to the README.
And for maintaining both branches I would recommend that you always work with feature branches and PRs.
Then you can ping me and I will prepare the same PR for the main branch.
Might be easier, if you have no v2 setup for testing.

Hi Kevin, yes I will do so. I already started working on this. I have a minimal V2 instance up and running and will continue some testing. The "cache" classes are also an excellent process to enhance performance on unique queries. I will take this over for v1 as well. Thanks also for the ping opportunity - as will continue to work on 1 for some time that's very much appreciated - I don't expect major updates anyway.

The "cache" classes are also an excellent process to enhance performance on unique queries. I will take this over for v1 as well.

Definitely, could be used here pretty good. As you always know that the cache can be expired, as soon as someone submits a new approval request.
Well, I already did some optimizations which were not strictly related to the v2 and thought that the PR wouldn't get easier to read with even more "unnecessary” changes 😁 but we can look at that together later on!

Hi @kevinpapst,
Was this branch created from main or from kimai_v2_update?
Sounds that you created your PR from main because have a lot of changes that I already made at kimai_v2_update

I found the answer here: https://github.com/KatjaGlassConsulting/ApprovalBundle/issues/17#issuecomment-1868444855

Apart from the strange URL as mentioned above and the opportunity to remove the number indicator on how many approvals are open, the PR is working perfectly fine in my environment with my data.

Thanks again for all your support here. The version 2 support is now available on the main branch and version 1 is available on bundle_for_kimai_v1. I have decided to go with ApprovalBundle version 1.x.x for kimai 1 support and version 2.x.x for kimai 2 support. I am going to work on performance updates in January and probably include some minor settings which I should be able to do for 1 and 2. If there is something more complex coming I will ping you. Thanks for this option.
Wish you happy holidays and a good start into the new year.

Maybe would more clear: stable-kimai-v1 or only stable1 and would be nice to have a CONTRIBUTING.md file explaining about this pattern or maybe a wiki page of this repo.
What you think about this @KatjaGlassConsulting ?

Very strange, I did not receive any message about the PR being merged or your replies...
I think I pushed a couple of other changes after your merge.
Yeah, thank you Github 🤪 so I'll need to check and open a new PR^^
Thanks for merging @KatjaGlassConsulting 👍

Found the commits and created a new PR:
https://github.com/KatjaGlassConsulting/ApprovalBundle/pull/28

Is this my PR: https://github.com/KatjaGlassConsulting/ApprovalBundle/pull/20
We made the same changes. You didn't saw my contributions because was merged to branch kimai_v2_update. I think that @KatjaGlassConsulting merged using a rebase from my branch beucause I can see my commits at branch branch kimai_v2_update.
I think that the branch kimai_v2_update need to be deleted because sounds that is impossible to merge my contributions because will have a lot of conflicts and you already made all that I did at this PR.
But don't worry, the important is that now the code of this project was updated to be compatible with newest version of Kimai.

Hi @vitormattos, I will create a ignore/kimai_v2_update based on your branch as you branch shows very nicely the single steps to perform when migrating from 1 to 2. I very much appreciate you step-wise approach. Didn't had time to clean up the branches.

@KatjaGlassConsulting just ignore the branch kimai_v2_update for now. I made a work very similar to Kevin and will be near to impossible to recovery the work at branch kimai_v2_update.
Don't worry about this, is problems that could occur at our work as software engineer. We can create and destroy codes and we can don't use codes that we created and this isn't a problem. Is part of our work.
Only a good point that will be good is create a flow to contribute. If you want, I can create a draft PR about this creating a CONTRIBUTING.md file to we start a discussion over the suggestion of workflow. If you like, you can merge.

Hi @vitormattos, if you already have a skeleton for a contributing and could draft something, that would be nice yes. What I would like is that people open up an issue and always write there when they are working on something, so everyone can be aware.
The migration has been a super-big task which had not been working on for quite some time - as I am still in the V1 world, that's my focus and finding time is always a issue. So your and other contributions are very welcome. Unluckily it was taken up by multiples at the same/shortly after time. I would not expect something like this to happen again, especially as typically there are no major changes.

😃 This is the power of open source projects!


Billing Page - Require Opening Balance, Payment, Amount Charged, Ending Balance

instead of EB and Amount Changed
that should be
Opening Balance from Previous Month
+
Amount Charged - Total of current months expenses
Payment and Discounts - Total of all PAyment and Discounts
Ending Balance


feat: ✨ covalent resource and asset

Built an asset that fetches all mainnet project registry transactions. Appears to be working locally or inside reconfigured forked CI .
Manual config changes needed  for new CI workflow:

[ ] repository wide secret COVALENT_API_KEY set up in here.

New asset fetches ~3k transactions, which should cost about 300 covalent credits out of  100k monthly free tier.
Takes about 3 minutes to run, but in parallel with other assets doesn't affect overall speed to much.

What is needed for this PR to be ready? Happy to merge it even if not fully complete!

The only thing needed from your side:

repository-wide secret Covalent API key ${{ secrets.covalent_api_key }}

As per my changes, I will push them tomorrow + deconflict. Will let you know once this is ready.

If you want you can consider it ready to merge. Tested new version on the fork, and CI appears to be working, as long as COVALENT_KEY is set up first.
https://github.com/DistributedDoge/gitcoin-grants-data-portal/actions/runs/7485200208/job/20373252823
New behaviour:

not having a key at all will result in Error when trying make run or fetching assets in make dev.
having any random string as API key should materialize other assets except for this one
dagster run locally expects COVALENT_API_KEY, CI expects COVALENT_KEY
dagster throws helpful error message to let you know what it is missing though:

dagster._config.errors.PostProcessingError: You have attempted to fetch the environment variable "COVALENT_API_KEY" which is not set. In order for this execution to succeed it must be set in this environment.

Problems:

I could not find a way to make asset optional if triggered from asset job selecting  [*] like we do in make run.
DESIRED behaviour would be that if we don't have a key set up, an asset doesn't even try to materialize

I was hoping asset groups would be a solution, alas I don't think dagster asset selection language used by CLI and python is actually using asset groups at all.
@asset(
    compute_kind="Covalent_API",
    group_name="chain_data",
)

Back to the drawing board, strange that I didn't see this error maybe your covalent key wasn't pasted right?
dagster._core.errors.DagsterExecutionStepExecutionError: Error occurred while executing op "ethereum_project_registry_tx"::

requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api.covalenthq.com/v1/eth-mainnet/address/0x03506eD3f57892C85DB20C36846e9c808aFe9ef4/transactions_v3/page/1/

strange that I didn't see this error maybe your covalent key wasn't pasted right?

I still haven't added the Covalent API key. Doing that right now!

Alright, COVALENT_API_KEY is now on the CI environment! Sorry for the delay there!

If you could kindly squash before merging, or however Github calls it. I don't like leaving a mess in commit history.

Yes! In fact, let me make squashing the default in this repository.

Forked CI with my own API key inserted will succeed now, so the most likely cause of error here is environment mismatch between our versions.

Absolutely on rush to do so, but if you do happen to circle back here after the weekend:

make sure that the key is defined in secrets tab not variables
key is called COVALENT_API_KEY
key is pasted as is, i.e. cqt_something without any " quotes or anything

Weird, there is actually a COVALENT_API_KEY in the repo since last week.
Going to merge and see if it needs to update the CI on main for some reason.


[Feature request] auto-detect missing libstdc++.so.6 issue, and suggest fix or auto-apply fix

EDIT by @savil:
we resolved the immediate bug via being able to add stdenv.cc.cc.lib. However, the developer-UX here could be improved and this task is now tracking that:

we could auto-detect this scenario and suggest a fix or auto-apply the fix.
we also need a better story around locking and updating stdenv.cc.cc.lib.

Original bug report:
Current Behavior (bug)
Most (python) packages won't suffer from the problem I'm describing below, but some will.
Still, I think the problem can be addressed by devbox.
dagster is a popular python framework, whose installation provides a package and a executable.
What works:

first of all, dagster can be installed with your python pip example in the venv
it can be imported from the venv (i.e. import dagster works)

What doesn't work:

running the executable fails, due to not finding libstdc++.so.6.
In my experience, not finding that library is a pretty common error that executables installed via nix run into.

# in the venv
$ dagster
Traceback (most recent call last):
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/bin/dagster", line 5, in <mod
ule>
    from dagster.cli import main
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site-packages/
dagster/_module_alias_map.py", line 72, in exec_module
    base_module = importlib.import_module(self.base_spec.name)
  File "/nix/store/qpwrwhkz7hkp8069v369mclp3yd93p6v-python3-3.10.13/lib/python3.10/importlib/__init__
.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site-packages/
dagster/_cli/__init__.py", line 4, in <module>
    from .api import api_cli
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site-packages/
dagster/_cli/api.py", line 14, in <module>
    from dagster._cli.workspace.cli_target import (
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site-packages/
dagster/_cli/workspace/__init__.py", line 1, in <module>
    from .cli_target import (
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site-packages/
dagster/_cli/workspace/cli_target.py", line 29, in <module>
    from dagster._core.host_representation.code_location import CodeLocation
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site-packages/
dagster/_core/host_representation/__init__.py", line 9, in <module>
    from .external import (
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site
dagster/_core/host_representation/external.py", line 38, in <module>
    from dagster._core.host_representation.origin import (
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site
dagster/_core/host_representation/origin.py", line 16, in <module>
    import grpc
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site
grpc/__init__.py", line 22, in <module>
    from grpc import _compression
  File "/tmp/tmp.Y07SaqoKmV/.devbox/virtenv/python310Packages.pip/.venv/lib/python3.10/site
grpc/_compression.py", line 20, in <module>
    from grpc._cython import cygrpc
ImportError: libstdc++.so.6: cannot open shared object file: No such file or directory

Expected Behavior (fix)

Ideally, install the missing dependecy and/or export some missing Env Vars so it can find it
or at least to least inform the user: "hey, the dependecy you asked for installed a pkg (which will work), and an executable, and we're detecting that the executable will not work"

Why do I think this problem should be addressed by devbox ?
Imagine I didn't use devbox, and I had a global python installation in /nix/store.
I can create a venv off of that global python, run pip install dagster in the venv, and I'd be in a similar place: import dagster would work, but running the executable would fail.
devbox can be a step-up from that experience, and either fix or at least inform the user of the problem and suggest a solution.
As a side note, the above scenario is how I currently do things, except that the global python which I create venvs from is from asdf, because doing that will allow the dagster binary to work.
Additional context

devbox version

$ devbox version -v
Version:     0.7.1
Platform:    linux_arm64
Commit:      9444baeabcb69c2ec8d67ce57536a44171843d9d
Commit Time: 2023-10-19T19:11:54Z
Go Version:  go1.21.3
Launcher:    0.2.0

devbox.json

finding libstdc++.so.6 on my system

$ fd --unrestricted --ignore-case --absolute-path --glob "libstdc++.so.6" /
/usr/lib/aarch64-linux-gnu/libstdc++.so.6
# it's also in nix store itself, as I've installed gcc

@aidigital Thanks for filing this issue. Usually, the workaround for this libstdc++ not found is to do devbox add stdenv.cc.cc.lib. Does that work for you?
Thanks also for your suggestions about improving the overall experience for such a scenario. I agree the developer-UX here can be better.

@savil Thank you, that worked!
Just for posterity, it turns out there are 2 ways to solve the problem:

declare stdenv.cc.cc.lib into devbox.json

if you're a home-manager user, you can declare stdenv.cc.cc.lib in home-manager and export LD_LIBRARY_PATH=$HOME/.nix-profile/lib (in ~/.zshenv or the equivalent depending on your shell).
This is a bit more generic, as you no longer have to include that dependency into every devbox.json project that might need it.

@aidigital great. Glad to hear it worked.
Good point about the home-manager. When developing Devbox, we usually have a frame-of-reference that tries to make the devbox-project be independently runnable, and reproducible. This matters much more for folks collaborating on a project with a team, or want it to be reproducible for CICD. Of course, totally valid to also add it as a global package for convenience as long as you're aware of the trade-off and can say its worth it for your scenario!
Let me rename this task to track your other request of auto-detecting failed libstdc++ import error and suggesting a fix, or auto-applying the fix.

Try this workaround in your devbox.jsonl to get stdenv.cc.cc.lib from nixpkgs at the nixos-23.05 release version via its flake:
{
  "packages": [
    ...
    "github:NixOS/nixpkgs/nixos-23.05#stdenv.cc.cc.lib"
  ],
  ...

I'm not sure if the below is bug of devbox or not.
But basically I found using a specific version of gcc to be more reliable than stdenv.cc.cc.lib.
For example, here I'm using stdenv.cc.cc.lib in the devbox.json file:
{ "packages": [ "stdenv.cc.cc.lib" ] }

The above gives me gcc 12.3:
❯ devbox shell

❯ readlink -f ./.devbox/nix/profile/default/lib/libstdc++.so.6
/nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6.0.30

❯ which gcc
/nix/store/zlzz2z48s7ry0hkl55xiqp5a73b4mzrg-gcc-wrapper-12.3.0/bin/gcc

And if we use strings to look at what libstdc++.so.6 requires, we can see GLIBC_2.38 ...
❯ strings ./.devbox/nix/profile/default/lib/libstdc++.so.6 | grep ^GLIBC | sort | uniq
GLIBC_2.36
GLIBC_2.38  # 👈 oh oh
GLIBCXX_3.4.29
GLIBCXX_3.4.30
# ...

... however my machine has 2.36
❯ ldd --version
ldd (Debian GLIBC 2.36-9+deb12u3) 2.36

So in my scenario, I had stdenv.cc.cc.lib as well as<EMAIL_ADDRESS>I created a venv, installed dagster in it, activated the venv,
# note from the line below that I'm in both venv and the devbox shell
Edft.Data.DagsterGermanPipelines on  master [✓] via 🐍 v3.11.4 (venv) via ❄  impure (nix-shell-env)
❯ dagster --version
ImportError: /nix/store/ld03l52xq2ssn4x0g5asypsxqls40497-glibc-2.37-8/lib/libc.so.6: version `GLIBC_2.38' not found (required by /home/adrian/repos/Data-Pipelines/Edft.Data.DagsterGermanPipelines/.devbox/nix/profile/default/lib/libstdc++.so.6)

If I'm just in the venv but not in the devbox shell, it works, of course.
But I need to be in the devbox shell too, because I have other utilities in it, and that's the whole point of devbox, to open a shell and do your work inside it.
# note I'm just in the venv
Edft.Data.DagsterGermanPipelines on  master [✓] via 🐍 v3.11.4 (venv)
❯ dagster --version
dagster, version 1.5.8

Fix
Now, if instead of  { "packages": [ "stdenv.cc.cc.lib" ] }, I use { "packages": [<EMAIL_ADDRESS>] }, the libstdc++.so.6 file will ask for GLIBC_2.36 instead of GLIBC_2.38, so everything will work:
❯ strings ./.devbox/nix/profile/default/lib/libstdc++.so.6 | grep ^GLIBC | sort | uniq
GLIBC_2.36   # I _do_ have 2.36 on my system, so this will work
GLIBCXX_3.4.29
GLIBCXX_3.4.30
# ...

Notes:

this problem (stdenv.cc.cc.lib giving me a version of c++ shared object file which requres a version of c which my system didn't have) happened on this WSL Debian running in Azure

OS: Debian GNU/Linux 12 (bookworm) on Windows 10.0.19044 x86_64
Kernel: <IP_ADDRESS>-microsoft-standard-WSL2

On a different VM (the below specs) which also has glibc 2.36, until 1-2 weeks ago, stdenv.cc.cc.lib gave me gcc-wrapper-9.5.0, and this worked.
As of the time of this message however, it also gives me gcc 12.3, and same error happens.
OS: Debian GNU/Linux 12 (bookworm) aarch64
Host: Parallels ARM Virtual Machine Parallels ARM Virtual Platform
Kernel: 6.1.0-13-arm64

on both of those machines, totally outside of devbox, using home-manager  to install stdenv.cc.cc.lib (correctly, shall we say?) gave me gcc 12.2 not 12.3. Hence why I started this message with "this may or may not be a devbox problem".

This also means that in all fairness, I actually don't need either stdenv.cc.cc.lib or gcc in the devbox.json file.
But it feels like having them there shouldn't break things either.

@aidigital yeah, this Glibc version mismatch is an issue we've been working on. The underlying cause is a bit involved to explain, but it has to do with what version of glibc the nix packages were built by their maintainers. The glibc version installed on your system isn't relevant: nix packages are designed to be independent of the system by referencing all their dependencies in /nix/store.
We have a preliminary fix that was implemented in #1574. We know that it still has some bugs, so take it with a grain of salt.  So:

You could try patching your python package with patch_glibc: true as shown in that PR's summary.
Note, you'll have to convert the packages in devbox.json from a list to a map, as show in the PR's summary.
Unfortunately, this patch_glibc feature currently breaks the Devbox python plugin which normally automatically sets up your venv, so you'll also need to manually do that in a manner similar to the virtenv script in that PR's summary.

Hopefully, that will update your python and dagster to work with the latest glibc 2.38. Let us know if it does?

@savil, thanks for your suggestion.
I ended up having to temporarily create a venv with asdf due to some problems with the venv cretead by devbox.
Let me explain.
The relavant pkgs are these:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    "stdenv.cc.cc.lib"

I would create a venv, manually, then install dagster and pyodbc.
Here's where it gets good:

if from my shell I activated the venv and the devbox shell, I would be able to run my dagster pipeline which at some point use pyodbc to read from a mssql db
but when running the dagster-webserver binary which started the dagster UI and ran the pipeline, no matter in which shells I was running it from, I'd always get

"pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib '/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.3.so.2.1' : file not found (0) (SQLDriverConnect)")"

I tried playing with devbox shellenv to try and make it get the correct LD_LIBRARY_PATH etc, but no dice.
Maybe dagster-webserver strips away the env it receives, I don't know.

For more context, I just lost 2-3 hours banging my head over this in https://github.com/cgohlke/imagecodecs/issues/87.
Essentially, the python package imagecodecs silently fails with no output making it really difficult to tract to this issue.

Welp, that breaks nodejs. I am catching to the other issues. This seems like a very challenging problem..

Probably it's because stdenv.cc.cc.lib doesn't provide the same libraries that the executable was linked against.
Couple of thoughts:

can you try installing a different pkg instead of stdenv.cc.cc.lib;  e.g<EMAIL_ADDRESS>as  I mentioned above ?
or, as another workaround, you may need to unset the LD_LIBRARY_PATH and set it to what it was set before you ran devbox shell ?

gcc doesn't quite help, when ldd the that is breaking I get:
libc.so.6 => /nix/store/gqghjch4p1s69sv4mcjksb2kb65rwqjy-glibc-2.38-23/lib/libc.so.6 (0x00007ff492c16000)
        /nix/store/gqghjch4p1s69sv4mcjksb2kb65rwqjy-glibc-2.38-23/lib64/ld-linux-x86-64.so.2 (0x00007ff492f9b000)
libstdc++.so.6 => not found
...

with stdenv.cc.cc.lib I get
libstdc++.so.6 => /home/jpambrun/work/devboxtest/.devbox/nix/profile/default/lib/libstdc++.so.6 (0x00007f1dc53a0000)

Aslo stdenv.cc.cc.lib breaks nodejs@14, but not nodejs@16
On the positive side, devbox makes this very easy to test.

Similar to node, a newer version of python (including pandas) has better chances to work because it'll have been linked against the newer lib provided by  stdenv.cc.cc.lib.
I saw in your issue you're using "python": "3.9.10".
I was using python 3.11.5 and stdenv.cc.cc.lib, and it worked.
So I'd try bumping it if you're not otherwise restricted to that older version.

These versions, python 3.9 and node 14, are imposed by projects I am working on and have little agency over it.
The pip imagecodecs with python39 works only with stdenv.cc.cc.lib, but then node14 doesn't. So they end up being kind of mutually exclusive in a single devbox. I can of course have multiple independent devbox to work around this.
However, thinking out loud, these issues and the challenge in identifying/debugging them makes this nixos-based approach a bit less interesting/valuable.

@aidigital @jpambrun thanks for reporting these. Apologies for the delay in acknowledging your messages; I'd been away for some family time over Thanksgiving here in the US. Will chat with others on the team about the glibc issue as well, and how to pursue a fix.

Any updates?  I've been bitten by this too.

+1 on the above. I am really not sure if this is a combination of problems
the use of venv within devbox and the fact that you use use a specific version of stdenv.cc.cc.lib .
I have the following simple setup
`{
"packages": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>"stdenv.cc.cc.lib",
],
"shell": {
"init_hook": [
". $VENV_DIR/bin/activate",
],
"scripts": {
},

},
}
`
But I still end up on
``

same here
OSError: libstdc++.so.6: cannot open shared object file: No such file or directory

added "export LD_LIBRARY_PATH=./.devbox/nix/profile/default/lib" , and it worked.
{
  "$schema": "https://raw.githubusercontent.com/jetpack-io/devbox/0.10.1/.schema/devbox.schema.json",
  "packages": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>    "github:NixOS/nixpkgs/nixos-23.05#stdenv.cc.cc.lib"
  ],
  "env": {
    "VENV_DIR": ".venv"
  },
  "shell": {
    "init_hook": [
      "export DEVBOX_DEBUG=1",
      ". $VENV_DIR/bin/activate",
      "pip install -q -r requirements.txt",
      "export LD_LIBRARY_PATH=./.devbox/nix/profile/default/lib"
    ],
    "scripts": {
      "test": [
        "echo \"Error: no test specified\" && exit 1"
      ]
    }
  }
}

If you're using poetry then I'd suggest creating a separate wrapper flake for poetry which propagates the appropriate LD_LIBRARY_PATH variable to the package. I found that exporting LD_LIBRARY_PATH inside the devbox.json broke node binaries and it kept complaining about not being able to find GLIBC_ packages. The wrapper ensures that LD_LIBRARY_PATH is visible to only poetry
{
  description = "Poetry wrapper with LD_LIBRARY_PATH";

  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
    flake-utils.url = "github:numtide/flake-utils";
  };

  outputs = { self, nixpkgs, flake-utils }:
    flake-utils.lib.eachDefaultSystem (system:
      let
        pkgs = import nixpkgs { inherit system; };
        poetry-wrapper = pkgs.stdenv.mkDerivation {
          name = "poetry-wrapper";
          buildInputs = [ pkgs.poetry ];

          LD_LIBRARY_PATH = with pkgs; lib.makeLibraryPath [
            stdenv.cc.cc.lib
          ];

          buildCommand = ''
            mkdir -p $out/bin
            cat <<EOF > $out/bin/poetry
            #!${pkgs.bash}/bin/bash
            export LD_LIBRARY_PATH=${pkgs.lib.escapeShellArg "\$LD_LIBRARY_PATH"}
            exec ${pkgs.poetry}/bin/poetry "\$@"
            EOF
            chmod +x $out/bin/poetry
          '';
        };
      in {
        packages = {
          poetry = poetry-wrapper;
        };
        devShell = pkgs.mkShell {
          buildInputs = [ poetry-wrapper ];
        };
      }
    );
}

Setting LD_LIBRARY_PATH in init_hook has the unfortunate downside of breaking other things that use a different gcc version.
The wrapper flake has the unfortunate downside of triggering a compile of python. This seems to be quite the slowdown, not great for sharing with a team. If there is a way to shim things in without a slowdown, that'd be interesting.
For now, I've just created a shim that I link in the way of every binary potentially suffering from this issue.
devbox.json
{
  "packages": [
<EMAIL_ADDRESS>    "stdenv.cc.cc.lib"
  ],
  "init_hook": [
    "ln -sf $VENV_DIR .venv",
    ". $VENV_DIR/bin/activate",
    "export INIT_DEVBOX_PATH=\"$PATH\"",
    "export PATH=\"$DEVBOX_PROJECT_ROOT/bin:$PATH\""
  ]
}

bin/python-wrapper
#!/usr/bin/env bash

# This wrapper adds devbox package shared libraries to python. Notably, this
# includes stdenv.cc.cc.lib (C++) which is required by the grpc python module.
#
# The symlinks to the shim were created with:
# cd bin; ls "$DEVBOX_PACKAGES_DIR/bin" | grep py | xargs -n1 ln -sf python-wrapper

set -eou pipefail

export PATH="$INIT_DEVBOX_PATH"
export LD_LIBRARY_PATH="$DEVBOX_PACKAGES_DIR/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}"

exe=$(basename "$0")

# Prevent infinite loops
if [ "$exe" = "python-wrapper" ]; then
  exe="python"
fi

exec "$exe" "$@"

So, the problem is the python, not poetry.  Also, I really dislike the defaults devbox uses for poetry by making it a plugin.
This is the best solution I have found. I DONT RECOMMEND INSTALLING POETRY VIA DEVBOX. USE RAW NIXPKG.

Add pyenv - devbox add pyenv@latest
Install poetry via flakes - not the wrapper I mentioned before, but the raw poetry i.e.

// flake.nix
packages = {
  poetry = poetry-wrapper;
};

Use pyenv to install a python distribution. I recommend using conda's pre-compiled python - pyenv install miniconda3-3.11-23.11.0-1
Point poetry (installed by the flake) to this python distribution using poetry env use $(PYENV_VERSION=miniconda3-3.11-23.11.0-1 pyenv which python) and things will just work by default. VSCode's autocomplete, all python packages.

For now, I've just created a shim that I link in the way of every binary potentially suffering from this issue.

This solution avoids all the nix LD_LIBRARY_PATH issues, and doesn't pollute the PATH with un-necessary libraries.


Doesn't compile using erlang.mk

The app seems to need an endless list of dependencies. I've had to download a very large number of dependencies manually, well over 200 MB so far, and it is still complaining about missing more. Did this app really need to be so heavy, especially with Prometheus - maybe a bit ironic that one cannot use a Erlang package with getting Golang and over a dozen of Go packages.
It seems I'm missing something painfully obvious and that there is a more straightforward way of getting it to compile using erlang.mk?

The cause of the problem was using an outdated version of the rebar.lock file to manually include dependencies. The rebar.lock file has now been updated in the master branch, and Prometheus is no longer a dependency. The app works fine now.


Error Opening Wallet: "this.masterWallet" is null

2021-10-29 22:33:19,895 ERROR [JavaFX Application Thread] c.s.s.AppController [null:-1] Error Opening Wallet
java.lang.NullPointerException: Cannot invoke "com.sparrowwallet.drongo.wallet.Wallet.setChildWallets(java.util.List)" because "this.masterWallet" is null
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.io.db.DbPersistence.loadWallet(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.io.db.DbPersistence.loadWallet(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.io.Storage.loadEncryptedWallet(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.io.Storage$LoadWalletService$1.call(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.io.Storage$LoadWalletService$1.call(Unknown Source)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

Can you confirm:

Are you using Windows?
Were you using the View > Refresh Wallet function before this occurred?
Are there any errors in the log prior to this error?

It would help to narrow this issue down for a fix.
Unfortunately the wallet file itself is corrupt and will need to be recreated (as a new wallet) from seed/backup.

Using MacOS
I am not sure but think yes I was refreshing wallet

Thanks for the info. Nothing earlier in the log that may indicate what caused this? If so it would likely also have DbPersistence and saveWallet in the stacktrace.


deprecating BackendCompilationUtilities trait for object

This is to fix the backporting issue with #1572, which was caused by adding a method to the BackendCompilationUtilities trait.
Contributor Checklist

[ ] Did you add Scaladoc to every public function/method? N/A
[ ] Did you update the FIRRTL spec to include every new feature/behavior? N/A
[ ] Did you add at least one test demonstrating the PR? N/A
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you state the API impact?
[ ] Did you specify the code generation impact? N/A
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement

bug fix (backporting failure)

code cleanup

API Impact

This PR deprecates the BackendCompilationUtilities trait for an object of the same name.
Backend Code Generation Impact

None
Desired Merge Strategy

Squash: The PR will be squashed and merged (choose this if you have no preference.)

Release Notes

The BackendCompilationUtilities trait is deprecated for an object of the same name.
Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (1.2.x, 1.3.0, 1.4.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

These changes successfully passed backport compatibility tests against 1.3.x when I ran sbt +mimaReportBinaryIssues locally.


Compilation error

Hi Team,
I am new to Apache-Royale, I am trying to build a simple HelloWorld application, I have followed the steps as shown in Git. I am getting an error like  Unable to open royale-config.xml, Please find the below screenshot.

Hi @dileepnaduvinamani ,
I believe you may experiencing known issue if you are using 0.9.6 version. Try my workaround. This patch fix will be also available as part of upcoming Moonshine IDE release.

Hi @piotrzarzycki21
Thank You :) It's working fine with Hello World.


feature/independent time

Allows you to specify a time with the "watch" ⌚ emoji if the setting to differentiate between tasks and reminder emoji is turned on eg;
- [ ] Task ⌚ 10:00 📅 2021-09-17

I'm by no means a professional and not very familiar with the codebase, so this isn't very well implemented. I basically just forked this for personal use, but figured maybe you might want to pull it in, its just some nice QOL to make tasks a bit shorter and easier to use with the tasks plugin.
All the tests pass (on linux), I added a single test for the added feature, and I added info on how to use it (as well as the bug I've encountered with recurrence) into the docs.

Is it possible to add a time picker?


Now Playing functionality is lost shortly after install (can't prevent ASI from auto updating?)

Device name: Pixel 7 Pro
Rom name: Stock
Android version: 14 (June 2024)
Pixelify version: 3.0

Bug Description: shortly after installing, "Now Playing" works, but then it appears to be lost shortly after. I have a shortcut to access the history on my home screen and it changed to "App not installed", and the lock screen listener goes away too.
I suspect the root cause of this is "Android System Intelligence" auto updating, but contrary to the instructions, there is not an option in the play store to prevent it from doing so (unless there is an alternate method I have not found). I was able to find the app store listing from settings->apps (it does not readily come up in the play store search), but then the option to uncheck the box in the three-dot menu (which I used for the photos app), is simply not there.
I have experienced this twice, after uninstalling pixelify and updating the phone to a new monthly firmware, and then reinstalling pixelify, both the main module and the standalone for Now Playing, it was working normally for a bit, but a day later it is broken again.

same here. not the first time Now Playing has disappeared on my Pixel 6 Pro.
I use the Pixelify module only for the unlimited storage and set everything else to not install. The previous time Now Playing stopped working on my phone, I realized it was related to the Android System Intelligence. I simply uninstalled (updates) and updated it via Play Store again and got it working. However, this time round, doing the same did not fix anything.
I noticed that Android System Intelligence was also not updated when I went to view the app on Play Store (all apps > searched for ASI > view on Play Store).
Also on June firmware. Using APatch with Zygisk Next

Here the same issues on a Pixel 8. I discovered a day after installing Pixelify (only for the unlimited storage) that Now Playing isn't working at all. Android System Intelligence keeps crashing after disable/enable Now Playing on the phone. After unistalling Pixelify everythins works as it should.


Add Swift 4 support

Description

Motivation and Context

How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

@billabt I had not yet fixed the Xcode project for this PR in the way I did for the BlueSocket PR. Is this needed for this package? It looked like you had added similar fixes to BlueSSLService after merging that PR.


Update Docker Run command

Pull Request Type

[ ] ✨ feat
[ ] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[ ] 🔨 chore
[x] 📝 docs

Relevant Issues

resolves #xxx
What is in this change?
Describe the changes in this PR that are impactful to the repo.
Additional Information
Add any other context about the Pull Request here that was not captured above.
Developer Validations

[ ] I ran yarn lint from the root of the repo & committed changes
[ ] Relevant documentation has been updated
[ ] I have tested my code functionality
[ ] Docker build succeeds locally

resolves #754


Update config.toml

Added the SHA256 variable that was missing.

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
The checksum variable was missing.

Special notes for your reviewer:

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

cb18a94 Update config.toml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

cb18a94 Update config.toml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rajakavitha1 after the PR has been reviewed.
You can assign the PR to them by writing /assign @rajakavitha1 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rajakavitha1 after the PR has been reviewed.
You can assign the PR to them by writing /assign @rajakavitha1 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


FluxCD GitOps Integration

A request to enhance blueprints deployment options by adding an addon for FluxCD which will allow users to use FluxCD to manage their GitOps workflow.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Describe the solution you would like

Describe alternatives you have considered

Additional context

duplicate of https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/issues/26
Please feel free to add any feedback to this issue if interested https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/issues/114


Unable to complete Hedge Alchemy from cobweb recipe

The cobweb recipe for the cauldron seems broken, making the "Hedge Alchemy" quest of the Thaumonomicon unable to be completed. Not sure if this is a mod interaction or a TC bug.

Having the same problem.

I also have the same issue, 6.1BETA26

Im looking for a temporarily solution: (If you gonna try, dont try anything without a backup) if you open Thaumcraft-1.12.2-6.1.BETA26.jar with 7-zip or something like that and reach assets\thaumcraft\research\ folder there is alchemy.json there.  Open it with Notepad+ or something like that. search "hedge",  find HEDGEALCHEMY.stage.3 section and there is:
{                     "text": "research.HEDGEALCHEMY.stage.3",                      "required_knowledge":["OBSERVATION;ALCHEMY;1"],                      "required_craft":["minecraft:clay_ball","minecraft:string","minecraft:web","minecraft:lava_bucket"],                     "recipes": ["thaumcraft:hedge_tallow","thaumcraft:tallowcandles", "thaumcraft:hedge_leather",                                 "thaumcraft:hedge_gunpowder","thaumcraft:hedge_slime","thaumcraft:hedge_dye","thaumcraft:hedge_glowstone",                                 "thaumcraft:hedge_clay","thaumcraft:hedge_string","thaumcraft:hedge_web","thaumcraft:hedge_lava"]                 },
So, broken recipe is thaumcraft:hedge_web we can change the requirement or i dont know at this point i should search where are the recipes so we can add some essentia to cobweb.
Or maybe we can put different requirement like making "required_craft":["minecraft:clay_ball","minecraft:string","minecraft:web","minecraft:lava_bucket"], to "required_craft":["minecraft:clay_ball","minecraft:string","thaumcraft:alumentum","minecraft:lava_bucket"], so atleast maybe we can pass the broken quest with alumentum until a real fix.

The problem is incompatibility with ProjectE mod


Click on Start/Stop icon on main stack screen gives you a drop-down

Version - Master with reskin UI
Steps:

Create a Stack and add a Service
On main Stack page, click on the Start icon that is next to the Stacks' drop-down menu icon.

Results:
The drop-down menu appears.  This is the same when the icon changes to the Stop icon

Verified fixed - Master with newest reskin


Bug 2314454: sanitize connection pool key pod name

The csi-addons sidecar sanitizes the holder identity. The connection pool stores the mapping with key as the unsanitized name for csiaddonsnode, which leads to the failed to find the namespace where driver issue.
To address this, we should sanitize the csiaddonsnode name before entering it into connection pool.
(cherry picked from commit https://github.com/red-hat-storage/kubernetes-csi-addons/commit/4371d896ba88033f379ee9e47291a4ffeb2e5f81 and https://github.com/red-hat-storage/kubernetes-csi-addons/commit/7b4049db0de828894e709f8768395d81ee1f284f)

/lgtm
/approve


Cannot read properties of undefined (reading 'uri')

Using vscode to create a Quarkus occurred a problem. It is showing that 'Cannot read properties of undefined (reading 'uri')'.

Could you share yourproject please. is it a Maven or Gradle project?

Could you share your project please. is it a Maven or Gradle project?

Yes,Maven Project and My project is a initiatial project not edited.

@successismyonlyway have you again this issue?

@successismyonlyway I close the issue, please install the vscode-quarkus 1.18.0 which has been released at 26 August 2024, if you have again the problem, please reopen it.


Run tests on the new example

Hi @shym and @n-osborne, sorry for my (very) late answer. Actually, I was thinking about the folder examples to be a sort  of repository for "ongoing" case studies. This means you can use put there gospel specification that does-not-even-yet type-checks. So, I guess always running sanity tests on these examples might not be the best idea.
Maybe I should try to hide this folder, or maybe give it a more suggestive name?

comment.md

Thanks @mariojppereira.
Indeed, as a newcomer, a folder named examples would be the first place I look to learn how to write correct specifications. And I really think it is a very good idea to have that :-)
For specifications that are not (yet) corrrect, the test/issues folder may be a good place? We added it with @shym some time ago to track tests related to github issues (or at least, that was the idea, not completely sure we have been thorough with that).
Another idea would be an experiment folder (maybe test/experiment?).

I agree a different name would be better for WIP specs. I don’t mind that directory being visible as long as its purpose is clear (by its name and by a README).
Even for WIP specs where the typechecker will (initially) fail, I think it is important to keep track of it. Note that the tests we run do not require the file to type-check, but will just add a prologue with the gospel check error if any. This will be useful to help develop the typechecker to cover those new cases.

Long overdue. Merging.