deps: update lestrrat-go/jwx, x/net, x/crypto

Update github.com/lestrrat-go/jwx from v1.2.25 to v1.2.29.
This includes security patches for vulnerabilities reported to us via dependabot:

lestrrat-go/jwx's malicious parameters in JWE can cause a DOS
Parsing JSON serialized payload without protected field can lead to segfault
JWX vulnerable to a denial of service attack using compressed JWE message

As far as I understand, these issues affect the JWE and JWS modules, which we don't use. We use the JWA and JWT modules to perform JWT authorization via Bearer tokens as part of the internal management API.
The update to jwx triggers version bumps for the x/net and x/crypto dependencies. If we bump these, we might as well use the latest version of these:
Update x/net from v0.14.0 to v0.24.0.
Update x/crypto from v0.12.0 to v0.22.0.
This, in turn, addresses a number of dependabot vulnerability alerts.

HTTP/2 Stream Cancellation Attack
Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin
HTTP/2 rapid reset can cause excessive work in net/http
net/http, x/net/http2: close connections when receiving too many headers

As far as I'm aware, the internal management APIs do not use HTTP/2, and the gRPC used for the control plane messaging has a separate implementation of HTTP/2. Thus, I believe the vulnerable code is not actually used by us.

This change is


Restore android workaround for CONST_STRING_DECL

Restore workaround for android initially introduced int https://github.com/apple/swift-corelibs-foundation/pull/622
https://github.com/SwiftJava/swift-corelibs-foundation/commit/6213cbabce1a4c3d9ac1573aef4aaaa8b102953b
Refix: https://bugs.swift.org/browse/SR-2587 https://bugs.swift.org/browse/SR-2588

Given that the mangling changed on ToT, is the same value here still correct?

Hi @parkera I check it in swift-3.1-RELEASE and it works there

Should I open two PR with different symbols to master and swift-3.1-branch?

Yes, they are different.

Replaced by to different PRs
#957  for master
#958 for 3.1


Includes are added even if they are guarded by #ifdef-s

When parsing includes in hlsl file all of them are added even if they are guarded by failed #ifdef
#include "header_a.ush"

#ifndef SOMEDEF
#include "header_b.ush"
#endif

Right now both header_a and header_b are included and this leads to compilation errors.

Mmh, not sure that's easily fixable.
Where is SOMEDEF defined here? In header_a?

Yes this define is from other header.
It's not that big of a problem right now.
As a workaround I do such includes in function body or in other headers.
I don't see easy fix for that and I'm not sure if it's worth fixing.
I've added issue to see what's your stance on this 😃

Hi!  Just a thought here, but it would take some refactoring:  You could run an external c pre-processor on the file.  In gcc, you use -E, and in msdev, it's /P (I think - I haven't done this in a while).  There may be a decent c preprocessor that you could build in.
As an aside:  How do you set your include paths?  I've been trying to figure this out for 2 days and I can't get includes to work - Thanks!  Love this thing!

As an aside: How do you set your include paths? I've been trying to figure this out for 2 days and I can't get includes to work

You need to use AddShaderSourceDirectoryMapping in module that loads in early enough LoadingPhase like PostConfigInit


Where are the model download links?

e.g. : RealESR_Gx4.onnx
Can you point me all models download links?

Hi my friend, here is the link

https://gofile.io/d/4Dpnls

extract theese file in AI-onnx directory :)

hello it seems that the link is broken

hello it seems that the link is broken

Hi @dybilisim, the link https://gofile.io/d/hIOmMc seems working.
The link is updated with each release, it is in the AI-onnx folder


[ecos 1459] Move all marketplace further reading readme sections to the manifest

What does this PR do?

Moves Further Reading Section to the new manifest.tile.resources field.
Motivation

https://datadoghq.atlassian.net/browse/ECOS-1452
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

This LGTM. FYI: I didn't check every link 😅
I'm guessing the validation failures are due to unrecognized resource types?

Overall looks good. Two groups of comments though:

it looks like validation is failing from some of the resource_type values being invalid?

Regarding these, the validations should pass once the cloud siem service gets deployed with the support for the new resource_types


error#1603

Cookbook version
[Version of the cookbook where you are encountering the issue]
Chef-client version
[Version of chef-client in your environment]
Platform Details
windows 2K12 STD R2,
Scenario:
[What you are trying to achieve and you can't?]
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]
Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
Actual Result:
[2017-05-16T00:07:21+00:00] FATAL: Mixlib::ShellOut::CommandTimeout: windows_package[Apache HTTP Server 2.2.25] (apache2-windows::default line 26) had an error: Mixlib::ShellOut::CommandTimeout: command timed out:
---- Begin output of msiexec /qn /i "c:\ge\corp\local-mode-cache\cache\package\httpd-2.2.25-win32-x86-openssl-0.9.8y.msi" /quiet /passive INSTALLDIR="C:/Apache2.2" ALLUSERS=1 {}SERVERDOMAIN=WIN-L3GD1NADBCG {}SERVERNAME=WIN-L3GD1NADBCG {}SERVERADMIN=admin@WIN-L3GD1NADBCG ----
STDOUT:
STDERR:
---- End output of msiexec /qn /i "c:\ge\corp\local-mode-cache\cache\package\httpd-2.2.25-win32-x86-openssl-0.9.8y.msi" /quiet /passive INSTALLDIR="C:/Apache2.2" ALLUSERS=1 {}SERVERDOMAIN=WIN-L3GD1NADBCG {}SERVERNAME=WIN-L3GD1NADBCG {}SERVERADMIN=admin@WIN-L3GD1NADBCG ----

HI,
Im running this cookbook on OS windows 2K12 STD R2, but its not running ok, and is sending me error 1603, I added the parameter "/passive"  on MSIEXEC install options, but didnt work either, is sending a timeout error, I already increased to 3600 (using "node.override" on default.rb).
So could please someone help on this?
timeout error (I changed the path to C:\apache2.2, as default on cookbk didnt work):
[2017-05-16T00:07:21+00:00] FATAL: Mixlib::ShellOut::CommandTimeout: windows_package[Apache HTTP Server 2.2.25] (apache2-windows::default line 26) had an error: Mixlib::ShellOut::CommandTimeout: command timed out:
---- Begin output of msiexec /qn /i "c:\ge\corp\local-mode-cache\cache\package\httpd-2.2.25-win32-x86-openssl-0.9.8y.msi"  /quiet /passive INSTALLDIR="C:/Apache2.2" ALLUSERS=1 {}SERVERDOMAIN=WIN-L3GD1NADBCG {}SERVERNAME=WIN-L3GD1NADBCG {}SERVERADMIN=admin@WIN-L3GD1NADBCG ----
STDOUT:
STDERR:
---- End output of msiexec /qn /i "c:\ge\corp\local-mode-cache\cache\package\httpd-2.2.25-win32-x86-openssl-0.9.8y.msi"  /quiet /passive INSTALLDIR="C:/Apache2.2" ALLUSERS=1 {}SERVERDOMAIN=WIN-L3GD1NADBCG {}SERVERNAME=WIN-L3GD1NADBCG {}SERVERADMIN=admin@WIN-L3GD1NADBCG ----
ProcessId: 2320
app_name: C:\Windows\system32/msiexec.EXE
command_line: msiexec /qn /i "c:\ge\corp\local-mode-cache\cache\package\httpd-2.2.25-win32-x86-openssl-0.9.8y.msi"  /quiet /passive INSTALLDIR="C:/Apache2.2" ALLUSERS=1 {}SERVERDOMAIN=WIN-L3GD1NADBCG {}SERVERNAME=WIN-L3GD1NADBCG {}SERVERADMIN=admin@WIN-L3GD1NADBCG
timeout: 600
chef-client.zip

What happens if you try to install by hand? We don't have enough details to understand what's going on here yet. What version of chef-client are you using? This should be visible in the first parts of the chef converge. What does the contents of your wrapper cookbook look like?

Thanks for your reply Jeniffer.!
Currently my AMI has installed the ver of CHEF 12.13.37, but I installed manually ver. 12.4 & 12.6 (per cookbk requirmtns), but the results were the same: “error #1603”.
My next action now, is try to download and unzip binaries from my “default.rb”, then work on configurations files (httpd.conf & server.xml) to apply specific configs.
About my coobook, currently Im installing also Java in same coobook, and this one, its installed and working ok, except “apache2-windows” one.
Im attaching the last output from chef, hope could be helpful.
Thanks & regards
HG
From: Jennifer Davis<EMAIL_ADDRESS>Sent: miércoles, 17 de mayo de 2017 07:14 p.m.
To: chef-cookbooks/apache2-windows<EMAIL_ADDRESS>Cc: Gonzalez, Hugo (GE, Corporate, consultant<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: EXT: Re: [chef-cookbooks/apache2-windows] error#1603 (#3)
What happens if you try to install by hand? We don't have enough details to understand what's going on here yet. What version of chef-client are you using? This should be visible in the first parts of the chef converge. What does the contents of your wrapper cookbook look like?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/chef-cookbooks/apache2-windows/issues/3#issuecomment-302265384, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbbmsfCwkGbtU0yaeGNVacS9fSziNHoGks5r6401gaJpZM4NeQ72.


Display syntax errors in quickfix window

Is there a way to configure vim-autoformat to display syntax errors detected by formatters?
For example, when I pipe a file with a syntax error into goimports, it returns exit code 2 after printing nothing to stdout and printing errors to stderr, e.g.
main.go:3:9: expected 'IDENT', found '{'
main.go:4:2: expected '(', found 'IDENT' x
main.go:6:2: expected declaration, found 'IDENT' blah

I'm using au BufWrite * :Autoformat, and I would find it helpful to have those errors displayed in the quickfix window (with setqflist) so that I can see and correct them immediately instead of only seeing them when I try to compile the code. Right now, vim-autoformat appears to silently hide the errors.
#182 looks like a similar request where the quickfix window was mentioned.
And thank you for vim-autoformat! It seems much more reliable than other formatting extensions I had been using, which had unfortunate tendencies to mess up my undo history or mangle the buffer if I made additional edits while the formatter was running.

The aim of a formatting tool is to do a best effort in formatting the code. To display syntax errors and other issues you should use a linter integration plugin instead, such as syntastic. That plugin probably already does what you want.

Thanks for the quick reply! I understand your rationale; at the same time, I'd rather not need to run goimports (or gofmt) twice or use a much-larger plugin like Syntastic. I hacked in rudimentary quickfix support at https://github.com/derat/vim-autoformat/commit/00bffa48048f9ebd9e3fd873d16ac7225689c813, in case anyone else finds it useful.


Force versions link to always go to dev versions file

Issue #, if available:
Description of changes:

Ensure versions link in website always links to dev documentation. This way it doesn't become outdated over time.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The updated version page will redirected user to 0.8.3 dev website, is it intended behavior to route users cross versions?

The updated version page will redirect user to 0.8.3 dev website, is it intended behavior to route users cross versions?

Yes, this is intended. Otherwise how would you go from an old doc page to seeing all the new versions? The alternative is removing versions from the page for dev and stable, so they don't reference incorrect versions on old pages.

I agree with Nick's observation that the existing versions page won't provide a link for users to navigate from an old version back to a new version because it only has version links for version that exist when the version was created. Permanently changing this link is an expedient way to fix this.
@Innixma - Is there a reason why you prefer changing the versions link to https://auto.gluon.ai/dev/versions.html instead of https://auto.gluon.ai/stable/versions.html? If the stable versions were updated correctly, which @tonyhoo addressed in https://github.com/autogluon/autogluon/pull/3552, I think pointing to stable would be a better long term solution.

@gidler Good point, yes if it is fixed as in #3552, then we can have it point to stable, which would be better.

Updated to stable


DNS resoluion for DNS services with targets in hostnetwork fails.

Rancher Versions: Cattle Build from alena/revfeb7
Steps to reproduce the problem:
Create 2 services in host network mode.
Create a dns service - WEB1 pointing to these 2 services.
Create a service in managed network which is  linked to this dns service.
From containers of this service , we are not able to resolve "WEB1".
root@ad3b5036e49b:/# dig WEB1 +short
;; Warning: Message parser reports malformed message packet.
root@ad3b5036e49b:/# ping WEB1
ping: unknown host WEB1

Following automated test case fails:
admin_client = <cattle.Client object at 0x7f4fed1f7990>
client = <cattle.Client object at 0x7f4fed733290>

   def test_dns_svc_managed_cosumed_service_hostnetwork(admin_client, client):

       port = "3118"

       service_scale = 1
       consumed_service_scale = 1

       env, service, consumed_service, consumed_service1, dns = \
           create_environment_with_dns_services(
               admin_client, client, service_scale, consumed_service_scale, port,
               isnetworkModeHost_svc=False, isnetworkModeHost_consumed_svc=True)

       validate_dns_service(
           admin_client, service, [consumed_service, consumed_service1], port,
>           dns.name)

tests/v2_validation/cattlevalidationtest/core/test_dns_services.py:848:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

admin_client = <cattle.Client object at 0x7f4fed1f7990>
service = {'createdTS':<PHONE_NUMBER>000, 'launchConfig': {'tty': False, 'networkMode': u'managed', 'vcpu': 1, 'kind': u'container'...02-07T23:34:05Z', 'scalePolicy': None, 'fqdn': None, 'createIndex': 1, 'instanceIds': [u'1i197'], 'selectorLink': None}
consumed_services = [{'createdTS':<PHONE_NUMBER>000, 'launchConfig': {'tty': False, 'networkMode': u'host', 'vcpu': 1, 'labels': {'io.rancher...2-07T23:34:07Z', 'scalePolicy': None, 'fqdn': None, 'createIndex': 1, 'instanceIds': [u'1i199'], 'selectorLink': None}]
exposed_port = '3118', dnsname = 'WEB1', exclude_instance = None
exclude_instance_purged = False, unmanaged_cons = None

   def validate_dns_service(admin_client, service, consumed_services,
                            exposed_port, dnsname, exclude_instance=None,
                            exclude_instance_purged=False, unmanaged_cons=None):
       time.sleep(sleep_interval)

       service_containers = get_service_container_list(admin_client, service)
       assert len(service_containers) == service.scale

       for con in service_containers:
           host = admin_client.by_id('host', con.hosts[0].id)
           containers = []
           expected_dns_list = []
           expected_link_response = []
           dns_response = []

           for consumed_service in consumed_services:
               cons = get_service_container_list(admin_client, consumed_service)
               if exclude_instance_purged:
                   assert len(cons) == consumed_service.scale - 1
               else:
                   if unmanaged_cons is not None \
                           and consumed_service.id in unmanaged_cons.keys():
                       unmanaged_con_list = unmanaged_cons[consumed_service.id]
                       if unmanaged_con_list is not None:
                           assert len(cons) == \
                               consumed_service.scale + \
                               len(unmanaged_con_list)
                       for con in unmanaged_con_list:
                           print "Checking for container : " + con.name
                           found = False
                           for consumed_con in cons:
                               if con.id == consumed_con.id:
                                   found = True
                                   break
                           assert found
                   else:
                       assert len(cons) == consumed_service.scale
               containers = containers + cons
           for con in containers:
               if (exclude_instance is not None) \
                       and (con.id == exclude_instance.id):
                   logger.info("Excluded from DNS and wget list:" + con.name)
               else:
                   if con.networkMode == "host":
                       con_host = admin_client.by_id('host', con.hosts[0].id)
                       expected_dns_list.append(con_host.ipAddresses()[0].address)
                       host_name = con_host.hostname
                       host_os = con_host.info["osInfo"]["operatingSystem"]
                       if host_os.startswith("Ubuntu"):
                           # If host name is fqdn , get only the hostname
                           index = host_name.find(".")
                           if index != -1:
                               host_name = host_name[0:index]
                       expected_link_response.append(host_name)
                   else:
                       expected_dns_list.append(con.primaryIpAddress)
                       expected_link_response.append(con.externalId[:12])

           logger.info("Expected dig response List" + str(expected_dns_list))
           logger.info("Expected wget response List" +
                       str(expected_link_response))

           # Validate port mapping
           ssh = paramiko.SSHClient()
           ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy())
           ssh.connect(host.ipAddresses()[0].address, username="root",
                       password="root", port=int(exposed_port))

           # Validate link containers
           cmd = "wget -O result.txt --timeout=20 --tries=1 http://" + dnsname + \
                 ":80/name.html;cat result.txt"
           logger.info(cmd)
           stdin, stdout, stderr = ssh.exec_command(cmd)

           response = stdout.readlines()
>           assert len(response) == 1
E           AssertionError

tests/v2_validation/cattlevalidationtest/core/common_fixtures.py:1373: AssertionError

Tested with  rancher-server version  - v1.5.0-alpha1 and rancher/metadata:v0.8.4.
Automated runs do not report this failure .


Error in service example?

Could it be that there is an error in the new example for calling the service?
VS signals an error and the template renders Unknown

Which home assistant version are you using?

Having the same issue and using the latest version available

It works on my machine if I put it into a yaml file (I didn't check the GUI). Maybe the VS syntax highlighter doesn't support this quite new feature yet.
Regarding the unknown state: In your example, the state will be only updated once per day, at 00:00.

it does not make a difference, I adjusted the trigger time with no success.

@nin9s Please share your configuration.

`template:

trigger:

platform: time
at: 15:02
action:
service: epex_spot.get_lowest_price_interval
data:
earliest_start: "09:00:00"
latest_end: "18:00:00"
duration:
hours: 1
response_variable: resp
sensor:
name: epex_lowest_intervall
device_class: timestamp
state: "{{ resp.start is defined and resp.start }}"
`

Again... I'm just a n00b at HASS.
But don't you always need quotation marks around the time so that the colon is not misinterpreted?
eg "15:02:00"

hi, please look also into the topic: https://github.com/mampfes/ha_epex_spot/discussions/50

Any updates?

Fixed for me


Question regarding datasource

Hello. So i have a few questions:

Is any other datasource supported other than druid, like hikaricp or others? As i have tested with hikari, dbcp and some others, but none worked other than druid. No errors was thrown, but it just didn't work as expected.
Is kafka supported yet with Seata?
Is Nacos mandatory? As i have been able to run it without nacos.
How to set the env variable SEATA_CONFIG_NAME to yml file, or is conf file only supported on docker.
Thanks

1.All DataSource should be supported.
2.They are two things.
3.Nope.We support many of configuration and discovery middleware
4.check this out:https://seata.io/zh-cn/docs/ops/deploy-by-helm.html


 Nov. 2018 um 21:35 Uhr schrieb Sajo8<EMAIL_ADDRESS>
lmao
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ForkMaps/cryptonote/pull/27#issuecomment-435052124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfdIMU2h8rltJxq6Hx-vfL5OdeKhBxIaks5uqwa5gaJpZM4YFxv9
.


Re-Scan WSL distros at launch

Summary of the new feature/enhancement
I think it could be useful to have Cascadia re-scan the WSL distros every time it launches, so that installing a new WSL distro will reflect on the profiles menu.
Proposed technical implementation details (optional)
It would just run CascadiaSettings::_AppendWslProfiles every time the app loads up, so it gets them all and adds any new profiles necessary,

Hey, weird enough, this’ll be fixed by #754. There’s a spec review in progress for that feature at #1258.


Not working with host key algorithm: ssh-ed25519

Test with the docker image: https://github.com/sgaunet/alpine-sshd
Example:

panic: Failed to dial: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

fixed in latest release (v0.1.0-beta-7)


Fix status API for null ban duration and user roles

Codecov Report

Merging #589 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             master    #589      +/-   ##
===========================================
- Coverage      5.90%   5.89%   -0.01%
  Complexity     2246    2246
===========================================
  Files           173     173
  Lines         11132   11138       +6
===========================================
  Hits            657     657
- Misses        10475   10481       +6

Impacted Files
Coverage Δ
Complexity Δ

includes/API/Actions/StatusAction.php
0.00% <0.00%> (ø)
2.00 <0.00> (ø)

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 275fdb4...7f9eadc. Read the comment docs.


Configure Jocko from the command line

Allow all the address binding to be configured

Allow a memberlist of serf nodes to bootstrap things

Add a quick start guide for getting a 3 node local cluster running

https://github.com/travisjeffery/jocko/compare/55577b7b2f5ff1819d885bdd5fea814b4aec6f74...3bf02b3a57e77cd85d1d26c599c0a48577c2bf3b
thanks!


Some enchantments

I noticed that Ethereal, Vortex, and Soulbound were removed. If I were to add them from an older version would they be able to work? If not, is there any way I can re-add them to CrazyEnchantments? Thanks again for the help!

All 3 of those enchantments never existed in this plugin. My guess is Ethereal and Vortex are renamed enchantments but I don't know what renamed enchantments those are.
Soulbound was never an enchantment in CE but was instead turned into an item called Protection Crystal by default but is still in CE.

So, Vortex is renamed. And I can't seem to find Ethereal. So I don't know where the other two came from. Thanks though. The only reason I asked is that on one of the older versions/other servers we have, they have these three enchantments that are in the enchantment.yml and all. That's all. Thanks~


branch: filters

For https://github.com/phetsims/scenery/issues/707 and associated cleanup

Merged to master and deleted, closing.

Should be re-deleted as part of phetsims/special-ops#198

Deleted, closing.


/usr/lib/libc.so.6: version `GLIBC_2.33' not found

Describe the bug
I build my application on one machine, then I have a friend who tries to launch the appimage on another machine using another glibc version. They get the following error:
./my-app: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by ./my-app)

To Reproduce
Steps to reproduce the behavior:

Build an appimage with one machine.
Try to launch the appimage on another machine. (With another version of glibc.)
See the error; the app does not launch.

Expected behavior
I expect the appimage to "just work", since as far as I know appimages should have static libraries and therefore launch on any machine.
Are there any solutions to this?
Platform and Versions (please complete the following information):
Operating System - Linux(5.11.4-zen1-1-zen) - linux/x64

Node.js environment
  Node.js - 15.11.0
  tauri.js - 0.14.1

Rust environment
  rustc - 1.50.0
  cargo - 1.50.0
  tauri-bundler - 0.9.4

Global packages
  NPM - 7.6.1
  yarn - 1.22.10

App directory structure
/.git
/dist
/src-tauri

App
  tauri.rs - 0.11.1
  mode - embedded-server
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: http: https: 'unsafe-eval' 'unsafe-inline'
  distDir - ../dist
  devPath - http://localhost:4000

If this happens with the dev branch, then please reopen this issue.
To use the dev branch, please view this page:
https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#development-guide
For more information, see: https://github.com/tauri-apps/tauri/issues/1253

It should not be closed, I got the same issue and found no solution here! It's not cross-platform at all!

Can you confirm this is still happening on Dev / beta @pansila ?

FYI - the reason it was closed is because of our policy not treating issues apparently related to the alpha (and webview/webview) version of Tauri.

Our research has shown that we might have to resort to "rust compiler tricks" because for whatever reason older versions of GCC are forwards compatible, but newer ones are not backwards compatible. I had hoped that things had "fixed themselves" recently, but will reopen to be on the safe side.

Can you confirm this is still happening on Dev / beta @pansila ?

I'm using<EMAIL_ADDRESS>

that is not latest. can you try cargo update ? we are on beta-rc.2 already

It's not GCC compatibility issue, but the glibc version mismatch on different machines. I'm now trying to build the tauri app targeting at x86_64_unknown_linux_musl, but openssl and glib-sys failed to build with musl. openssl issue could be circumvented with vendored feature (openssl = { version = "0.10.33", features = ["vendored"] }) while got no idea for glib-sys.

sorry, I meant glibc not gcc
https://redbeardlab.com/2019/05/07/rust-and-glibc-version/

I managed to use the Cross to build the tauri app. Just need to build a new docker image based on the Cross docker image rustembedded/cross:x86_64-unknown-linux-gnu to provide a complete build environment for tauri.
Dockerfile:
FROM rustembedded/cross:x86_64-unknown-linux-gnu

RUN apt-get update && apt-get install --assume-yes \
    libssl-dev libglib2.0-dev libcairo2-dev libpango1.0-dev \
    libatk1.0-dev libgdk-pixbuf2.0-dev libsoup2.4-dev \
    libgtk-3-dev libwebkit2gtk-4.0-dev

I also need to replace tauri-cli executables to use cross instead of cargo when building.
rust.rs
pub fn build_project(debug: bool) -> crate::Result<()> {
...
-  let status = Command::new("cargo").args(args).status()?;
+  let status = Command::new("cross").args(args).status()?;
...

awesome work and insight

But failed to run....
How can I compile a Rust program so it doesn't use __cxa_thread_atexit_impl?

Can you see if adding this to a src-tauri/.cargo/config file fixes the problem?
[target.x86_64-unknown-linux-gnu]
rustflags = ["-Ctarget-feature=+crt-static"]

But failed to run if target machines's glibc version is lower than GLIBC_2.18.

I get that, but at some point we just have to cut our losses and admit that if a user is not keeping fundamental libs up to date then there isn't much we can do about it - other than perhaps informing them to join the 21st century. :P

Jokes aside, 2.18 was released in 2013 - and only RHEL considers it still useful. Please compare:
https://sourceware.org/glibc/wiki/Release#Distribution_Branch_Mapping

Can you see if compiling with this env variable fixes the issue?
$ export RUSTFLAGS="-C target-feature=-crt-static"

Thanks, didn't work though.
...crt-static feature which is turned off by default (except for musl).

Hmm this is tricky. I also found out that statically linking glibc is highly discouraged. So if we want to share Tauri apps with older machines, we need to compile with an older glibc version too :/

I hit this issue trying to release to centos 7 having built on ubuntu. The workaround is to create a docker image for the environment you are releasing to, or use a tool like rust embedded cross build that does this automatically for you (I haven't used that tool yet).
so the trick is you also need to build tauri and build your app with that version (not the downloaded node package)
Here's the important steps at tleast for centos 7 (for example):
FROM centos:centos7.3.1611

RUN yum install -y \
  # notice I'm using an old version of webkit. It works!
  webkitgtk4-devel \
  openssl-devel \
  curl \
  wget \
  squashfs-tools \
  gcc \
  gcc-c++ \
  make \
  file \
  # for scp transfer of build
  openssh-clients \
  openssh && \
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash && \
. $HOME/.nvm/nvm.sh && \
nvm install node --latest-npm && \
nvm use node && \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y && \
. $HOME/.cargo/env && \
cargo --help && echo $(rustc --version) && \
# do not use downloaded packages of tauri - you must build it yourself in this environment for correct GLIBC version
cargo install tauri-cli --vers 1.0.0-beta.5 && \
cargo install tauri-macros --vers 0.0.0

# now instead you build your appimage like:
# cargo tauri build --debug --verbose

I hit this issue trying to release to centos 7 having built on ubuntu. The workaround is to create a docker image for the environment you are releasing to, or use a tool like rust embedded cross build that does this automatically for you (I haven't used that tool yet).
so the trick is you also need to build tauri and build your app with that version (not the downloaded node package)
Here's the important steps at tleast for centos 7 (for example):
FROM centos:centos7.3.1611

RUN yum install -y \
  # notice I'm using an old version of webkit. It works!
  webkitgtk4-devel \
  openssl-devel \
  curl \
  wget \
  squashfs-tools \
  gcc \
  gcc-c++ \
  make \
  file \
  # for scp transfer of build
  openssh-clients \
  openssh && \
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash && \
. $HOME/.nvm/nvm.sh && \
nvm install node --latest-npm && \
nvm use node && \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y && \
. $HOME/.cargo/env && \
cargo --help && echo $(rustc --version) && \
# do not use downloaded packages of tauri - you must build it yourself in this environment for correct GLIBC version
cargo install tauri-cli --vers 1.0.0-beta.5 && \
cargo install tauri-macros --vers 0.0.0

# now instead you build your appimage like:
# cargo tauri build --debug --verbose

Btw I've changed the CLI binary build CI to run on ubuntu-18.04 (that's the lowest available ubuntu on github actions :/) so maybe you won't need to build the CLI by yourself on the next release.

@lucasfernog thanks, and actually appimage has documented the best practice for this exact issue:

You should use a binary that has been compiled on an older system. Unfortunately, the complication is that distributions usually compile the latest versions of applications only on the latest systems, which means that you will have a hard time finding binaries of bleeding-edge software that runs on older systems. A way around this is to compile dependencies yourself on a not too recent base system, and/or to use LibcWrapGenerator or glibc_version_header or bingcc.

I'm still a bit confused by the best practice docs I linked. If I build my appimage on centos7 it does not run on ubuntu 18.04, probably because regardless of C/C++ runtime there's still a requirement to include some shared libraries, like libssl:

error while loading shared libraries: libssl.so.10

Yeah we still need to take care of copying shared libraries to the appimage.

had similar issue with lastpass-cli, compiled and ran fine on laptop using "ubuntu 21.04" but trying to execute that binary in an azure devops pipeline with hosted agent using "ubuntu 20.04" got error "GLIBC_2.33 not found", workaround was to build it in the pipeline

I'll close this since we fixed the AppImage issues and there's nothing we can do regarding the glibc version. This will be documented.

I hit this issue trying to release to centos 7 having built on ubuntu. The workaround is to create a docker image for the environment you are releasing to, or use a tool like rust embedded cross build that does this automatically for you (I haven't used that tool yet).
so the trick is you also need to build tauri and build your app with that version (not the downloaded node package)
Here's the important steps at tleast for centos 7 (for example):
FROM centos:centos7.3.1611

RUN yum install -y \
  # notice I'm using an old version of webkit. It works!
  webkitgtk4-devel \
  openssl-devel \
  curl \
  wget \
  squashfs-tools \
  gcc \
  gcc-c++ \
  make \
  file \
  # for scp transfer of build
  openssh-clients \
  openssh && \
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash && \
. $HOME/.nvm/nvm.sh && \
nvm install node --latest-npm && \
nvm use node && \
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y && \
. $HOME/.cargo/env && \
cargo --help && echo $(rustc --version) && \
# do not use downloaded packages of tauri - you must build it yourself in this environment for correct GLIBC version
cargo install tauri-cli --vers 1.0.0-beta.5 && \
cargo install tauri-macros --vers 0.0.0

# now instead you build your appimage like:
# cargo tauri build --debug --verbose

Is there an equivalent to this for (K)ubuntu?

@siauderman I'd recommend using github actions for this since it supports ubuntu 18.04 too and you could build for mac and windows at the same time. Alternatively we added support for cross quite some time which should make this pretty straight forward too.
If you still want to use the docker script you need to

Replace the first line with an ubuntu image
replace RUN yum install [...packages...] with the ubuntu instructions from our docs
update the tauri-cli version (or use the npm package since we build that on ubuntu 18.04 too so it should work)
remove the tauri-macros line

I have the same errors when using cross to build a tauri app a few days ago. And I found it is because the packaging phase did not running in the docker container. See https://github.com/tauri-apps/tauri/issues/4255.

I have successfully built and run a Tauri app on CentOS/RHEL 7.  I found the information in this thread helpful (https://github.com/tauri-apps/tauri/issues/1355#issuecomment-896434917 in particular) but incomplete.  I modified the Dockerfile provided above and add step-by-step instructions to build Tauri apps that will work on CentOS/RHEL 7 (glibc 2.17) and newer.
I've captured this at https://github.com/rfdonnelly/tauri-builders but I've also copied and pasted the relevant information below:
Dockerfile
# Adapted from: https://github.com/tauri-apps/tauri/issues/1355#issuecomment-896434917

FROM centos:centos7.9.2009

# Install dependencies
RUN \
    yum install -y \
        # notice I'm using an old version of webkit. It works!
        webkitgtk4-devel \
        openssl-devel \
        curl \
        wget \
        squashfs-tools \
        gcc \
        gcc-c++ \
        make \
        file \
        librsvg2-devel

# Install NVM
RUN \
    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash \
    && source $HOME/.nvm/nvm.sh \
    && nvm install 14 --latest-npm \
    && nvm use node

# Install Rust
RUN \
    curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y

# Install Tauri CLI
RUN \
    source $HOME/.cargo/env \
    # do not use downloaded packages of tauri - you must build it yourself in this environment for correct GLIBC version
    && cargo install tauri-cli --vers 1.0.4
    # NOTE: tauri-macros has nothing to install (no binaries) so this isn't needed
    # && cargo install tauri-macros --vers 1.0.4

ENV PATH=/root/.nvm/versions/node/v14.20.0/bin:$PATH
ENV PATH=/root/.cargo/bin:$PATH

# now instead you build your appimage like:
# cargo tauri build --debug --verbose

Instructions
Create a Tauri app
# Select the default for all prompts (just keeping pressing Enter)
npm create tauri-app

Install the dependencies
cd tauri-app
npm install

Modify the Tauri bundle identifier
# Edit src-tauri/tauri.conf.json and change the value of tauri.bundle.identifier to "test"
vim src-tauri/tauri.conf.json

Build the CentOS 7 Tauri build image
docker build -t tauri:centos7 .

Build the Tauri app
docker run -it --rm \
    -v $PWD:/src \
    -w /src \
    tauri:centos7 \
    /bin/bash -c "cargo tauri build --debug"

Run the Tauri app
src-tauri/target/debug/bundle/appimage/tauri-app_0.1.0_amd64.AppImage

Video
The following video shows a Tauri app being built in a CentOS 7 Docker container and being run on Ubuntu 22.10 under WSL 2.
https://user-images.githubusercontent.com/28975/181635416-17b5ada6-ee01-4862-8808-f74cde427110.mp4

In my case, running rustup default stable solved it (Ubuntu 20.04)

Has anybody figured this out for tauri-v2-beta yet?    I'm trying to get an appImage that will work on Centos Stream 9, but haven't found an OS that will build for me yet.
It appears we need an OS with GLIBC <= 2.34 (to support CentOS Stream 9) and a gnome glib >= 2.70 (which is what it appears that Tauri needs).
Am I just going to have to build gnome from source?

Just built on arch based system and tried to run the Appimage on debian.
failed missing GLIBC .
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38'

Not sure if this would be helpful, but I've encountered the same issue, and I used zig cc to link against an older glibc version. Though my repo is for cross compiling to arm64, you can just ignore the cc stuff(if compiling for the same arch), and change the config(.cargo/config.toml) accordingly. REPO
In short: you can(?) compile for older systems with a newer glibc on the host machine.


Authentication failure because of _csrf_token on rails app

Please complete all sections.
Configuration

Provider Gem: omniauth 2.0.4, omniauth_openid_connect, omniauth-linkedin-oauth2, omniauth-rails_csrf_protection
Ruby Version: 2.7.5
Framework: rails <IP_ADDRESS>
Platform: macOS

Expected Behavior
The request validation phase succeeds with the correct given csrf token from session and request
Actual Behavior
Users get an "OmniAuth::AuthenticityError, Forbidden" error in the request phase.
OmniAuth.config.request_validation_phase is using OmniAuth::AuthenticityTokenProtection which is looking for the default key :csrf in the session. Rails apps are using the key _csrf_token instead. So because the key is missing in the session a random one is generated, thus the csrf tokens from session and the request do not match.
Steps to Reproduce

Create a rails app with omniauth, omniauth-linkedin-oauth2
Configure linkedin oauth
Add a button in rails app for linkedin login
Click login and observe the logs

My Workaround
I'm not sure whether I'm just doing things wrong. But since omniauth-rails_csrf_protection is used in my case which is hooked into OmniAuth.config.before_request_phase and it is doing exactly the same thing as OmniAuth.config.request_validation_phase just using the correct key for rails. I've manually set OmniAuth.config.request_validation_phase = nil in an initializer. And it started to work fine 🤷♀
Is it supposed to work like that in rails?

ah ok that was my misstake. Thanks :)

I use omniauth-rails_csrf_protection gem, and csrf detected errors occurs not only development environment. Is there any way to skip check csrf? I'm using rails api.

@inska can you open a new issue w/ an example app that reproduces your issue?


bugfix: BLE + Mambo.disconnect()

Minidrone.py L724: raises exception since not hasattr(self, 'groundcam')

Why closed?  I hadn't had a chance to look at the issues you posted.  I wasn't going to change requirements (the cv2 issue) but really hadn't had a chance to look at the others.

I actually only wanted to submit the bugfix (634718c0c846f3c100a7664a250d63439322c3ba). I should have made a separate branch, oops.
The rest are intended for a thin ROS wrapper of pyparrot for controlling Mambo. Some of these needs to be ROS-compatible seem to go against your design principles and constraints (e.g. Python3 only, optional cv2), so I meant to have my wrapper target my fork of pyparrot.

Not going to accept this full set of changes as I don't want to make cv2 required, etc.  As you said, that belongs in your fork (which I am interested in seeing).  Unfortunately GitHub only allows an all-or-nothing accept, which means I can't take part of your changes.


Feature/#124 add relations to backend

Add Relations to backend
Description

The possibility of adding relationships between entities is added.
Motivation and Context

To offer similiar functions like other project builders and fully enable ER-modelling, relationhips are added to the entities.
How has this been tested?

Via Acceptance tests of the rest-interface.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. - will be done later

bitte erst den PR #123 mergen


Changelog?

I cannot find a changelog anywhere. Surely this would be helpful, especially when there are breaking changes (e.g. removed/modified classes) between versions?

Hey @benface! We haven't had any breaking changes yet, but everything is always documented on the releases page.
We'll add a real changelog to the docs eventually too.

@adamwathan Oh, I don't know how I missed that! Good to know, thank you. :)


 I guess this is why a lot of test cases in user-tests.js were commented out (https://github.com/nodejitsu/jitsu/blob/master/test/commands/users-test.js#L17).

Thanks! All merged in, with a fix in 519ab84 to move the new prompt property where it needs to be.  For future reference, any new prompt properties belong in lib/jitsu/properties.js - it helps keep the other code cleaner and smaller.


change of serial number and mac address

Good morning; on one of the previous versions we could put a mac address and a serial number of our sinology but since the last updates no longer possible, is there a method to change this? THANKS

thank you for your job !!

I still have a question, on CCTV, there are no camera licenses, I don't know how to do it, do you have a solution? THANKS


Updated the browser tests for the recent change to wagtail pages

The Blog, Newsroom and Activity Log were updated to Wagtail pages, which in turn updated the filter, post list, and pagination components. The tests started to fail due to the markup changes, this PR updates the hooks to search for the correct markup.
Changes

Updated the pagination, filter, and email signup shared objects for the latest atomic components
Updated Activity Log page objects to use shared objects
Updated the specs to silence tests that need a bit more refactoring later
Silenced the non-atomic components in Press Resources (this will be updated to Wagtail soonish)

Testing

gulp test:acceptance --sauce=false

Review

@KimberlyMunoz
@anselmbradford
@sebworks
@kurtw
@kave
@richaagarwal

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

timeout errrors, works otherwise 👍

👍  all pass

👍


S3Path.toUri() breaks on path with spaces

To reproduce:
S3Path p = (S3Path)Paths.get("s3://mybucket/dir with space/and\tspecial&chars");
p.toUri(); -> java.net.URISyntaxException: Illegal character in path at index  ...

I am providing a PR

Thanks.
Is the goal here to avoid the Path being URL encoded?


Implement update_user_pool_domain

Introduce the CognitoIDP's UpdateUserPoolDomain to update configuration
options of the associated domain to a Cognito IDP (e.g. ACM certificate).
This implements feature #2308

Coverage decreased (-0.06%) to 93.037% when pulling 81980850d4c140849af5ecd09001807434b5bacc on caguado:fix/2308 into 9acdc59aa4ec54e2b995a4793503513e0b0dc055 on spulec:master.

thank you!


Randomize Embedded Chunk File Offset

In the current implementation, the stEG chunk is embedded right before the IEND chunk. So, when inspecting the output file, it is easy to see the chunk. To make it a bit more difficult, we should try to embed the chunk somewhere in the middle of the file.

Implemented in 2822ba41b2842902d1e7ba3d172585d04b432743


Rename project for clarity - RSS3 is an existing standard

Aaron Swartz defined RSS3 20 years ago.
Spec: http://www.aaronsw.com/2002/rss30
Announcement: http://www.aaronsw.com/weblog/000574
Maybe you can be RSS4 instead?

I assumed that's the difference between web3.0 and web3, rss3.0 and rss3

This is my concern too. Should have been clarified in the first place.

@kevinmarks If I remember correctly, the official considered this point. That's why RSS3 is used instead of RSS3.0, which is like Web3.0

The rss3.io site itself reads rss3 'the feed in web3.0', making the OP's point, regardless of the mentioned 'consideration'

We would love to see an update of the RSS standard, but it has stopped updating for a long time and there is no way to continue the update of the RSS standard, but we also do not want to stop the search for free distribution of information, so we created a new protocol RSS3, RSS stands for a tribute to the history and 3 stands for Web3.
RSS has its version 2.0 3.0, and RSS3 will have its version 2.0 3.0, they are not related in any way.

We would love to see an update of the RSS standard, but it has stopped updating for a long time and there is no way to continue the update of the RSS standard, but we also do not want to stop the search for free distribution of information, so we created a new protocol RSS3, RSS stands for a tribute to the history and 3 stands for Web3.
RSS has its version 2.0 3.0, and RSS3 will have its version 2.0 3.0, they are not related in any way.

The lack of an update in RSS gave us Atom and it's extensible by design (being the basis of things like podcasts and ActivityStreams).


upgrade CW packages to v2

migration guide: https://github.com/CosmWasm/cosmwasm/blob/main/MIGRATING.md#15x---20x

blocked on https://github.com/CosmWasm/cw-nfts/pull/160

I'm looking into this, there's a bit of a dependency snag to resolve here -- cw-nfts actually depends on this repo, for the cw-paginate-storage package: https://github.com/public-awesome/cw-nfts/blob/v0.19.0/Cargo.toml#L28
I can't get the cw721 package to compile without updating or removing this dependency. There's only one place the package is used and it only relies on the paginate_map_values query defined here.
Since it's only called once and the implementation is hardly any longer than the function call, maybe the best solution is to inline it and stop relying on the package?

I'm looking into this, there's a bit of a dependency snag to resolve here -- cw-nfts actually depends on this repo, for the cw-paginate-storage package: https://github.com/public-awesome/cw-nfts/blob/v0.19.0/Cargo.toml#L28
I can't get the cw721 package to compile without updating or removing this dependency. There's only one place the package is used and it only relies on the paginate_map_values query defined here.
Since it's only called once and the implementation is hardly any longer than the function call, maybe the best solution is to inline it and stop relying on the package?

omg nooo, thank you for figuring this all out 🙏
i'm very down for that solution. it sounds best to me to depend on fewer packages if the reliance is so trivial.

Actually I see they're not even using it for pagination now that I look closer at the implementation, passing None for both bounds. So I'd say that's definitely the way to go, code is much more clear without the indirection anyways.


NRFeatureFlag_BackgroundReporting Not Working

I'm trying to use the new background reporting flag, but it doesn't appear to be working.
Description
I have set up the background modes, and have added my background task identifier. My background task is running as expected, I have verified this through remote logging. Still, no NewRelic data is coming through while the background task is running.
The following is at the top of my app delegate.
NewRelic.enableFeatures(NRMAFeatureFlags.NRFeatureFlag_BackgroundReporting)
NewRelic.setApplicationVersion(UIApplication.appVersion)
NewRelic.setApplicationBuild(UIApplication.buildNumber)
NewRelic.start(...)

Expected Behavior
NewRelic data should be flowing every time my background task runs. No events, networking data, etc., are making it through.
Relevant Logs / Console output
Your Environment
iOS 17.5.1
NewRelic SDK version 7.4.12

I'm even getting a success result from NewRelic.recordCustomEvent(...), but the events are not making it through

There was a bug in the iOS agent where if you foregrounded your app before the background harvest executed those events wouldn't get sent. That bug was fixed in a previous version of the agent. Please update to the newest iOS agent version


plugin(feedback): migration of feedback plugins to backstage/community-plugins workspace

Hey, I just made a Pull Request!
The feedback and feedback-backend plugins from the janus-idp/backstage-plugins repository was migrated to the community plugins, based on commit a8fe67c2. The migration was performed by following the manual migration steps outlined in the Community Plugins CONTRIBUTING guide
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

CI is now passing 🚀  cc: @BethGriggs for review


Add CoNLL 2023

I'm adding CoNLL 2023.
For the timezone, I'm supposing is Anywhere on Earth (which is customary in similar conferences), but I have also asked them via email, and if they answer differently then I'll send another PR to fix it.
Source of the h-index.

Thanks for contributing!

Just for the record, the timezone was confirmed by one of the organizers to me via email:

All deadlines are 11:59pm UTC-12h (anywhere on Earth).


Miscellaneous packaging improvements

Use pyproject.toml for packaging, instead of setup.{cfg,py}.
Replace usage of deprecated pkg_resources with importlib.metadata/importlib_metadata (Python 3.7 only).
Various housekeeping and clean-up of the CI workflows.
Use pytest-xdist to parallelize tests (n=2) on GHA runners; this shortens run time of individual jobs by up to 5 minutes.
Cherry-pick two commits (by @glatterf42 originally at #494) adjusting for pandas 2.0.0.

How to review
Read the diff and note that the CI checks all pass.
PR checklist

[x] Merge iiasa/ixmp#476, required to address an issue with the codecov dependency.
[x] Continuous integration checks all ✅
[x] ~Add or expand tests;~ coverage checks both ✅
~Add, expand, or update documentation.~ N/A
~Update release notes.~

@glatterf42 #683 led to conflicts in test_tutorials.py; please wait for me to rebase &  deconflict before reviewing.

Sorry, I didn't realise it would. I'll review once you are done.

NB the codecov/patch check failure occurs because a few lines are changed in .tools.add_year, but that code remains untested. The tests will be added by #494, from which those changes were cherry-picked.

Do we now have to remove those commits from #494 or does git recognize that we included them here already once we merge both?

Do we now have to remove those commits from #494 or does git recognize that we included them here already once we merge both?

Yes, they can be removed in a few steps:

Check out that branch.
git rebase -i HEAD~10 —replacing "10" with some number that goes back far enough to include those commits.
Edit the TODO list in the editor that is opened. Put "d" or "drop" on the start of the line for those commits that have been cherry-picked; leave the rest the same.
git rebase main; this will move the branch to the head of main, which already contains the cherry-picked commits.

Another way is to just do (1) and (4). During the rebase, git will complain, twice, that the cherry-picked commit "is (now) empty", because all changes they contained are already on main. It will prompt you to do git rebase --skip each time.

This is mostly just FYI: I've applied your suggestion to #494 and ran (1) and (4) after updating my local main. The process was slightly different for me, then: git immediately told me that it skipped the two previously applied commits. It still found two merge conflicts, however, which I had to resolve manually (both about the beginning of the definition of the interpolate_1d function). After that, I had to force push the branch because my initial updates to main were not yet included in the upstream branch.

In this PR I forgot to adjust this line in the "nightly" CI workflow:
https://github.com/iiasa/message_ix/blob/a824be9f5a641ec4c998485c886a77ff0f39ab91/.github/workflows/nightly.yaml#L47
…to refer to pyproject.toml, mirroring the change made to the "pytest" workflow. As a result the workflow fails, e.g. https://github.com/iiasa/message_ix/actions/runs/4728750039


Request from Telegram X

Thank you for your hard work, this is what I have been looking for. Hopefully in the future it can also work for Telegram X

Thank you for your support
After reviewing issues with Telegram X I have concluded that it stores session in completely other way then Telegram does.
Telegram X seem to store session in files/tdlib/td.binlog file, it should not be very hard, you can do that by reading it using NativeByteBuffer class and getting information from it using different methods from NativeBytesBuffer, but unfortunately I am not doing that now (maybe in future, but not now)

we need the Telegram X. please add this

Can support be added for Telegram X

Those who want the version for Telegram X, I have solution for you. Please dm me in telegram or discord, my nickname is: @lplpqq


How do I skip live streams when archiving a youtube channel?

What is the purpose of your issue?

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

How do I skip live streams when archiving a youtube channel? Is there an option to ignore streams which are live right now?

See #12946.


Rerunning build to see if failures related.

This is still a draft? Any progress?


VolleyNetworkStack : why RequestQueue requestQueue is static ?

If I have two services when creating the second one it will call again VolleyNetworkStack.newInstance which will call the constructor again and because requestQueue is static it will override the previous one.
So for exemple if in my first service i need to trust a specific certificate, i will not be able to connect to my web service anymore.
I think it should be something like this :
private RequestQueue requestQueue;

private VolleyNetworkStack(Context context, WaspHttpStack stack) {
    requestQueue = Volley.newRequestQueue(context, (HttpStack) stack.getHttpStack());
}

static VolleyNetworkStack newInstance(Context context, WaspHttpStack stack) {
    return new VolleyNetworkStack(context, stack);
}

RequestQueue getRequestQueue() {
    if (requestQueue == null) {
        throw new NullPointerException("Wasp.Builder must be called");
    }
    return requestQueue;
}

I think it would be great to have just one service and make it as much dynamic as possible. Probably we can consider adding the trusting certificate logic using annotations. What do you think?
When do you think having more than one service can make sense apart from this certificate example you pointed out?

I think there is no harm to make it non-static, that's totally valid and RequestQueue is not so expensive in the terms of cost. I'm also wondering why we added static there at the first place. Need to check though, but so far seems there is no advantage of having static.
But as @AlexBalo  said, we really want to stick just one interface to handle everything and make things easier. That's why we introduced annotation solutions to avoid having 2 different services. At least so far, we managed to not needing the second one.
Apart from that, with wasp, different endpoint can be added to specific request calls. If we provide a certificate for that as well, there will be no need to another service.
By looking the code, I think we also need to consider check the context and use the only applicationContext(), if the context comes from the activity, we would have a strong reference and prevent GC apparently.
And for the getting requestQueue, we should also consider synchronization.

Let say that i have 100 request to make, 50 on api A and 50 on api B, i should annotate 50 time the method for api B !
And for exemple for api if both api A and B need Authorization, how do you manage different RequestInterceptor per apis?
In my mind, as soon i have to connect to different apis i should have a different service.

@adrienleroy In the next release, we will remove the static declaration.

@adrienleroy yes, sure I agree with what you said. Logically makes more sense to have different services if you are connecting to different apis for example.

This is fixed, (v1.5)


RGI16: Mt Kenya misses one outline

This is a very picky comment as these glaciers are sooo small. This glacier I marked consists of two glaciers: Tyndall (the larger one) and Heim (the small part I marked). One glacier is missing: Northey. See Rostom & Hastenrath 2007: 10.3112/erdkunde.2007.03.05: https://www.erdkunde.uni-bonn.de/archive/2007/variations-of-mount-kenyas-glaciers-1993-2004
G037305E00152S

Thanks for the feedback @rainerprinz !

This is a very picky comment as these glaciers are sooo small.

All feedback is welcome. Whether we implement it or not is a different story ;-)
Is the outline available in GLIMS? See https://www.glims.org/maps/glims . If it is, then including it in RGI is no problem. If not, than someone needs to submit it to GLIMS so that it can be included in RGI.
In any case, we will leave this issue open until resolution.

I came across this issue while diligently avoiding some admin work earlier today, and managed to georeference the map from the paper referenced by @rainerprinz, as well as the earlier paper by the same authors with outlines from 1993:

From what I can tell from the maps, Diamond Glacier (labeled on both the 1993 and 2004 maps) is also missing from GLIMS, which only has outlines from 1993 (though not the date listed in the 1994 paper).

I don't know what to do with this information ;-) - are new outlines going to glims soon?

Mapping these little glaciers is delcate. High resoultion images are preconditioned. Sometimes there is too much snow cover, somtimes they are barley visible because of shadows. Diamond glacier still exists, only ~200 m² though. I was hesitating submitting the MtK inventory, as we just prepare a new one for all East African glaciers (Mt Kenya, Rwenzori and Kilimanjaro). Paper will be submitted soon.

@fmaussion - fair enough, I apparently forgot to add my question. I wasn't 100% sure about sending these to GLIMS, given that this is just digitized from maps created by someone else, and they should probably get the "credit"?
@rainerprinz  - do you already have versions of the 1993/2004 outlines, in addition to the updated East African inventory?

I don't have the full outlines for 1993/2004. I just have Lewis Glacier outlines. An inventory for MtK is available for 2016, but not submitted. We decided to submit the full East Africa inventory from 2021 in a few weeks. Is there a need to digitize Diamond Glacier for 1993/2004 for consistency?

No, no - I digitized all of the glaciers in the 1993 and 2004 maps, though there's a slight shift in the 1993 outline for Diamond Glacier due to what appears to be an error in the original maps.


Restored to orig-fs using SnapBack, fugu now says that it's already installed.

iPhone 11
iOS 14.5.1
I restored my rootfs using SnapBack since the fugu app got deleted. I was having some issues so I needed to restore the rootfs. Upon re-installing Fugu after this, I get "Fugu is already installed" after I click Jailbreak + untether, and unc0ver now says Unsupported again, so I'm basically stuck.

 I don't know if you are experience or not. Read carefully and double check your work.

Worst case scenario. Gotta update to latest.
Best case you will get Cydia back ￼


Internal Server Error 500

Investigate and fix the issue

@svasylenko How can this be tested?  Unaware of the actual issue.


[DeviantArt] Add support for recursive ripping

RipMe 1.4.16/8bfd15e largely works on DeviantArt.com ...

Ripping itself functions great so far with JPG, PNG pics and GIF animations in small galleries/folders (max 3 pages). Other things and larger sizes untested.
However, recursive gallery/folder ripping doesn't work, so essentially RipMe functions like fully functional ('fully functional' meaning it downloads everything it sees, unlike ...) JDownloader.

Can you give examples of what recursive ripping would look like?
Thanks for the positive feedback, but as a general comment about issues, please make the actionable issue clear in your issue title.

^ Recursive is simple: all folders visible on the current address are downloaded.
http://miss-symph-0x0.deviantart.com/gallery/ has 3 uploads in gallery root, which are downloaded just fine. But her folders are unmentioned without explicitly linking them, which given a big enough gallery is a big job (my gallery has over a dozen folders, for example, but no subfolders) without manually parsing the HTML.

@rautamiekka Thanks, makes sense.

I know versions well before DA made the big changes the recursive ripping worked perfectly.


FixFix duplicate normal workload group when upgrade 2.0->2.1.1->2.1.2

Proposed changes
when upgrade doris from 2.0->2.1.1->2.1.2, user may found duplicate normal workload group.

After alter normal group, id=11001 group changes.

run buildall


Text Leading and Width

Adjust text leading to be consistent throughout site.
Adjust text span shorten to be 60-80 characters wide

I have done this in examples in photoshop. I showed you all last Thursday (3-15-18) and have done more updates since then. It's saved on my computer!

@digijim leading is still wonky in places. mainly at end of paragraph body before start of next heading. can we fix that before we go live, please?


Add a Gitter chat badge to readme.md

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

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

closing because badge is already added in develop branch


[DRAFT] Add load balanced tor proxy to AWS terraform config

Description
This is more a basis for discussion than a serious proposal to merge. I'm happy to take suggestions, I am not a tor expert so there may be much that can be improved, eg using some other existing tor proxy setup, or not using one at all.
The goal is to obfuscate the origin IPs and keep them changing, and to create a simple way of creating a db1000n installation with proxy, in AWS. It's immediate benefit is that it seems to work, as far as I can tell.
Notes:

var.name is changed as NLBs don't support underscores in their names
the db1000n servers will need to be restarted if the NLB is recreated. Is it possible to change the db1000n proxy config without restarting?
there is a var.zones variable that allows you to configure the number of availability zones - defaults to 2. LBs require >1
the tor instances have a netcat-based healthcheck. There's probably a better way
the tor instances have a cron job that calls HUP on tor processes every min, to get a new IP
works with the newly defaulted arm instances

Fixes # n/a
Type of change
Please delete options that are not relevant.

[ x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
tests were carried out with the ireland variable file

[ x] Test A: apply/delete/apply - no problems with creating or deleting
[ x] Test B: 24hr soak test in eu workspace

Test Configuration

Release version: git hash 1df67b9 (make funlen a little happier)
Platform: default

Logs
docker logs <container> | grep Response
 [ Response rate ]  0.0%
 [ Response rate ]  9.1%
 [ Response rate ] 14.3%
 [ Response rate ] 27.5%
 [ Response rate ] 41.7%
 [ Response rate ] 42.9%
 [ Response rate ] 47.3%
 [ Response rate ] 42.1%
 [ Response rate ] 44.0%
 [ Response rate ] 46.8%
 [ Response rate ] 49.7%
 [ Response rate ] 49.6%
 [ Response rate ] 53.3%
 [ Response rate ] 52.8%
 [ Response rate ] 53.1%
 [ Response rate ] 51.8%
 [ Response rate ] 56.0%
 [ Response rate ] 54.0%
 [ Response rate ] 54.3%
 [ Response rate ] 51.8%
 [ Response rate ] 52.9%
 [ Response rate ] 51.3%
 [ Response rate ] 51.9%
 [ Response rate ] 54.7%
 [ Response rate ] 53.6%
 [ Response rate ] 53.7%
...

Screenshots

Looks pretty good to me, someone recently told me that they had issues with tor proxy, can you confirm that it works for you? I was going to start looking into possible causes tomorrow but knowing that it works for you would allow to assume that the problem is in the configuration rather than in code and save some time

the db1000n servers will need to be restarted if the NLB is recreated. Is it possible to change the db1000n proxy config without restarting?

It is possible but would require some changes to the default config (or use of a custom one) - basically you'd want to embed each job that uses a proxy into an infinite loop job (hope I didn't forget to add it) and make an internal one to only perform a fixed number of requests - it would then end the job but the outer loop would start it again reevaluating the proxylist template (potentially need to add some additional templates depending on how exactly you plan to pass this proxy to a program). Although I thought that tor changes the circuit without the need to recreate the proxy, am I missing something here?

@Arriven thanks for the prompt reply. Tor seems to be working well for me both locally and in AWS.
The NLB would only get recreated when something significant changes like changing the number of availability zones you load balance across, or a decision to change something else fundamental. I don't think it's necessary to change things in db1000n - there must be many other higher priorities!
One thing I'm not sure of is how many existing AWS db1000n terraformers would welcome this change... I don't want to mess with anybody's existing/working setup.

@Arriven - kudos for a bloody amazing tool by the way :-D

I'll try to find where that issue was mentioned
As for disrupting current workflows for people: there's always an option to have both old and new config in two different folders although I'd prefer having some switches to enable/disable tor NLB within a single terraform deployment

I'd prefer having some switches to enable/disable tor NLB within a single terraform deployment

I did think about that. Leave it with me

I have checked in a module-ised version of the tor proxy, and I have set the defaults to no-proxy.
Incidentally - I am seeing errors in my tor proxy I didn't see yesterday:

Mar 25 12:46:05 ip-10-0-0-136 Tor[1359]: We tried for 15 seconds to connect to '[scrubbed]' using exit $ at x.x.x.x. Retrying on a new circuit.

I am wondering if there is some clever auto-blacklisting going on at the other end, or some of the tor relays are off or disabled in some way - hopefully the network will notice and remove them from the pool.
I am honestly not sure how to tell how well this is working beyond tailing the Response rate in the logs. One difference between the Response rate on a proxy and a non-proxy build is that on the proxy builds the Response rate rises comparatively slowly before stabilising. My current response rate is in the high 60%s

@SemiConscious I've done some testing with tor as well (except I've build the tor service directly into the docker image). Unfortunately, I observe a significant reduction in the number of accepted sessions. The tor service log shows the same output as yours, constantly changing exits with little success. Have you looked at the generated traffic stats in comparison to going through a VPN or directly? I'm afraid the response rate as it stands right now is not an adequate measure of attack success. You can stay at 60% forever if your traffic is not accepted at all (which is what I observe with multiple targets).

I agree - it's not a complete solution, and it was particularly bad on
Friday - I have 5 proxy instances which were running at 100% CPU capacity
and a very poor network throughput. It seems VERY config-dependent. I
noticed on friday that there was a lot of targeting of non port 80/443
sockets, eg 5060 (sip) and Tor doesn't support UDP, so Tor spends a lot of
time trying to resolve unresolvable failures. Here's how my cluster is
currently looking, which is a bit better:
[image: image.png]
I get, obviously, much higher performance if I run without the proxy ...
but my assumption so far is that this is misleading as the attack will
almost certainly be rejected by the target as it's from an unsafe country.
The consequence of that, I thought (maybe), was that fewer higher quality
results, even a lot fewer, might result in more damage at the other end.
What's your view on that? We need to keep the servers at the other end
working, hold open connections ... just hammering away with known-bad IPs
won't be doing much IMHO.
One other thing - frustratingly and idiotically I left a key config line
for tor out of the pull request. You need to add this line
echo "ExitNodes {ru},{pl},{by},{md},{cz} StrictNodes 1" >> /etc/tor/torrc
My next revision will include a way to set this as a variable. but it may
be moot if it turns out that Tor is not the right solution for db1000n.
I am actually working right now on an OpenVPN version, I'm looking at
Windscribe initially as a provider (it will probably need a pro account) -
I'll do a pull request on that when I get it working properly and I'd
appreciate your feedback on how it compares.
By the way I have been trying to see if I could utilise AWS edge data
centers somehow as the IP origin for the attacks (using Global
Accelerator), but I cannot at the moment see how to route outbound traffic
through edge locations - it can only be set up to allow inbound traffic.
There might be another way to do that that I am not aware of and I will
keep looking - making use of edge locations in Bulgaria or Serbia might
mean unblocked traffic without a proxy, so it would be a nice win! Though
you'd need to keep recycling IP addresses :P
On Sun, 27 Mar 2022 at 13:08, jdoe7865623 @.***> wrote:

@SemiConscious https://github.com/SemiConscious I've done some testing
with tor as well (except I've build the tor service directly into the
docker image). Unfortunately, I observe a significant reduction in the
number of accepted sessions. The tor service log shows the same output as
yours, constantly changing exits with little success. Have you looked at
the generated traffic stats in comparison to going through a VPN or
directly? I'm afraid the response rate as it stands right now is not an
adequate measure of attack success. You can stay at 60% forever if your
traffic is not accepted at all (which is what I observe with multiple
targets).
—
Reply to this email directly, view it on GitHub
https://github.com/Arriven/db1000n/pull/406#issuecomment-1079917112, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANMOPX6LOOUF72FAOVCOQ3VCBMVTANCNFSM5RRBBPHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

By the way - I did consider putting Tor into the db1000n container. It
would work great for those not running in the cloud. But for the cloud, I
felt that it was likely that the resource needs of the proxy wouldn't scale
with the resource needs of db1000n and my plan eventually is to use
autoscaling to grow (whatever) proxy containers we end up using, and that
if proxies are resource hungry we could just scale them out to get the
throughput we want. The downside of course is that load balancers aren't
free. But nor is freedom!
We could code it not to require load balancers but we'd need lambdas which
fire on instance creation and destruction, and restart the app containers,
or we could use service discovery via Route53 which again costs, and I am
not sure how db1000n treats proxy DNS names internally - if it resolves
once at startup then we'd need to restart the app containers again when
proxies are added/removed which is not ideal. That's FYI why I put a load
balancer in - there will only be 2 ip addresses, one for each availability
zone.
On Sun, 27 Mar 2022 at 13:08, jdoe7865623 @.***> wrote:

@SemiConscious https://github.com/SemiConscious I've done some testing
with tor as well (except I've build the tor service directly into the
docker image). Unfortunately, I observe a significant reduction in the
number of accepted sessions. The tor service log shows the same output as
yours, constantly changing exits with little success. Have you looked at
the generated traffic stats in comparison to going through a VPN or
directly? I'm afraid the response rate as it stands right now is not an
adequate measure of attack success. You can stay at 60% forever if your
traffic is not accepted at all (which is what I observe with multiple
targets).
—
Reply to this email directly, view it on GitHub
https://github.com/Arriven/db1000n/pull/406#issuecomment-1079917112, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANMOPX6LOOUF72FAOVCOQ3VCBMVTANCNFSM5RRBBPHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Arriven @jdoe7865623 I have tried a lot of different things today. My main aim was to develop an openvpn solution to replace tor, which I have checked in, though it looks as if I'll need a new pull request.
The headline result is that it doesn't seem to make much difference, though with a 'pro' windscribe account using IP addresses in St Petersburg I'm not seeing any errors from openvpn. openvpn is running as a container alongside db1000n, and the db1000n container uses the openvpn as a proxy using the docker `-network=container:xxx' switch. So no load balancer and db1000n runs without a -proxy setting.
Running without the proxy, however, did make a difference, in the sense that connections cycled more quickly, and there was a LOT more incoming data to the application, like an order of magnitude. But IMHO this supports my theory that the setup with the proxy (tor or openvpn) is actually doing more damage to the target than not using the proxy, even though the performance appears better without the proxy. Here's output for ss -s, with the proxy:

and without:

My interpretation of this data is that we are holding many more connections open when using the proxy than when we are not, thus doing more damage. But ... maybe that's wishful thinking, and maybe it's just as good to make many more connections even if they are trivially rejected at the other end due to IP geolocation. I honestly don't know ... but my gut feel is that firewall connections and application sockets are a more valuable resource than network bandwidth.
Question: how should we be measuring how well we are doing?
Question: how to increase the number of concurrent connections db1000n is making?


Export Identifers [was "LSID"]

We are starting to add LSIDs to people, taxa and sources.
Is it possible to have a filed LSID in the export facilities?

You can presently download all identifiers in your project via the Data Card -> Identifier -> Download.  This doesn't include Source and People identifiers however.
We'll have to figure out where to implement these. If you just want the above unified with Source and People then we'll make a single unified CSV table.  IDentifiers are stored as "polymorphic", so they are all in a single table.
As a side note you should, perhaps, focus on ORCIDs for People as the preferred identifier and DOIs for Sources.  These will have much more impact in linking/integrating your data with the bigger picture. than LSIDs.
TaxonNames - who knows what is preferred, OTUs- again, highly unclear.

Thanks, Matt:
(1) usually dead people don't have ORCID, and LSID seems to be a decent alternative -- and they don't have to be mutually exclusive.
(2) Most older papers don't have DOI, but again LSID seems to be stepping up to fill this blank.
(3) For taxon names -- who knows? But again I would choose LSID to have all with the same standard.
And... I have plans to integrate my Opiliones project with my OmniPaper site which contains lots of biographies and bibliography -- once having a database with the relevant data it won't be difficult.

Note to self, close with /api/v1/identifiers.csv.


Add folders

As requested by #5
An example has been given in the readme. Let me know if you have any questions or suggestions.

@Quminouse, thanks for the PR.
I am not fully convinced by the idea of folders here. Don't you think that a folder here can be just an alias and then we can support a table or string for that alias?
Let me know your views.


List component subtitle color flexibility

Partially resolves https://github.com/Shopify/pos-next-react-native/issues/27744
Background
PFR was updated to allow a backwards-compatible way of changing colors of subtitles of a List.
Solution
This PR enables that on the POS UI extension side by changing the interfaces.
🎩
I do not know how this can be tophatted without future PRs.

Could you please update the ListRow docs in the pos-extensions/1.5.0 branch to reflect these changes as well?

Could you please update the ListRow docs in the pos-extensions/1.5.0 branch to reflect these changes as well?

Sure thing


Humble manifesto update proposal

Use an optimistic and visual wording approach to evoke positivity 👍🏽 ?

@0xjgv can you give some background on why this specific wording improves the manifesto?

To be completely honest I feel your wording tends more towards "fancy"/"fluffy" marketing-style language, rather than just simple and clear, which is the tone I was going for in the manifesto, mimicking the very simple language used in https://agilemanifesto.org/
Maybe the wording reminds me of the very verbose and fluffy output of AI 😅


Ensure usage of metadata when storing data is consistent

What is your issue?
Ensure that the interface for the interpretation of metadata is consistent across all data types.
From discussion on 19/07/2023
Principles:

Each data type has it's own set of metadata keys

Any metadata keys which do overlap between data types should be consistent (e.g. treated in the same way - specific type, specific format etc.)

Some metadata keys always needs to be specified / inferred when creating a specific Datasource
Additional, optional metadata keys can also be specified

Can be explictly defined (e.g. within the function call such as "database", "database_version" for Emissions class and standardise_emissions function)
Can be included as freeform additional keyword arguments (kwargs)

When adding data, a datasource lookup should involve required keys + any optional keys specified

Potential setup and update steps:

Ensure optional keyword inputs are used in the same way for all data types

combine required and optional keys when performing the datasource lookup
this could be moved onto the store base class (e.g. BaseStore.datasource_lookup) rather then defined within each individual read_file method.

Add and use kwargs for all standardise functions? Link to optional keyword inputs:

add to standardise(..., **kwargs) functions
add to ...read_file(..., **kwargs) methods on store classes
interpret kwargs as (additional) optional metadata keywords

Add configuration file (to allow customisation)?

Discussion from issue #683:

Okay, so:
data and metadata are read from files (e.g. by _read_data in _gcwerks.py)
assign_attributes parses some of this metadata and passes it to get_attributes
get_attributes modifies the data (Dataset) using some of the arguments passed from assign_attributes (and adding stuff without reference to the arguments passed by assign_attributes?)
assign_attributes gets the modified data back from get_attributes then passes the original metadata passed to assign_attributes and the attributes of the modified data to sync_surface_metadata
sync_surface_metadata compares the values in the metadata and attributes for common keys, and might update them or ignore mismatches depending on the value of overwrite_mismatch, which you can specify in standardise_surface
standardise_surface calls the parser function (e.g. parse_gcwerks) which returns the "aligned" metadata that matches the attributes of the data returned from the parser
the metadata returned from the parser is added to the metastore
Also around steps 3 and 4, the changes made to the metadata are to ensure compliance with CF standards.
It would be nice to simplify this, but that should probably be another issue. Is it written this way because there can be some keys that are in the metastore that shouldn't be in the attributes, and some keys that are in the attributes of the input data that shouldn't be in the metastore? (e.g. optional search keywords in the metastore and extra info attached to the input data)
It seems like it ought to be possible to
collect, clean, combine, and make compliant all metadata (e.g. from user input and input files)
set the attributes of the data file based on this combined metadata
set the metadata for the metastore based on this combined
The current process does this, but parts are intertwined. I guess optional or "unexpected" metadata might be problematic, but we can track its source, and e.g. if it was in the input data, add it to the attributes in step 2.

A question that's come up (for me) which working on issue #683 is: how can we make it so that in the future, if we wish to distinguish data by a key, we can do so without adding it to required keys and then re-standardising data?

From discussion yesterday, this was the code I sketched out for creating the metadata in a standardised way. At the moment this was specific to surface but doesn't have to be if we made metadata_needed into a required input (metadata_default_keys() is specific to surface at the moment). This was within the "openghg/standardise/meta/_metadata.py" file
def create_surface_metadata(user_inputs: Dict[str, Any],
                            stored_data: Dict[str, Any],
                            attributes: Dict[str, Any],
                            metadata_needed: List = metadata_default_keys(),
                            allow_missing: bool = False,
                            ) -> Dict[str, Any]:
    """
    """

    attribute_sources = [user_inputs, stored_data, attributes]

    metadata = {}
    missing_metadata = []
    # Search parameter sources (in order) and populate metadata
    for param in metadata_needed:
        for source in attribute_sources:
            if param in source:
                metadata[param] = source[param]
                break
        else:
            if allow_missing:
                logger.warning(f"Unable to add '{param}' key to metadata")
            else:
                missing_metadata.append(param)

    if missing_metadata:
        raise ValueError(
            "Cannot extract or infer the following parameters needed for metadata from user inputs, stored data or attributes:\n"
            f" - {', '.join(missing_metadata)}"
        )

    return metadata

Like search versus search_surface etc. we could also have a create_metadata generic function and a set of create_surface_metadata, ... functions which call create_metadata under the hood.

If I'm taking the lead on this, my plan is to make an abstract base class with functions for the various steps involved in standardised data. The common elements of the process will be in this class, and then for each data type, we can add to or override the base methods. Ideally it would work out so that in the child classes, you should just see that parts that are specific to that class. (ABC might not be the only option... I'll see what other options there are for a uniform interface.)
Also I think methods in the base class whose main purpose is adding data to the object store could be split out into their own class or module. In theory, we should be able to take any metadata and data pair and add that to the object store. (Of course, we don't necessarily want to add arbitrary data, but the functionality should be separate from processing data and metadata.)

Thanks for taking the lead on this Brendan. This sounds like a great plan and something useful to discuss at the architecture meeting.
Would you mind opening a separate issue for this (and move over the details posted above to that issue)? I think it'd be more clear if we keep this issue about metadata / attribute differences and definitions and we can start a new issue around simplification of the base and data type classes as you described. (I don't believe we have a pre-existing issue for this but feel free to check).


Run CI on Julia nightly

Codecov Report

Merging #822 (8b0e082) into dev (856928c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #822   +/-   ##
=======================================
  Coverage   85.77%   85.77%
=======================================
  Files          37       37
  Lines        3516     3516
=======================================
  Hits         3016     3016
  Misses        500      500

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@DilumAluthge Can this be closed now?

Actually, we should merge this, so that we can detect if tests start failing on Julia nightly again.

I guess this sounds silly, but I don't like all those red crosses I get after my commits when nightly fails, which it frequently does. That's why I disabled nightly. Is there a workaround?

Yeah, it is unfortunate that sometimes Julia nightly is failing. The problem is that if we don't test on Julia nightly, we don't catch bugs like https://github.com/JuliaLang/julia/issues/46405 until after a new version of Julia has been released.


fix: spritesheet chrome bug

Description
Music year: 1973

List of changes

Issue(s)
https://oaknationalacademy.slack.com/archives/C05QD9NE0P8/p1718186425945029
How to test

Go to https://deploy-preview-2501--oak-web-application.netlify.thenational.academy
You should see SVGs rendering us per usual

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

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


OKD support for GCP provider

We would like to keep this master issue to link new issues which are related to GCP deployment so we can keep track as well as letting community know if a specific provider deployment is supported or has known issues etc

Depends on https://github.com/coreos/fedora-coreos-tracker/issues/147 mostly

coreos/fedora-coreos-tracker#147  is now completed and closed; fcos images are now available in GCP, documentation here: https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-gcp/

GCP support is available in Beta 4 at least, closing


Sometimes a a transaction error occurs - Cannot call send in state COMMITTING_TRANSACTION

While running and publishing messages back to Kafka (pollAndProduce), sometimes a transaction error occurs in the log:
java.lang.IllegalStateException: Cannot call send in state COMMITTING_TRANSACTION
This is due to some error in the way transaction state is managed / monitored by the system.
Also, as reported by a user:

It doesn’t get stuck on Cannot call send in state COMMITTING_TRANSACTION, it just re-processes.
However, sometimes I get Invalid transition attempted from state READY to state COMMITTING_TRANSACTION on startup and then an infinite loop occurs. I’ve only seen this happening when I set max.poll.records very low.

I've contributed a small test-case that reproduces some of the issues we discussed on slack: https://github.com/JorgenRingen/parallel-consumer/blob/bug25/parallel-consumer-examples/parallel-consumer-example-core/src/test/java/io/confluent/parallelconsumer/examples/core/Bug25AppTest.java
By tweaking the parallel-consumer and kafka-consumer settings I can reproduce Invalid transition attempted from state READY to state COMMITTING_TRANSACTION. Should happen on maxPolledRecords .
Also reproduced messagesProcessed > messagesProduced and Cannot call send in state COMMITTING_TRANSACTION (as the test is now).

Afternoon @JorgenRingen, I believe I have fixed the issue with transactions / commit state, and now made transactions optional as well: https://github.com/confluentinc/parallel-consumer/pull/31/files
Take a look at the interface and let me know what you think - specifically this choice: https://github.com/confluentinc/parallel-consumer/pull/31/files#diff-12c3d1f966a5367ab47be49f7c0f11a9dcd4cf339b73acb092b8c44ae9c9a6e2R45

Evening @astubbs, great with optional transactions. Adding the parameter and verifying by IllegalArugmentException'ing seems like a pragmatic and fair approach to me. However, if introducing support for optional producer, the parameter might be a little confusing. Don't have any immediate ideas on how to improve. Maybe some "fluent style" perhaps (which might be totally overkill) like ParallelConsumerOptions.with[outProducer|NonTransactionProducer|TransactionalProducer]().numberOfThreads(...).maxConcurrency(...)
I actually found a bug in the test:
https://github.com/confluentinc/parallel-consumer/pull/31/files#diff-d6d31b42ae96a5e31f2793c52624720af3a084c434707a9f031969a7af1b4e14R96 <- this line would always override maxPollRecords instrumented by the tests.
I deleted the line, added a couple of more tests and better verification and error-messages.
In my branch the following tests now fail fairly consistently:

io.confluent.parallelconsumer.examples.core.Bug25AppTest#testTransactionalLowMaxPoll (1) (infinite loop on every run)
io.confluent.parallelconsumer.examples.core.Bug25AppTest#testTransactionalDefaultMaxPoll (500) (infinite loop about ~50% of the times)

Typically infinite loops occurs when processed - produced=16 (16 = default number of threads)
All non-tx tests works and tx works when running with maxPollRecords=10000.
Checkout updated test:
https://github.com/JorgenRingen/parallel-consumer/commit/be57d9252d247a72f411a54767e1df75e3298d8f


Deploy a service for the Node Problem Detector component

How to categorize this PR?

/area monitoring
/kind enhancement
What this PR does / why we need it:
Deploy a service for the Node Problem Detector component to facilitate scraping the kube-system/node-problem-detector daemonset's endpoints by a Prometheus that is managed by shoot owners.
Which issue(s) this PR fixes:
Fixes #9481
Special notes for your reviewer:
cc @rickardsjp
Release note:

A service is added for the shoot cluster's kube-system/node-problem-detector daemonset

/approve

/test pull-gardener-e2e-kind-ha-single-zone-upgrade


add tb210.toml to testnet-15

Description
add tb210.toml to testnet-15.
Hello from Sweden. I am very excited to join Namada Network. I am software developer with passionate in Web3, have been running cosmos-based nodes, polkadot-based nodes, eth as well as move-based nodes.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

This validator was not recognised as a previous validator and has update in the title. Please read the description.


Failing to get CPU clock speed when running on ARM (raspberry pi)

Steps to reproduce

Run mix test on a raspberry pi running raspbian

Expected output

test .cpu_speed returns the speed of the current cpu passes

Actual output
$ mix test
Compiling 2 files (.ex)
warning: Enum.filter_map/3 is deprecated, use Enum.filter/2 + Enum.map/2 or for comprehensions
  test/benchee/benchmark/runner_test.exs:26

............................................................................................................................................................

  1) test .cpu_speed returns the speed of the current cpu (Benchee.SystemTest)
     test/benchee/system_test.exs:32
     Assertion with =~ failed
     code:  assert Benchee.System.cpu_speed() =~ ~r"\\d+.*hz"i
     left:  "ARMv7 Processor rev 5 (v7l)"
     right: ~r/\d+.*hz/i
     stacktrace:
       test/benchee/system_test.exs:33: (test)

....................................

Finished in 6.2 seconds
193 tests, 1 failure

I'm actually thinking that maybe that test doesn't have as much value as we might think. In that test we're making an assumption about the systems that everyone will be running these tests on (and in CI as well, which has already been proven an issue), and they seem to be causing more trouble then I think they're worth.
Maybe the answer here is just to get rid of that test and test this function in some other way? I have an open PR (#106) addressing this kind of thing.

Positive on what @devonestes said! :) When I manage to look at #106 but I'm pretty sure that we're better off with that


Add web support. Address small nitpicks and formatting changes. Incre…

Hi,
This looks like an interesting project, congrats :-)
I added web support to the package by using the universal_io plugin, which abstracts away the Platform and the HTTP client classes because normally they cannot be used on web.
I also did some small formatting, extracting out a constant and incrementing the package version.
I made a new app on the aptabase website and it seems to be working fine.
Let me know what you think, thanks!

And we could also change the README.md to mention web is supported 🚀

Just pushed new changes after review. I think it's fine, let me know if there's anything else that should be addressed here.

It's perfect, thank you 🎉


Add Finance and Fintech section, along with CoincapMCP

Add Finance and Fintech section, along with CoincapMCP

Added here and also added to https://glama.ai/mcp/servers


Add clarification about scheduling of vulnerability scanning; once at push? or periodically?

This document states "When a new image is pushed, Security Center scans the image...". So I assume vulnerability scanning only occurs once, at push time. Or is there a mechanism where scanning is scheduled periodically? If so how do I know when the image was last scanned? Can I control the schedule? The doc should clearly describe the scheduling capabilities.

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

ID: ad7c05f1-f69c-c033-0409-39f5c8f03674
Version Independent ID: ebcceb7b-0d9c-618c-9576-b3b1713fe1ef
Content: Container Security in Azure Security Center
Content Source: articles/security-center/container-security.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@rogersass
Thanks for your feedback! We will investigate and update as appropriate.

@YuriDio can you confirm?

Currently scans are only triggered by a push event to the ACR registry.
For now, to implement scheduling, customers need to re-push images to the registry.
We are currently working to expand that and add continuous scans, but do not have a concrete ETA to share just yet.
Hope this helps!

We will proceed to close this thread but if you have further questions feel free to create a new issue.

Thanks for the follow-up and clarification!


Copy deep url to clipboard

Current implementation does not actually copy text to clipboard when the copy button is pressed.

@SoIidarity is this fixed?