Azure CDN : Change casing for subscription ID and API version

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
ASAP
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
ASAP
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[x] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@jorinmejia
The failure on go and python seems relate to description difference on https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cdn/resource-manager/Microsoft.Cdn/stable/2020-09-01/afdx.json#L5554-L5560

@weidongxu-microsoft,

For the SDK azure-sdk-for-go, we do not get any helpful error information. It only mentions this error here :

"[ERROR] this package does not exist even after the generation, this should never happen"

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=688319&view=logs&j=0303ead4-2e3b-557b-303e-fe8735d4d18f&t=b29b24f0-8be9-5e66-edce-54fd3565c09c&l=173

Perhaps this is a bug in the Go SDK validator?

For Swagger ApiDocPreview, we get an error saying the yml files could not be generated? Can you help us understand why?

For Swagger BreakinChange , we are only changing the casing on 2 parameters to maintain consistency. Do we still need a full ARM API review?

@weidongxu-microsoft,

For the SDK azure-sdk-for-go, we do not get any helpful error information. It only mentions this error here :

"[ERROR] this package does not exist even after the generation, this should never happen"

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=688319&view=logs&j=0303ead4-2e3b-557b-303e-fe8735d4d18f&t=b29b24f0-8be9-5e66-edce-54fd3565c09c&l=173

Perhaps this is a bug in the Go SDK validator?

For Swagger ApiDocPreview, we get an error saying the yml files could not be generated? Can you help us understand why?

For Swagger BreakinChange , we are only changing the casing on 2 parameters to maintain consistency. Do we still need a full ARM API review?

/azp run

/azp run

@ArcturusZhang This PR make some casing change on type name to make it consistent across 3 JSONs.

@ArcturusZhang This PR make some casing change on type name to make it consistent across 3 JSONs.  Let me know when you need it merged.

@jorinmejia Go SDK is OK with it. Let me know when you need it merged.

@jorinmejia Go SDK is OK with it. Let me know when you need it merged.

@weidongxu-microsoft, please merge the changes ASAP. Thank you.

@jorinmejia Go SDK is OK with it. Let me know when you need it merged.

@weidongxu-microsoft, please merge the changes ASAP. Thank you.

@weidongxu-microsoft, please merge the changes ASAP. Thank you.

@weidongxu-microsoft, please merge the changes ASAP. Thank you.


Stock of substituted template part variants does not show up in BOM

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

Describe the bug*
Hi
I have a template part CAP01 which has no stock. I have two variants of this CAP02 and CAP03 which have 100 pcs stock each.
When I open the part view of CAP01 I see a total stock count of 200 pcs. OK
I have CAP04 which is a normal part with no stock.
Now I have CAP04 in a BOM. I see zero in the Available column. OK.
On this position in the BOM I add CAP01 as a substitute part and allow variants.
However I still see zero stock in the BOM view and also in the Build Order-Allocate stock view.
I would expect to see 200 as I substituted CAP04 with CAP01 which has stock from the variants.
Is this a bug or a feature? May be I did not understand the Template/Variant system in the right way. Thanks in advance,
Michael
Steps to Reproduce
See description above.
Expected behavior
I would expect to see 200 as I substituted CAP04 with CAP01 which has stock from the variants.
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Inventree 0.8.4
Ubuntu 22.04.1 LTS
Relevant log output
No response

@SergeoLacruz the combination of "substitute part" and "allow variants" does not work together. The query structure becomes too complex when adding these multiple requirements together.
You can see here that the variant stock count works, but variant stock is not calculated "on the fly" for substitute parts.

Thanks for the clarification.And I even cannot allocate the stock in that case.
So I will look for another way that fits our design flow best. Thanks
Michael


feat(db) support unique constraint on foreign fields

Summary
Adds support for unique foreign key fields in schema like:
{ service = { type = "foreign", reference = "services", unique = true, }, },

Also generates all the normal unique DAO functions for unique foreign keys:

select_by_[service]
update_by_[service]
upsert_by_[service]
delete_by_[service]

Where [service] is the foreign field with unique=true.
This PR also adds new error invalid foreign key and changes the code to use it where it should.

Changed it to wip as I found out that *_by_* doesn't support table values such as foreign keys currently. The problem actually exists in strategies.

I removed wip label as:
https://github.com/Kong/kong/blob/master/kong/db/dao/init.lua#L431
That line has been there for long, so we don't actually support any foreign fields with composite key.

Let's double-check that select_by_[service] and friends work for DB-less

@hishamhm dbless unique foreign now implemented, and tests added.


fix error in readme

The README showed HTTP_HEADER as a constant, when it should be HTTP_METHOD

See: https://jira.duraspace.org/browse/FCREPO-1699


Fix windows issues with extract and pack

extract and pack currently have multiple issues on windows

why didn't I say what those issues where though


Samarth agarwal1/update doc

I have updated the doc to reflect the changes in this PR in candig-ingest: https://github.com/CanDIG/candig-ingest/pull/31
This PR should only be merged when the PR in candig-ingest has been merged.

It looks good - I am just thinking if we should stress that using a list to ingest multiple records of the same table as the preferred method.
There's two ways to do this, either we do not document the old way (having it in a totally separate entry), or we indicate that this is obsolete and is not recommended.

If there are any JSON files that use the old way (having it in a totally separate entry), then I think it might be a good idea to indicate that it is obsolete and not recommended for backwards-compatibility. Otherwise, we probably shouldn't document the old way because the docs are meant to be concise.

If there are any JSON files that use the old way (having it in a totally separate entry), then I think it might be a good idea to indicate that it is obsolete and not recommended for backwards-compatibility. Otherwise, we probably shouldn't document the old way because the docs are meant to be concise.

The sample json provided doesn't


mission-editing UI review.

Should be able to edit both template and solutions.

Why have duplicate tab?

Global settings should look global. Move the following into "global":

Adding new questions

Mission briefing

Global deployment

Should be able to rearrange questions.

Ger Hean says it's fixed.


d your bespoke

What went wrong?
Please give us a brief description of the problem, including the text of any error messages
What steps did you follow?
Change the steps below to match the commands that you ran

gem install backup --version 4.3.0
backup check
backup perform [OPTIONS]
Check the file that is produced by backup

How is your copy of backup configured?
Please attach the config.rb file that backup is using, and any relevant model files from the models/ directory
Tell us about the computer that runs the backup gem
Change the information below to match the details of your computer

Operating system: Ubuntu Server 14.04.5
Ruby version: 2.3.1
Tools or services used by backup: MySQL 5.7.9, GnuPG 1.4.16

Apologies, I was typing in the wrong window and triggered the right shortcuts to make an issue.


[Bug]: Shopify theme dev --live-reload seems to have no effect

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
shopify theme dev --live-reload off
should prevent automatic reloads.
Actual behavior
The argument seems to use hot-reload no matter what is passed.
Verbose output
No verbose out using the above command.

Reproduction steps

Run shopify theme dev --live-reload off
Make a changed to a watch file
Watch the opened browser tab reload

Operating System
MacOS Ventura 13.3.1
Shopify CLI version (check your project's package.json if you're not sure)
3.45.1
Shell
ITerm2
Node version (run node -v if you're not sure)
v18.15.0
What language and version are you using in your application?
No response

Nevermind I was using it on the wrong script.

Nevermind I was using it on the wrong script.


When using minimized view-models, fully charging the lead pipe blocks a good chunk of the screen

Intentional + if it's that obstructive change view-model positions / use min models.
Closing as not a bug.


Fix supported Ruby version in README

Claim is not actually true: various Ruby 1.9/2.x syntax usages in codebase
1.8.7 is no longer supported

REally? Where do we use 1.9 syntax in the core? I know, I switched tests to 1.9 partly, but the actual code should be 1.8-fine?

@apotonick

Where do we use 1.9 syntax in the core?

https://github.com/apotonick/representable/blob/master/lib/representable/parse_strategies.rb#L53
and yes, the tests of course…
Is it really worth maintaining 1.8-support?


Datadog Agent Docker image not collecting GCE labels as tags

Describe what happened:
No label associated to my GCE instance are being exported to datadog.
Describe what you expected:
While using datadog agent latest docker image, RepoDigests: datadog/agent@sha256:97359fbf552d3bfb55d051fda070f9d943b6ef41c8ca45b6d90b889b878cce79
What I expected was for the labels associated with my GCE instance, for example, "costcenter:production" to be exported by the datadog agent, as it says it does in this official link https://www.datadoghq.com/blog/monitor-google-compute-engine-with-datadog/ in the 'Drilling down with tags' section of the article.
Steps to reproduce the issue:
Setup GCE instance, add custom label (example costcenter:production), run datadog-agent as docker image. The instance will show up in the infrastructure page but will not be taged with the costcenter:production
Additional environment details (Operating System, Cloud provider, etc):
I was using a very simple n1-standard-2 instance with Debian9 as the OS, docker-ce installed using the official docker page steps and the latest docker image for the agent.

Hi @Leluke
What's the version of the agent tied to this sha256?
Some notes:
We are getting the hostname and tags from GKE by hitting these metadata API endpoints:

http://<IP_ADDRESS>/computeMetadata/v1/instance/name
http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname
http://<IP_ADDRESS>/computeMetadata/v1/?recursive=true

workload identity can block access to these endpoints so make sure it is not activated on your cluster or you give the rights to the agent's pod to access these endpoints.


Westlad/client rollback

Currently, nightfall-client does not respond to Rollback events.  This causes the problem that a rollback may remove a nullifier from the blockchain record.  This would mean that the corresponding commitment was no longer spent and thus could be spent 'again'.  With no rollback capability, nightfall-client will not, however, know this.  This will have the effect of locking up funds.
This PR fixes #88 i.e. the problem above. It makes nightfall-client respond to both Rollback and BlockProposed events.  Why does it need BlockProposed?  To complete a rollback, nightfall-client needs to know which block a nullifier is in, otherwise it can't tell which nullifiers it has to roll back.  BlockProposed gives it this information.
nightfall-client now recognises two states for a commitment: isNullified is set as soon as a commitment is spent.  This immediately prevents nightfall-client trying to spend it again. However, the commitment isn't 'properly' nullified until the nullifier appears on-chain, at this point nightfall-client also sets isNullifiedOnChain from -1 to the L2 block number of the block that this particular nullifier is in, so that it can be rolled-back in the future if needed.  Of course, we can still get a situation where isNullified = true locks a commitment from being spent again but the nullifier never appears on-chain. This isn't really nightfall-client's faulty though - it's up to the user application to make sure they sign and send blockchain transactions that it's given.
I had considered extracting the information needed for nightfall-client from nightfall-optimist and timber, to avoid another connection to the blockchain client.  However, this doesn't work because only nightfall-client has access to the zkp private key and, without this, it's not possible to associate a commitment with its nullifier.  This means that neither nightfall-optimist or timber can tell nightfall-client which commitments it should release for spending.
To make this all work, some changes were needed to nightfall-optimist.  That's because nightfall-optimist does a duplicate nullifier check but, quite reasonably, did not include the concept of a nullifier being removed in a rollback. To fix this rollbacks now delete rolled-back nullifiers in nightfall-optimist (this is a stronger removal than the isMined flag the went before).  There are some other, minor changes to the duplicate nullifier logic (nullifiers are stamped with a blockHash when a block is saved, rather than after checking the block, to avoid an intermediate state where a block is considered 'mined' but its nullifiers aren't). Rollbacks also delete any Transfer or Withdraw transactions that are rolled back.  This is needed because otherwise they may be re-proposed before the corresponding transactions that created the input commitments, which is a challengeable causality violation.  We don't want to give an innocent proposer this headache.  It will be nice, as a future enhancement, to give the transactor their fee back but we don't do that yet to avoid overcomplicating the PR (hopefully this is a small, rare loss).
This PR does not include a capability for nightfall-client to recover if it falls out of sync.  That's because this PR is already quite big.  We'll do the state-sync as a followup PR.  This isn't too mission-critical because falling out of sync will just mean that (in the event of a rollback) some commitments will remain un-spendable unnecessarily.

While I think it's a good idea to have client listen to the blockchain, I'm curious as to why this doesn't work.

I had considered extracting the information needed for nightfall-client from nightfall-optimist and timber, to avoid another connection to the blockchain client. However, this doesn't work because only nightfall-client has access to the zkp private key...

It requires a small modification of the transactions collection to include blockNumberL2 (which incidentally may be needed for #94 and/or #95). Can't client request all transactions that optimist has (regardless of mempool status) and :

Filter transactions by the commitments + nullifiers it has stored locally(these are transactions it cares about)
if there are commitments that are not in any transactions then isNullified: false and isNullifiedOnChain: -1
if a commitment is in a transaction marked as mempool:false then isNullifed: true
if a nullifier is in a transaction that has  a blockNumberL2: x then isNullifiedOnChain: x.

Updating can either be through regular long-polling by client to optimist or through a pub/sub websocket where optimist can push changes to it's transactions collections.

Yes, that's quite true.  I was a bit imprecise.  What I meant was that Client can't simply do a query to Optimist for the information; it can't ask 'give me the spend status of this commitment', it still has to process blockchain information itself.  In the method you describe it's effectively using Optimist as a proxy server for connecting to the blockchain client. There seems no advantage in routing like that, other than to move load from the blockchain client to the Optimist server, given that the blockchain client already has a suitable subscription interface.


Feature: partitionByComment support line and block

What rule do you want to change?
any rule support partitionByComment
Describe the problem
Mostly is issue mixed with jsdoc.
Comments are used to explain code but also causes sorting behavior unexpected.
Code example
With sort-objects config to { type: "alphabetical", order: "asc", partitionByComment: true, }
export const foobar = {
  foo: 'foo',

  /**
   * This is bar
   */
  bar: 'bar',
}

If partitionByComment: 'line' is supported. It can be fixed automaticly.
Additional comments
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Hi @ntnyq, you can also fill partitionByComment with a pattern or list of patterns instead of true, could it solve your issue?

Hi @ntnyq,
I think it's a good use case.
You can also fill partitionByComment with a pattern or list of patterns instead of true.

Didn't notice it supports string pattern before. However, as I tried, it only match the comment content but not comment type.

Yes, indeed it proposes just a workaround.
Did you try a regex which excludes multiline comments, e.g. partitionByComment: "^[^\n]*$"

Yes, indeed it proposes just a workaround.
Did you try a regex which excludes multiline comments, e.g. partitionByComment: "^[^\n]*$"

Yes, partitionByComment: "^[^\n]*$" works fine.

Still, we can enhance the partitionByComment schema to allow config like:
type PartitionByComment =
	| boolean
	| string
	| string[]
	| {
		type?: 'line' | 'block',
		pattern?: string | string[]
	}

Still, we can enhance the partitionByComment schema to allow config like:
type PartitionByComment =
	| boolean
	| string
	| string[]
	| {
		type?: 'line' | 'block',
		pattern?: string | string[]
	}

I think that
type PartitionByComment =
	| boolean
	| string
	| string[]
	| {
		line?: boolean | string | string[]
		block?: boolean | string | string[]
	}

Agreed. It's better.


Poorly Documented

The documentation is not proper. The example is outdated. On the pub.dev, it shows the latest code, but not the entire code. The assets folder is missing. There are no filters, masks etc. The code in example/main.dart still is old from the previous library: rwa_deep_ar.

check the dev branch for latest code

Thanks for that


Add AWS partner badge

Fixes: https://github.com/pulumi/marketing/issues/32
I put the badge in the hero because after playing around a bit it seemed like the best place for it to go, but I can be convinced of a different spot. I had struggled trying to put it somewhere where it would look "seamless" but I think I landed in an alright place.

this looks pretty out of place visually, @isaac-pulumi do you know if the black top-border and shadow on the card you included in the issue at necessary branding to carry over?
id also suggest reducing the size a bit and placing it above the buttons.

this looks pretty out of place visually, @isaac-pulumi do you know if the black top-border and shadow on the card you included in the issue at necessary branding to carry over?
id also suggest reducing the size a bit and placing it above the buttons.

The logo is what AWS provides, so, we probably should not alter it.  I agree that it can be smaller -- @zchase are you able to make that change?

@isaac-pulumi @susanev How does the new preview look?

can we put it above the buttons? if not, or if not easy im good to merge.


amend metadata update writes to only target primary node, not CCRs

TENTATIVE - NOT TO MERGE
🗒 Summary
Limits document update writes to registry proper, and not any cross-cluster nodes
⚙ Test Data and/or Report
Unit tests pass.  Manually tested against prod (still feels dirty to write)
♻ Related Issues
fixes #34 iff this is the intended behaviour

Closing no-op - this is not the desired approach.


Fix bulleted list on expander page

https://service-manual.nhs.uk/design-system/components/expander
The bulleted list in When not to use an expander doesn't read right. Needs tweaking.

@sarawilcox Would you be happy with the attached?

PR is here if you are! https://github.com/nhsuk/nhsuk-service-manual/pull/1811/files

Nice, thanks.


pull request for e2e test at 12/26/2016 01:15:08

:white_check_mark: Validation status: passed
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.


Having an Issue running Tox

Whenever I try to run pipenv run tox it tries to run /venv/bin/python -m pipenv graph. Basically the same as running pipenv inside pipenv failing because pipenv isn't a dependency. I have a temporary work around by installing pipenv as a --dev dependency, but was wondering if this was an issue with how tox gets executed from within pipenv due to how tox-pipenv works?
jacobhowell@Jacobs-MacBook-Pro-2 ~/N/nal-ml> pipenv run tox
Loading .env environment variables…
ERROR: invocation failed (exit code 1), logfile: /Users/jacobhowell/NotActivelyLooking/nal-ml/.tox/py36/log/py36-4.log
ERROR: actionid: py36
msg: envreport
cmdargs: ['/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/bin/python3.6', '-m', 'pipenv', 'graph']

ERROR:  Traceback (most recent call last):
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pipenv/vendor/pipdeptree.py", line 16, in <module>
    from pipenv.vendor.pip_shims import get_installed_distributions, FrozenRequirement
ModuleNotFoundError: No module named 'pipenv'

Traceback (most recent call last):
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/bin/tox", line 11, in <module>
    sys.exit(run_main())
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/session.py", line 40, in run_main
    main(args)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/session.py", line 46, in main
    retcode = Session(config).runcommand()
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/session.py", line 415, in runcommand
    return self.subcommand_test()
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/session.py", line 610, in subcommand_test
    self.runenvreport(venv)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/session.py", line 622, in runenvreport
    packages = self.hook.tox_runenvreport(venv=venv, action=action)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pluggy/hooks.py", line 258, in __call__
    return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pluggy/manager.py", line 67, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pluggy/manager.py", line 61, in <lambda>
    firstresult=hook.spec_opts.get('firstresult'),
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pluggy/callers.py", line 201, in _multicall
    return outcome.get_result()
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pluggy/callers.py", line 76, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/pluggy/callers.py", line 180, in _multicall
    res = hook_impl.function(*args)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox_pipenv/plugin.py", line 167, in tox_runenvreport
    output = venv._pcall(args, venv=False, action=action, cwd=basepath)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/venv.py", line 409, in _pcall
    redirect=redirect, ignore_ret=ignore_ret)
  File "/Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/lib/python3.6/site-packages/tox/session.py", line 212, in popen
    "%s (see %s)" % (invoked, outpath), ret)
tox.InvocationError: InvocationError for command /Users/jacobhowell/.local/share/virtualenvs/nal-ml-OzYvifs4/bin/python3.6 -m pipenv graph (see /Users/jacobhowell/NotActivelyLooking/nal-ml/.tox/py36/log/py36-4.log) (exited with code 1)

This plugin should be used outside of pipenv. Don’t use pipenv run tox because it’ll cause the loop you saw. Just call tox within the venv

So should I run something pipenv shell --> tox or just run tox from the application directory?

nm I found out haha, I need to run pipenv shell and then tox. Why is that by the way if you don't mind me asking?

Ahh ok thank you. For some reason now when running pipenv run tox it works, i think it was due to when I ran pipenv shell, tox it may have fixed something which is weird, from now on I'll switch to using pipenv shell, tox


Allow the Value type to specify what it can be set to

NOTE: everything here assumes that #259 will be fixed. For testing purposes, I have modified the StateObject type to the following, but everything here should work regardless of the fix used.
export type StateObject<T> = Dependency & {
	type: "State",
	kind: string,
	_typeIdentifier: (never) -> T
}

The Problem
(all code samples shown best work in strict mode)
Currently in Fusion, the Value type can be converted so that its generic can be made looser. This means that the following code is allowed:
local foo: Fusion.Value<string> = Value("foobar")
local bar: Fusion.Value<string | number> = foo

While this may seem fine at first glance, it can be a problem, specifically for functions that make use of :set(). Consider the following contrived example:
local function modifyValue(val: Fusion.Value<number | string>): ()
	local currentValue: number | string = peek(val)
	val:set(tostring(currentValue) .. "-" .. type(currentValue))
end

local bar: Fusion.Value<number | string> = Value(1)
modifyValue(bar) -- This is completely fine and will never cause problems

local baz: Fusion.Value<string> = Value("baz")
modifyValue(baz) -- This is completely fine and will never cause problems

local foo: Fusion.Value<number> = Value(5)
modifyValue(foo) -- This should not be allowed

print(peek(foo) + 5) -- Errors, but doesn't give a type error

Even if Value:set() was correctly typechecked (it isn't currently), this would still be allowed by the current system. The problem is that both ends see it as okay, but as a whole it isn't.
From the perspective of the code that is calling the function, foo can contain number, which can be made looser into number | string, so passing it into the function is allowed. From the perspective of the function, val can contain either a number or a string, so setting it to a string should be allowed. However, looking at the whole code, it is obvious that it will error, as foo gets set to be a string, and the code that handles foo doesn't expect that.
The only "fix" for this that uses only one generic type would be to make it so that the Value type cannot be changed whatsoever, neither by loosening it nor by strictening it. However this limits what code can do. Consider the baz variable. Passing it to modifyValue would never cause any errors, but with the proposed immutability of the Value type, it wouldn't be allowed. This also causes problems with the creation of Value objects, as the inferred type will likely be stricter than the actual type you want (this is my guess as to why Value:set() isn't currently typechecked).
Potential Solution
To solve these issues, a second generic type could be used to separate what a Value may contain and what a Value can be set to. For demonstration purposes, I will change the Value<T> type to Value<T, S>, where T represents what peek or use can return, and S represents what :set() can be called with. Value<T, T> would be similar to the current Value type.
The T type would behave like it currently does, and can be made looser but not stricter. This means that number can become number | string, but not vice versa. The S type would behave the opposite; it can be made stricter but not looser. This means that number | string can become number, but not vice versa.
A lot of the time (especially for variables), T and S will be the same, so to simplify this, the S generic should default to T.
The reasoning for why these types behave this way can be seen by examples. Let's try to fix the previous problematic code. We want to say that modifyValue can handle val containing either a number or string, but also warn that it will set val to contain a string, so any code relying on val must be able to handle that.
local function modifyValue(val: Fusion.Value<number | string, string>): ()
	local currentValue: number | string = peek(val)
	val:set(tostring(currentValue) .. "-" .. type(currentValue))
end

local bar: Fusion.Value<number | string> = Value(1)
modifyValue(bar) -- No type errors

local baz: Fusion.Value<string> = Value("baz")
modifyValue(baz) -- No type errors

local foo: Fusion.Value<number> = Value(5)
modifyValue(foo) -- Type error

From the bar variable, we can see that S=number | string can be converted to S=string without issue. This makes sense, as if val is allowed to be set to either a number or string, then only setting it to a string is fine.
From the baz variable, we can see that T=string can be converted to T=number | string without issue. This makes sense, as if the function can handle val containing either a number or string, it can handle val only containing a string.
Implementation
The current Value type looks like so:
export type Value<T> = StateObject<T> & {
	kind: "State",
 	set: (Value<T>, newValue: any, force: boolean?) -> ()
}

Since the proposed new behavior of T is the same as the current T, we don't need to modify the generic. For implementing the S generic, we should specify the default as T, and change the newValue: any to newValue: S. Since S would then be the parameter of a function, it can only be made stricter, not looser. The final code would be so:
export type Value<T, S=T> = StateObject<T> & {
	kind: "State",
 	set: (Value<T, S>, newValue: S, force: boolean?) -> ()
}

A small flaw with this is that, while S is assumed to be a subset of T, nothing is stopping you from not making it one. A potential solution would be to change the StateObject<T> to StateObject<T | S>. This would change what T represents (peek and use could return more than just T), but would make sure that code can handle anything that the Value can be set to, and even works fine when S is any. If we want to do so, the version of the code would be so:
export type Value<T, S=T> = StateObject<T | S> & {
	kind: "State",
 	set: (Value<T, S>, newValue: S, force: boolean?) -> ()
}

In the init.lua for the library, the type should be changed as well:
export type Value<T, S=T> = PubTypes.Value<T, S>

The Value constructor must be fixed. Since it creates a new Value, no code will rely on it only being set to the inferred type, so it is safe to make S be any (this is necessary, as the inferred type T will likely be stricter than what you want), like so:
Value: <T>(initialValue: T) -> Value<T, any>,

I'm really grateful for the detail here since I'm not really well versed in Luau type syntax. This definitely was an oversight.


Does not function.

Title.
Due to Discord switching from Babel to SWC, this breaks any and all plugins and themes.
Please update this to work with BD again.

This is a known issue with the new discord update and has been fixed with BD update v1.8.0 released today, please update your BD
See https://github.com/BetterDiscord/BetterDiscord/issues/1417

I am updated already.


Should we move query documentation to deepcase subsection?

https://github.com/deep-foundation/documentation/blob/0a1a58a182d56f12cb73949b24d04ec9f6437c0d/freephoenix888/core-package-subsection/core-package-subsection.tex#L119-L120

@ivansglazunov Query link is used only on client side (UI) or it may be used on server too (for example for portals into another Deep instances)?


v2022.07.0 release

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Of course the bot just made its PR. Closing this one and I'll merge that one.


Async overloads source generator

I took a crack at writing a source generator to replace the AsyncOverloads.t4 template. This is a follow up to my PR #1545.
Details
The source generator looks for methods annotated with the [GenerateAsyncOverload] attribute.
It generates a public method with the same signature, return type, generic parameter constraints, etc. that calls the annotated method.
The generator even copies the XML documentation to the public method. 🤓
API Diff
I used Microsoft.DotNet.GenAPI (the tool generates a C# file representing the API of an assembly) to ensure that I didn't accidentally break the API surface.
A pre-generated diff is available in this gist. The only thing that changed is that the comparer parameter in the generated methods is now marked as nullable too which is a good change I think?

Instructions for verifying the API diff

Install the Microsoft.DotNet.GenAPI package (this requires adding a custom NuGet feed)
Here's a .patch file that installs Microsoft.DotNet.GenAPI (can be applied using git apply <patch-file>).
Switch to the main branch
Generate an API snapshot before the changes:
dotnet build /p:GenerateReferenceAssemblySource=true /p:GenAPITargetPath=System.Linq.Async-before --framework netcoreapp3.1 --no-incremental Ix.NET/Source/System.Linq.Async
Switch to this PR's branch
Generate an API snapshot after the changes:
dotnet build /p:GenerateReferenceAssemblySource=true /p:GenAPITargetPath=System.Linq.Async-after --framework netcoreapp3.1 --no-incremental Ix.NET/Source/System.Linq.Async
Compare the changes:
git diff --no-index -- Ix.NET/Source/System.Linq.Async/System.Linq.Async-before Ix.NET/Source/System.Linq.Async/System.Linq.Async-after

Unrelated changes
I found that having a solution filter that only opens projects needed for System.Linq.Async to be really helpful while working on System.Linq.Async. I can revert the commit ba8ba26 if you don't want the solution filter checked into the repo.

Thanks for your contribution. This simplifies and modernizes the code significantly and sets a good example for future source generators in this space (e.g. the generation of expression tree based "queryable" variants of operators, which is a bit more involved).


Sign in to asura scans for subscription

Source name
Asura Scans
Source language
English
Describe your suggested feature
The ability to sign in to our subscription for asura scans.
Other details
Extension name: Asura Scans (lang: en; package: eu.kanade.tachiyomi.extension.en.asurascans)
Extension version: 1.4.42 (lib: 1.4; version code: 42)
NSFW: false
Update available: false
Obsolete: false
Shared: true
Repository: https://raw.githubusercontent.com/keiyoushi/extensions/repo
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I have updated the app to version 0.15.3.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

There should be no need to do any modifications for this. Just open the webview from AsuraScans extension and login
(this process worked for logging into my kavita server trough extension if I remember correctly)

The extension updated and now working

Closing in favor of #6614
As mentioned before, sign into your Asura account through WebView, then you should be able to view whatever paid content you have access to.


Graceful draining of connections

This is the code we use in a project to make sure Cowboy closes down gracefully when the application stops. To do this, we have a listener bound to http_api and we have an application callback using prep_stop/1 to prepare the application for stopping gracefully:
prep_stop(_) ->
    ranch:set_max_connections(http_api, 0),
    drain_connections(10),
    [].

The helper drain_connections/1 runs the following loop:
drain_connections(0) -> ok;
drain_connections(N) ->
    timer:sleep(1000),
    case ranch_server:count_connections(http_api) of
        0 -> ok;
        K when K > 0 ->
            lager:info("finishing work on active connections: ~p connections left", [K]),
            drain_connections(N-1)
    end.

It would be really nice to have some kind of "official" support for this kind of thing, so we didn't have to go peek inside ranch. I'm also not sure this is entirely the right way to go at it.
The reason this is nice to have is that if you close down the system, then connections are finished while no new connections are made. Once drained, the application is stopped for real. This means any dependencies the app might have on correct operation is torn down after the last connection has been drained. It avoids races when you stop a node to deploy a new version of the code.

Thanks. I can base a test on this and then implement something matching the test.

Any updates for this?

+1 I just had a discussion about zero-downtime deploys with Kubernetes and Elixir/Phoenix and I think cowboy is probably the right place to put it.
When Kubernetes is ready to cycle your app/pod, it sends a SIGTERM to your app so you can perform pre-shutdown tasks and drain connections. No new requests go to your app during this time. 30s later, if your app is still running, it sends a SIGKILL and brutally kills the app.
The problem is Elixir/Phoenix seems to shutdown immediately after receiving the SIGTERM. There is a discussion about adding connection draining to Phoenix, but it was rejected. See https://github.com/phoenixframework/phoenix/issues/1742
Regardless of whether anyone has time to implement it, do you think cowboy is at least the right place to do it?

Just putting in my 2 cents that I like this idea; also a disclaimer that I'm currently being bitten by it on a production web app whenever I do a CI deploy...

Cowboy is not the right place to do things like this, Ranch is.
The way you describe, where something external (load balancer etc.) holds off sending new connections while you effectively gracefully restart the listener. I am not really interested in this because it only works for the more complex setups. If you don't have a load balancer, you don't want to wait before accepting new connections. It has to happen even while older connections exist.
What I would like to have is a way in Ranch to close/reopen the listening socket with new options. The existing supervision tree would stay, and Ranch would just propagate the changed socket everywhere it's needed. New and old connections would continue working side by side.
The end result is that if you don't have a load balancer you have a very minimal interruption in accepting connections but existing connections stay alive, and if you do have a more complex setup then you can do this update in a few milliseconds instead of waiting for connections to slowly be dropped. (I do not know Kubernetes so I can't say if it would keep connections alive though. It depends on your deployment. If it just stops sending connections and then resumes sending them later without touching existing connections, no problem.)
I have no plans for this before Ranch 2.0 though. There's an old ticket, https://github.com/ninenines/ranch/issues/83 and I have no plans to work on this at the moment, at least not when Cowboy 2.0 still needs heavy maintenance.

@essen thanks for the thoughtful response!
I may be misunderstanding you, but I don't think "wait before accepting new connections" is actually something we're looking for. When we deploy, we bring up a new instance that immediately starts serving requests. Then, we stop sending requests to the old instance, drain requests, and then terminate it. We're not really to "restart" the app at all. We bring up a brand new one and destroy the old one.

Ah right. You want a graceful_stop_listener, and I'm talking about a graceful_restart_listener. Well the good news is that they're not incompatible goals.

Ah awesome :) would you still say that the graceful_stop_listener should be implemented in ranch and not cowboy?

Yes everything that has to do with listeners is Ranch's territory. Cowboy only has some shortcuts.

The most recent commit of Ranch has the ability to suspend listeners (killing the listening socket but leaving connections alive). This is a first step toward a graceful drain. Not sure more should be done. Please look it up!

Can't wait for this to be implemented 👍

Is someone working on that issue? Our Elixir pods are being killed instantaneously

Has there been any talk about how to handle Keep-Alive connections? Ranch will suspend the listener and wait a configurable amount of time before force shut down, but the keep-alive connections are still able to send requests and they will be happily processed by ranch even if the listener is suspended.

For existing connections the Cowboy processes should handle the shutdown exit signal or similar and there's more work to be done on that.

Thanks @essen . For follow up for other readers (I hate not coming back with a solution after posting a problem):
I ended up setting a value in an ets table that indicates that any open connections should be terminated upon their next request (https://github.com/pushex-project/pushex/blob/master/lib/push_ex_web/config.ex#L11). A "drainer process" which suspends ranch listener also sets this value. This value is then checked in each API request to see if it needs to send a close header (https://github.com/pushex-project/pushex/blob/master/lib/push_ex_web/controllers/push_controller.ex#L31).
This works great for the particular application I'm working with and caused a bunch of errors on shutdown to 0 errors on shutdown.

Cowboy now has graceful shutdown of HTTP/2 connections, but it can't be triggered by the user just yet. Still it shouldn't be much work needed to do it for both HTTP/1.1 and HTTP/2 since the mechanisms are already there. For Websocket the mechanism is missing and it will need to be added.

@essen which version of cowboy are you targeting for these changes? Then I can add a notice to the readme of ranch_connection_drainer.

I'm not sure yet. Currently working on 2.7 but I can't promise this will be in it.

Ok no worries. If you update this when you know then I can just add it then :+1:

Considering the scope of this ticket is still fairly large it won't make it into 2.7. However I think it should be worked on soon after 2.7 so that the changes are available for testing as long as possible before 2.8.

In our use case, we have very long-lived HTTP/2 connections, used for machine-to-machine communication (5G mobile network infrastructure in our case). They are never idle so they never time out. In order to trigger load balancing after adding more nodes (VMs/containers/etc.) to the system, we need a way to tell some of the clients to re-connect, i.e. trigger a graceful shutdown (goaway) on individual connections. Something as simple as Pid ! goaway would do. Then we can use ranch to find the connections:
    Pids = ranch:procs(Ref, connections),
    [Pid ! goaway || Pid <- lists:sublist(Pids, 1, 5)].

Cowboy now has graceful shutdown of HTTP/2 connections, but it can't be triggered by the user just yet

We are willing to contribute an interface for it, but first it would be nice to know if it would be accepted and how you'd want it to look like. We only need it for HTTP/2. Thanks!

Via sys:terminate, there's a TODO about using graceful shutdown there. There's a similar TODO for the parent process exit signal so that all connections attempt to shutdown gracefully when the supervisor exits.

The graceful shutdown PR has been merged. Closing, thanks!


overlay port:quazip  can't find FindQt5.cmake

Describe the bug
I have installed qt using online installer.
Now I create a cmake project with overlay port in vs2022.
I have set necessary var in CMakepreset.json:

error info:

I upload the test project.
vcpkg_test.zip
Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:

./vcpkg install xxxx
See error
Repro code when

Expected behavior
A clear and concise description of what you expected to happen.
Failure logs
Additional context
Add any other context about the problem here.

It seems that CMAKE_PREFIX_PATH has not been passed to  CMakelist.txt of custom port.

@insar-dev, thanks for posting this issue, I will try to reproduce your issue locally.

It seems that CMAKE_PREFIX_PATH has not been passed to CMakelist.txt of custom port.

Hardly any setup details are passed through from your user project to vcpkg tool to portfiles script mode to CMake project mode. You use the regular CMake integration variables,
https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/cmake-integration#settings-reference.
Basically, mixing non-vcpkg dependencies and vcpkg dependencies could be troublesome. Qt comes with a lot of dependencies, e.g. zlib.


daal4py.oneapi module import fix

This is a fix of #652
Now when the user imports oneapi module it is being searched in the current daal4py/oneapi subdirectory or in site-packages

/intelci: run


Storing the default value to know if a pre-filled form has real changes

Is your feature request related to a problem? Please describe.
Sometimes a form does not come empty but is already filled with data (imagine editing an existing entity coming from the database).
If I edit a field and bring it back to the original value, ngrx-forms flags it as dirty because the value changes.
Describe the solution you'd like
It can be useful to add a defaultValue field to the store to keep track of the default value and compare it with the actual value to know if it's the default one or not.
The default value can be set with a new SetDefault action and a new isDefault boolean can be added.
Describe alternatives you've considered
The default value can also be stored by passing a boolean flag to SetValue.
Additional context
This also helps handle a Save button to enable it only if the form has changed from the default value.
Let me know if you find this idea worth the time, I can also come up with a PR so we have some code to discuss.

a couple available approaches come to mind - haven't tried them, but seem like they should work.
a) using createFormGroupState in your reducer to "reinitialize" the form, providing the value you want.
b) use markAsPristine after setting the value

Thank you for the reply!
This indeed works if you want to set a value at first, and have a clean state :)
However, if for example I type a letter and I delete it, the form is no longer set as Pristine so I don't know that the current value, in fact, is exactly the same as before.

However, if for example I type a letter and I delete it, the form is no longer set as Pristine so I don't know that the current value, in fact, is exactly the same as before.

I see, I understand better now.  I would argue that's not typical form-control behavior, specifically in the angular forms space. The control at that point would in fact be touched & dirty NOT pristine
If I were trying to achieve this behavior, I would probably either set the defaultValue in my store (outside the form) or possible leverage userDefinedProperties for that value, and do a comparison in a updater function, and set the control back to pristine if the current value and default value are equal - but this could get expensive depending on the size of your form


Clarify conflict case where provisioning or binding is in progress

When provisioning or binding is in progress, it is possible in theory to send another provisioning or binding request with different parameters. The spec does not say how to handle this case but it makes sense to send a 409 Conflict response in this case.

Hey there!
This looks interesting, but we need you to sign the CLA first.

@jberkhahn working on it 👍
Was confinced I already signed a CLA a long time ago but probably mistaken.

Closing and reopening to retrigger CLA bot

I just signed and sent the CLA.


[FLINK-22562][docs-zh]Translate recent updates to backpressure and ch…

…eckpointing docs

What is the purpose of the change
Translate recent updates to backpressure and checkpointing docs
Brief change log
Update 'flink/docs/content.zh/docs/ops/monitoring/back_pressure.md'
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving):  no
The serializers:  no
The runtime per-record code paths (performance sensitive):  no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper:  no
The S3 file system connector:  no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

cc @wuchong @xccui @klion26, looking for your feedbacks, thanks!

Hey, can this be merged?

@PatrickRen Hi Patrick, could you give some feedbacks for my translation? Thank you so much!

Hey, can this be merged?

Yes, I think it's ready.

Hi @wuchong, this pr is ready for merge. could you?


[Feature]: Disabling Problem reports for specific files and/or folders

Description
There should be an option to exclude a specific file or a whole folder from the problem reporting. This file/folder can still be in the IDL path and could/should still be parsed by the extension.
Additionally, there should be an option to exclude a specific file or a whole folder from parsing. This file/folder can still be in the IDL path, e.g. as a subfolder of a path given to IDL path.
Why it Matters
I am working on a part of a huge IDL library (solarsoft), and thus I need this whole library in my IDL path due to its dependencies of my part of the library to other parts of the library. So, I would like the entire library to be parsed, but I only want problems from my part of the library to be reported.
I develop my part of the library outside of the library itself, in its own git repository, and I only sync my repository to the library when I am happy with the current code. I.e. the code that I really want to get problem reports for is in another path than the library, but also in the IDL path.
That means, I would like to exclude my part of the library from parsing altogether since when it is parsed, I get a whole bunch of 'duplicate' warnings, which I don't want. Furthermore, the extension reports problems from my part of the library that is in the library and not updated.
I am sure I am not the only one with this problem.
Suggested Behavior
Add two options to the extension settings.

'Exclude file/path from reporting problems'
'Exclude file/path from being parsed'

Both options would act very similarly as e.g. idl.IDL.path. That means one could 'Add items' which would be paths to a file or folder and possibly use the '+' syntax to include subdirectories.
Alternate Behavior
I know it is possible to disable a file from reporting problems by adding a comment line with the comment 'idl-disable'.
But this is not practical for mainly two reasons: The library consists of thousands of files and I only have control over a small portion of the library.
Even if I could implement this solution, I would still like to exclude subfolders of the IDL path from being parsed.

I also saw the option idl.problems.includeProblemsFromIDLPath but I haven't found out what this does.

Thanks for reporting this!
First, for the preference you found, the VSCode UI (and hover help in the JSON settings editor) should give you the description of each setting.
For reporting problems, I think it probably makes sense to add a new setting that can exclude reporting problems for specific folders without having to change code. I think file-specific exclusions might be a little too much detail/control here and I think we would want this to behave the same way as IDL's search path (i.e. "+" to exclude a folder and subdirectories from being reported). I can poke at a new setting for this which shouldn't be too hard to get together.
For excluding folders from the parsing path, I'm not sure what to think about that just yet. However, if you want to bypass the default behavior, you can manually control IDL's path using the environment launch setting that we provide in the extension. This way IDL will know about the code/path, but VSCode won't parse/report it
I think this might work to solve your second problem.
Here's where you can find it:

Thanks for your quick reply.
Ok, now I get it with the IDL_PATH and this setting. In my case, this doesn't help me though, since what I want to exclude is a subdirectory of a directory I want to have parsed (but not reported :) ). But never mind this feature request (about excluding paths from being parsed), this does not have a high priority, and I think I know how to work around this problem. I.e. I don't include the whole library, but only the subdirectories minus the one I do not want. A bit more complicated but works fine.
But adding a setting to exclude directories from being reported would still be very nice to have. A file-specific exclusion is probably overkill, I agree. At least, I won't need this kind of specificity, excluding directories would be good enough.

Yes, I do have a workaround, so this feature isn't a high priority. But I appreciate that you want to leave this feature request open.

Ah, whoops! I thought I had done that on one of the branches, but that looks like it snuck in to develop and the release.
But good eye! That was me mocking up the parts and pieces for your original feature request.
I'll add that to my list to get wrapped up in the next few weeks and it will actually work.


bug:not working with react

The npm package doesn't seem to be working with react, as soon as you import the package (Either way with import or require) you get "TypeError: util_1.TextEncoder is not a constructor"
**Full error log:
3 | function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
4 | return new (P || (P = Promise))(function (resolve, reject) {
5 |     function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }

6 |     function rejected(value) { try { step(generator"throw"); } catch (e) { reject(e); } }
| ^  7 |     function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
8 |     step((generator = generator.apply(thisArg, _arguments || [])).next());
9 | });
**

Please put any code related to the issue within these backticks

This library does not have any support with the client side browser, so using this in a React environment will not work. If you are using something like NextJS, you might be able to use the status method within the getServerSideProps function for a page component since that is ran on the server, but no promises on that.


Installation issues with v4 on Raspberry Pi 4

I ran the below command
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash
Note: I added sudo to the bash in the install script otherwise i wasnt able to install
and below was the output
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)

-------------
OS: debian 11
Coolify version: 4.0.0-beta.18
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
Digest: sha256:1d167cf8386f08c9b0ea555954acbe74718fd3ec443dbbbdbf2f06ddbc7197dd
Status: Image is up to date for ghcr.io/coollabsio/coolify-builder:latest
 redis Pulling
 postgres Pulling
 coolify Pulling
 coolify Pulled
 redis Pulled
 postgres Pulled
time="2023-07-19T16:37:57Z" level=warning msg="volume \"coolify-db\" already exists but was not created for project \"app\". Use `external: true` to use an existing volume"
 Container coolify-db  Recreate
 Container coolify-redis  Recreate
 Container coolify-db  Recreated
 Container coolify-redis  Recreated
 Container coolify  Recreate
 Container coolify  Recreated
 Container coolify-db  Starting
 Container coolify-redis  Starting
 Container coolify-redis  Started
 Container coolify-db  Started
 Container coolify-redis  Waiting
 Container coolify-db  Waiting
 Container coolify-db  Error
 Container coolify-redis  Healthy
dependency failed to start: container coolify-db is unhealthy

Congratulations! Your Coolify instance is ready to use.

Please visit http://X.X.X.X:8000 to get started.

when i run docker ps, i can see that the coolify-db is having issues
CONTAINER ID   IMAGE                COMMAND                  CREATED         STATUS                          PORTS      NAMES
49a9a351a62f   postgres:15-alpine   "docker-entrypoint.s…"   5 minutes ago   Restarting (1) 30 seconds ago              coolify-db
823e6d6836fa   redis:alpine         "docker-entrypoint.s…"   5 minutes ago   Up 5 minutes (healthy)          6379/tcp   coolify-redis

Found this in the coolify-db container logs
initdb: error: directory "/var/lib/postgresql/data" exists but is not empty
initdb: hint: If you want to create a new database system, either remove or empty the directory "/var/lib/postgresql/data" or run initdb with an argument other than "/var/lib/postgresql/data".
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

But do not know which local directory is mapped in within the container path "/var/lib/postgresql/data" to check this further

cleaned up the existing coolify-db volume and have rerun the installation script curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash. This solved the issue

What do you mean you "cleaned up" the db. Did you delete the volume or modify it's contents?

cleaned up the existing coolify-db volume and have rerun the installation script curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash. This solved the issue

What do you mean you "cleaned up" the db. Did you delete the volume or modify it's contents?

I deleted the docker volume


in Node::~Node why n->control_deps.clear() is not called?

I noted that n->inputs.clear() is called,
don't quite understand why n->control_deps.clear() is not called.
thank you~

Actually, it doesn't matter. The nodes in the loop will be deleted after the destruction, so the input entry vector and control_dep vector will all be cleared anyway. I agree it is much clearer to either explicitly have both of them cleared or leave them to be cleared by the destruction.


Not receiving any response to a chat request

Bug Report
Description
Trying to run ollama-webui-lite per instructions in project's readme. Getting the error below during chat. Connectivity to ollama seems to work fine.

DOMException: Failed to execute 'transaction' on 'IDBDatabase': One of the specified object stores was not found.

Steps to Reproduce:

Execute ""npm run dev"
Navigate to "localhost:3000"
Submit a chat question

Expected Behavior:
Should receive a response
Actual Behavior:
Running icon is displayed but no response. Cancelling the chat does not produce a response.
Environment

macOS Ventura
Chrome

Reproduction Details
Confirmation:

[x ] I have read and followed all the instructions provided in the README.md.
[ x] I have reviewed the troubleshooting.md document.
[x ] I have included the browser console logs.
[ ] I have included the Docker container logs.

Logs and Screenshots

I was able to make it work in incognito window. I was also running ollama-webui in the same browser session. There may have been a conflict with something cached from ollama-webui?


DatePicker V1

Initial Date Picker implementation. Closes #44
Features:

Input date and time using the text field
Select day by clicking on the calendar button to open the calendar popover from react-day-picker
Switch months and years from within calendar picker (does not affect date until a day is selected)
formatString string prop to specify date format, see https://date-fns.org/docs/format for docs. Defaults to "ISO" which is not part of date-fns since normal ISO string cannot be specified using normal date string.
min and max date props to bound the date selection
minWidth number prop to specify min width of text input, useful for sizing based off the format
errorString string prop to pass in an external validation that will be shown if all other internal validations first pass
renderHeader and renderFooter function props that take setDateState and setOpen as args. Useful for adding additional content above and below the calendar content in the popover.
utc boolean prop (defaults to true) to specify if the time should be in UTC or local time.
adornment React.ReactNode prop for passing in additional content to the left of the calendar button on the right side of the input.
Validation including basic date validity, date adherence to optional min, max, and required props

Looks great! Did we also want to expose a renderDay prop to pass through to DayPicker so that users can provide custom day components?

Great suggestion. I've added a renderDay prop which is passed the DayContentProps from DayPicker. Added a story where it uses renderDay to show day of year below the date.

perfect! :shipit:


Cloudwatch integration for autoscaling.

Just FYI, there is a project for this:
https://beta.docker.com/docs/aws/scaling/


Documentation: Updated URL to plugin reference - docker-volume-netshare

What I Did
Updated the URL for docker-volume-netshare which is was recently moved under an open-source organization on GitHub.
No other changes - just replaced the github.com path from github.com/gondor to github.com/ContainX.

LGTM 🐺


SECRET KEYS! b4 deployment

Secret keys (environment variables):

db url
jwt
db credentials
connection string

JWT secret is now in .env file.  > add to HEROKU on deployment.


Write a full-stack restart script on blue

For convenience, and since we're using a newer version of MySQL from EPEL (which has a convoluted service name), this is a reminder to write a small full-stack restart script on blue. This will enable the team to restart the database server and SEGS in one go. This could also be used via cron for periodic therapeutic restarts.

/usr/local/bin/segs_stack.sh has been created and accepts the typical init script stop, start, restart, and status verbs.


Having the null check separate is not necessary. The method will retu…

…rn if the first statement is false, it will not cause a NullReferenceException.

This change is

I will assume this is covered by existing tests
If not, I'd appreciate it if you could make another PR


error with configuration file

docker run --name=pokego-bot1 --rm -it -v $(pwd)/configs/config.json:/usr/src/app/configs/config.json pokemongo-bot
2016-08-09 13:26:23,926 [       cli] [INFO] PokemonGO Bot v1.0
2016-08-09 13:26:23,931 [       cli] [INFO] No config argument specified, checking for /configs/config.json
configs/config.json:3:16: Error: Can not decode value starting with character u'\u201c'
|  At line 3, column 16, offset 50
configs/config.json:3:39: Info: Recovering parsing after character u','
|  At line 3, column 39, offset 73
configs/config.json:4:16: Error: Can not decode value starting with character u'\u201c'
|  At line 4, column 16, offset 92
configs/config.json:4:34: Info: Recovering parsing after character u','
|  At line 4, column 34, offset 110
configs/config.json:100:6: Warning: Object contains duplicate key: u'any'
|  At line 100, column 6, offset 2665
|  Object started at line 98, column 15, offset 2579
configs/config.json:110:6: Warning: Object contains duplicate key: u'// Zubat'
|  At line 110, column 6, offset 3220
|  Object started at line 98, column 15, offset 2579
configs/config.json: has errors
2016-08-09 13:26:23,980 [       cli] [CRITICAL] Error with configuration file
not sure why but i always get this error with configuration file?

Use this. http://pastebin.com/UStttHL2
Also, don't put in a Google Maps API key it messes up.

Still getting the same error. any other suggestions?

With suggested:
bot1-pokego_1     | 2016-08-25 02:37:37,208 [       cli] [INFO] PokemonGO Bot v1.0
bot1-pokego_1     | 2016-08-25 02:37:37,226 [       cli] [INFO] commit: not found
bot1-pokego_1     | 2016-08-25 02:37:37,230 [       cli] [INFO] No config argument specified, checking for /configs/config.json
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: String literal is not terminated
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  String started at line 96, column 10, offset 2671
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: String literal is not terminated with a quotation mark
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  String started at line 96, column 10, offset 2671
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:10: Error: Missing value for object property, expected ":"
bot1-pokego_1     |    |  At line 96, column 10, offset 2671
bot1-pokego_1     |    |  Object started at line 93, column 18, offset 2599
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: Unexpected end of input
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: Object literal (dictionary) is not terminated
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  Object started at line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    with text: True
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: Object literal (dictionary) is not terminated
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  Object started at line 93, column 18, offset 2599
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: Object literal (dictionary) is not terminated
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  Object started at line 91, column 6, offset 2542
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: Array literal (list) is not terminated
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  Array started at line 11, column 13, offset 358
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json:96:24: Error: Object literal (dictionary) is not terminated
bot1-pokego_1     |    |  At line 96, column 24, offset 2685 (AT-END)
bot1-pokego_1     |    |    near text: True
bot1-pokego_1     |    |  Object started at line 1, column 0, offset 0 (AT-START)
bot1-pokego_1     | /usr/src/app/pokemongo_bot/../configs/config.json: has errors
bot1-pokego_1     | 2016-08-25 02:37:37,295 [       cli] [CRITICAL] Error with configuration file
bot1-pokego_1     | pokemongobot_bot1-pokego_1 exited with code 255```


[Bug]: BitWarden Desktop won't install correcly

What happened?
Download is correct only the install parameter is missing a parameter, needed for the latest version(s)
Currently only "/S" is used, "/allusers" must (now) also be added to install for all users.
desktop-apps
Version
2409.1419
What PowerShell edition/s are you running Evergreen on?
Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows 10+
Have you reviewed the documentation?

[X] Troubleshooting at: https://stealthpuppy.com/evergreen/troubleshoot/
[X] Known issues at: https://stealthpuppy.com/evergreen/issues/

Verbose output
PS C:\> (Export-EvergreenManifest -Name BitwardenDesktop -Verbose).Install.Virtual
VERBOSE: Get-FunctionResource: read application resource strings from [C:\Users\John\OneDrive -
JOBICO\Documents\WindowsPowerShell\Modules\evergreen\2409.1419\Manifests\BitwardenDesktop.json]

Name                           Value
----                           -----
Arguments                      /S
PostInstall

Those install switches included in the manifest aren't really intended as a fully supported feature. I was looking at including those but that's not really what Evergreen is focused on. Create a script that includes the correct install switches and doesn't use those included in the manifest

I already fixed it at my side in the script indeed, just wanted to pass the information.


taxonlookup not on CRAN, current version of MS says that it will be

when we discussed this before, it was blocked by storr which was blocked by something else, which had an important bug or something like that?  any progress on that?

phyndr is not blocked by anything - only taxonlookup is.  And storr is still blocked by RedisAPI because I'm rewriting the Redis support and don't want two versions of that up...

I'm OK with taxonlookup not being on CRAN, I'll take that out of the MS...

see 72a7375e0ae49637d0ff5b932a407dca6a4bc494


Client-side generated validation messages

Currently validation messages generated by the Client-side only support labels that are strings, this will need to be updated to support the use of castStringToElement so that labels can be displayed properly.
As labels are not necessarily always strings, sometimes they're html containing links. They would end up appearing as [object Object] is required when a validation error happens for that field.

Pointers for how to fix this: FormBuilder.js uses Validator.js to trigger validation (see validateField()). castStringToElement.js is a helper that casts to a React element. Validation errors are shown in FieldHolder.js and FormAlert.js (see renderMessage()).

Is this related to framework anymore? Can this be closed?

Hmmmn, it would be worth double checking that this isn't worth transferring to admin before it is closed I think.

Preeeetty sure it's irrelevant now. Looked at the parts @chillu mentioned and it looks like it's been addressed (or subsequently refactored). Reopen if I'm mistaken 🙂


Inaccurate results

I am getting inaccurate results when I take the readings 5 times back to back.. these are the following readings I am getting: 77, 59, 65, 65, 77
Has anyone faced this issue too? or is it just my pulses that are fluctuating? If the issue is real I would really like a solution as it's causing a bottleneck in my project.

Any updates on this issue? Am also having same issue.

I can't tell you if the project calculates your heart rate right, but it's normal that if your measure your heart rate 5 times it should never be the same because your heart beats irregular. If you want to learn more about read this: https://en.wikipedia.org/wiki/Heart_rate_variability

The problem is that the algorithm used is very basic...it just measures a heartbeat whenever the red intensity goes below the average. If there's any noise in the signal then you'll end up getting multiple beats counted for one actual heartbeat.


spanner-jdbc: Fix possible IllegalArgumentException in SingleUseTransaction

The fireAndForgetRollbackAndCloseTxManager method could cause an IllegalArgumentException if it happened to execute after a different method had already closed the TransactionManager. The fireAndForgetRollback method has therefore been removed and replaced with a synchronous rollback call. This will make update statements in autocommit mode that return an error slightly slower than they were, as they will not return until the rollback method has been executed.
The fireAndForgetRollback method is something that should rather be added to the TransactionManager itself.
Fixes this flake: https://source.cloud.google.com/results/invocations/df3b7c34-a981-4dfa-9978-7fa34e290142/targets/cloud-devrel%2Fclient-libraries%2Fjava%2Fgoogle-cloud-java%2Fpresubmit%2Fjava7/log

@skuruppu I had the same issue with a different PR yesterday and talked to @kolea2 about it. She confirmed that it is unrelated to this

@skuruppu @olavloite yep, that is a temporary break while we wait for the linkage monitor build to be updated. Fine to merge.


Expose host flavor

Description
Host flavor variable has been exposed. Because it cannot be set with cpu and memory, a local was added to identify if the host_flavor is set. If it is set a version of the database is created using the host flavor, if not a version with cpu and memory is created.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

@ocofaigh This was a solution that I found. But I am open to suggestions as I agree that this is probably not the best way to go about this. The problem I ran into when I testing what would work, is that only host_flavor and disk can be listed in the resource, or memory, disk, and cpu. It does not support all at once. I don't know of another way to define that group block only based on what is inputted.

I tried to solve a similar issue by using dynamic group on the group_id = "member" maybe you already tried that approach?
`  # "member" group with host_flavor only for the enterprise-sharding plan
dynamic "group" {
for_each = var.database_plan == "enterprise-sharding" ? [1]:[]
content {
group_id = "member"
  host_flavor {
    id = var.host_flavor
  }

  disk {
    allocation_mb = var.disk_size
  }

}

}
"member" group for other database_plan
dynamic "group" {
for_each = var.database_plan == "enterprise-sharding" ? []:[1]
content {
group_id = "member"
memory {
allocation_mb = var.ram_size
}
  disk {
    allocation_mb = var.disk_size
  }

  cpu {
    allocation_count = var.cpu_size
  }
}

} `

@ocofaigh This was a solution that I found. But I am open to suggestions as I agree that this is probably not the best way to go about this. The problem I ran into when I testing what would work, is that only host_flavor and disk can be listed in the resource, or memory, disk, and cpu. It does not support all at once. I don't know of another way to define that group block only based on what is inputted.

I tried to solve a similar issue by using dynamic group on the group_id = "member" maybe you already tried that approach?
# "member" group with host_flavor only for the enterprise-sharding plan
  dynamic "group" {
    for_each = var.database_plan == "enterprise-sharding" ? [1]:[]
    content {
      group_id = "member"

      host_flavor {
        id = var.host_flavor
      }

      disk {
        allocation_mb = var.disk_size
      }

    }
  }
 # "member" group for other database_plan
  dynamic "group" {
    for_each = var.database_plan == "enterprise-sharding" ? []:[1]
    content {
      group_id = "member"
      memory {
        allocation_mb = var.ram_size
      }

      disk {
        allocation_mb = var.disk_size
      }

      cpu {
        allocation_count = var.cpu_size
      }
    }
  }

Thank you! Yes, I am actually about to push a commit with a change using dynamic blocks.

/run pipeline

Todd and I noticed that in the other_test.go there is some possible test duplication. The basic example tests pg version 12 and then the ICDVersions test runs through all the versions testing each one, so testing 12 again.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

Suggest to merge this one. Latest comments from Todd have been addresses (he's out of the office).
@shemau @ocofaigh - ok with the latest?

:tada: This PR is included in version 3.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


New architecture support

Hey, thanks for the great library!  I'm just experimenting with it, but it seems it doesn't work on the new rn architecture.  Fortunately it doesn't crash or error out or anything, it just seems to my eye to display a regular view with a regular border radius.
Old arch:

New arch:

Code is exactly the same, just toggled on the new architecture in the expo build properties plugin then rebuilt the project (expo/CNG/prebuild).

thanks for pointing this @gorbypark
it should be now working in 1.1.0
https://github.com/Malaa-tech/expo-squircle-view/releases/tag/1.1.0
if you still have issues with it please let us know 🙏


Altitude lookup table

Currently, altitude for pvlib.location based algorithms defaults to zero, but if we include a low-resolution altitude lookup, we can provide better results when altitude is not specified.
We can make this altitude lookup the same format as LinkeTurbidities.h5, so it wouldn't require that much new code or any new dependencies.
I was able to build an altitude map using open data aggregated by tilezen. My test H5 file is currently 13 mb using 4320x2160 resolution, uint16 altitude, and gzip compression. We are free to distribute this data, but we do need to do is add this attribution somewhere in the documentation.
Would you guys be interested in this feature? Should I make a pull request?
Here is a plot of my sample

:

Is there an api we can use instead?

Cool idea. I can't really comment on the cost (if any) of distributing another relatively large data file.
Some thoughts: the technical improvement to modeling would be minor: the only use of 'altitude' is to estimate air pressure for a clear-sky model or for adjusting geometric solar position to apparent position. But there's an intangible benefit from not having to look up a value, or having to explain why the default 0m is good enough. To me the intangible benefit is likely greater than the improvement in model results.
As alternatives, several of the weather data sources (PSM3, others), but not all, return altitude.

Could file size be reduced by omitting the ocean bathymetry data?  I'm not really familiar with h5 files.  If accuracy is not so important, maybe cutting the values down to 8 bits would be acceptable.

Cool idea

Yes!  Makes me wonder if there are other such datasets we should consider.

Accuracy is not so important

Good point. Altitude rounded to 100m increments is probably good enough.

I'm unsure about packaging an elevation map with pvlib. But a higher resolution data set could be useful for shading. I thought there were some PR discussions along those lines.

I think getting altitude is probably something we can outsource to an API like the Google Maps maybe, ESRI, or MapQuest? Seems a lot easier than adding 10 mb to the package maybe?

Found these:

Google map elevation API, guide

open elevation api

Air Map API

open topo data api

DEM.NET EG

This URL will give you (quickly!) the elevation near Notre-Dame de Paris (39 meters), using SRTM GL3 dataset :
https://api.elevationapi.com/api/Elevation?lat=48.854624&lon=2.3436793&dataSet=SRTM_GL3

And more… I googled “elevation api lookup”

I tried the suggestions to reduce the size of the altitude lookup map.
If I set the oceans data to zero, it compresses much better and goes down to 3.9 mb.
I also tried encoding the remaining land data as uint8 in 35m increments.
This uint8 version is 1.2 mb after gzip compression.
I agree that an API would be good for high-resolution use cases like shading.
But I think having a fallback built-in is still valid.
An external API has more friction; You need API keys, there can be costs or limits, and it adds more latency.

Also, where I got the original data can be helpful in high-resolution use-cases. It is hosted for free by aws in their open data initiative.
You can fetch terrain tiles using slippy tilenames from this URL template
https://elevation-tiles-prod.s3.amazonaws.com/v2/terrarium/{zoom}/{x}/{y}.png.
And here are the docs for how to convert RGB -> meters

I'm -1 to having Location.get_solarposition() make web requests, if that's being proposed.  I'm cautiously open to bundling a local dataset if it's only a ~1MB expense (our current dist is ~30 MB).
I'm also open to iotools functions for elevation data, although I'm not sure I see a lot of value in it if the relevant API calls are as simple as requests.get("url?lon=X&lat=Y").json()['elevation'].  I think I'd rather see a gallery example showing how to DIY in that case.

This discussion suggests there are two, perhaps complementary, enhancements:

provide a low-resolution, low-accuracy altitude to supplement the current default of 0. for clearsky and solar position calculations.
via iotools, provide access to an API for high-resolution elevation data for detailed modeling of shading, tracker steering, and (in future pvlib) spatially varying module orientation.

Access to an API for detailed elevation data will not relieve those who want a simple alternative to the current default. Similarly, a low-resolution file included with pvlib will not satisfy those looking for high accuracy elevation.
I'm not opposed to having all three (current default, low-resolution internal lookup, high resolution via API) in pvlib.

I think it'd be great to have the option of something like this:
pvlib.location.Location(latitude=55, longitude=10, altitude='SRTM')

and then have the location object call an API (using a function from iotools) that retrieved the elevation.

It looks like the 1.2 mb version might be acceptable. I will make a pull request early next week and you can make the final decision then. I also will play with the encoding a bit, there might be ways to increase accuracy while staying ~1 mb.

I wonder if folks will start to cannibalize  pvlib for elevation data, and then send issues complaining that it's only accurate to 35m :rofl:

I wonder if folks will start to cannibalize pvlib for elevation data, and then send issues complaining that it's only accurate to 35m 🤣

Assuredly, yes.

I think this is a nice addition.  There are probably a variety of technical variations possible, for example using netcdf, but it's also fine the way it is.


Update backitup to stable Release 1.0.0

Should versionDate also be updated?!

No the Versionsdate is ok


Issue #1 UI: Calendar

The calendar picture is in the design folder, I am not sure where to put it, you may change its location.

Perfect. Thank you for your design


bumped django-filter and fixed breaking changes

Followed this document: https://github.com/carltongibson/django-filter/blob/1.0.0/docs/guide/migration.txt
Searched for stuff that might break and fixed them. Tested with the example project.

Coverage decreased (-0.5%) to 78.678% when pulling f2537e945fa5c3a896b404b2da162cddb8544396 on feature/171-bump_django_filters into 0de00c7536ade61d3bcc349fb52a255b4b53b7fc on develop.

Coverage decreased (-0.5%) to 78.678% when pulling f2537e945fa5c3a896b404b2da162cddb8544396 on feature/171-bump_django_filters into 0de00c7536ade61d3bcc349fb52a255b4b53b7fc on develop.


New MainNet chain download for neo-cli (block 2002315)

I am getting a corrupted compressed block error on this new (current to block 2002315) MainNet chain download.


Remove obsolete docker setup documentation

Support for docker was removed in
https://github.com/gopasspw/gopass/pull/1309.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1433   +/-   ##
=======================================
  Coverage   64.82%   64.82%
=======================================
  Files         201      201
  Lines       11466    11466
=======================================
  Hits         7432     7432
  Misses       3222     3222
  Partials      812      812

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 e7c31ae...871edac. Read the comment docs.


phiola.exe (also phiola-gui.exe) crash  while playing m3u file with radio stations when going next / previous

Happens with all version up to latest phiola-2.1-beta2
ONLY while playing m3u file with online radio stations:
Pressing key 'n' for next track or 'p' for previous one goes OK if I don't do it too fast (more than 1 second between presses)
Runs fine with local files.
phiola-crashdump-6648d725.txt
cmd_output.txt
RADIOS.m3u.txt

Easily reproducable on Linux, thank you for the info!

Fixed in v2.1-beta3


Add analytics event to publish success/failure in clients

The analytics events are here https://github.com/lbryio/lbry-sdk/blob/master/lbry/extras/daemon/analytics.py
We need a new event that tracks calls to the publish API endpoint and whether each publish succeeds or fails.

Great to hear that you want to tackle this.

Yes. I'd call the event Publishes, and then pass the outcome (success or failure) as a property to the event.
yes. you can copy send_server_startup_error, which includes the message property but you can that an outcome property with "success" or "failure" as the options

Is this issue still open @lyoshenka ?

yep

I created the pull request #3452 (which aims to resolve the issue), but I, allegedly, do not have permissions to link the pull request to the issue. Based on the information I found on the web - there is supposed to be a cog-like button on the sidebar of this page, but I do not see one.

@jackrobison is right that we're moving away from tracking events like this in our analytics. thanks for your PR @FemtosecondLaser and sorry that we didn't close this issue earlier


issue 321 home news rewording

This PR closes #321

Your tests fail, because there is a protractor test that checks for the contents of the home page news header. That test already existed and was likely added in the first place, simply to test wether protractor tests worked. But it's not a good idea to keep that test, we don't want our tests to fail if you change your home page news. Luckily @Atmire-Kristof already fixed this issue for the entities PR, in e39879b76212f27f1dcb60b11e45c030f50c21f7, so perhaps you can cherry-pick that commit?

https://github.com/DSpace/dspace-angular/commit/e39879b76212f27f1dcb60b11e45c030f50c21f7 has been cherry picked to resolve this.


Lity and YouTube video playback

Can I force the YouTube player to show a reload button and same poster at the end of video?
I typically get a grid of suggested videos. I don't want that, just the same video I loaded with Lity (with its poster) and the reload button.
Thanks.
HB

I have no idea if YouTube allows that. Lity just creates an iFrame and loads the YouTube embed URL. Lity ensures to pass all query parameters from the original URL to the embed URL, so maybe there some parameters to control that.


Generator doesn't follow config when changing provider directory.

Example:
config:
[
    ...
    generator =>  [
        ...
        'provider' => ['path' => 'Base/Providers', 'generate' => true]
    ]
]

When I make the module it puts the files in the right place but module.json and composer.json point to App/ModuleName/Providers/ModuleProvider.php
Similarily a related issue is when RouteServiceProvider is in app/Blog/Base/Providers, it tries to point routes to __DIR__ . '/../Http/Routes/web.php' which should be 2 directories up now... I think it would be better to use (module_path('Account') . '/Http/Routes/web.php');
The structure I'm going for is:
|app
|--|Blog
|--|--|Base
|--|--|--|Events
|--|--|--|Notifications
|--|--|--|Providers
|--|--|--|Tests
|--|--|--|config.php
|--|--|Data
|--|--|--|Migrations
|--|--|--|Models
|--|--|--|Seeders
|--|--|Http
|--|--|--|Controllers
|--|--|--|Middleware
|--|--|--|Requests
|--|--|--|Routes
|--|composer.json
|--|module.json

Hi,
Thank you for your patience.
Thank you for reporting this, I've fixed this here: https://github.com/nWidart/laravel-modules/commit/d2bbe192e105ff9030401e160e0c908e62f8206b

And the second issue has been resolved here: https://github.com/nWidart/laravel-modules/commit/8b259fa847400140d4a459ba2640fc9970f93a2c

Tagged as 6.2.0


Signal input error highlighting

Hello
Binding with signal input (Angular 17) is reported as error with highlighting.
<app-test [classicInput]="myString" [sgnInput]="myString" />

@Component({
  selector: 'app-test',
  standalone: true,
  imports: [],
  template: ` <p>test works!</p>`
})
export class TestComponent {
  sgnInput = input("notWork");
  @Input()
  classicInput:String="work"
}

@Component({
  selector: 'app-testCont',
  standalone: true,
  imports: [TestComponent],
  template: `
    <p>
      test works!
      <app-test [classicInput]="myString" [sgnInput]="myString" />
    </p>
  `
})
export class TestContainerComponent {
   myString:String="my text"
}

Please work on this!  It makes working with input signals very painful.

I spent a lot of time trying to resolve errors when I converted my project to input signals, went through documentation multiple times and realised that this was a angular service problem... please correct this