Geodata: Enable geographic search

All biosamples and publications are tagged with a geographic location object, where the geojson object is indexed as a geospatial index in the backend MongoDB collection. This allowas e.g. for $geonear queries, showing all samples from a geographic region.
		"geo" : {
			"label" : "Antalya, Turkey",
			"precision" : "city",
			"city" : "Antalya",
			"country" : "Turkey",
			"latitude" : 36.91,
			"longitude" : 30.7,
			"geojson" : {
				"type" : "Point",
				"coordinates" : [
					30.7,
					36.91
				]
			},
			"ISO-3166-alpha3" : "TUR"
		}

Also, we provide a service for accessing locations by the city name:

https://progenetix.org/services/geolocations?city=Zurich

... which e.g. can be used to autofill parameters.
To implement

geographic query (Samples, Publications) which sends geolatitude, geolongitude, geodistance as query parameters
lat & long should be derived from a selected city; geodistance is an integer (radius around point in meters => probably km in form * 1000

Closing since implemented; improvements/fixes will be addressed separately.


chore(main): release 1.3.1

:robot: I have created a release beep boop
1.3.1 (2024-09-27)
Miscellaneous Chores

release 1.3.1 (cef3090)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.3.1
:sunflower:


Calling hooks in a fn without #[hook] has terrible diagnostics

Problem
Hooks can be called in either function components or other functions marked as #[hook] (custom hooks). Calling hooks in a context that is not either of those results in terrible diagnostics, that make it very hard to figure out what is actually happening.
Steps To Reproduce
Try to compile the following snippet
use yew::{use_effect, use_state, hook};

// #[hook] // uncomment this line to see the hook compile properly
fn use_some_hook() -> String {
    let state = use_state(String::new);

    {
        let state = state.clone();
        use_effect(move || {
            state.set(String::from("some new value"));
            || {}
        })
    }

    (*state).clone()
}

Actual behavior
This error:
$ cargo check --target wasm32-unknown-unknown
    Checking yew v0.19.3 (/home/hamza/code/yew/packages/yew)
error[E0599]: no method named `clone` found for opaque type `impl functional::hooks::Hook<Output = functional::hooks::use_state::UseStateHandle<String>>` in the current scope
  --> packages/yew/src/suspense/hooks.rs:74:27
   |
74 |         let state = state.clone();
   |                           ^^^^^ method not found in `impl functional::hooks::Hook<Output = functional::hooks::use_state::UseStateHandle<String>>`

error[E0308]: mismatched types
   --> packages/yew/src/suspense/hooks.rs:75:9
    |
75  | /         use_effect(move || {
76  | |             state.set(String::from("some new value"));
77  | |             || {}
78  | |         })
    | |          ^- help: consider using a semicolon here: `;`
    | |__________|
    |            expected `()`, found opaque type
    |
   ::: packages/yew/src/functional/hooks/use_effect.rs:141:1
    |
141 |   #[hook]
    |   ------- the found opaque type
    |
    = note: expected unit type `()`
             found opaque type `impl functional::hooks::Hook<Output = ()>`

error[E0614]: type `impl functional::hooks::Hook<Output = functional::hooks::use_state::UseStateHandle<String>>` cannot be dereferenced
  --> packages/yew/src/suspense/hooks.rs:81:5
   |
81 |     (*state).clone()
   |     ^^^^^^^^

Some errors have detailed explanations: E0308, E0599, E0614.
For more information about an error, try `rustc --explain E0308`.
warning: `yew` (lib) generated 1 warning
error: could not compile `yew` due to 3 previous errors; 1 warning emitted

Expected behavior
Should give a better error message.
Environment:

Yew version: master
Rust version: 1.60.0
Target, if relevant: wasm32-unknown-emscripten
Build tool, if relevant: cargo check --target wasm32-unknown-unknown

Questionnaire

I'm interested in fixing this myself but don't know where to start

Gave it a little try.
It does not seem possible only using proc macros.
As function_component macro cant introspect code and check if Hook trait is implemented.
https://github.com/yewstack/yew/blob/7178d2ea3d3a12e08189c7e97fb2e2292e32270a/packages/yew-macro/src/hook/body.rs#L45-L56


How to set different/separated env vars per function?

Hello,
Thank you for creating an amazing useful library.
Can I set some vars only for one(or more) functions in a project?
Thanks.

It's a very good question. I didn't find any possibility to set this with the usage of this library that's why I decided to create my own config.js file to keep all the needed env variables and put them where I want during the work with serverless 😃
@colynb is it possible to do this via your library?

Would you mind describing a use-case/scenario so that I can get a better understanding? Thanks

@colynb Yes, of course, and I believe that it will be a simple example 😉
functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

I'm having a similar use case: I want to load env variables in my fargate task definition, but not in my lambda functions.
Your snippet should work if you add this setting:
custom:
  dotenv:
    include: [] # Do not inject env variables into lambdas

Having an option to disable auto injection could be great by the way :)

@colynb Yes, of course, and I believe that it will be a simple example 😉
functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

Hello everyone, I have additional questions about this scenario:
Assuming there are 10 env vars declared in .env e.g. SAMPLE_A ... SAMPLE_J
What happens to sample-funtion-a if we declare:

SAMPLE_C ... SAMPLE_J under custom > dotenv > include, and also

SAMPLE_A under sample-function-a

will sample-function-a get all the env vars except SAMPLE_B?

Hi, any updates on this?

@colynb Yes, of course, and I believe that it will be a simple example 😉
functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

This will definitely be very helpful

@krlozadan sorry for the VERY late response. I've been using today to get caught up on this plugin. As I mentioned in a few other issues here recently, I'm extremely nervous about accidentally introducing breaking changes so I erred on the side of simply ignoring these requests.

@colynb Yes, of course, and I believe that it will be a simple example wink
functions:
  sample-funtion-a:
    handler: src/handler.sampleFunctionA
    environment:
      SAMPLE_A: ${env:SAMPLE_A}
  sample-funtion-b:
    handler: src/handler.sampleFunctionB
    environment:
      SAMPLE_B: ${env:SAMPLE_B}

With the current functionality, we will get SAMPLE_A and SAMPLE_B in the environment section of both functions.

Hello everyone, I have additional questions about this scenario:
Assuming there are 10 env vars declared in .env e.g. SAMPLE_A ... SAMPLE_J
What happens to sample-funtion-a if we declare:

SAMPLE_C ... SAMPLE_J under custom > dotenv > include, and also
SAMPLE_A under sample-function-a

will sample-function-a get all the env vars except SAMPLE_B?

I am 90+% sure of the following. Please test my statements below if you would like to be 100% sure.
Environment variables defined with dotenv end up at the project level according to https://github.com/neverendingqs/serverless-dotenv-plugin/blob/2b66c1550bdbeb06be477cb068f4e41ad67f1339/index.js#L120-L122.
In your example, sample-function-a will include SAMPLE_B ... SAMPLE_J from the dotenv file(s) because it pulls it from the project level.
Furthermore, environment variables with the same name defined at the function name takes precedence over ones defined at a project level. This means sample-function-a's SAMPLE_A value is whatever you declare it to be. In your example, because you set it to ${env:SAMPLE_A},  sample-function-a's SAMPLE_A value will be the same as the one in the dotenv file(s).

I'm having a similar use case: I want to load env variables in my fargate task definition, but not in my lambda functions.
Your snippet should work if you add this setting:
custom:
  dotenv:
    include: [] # Do not inject env variables into lambdas

Having an option to disable auto injection could be great by the way :)

This is my recommendation as well. Please see https://github.com/neverendingqs/serverless-dotenv-plugin/issues/89 for details.

I think all questions have been answered. Because there are a variety of questions here, if you have a follow-up question or a related question, please post it in https://github.com/neverendingqs/serverless-dotenv-plugin/discussions/categories/q-a.
Thanks!


[Bug]: All interactive elements require double-click after closing drawer by releasing on mobile

Reproduction
https://www.shadcn-vue.com/docs/components/drawer.html
Describe the bug
After closing the drawer component by dragging it down and releasing, the first click on any interactive element on the page is not registered. It requires a second click to actually trigger the element's action. It does only seem to happen on my mobile device.
Test flow:

Open the drawer
Close the drawer by dragging down and releasing
You now have to click any interactive element on the page two times before the element's action is triggered

System Info
Test device: Google Pixel 8 Pro, Android
Test browser: Google Chrome, version 128.0.6613.146

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

Hello there!
I can't reproduce the issue on the website itself
Do you have any problem with the drawer component page?
If not, could you please provide a reproduction?

Hello there! I can't reproduce the issue on the website itself Do you have any problem with the drawer component page? If not, could you please provide a reproduction?

Which device did you test with? I am able to reproduce the issue on the website :)

I have the exact version
Chrome: Chrome 128.0.6613.146
OS: Android 12; M2007J20CG Build/SKQ1.211019.001
But I can't reproduce the issue, could you please check if an overlay is present when dragging the drawer down?
You can inspect an interactive element right after the drawer is closed.

@Saeid-Za

I have the exact version Chrome: Chrome 128.0.6613.146 OS: Android 12; M2007J20CG Build/SKQ1.211019.001

I have OS: Android 14; Build/AP22A.240905.003. Not sure if that changes anything 🤔

But I can't reproduce the issue, could you please check if an overlay is present when dragging the drawer down? You can inspect an interactive element right after the drawer is closed.

It's very weird - I tried inspecting on my phone and if I inspect the element I want to click before clicking it, after closing the drawer, the issue does not happen. It does happen if I do not inspect the element I want to click before clicking it. It does not seem like the overlay is present, but I'm not sure if that is because of the inspecting thing or not. I also tried adding an event listener for click events on the document and the click on an element after closing the drawer does not trigger at all 😕

Do you encounter this issue only on your mobile device?

Yes, mobile only.

Update: The bug is also happening on iPhone/Safari: https://github.com/radix-vue/vaul-vue/issues/66#issuecomment-2372024550

@Saeid-Za Do you have any idea of how to fix this? :)


Set user-defined list of colors, decrease required iOS version

Allow to set any list of predefined colors
Set named color programmatically to use on older iOS versions

Thank you for the great pull request😊


Suddenly getting "authorization failed" messages for admin and users

Version:
Connected to -------------:8086 version 1.2.4
InfluxDB shell version: 1.2.4
Steps to recreate:
In influx:

auth
username: admin
password:
show users
ERR: authorization failed

System hasn't been modified, no passwords have been changed. It just suddenly stopped authenticating. Any ideas on what went wrong? Hints on how to reset passwords?

same here.. Trying with nightly..
    #start without auth
    $proc = Start-Process -FilePath $influxd -PassThru
    $user = "influx"
    $passwd = "admin"
    $r = Invoke-WebRequest -Method Post -Uri "http://localhost:8086/query" -Body "q=CREATE USER   $user WITH PASSWORD '$passwd' WITH ALL PRIVILEGES" -UseBasicParsing

    #enable auth & restart
    $proc.Kill()
    (get-content $influxconf | foreach-object {$_ -replace "# auth-enabled = false" , "auth-enabled = true" })  | Set-Content $influxconf
    Start-Process -FilePath $influxd -ArgumentList "-config $influxconf" | Out-Null

    $r = Invoke-WebRequest -Method Post -Uri "http://localhost:8086/query?u=$user&p=$passwd" -Body "q=show users" -UseBasicParsing

giving me  Invoke-WebRequest : {"error":"authorization failed"}

Update on my situation,

I needed to re-generate the config file on the target platform (Windows in my test)
It does not like to have a non ASCII letter in password. (e.g. influx§)

.\influx.exe -username admin -password influx§

Connected to http://localhost:8086 version 1.4.0~n201707240800
InfluxDB shell version: 1.4.0~n201707240800
> show databases
ERR: authorization failed
Warning: It is possible this error is due to not setting a database.
Please set a database with the command "use <database>".

Getting the same issue with influxdb hosted on containers version 1.8.6 oss


add deep links to treasury tabs

As requested from lipman - enable deep links on treasury dashboard tabs.
For example - when navigating to https://app.olympusdao.finance/#/dashboard/treasury the treasury tab should be visible.

I agree.


How to close properly the port com

Hi
Thanks a lot for this Library
How can we close the com port of the instrument class (like serial.close()) ?
I have tried :
self.instrument.master.propar.stop()
or
self.instrument.master.stop()
But when i run again the program I had the following message :
Attempting to use a port that is not open
Thanks in advance

Hi Guys!
Same question here, I cannot close the propar.instrument() instance properly and it doesnt seem to be implemented yet. There is a close() method from the serial.py, but I think its not been used so far.
Thanks in advance


Make exception more specific to suppress rspec warnings

Without this I get the following warning when running the specs:
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/tomclose/zesty/redis-semaphore/spec/semaphore_spec.rb:95:in `block (3 levels) in <top (required)>'.

Awesome, thanks @tomclose!


Kurogewashu/decimal places

PR for https://github.com/OriginProtocol/origin-dollar/issues/661

We should use a lighter color grey for digits 3-6.

Good idea @joshfraser , it would be difficult to do in the input field, but I can add it into the expected output area

Thanks for the quick turnaround. We should use black instead of the dark gray on the second input field (up to the second decimal). We probably want the faded numbers to be the same hue as the background as well.

Hey, I seem to have encountered a couple of bugs:

(output balance is incorrect)

(input should format to 10302.00)
let me know when you address them and I can take another look 👀

@sparrowDom fixed the error, I may have used the provided function incorrectly.
app.hashflow.com, mentions zero slippage, tight spreads, MEV resistant. Their UI could be broken right now, but they also only use two decimal places.

I would go with 2-3 decimal places in expected output for better accuracy. I do understand how it may be valuable to have more decimal places in the expected output, so if anyone requests, I can add it back (also curious at comparing between expected and actual outputs).
Ideas for next steps:
-18 decimal places for input, or the max available decimal places for each token
-enable swapTokensForExactTokens

@sparrowDom only the first error is fixed* Just got a chance to look into the second one:

It works up to three digits, which my wallet coincidentally only has. Looking at your screenshot it should still work with "insufficient balance" error.
Currently using onBlur to add decimal places, if we use onChange, it would glitch when deleting the decimal place, (e.g. 100.00 becomes 10000 immediately as soon as the . is deleted)
Thought we could use debounce with onChange, but it wouldn't solve the above error if someone were in the middle of updating a number
I've isolated the problem: if it's larger than 3 digits with no decimal, then it gets caught in "checkValidInputForCoin" from "utils/math"
Are there unit tests for this regex line somewhere?
^((\\d{1,3})(?:[0-9]{3}){0,1}|(\\d{1})(?:[0-9]{3}){0,2}|(\\d{1,18}))((\\.)|(\\.\\d{1,${decimals}}))?$

@KurogeWashu I've cleaned up the PR a bit. I think everything should be working now as expected. Please take a look if it looks ok to you

@sparrowDom Looks good!


Reexport meta from foundation.

This wasn't quite as satisfying as I'd hoped, mostly because at the material layer (where we use @required a lot) we still have to import something from another layer in every file just to get the annotations.

The advantage here is that if you already import foundation, which you in theory often will, then you get these for free without having to import meta/meta. The other advantage is that our imports look cleaner just importing flutter packages.
The disadvantage is that now you're getting everything else in foundation where before you only got meta.
I could go either way on this.

Seems sort of neutral, but LGTM if you want to land it.  The arc.dart change is good through.  :)

Gonna merge this and see if I can improve it further.


Update http links

@NextTurn : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Link corrections confirmed. Thanks.


style(AppHeaderCatalogDropdown): responsive layout for mobile/tablet

Overview

Make new catalog dropdown responsive.
Sorry about the commit history - i originally branched off of another PR and the commits from that branch hopped onto this one. Squashing unsuccessful.

Monolith PR env: https://pr-30358-monolith.dev-eks.codecademy.com/
Desktop should look the same. Mobile, tablet should now be responsive. Only Catalog submenu should scroll.
PR Checklist

[x] Related to designs: https://www.figma.com/file/40NSFXquATvE19Gm9pnJzI/Catalog-navigation-dropdown?node-id=419%3A6020
[x] Related to JIRA ticket: DISC-558
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.c71312.0@codecademy/gamut-labs@31.3.4-alpha.c71312.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6255e23ce077bf1bb64c9f9e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.3a94d9.0@codecademy/gamut-labs@31.3.4-alpha.3a94d9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6255f31331981407b4b32c3e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.101-alpha.4756c1.0@codecademy/gamut-labs@31.5.1-alpha.4756c1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6255f81e9dfeac0981146c18--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.101-alpha.199070.0@codecademy/gamut-labs@31.5.1-alpha.199070.0@codecademy/gamut@46.1.1-alpha.199070.0@codecademy/monaco@0.6.33-alpha.199070.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://62573ac700b700205eb29c03--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.102-alpha.0bc703.0@codecademy/gamut-labs@31.6.1-alpha.0bc703.0@codecademy/gamut@46.1.2-alpha.0bc703.0@codecademy/monaco@0.6.34-alpha.0bc703.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://62574b1465c5de303e027016--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.102-alpha.4ddd00.0@codecademy/gamut-labs@31.6.1-alpha.4ddd00.0@codecademy/gamut@46.1.2-alpha.4ddd00.0@codecademy/monaco@0.6.34-alpha.4ddd00.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://625872cf6598c300b9c8d1f4--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.102-alpha.ad3bd4.0@codecademy/gamut-labs@31.6.1-alpha.ad3bd4.0@codecademy/gamut@46.1.2-alpha.ad3bd4.0@codecademy/monaco@0.6.34-alpha.ad3bd4.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://625882388e01fe05315d0130--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.102-alpha.2e846b.0@codecademy/gamut-labs@31.6.1-alpha.2e846b.0@codecademy/gamut@46.1.2-alpha.2e846b.0@codecademy/monaco@0.6.34-alpha.2e846b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6259d2b044c1ea00a9587fce--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.106-alpha.acdda3.0@codecademy/gamut-labs@31.8.2-alpha.acdda3.0@codecademy/gamut@46.1.3-alpha.acdda3.0@codecademy/monaco@0.6.35-alpha.acdda3.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6259ddd544c1ea073d5882d0--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.106-alpha.fe1657.0@codecademy/gamut-labs@31.8.2-alpha.fe1657.0@codecademy/gamut@46.1.3-alpha.fe1657.0@codecademy/monaco@0.6.35-alpha.fe1657.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6259e0e26b9d2b008bc45f41--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.106-alpha.3239b6.0@codecademy/gamut-labs@31.8.2-alpha.3239b6.0@codecademy/gamut@46.1.3-alpha.3239b6.0@codecademy/monaco@0.6.35-alpha.3239b6.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://625cce4d7e5f4f542f8fcd0b--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.106-alpha.3e5c9b.0@codecademy/gamut-labs@31.8.2-alpha.3e5c9b.0@codecademy/gamut@46.1.3-alpha.3e5c9b.0@codecademy/monaco@0.6.35-alpha.3e5c9b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://625cd9d884238d5a3612fab4--gamut-preview.netlify.appDeploy Logs

looking pretty good but noticed a few oddities...

the spacing for full menu looks kinda off

the tablet/md view looks a little off oo

did you go over this with tamar? it also seems like some of her designs aren't in line with what we already had (icons on tablet dont show) so probably good to make sure she is in the loop

looking pretty good but noticed a few oddities...

the spacing for full menu looks kinda off

the tablet/md view looks a little off oo

did you go over this with tamar? it also seems like some of her designs aren't in line with what we already had (icons on tablet dont show) so probably good to make sure she is in the loop

tamar mentioned tablet spacing as well. I am pushing fix for this. I also added spacing for that line. Otherwise she says looks good.

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.106-alpha.4e7222.0@codecademy/gamut-labs@31.8.2-alpha.4e7222.0@codecademy/gamut@46.1.3-alpha.4e7222.0@codecademy/monaco@0.6.35-alpha.4e7222.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://625ddef071c034008e17dd10--gamut-preview.netlify.appDeploy Logs

just noticed this is failing some e2e tests on the monolith + probably should double-check portal as well - will ✅ again once those are passing CI!

Ah had some flakers on that one. Just reran - looks to be passing now.

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.106-alpha.a054d6.0@codecademy/gamut-labs@31.8.2-alpha.a054d6.0@codecademy/gamut@46.1.3-alpha.a054d6.0@codecademy/monaco@0.6.35-alpha.a054d6.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6260843cd8391c3d8326500b--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.107-alpha.f79d4e.0@codecademy/gamut-labs@31.8.3-alpha.f79d4e.0@codecademy/gamut@46.1.3-alpha.f79d4e.0@codecademy/monaco@0.6.35-alpha.f79d4e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6260a57ecd61835700751143--gamut-preview.netlify.appDeploy Logs


SIMD#83 - SVM changes to allow conflicting entries

Problem
Leader pipeline can only process entries with non-conflicting transactions which limits the innovation in scheduling strategy and thus better TPS.
Summary of Changes
Changes to enable SVM to handle self-conflicting entries:

Move all the account state changing functions (like fee and rent deduction) from loading accounts function to the execution part of the batch processing.
Perform the account state changing operations on tx-by-tx basis rather than at entry level. Carry the temp state of accounts during fee deduction and execution of txns. This is to use the intermediate account state for any conflicting txn in the same entry.

Related to:
#1025

Also please run clippy and fmt on your PR before committing; it will make review process more straight-forward if I do not have to also comment on fixing basic CI operations

i think this needs rebase on #1636
Also, maybe we need program_cache changes as well?

also needs to ensure there's no problem of non-disjoint entries for acccount_lookup_table functionality and find_send_votes() code-path.

Also, maybe we need program_cache changes as well?

From my discussions with @alessandrod, program updates are not "available" in the slot they happen in. i.e. if there's a program upgrade in slot N all txs in slot N will use the old program bytes. All txs in slot >N would see the upgrade.
So I don't think there's any issues with program-cache, at least from the program modification perspective.

also needs to ensure there's no problem of non-disjoint entries for acccount_lookup_table functionality and find_send_votes() code-path.

Not sure about find_send_votes, so agree that needs to be checked.
I think ALT functionality should be good already. ALT resolution is "locked" to the state at start of the slot - i.e. changes are not available until next slot.

i think this needs rebase on #1636
Also, maybe we need program_cache changes as well?

One significant change I noticed while rebasing is that the fee validation has been moved into a separate step and is now performed on an entire entry at once. Previously, this validation was done on a per-transaction basis during account loading. This change might cause issues in self-conflicting batches where transaction fee validation results can vary between transactions.
I am considering moving the fee validation to a point where it is done before the execution of each transaction. Any thoughts on this approach?

Rebased and incorporated all refactoring changes.


Partition asymmetry as defined in https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2868386/

I also added a higher level test for both of the partition functions.

Current coverage is 100% (diff: 100%)

Merging #585 into master will not change coverage

@@           master   #585   diff @@
====================================
  Files          41     41
  Lines        2039   2047     +8
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
+ Hits         2039   2047     +8
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 6d3c840...0ccbd07

The last commit partly fixes #586, but the bifurcation angle tests are still missing.

Please don't merge yet. I need to simplify the tests further.

OK, I think that now all cases and bifurcation functions are covered with the tests, so #586 should be fixed. @mgeplf let me know if this works.


Changed config to remove some big elements from redux devtools state

Overview

I did this and my browser and my computer are finally breathing.
— @sorodrigo

God gave me choice between good memory and devtools with a lot of info on them, I don't remember what I chose.
— me

many thanks to @sorodrigo for his wisdom and blazin experience.


MarkCount / MarkArray

I'm trying to generate a variable font with one axis from five weights. As far as I know the glyphs are compatible and the order is the same. However, I'm getting this AssertionError when fontmake tries to merge the GPOS table:
Building interpolation-compatible TTFs
Converting curves compatibly
New spline lengths: 1: 8, 2: 915, 3: 591, 4: 44, 5: 2
Saving TTF for Upgrade-UltraBlack
Underline position not set in UFO, defaulting to UPM * -0.075
Underline thickness not set in UFO, defaulting to UPM * 0.05
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Saving TTF for Upgrade-Hairline
Underline position not set in UFO, defaulting to UPM * -0.075
Underline thickness not set in UFO, defaulting to UPM * 0.05
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Saving TTF for Upgrade-Black
Underline position not set in UFO, defaulting to UPM * -0.075
Underline thickness not set in UFO, defaulting to UPM * 0.05
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Saving TTF for Upgrade-Light
Underline position not set in UFO, defaulting to UPM * -0.075
Underline thickness not set in UFO, defaulting to UPM * 0.05
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Attempting to fix OTLOffsetOverflowError %s
Saving TTF for Upgrade-Semibold
Underline position not set in UFO, defaulting to UPM * -0.075
Underline thickness not set in UFO, defaulting to UPM * 0.05
Building variable font variable_ttf/UpgradeRoman-VF.ttf
Axes:
OrderedDict([('wght', {u'map': None, 'name': 'wght', 'default': 0.0, 'tag': 'wght', 'maximum': 500.0, 'minimum': 0.0, 'labelname': {'en': 'wght'}})])
Internal master locations:
[{'wght': 300.0},
 {'wght': 0.0},
 {'wght': 100.0},
 {'wght': 200.0},
 {'wght': 500.0}]
Internal axis supports:
{'wght': [0.0, 0.0, 500.0]}
Normalized master locations:
[{'wght': 0.6}, {'wght': 0.0}, {'wght': 0.2}, {'wght': 0.4}, {'wght': 1.0}]
Index of base master: 1
Building variable font
Loading master fonts
Generating fvar
Generating avar
No need for avar
Building variations tables
Generating MVAR
	xhgt: OS/2.sxHeight	[478, 462, 462, 470, 502]
Generating HVAR
font is <fontTools.ttLib.TTFont object at 0x124ecec50>
Merging OpenType Layout tables

Traceback (most recent call last):
  File "/Users/michiel/Code/TnBits/src/tnbits/toolparts/bakery/controller.py", line 240, in run
  File "/Users/michiel/Code/FontMake/Lib/fontmake/font_project.py", line 438, in run_from_designspace
  File "/Users/michiel/Code/FontMake/Lib/fontmake/font_project.py", line 497, in run_from_ufos
  File "/Users/michiel/Code/FontMake/Lib/fontmake/font_project.py", line 220, in build_variable_font
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/__init__.py", line 725, in build
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/__init__.py", line 518, in _merge_OTL
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 107, in mergeTables
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 94, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 71, in mergeObjects
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 94, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 71, in mergeObjects
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 94, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 71, in mergeObjects
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 96, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 81, in mergeLists
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 92, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 621, in merge
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 81, in mergeLists
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 94, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 71, in mergeObjects
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 94, in mergeThings
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 71, in mergeObjects
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/varLib/merger.py", line 98, in mergeThings
AssertionError: ((32, [32, 32, 34, 30, 18]), 'int', '.MarkCount', 'MarkArray', '.MarkArray', 'MarkBasePos', '[0]', 'Lookup', '[1]', 'list', '.Lookup', 'LookupList', '.LookupList', 'GPOS', '.table', 'table_G_P_O_S_')

Is something wrong with the source UFOs? How can I tell? This is in RoboFont 2 btw.

Did you check your anchors? You might have glyphs with different anchors accross masters.

@khaledhosny They are different, so  that's probably it. Thank you, will close this for now.


Training: Standard WM debugging

Impact of the new feature
WM in general
Is your feature request related to a problem? Please describe.
Sharing knowledge and empowering WM/Ops to understand and debug the system. Sub-task of https://github.com/dmwm/WMCore/issues/11837
Describe the solution you'd like
Topic of this ticket is: Standard WM debugging
For the expected solution, please refer to the meta-issue for further details (in short: documentation + recorded presentation).
Describe alternatives you've considered
None
Additional context
None

Thanks for the efforts @amaltaro. Here I'll leave a few subjects that I think should be included in this training:

Debugging on running components

Attaching debuggers to component processes
Safety considerations and best practices when working on production environments

Reproducing issues on testing environments
CouchDB logs and test queries

I would also like to see material on the following subjects, although I'm not sure they fall into the scope of this training (maybe useful for a future session):

Setup development environment
Applying patches in development env (and production?)
Running tests

My opinion for a basic debugging is:

workflow status based debugging (according to the status, where we need to look for information)
heartbeat timeout debugging
multi-thread WMAgent components investigation

I would actually not add anything new but I'd mostly like to second  @germanfgv 's suggestion. Thanks German! All of what you requested is falling perfectly under this session, and I'll be pretty happy to walk through those. If you want we  can even meet in advance and you let me know about any particular use case you may have already encountered.

I second @germanfgv suggestions, they are all highly useful topics that I would also be interested in.
If in scope, I would also like to add a topic on debugging WQEs, Why a certain WQE was picked or what the next WQEs a workflows will be picked by the agent next. I find this process of pulling work opaque and would like to know how to debug this in the agents.
Thank you.

I'm closing the issue, since the training has been held successfully

@anpicci let me reopen it such that we do not forget the deliverables - as discussed in yesterday's meeting and post-meeting on MM - a page in wmcore-docs with those questions/answers that we addressed in the training, plus the others that we did not manage to cover.
I plan to have it done today, but in case I miss it, we have this open issue to remind me.

After discussing with alan, here is the new page in wmcore-docs.

https://cms-wmcore.docs.cern.ch/training/workflow-troubleshoot/
introduced with the merge request https://gitlab.cern.ch/dmwm/wmcore-docs/-/merge_requests/70

I think we can close this issue

Awesome, thank you very much, Dario. I am closing this ticket out as completed now. Thanks again everyone!


what's the difference between maplab and voxblox?

maplab : https://github.com/ethz-asl/maplab

after reading our papers again and a lot of discussions we came up with the following list of differences:

Sources:

https://en.wikipedia.org/wiki/Sheep
https://en.wikipedia.org/wiki/Fox
https://arxiv.org/abs/1711.10250
https://helenol.github.io/publications/iros_2017_voxblox.pdf

@mfehr Marius it's funny but so meaningful. Thanks

after reading our papers again and a lot of discussions we came up with the following list of differences:
Sources:

https://en.wikipedia.org/wiki/Sheep
https://en.wikipedia.org/wiki/Fox
https://arxiv.org/abs/1711.10250
https://helenol.github.io/publications/iros_2017_voxblox.pdf

This reply is very beautiful!


python-zmq-debuginfo.x86_64 debug info is not correct.

while trying to use GDB to determine what is happening with a weird segfault. I have gdb complaining that the debug info for zmq does not match file files correctly.
[root@salt00 test]# gdb
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) file python3
Reading symbols from /usr/bin/python3.6...Reading symbols from /usr/lib/debug/usr/bin/python3.6.debug...done.
done.
(gdb) run -c 'import salt.config'
Starting program: /bin/python3 -c 'import salt.config'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/constants.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/constants.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/constants.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/constants.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/constants.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/c4/78b639f3957c6c0cfb95c239be1dde9d3e5712.debug
warning: the debug information found in "/usr/lib/debug//lib64/libzmq.so.5.0.0.debug" does not match "/lib64/libzmq.so.5" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/libzmq.so.5.0.0.debug" does not match "/lib64/libzmq.so.5" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug//usr/lib64/libzmq.so.5.0.0.debug" does not match "/lib64/libzmq.so.5" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64//libzmq.so.5.0.0.debug" does not match "/lib64/libzmq.so.5" (CRC mismatch).

Missing separate debuginfo for /lib64/libzmq.so.5
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/45/122744768c850cf7c53df63e5f7ef91e1b26fe.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/error.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/error.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/error.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/error.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/error.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/a2/c1fbf623f93220d8eb505b6fb046c5ef3de0f2.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/message.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/message.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/message.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/message.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/message.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/42/f40d4ecbb29e12a239876ce8495587ded36bca.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/context.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/context.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/context.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/context.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/context.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/4c/072e227f343c07813d6fcee39db3b02951141d.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/socket.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/socket.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/socket.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/socket.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/socket.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/2d/51b9d95eba8b078e976914b2a3f89ea1b1053b.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/utils.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/utils.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/utils.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/utils.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/utils.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/72/1dd010fa3920726394e109f00d11ddf0ec0cc7.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/_poll.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/_poll.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/_poll.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/_poll.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/_poll.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/d6/fbca2eb9d20d655a1ff3a4bf34adb35175d3a8.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/_version.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/_version.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/_version.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/_version.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/_version.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/3d/e27b2fddb45f8fc0975892d3db5a68a552c31e.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/python3.6/site-packages/zmq/backend/cython/_device.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/_device.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib64/python3.6/site-packages/zmq/backend/cython/_device.cpython-36m-x86_64-linux-gnu.so.debug" does not match "/usr/lib64/python3.6/site-packages/zmq/backend/cython/_device.cpython-36m-x86_64-linux-gnu.so" (CRC mismatch).

Missing separate debuginfo for /usr/lib64/python3.6/site-packages/zmq/backend/cython/_device.cpython-36m-x86_64-linux-gnu.so
Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/90/dee82860891668053685bd49f1c71d814cb15d.debug
[Detaching after fork from child process 2493]
[Detaching after fork from child process 2495]
[Inferior 1 (process 2489) exited normally]
(gdb)

[root@salt00 test]# yum list installed |grep zmq
python-zmq-debuginfo.x86_64     17.0.0-5.el7                    @salt-py3-latest
python36-zmq.x86_64             17.0.0-5.el7                    @salt-py3-latest

Which repo did you have configured that this is pulling from? or rather, what does your .repo file look like?

ugh, thanks. I thought I had already switched to saltproject. apparently I did not on this host
[salt-py3-latest]
name=SaltStack Latest Release Channel Python 3 for RHEL/Centos $releasever
baseurl=https://repo.saltstack.com/py3/redhat/7/$basearch/latest
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/saltstack-signing-key, file:///etc/pki/rpm-gpg/centos7-signing-key

humm, nope switching to saltproject and uninstalling and reinstalling that debuginfo and gdb still gives the same errors

btw, going forward, I've been just copying the rpms from epel directly rather than re-compiling them from source rpms.  The only thing I do is re-sign them.
https://repo.saltproject.io/salt_rc/py3/redhat/7/x86_64/
I wasn't planning on copying the respective debug rpms or source rpms for ones directly copied from epel, assuming people could just grab epel's copies of those if they wanted them.
Is that going to be an issue?

looks like python36-zmq in our repos is a newer version that is not in epel, so this is a legitimate problem I need to look into.  Hopefully in time for 3003.1.


opml-conduit test suite broken with uri-bytestring-0.2

Ping @k0ral. It seems that URI is no longer an instance of Generic.
[2 of 3] Compiling Arbitrary        ( test/Arbitrary.hs, dist/build/tests/tests-tmp/Arbitrary.o )

test/Arbitrary.hs:44:12:
    No instance for (Generic URI) arising from a use of ‘genericShrink’
    In the expression: genericShrink
    In an equation for ‘shrink’: shrink = genericShrink
    In the instance declaration for ‘Arbitrary URI’

Fixed in https://github.com/k0ral/opml-conduit/commit/e66d644cf6e9026f05e1f423ce206b4e9b12d4cf, included in release <IP_ADDRESS> . Thanks for reporting.

Thanks!


PTX-5395: PDS Functional test automation.

Considering the fact it is just sample automation run for a very basic scenario. There are multiple instances in the code that are supposed to be improved/modified and also M6/Beta test runs are of high priority as of now. Hence I will be taking up the improvement/modification in the codes once the Jenkins pipeline will be integrated with the torpedo run for PDS.

This seems to have become kind of stale.
If there's not any strong desire to finish this, I would tend to ditch most of the code that got ported over from our old prototype and build the structure from the ground up, because at this point it's questionable how much of the old stuff is still relevant and we might just be dragging a lot of dead code with us.
I would start out from a single primitive spec, make it a failing one with no actual logic, and we can use it to start sketching out the feedback part of a failing test (describing component states/grabbing logs from PDS components) to see if we can get any helpful format out of it. I can take this up in the coming days, at least put down the structure to build upon.


Album get_title() sometimes returns "Album not found" if properly_capitalized is set

Uncovered an corner case where calling get_title() on an album returns WSError: Album not found for a valid album, only if properly_capitalized is set to True.
Using latest pypi version, 3.2.1
This works:
release = lastfm.get_release(":zoviet*france:", "Loh Land")
api_release.get_title()

This does not:
release = lastfm.get_release(":zoviet*france:", "Loh Land")
api_release.get_title(properly_capitalized=True)

Thanks for the report.
What is lastfm.get_release?
Is it the same as something like:
import pylast

API_KEY = "TODO"
API_SECRET = "TODO"

network = pylast.LastFMNetwork(api_key=API_KEY, api_secret=API_SECRET)

album = network.get_album(":zoviet*france:", "Loh Land")

If so, I can reproduce it with that exammple:
>>> album = network.get_album(":zoviet*france:", "Loh Land")
>>> album.get_title()
'Loh Land'
>>> album.get_title(properly_capitalized=True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pylast/__init__.py", line 1539, in get_title
    self._request(self.ws_prefix + ".getInfo", True), "name"
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pylast/__init__.py", line 1118, in _request
    return _Request(self.network, method_name, params).execute(cacheable)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pylast/__init__.py", line 951, in execute
    response = self._download_response()
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pylast/__init__.py", line 940, in _download_response
    self._check_response_for_errors(response_text)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pylast/__init__.py", line 970, in _check_response_for_errors
    raise WSError(self.network, status, details)
pylast.WSError: Album not found

But not with something like:
>>> album = network.get_album("Nirvana", "Nevermind")
>>> album.get_title()
'Nevermind'
>>> album.get_title(properly_capitalized=True)
'Nevermind'

Perhaps it's related to the non-alpha characters in the name... Do you have other examples which don't work?

Thanks for the quick response. get_release was a wrapper for get_album, I've updated my original post accordingly.
On closer inspection, I think this is most likely yet another problem with the last.fm API itself. The album doesn't seem to have a full set of data associated with it, perhaps this is related.
This does not load:
http://ws.audioscrobbler.com/2.0/?method=album.getinfo&api_key=xxx&artist=:zoviet*france:&album=Loh Land&format=json
https://www.last.fm/music/:zoviet*france:/Loh+Land
However this does (same artist, so it's probably not a unicode issue):
http://ws.audioscrobbler.com/2.0/?method=album.getinfo&api_key=xxx&artist=:zoviet*france:&album=just an illusion&format=json
https://www.last.fm/music/:zoviet*france:/Just+An+Illusion

network.get_album doesn't make any API calls, it just returns an Album object.
Similarly, Album.get_title() doesn't make any API calls, it just returns the title you gave when creating the object.
However, Album.get_title(properly_capitalized=True) does make an API call, to get info from Last.fm about the album, and return the canonical name Last.fm has for the album.

It's working for an artist with an asterisk:
>>> album = network.get_album("B*Witched", "C'est la vie")
>>> album.get_title(properly_capitalized=True)
"C'est La Vie"

And with a colon:
>>> album = network.get_album("D:Ream", "world")
>>> album.get_title(properly_capitalized=True)
'World'

But for some reason not for :zoviet*france:

However, if we get the artist, and then look up the top albums:
>>> artist = network.get_artist(":zoviet*france:")
>>> artist.get_name(properly_capitalized=True)
':Zoviet*France:'
>>> albums = artist.get_top_albums(limit=20)
>>> albums[0]
TopItem(item=pylast.Album('Zoviet France', 'Decriminalisation Of Country Music', pylast.LastFMNetwork('TODO', 'TODO', '', '', '')), weight=39233)
>>> albums[11]
TopItem(item=pylast.Album('Zoviet France', 'Loh Land', pylast.LastFMNetwork('TODO', 'TODO', '', '', '')), weight=40425)

So for some reason, Last.fm have these under the name Zoviet France. Plugging that back in to the original query:
>>> album = network.get_album("Zoviet France", "Loh Land")
>>> album.get_title(properly_capitalized=True)
'Loh Land'

I'm not sure why it's doing this, there seems to be something strange on the Last.fm side.
For example, if you visit https://www.last.fm/music/:zoviet*france: in the browser, it redirects to https://www.last.fm/music/Zoviet+France

If you click to see the albums, and choose Loh Land, the link is https://www.last.fm/music/Zoviet+France/Loh+Land but it redirects to https://www.last.fm/music/:zoviet*france:/Loh+Land

Some other albums are under Zoviet France, and others under :zoviet*france:
https://www.last.fm/music/Zoviet+France/Misfits,+Loony+Tunes+and+Squalid+Criminals
https://www.last.fm/music/Zoviet+France/Music+For+A+Spaghetti+Western
https://www.last.fm/music/:zoviet*france:/Shouting+at+the+Ground
https://www.last.fm/music/:zoviet*france:/Just+An+Illusion
https://www.last.fm/music/:zoviet*france:/The+Decriminalisation+of+Country+Music
https://www.last.fm/music/Zoviet+France/Gris
https://www.last.fm/music/Zoviet+France/Gesture+Signal+Threat
https://www.last.fm/music/:zoviet*france:/Norsch
So it appears that different albums appear under different canonical names, depending on what the band were using at the time (or how Last.fm has that data), and you need to use the right one?

Last.fm has support for aliasing, so common alternative names/misspellings will redirect to the correct entry. I believe this is what's happening here - https://www.last.fm/music/:zoviet*france: redirects to https://www.last.fm/music/Zoviet+France , however the same redirection isn't happening on the API. Unfortunately this is something which would have to be fixed on their end.

https://getsatisfaction.com/lastfm/categories/lastfm_api would be the place to report it to Last.fm. Drop a link here if you do. Thanks!


bilibili: 1.13.5-2 -> 1.13.6-2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/msojocs/bilibili-linux/releases.
meta.description for bilibili is: Electron-based bilibili desktop client
meta.homepage for bilibili is: https://github.com/msojocs/bilibili-linux
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.13.6-2 in filename of file in /nix/store/cdzryfkqb1qvmdzy14m9zim3kivp0jj6-bilibili-1.13.6-2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bilibili

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cdzryfkqb1qvmdzy14m9zim3kivp0jj6-bilibili-1.13.6-2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bilibili https://github.com/r-ryantm/nixpkgs/archive/10680f39b762d00685cb8d516f1253632e46878e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/10680f39b762d00685cb8d516f1253632e46878e#bilibili

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cdzryfkqb1qvmdzy14m9zim3kivp0jj6-bilibili-1.13.6-2
ls -la /nix/store/cdzryfkqb1qvmdzy14m9zim3kivp0jj6-bilibili-1.13.6-2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

bilibili

Maintainer pings
cc @jedsek @kashw2 for testing.

@NixOS/nixpkgs-merge-bot merge


TC0002: Interaction Handling with more than 1 federate

in test case TC0002 the helloWorldBaseModel.getInteractionMessageStatus() must collect for all incoming interactions in order to test if SuT interaction has been received. Test in line 165 must be exteded to test a list of received messages

Changed handling of interactions to save interactions by country name. The tests will check if the values are correct for the country.


Fix issue with resolving closures in langlib calls with arrow expressions in query expressions

Purpose
$title
Fixes #38783
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@lasinicl Please send this fix to master as well.


KAFKA-15130: Delete remote segments when delete a topic

The PR resolve issue KAFKA-15130. When tiered storage is enabled and delete.topic.enable=true , deleting a topic should also delete the corresponding segments of that topic on the remote system, and cancel the RLMTask for that topic.
Co-authored-by: Kamal Chandraprakash<EMAIL_ADDRESS>

@divijvaidya @showuon The PR is ready for review. Please take a look.

Apologies if my question is due to lack of context, but the RemoteLogManager has a method called stopPartitions which doesn't appear to be called by anything currently. Is there a reason why you are not calling that method directly from the ReplicaManager and putting the logic in it?

Thanks for the comment @clolov. It seems this PR calls RemoteLogManager.stopPartitions().

@DL1231
Thanks for the changes in the PR! It needs few more changes which I have done based on our internal branch. And, would like to collaborate with you on this PR.  The commit in my KAFKA-15130 git branch contains some of the remaining changes required. I am also working on deleting the remote log segments on KRAFT mode.
Shall I will work with you to push these changes into your branch?

@kamalcph
Sure, I appreciate your feedback on the PR. Please go ahead and collaborate with me on the changes. You can push the remaining changes from your KAFKA-15130 branch to my branch. Let's work together to finalize the PR. Thank you!

@DL1231 @junrao @showuon
Update the PR to remove the remote log segments when a topic gets deleted in ZK mode.
In the next set of commits, will address:

Covering with unit tests
Making the segment deletion async and
Adding support for Kraft.

Please take a look when you get chance!

port. ZK mode is deprecated and we cannot add new features there that don't exist in KRaft.
Leaving a -1 until this is addressed.

I didn't follow previous changes, but I think current implementation also works for KRaft mode, right? I can see ReplicaManager#applyDelta is invoking stopPartitions, which will do what we expect. Is my understanding correct?

I didn't follow previous changes, but I think current implementation also works for KRaft mode, right? I can see ReplicaManager#applyDelta is invoking stopPartitions, which will do what we expect. Is my understanding correct?

@showuon : It seems the latest PR still doesn't support KRaft. The issue is that ReplicaManager#applyDelta is invoking a version of stopPartitions() that always sets StopPartition.deleteRemoteLog to false.

@junrao @divijvaidya @showuon @satishd
Addressed your review comments and added support for Kraft mode. PTAL when you get chance!
Tickets are created for the pending items: KAFKA-15331 and KAFKA-15313

@kamalcph : Thanks for the updated PR. Just a couple of minor comments. Also, do we have test cases that cover topic deletion in KRaft mode with remote storage?

Added the integration test. PTAL.

@divijvaidya @junrao @showuon @satishd
Addressed your review comments. PTAL.

@junrao
Test failures are unrelated to this PR. I've ran them locally, they were succeeded:
Build / JDK 11 and Scala 2.13 / [2] tlsProtocol=TLSv1.2, useInlinePem=true – org.apache.kafka.common.network.SslTransportLayerTest
17s
Build / JDK 11 and Scala 2.13 / testThreadPoolResize() – kafka.server.DynamicBrokerReconfigurationTest
23s
Build / JDK 11 and Scala 2.13 / testBecomeFollowerWhileOldClientFetchInPurgatory() – kafka.server.ReplicaManagerTest
<1s
Build / JDK 11 and Scala 2.13 / testTaskRequestWithOldStartMsGetsUpdated() – org.apache.kafka.trogdor.coordinator.CoordinatorTest

I will merge the PR to unblock other integration test related PRs. Remaining items if any can be addressed in followup PRs.

Failed tests do not seem to be related. @kamalcph Please check and confirm.

I will merge the PR to unblock other integration test related PRs as it has got 2 +1s(Jun and me). Remaining items if any can be addressed in followup PRs.


Allow to Collapse Blocks

Is your feature request related to a problem? Please describe.
Long config files lack the possibility to get an easy overview of different config directives.
Describe the solution you'd like
In long(er) config files, it would be great to have the possibility to collapse blocks from { to }, so you could easily check all existing locations (for example)
Describe alternatives you've considered
The only alternative (I see) would be to migrate every block into a file that is included into the config.

Collapse Blocks feature added. The new version is available for download


PowerShell does not have overload method of TrackEvent() in Microsoft.ApplicationInsights.TelemetryClient

Hi all,
I was trying to use Microsoft.ApplicationInsights.TelemetryClient to send custom event to Application Insights via PowerShell. I did find TrackEvent() has overload method which might could send custom measurements. However, it said Cannot find an overload for "TrackMetric" and the argument count: "3".
this is my code
$client = [Microsoft.ApplicationInsights.TelemetryClient]::new()
$p = [pscustomobject]@{
    Str = "String Test"
} | ConvertTo-Json

$measurement = [pscustomobject]@{
    totalTime = 0.33
} | ConvertTo-Json
$client.TrackEvent("Test Message", $p, $measurement);

Is there anyone know how to send the custom measurements data to the application insight?
Tks.

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

ID: 61c28aeb-55c8-b340-f9d1-dcbdd3404bde
Version Independent ID: 1ff4149b-f85c-a9d7-c8b0-cbb2c5357af2
Content: TelemetryClient.TrackEvent Method (Microsoft.ApplicationInsights) - Azure for .NET Developers
Content Source: xml/Microsoft.ApplicationInsights/TelemetryClient.xml
Service: application-insights
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

This issue has been transferred to the repository where the Microsoft.ApplicationInsights package is maintained as #2744.


Trade multiple times glitch

https://www.reddit.com/r/Augur/comments/4boex1/trade_glitch/

I wrote the original reddit post - just signed up so I could post issues here instead.
I just found/figured that my account was likely deleted, possibly days ago. I didn't know it until now because I was able to log in and make trades - though it was generally glitchy but I chalked it up to the beta. I couldn't log in after clearing the browser cache so I created a new account with identical information and it looks like I am starting over again from scratch. I've made a few test trades and so far everything is smooth.

Though I was optimistic having an expired account was the cause and a new account the fix, it looks like it happened again. Not sure because the trade froze, but going in for 1000 shares appeared to put me on track for 2000.
Trade commitment hash:
-0x716c8c569887d245cab507a5072a3263c6267ce6c6f885c995265e88fbd306e8
Trade commitment sent. Waiting for confirmation...
Trade commitment sent. Waiting for confirmation...
Trade commitment confirmed. Sending trade...

Combined with #615


[pre-sve] TC-MF-1.10 BCM mode advertised as CM=0

Problem

BCM opened and avahi-browse shows CM=1
BCM opened and avahi-browse shows CM=0 which shouldn't happen according to <IP_ADDRESS> "A Commissionee that is not in
commissioning mode (CM=0) SHALL NOT publish this subtype"
TC-MF-1.10
qpg6105 + x64 controller

txt = ["PI=" "PH=36" "CM=0" "D=3840" "T=0" "SAI=300" "SII=5000" "VP=65521+32773"]
= enp0s3 IPv6 6FCB71DD481A6B86                              _matterc._udp        local
hostname = [223BAECD839A1E85.local]
address = [fd11:22::b085:8ca5:8047:abee]
port = [5540]

Proposed Solution
No fix

How was BCM window opened?

@jimlyall-q What exactly was being browsed for?
When CM=0, what should happen is:

There is a TXT entry with key "CM" and value "0".  That's what I see in the txt = bits shown above, and that part is correct.
The service name is not registered for the _CM._matterc._udp type+subtype (that's the "SHALL NOT publish this subtype" bit from the spec).  Was the browse being done for that subtype, or just for _matterc._udp across all subtypes?

Also, above where it says "BCM opened and avahi-browse shows CM=0" is that supposed to be "BCM closed and ..."?  Because having CM=0 while a commissioning window is open would be very unexpected.

TC_MF_1_10.1654071053.log
Steps 2 open commissioning window - chip-tool administratorcommissioning open-basic-commissioning-window 500 1 0 --timedInteractionTimeoutMs 1000
Step 3 avahi-browse - avahi-browse -rt _matterc._udp

Step 3 avahi-browse - avahi-browse -rt _matterc._udp

Thank you.
So if the server has extended discovery enabled, after initial commissioning it will advertise itself with CM=0.  You can see this in the log after network enable when we start getting advertisements like:
[1654071097.354913][3439:3444] CHIP:DIS: MINMDNS: received SRV record for 6FCB71DD481A6B86._matterc._udp.local
[1654071097.357259][3439:3444] CHIP:DIS: MINMDNS:     Commission SRV for instance 6FCB71DD481A6B86: 223BAECD839A1E85.local
...
[1654071097.357278][3439:3444] CHIP:DIS: MINMDNS: received PTR record for _services._dns-sd._udp.local
...
[1654071097.357290][3439:3444] CHIP:DIS: MINMDNS: received TXT record for 6FCB71DD481A6B86._matterc._udp.local
[1654071097.357299][3439:3444] CHIP:DIS: MINMDNS: received PTR record for _services._dns-sd._udp.local
[1654071097.357328][3439:3444] CHIP:DIS: MINMDNS: received PTR record for _L3840._sub._matterc._udp.local
[1654071097.357332][3439:3444] CHIP:DIS: MINMDNS: received PTR record for _S15._sub._matterc._udp.local
[1654071097.357337][3439:3444] CHIP:DIS: MINMDNS: received PTR record for _V65521._sub._matterc._udp.local
[1654071097.357341][3439:3444] CHIP:DIS: MINMDNS: received PTR record for _matterc._udp.local

The logging here does not show the contents of the TXT record, but I would assume it's got "CM=1" in it.  Note the lack of a "_CM.sub._matterc._udp.local" PTR record, because we are not in commissioning mode at that point.
When a commissioning window is then opened it will generate a new instance name and advertise with CM=1 (since it's a basic commissioning window).
The avahi-browse then shows the old records (because they get cached until TTL expires), so you see things like:
= docker0 IPv6 6FCB71DD481A6B86                              _matterc._udp        local
hostname = [223BAECD839A1E85.local]
address = [fd11:22::b085:8ca5:8047:abee]
port = [5540]
txt = ["PI=" "PH=36" "CM=0" "D=3840" "T=0" "SAI=300" "SII=5000" "VP=65521+32773"]

which has the same instance name as the log from minmdns above, and definitely has CM=0.
You also have the new records:
= docker0 IPv6 F24A94727E3F1C9A                              _matterc._udp        local
hostname = [223BAECD839A1E85.local]
address = [fd11:22::b085:8ca5:8047:abee]
port = [5540]
txt = ["PI=" "PH=36" "CM=1" "D=3840" "T=0" "SAI=300" "SII=5000" "VP=65521+32773"]

where the hostname is the same (since that's based on the MAC address), but the instance name is now F24A94727E3F1C9A instead of 6FCB71DD481A6B86.  These are the records for the commmissionable advertisement, and they have CM=1.
Doing avahi-browse -rt _CM._sub._matterc._udp should work to only browse the things that have the _CM PTR record bits (i.e. only the things that are currently commissionable), and none of those should have CM=0 in the TXT records.

Oh, and in step 4, when we are doing on-network discovery you can see:
[1654071102.239650][3455:3460] CHIP:DIS: MINMDNS: received SRV record for F24A94727E3F1C9A._matterc._udp.local
[1654071102.239743][3455:3460] CHIP:DIS: MINMDNS:     Commission SRV for instance F24A94727E3F1C9A: 223BAECD839A1E85.local
[1654071102.239770][3455:3460] CHIP:DIS: MINMDNS: received TXT record for F24A94727E3F1C9A._matterc._udp.local
[1654071102.239801][3455:3460] CHIP:DIS: MINMDNS: received PTR record for _CM._sub._matterc._udp.local
[1654071102.239827][3455:3460] CHIP:DIS: MINMDNS: received PTR record for _L3840._sub._matterc._udp.local
[1654071102.239850][3455:3460] CHIP:DIS: MINMDNS: received PTR record for _S15._sub._matterc._udp.local
[1654071102.239874][3455:3460] CHIP:DIS: MINMDNS: received PTR record for _V65521._sub._matterc._udp.local
[1654071102.239896][3455:3460] CHIP:DIS: MINMDNS: received PTR record for _matterc._udp.local

which is the advertising for the new instance name, and shows the _CM PTR record here, as expected.

Thanks for spec help


Preview 3 edits

Added migrate to the list of commands
Used docfx syntax for notes
Fixed heading levels in new articles
Made pseudo-variables in csproj consistent in dependencies
Remove references to project.json sections from deploying
Remove F# from dotnet new, since it's not supported
Added back missing --framework to dotnet test
Typos, grammar and other small fixes

cc: @blackdwarf, @mairaw

Issues I noticed, but did not fix:

There are some links with no targets in the Preview 3 articles. I assume this is a known issue.
Example csproj in Consuming per-project tools section  of the extensibility model article has empty <Version>. If this is intentional, I think it should be called out in the text. If it's a mistake, it should be fixed.
The csproj article (which is linked from other articles but not from the TOC) contains en dashes, which don't render correctly (some kind of encoding issue?).

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/core/preview3/deploying/index.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/csproj.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/dependencies.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/dotnet-build.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/dotnet-new.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/dotnet-nuget-delete.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/dotnet-restore.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/dotnet-test.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/extensibility.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/index.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/layering.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tutorials/using-with-xplat-cli-msbuild-folders.md
:white_check_mark:Succeeded
View
Details

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

@svick why second-level headings as top level?

@blackdwarf I changed it so that the main heading of an article is H1, the headings under that H2.
For example, the layering article currently has the main heading as H2 (---), and headings under that as H1 (#). Contrast that with the main Preview 3 article, which has the main heading as H1 (#) and headings under that as H2 (##).
In other words, I just changed the articles to a style that logically makes sense and is consistent with the rest of the docs.

It seems I also accidentally fixed the encoding issue with en dashes in csproj.

LGTM.

Thanks @svick! The changes look good to me too.


Rails 3.1 fixes

Please merge these changes (mostly openSUSE's Rails 3.1 fixes).
Alternatively, please add me<EMAIL_ADDRESS>to the gem owner, and I'll upload a new version of migration_test_helper.

Hi there! We’re doing some open source maintenance work and closing old PRs. If you would still like this PR to be merged in, please re-open it by 2-weeks-from-today. Thanks!


SBT 1.3 Coursier cannot resolve plugin in scripted test

steps
sbt version: 1.3.x (tested with 1.3.0 - 1.3.3)
problem
When following the approach to create a scripted test in https://www.scala-sbt.org/1.x/docs/Testing-sbt-plugins.html, by including the plugin.version in scriptedLaunchOpts, and importing the SBT plugin to test in the scripted test's project/plugins.sbt, when running SBT 1.3, Coursier fails to resolve the locally published SNAPSHOT version. When disabling Coursier with useCoursier := false, it is able to behave properly again.
expectation
SBT scripted test should disable Coursier by default, without having to explicitly do so with useCoursier := false.
notes
See https://github.com/daniel-shuy/liquibase-slick-codegen-sbt-plugin/blob/1.1.1/src/sbt-test/sbt-1.0/compile/project/plugins.sbt for an example. If useCoursier := false is removed, scripted test will fail.

@daniel-shuy Thanks for the report! I would say that the expectation is that it resolves locally published SNAPSHOTs without reverting back to Ivy.


Fixing the registration form.

Describe the bug
The registration form seems out of place and should be fixed .
To Reproduce
Steps to reproduce the behavior:

Go to Live events
Click on Register Now
See error

Expected behavior
The navbar must actually be in the center with a better ui that resonates with the website .
Screenshots

Desktop (please complete the following information):

Browser chrome

Also I want to add that there must be a navbar also on the registration page , I feel that gives a better navigation.


CB-10935: fix an issue of can not sync new contact into icloud which update new photo with ABPersonSetImageData()

fix an issue of can not sync new contact into icloud which update new photo with ABPersonSetImageData()

this is the bug report : 10935

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android Mac
Link
Link
Link

Can one of the admins verify this patch?

Ping @shazron - what do you think of this? Looks like we're forcing decoding base64 image data in a contact to help with an alleged iCloud sync issue.

This plugin is being deprecated. No more work will be done on this plugin by the Cordova development community. You can continue to use this plugin and it should work as-is in the future but any more arising issues will not be fixed by the Cordova community.


Publish 7.6-20220819003659+0000

Publish 7.6-20220819003659+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.


Update .npmignore

https://github.com/cerner/terra-core/issues/384
Update .npmignore for each package. Add target, tests, and reports.  This will prevent publishing excess files.

Resolved in #86.


Introduce threads xsd 2.0 which is using PersistentResourceDefinition…

… and new parsers
this makes it easier for inclusion by other subsystems that use parts from threads

Linux Build 1843 is now running using a merge of 3577771a352e0fb8920d92fba6b597f3cc2d75e8

Windows Build 1393 is now running using a merge of 3577771a352e0fb8920d92fba6b597f3cc2d75e8

Core - Full Integration Build 989 is now running using a merge of 3577771a352e0fb8920d92fba6b597f3cc2d75e8

Core - Full Integration Build 989 outcome was FAILURE using a merge of 3577771a352e0fb8920d92fba6b597f3cc2d75e8
Summary: Tests passed: 113, ignored: 55; exit code 1 (new) Build time: 0:02:30
Build problems:
Process exited with code 1

Windows Build 1393 outcome was SUCCESS using a merge of 3577771a352e0fb8920d92fba6b597f3cc2d75e8
Summary: Tests passed: 3109, ignored: 70 Build time: 0:20:15

Linux Build 1843 outcome was SUCCESS using a merge of 3577771a352e0fb8920d92fba6b597f3cc2d75e8
Summary: Tests passed: 3109, ignored: 70 Build time: 0:22:26


How to upload file with custom name to s3(using s3store)?

Question
Hi, my sincere apologies if this is a stupid question but I'm unable to find a way to upload files to s3 with a custom name and headers. I am using s3 store to directly upload files to my bucket.
I am able to read the original filename once the file is uploaded(below is the code), but how do I use this name while uploading? Do I need to rename the file once it is uploaded or is there a way to pass it before the upload starts? Any help would be really appreciated.
go func() { 		for { 			event := <-handler.CompleteUploads 			filename, filetype := event.Upload.MetaData["filename"], event.Upload.MetaData["filetype"] 			fmt.Println("Uploaded. File Details -->> ", filename, filetype) 		} 	}()
Setup details

Operating System: macOS
Used tusd data storage: AWS S3
Used tusd configuration: programmatic implementation
Used tus client library: tus-js-client

tusd does not have a native feature for this but you can rename the upload after it is completed. I added a FAQ entry for this: https://github.com/tus/tusd/blob/master/docs/faq.md#how-can-i-keep-the-original-filename-for-the-uploads

S3 doesn't support rename directly, meaning you will need to do a copy and delete, which can be extremely slow, sometimes taking as much time as the upload itself.

I know this may not be a satisfying answer for you, but if renames are to slow, you might have design your system without using the original file names. We are open to discuss alternative solutions but tusd currently does not offer such a feature.
Closing this issue since the original question was answered.

Sadly that probably won't do for the kind of system we have in place that will use tusd. So we will have to either cope with the slow renames, or I'll might just try and see what it will take to add support to use the passed name instead of random IDs to tusd.


Support adding & querying metadata on environments

Can be exposed by 'compose-tunnel-agent' which might worth changing to simply Preevy agent.
Such metadata can be:

Time of creation
Provider flags (size, region)
Git Context
Current services/tunnels (already implemented partly)
Plugins metadata

This data can be used by Preevy widget/dashboard

done


feature: most.create for nodejs style callbacks

Node has the below style of async API for their ecosystem. Seeing the most.create is going to be moved into its own project, can we get a simple/clean way to provide Node async functions to it to create a stream source? e.g. most.fromNodeCallback(myAsync)
function myAsync(val, cb) {
   const err = null;
   const result = "success";
   // do something async
   cb(err, result); // may be called once or multiple times
}

Also, I'd like to avoid needing another library (like bluebird) to wrap the functions into promises for most.

Here's a rough Node alternative to create- haven't tested it yet:
https://gist.github.com/jadbox/8fed38ae730e8fb6a909edb9f6deae0c

Hey @jadbox.  Thanks for posting the gist.  The direction we're taking now is to keep the most core package lean and focused on pure operations, and to make it easy for folks to publish a la carte packages for functionality like your fromNodeCallback and flatMapNode.
BTW, most.create is not going away, it will simply move to another package.  So, you'll still be able to use it.  So, I can think of a couple options:

You could publish those now using most.create (with most as a peerDep).  When the new package containing most.create is available, you could switch your package to use that

You could implement and publish those functions using most's Source and Sink architecture in a more efficient way than using create.  This may sound more intimidating, but it's actually quite simple.

Either way, join us in the gitter chat and we'd be happy to help!

@jadbox It could possibly look like this: https://gist.github.com/TylorS/00e37b84498c78f2da3bcd948495f2fd

I'm curious why the Src/Sink method would be faster than most.create?
Would native Node support be important enough to put into core?
@TylorS Thanks for the example!

Would native Node support be important enough to put into core?

My first instinct is that it should be a separate package, e.g. @most/node or something fairly obvious like that, but I'm open to discussing it.  Browser apps likely wouldn't need it 90% of the time, so being able to add it to a project a la carte is appealing.
Thoughts?

I'm curious why the Src/Sink method would be faster than most.create?

All most streams make the same guarantee: the function you pass to observe/forEach/reduce will not be called before observe/forEach/reduce returns.  There are really two options for making that guarantee in most.create, either 1) wait for the stack to clear before calling the producer function passed to most.create`, or 2) buffer events and propagate them after the stack clears.
Originally, it did 1, which proved to be confusing for users, so we switched to 2.
Since node functions already are async (well, they should be anyway!), by their very nature they would not propagate an event before the stack clears.  So, there is no need to a lot of the buffering gymnastics that most.create does ... it'd just be adding overhead for no reason.
There are a few other more minor factors.  For example, most.create creates 3 closures to pass to the producer function.  A node solution probably would only need 1.  Also, because most.create is a general purpose solution, it has to do more generalized error handling.  That means it uses try/catch in several places, which prevents the VM from optimizing several functions.
On the other hand, using Source/Sink directly is more "bare metal".  A node solution with Source/Sink would not need to do buffering, could create fewer closures, and could do error handling in a way that is more tailored to node style functions.

@briancavalier thanks for the clear explanation!
I'm torn if Node cb support should be in core. However, I can foresee Most becoming popular for Node due to the performance, and fromEvent is in core yet it is really used for browsers.

Hey @jadbox, sorry for not responding for a bit.  I think I like the idea of creating a separate package.
most.fromEvent is a bit of an outlier.  It was created before we had formed our current direction of keeping the core lean and adding platform or environment specific sources/adapters in separate packages.  Now we have @most/dom-event, which is a much nicer API for DOM events (somewhat ironically, most.fromEvent also supports node's EventEmitter!).
Would you be interested in helping out with a node-related package?

Hey @jadbox
I have been having the same issue as you ! and it seems like a general problem even in my workflow. I tried different techniques. One Major headache is input tracking.
https://github.com/partially-applied/mostify
I created this tiny module to take care of both the problems, hope you like it !

@jadbox Now that @partially-applied has created mostify, and @most/create is available as an a la carte package, I feel like there are good solutions out there for now.
So, I'll close this, but please feel free to continue discussion here.

Okay, thanks @briancavalier


Allow lightkurve's psf fitting priors to be input in image coordinates and/or RA, Dec

Currently one must input detector column and row, which is proving problematic for stars in crowded superstamp regions (e.g., M67) that go across channel boundaries where the detector coordinates are discontinuous. It would be a lot easier to use the local coordinate system of the TPF to specify star positions (though one would still use the detector coordinates to retrieve the PRF model).

Currently working on this now with AMC!

This is really cool! Which branch are you both working on?

We are discussing the possibility of adding an option to apply pos_corr offsets directly inside the phot.fit().  Currently the sole argument of phot.fit() is tpf_flux.  AMC and I suggest the following change:
Instead of taking tpf.flux as an argument, make it take in tpf.  This way, the fitting code will have access to tpf.poss_corr1 (and 2).
poss_corr would be used to shift the priors left-right and up-down, to maintain the desired prior window in the face of spacecraft-induced motion.  This feature can either be the default, or an opt-in keyword-arg.

Closing this issue because we do not currently have resources to develop PRF photometry features, unfortunately!


[Fix][TIR] Fix dtype issues for match_buffer and ramp node

This PR fixes dtype issues for

the strides parameter of match_buffer.

When stride is a tir var, it would become a string like "A_s0" in the printed script.
If the strides are int64 vars, when we parse the printed script, the dtype of the strides will be set to int32 by default. That causes dtype misalign and effects the structural_equal check.
We will cast the string stride to the dtype of shape (which is always a primexpr)

ramp node. If the dtypes of base and stride of a ramp node do not match, the dtype of stride will be casted to the dtype of base.

@tvm-bot rerun


Open all connections from internal networks

This pr opens all connections from internal networks.

+1
cc @gao-feng @laijs

Requires #202 for travis.

lgtm


LDAP: Added TLS support

A new option is available in .env file: LDAP_START_TLS=true|false
It is necessary to add the option TLS_CACERT <path_to_bundle.pem> in /etc/openldap/ldap.conf to make it work. Because, unfortunately, the LDAP options is simply ignored by (my) PHP (i don't know why). Maybe yours it will work?

Thanks for this @Body4 and sorry for the delayed response,
I followed this up with some further changes in af032f89932290b9f1217e80733447da6c039f55.
I found luck in my certificate being verified by importing the CA certificate into the BookStack host system's trusted certificate store.
This is now in master, to be part of the next feature release.


fix: Workflow dependency

fixes workflow dependency error
updates sleep time to wait for solution to catch up

/gcbrun


Updated GIS install instructions to use the latest versions of GIS libraries.

GEOS 3.4.2 reportedly does not work fully as expected. Bump GEOS recommended version to 3.6.2.
https://www.reddit.com/r/django/comments/8pim8i/how_do_i_request_an_edit_in_the_geodjango/

Could you also bump the versions of the other packages on this page?

Shouldn't this snippet written with a placeholder (like <latest version>) instead of hardcoding a version number?

GEOS 3.4.2 reportedly does not work fully as expected

What's the issue?

Shouldn't this snippet written with a placeholder (like ) instead of hardcoding a version number?

That would seem like a reasonable idea. How could the latest-version be inserted into the tutorial? E.g. we could keep a list of latest version for the libraries, and the documentation pre-build script would insert their values throughout the article(s) where relevant.

Something like First, download a Django-supported GEOS archive from the GEOS website... and then a litteral <version> string in the lines below? I don't think inserting a real version number is worth the trouble.

Well, I think it is done so people can copy/paste the commands. That makes it easier to get started.
Another idea would be to maintain a basic installation script, so users could just run the script instead of a series of commands.

In my opinion, building from source is not for the faint-hearted, but for relatively experienced devs, that's why I think they are able to make the version replacement themselves.

I'd be in favor of placeholders also.


Autoregressive HMMs (ARHMMs)

This is a placeholder for merging my code on AR-HMMs into main. I still have to:

[ ] Implement the m-step for the emissions parameters
[ ] Per the above point, decide whether to write a LinearRegression object to encapsulate the VAR parameters.
[ ] Make a demo, like this one.
[ ] Write test code.
[ ] Discuss with you all whether extensions of HMMs like this one should overwrite all the functions with functions of the same name but taking extra arguments, like history for the ARHMM. For example, the ARHMM has

    def filter(self, emissions, history):
        return hmm_filter(self.initial_probabilities,
                          self.transition_matrix,
                          self._conditional_logliks(emissions, history))

This will come up when we implement things like GLM-HMMs and IO-HMMs, which take inputs.

In lgssm.inference we have lgssm_filter(params, emissions, inputs=None). Can we use the same API for HMMs? For an AR HMM, the inputs could be the lagged emissions, so u[:,t] = y[:,t-L:t-1] - we rely on the model-specific conditional_logliks to know how to compute p(yt | zt, ut) for arbitrary yt, ut.

I would suggest keeping arhmm inside the hmm folder, since it's a minor variation on the other models.

R/e api, we could make them optional args in the HMM base class, but if we explicitly enumerate them as hmm.filter(self, emissions, history=None), then we may find ourselves adding more optional inputs down the road. E.g. for GLM-HMMs we might have to extend it to hmm.filter(self, emissions, history=None, inputs=None).
It might be cleaner (though admittedly more opaque) to have BaseHMM.filter(self, emissions, **kwargs) and then let inheriting classes add more keyword args as necessar.y

I'm closing this PR since we've taken it in parts. I'll keep the branch around for a while till we finish the AR-HMM integration.


enhancementsupport unnest subquery with group by and having clause

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Update to Laravel 7

I fixed to SymfonyUploadedFile parameters

Thank you --
Fixed a bug and added a support for Laravel 7 in v1.4.0
🎉 Finally a release for Laravel 7 support
⛑ Finally I've fixed problems with chunks (Dropzone/Resumable.js with parallel upload).
👍 Also I've found a solution how to get file data after upload for a Dropzone. Check WIKI.
If you created a packagist entry please mark it as deprecated (in favor of this package) or delete it - it can confuse people.
Thank you for your patience.


When editing meta-data on a page - the Page Summary editor should be disabled if the "Auto Generate summary" flag is enabled.

Behavior:  When editing the meta-data on a page, under “Page Summary”, the Rich Text or TinyMCE editor should not be enabled and allowed to have data put in there is the flag for “Auto Generate summary” is enabled.

Environment
This was reproduced on the following nightly build of version 8.1.1

When testing with the following nightly build of 8.1.1 (see screenshot), I am getting errors in the java console related to the auto summary when I view Meta-Data.

When I put the page in Edit view - I see that the Rich Text editor is not there (which is good), but then the java errors appear.

When I hit save, I get the java console errors below and my server hung:

The jetty console is showing the following:
10:02:24,021 ERROR [PSSerializerUtils] Unable to load XML file.  Check for syntax problems. Error: null C:javax.xml.bind.helpers.AbstractUnmarshallerImpl:L:335 Cause:Reference is not allowed in prolog. C:com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper:L:203, Data: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RegionBranches>
<regionWidgetAssociations/>
<regions/>
</RegionBranches>
10:02:24,021 ERROR [PSAssemblerBase] Problem during assembly: Error: The validated object is null C:org.apache.commons.lang.Validate:L:222
10:03:27,196 INFO  [Aging Agent] Polling aging action at: Wed Aug 10 10:03:27 EDT 2022...

I retested this on the following nightly build of 8.1.1:

I am seeing a bit of a "glitch" which I also showed to Nate.  When I first open the "Edit Meta-data", I see the Rich Text editor for a moment, then disappears with the "Auto generate Summary" flag on.

can no longer see the page summary editor when the auto generated is enabled


Be able to hide the limits

Add a boolean-option so the limit-numbers can be displayed or not. Default value should be that they are displayed.

Added in 0.1.10


[Event Request] Codeunit 825 - Sales Post Invoice Events - OnBeforeTempDeferralHeaderInsert

Dear ALAppExtensions team,
Through this issue we would like to request event publisher OnBeforeTempDeferralHeaderInsert to be added to Codeunit 825 Sales Post Invoice Events with the following signature:
    [IntegrationEvent(false, false)]
    local procedure OnBeforeTempDeferralHeaderInsert(var TempDeferralHeader: Record "Deferral Header" temporary; DeferralHeader: Record "Deferral Header"; SalesLine: Record "Sales Line") //New
    begin
    end;

which would be called as follows from RunOnBeforeTempDeferralHeaderInsert:
    procedure RunOnBeforeTempDeferralHeaderInsert(var TempDeferralHeader: Record "Deferral Header" temporary; DeferralHeader: Record "Deferral Header"; SalesLine: Record "Sales Line") //New
    begin
        OnBeforeTempDeferralHeaderInsert(TempDeferralHeader, DeferralHeader, SalesLine);
    end;

which would be called as follows from Codeunit 815 - Sales Post Invoice CalcDeferralAmounts:
            TempDeferralHeader."Amount to Defer (LCY)" :=
              Round(
                CurrExchRate.ExchangeAmtFCYToLCY(
                  SalesHeader.GetUseDate(), SalesHeader."Currency Code",
                  TempDeferralHeader."Amount to Defer", SalesHeader."Currency Factor"));
            SalesPostInvoiceEvents.RunOnBeforeTempDeferralHeaderInsert(TempDeferralHeader, DeferralHeader, SalesLine); //New
            TempDeferralHeader.Insert();

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Document setting kernel arguments (kargs)

See:

https://github.com/containers/bootc/issues/255
https://github.com/containers/bootc/pull/401
https://github.com/containers/bootc/issues/570

Thanks!