[v2.6] KDM Update for K8s March patch release

KDM Updates
TO BE RELEASED: Enabled in Rancher v2.6.5

New Kubernetes Version
Min Rancher Version
Min RKE Version

1.23.5-rancher1-1
2.6.4-rc0
1.3.3-rc0

1.22.8-rancher1-1
2.6.3-rc0
1.3.3-rc0

1.21.11-rancher1-1
2.6.0-rc0
1.3.0-rc0

Rancher System Images & Add-ons
Note: Please update system images and add-ons in the template as needed.
TBD
Developer Changelog

Add templates for new K8s versions. If a template that hasn't been released yet already exists, update it in place.
Update the default K8s version, and add or update the version information (MinRancherVersion and MinRKEVersion) in k8s_version_info.go for new K8s versions if needed (Use table from above).
Confirm versions for system images, add-on templates are correct using versioning reference table from below (expand details to view the table). Update the table if new versions are introduced.
Confirm add-on template version constraints in template.go are correct using versioning reference table from below (expand details to view the table). Update the table if needed.

Versioning Reference

Expand for system images & add-on templates versioning table

Note: Truncated repository names with a * indicates there are multiple images with that prefix. All repository names that match a truncated prefix should be checked for the same version stated in the table.
For example: rancher/weave-* matches weaveworks/weave-kube and weaveworks/weave-npc, and they should both have the same version.
v1.23.4-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.4.16-rancher1

rancher/hyperkube
v1.23.5-rancher1

rancher/rke-tools
v0.1.78

rancher/mirrored-k8s-dns-*
1.17.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.3

rancher/mirrored-coreos-flannel
v0.15.1

rancher/flannel-cni
v0.3.0-rancher6

rancher/mirrored-calico-*
v3.19.1

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.1ae238a

rancher/mirrored-pause
3.4.1

rancher/nginx-ingress-controller
nginx-1.1.0-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v1.1.1

rancher/mirrored-metrics-server
v0.5.1

rancher/mirrored-coredns-coredns
1.8.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.3

rancher/kubelet-pause
v0.1.6

rancher/mirrored-k8s-dns-node-cache
1.18.0

Add-on Name
Add-on Template Version Constraint

Calico
calicov319

Canal
canalv3211

Flannel
flannelv0140

CoreDNS
coreDnsv183

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv050

Weave
weavev120

Aci
aciv500

NginxIngress
nginxIngressv110Rancher3

Nodelocal
nodelocalv121

v1.22.7-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.4.16-rancher1

rancher/hyperkube
v1.22.8-rancher1

rancher/rke-tools
v0.1.78

rancher/mirrored-k8s-dns-*
1.17.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.3

rancher/mirrored-coreos-flannel
v0.15.1

rancher/flannel-cni
v0.3.0-rancher6

rancher/mirrored-calico-*
v3.19.1

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.1ae238a

rancher/mirrored-pause
3.4.1

rancher/nginx-ingress-controller
nginx-1.1.0-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v1.1.1

rancher/mirrored-metrics-server
v0.5.1

rancher/mirrored-coredns-coredns
1.8.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.3

rancher/kubelet-pause
v0.1.6

rancher/mirrored-k8s-dns-node-cache
1.18.0

Add-on Name
Add-on Template Version Constraint

Calico
calicov319

Canal
canalv3211

Flannel
flannelv0140

CoreDNS
coreDnsv183

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv050

Weave
weavev120

Aci
aciv500

NginxIngress
nginxIngressv110Rancher3

Nodelocal
nodelocalv121

v1.21.10-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.4.16-rancher1

rancher/hyperkube
v1.21.11-rancher1

rancher/rke-tools
v0.1.78

rancher/mirrored-k8s-dns-*
1.17.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.3

rancher/mirrored-coreos-flannel
v0.15.1

rancher/flannel-cni
v0.3.0-rancher6

rancher/mirrored-calico-*
v3.19.1

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.1ae238a

rancher/mirrored-pause
3.4.1

rancher/nginx-ingress-controller
nginx-1.1.0-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v1.1.1

rancher/mirrored-metrics-server
v0.5.0

rancher/mirrored-coredns-coredns
1.8.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.3

rancher/kubelet-pause
v0.1.6

rancher/mirrored-k8s-dns-node-cache
1.18.0

Add-on Name
Add-on Template Version Constraint

Calico
calicov319

Canal
canalv319

Flannel
flannelv115

CoreDNS
coreDnsv183

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv050

Weave
weavev120

Aci
aciv500

NginxIngress
nginxIngressv110Rancher3

Nodelocal
nodelocalv121

RKE PR is not up yet, also the rancher v2.6.5-rcX is not ready. Hence, reopened the issue.

Fresh install checks and upgrade checks looks good.
Provisioning Checks on Fresh Install of Rancher 2.6.5-rc1 - PASS

KDM points to dev-v2.6 branch.
Cluster creation succeeds for 1.23.5-rancher1-1, 1.22.8-rancher1-1, 1.21.11-rancher1-1 k8s versions with all network providers
Network checks succeeded for all new clusters
Ran validation tests for Canal cluster.
Network checks and Canal checks pass.

Provisioning Checks after Upgrading to new KDM - PASS

On latest released v2.6.5-rc1, KDM points to release-v2.6
Cluster creation succeeds for old k8s versions with all network providers.
Ran pre-upgrade checks
Point KDM to dev-2.6 branch.
Upgrade k8s to the latest patches v1.23.5-rancher1-1, 1.22.8-rancher1-1, 1.21.11-rancher1-1
Ran post-upgrade checks
Pre-Upgrade and Post-Upgrade checks pass.

RKE checks using 1.3.10-rc3 passed for v1.23.5-rancher1-1, 1.22.8-rancher1-1, 1.21.11-rancher1-1 k8s version.
RKE default k8s version  -
dev-v2.6 should have the default as v1.22.8-rancher1-1
{
"RKEDefaultK8sVersions": {
"0.3": "v1.16.3-rancher1-1",
"default": "v1.22.8-rancher1-1"
}

Closing the issue since all the checks passed.

This is now superseded by https://github.com/rancher/rancher/issues/37388 since March patches were not formally released in KDM. These versions are removed per https://github.com/rancher/kontainer-driver-metadata/pull/889.


Sync with OpenJSF to organize press release

Email TSC members when this is ready.

@alexduran4 to liaise with OpenJSF marketing to sync on:

press release,
blog posts,
AMP keynote speaker.

Make sure press release/blog post can be reviewed by TSC members prior to announcement.


meltano elt tap-spreadsheets-anywhere target-postgres writing 0 records for stream

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2628
Originally created by @a_sharma24 on 2021-03-04 22:38:48

What is the current bug behavior?
What is happening now?
I am unable to write any records to the database using tap-spreadsheets-anywhere.
What is the expected correct behavior?
What should be happening?
When running meltano elt tap-spreadsheets-anywhere target-postgres everything should be loaded into the postgres database from the specified xls file.
Steps to reproduce
How one can reproduce the issue?
# project setup
1. meltano init
2. meltano add extractor tap-spreadsheets-anywhere
3. meltano add loader target-postgres --variant meltano
4. meltano elt tap-spreadsheets-anywhere target-postgres

the link to the dataset
https://dataverse.harvard.edu/file.xhtml?persistentId=doi:10.7910/DVN/27763/ADYC1Q&version=1.0
my meltano.yml file
version: 1
send_anonymous_usage_stats: true
project_id: c5e43ad3-aa5f-4b0a-8152-74183e9ec814
plugins:
  extractors:
  - name: tap-spreadsheets-anywhere
    variant: original
    pip_url: git+https://github.com/ets/tap-spreadsheets-anywhere.git
    config:
      tables:
      - path: https://dataverse.harvard.edu/api/access/datafile/
        name: us__military_deaths
        pattern: ':persistentId?persistentId=doi:10.7910/DVN/27763/ADYC1Q'
        start_date: '2014-11-04T18:38:22Z'
        key_properties: []
        format: excel
        worksheet_name: Worldwide
    capabilities:
    - catalog
    - discover
    - state
  loaders:
  - name: target-postgres
    variant: meltano
    pip_url: git+https://github.com/meltano/target-postgres.git
    config:
      user: military
      host: <IP_ADDRESS>
      port: 5432
      dbname: military_deaths

Relevant logs and/or screenshots
Please use code blocks (```) to format console output
meltano                   | Running extract & load...
meltano                   | No state was found, complete import.
tap-spreadsheets-anywhere | INFO Using supplied catalog /Users/asharma/military_data_analysis/meltano/.meltano/run/elt/2021-03-04T222427--tap-spreadsheets-anywhere--target-postgres/567b2418-26a7-4b43-94a3-41377b22abda/tap.properties.json.
tap-spreadsheets-anywhere | INFO Syncing stream:us__military_deaths
tap-spreadsheets-anywhere | INFO Assembled https://dataverse.harvard.edu/api/access/datafile//:persistentId?persistentId=doi:10.7910/DVN/27763/ADYC1Q as the URL to a source file.
target-postgres           | INFO Table 'us__military_deaths' exists
tap-spreadsheets-anywhere | WARNING URL did not return a last-modified header so using current date and time.
tap-spreadsheets-anywhere | INFO Wrote 0 records for stream "us__military_deaths".
meltano                   | Extract & load complete!
meltano                   | Transformation skipped.

Possible fixes
If you can, link to the line of code that might be responsible for the problem or suggest a fix
I'm not quite sure what is happening. I believe it could potentially be a problem with the last-modified-header warning, but I'm not really sure.
Further regression test
Ensure we automatically catch similar issues in the future

[ ] Write additional adequate test cases and submit test results
[ ] Test results should be reviewed by a person from the team

View 6 previous comments from the original issue on GitLab


refactor(types): lint

@danielsogl Again, if I'm going to accept lint PRs, there's got to be changes to the actual lint config. As I mentioned, there's already a linter in the CLI and according to its rules, there are no lint issues. Run npm run lint to see for yourself.
Without actual toolchain integration, we're just subjectively moving whitespace around.

I will submit a PR for the ionic-lint repo: https://github.com/driftyco/tslint-ionic-rules/blob/master/tslint.js
Actually, I orient my at the angular-cli lint rules


look into failing s3 logs for Feb 2024

s3 log consolidation for Feb 2024 didn't process correctly. Need to debug and get out summary files

Some logs in February had an extra column due to the parsing of the data, the Operation was split over two lines and so parsed as two columns. Fixed in #65. All logs for February 2024 have been processed.


Ctrl+Enter returns error when vacuum command is present in the editor

Description
The documentation says: to execute a query under the cursor, press Ctrl+Enter.
But when the editor contains these 2 queries:
select * from tablename;

vacuum full freeze verbose tablename;

Ctrl+Enter key combination returns error:
SQL Error [25001]: ERROR: VACUUM cannot be executed within a pipeline
in both cases — when the active cursor is on one or the other query.
However, if queries are being swapped:
vacuum full freeze verbose tablename;

select * from tablename;

each one executed normally without errors.
But when adding one another:
vacuum full freeze verbose tablename;

select * from tablename;

vacuum full freeze verbose othertablename;

only first query executed without errors.
DBeaver Version
Community Edition 24.0.3
Operating System
No response
Database and driver
PostgreSQL 16.2
PostgreSQL JDBC Driver 42.7.3
Steps to reproduce
No response
Additional context
No response

Duplicate of https://github.com/dbeaver/dbeaver/issues/26416
The fix will be included in DBeaver 24.0.4.
Also you can try Early Access version with fix https://dbeaver.io/files/ea/ now.

The issue is not yet fixed in version 24.2.2.
SQL Error [25001]: ERROR: VACUUM cannot be executed within a pipeline

It seems that multiple VACUUM queries cannot be executed at once. However, it does work in PSQL.


Better Menu

Menu use RakugoTextLabel
Now menu([["First Choice"]]) is the same as menu([["First Choice", "First Choice", {} ]])
Now menu([["First Choice", 1]]) is the same asmenu([["First Choice", 1, {}]])

 Make menu() simpler to use

 Make RakugoTextLabel


New version: GNU.Octave version 8.1.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


sparse_conjugate_gradient: fix Windows path separator

Description
There was a missed Linux-style path separator in the Windows makefile for sparse_conjugate_gradient.
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

waiting on test results


intel_adsp: Unify trace backends, fix "__noinit" cacheability

Combine the two trace backends so apps can reliably printk early and use logging later without the two implementations stepping on each other.
Fix one (fairly severe, but obscure) but with the cache coherence of the __noinit section that I stumbled over while mucking with this.

Ping this one again.  Note that this has an important bug fix and that I'm going to need it merged before we can get sanitycheck working on anything that requires the log backends.


Optional string can't be decoded to string field with @ppxCustom

I tried to ask where i could before filling an issue but dont understand what's going on here.
the following example:
module OptionalString = {
 type t = string;
 let parse = opt => switch(opt) {
  | Some(str) => str
  | None => ""
 }

 let serialize = str => {
  if str == "" {
    None
  } else {
    Some(str)
  }
 }
}

type test {
  image: string,
}

module Query = %graphql(`
  query MyQuery(){
     test @ppxAs({type: "test"}) {
        image @ppxCustom(module: "OptionalString")
     }
  }
`)

lends me this error, and I don't understand why:
 This has type:
    option<'a>

  But somewhere wanted:
    string

It's like the ppxCustom is ignored :/

optionality is already handled by the ppx you just have to decode the actual type

If i follow you well, i should be able to do this?
type test {
  image: string,
}

module Query = %graphql(`
  query MyQuery(){
     test @ppxAs({type: "test"}) {
        image
     }
  }
`)

Even if image is an optional field in the schema?

@jfrolich i stumbled upon the same problem on another type, it's like the ppxCustom directive is ignored:
type stats = {
  __typename: string,
  playlist_count: float,
  subscriber_count: float,
  subscription_count: float,
  track_count: float,
}

module BigInt = {
  type t = float;
  let parse = json => switch(json->Js.Json.decodeNumber) {
    | Some(nbr) => nbr
    | None => 0.0
  }
  let serialize = nbr => nbr
}

module ForNavtabs = %graphql(`
  query getStats($profileId: uuid!){
    stats(where: {id: {_eq: $profileId}}) @ppxAs(type: "stats") {
      playlist_count @ppxCustom(module: "BigInt")
      subscriber_count @ppxCustom(module: "BigInt")
      subscription_count @ppxCustom(module: "BigInt")
      track_count @ppxCustom(module: "BigInt")
    }
  }
`)

I get the same error again

@ppxCustomOpt should fix this in master. I still need to add the documentation.


Package publish size

Hi, thanks for your work!
I’ve noticed that published package caniuse-db contains two duplicate files: data.json in the root and data-1.0.json in the folder fulldata-json.
Each of this files weights ~3 MB. Considering the popularity of this package (~1M weekly downloads), it’d be nice removing one of them to reduce the package publish size. Is it possible? Is there any specific purpose for publishing both of them?

Mostly legacy reasons, not wanting to break anything already referencing the original version. In particular this was the case before the data was made available as a package.
I believe most consumers of caniuse data go through caniuse-lite which is specifically designed to reduce the size of the exported data.


README.md links to getting_started, not getting-started

Following the link to github.io from the README.md in github.com looks really odd. Changing it as in the title seems to work.

This seems to be fixed

verified


More Useful Copper compat

Describe your idea
Hi, can you make this mod work with copper tools mod

Yes, done.
I think I did everything to support these generic tool types. Since I don’t know which copper mod, I can’t do.


PROPOSAL: CpiGuard Extension

CpiGuard
tldr
cpi guard is an extension that prevents certain token actions inside cpi, to protect users from implicitly signing for actions they cant see, hidden in third-party programs
full summary of changes:

changes to existing token-2022 processors:

transfer: if extension enabled and in cpi, authority must be delegate, or abort
burn: if extension enabled and in cpi, authority must be delegate, or abort
close_account: if extension enabled and in cpi, destination must be owner, or abort [IN FLUX: we may further limit to native mint accounts]
approve: if extension enabled and in cpi, abort
set_authority:

if Account and extension enabled and in cpi and authority to change is close authority and intent is to remove it, remove it
otherwise, if Account and extension enabled and in cpi, abort
if Account and authority to change is owner and extension enabled, abort regardless of cpi (this is to prevent moving a CpiGuard account to a program)

new CpiGuard instruction and processor, modeled after RequiredTransferMemos interface. changing CpiGuard status in cpi is not allowed
program tests for all invariants listed above
token-client support for CpiGuard
token-cli support for CpiGuard (todo after extension merged)
token-js support for CpiGuard (todo after extension merged)
documentation in token-2022/extensions.mdx for CpiGuard (todo after extension merged)

this is an extension that can be enabled or disabled by users at-will. it does not break backwards compat. rather, it simply automates a choice to systematically decline to sign certain types of transactions
background
interacting with a dapp as a user means signing transactions that are constructed for you by its frontend code. there are three fundamental ways for a dapp to transfer funds from the user to the dapp (or, equivalently, burn them):

insert a transfer instruction in the transaction, which the user signs for
insert an approve instruction in the transaction, which the user signs for, and perform a cpi transfer under program authority
require the token program and a user signer for an opaque program instruction, and perform a cpi transfer under user authority

the first two are safe, in that the user can see exactly what is being done, with zero ambiguity. the third is quite dangerous. passing in a wallet signature allows the program to perform any action the user could, without any visibility into what it may be doing. there have been some attempts at workarounds, for instance phantom may simulate the transaction and attempt to warn about balance changes. but, fundamentally, this is intractable [jocular citation of turing 1936]
this also doesnt cover the approve and set authority instructions, which can grant authority to transfer all user funds without immediately effecting a balance change. wallets could also warn if the various authorities change after simulation, but again, this isnt perfect
there are two ways to make this much safer that dont have to grapple with undecidability:

wallets should warn whenever a wallet signature is made available to an opaque (non-system, non-token) instruction, and users should be educated to treat the request for a signature on such an instruction as highly suspect
the token program should have a means to prevent cpi calls on user authority from taking place, forcing opaque programs to directly ask for such authority in a user-visible manner

this proposal concerns the second
proposal
add a new Account extension to Token2022: CpiGuard
this would allow a user to opt in to backwards-compat-breaking behavior, rejecting certain kinds of cpi actions involving their token account:

transfer via cpi must go through a delegate
burn via cpi must go through a delegate
close_account via cpi must go through a close authority
approve via cpi is banned
set_authority via cpi is banned
disabling cpi guard via cpi is banned

this change is non-breaking for users who do not enable it, and users are free to enable or disable it as they please. the purpose of this is to protect users from accidentally granting a program permission to perform actions with their signature, if they personally choose not to allow such behavior
it also is part of an attempt to nudge program authors toward designing with "nothing up their sleeve," creating a ux pitfall that encourages them to use user-authed token instructions rather than user-authed cpi calls. especially with address maps live and double-size transactions in the pipeline, program authors should have sufficient space in their transactions to do things the right way
this change does not impact the ability of programs to auth their own accounts, or accounts of other programs, via cpi. they should simply not enable the extension
thoughts concerns etc
i waffled on whether to ban close_account entirely or not. i decided against it because, while close authority does behave in a surprising manner, the user is free to grant it to a program if they really want to
we might want to ban changing cpi guard status in cpi entirely, because if a program enabled it for their own account, they would not be able to disable it. there is also a very stupid edge case where a user could transfer ownership of a cpi-locked account to a program, which then wouldnt be able to close it. honestly i realized while writing this proposal that we needed to ban removing cpi guard in cpi or else a program could trivially bypass it
the tricky bit here is we cannot detect whether an account is a pda or an eoa without an ed25519 syscall, and requiring this overcomplicates a relatively simple extension. perhaps we unconditionally ban changing cpi guard status inside cpi, and we unconditionally ban transferring ownership of an account unless cpi guard is disabled. this feels right but i havent fully thought through all the edge cases
i considered making this extension trimodal, with a third "ban token actions via cpi entirely" state. but this seems superfluous. the point is not to prevent action from being taken, but to force developers to expose those actions to the user
its worth noting that this may seem like it overlaps the functionality of ImmutableOwner, but it doesnt. we prevent a program from changing an account owner via cpi, but the program is still free to surface a set_authority instruction for owner, and a user is free to sign for it
the owner/authority distinction is not perfect, if the user were for whatever reason to set themself as their own delegate or close authority (assuming this isnt blocked the processor, i havent checked). we could check that the supposed authority is different from owner. but we could also just say this is dumb
alternate names
my original name was SafeCpi, which i immediately discarded in favor of SaferCpi so as to disclaim all liability for the consequences of my actions. CpiLock was another candidate. TokenGuard or NoSignaturePassthrough or some other things were also considered. i think CpiGuard sounds best, but im open to suggestions
fin
please let me know questions/comments/words of encouragment/stern rebukes and chastisements, and feel free to tag anyone who you think might also have thoughts or should also have visibility on this. ideally i get this in before we freeze Token2022, but, i guess we will see
cc @joncinque @CriesofCarrots @mvines

This all looks great. The workings of it are very clear, and I agree that it's best to lock down as much as possible for full safety.  This will absolutely break things, but it's easy afterwards to go to a dapp and say "hey, why don't you support safer accounts?" and force them to do the right thing.
For this point in particular:

close_account via cpi must go through a close authority

This one can cause a bigger footgun in the future.  For delegates, it's easy to create an ephemeral keypair for one transaction, lose the key, and then just revoke it later.  With a separate close authority, you're forced to keep that key around afterwards, so what key will a wallet use?  Would you have to sandwich your call to the program with set_authority on both sides to set it to an ephemeral keypair and set it back? If you forget the second one, you've lost close authority on that account for good.
On the flip side, if there's no guard on close, sketchy dapps can use your signature on a wrapped SOL account to take all the SOL in it.  This is pretty specific, but here's my idea:

close_account via CPI must set the owner as the recipient of the lamports

This way, a sketchy program can't do anything nasty with your signature, which seems to be the main intent of this extension.

With a separate close authority, you're forced to keep that key around afterwards
theres no need for an eoa in this case. it would look like: set_authority instruction grants close authority to a pda. program can close the account if it chooses

i was gonna say "or repudiate its authority" but now i realize that if we ban set_authority through cpi, the user would need to turn off CpiGuard. but at least it wouldnt require their signature? mm, i guess we could allow set_authority via cpi if its removing permissions rather than adding them, but this adds code complexity (attack surface)
hmm i guess letting a program call close_account isnt too bad since its already required to be empty of tokens...

This will absolutely break things
i feel compelled to repeat (for the benefit of onlookers) that this extension is opt-in and does not break backwards compat. if disabled, nothing different happens. and if enabled, it is equivalent to a user carefully reading every transaction and choosing not to sign it if it does particular things they dont personally approve of. the "breakage" to dapp authors is "i create a suboptimal ux experience for discerning consumers," not "certain behaviors that were possible before become impossible"

unrelated, i had the thought that maybe ImmutableOwner should prevent setting a close authority

it would look like: set_authority instruction grants close authority to a pda. program can close the account if it chooses

Maybe I'm missing something.  When a user grants close authority to another address, they can't get it back unless that address gives it back.  Is the assumption that a user would only do that for a good reason? ie. they trust the program to do the right thing.  But that goes against the central tenet of this extension, which is that we don't trust the program.

hmm i guess letting a program call close_account isnt too bad since its already required to be empty of tokens

The case I'm worried about is wrapped SOL, where all of the SOL in the account gets sent to the destination. If I sign something and pass my wrapped SOL account, a sketchy program can still steal all of the SOL in that account.

i feel compelled to repeat (for the benefit of onlookers) that this extension is opt-in and does not break backwards compat

Sorry, to be totally clear, what I meant is: it will break things in beautiful and good ways when enabled.

But that goes against the central tenet of this extension, which is that we don't trust the program.

i would say the central tenet is more like, the program must ask for the permissions in a way that allows the user to knowingly and willingly grant them. if set authority took place via cpi, it would be a violation of that intent. we ban that case. but if set authority takes place as a visible token instruction, the user is free to do whatever stupid thing they please, just as a user is free to delegate all their tokens to a program
but the fact that the user cannot revoke close authority if they change their mind does make it different, and i agree we shouldnt be incentivizing programs to ever use this feature. i think youre right about allowing close authority but returning lamports to owner

this is my current plan, in more programmer-y (ie, making it clear what branches i need to add) format:

changes to existing processors:

transfer: if extension enabled and cpi, authority must be delegate, or abort
burn: if extension enabled and cpi, authority must be delegate, or abort
close_account: if extension enabled and cpi, destination must be owner, or abort
approve: if extension enabled and cpi, abort
set_authority:

if Account and extension enabled and cpi and authority to change is close authority and intent is to remove it, remove it
otherwise, if Account and extension enabled and cpi, abort
if Account and authority to change is owner and extension enabled, abort regardless of cpi (this is to prevent moving a CpiGuard account to a program)

new CpiGuard instruction and processor, modeled after RequiredTransferMemos interface. changing CpiGuard status in cpi is not allowed
program tests for all invariants listed above
token-client support for CpiGuard (todo after program finalized)
token-cli support for CpiGuard (todo after program finalized)

ok heres the baldest yak ive ever encountered. in doc comments, do we want to refer to the act of calling into a program like:

cpi (noun), eg "This happens in cpi."
Cpi (proper noun), eg "This happens in Cpi."
cross-program (adjective), eg "This happens cross-program." or "This happens in a cross-program context."
Cross-Program Invocation (proper noun), eg "This happens via Cross-Program Invocation."

i like 1, 2 feels more "correct" but also somewhat strange because unlike most other proper nouns here (Account, Transfer, Required Memo Transfers) it refers to an operating environment, rather than a concrete struct or enum variant

Looks like it's officially called "CPI" or "cross-program invocation" https://docs.solana.com/terminology#cross-program-invocation-cpi

ah also i grepped the monorepo and CPI is ubiquitous but Cpi nonexistent. im gonna follow the convention we use with bpf: BPF in documentation, Bpf when part of type nams

Ty


[C-Api] user-data for sink/src callback

Separate user-data for appsrc/sink callback.

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #456. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


It doesn't seem clear if it's possible to remove event listeners such as onTokenRefresh.

Thanks for the awesome plugin, I have a quick stupid question that I can't seem to determine if possible (or necessary). I would like to unregister listening to onMessageReceived and onTokenRefresh if the user is logged out and thought I more cleared way about this would be to unregister these listeners vs. just writing guards within them.
Is it possible to unregister event listeners?

Just pass an empty function:
FirebasePlugin.onTokenRefresh(function(){});


⚠ ClamAV has degraded performance

In e2b534a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 6cbd0de.


DS uses InRamImage although GDAL provider was selected

Steps to reproduce

Click on Add Layer... button.
Select a jpg file to load (I used the image from issue #889), GDAL - Images as format and click open.
See that used ram goes up although when using GDAL image provider it would stay the same.

DotSpatial version: current master
Expected behaviour
As the  formats are added to the list based on the provider that can load them, DS should load the image with the provider that corresponds to the selected format entry.
Actual behaviour
DS uses the first provider that is able to load the file (for images most often InRamImageProvider) although the list indicates that GDAL would be used.

@mogikanin Could you please have a look at this fix before I commit it to master branch?

Looks ok. You can merge it into master.


Support edge and dev flags on kitto.new CLI

When initializing a new dashboards, engineers should be able to specify whether they want to use the release version of Kitto, the edge version (current master branch), or a dev version pointing to a local copy of Kitto.

CLI interface would look like the following:
mix kitto.new # <= Creates a new dashboard with the kitto dependency pointing to the current version on hex.pm
mix kitto.new --edge # <= Creates a new dashboard with the kitto dependency pointing to the git repo
mix kitto.new --dev "kitto" # <= Creates a new dashboard pointing to the local path of "$PWD/kitto"


Provide action to detail clinical service forms

The details buttons in Clinical Services are working now

Coverage decreased (-0.1%) to 30.808% when pulling 8a3f387943b85385da85e52a4371ed43719397c5 on valvijo:master into d88962b7cd7303a6ad9d3b39d6cf0e41ea79367e on esaude:master.


please implement support for SCReAM algorithm

The SCReAM algorithm - https://github.com/EricssonResearch/scream - offers a way to efficiently compute dynamically the available bandwith for RTP streams.
Would be awesome for baresip to support optionally linking against SCReAM.
Even if over time it might turn out that the Google GCC algorithm or something else does a better job at bandwidth prediction, I imagine that work now on what seems to me the most efficient contender in the field likely aids also in hooking into alternative algorithms later.

many thanks for the input regarding congestion control. For now I have added it to
the roadmap:
https://github.com/alfredh/baresip/wiki/Roadmap
adding support for CC and testing it properly is quite a large task. Even if the 3rd party
library contains a working stack, it will still have to be integrated with baresip.
personally I have no time to work on this any time soon. If someone is interested
in implementing and testing this, please let me know.
/Alfred


Update Docker File and/or Project Dependencies Such that the as builder image is not GB of data

Is your feature request related to a problem? Please describe.
Currently when trying to build the container image locally it takes a very log time and alot of space (see additional context below). This means that not all developers are able to build this image and test their work in an iterative way.
Describe the solution you'd like.
I would like the as builder image to be as small as possible so that it can be built with a standard podman vm. I'm not sure if this is due to the docker file and build process, or the dependencies that the project is pulling in. Further investigation is needed.
Describe alternatives you've considered.
N/A
Additional context.
Below are the image sizes of the entire build process, the image marked as <none> is the as builder image.
8:16
─acornett at acornett-mac in ~/go/src/github.com/acornett21/operator-certification-operator on fix_weird_build_issue✘✘✘
╰─± podman images
REPOSITORY                                     TAG         IMAGE ID      CREATED        SIZE
quay.io/opdev/operator-certification-operator  latest      b91df0adf025  2 minutes ago  163 MB
<none>                                         <none>      839a40940b8c  3 minutes ago  3.59 GB
docker.io/library/golang                       1.17        e5993351274b  4 hours ago    963 MB
registry.access.redhat.com/ubi8/ubi-minimal    latest      cc54f67dc341  4 weeks ago    107 MB

/assign


Ownerhash unavailability to wrapped names

Ownerhash is not available to wrapped names due to logic misplacement in CCIP2ETH:resolve()
Fix only possible upon re-deployment in future releases

Fixed by https://github.com/namesys-eth/ccip2-eth-resolver/commit/22800e11ae0ea796658c89d3ce84433283fcaafc


Project obsolete?

Doesn't seem to work with the latest version of React / Xcode / iOS / Google SDK.

@nuthinking Can't say so. I successfully implemented a solution using this lib. The only obsolete thing here is README - the link to Swift bridge creation is really obsolete.

@pkantsedalov How did you do it? Google doesn't provide google-services.json anymore right?

@arju88nair I didn't even download anything from Google. Just copypasted files from current repo to my native sources and added Swift bridge. After that everything works fine.

So it must be me. Thanks for the info!


prefix for sio in example data is incorrect

sio prefix is:
http://semanticscience.org/resource/

Original bug report (came in through FiaB)
yarrrml-rdfizer                  | arguments: /mnt/data/CARE_yarrrml.yaml --outputfile /mnt/data/triples/CARE.nq --serialization nquads
yarrrml-rdfizer                  | mapper arguments: --outputfile /mnt/data/triples/CARE.nq --serialization nquads
yarrrml-rdfizer                  | node:events:491
yarrrml-rdfizer                  |       throw er; // Unhandled 'error' event
yarrrml-rdfizer                  |       ^
yarrrml-rdfizer                  |
yarrrml-rdfizer                  | Error: Invalid IRI found in prefix delcaration: "<https://sio.semanticscience.org/resource/"
yarrrml-rdfizer                  |     at Reader.error (/yarrrml-parser/node_modules/@graphy/content.ttl.read/main.js:873:9)
I'm not sure why getting the prefix wrong in the yarrrml would cause this error... but it may be related to having a different sio prefix in the CSV... (???)  Or something happens in the Hefesto stage?
It's a werid one!

Oh... I see the problem.  You need to update the prefix, but that isn't what is causing the problem :-)

SIO prefix changed to http://semanticscience.org/resource/


Add Community Plugin Repository to README

I think a link to
https://github.com/Mixaill/awesome-gog-galaxy
should be added to the README, so users can find community plugins more easily, since they are directed from the GOG Galaxy Client to this repository.

Instead of providing links to a third party repositories, we're thinking about adding something more convenient and user-friendly. Please stand by :)

Any developers who want their plugin to be searchable in the GLX should raise a ticket (GLX -> cogwheel menu -> Report Issue). After that procedure is complete, plugin will be available for all GLX users.


tried on both Windows and Ubuntu - not working...

after entering name and password, always returns the following
Traceback (most recent call last):
File "giveaways.py", line 102, in
main()
File "giveaways.py", line 88, in main
login(session, username, password)
File "giveaways.py", line 11, in login
form = tree.xpath('//div[@id="signInForm"]')[0]
IndexError: list index out of range
I've even checked by resetting my password - I use my email and password to login online, but always this error with the script

+1

@skulltech any update on this?

Hey @vaibhavpacharya sorry I totally missed this. Will look into this.

any chance you'll work on this again?


Investigate options for DSDay ticketing

What
Investigate options for ticketing now that Eventbrite charges
Why
Eventbrite charges for free events now. Also it didn't fulfil all our needs anyway.
Who needs to work on this
Imran, Antoni
Who needs to review this
PM & DM
Done when

[x] Alternative platforms investigated
[x] Proposal pitched to DSDay team - Google doc
[ ] Test events created to demonstrate attendee experience
[ ] Dependency: Needs to be compatible on agreed payment mechanism https://github.com/alphagov/govuk-design-system/issues/3016
[ ] New ticketing platform selected

Options

Ticket Tailor
Humanitix

Investigation doc

Offering Humanitix as a option, if they're available in the UK.
It's an Australian events ticketing company that seems to have a strong focus on accessibility: https://humanitix.com/au/accessible-events

One idea we could (re)visit is using Hopin for ticket registration, and billing with its Hopin's paid ticketing feature.
It's worth considering as the previous issue with ticket rushes would probably be smoothed out if there's a payment involved. Probably enough that we can probably manage through support.
It'd require working with a Stripe account, which feature-wise is pretty well-regarded.
Con however, is that the ticketing fee is quite steep for the 'starter' plan, nearly 10% total. The fees are also non-refundable so we need to be clear we'd only be able to issue partial refunds minus the fees.

I've filled out the current batch of options and added requirements I'm aware of.
Thanks @davidc-gds, Humanitix looks promising — it has the "pending tickets" functionality which only Eventbrite seemed to have (to manage high demand for tickets and equal opportunity for people to get tickets)! I can see UK paid events so presumably it's possible for us to use!

Added an extra step proposed by Antoni to create test events in our top 2 choices — Ticket Tailor and Humanitix — for DSDay team to better see what the attendee experience looks like.


Improve handling of S3 offloading configuration in other regions

Is your enhancement request related to a problem? Please describe.
Currently, when using S3 offloading in a region other than us-east-1, the underlying jclouds library does some non-standard AWS things which require both:
A) the policy Pulsar is running as to have GetBucketLocation permissions and
B) to change the endpoint to use a region specific endpoint
This causes confusion which is not well documented and difficult to explain, and different from most AWS implementations. See https://github.com/apache/pulsar/issues/3833 for context
Describe the solution you'd like
We should do 2 things

See if we can eliminate the need for GetBucketLocation, looking at https://github.com/apache/jclouds/blob/31a3e5b5df1543d04098e3a694130b7ae8e6e079/apis/s3/src/main/java/org/jclouds/s3/config/S3HttpApiModule.java#L91 it appears to only be used when jclouds detects multiple regions. Where jcloud is getting more than one region from isn't clear, but if the user sets a region, we should just use that single region and skip the getBucketLocationCheck
Ensure that setting just the region is sufficient to configure the correct endpoint. Getting rid of the GetBucketLocation check may be sufficient such that the default endpoint works, otherwise, we should build the correct endpoint name if the region is specified but no endpoint is manually provided

Describe alternatives you've considered
Another consideration (and perhaps still a longer term goal) is to replace the use of jcloud for AWS (but still use it for other cloud providers) as jcloud does have some other behavior that differs from AWS.
Additional context

@Renkai Could you please take a look at this issue?

@Renkai Could you please take a look at this issue?

If my understand is not wrong, current jcloud API we are using event don't permit us to set region manually, it have to be generated by endpoint https://github.com/apache/pulsar/blob/98ad39ffa51239e389c73411dfb8df7f5592a5aa/tiered-storage/jcloud/src/main/java/org/apache/bookkeeper/mledger/offload/jcloud/provider/JCloudBlobStoreProvider.java#L283
Maybe we should help Jcloud make right error info, or we can use the official SDK of AWS to generate Jcloud compatible endpoint in advance.

If my understand is not wrong, current jcloud API we are using event don't permit us to set region manually, it have to be generated by endpoint https://github.com/apache/pulsar/blob/98ad39ffa51239e389c73411dfb8df7f5592a5aa/tiered-storage/jcloud/src/main/java/org/apache/bookkeeper/mledger/offload/jcloud/provider/JCloudBlobStoreProvider.java#L283
Maybe we should help Jcloud make right error info, or we can use the official SDK of AWS to generate Jcloud compatible endpoint in advance.

It might be a long journey to refactor our blob client to solve this issue

It might be a long journey to refactor our blob client to solve this issue

Confirmed w/ @Renkai, currently they are solving this issue. Will add docs later.

Confirmed w/ @Renkai, currently they are solving this issue. Will add docs later.

Confirmed w/ @Renkai, it might take some time to solve this issue, but now I can add the workaround to docs to make users clear.

Confirmed w/ @Renkai, it might take some time to solve this issue, but now I can add the workaround to docs to make users clear.

A workaround patch in doc is available here.
https://github.com/apache/pulsar/pull/9366

Move this to the next release.

Move this to the next release.

Removing the release label. We need a PR to have a release.

If you are not in us-east-1 then you can workaround this issue in broker.conf
I'm using terraform and ansible - here's the broker.conf template
s3ManagedLedgerOffloadBucket={{ s3_bucket }}
s3ManagedLedgerOffloadRegion={{ s3_region }}
s3ManagedLedgerOffloadServiceEndpoint={{ s3_url }}

Here is the setting of these facts in the ansible playbook.
        s3_bucket: "{{ tf_s3_bucket }}"
        s3_region: "{{ tf_s3_region }}"
        s3_url: "https://{{ tf_s3_bucket }}.s3.{{ tf_s3_region }}.amazonaws.com"

I read the bucket and region from a file created by terraform:
    - name: Get variables from terraform
      include_vars: ./tf_ansible_vars.yaml

In terraform the bucket and region are from the terraform.tfvars and written like so:
region          = "us-west-2"
ami             = "ami-9fa343e7" // RHEL-7.4
s3_bucket       = "omb-testing-1"

# Export Terraform variable values to an Ansible var_file
resource "local_file" "tf_ansible_vars" {
  content = <<-DOC
    tf_s3_bucket: ${var.s3_bucket}
    tf_s3_region: ${var.region}
    DOC
  filename = "./tf_ansible_vars.yaml"
}

Here's a possible work around for some people's use cases: https://stackoverflow.com/questions/73169813/jclouds-getbucketlocation-timeout-on-getblob/73902608#73902608
Note also that this ticket also suggests a possible general solution whereby jclouds provides a mechanism for users to pre-load the bucket-to-region LoadingCache with key/value pairs for their buckets that are in known regions. This would seem to be simpler than trying to rework the api from top to bottom to pass in the user endpoint.


Pyam does currently not support 3.12

It's been a little over a month since python 3.12 was officially released.
Would be worth a short to see if it's out of the box compatible if that hasn't been tested so far.

I can tell you at least one dependency that is not yet released for Python 3.12… https://github.com/iiasa/ixmp4

Ah right, then we'll have to revisit this at some point. I'd keep this issue open though.

ixmp4 is out now: https://pypi.org/project/ixmp4/ :)
So please check if pyam now supports 3.12 and if it does, please do another release without the version pin :)

Closed via #825.


Install groovy

Install groovy instead of using older Ubuntu packaged version

@edwardmlyte I amended initial commit with change to update the development-environment-base.json apologies


Setting to enable/disable XML documentation comments generator

Dear @365businessdev,
The AL Code Outline extension offers a similar feature for generating documentation comments, which can be disabled through a setting alOutline.docCommentsType.
Could you add a setting that allows us to disable documentation comments to be created after typing /// from this extension? This way we can choose one of the two implementations.

New setting enableDocComments in version 0.3.1


Adding dependabot.yml file

We need to add the dependabot.yml file as it helps us to keep our dependencies up to date. Every day, it checks your dependency files for outdated requirements and opens individual PRs for any it finds.
@amanjaiman1 please assign me this issue under gssoc'23.

We already have :)


Add fromController method that accepts a PinotClientTransport

feature (partially fixes #10924).
ConnectionFactory class is used to create instances on pinot client's Connection class. There are different methods available depending upon the kind of broker that we want to use. All of these except fromController also provide a variant to accept a PinotClientTransport from the user.
We are wrapping around the ConnectionFactory class in the Vert.x wrapper for pinot client to provide our custom transport. Since the constructors of the Connection class are package-private, we cannot directly add this method to an external package. Further, this method seems to be absent from the class only as a mistake (there are methods to specify custom transports with all other brokers).
Hence, adding this method.

Codecov Report

Merging #11013 (44f526b) into master (379d761) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #11013      +/-   ##
==========================================
- Coverage    0.11%    0.11%   -0.01%
==========================================
  Files        2192     2192
  Lines      118016   118019       +3
  Branches    17869    17869
==========================================
  Hits          137      137
- Misses     117859   117862       +3
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
0.00% <0.00%> (ø)

integration1temurin17
?

integration1temurin20
?

integration2temurin11
?

integration2temurin17
?

integration2temurin20
?

unittests1temurin11
?

unittests1temurin17
?

unittests1temurin20
?

unittests2temurin11
?

unittests2temurin17
0.11% <0.00%> (ø)

unittests2temurin20
?

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

Impacted Files
Coverage Δ

...ava/org/apache/pinot/client/ConnectionFactory.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Bug]: The pg database archives the ob database, and the log prints a null pointer

ODC version
ODC432
OB version
pg9
oboralce422
What happened?
The pg database archives the ob database, and the log prints a null pointer

What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?
。
Anything else we need to know?
No response

The pg database password is empty.

fixed


Keep history of actions until completion or approval

As a DM, I want to be able to verify the rolls/changes made by the users, so that we can check if they are doing it correctly or not cheating.   The history should stay present until a DM approves the changes when they could then be removed.

Hey thanks for the suggestion! This has been requested a couple times now, so I'll look at implementing this sometime shortly.


Pass association/batch_key to query function

Would it be possible to add the association name to the options passed to the query function when using a custom query?
For example:
Dataloader.load(loader, Post, :replies, post)

would pass %{assoc_name: :replies} or something similar to the opts parameter in the query function.

@Un3qual can you elaborate on your use case?

It would be useful to easily be able to have different behavior for the query function depending on which association I'm loading.

It's a lot less fragile if instead the options are passed in directly:
Dataloader.load(loader, Post, {:replies, %{some_option: true}}, post)


TPv2 Add the ability to inspect a cert/DS

This PR adds the ability to inspect a user provided cert chain or the one from a specific DS. This requires the use of a new library node-forge. This library is relatively large (~200Kb compressed) and as such the functionality is relegated to it's own module.

Which Traffic Control components are affected by this PR?

Traffic Portal v2

What is the best way to verify this PR?
Ensure the SSL chunk is only loaded when navigating to one of the two endpoints, core/certs/ssl and core/certs/ssl/ds/:xmlId. The generic endpoint has a sidebar entry under Other and should work.
For DS cert (which needs to be navigated to manually), there should be two tabs. One displaying the information that TO provides, and the other displaying the processed cert info.
The generic cert also has two tabs, the processed tab like with DS cert, and an input tab where the user can input the cert. The only validation that should occur on this tab is ensuring the cert field is not empty.
The processed cert screen should always show the chain in root -> client order. It should also display the detected order (if possible). In case of a cert that doesn't match or a cert doesn't parse it should properly update the order to "Unknown" and that specific certs name to "Error".

PR submission checklist

[x] This PR has tests
[ ] This PR has documentation
[ ] This PR has a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

node-forge is kinda big - I'm just wondering if the things you need to do can be accomplished with a SubtleCrypto interface? It's pretty basic, but if it does have the required functionality then it'd be the superior choice IMO.

I would've loved to use a native browser api but the ones that exist are insufficient and at best would require significant amounts of code to replicate the current behavior. SubtleCrypto in particular requires knowledge of the cert crypto algorithm to even call the constructors.


[Extension bug]Can't log in with master password

I installed the Bitwarden CLI and extension and upon logging in, it prompted me to enter my master password which I did correctly several times, but it kept telling me "Invalid Credentials". After it showed me the first time, I logged in to the Bitwarden Desktop app using the same master password to make sure I'm not mistaken and it logged in successfully, but I kept trying it on the Raycast extension and it kept telling me "Invalid Credentials". Is there any fix to this?

Hi, this is a duplicate of #360
This error is due to some transformation made by raycast on the text input field.
I will update the extension as soon as the api is updated to support raw text in input fields. Sorry for the inconvenience :/

Oh, thanks for the clarification, does that mean I should just close the issue or leave it open, maybe for later reference?

Hi, this is a duplicate of #360 This error is due to some transformation made by raycast on the text input field.
I will update the extension as soon as the api is updated to support raw text in input fields. Sorry for the inconvenience :/

Let's close it, #360 will be fixed in the next release


Move u64 to u32 when packing is introduced

Waiting on compiler to automatically pack contiguous u32s.
If not, we can implement this ourselves.

https://github.com/snapshot-labs/sx-starknet/issues/483


Add CARGO_PATH environment variable

This PR adds an environment variable CARGO_PATH to specify search path for programs spawned by cargo.
If there is a newer compiler than system compiler on PATH, some rust compilation fail.
This is reported at https://github.com/rust-lang/rust/issues/58394 and https://github.com/rust-lang/cargo/issues/6582.
To resolve the issue, this PR adds CARGO_PATH to specify compiler and linker path.
For example, https://github.com/rust-lang/rust/issues/58394 can be resolved like below.
$ echo $PATH
~/.linuxbrew/bin:~/.cargo/bin:/usr/bin:/bin
$ cargo build
/// failed
$ export CARGO_PATH=~/.cargo/bin:/usr/bin:/bin
$ cargo build
/// success

In this case, cargo without CARGO_PATH calls ~/.linuxbrew/bin/cc as linker, but rustc expects system linker, therefore the compilation fails. Alternatively cargo with CARGO_PATH calls system linker and the compilation succeeds.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Eh2406 (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors r? @alexcrichton

Thanks for the PR! I would personally be hesitant to merge this feature though. This seems like a bit of hack in Cargo to work around something that may not be fully understood? Are there perhaps other ways to solve this problem without resorting to this hammer?

In my understanding about https://github.com/rust-lang/rust/issues/58394, the followings must be system toolchain because official rustc binary is linked to system libc.

Linker called by cargo
C compiler called by cc-rs

Because both of them use PATH to search toolchain, I think the issue can be resolved by CARGO_PATH.
Although I can understand this feature is too large.
Currently I have two other ways, but I think both of them are not good.
individual setting
Both of them can be set individually. Linker called by cargo can be set by ~/.cargo/config like below:
[target.x86_64-unknown-linux-gnu]
linker = "/usr/bin/cc"

C compiler called by cc-rs can be set by CC environment variable.
export CC=/usr/bin/cc

Pros
No modification is needed.
Cons
CC environment variable affects other programs like make.
If another crate like cc-rs will be created, another setting will be needed.
wrapper of cargo
A wrapper of cargo can set PATH passed to cargo.
For example, zsh function like below:
function cargo() {
      PATH=~/.cargo/bin:/usr/bin:/bin command cargo $@
}

Pros
No modification is needed.
Cons
This is not an official feature of cargo/rustc. So I would be hesitant to announce this solution to other linuxbrew users.

If the goal here is to switch linkers then configuring .cargo/config is the way to do that, but I'm personally still not really understanding what the motivation is to switch out PATH

Linker called by cargo can be specified through .cargo/config, but C compiler/linker used at build.rs is still searched in PATH. So I want to switch PATH.

Ok if this is purely about switching linkers I'm going to close this since that's done with various other configuration that we have in Cargo. Switching rustc's linker is done via .cargo/config, and build scripts should provide their own way of configuring linkers. For crates using cc, for example, there's a variety of env vars to configure.

Ok. I will resolve this issue by cargo wrapper function.
Thanks.

How Windows 10 Solves this Problem

Switching rustc's linker is done via .cargo/config, and build scripts should provide their own way of configuring linkers.

This doesn't really work in a number of cases without something like #9322.


Gettin' Rekt On My Note 10+. Totally works on my SM-T150 So I Feel Confident I Know How To Use It

[ ] I have read the FAQ.
[ ] I have searched in existing issues.

Environment

OS: Android 12
scrcpy version: 1.16
installation method: Uhm I'm sorry I'm not sure I just grabbed it from here on GH
device model: Note 10+
Android version: 12

Describe the bug
connected to <IP_ADDRESS>:34649
INFO: scrcpy 1.16 https://github.com/Genymobile/scrcpy
C:\Users\Andrew\Downloads\SM-T510\platform-tools\scrcpy-se... file pushed, 0 skipped. 16.2 MB/s (33622 bytes in 0.002s)
adb.exe: error: more than one device/emulator
ERROR: "adb reverse" returned with value 1
WARN: 'adb reverse' failed, fallback to 'adb forward'
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27183, retrying on 27184
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27184, retrying on 27185
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27185, retrying on 27186
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27186, retrying on 27187
27187
[server] INFO: Device: samsung SM-N975U (Android 12)
INFO: Renderer: direct3d
INFO: Initial texture: 1080x2280
WARN: Device disconnected
[server] ERROR: Exception on thread Thread[main,5,main]
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:75)
at com.genymobile.scrcpy.ScreenEncoder.setDisplaySurface(ScreenEncoder.java:216)
at com.genymobile.scrcpy.ScreenEncoder.internalStreamScreen(ScreenEncoder.java:86)
at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:55)
at com.genymobile.scrcpy.Server.scrcpy(Server.java:76)Press any key to continue...
connected to <IP_ADDRESS>:34649
INFO: scrcpy 1.16 https://github.com/Genymobile/scrcpy
C:\Users\Andrew\Downloads\SM-T510\platform-tools\scrcpy-se... file pushed, 0 skipped. 16.2 MB/s (33622 bytes in 0.002s)
adb.exe: error: more than one device/emulator
ERROR: "adb reverse" returned with value 1
WARN: 'adb reverse' failed, fallback to 'adb forward'
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27183, retrying on 27184
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27184, retrying on 27185
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27185, retrying on 27186
adb.exe: error: more than one device/emulator
ERROR: "adb forward" returned with value 1
WARN: Could not forward port 27186, retrying on 27187
27187
[server] INFO: Device: samsung SM-N975U (Android 12)
INFO: Renderer: direct3d
INFO: Initial texture: 1080x2280
WARN: Device disconnected
[server] ERROR: Exception on thread Thread[main,5,main]
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:75)
at com.genymobile.scrcpy.ScreenEncoder.setDisplaySurface(ScreenEncoder.java:216)
at com.genymobile.scrcpy.ScreenEncoder.internalStreamScreen(ScreenEncoder.java:86)
at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:55)
at com.genymobile.scrcpy.Server.scrcpy(Server.java:76)Press any key to continue...
INFO: scrcpy 1.16 https://github.com/Genymobile/scrcpy
C:\Users\Andrew\Downloads\SM-T510\platform-tools\scrcpy-se...1 file pushed, 0 skipped. 8.9 MB/s (33622 bytes in 0.004s)
[server] INFO: Device: samsung SM-N975U (Android 12)
adb.exe: error: more than one device/emulator
ERROR: "adb reverse --remove" returned with value 1
[server] ERROR: Exception on thread Thread[main,5,main]
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:75)
at com.genymobile.scrcpy.ScreenEncoder.setDisplaySurface(ScreenEncoder.java:216)
at com.genymobile.scrcpy.ScreenEncoder.internalStreamScreen(ScreenEncoder.java:86)
at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:55)
at com.genymobile.scrcpy.Server.scrcpy(Server.java:76)
at com.genymobile.scrcpy.Server.main(Server.java:225)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:374)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:73)
... 7 more
Caused by: java.lang.IllegalArgumentException: displayToken must not be null
at android.view.SurfaceControl$Transaction.setDisplaySurface(SurfaceControl.java:3370)
at android.view.SurfaceControl.setDisplaySurface(SurfaceControl.java:2344)
... 9 more
INFO: Renderer: direct3d
INFO: Initial texture: 1080x2280
WARN: Device disconnected
Press any key to continue...

Android 12 requires scrcpy >= 1.18. Just upgrade.


valid URL containing an underscore cannot be added

From #202
Confirming a valid URL containing an _ (underscore)  cannot be added to the system
Screenshot

Example URLs

http://infoseek_rip.g.ribbon.to/crspalm.hp.infoseek.co.jp/
http://a_pollett.tripod.com/mayumihf.htm

Bug
So there is a problem with the process of checking a URLs, as both of the above are valid.

Yeah, URL validation is not perfect, and from what I understand this is quite opinionated. For now linkding just uses the default Djanog URL validator, so you could also report it there. As a workaround linkding provides an option to disable URL validation: https://github.com/sissbruecker/linkding/blob/master/docs/Options.md#ld_disable_url_validation

Django won't fix
https://code.djangoproject.com/ticket/18517

I'm here one year later trying linkding again (thanks to Browser Companion app for iOS/macOS) and these two URLs failed to import again, not that I expected it to have changed.
:)


Microsoft.Midi.GmDls not available for ARM64

Already reported this via the Feedback Hub, but no response/action so far:
The processor architecture of the project being built "ARM64" is not supported by the referenced SDK "Microsoft.Midi.GmDls, Version=10.0.17134.0". Please consider changing the targeted processor architecture of your project (in Visual Studio this can be done through the Configuration Manager) to one of the architectures supported by the SDK: "x86, x64, ARM".

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

ID: 90265caf-b1af-f015-674a-a015e3a35d65
Version Independent ID: bf193eb6-cd09-7538-12ef-da3cd0188e8d
Content: MIDI - UWP app developer
Content Source: windows-apps-src/audio-video-camera/midi.md
Product: uwp
GitHub Login: @drewbatgit
Microsoft Alias: drewbat

The framework package Microsoft.Midi.GmDls itself is in fact neutral and therefore works on ARM64.  The issue is that the manifest file included with it in the SDK is limiting it to only x86, x64, and arm.
That means that as a workaround before the fix ships in an upcoming SDK flight, you can edit the manifest XML file directly at %programfiles(x86)%\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.Midi.GmDls\10.0.17763.0\SDKManifest.xml and add arm64 to the SupportedArchitectures field.  With that change, projects using Microsoft.Midi.GmDls will build and run successfully as ARM64.

The workaround does the trick so I'm closing this issue. The WoA team confirmed this will be fixed in an upcoming SDK. Thanks a lot.


Only 3 types available?

I found 5 types in BugDetection.py but only 3 types are listed in README.md. Can these two types(IncorrectAssignment and MissingArg) be used?

The other two kinds of bugs are experimental and we found them to work less well than the three you find in the README, which is why they are disabled by default.


Rule 942100 is still triggered after setting ruleRemoveById

Describe the bug
Hi, rule 942100 is triggered with audit log:
ModSecurity: Warning. detected SQLi using libinjection. [file "/usr/local/owasp-modsecurity-crs-3.0.2/rules/REQUEST-942-APPLICATION-ATTACK-SQLI.conf"] [line "43"] [id "942100"] [rev "1"] [msg "SQL Injection Attack Detected via libinjection"] [data "Matched Data: 1o(1& found within ARGS:2dc05eb6: 220+(820||115 nF)"] [severity "2"] [ver "OWASP_CRS/3.0.0"] [maturity "1"] [accuracy "8"] [hostname "<IP_ADDRESS>"] [uri "/a/b/c/d"] [unique_id "162425608090.030571"] [ref "v73,17"]
ModSecurity: Access denied with code 404 (phase 2). Matched "Operator `Ge' with parameter `5' against variable `TX:ANOMALY_SCORE' (Value: `5' ) [file "/usr/local/owasp-modsecurity-crs-3.0.2/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "44"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 5)"] [data ""] [severity "2"] [ver ""] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "<IP_ADDRESS>"] [uri "/a/b/c/d"] [unique_id "162425608090.030571"] [ref ""]

I've tried to exclude it by creating this exclusion rule in REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf; however, 942100 is still being triggered.
SecRule REQUEST_URI "@streq /a/b/c/d" \
        "phase:2,log,pass,id:21506,ctl:ruleRemoveById=942100"

Expected behaviour
I expect 942100 not to be triggered with the exclusion rule for the particular uri.
Additional context
As suggested by someone on serverfault.com, I've also tried excluding the rule in phase 1 but to no avail.
Your Environment

CRS version (e.g., v3.2.0): 3.0.3
Paranoia level setting: default
ModSecurity version (e.g., 2.9.3): 3.0.3
Web Server and version (e.g., apache 2.4.41): nginx 1.13.6
Operating System and version: Ubuntu 18.04.3 LTS
Container info: openresty/openresty:<IP_ADDRESS>-2-bionic

The alert message that you posted contains the URI without the query string. The variable REQUEST_URI contains the URI including the query string and then you continue with the streq operator. In rule exclusions, I usually use the beginsWith operator.
Other than that, this looks good to me.

Hi, thanks so much for your prompt response. Just to make sure I understand correctly, you are saying that although my exclusion rule's URI matches the one in the audit log, the call actually has query string and so I need to use beginsWith instead. Thanks.

Yes, exactly.
It is not obvious the audit log URI is stripped down, it's just ModSec trying to make you miserable.
beginsWith should do the job, if not, then please provide the original request and I can run a quick test.

Any update here, @skwokie? If not, we're going to close this issue soon.

Thanks so much for your help!

You're most welcome.


Fast compilation should work if there are type errors and failOnTypeErrors is false

Sorry for the lack of tests. :cry:

Thank you for submitting this.  I will check it out as soon as I can.

Thanks, @thorn0.  We can extract this method and test it that way.


[SQL] Update resources for GeoZone param

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

Changelog
Add a changelog entry for 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 are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
ASAP
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[X] SDK of .NET (need service team to ensure code readiness)
[X] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[X] PowerShell
[X] CLI
[ ] Terraform
[ ] No refresh required 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

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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.

@ericshape Can you please help me understand what are these two issues mean and how can I fix them?
Here is the draft PR for .net sdk https://github.com/Azure/azure-sdk-for-net/pull/25298

we change the v5 SDK tag, thus the SDK breaking change is expected.
same as: https://github.com/Azure/azure-rest-api-specs/pull/16716

@zhenglaizhang @msyyc @ArcturusZhang
can you please take a look? Thanks!

approve for python breaking change

@MilanBrkicFON Could you help to add x-ms-enum for SyncGroups_ListLogs in specification\sql\resource-manager\Microsoft.Sql\preview\2021-02-01-preview\SyncGroups.json to avoid enum naming breaking changes for future. Other breaking changes seems acceptable.

I agreed with @tadelesh offline that I will not fix SyncGroup as part of this PS.

/azp run


[staging] perl: 5.38.0 -> 5.38.1, 5.36.1 -> 5.36.2

Description of changes
Fixes CVE-2023-47038, CVE-2023-47039 (windows)
Updates:

perl538: 5.38.0 -> 5.38.1
https://metacpan.org/release/PEVANS/perl-5.38.1/changes
https://www.nntp.perl.org/group/perl.perl5.porters/2023/11/msg267354.html

perl536: 5.36.1 -> 5.36.2
https://metacpan.org/release/PEVANS/perl-5.36.2/changes
https://www.nntp.perl.org/group/perl.perl5.porters/2023/11/msg267353.html

(NOTE: A newer 5.38.1a release also exists with minor changes to META.json)
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

This is broken currently, see https://github.com/Perl/perl5/issues/21671

5.38.1 was built OK in nixpkgs from perl-5.38.1.tar.gz. Is the test failure you're mentioning for the docker images caused by additional checks somehow?
Observing that perl-5.38.1a.tar.gz contains that META.json change, but not sure if this should be used instead.
I think we should wait merging this until upstream clarifies.
diff '--color=auto' -ur perl-5.38.1/META.json perl-5.38.1a/META.json
--- perl-5.38.1/META.json	2023-11-21 17:39:32.000000000 +0100
+++ perl-5.38.1a/META.json	2023-11-25 16:44:56.000000000 +0100
@@ -106,7 +106,7 @@
          "vxs.inc"
       ]
    },
-   "release_status" : "testing",
+   "release_status" : "stable",
    "resources" : {
       "bugtracker" : {
          "web" : "https://github.com/Perl/perl5/issues"
@@ -120,5 +120,5 @@
       }
    },
    "version" : "5.038001",
-   "x_serialization_backend" : "JSON::PP version 4.16"
+   "x_serialization_backend" : "JSON::PP version 4.07"
 }

We could alternatively add patches:

https://github.com/Perl/perl5/commit/92a9eb3d0d52ec7655c1beb29999a5a5219be664 Fix read/write past buffer end: perl-security#140
https://github.com/Perl/perl5/commit/8b943e377b1541a72513bb824d45603ab9a7fc97 win32: default the shell to cmd.exe in the Windows system directory (but windows, so prob not needed for nixpkgs)

Yeah, for 5.38.1 I was working with the source and sha256 as announced in http://nntp.perl.org/group/perl.perl5.porters/267354 - I know of 5.38.1a but there's no follow-up announcement yet.

Due to issues with these releases upstream, a new set of releases is planned:
5.38.2, 5.36.3, 5.34.3
https://www.nntp.perl.org/group/perl.perl5.porters/2023/11/msg267372.html
Let's wait for those before we continue

PR has been updated with new 5.38.2, 5.36.3 and corresponding perl-cross
https://www.nntp.perl.org/group/perl.perl5.porters/2023/11/msg267400.html


Add DevSecOps

https://github.com/TaptuIT/awesome-devsecops
This list is a collection of resources and tooling related to DevSecOps. DevSecOps is an extension of DevOps - a methodology and philosophy for software development - that aims to incorporate security expertise and testing into the development lifecycle, with the goal of creating more secure software.
This list of resources can help software development teams learn about and adopt DevSecOps practices and tooling, resulting in more secure software for everybody.
Reviewed PRs: #1756 #1758
By submitting this pull request I confirm I've read and complied with the below requirements 🖖

unicorn

This PR is a resubmission for #1760 after the old PR was closed due to renaming the default branch.
Since that PR was closed, I have resolved all noted issues including:

Renaming default branch to main.
Replaced banner image with high-DPI version.
Added a description for each entry.
Updated the link and description in this repository, as you suggested.

Please let me know if there are any further issues, and thanks for all your effort :D

In DevSecOps is an extension of the DevOps movement that aims to bring security practices into the development lifecycle through developer-centric security tooling and processes., can you linkify DevSecOps and DevOps to good sources where the user can read more about them?

@sindresorhus Good suggestion, I've added links to Atlassian and Rapid7, two really good resources for DevOps and DevSecOps respectively.
@mhxion Thanks for the suggestion, but having two levels of nested lists would be against the list guidelines

Should only have one level of nested lists, preferably none.

Tweet: https://twitter.com/awesome__re/status/1279131546897641473


Networking: Bad Gateway should lead to explicit pipeline failure

Current behavior:
If an endpoint isn't available, nginx responds with its default 502 response.
Expected behavior:
Rudra makes it explicity, that tests are failing, because the host cannot be resolved.
Similar issues with timeouts, etc. should also be taken into account.

Modified behavior to print out warning when all responses are 502s.


Doesn't work with date?

If I import a date, I receive weird data instead of the date.

use PhpOffice\PhpSpreadsheet\Shared\Date;
 ImportField::make('special_price_to')
                        ->mutateBeforeCreate(fn($value) => Date::excelToDateTimeObject($value)
                            ->format('y-m-d'))
                    ,

Did the trick


TechStack | a post with comments

https://saicoco.github.io/al-folio/blog/2015/comments/
an example of a blog post with comments

test


reorganize to use an internal mpsc event queue & processing thread

This allows use from tokio applications & other async runtimes.
This also drops the use of the tracing-serde-* crates and moves that
functionality within itself. These changes would have required
deviating even further from upstream in incompatible ways. This also
should improve performance because we're going to be cloning fewer
things that we don't end up even using.
Breaking Changes
This adds a finish function to TracingModality that must be called
before the main thread exits to ensure that all tracing messages have
been flushed to Modality. (This is the same thing that open telemetry
does.)
This also removes the ModalitySubscriber type that was previously
impossible to construct anyway and replaces it with
ModalityLayer::into_subscriber().

tracing-modality/src/layer.rs is largely tracing-serde-subscriber and tracing-modality/src/ingest.rs is largely tracing-serde-modality-ingest, except stripped down and specialized for handling exactly the information that we need here.

Force pushed squashing out the fixups


delete Submission not send notification

getDBUsersWithRole(pool = pool, profile = profile, role = config$dcf$roles$manager) return zero recipient

Require usage of getDBUsers(pool = pool, profile = profile, role = "manager")


Branch bugs modules

Module tab now refreshes on switching to it.
Modules can be deleted when related tasks are complete.
Tasks that are complete and no longer editable can keep deleted modules.
Testcases.
Modules del error message to follow countdowns

Codecov Report

Merging #224 (d7850c7) into master (7b4d2c6) will increase coverage by 0.82%.
The diff coverage is 60.86%.

@@             Coverage Diff              @@
##             master     #224      +/-   ##
============================================
+ Coverage     67.94%   68.76%   +0.82%
- Complexity      924      946      +22
============================================
  Files           126      126
  Lines          3048     3064      +16
  Branches        402      407       +5
============================================
+ Hits           2071     2107      +36
+ Misses          842      825      -17
+ Partials        135      132       -3

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/seedu/tr4cker/logic/LogicManager.java
66.66% <0.00%> (+10.78%)
12.00 <0.00> (+5.00)

...seedu/tr4cker/storage/JsonSerializableTr4cker.java
84.61% <0.00%> (ø)
11.00 <0.00> (ø)

src/main/java/seedu/tr4cker/ui/MainWindow.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

.../main/java/seedu/tr4cker/ui/module/ModuleCard.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

src/main/java/seedu/tr4cker/model/Tr4cker.java
91.35% <75.00%> (+8.02%)
33.00 <0.00> (+4.00)

...va/seedu/tr4cker/logic/commands/ModuleCommand.java
94.59% <100.00%> (+0.15%)
16.00 <0.00> (ø)

...eedu/tr4cker/logic/parser/ModuleCommandParser.java
95.45% <100.00%> (ø)
11.00 <0.00> (ø)

...in/java/seedu/tr4cker/logic/parser/ParserUtil.java
92.00% <100.00%> (+0.51%)
39.00 <4.00> (+4.00)

src/main/java/seedu/tr4cker/model/Model.java
55.55% <100.00%> (+5.55%)
5.00 <0.00> (ø)

...rc/main/java/seedu/tr4cker/model/ModelManager.java
95.53% <100.00%> (+10.57%)
56.00 <1.00> (+6.00)

... and 5 more

Continue to review full report at Codecov.

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


how to start the docker without update?

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04):Ubuntu 16.04
Apollo installed from (source or binary):source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0):3.5

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:
I want to know why when I start the docker ,it will take a long time today ,yesterday is ok! is there a good way to stop this update and also start the docker ?

Supporting materials (screenshots, command lines, code/script snippets):

@debuleilei docker takes care of updating the packages and it should not happen more than once. Has this happened more than once?

Closing this issue as it appears to be resolved. Feel free to reach out if you have additional questions. Thanks!


Is there some way to put components in table?

I'm tring to add some links by markdown on table's row, for operating my data, but seems markdown won't be rendered in table component.
Is there another way to add at least two link to a table cell?
from fastapi import FastAPI
from fastapi.responses import HTMLResponse
from fastui import FastUI, prebuilt_html
from fastui import components as c
from fastui.components.display import DisplayLookup, DisplayMode
from pydantic import BaseModel

app = FastAPI()

class Fake(BaseModel):
    name: str
    action: str

@app.get("/api/", response_model=FastUI, response_model_exclude_none=True)
async def ui():
    fake = [Fake(name="demo", action="[rename](/rename) [remove](/remove)")]
    return [
        c.Page(
            components=[
                c.Table(
                    data=fake,
                    columns=[
                        DisplayLookup(field="name"),
                        DisplayLookup(field="action", mode=DisplayMode.markdown),
                    ],
                ),
            ]
        )
    ]

@app.get("/{path:path}")
def index(path: str) -> HTMLResponse:
    print(path)
    return HTMLResponse(prebuilt_html())

@Dragon-GCS,
Thanks for the feature request. Definitely something we will consider for future releases!

It would also be great to be able to embed a button into the cell.
E.g., you could add an "edit" button to open a form modal.
I think this would be really helpful.

Fixed by https://github.com/pydantic/FastUI/pull/279
Also, you might want to check out https://github.com/pydantic/FastUI/pull/308


website link

there is no link to your website in website section .assign that task to me

i want to work on this issue

there is no link to your website in website section .assign that task to me

can you please brief so i can categorize it.

I would like to work on this. Please assign this to me.

I would like to work on this. Please assign this to me.


(BKR-584) Change to use mkdir_p helper command

Makes command cross-compatible for PSWindows

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1678/
Test FAILed.

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1765/
Test PASSed.


MINOR: Correct a broken link in the README

One char change to fix the broken link to the example market making script

Thank you so much for doing this!


models generator support instead of running a macro

Is this your first time opening an issue?

[X] I have read the expectations for open source contributors

Describe the Feature
I'm curious if this package allows for the execution of multiple models consecutively. Here's my scenario: I'm utilizing Airflow, and for each data ingestion, I need to pass it through several models. This involves some data canonicalization, followed by enrichment, and finally, business transformation. My preference is to run all these models sequentially, checking the expected results only after all models have been applied to the data, rather than testing each model individually. Can this package accommodate such a workflow?
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response

Hi @megetron3, thanks for opening this issue. Currently this package does not support the use case you describe as unit testing models is not supported by this package. Let's continue the conversation about unit testing models in #12


main in Package.json

In package.json your current main is configured to ./index.js
when we use webpack and require("color-space"); it uses this index.js. this index requires your husl.js. in your husl.js it has another require("husl"); the issue here is that in our configuration this resolves to itself since it checks the current folder first. it builds successfully but throws errors during runtime because _conv is undefined.
I ended up changing my requires to require("color-space/dist/color-space"); so that webpack finds your compiled version which fixed our issues.
What do you think of changing your main: to dist/color-space.js? so that people can use require("color-space") ?

dist/color-space is built to use as a standalone module, so it exposes global colorSpace in case if you don’t use any commonJS wrapper.
It seems to be the issue of webpack, have you looked up for the solution on that? Browserify builds it just fine.
BTW, do you use that husl color space? I can just exclude it from the index.js, it is quite uncommon space and adds up extra size to build.

We do use a CommonsJS wrapper. We don't use the husl colors pace at all.
Excluding it would be awesome.

actually you can include only the color-spaces you use, the size of build will be minimal: require('color-space/hsl')

I prefer that method, I'll talk to our developer that used the lib and have him only require the spaces used.
Thanks!

Ok. So I’ll close this, as this seem to be the issue of webpack.
@sokra, please have a look.

Works fine for me. Maybe a incorrect configuration.

Probably our configuration. we have a very complicated configuration where webpack configs are generated at build time for each component and components are compiled separately.
I'll make sure that we only require whats necessary instead of the entire index.
Thanks for your help.


IDN does not work?

http://ru.wikipedia.org/wiki/IDN
It seems email_validator does not consider emails like<EMAIL_ADDRESS>as valid email addresses.
So, in model:
  validates :email, :email => true, :uniqueness => true

and then in console:
[44] studium »  u.valid?
  User Exists (0.8ms)  SELECT  1 AS one FROM "users"  WHERE ("users"."email" =<EMAIL_ADDRESS>AND "users"."id" != 18) LIMIT 1
=> true
[45] studium »  u.email =<EMAIL_ADDRESS>=><EMAIL_ADDRESS>[46] studium »  u.valid?
  User Exists (0.7ms)  SELECT  1 AS one FROM "users"  WHERE ("users"."email" =<EMAIL_ADDRESS>AND "users"."id" != 18) LIMIT 1
  User Exists (0.5ms)  SELECT  1 AS one FROM "users"  WHERE ("users"."email" =<EMAIL_ADDRESS>AND "users"."id" != 18) LIMIT 1
=> false
[47] studium »  u.errors.full_messages
=> [
  [0] "Email имеет неверное значение"
]

Thanks. This will be fixed in #49 and I've added a test case for<EMAIL_ADDRESS>


[REVIEW] AlgoSketch - C++ SFML Algorithm Visualizer

Project Link: https://github.com/zedrex/AlgoSketch

Thank you for sharing, we will review on a live stream soon 👍 It looks like you are getting great community feedback already 💥


Progress bar possibility

Hey,
Keep in mind that i'm pretty new in the front-end dev world. I'm using vuerouter with a full vuejs site, on an express nodejs server. I would love to have a progress bar during the transition of my route components.
Do you have any guide line to have the loading of the route components in a progress bar, to finaly make the transition ?
Think that would only work with the promises ?
Thanks a lot !

For exemple, i've got a video in the template of one of my components. I would love to display a loading state during the time of this video loading.

@crispouille You can use $loadingRouteData to show a progress bar while in a loading state:

    <my-component></my-component>

Also as a note for the future, these types are questions are best suited for the community forums or gitter. The issues section is for reporting bugs, enhancements, and providing development feedback. Please review the Issue Reporting Guidelines: https://github.com/vuejs/vue/blob/dev/CONTRIBUTING.md#issue-reporting-guidelines
Thanks

@crispouille if you want follow up on this question please do so in the forums and just link back to this issue for reference.
@yyx990803 I think this issue can be closed out.

vue.esm.js?efeb:591 [Vue warn]: Property or method "$loadingRouteData" is not defined on the instance but referenced during render. Make sure that this property is reactive, either in the data option, or for class-based components, by initializing the property. See: https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.

loading

nothing help?


Put this on npm!

Hey, please put this on npm and bower.. package management will be easier :)

I have never done this before, any advice?

@Pritoj bower: https://github.com/rzajac/angularjs-slider/blob/master/bower.json

I published it here: https://www.npmjs.com/package/jusas-angularjs-slider


Docs.MS Release Updates for Azure.Storage.Common

Update docs metadata and targeting for release of Azure.Storage.Common

Docs Build status updates of commit 643537f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/latest/storage.common-readme.md
:warning:Warning
View
Details

api/overview/azure/latest/storage.common-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Storage Common client library for .NET - Azure for .NET Developers' is duplicated in: 'api/overview/azure/latest/storage.common-readme.md(2,8), api/overview/azure/preview/storage.common-readme.md(2,8), api/overview/azure/storage.common-readme.md(2,8), api/overview/azure/storage.common-readme-pre.md(2,8)'. Titles must be unique within a docset.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 643537f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/latest/storage.common-readme.md
:warning:Warning
View
Details

api/overview/azure/latest/storage.common-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Storage Common client library for .NET - Azure for .NET Developers' is duplicated in: 'api/overview/azure/latest/storage.common-readme.md(2,8), api/overview/azure/preview/storage.common-readme.md(2,8), api/overview/azure/storage.common-readme.md(2,8), api/overview/azure/storage.common-readme-pre.md(2,8)'. Titles must be unique within a docset.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Task]: Fix failing testerina tests for Java 21 migration

Description
$subject
Describe your task(s)
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/43406


adding new tutorial for using spin deploy github action

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[ ] The title, template, and date` are all set
[ ] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[ ] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[ ] Has passed bart check
[ ] Has run npm run build-index
[ ] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[ ] Headings are using Title Case
[ ] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[ ] Have tested with npm run test and resolved all errors

Closing this PR - looks like bart content is missing and the license got changed again...