Cannot resolve font by name in xelatex

Description
In unicode engines it should be possible to resolve fonts both by name (e.g. "TeX Gyre Termes") or by filename (e.g. "latinmodern-math.otf).
Unfortunately, this is broken for math fonts when using unicode-math in combination with xelatex.
In the template for providing a minimal test case you say "filename only please", but selection by "preferred family name" should work too, and works just fine with LuaLaTeX.
Add info or delete as appropriate:

Relevant for XeTeX
Issue tracker has been searched for similar issues? Yes

Minimal example demonstrating the issue
\documentclass{article}
\usepackage{fontspec}
\usepackage{unicode-math}
\setmainfont{TeX Gyre Termes}
\setmathfont{TeX Gyre Termes Math}
\begin{document}
$x$
\end{document}

In this case, when it comes to resolve TeX Gyre Termes Math, fontspec/unicode-math happily get something else (most likely TeX Gyre Termes), complaints that the font does not have the Math Script, and goes on typesetting math using Latin Modern Math.
However, on my system resolving TeX Gyre Termes Math is fine:
fc-match "TeX Gyre Termes Math"
texgyretermes-math.otf: "TeX Gyre Termes Math" "Regular"

The main issue here is not that the font is not found. It is that fontspec/unicode-math believe that they have found a font, yet getting the wrong one.
Unclear to me if the issue is with fontspec or unicode-math or xetex itself, though.
Further details

XeTeX finds fonts by symbolic name only for system fonts and not the one from the TeX distribution. You can set a link from the system fonts to the TeX fonts, e.g. for macOS in ~/Library/Fonts
ln -s /usr/local/texlive/current/texmf-dist/fonts/opentype/  ~/Library/Fonts/tl-opentype
with updating the font catalog with fc-cache -v -f it will find the font by symbolic name.
LuaTeX is different, because it handles the font search by an own font list for system and TeX fonts.


Cache - support for dependencies between cached items

In this PR request I would like to introduce cache dependencies.
The main purpose of cache dependencies is to create connection of various cache items with each other by specific identifiers. This functionality is intended to help with simple work with the invalidation of cache records that chain each other. The programmer does not have to remember all the names of the cache keys or the exact sequence of cache tags from which he wants to delete cached items. You just have to set dependencies and invalidate them. Cache dependencies are not supported in database cache store.
Cache dependencies usage example:
When storing records in the cache, you can set the dependencies like:

Cache::dependencies('my_cache_dependency')->set('test_item', 1);

Cache::tags(['taggroup_1', 'taggroup_2'])->dependencies('my_cache_dependency')->set('test_item', 1);

Also setting more dependencies for cached item is supported as well, you just have to set them as an array:
Cache::dependencies(['my_cache_dependency', 'another_cache_dependency'])->set('test_item', 1);

Or you can set dependencies as key, value pair: (this is useful if you want to make cache dependency by specific identifier/s from database etc.)
Cache::dependencies(['product' => [1]])->set('test_item', 1);

Cache::dependencies(['product' => [1, 2, 3, ..etc]])->set('test_item2’, 1);

If you want to invalidate (remove) all the records from the cache that have set specific dependency or dependencies, you can use one of the following codes:
Cache::dependencies('my_cache_dependency')->invalidate();
Cache::dependencies(['my_cache_dependency', 'another_cache_dependency'])->invalidate();
Cache::dependencies(['product' => [1]])->invalidate();

If you have any questions or suggestions, let me ask.
Thank you!

I'm not sure I can really take on maintenance of this atm. Maybe you could release a package for this? 🙂

Thanks for question. Yes, I can release it as a separate package but I thought, if there is a support for cache tags, it could be nice to have cache dependencies support as native as well.
Thanks for an answer. Have a nice day :)

I'm not sure I can really take on maintenance of this atm. Maybe you could release a package for this? 🙂

Thanks for question. Yes, I can release it as a separate package but I thought, if there is a support for cache tags, it could be nice to have cache dependencies support as native as well.
Thanks for an answer. Have a nice day :)


Add support for multiple environments

EDIT: A lot of the stuff in this top level is outdated - you can browse through the Environments milestone for a clearer picture :)
This issue was born out of RFC #220  👶
👉 Current Situation
wrangler publish --release only supports a single configuration. It would be very useful to compose a wrangler.toml that allows a project to be deloyed across multiple zones/accounts.
🙏 Proposed Usage
I think it would be good to keep this change backwards compatible with existing wrangler.toml configurations, and also allow a new configuration type. The following would all be valid wrangler.toml files.
👷 Current Configuration Style
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

This configuration would allow you to wrangler publish for zoneless and wrangler publish --release for zoned. This behavior should remain unchanged with this update.
👷 Add a staging environment to an existing configuration
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

[env.staging]
name = "staging-worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://staging.example.com"

This configuration would allow you to deploy zoneless with wrangler publish, wrangler publish --release would deploy the configuration at the top, and wrangler publish --release --env staging would deploy the worker to their staging environment.
👷Configuration that requires explicitly specifying environment
[env.prod]
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

[env.staging]
name = "staging-worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://staging.example.com"

This configuration would allow you to publish zoneless with wrangler publish, and wrangler publish --release would ask you to specify an environment to deploy to. You could run wrangler publish --release --env staging, wrangler publish --release --env prod, and wrangler publsh --release --env staging --env prod.
🤢 Problematic Configurations
⚠  Same name, different routes
[env.prod]
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

[env.staging]
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://staging.example.com"

These workers environments have the same script name. I think we should throw an error here asking them to change the name of one of their workers so they do not overwrite each other.
⚠  Same routes, different names
[env.prod]
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

[env.staging]
name = "staging-worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

This configuration is less of a problem because the API will already throw an error if you try to put a script with a different name on a duplicate route. (Right now the error message is kind of ugly though)
** EDIT 08-05-19 **
⚠  Different types
[env.prod]
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

[env.staging]
name = "staging-worker"
type = "javascript"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

This is a possible config and while it's a user error it kind of smells like poor design to allow this to be a valid config.

I think it could be error-prone to have prod and staging config in one file. Perhaps wrangler could allow specifying flag for alternative file like -f prod.toml and -f staging.toml

☝ open to considering this, it's probably much easier to implement and a cleaner API than what is currently being proposed. I'll speak with the team and gather thoughts. Thanks @prestonp 😄

Things I dislike:

having to pass --release and an env feels very weird. --release feels like a type of env
--env should accept lists. wrangler publish --env production staging should be valid.

Things I really want to see:

some sort of "dry run" functionality. complex publish commands could be an expensive footgun.
if we are keeping single file config, the current, non-namespaced config type should act as inheritable defaults for the new [env.<env name>] configs. i.e. you could do this

name = "worker"
type = "webpack"
account_id = "12345abcd"
private = true
# no zone_id, or anything else as default.
# if someone had those things, we could use them by default however.

[env.dev]
private = false

[env.staging]
# different zone
zone_id = "not_default"
route = "https://staging.otherzone.com"

[env.prod]
zone_id = "12345abcd"
route = "https://production.com"

[env.other_account]
account_id = "12345abcd"
zone_id = "12345abcd"
route = "https://other.property.com"

and if you don't specify something in one of the envs, it will get that field (if needed) from the "default" env

@xortive:

if we are keeping single file config, the current, non-namespaced config type should act as inheritable defaults for the new [env.] configs. i.e. you could do this

I keep going back and forth on this – I understand that having to specify type or account_id every time is annoying, but I also feel like having inherited defaults is an implicit and maybe confusing design choice – I think I might feel less confident about knowing what my config will be when I look in wrangler.toml. Do you think that's a valid concern?
Question around the "Configuration that requires explicitly specifying environment" section, @EverlastingBugstopper:
[env.prod]
name = "worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://example.com"

[env.staging]
name = "staging-worker"
type = "webpack"
zone_id = "12345abcd"
private = false
account_id = "12345abcd"
route = "https://staging.example.com"

This configuration would allow you to publish zoneless with wrangler publish, and wrangler publish --release would ask you to specify an environment to deploy to. You could run wrangler publish --release --env staging, wrangler publish --release --env prod, and wrangler publsh --release --env staging --env prod.

Wouldn't we want to support environments for zoneless deploys as well? wrangler publish --release --env $env makes sense to me, because there's no implicit/default environment defined. Why/how would wrangler publish work any differently? Does it assume one of the envs? IMO if you have the above TOML config, wrangler publish and wrangler publish --release should require an env, what do you think?

imho if you supply an env, it should be either a workers.dev deployment or a zoned deploy, not both, and we should move toward deprecating the --release flag, since that was sort of an "env" argument to begin with.

imho if you supply an env, it should be either a workers.dev deployment or a zoned deploy, not both, and we should move toward deprecating the --release flag, since that was sort of an "env" argument to begin with.

Agreed! I commented on #388 after this ticket and found myself thinking something similar.

While I agree that --release is less than ideal I think we want to keep this reverse compatible which is why I wrote things this way. That being said, I think maybe a good way to do this is to have --release be an alias for --env and if there is nothing passed to --env (or --release) then deploy to the unlabelled configuration, and then you could pass aliases to --env or --release. This would prevent the ugly --release --env staging API I proposed.

there are acceptable paths for deprecating flags that i think we should employ, such as retaining the --release flag and printing a deprecation warning to the console correcting to the updated use and indicating the release that will remove the flag entirely.
Beyond that, in the case of the updated usage, a default would be nice to have as well; that is, env.default should be used whenever an env is not passed. To preserve backward compatibility we can lump any top-level attributes into that env, and again print verbiage to the screen indicating what is happening. Docs and output can supplement best practices, such as using env.default as test/dev settings and passing specific envs for "prod" etc. This would, again, necessitate a multi-release deprecation path like the one described above.

based on earlier conversation around routes/release flag, we should also enforce that different environments have unique names to prevent confusion when updating your "staging" scripts changes what happens on your "prod" scripts because they have the same script name. I think that this feature will need considerable thought put into how we establish and communicate "best practices" to prevent surprises.

Love the idea of deprecation warnings and documenting best practices! In your example you have wrangler publish "falling back to default values" which happens to be a zoneless worker. What would that wrangler.toml look like? Currently wrangler publish will publish to zoneless worker, which makes sense, but your comment also said that any top-level attributes would be lumped into env.default. Top-level attributes today are only deployed on wrangler publish --release

here are the notes from our meeting; there's a couple of example tomls (old and new) and some proposed UX flows, BDD-style
old wrangler.toml
name = "worker"
type = "webpack"
zone_id = ""
private = false			// deprecate this
account_id = ""
route = ""

proposed new toml
[project]
type = "webpack"

[env.default]
name = "worker"
zone_id = ""
private = false			// deprecate this
account_id = ""
route = ""

[env.a]					// a zoned env deploy
name = "worker-a"
zone_id = ""
account_id = ""
route = ""
[[kv-namespaces]]
binding = "foo"
id = "stagingnamespaceid"

[env.workers-dot-dev]	// a workers.dev env deploy
name = "worker-a"
somethingforworkersdotdev = true
account_id = ""
[[kv-namespaces]]
binding = "foo"
id = "prodnamespaceid"

context: Wrangler 1.2.0
context: old toml
-> wrangler assumes top level values are "default"
-> wrangler behaves like it always did (--release goes to zone, none goes to subdomain)
-> wrangler outputs a warning, suggests action
context: new toml
context: no --env flag
-> wrangler looks for [env.default]
-> wrangler asserts that you can only target either a zoned route or workers.dev
context: with --env flag
-> wrangler looks for the correct env and throws if it is not found
-> wrangler throws if you also pass --release
example output for old toml -> --release flag:
$ wrangler publish --release
Warn: the release flag is deprecating, private key is deprecating, migrate peoples' tomls

next release
-> warn
-> update templates
-> update generated toml
-> update tutorials that reference release flag

For wrangler generate I'm assuming our wrangler.toml will look like this
[project]
type = "webpack"

[env.default]
name = "worker"
zone_id = ""
account_id = ""
route = ""

Looks like this was added, however when I publish my staging environment, it always overwrites my production environment. How to publish to the staging environment instead? I am using wrangler publish -e staging. I've defined both staging and production environments in my worker...


Add to_json, from_json; remove cast between json and varchar

Issue #3197

So, are we not going to have a CAST between json and varchar, or are we going to add it back later?

I'm not sure from_json is the right name. How about to_char?

Or maybe json_format?

We could have a flag to pretty print the JSON.

I agree that json_parse and json_format are better names. We can go with this if nothing better comes up. It's not a perfect name though because json_format feels counter-intuitive when one is trying to find the function that will turn his JSON document to VARCHAR. In addition, It does feel that parse and format is better than from and to because the two functions don't round trip.

Rebased and renamed

Had a couple comments and questions

Resolved comments and questions

Had one comment. Also the tests are failing. Otherwise, looks good


⚠ Bofrost.be has degraded performance

In 205b151, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1506 ms

Resolved: Bofrost.be performance has improved in 0499ae6 after 5 hours, 39 minutes.


Add Electron globalShortcut 'Alt+Shift+F' to toggle between 'Show/Hide Franz'

Description
Added shortcut Alt+Shift+F to toggle between 'Show/Hide Franz', which is a faster way then going to the System Bar Tray Icon and clicking it.
Motivation and Context
Feature request can be found here: #1218
How Has This Been Tested?
Tested on Ubuntu 18.10.
Verified with different applications that the global shortcut Alt+Shift+F doesn't collide with default shortcuts of the tested applications.
Types of changes

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

Checklist:

[x] My code follows the code style of this project (run $ yarn lint).

@mhatvan  Thanks for adding this.
We thought about that for quite some time in the past. If we are going to add a global shortcut it must me customizable for the user as a global listener has so much potential for conflicts.
If you are willing to tackle this then I'm more than happy to write down the specs.

hey @adlk,
I also had in mind that we could define default global shortcuts and then let the user customize them, in case they use an application shortcut that collides with it or just for fun, but decided against it since I didn't want to do UI changes without your knowledge.
Yes, I want to tackle this and it would be great to have mockups or some other visual reference of how you imagine it to look like for the users.

@adlk any updates from your side so that I can start working on customizable shortcuts?

@adlk is there still any interest from your side to implement this? Otherwise I will close the PR.


Ft basicapp springannotationprefix

We should replace "basicApplication" in spring annotation prefix. Current cases are:

@Component("basicApplicationAuthorityUtils")
@Service("basicApplicationNotificationUrlBuilderService")

Important note: needs to be tested.

I rewrite proposed code to remove useless .sh modification.


Code complete: proposals computed before document up-to-date

It seems that proposals can be computed before the document is up-to-date.
If you quickly type s y s ctrl-space, sometimes you get no suggestions, sometimes the suggestions that would be given if the line was blank (clone, etc.), and sometimes the correct suggestions (System, etc.).
(Imported from Bitbucket #19 reported by maxg on 2010-06-15)

Could not reproduce this issue. May have been resolved by a previous commit. Marked resolved unless issue comes up again.
(phy on 2010-06-28)


Status datapoints reported as unavailable / Restored after upgrade

After some recent updates (both HA and integration) all my OZW status sensors entities (boiler status, heating circuit 1 status, heating circuit 2 status, status DHW) become reported in Entities with status 'Restored' and internal entity state 'unavailable':
This entity is no longer being provided by the siemens_ozw672 integration. If the entity is no longer in use, delete it in settings.

Those are either sensors or binary sensors. I can still see the correct configuration in the core.config_entries in the .storage folder
            {
              "Id": "2002",
              "WriteAccess": "false",
              "OpLine": "3903",
              "Name": "Status DHW",
              "MenuItem": "Info",
              "DPDescr": {
                "Type": "Enumeration",
                "Name": "Status DHW",
                "Enums": [],
                "HAType": "sensor"
              }
            },
....
            {
              "Id": "2003",
              "WriteAccess": "false",
              "OpLine": "3907",
              "Name": "Status boiler",
              "MenuItem": "Info",
              "DPDescr": {
                "Type": "Enumeration",
                "Name": "Status boiler",
                "Enums": [
                  {
                    "Text": "---",
                    "Value": "0",
                    "IsCurrentValue": "false"
                  },
                  {
                    "Text": "SLT cut out",
                    "Value": "1",
                    "IsCurrentValue": "false"
                  },
                  {
                    "Text": "Fault",
                    "Value": "2",
                    "IsCurrentValue": "false"
                  },
                  {
                    "Text": "Switch cut out",
                    "Value": "3",
                    "IsCurrentValue": "false"
                  },
                  {
                    "Text": "Manual operation active",
                    "Value": "4",
                    "IsCurrentValue": "false"
                  },

.....
            {
              "Id": "1999",
              "WriteAccess": "false",
              "OpLine": "3904",
              "Name": "Status heating circuit 1",
              "MenuItem": "Info",
              "DPDescr": {
                "Type": "Enumeration",
                "Name": "Status heating circuit 1",
                "Enums": [
                  {
                    "Text": "---",
                    "Value": "0",
                    "IsCurrentValue": "false"
                  },
                  {
                    "Text": "SLT cut out",
                    "Value": "1",
                    "IsCurrentValue": "false"
                  },
                  {
....

Except integration and HA updates I did not performed any changes, especially to OZW integration. There are no warnings or errors in the log.
current HA version: 2024.3.3
siemens_ozw672 version: 0.2.9
Do you have any idea, what is wrong? Thank you.

I tried to downgrade to version 0.2.8 without success. But looking more closely I discovered, that while my original sensors are gone, new are provided by the integration. Please see both unavailable original sensors as well as new representing same datapoints bellow in the printscreen.

How this can happened?


Client/Server desync with a lot of Habitat stuff.

Fairy ring doors and trapdoors, when opened by other players or villagers, don't send an update to the other clients. IE: if I open a door on the server, the other players will see it as closed.
Something that happens that is much more apparent is using bone meal to grow fairy ring mushrooms. The mushrooms become a stem, letting me know a mushroom has grown, but the entire rest of the giant mushroom is invisible. The white outline in the second screenshot is me holding the FTB Ultimine hotkey showing the rest of the stem blocks in the giant mushroom. The only way I've been able to see the rest of the tree is by re-logging onto the server or leaving the area entirely and coming back.

Thank you for reporting, I will look into it soon.

I have looked into this and fairy ring doors and trapdoors use the vanilla Door and Trapdoor classes, so they should function the same.
The mushroom growing code also sets blocks the same way as it is done for vanilla mushroom growing so I'm not sure what might be causing this.


first ue4.24 support (virtual textures)

Hey, created a short fix for the ue4.24 virtual textures so that the viewer will be able to open fortnites files again

Sorry messed something up the VER_UE4_24 needs to get a new version number, old textures won't load with this anymore

I've made fixes for https://www.gildor.org/smf/index.php/topic,6846.0.html
It appears to be the same as in this PR, so I guess VirtualTexture feature appeared in UE4.23 rather than in UE4.24.

Possible, I just saw that it the game updated to UE 4.24 and with that the texture changes came in

I've verified many things just a few minutes ago. Fortnite DIDN'T use UE4.23 - it was on UE4.24 for months. This added a lot of mess with "real" UE4.23.

Ok, sorry then

Absolutely not a problem :)


Problem with the Geometric Brownian Motion Code from YT video

I get the following error:

TypeError                                 Traceback (most recent call last)
Cell In [19], line 1
----> 1 sample_paths = geometric_Brownian_motion (S_0, mu, sigma, T, dt, n)
Cell In [17], line 13, in geometric_Brownian_motion(S_0, mu, sigma, T, dt, n)
10     prices.append( prices[-1]np.exp((mu - .5(sigma2))dt + sigmanp.random.normal(0, np.sqrt(dt))))
11     time += dt
---> 13 if T (time) > 0:
14     prices.append(prices[-1]np.exp((mu - .5(sigma2))(T-time) + sigmanp.random.normal(0, np.sqrt(T-time))))
16 paths.append(prices)
TypeError: 'int' object is not callable
under the following code:
sample_paths = geometric_Brownian_motion (S_0, mu, sigma, T, dt, n)

Untitled1 - Jupyter Notebook.pdf

Hey there!  You need to specify "T - (time)" as you are decrementing the total number of discrete steps from the horizon T.
If you are interested in simulating GBM more concisely try using QFin!  QFin has a vectorized GeometricBrownianMotion class that you can pass those parameters to in the constructor to yield your sample paths.
If you have any more questions feel free to email me<EMAIL_ADDRESS>always happy to help!


Apply ACLs recursively - update documentation for child acl automatic deletion

[Enter feedback here]
Apply ACLs recursively, here it does not say that while propagating it from parent it will also delete all the acl that are present only on child blobs. This was a major issue for us where all existing acl got deleted for the child blob in adls gen 2 of us and created multiple job failures. And there is no way for easy recovery  from this state.
Can you please explicitly mention this in the documentation.

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

ID: 89b67548-fef4-4ad8-9605-ca5a16a4f1c1
Version Independent ID: 1be3381a-db1f-32e1-61e3-b4a0173ef4ce
Content: Storage Explorer: Set ACLs in Azure Data Lake Storage Gen2
Content Source: articles/storage/blobs/data-lake-storage-explorer-acl.md
Service: storage
Sub-service: data-lake-storage-gen2
GitHub Login: @jammArt
Microsoft Alias: jammart

@Abhishek-Dutta
Thanks for the feedback! We are currently investigating and will get back on this.

@Abhishek-Dutta Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thank you for your dedication to our documentation.
We sincerely apologize for the delayed response. After a careful review, we are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close

Thanks for your dedication to our documentation.
We sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary due to various constraints. Therefore, we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


Fix cchar definition on aarch64 macos (e.g. M1)

Fixes #18. Note that I'd also like to do something like this in test/test.rs, but it would only work on targets with libstd, which isn't something I know how to filter.
#[test]
fn check_vs_std() {
    let _: cty::c_char = 0 as std::os::raw::c_char;
    let _: cty::c_schar = 0 as std::os::raw::c_schar;
    let _: cty::c_uchar = 0 as std::os::raw::c_uchar;
    let _: cty::c_short = 0 as std::os::raw::c_short;
    let _: cty::c_ushort = 0 as std::os::raw::c_ushort;
    let _: cty::c_int = 0 as std::os::raw::c_int;
    let _: cty::c_uint = 0 as std::os::raw::c_uint;
    let _: cty::c_long = 0 as std::os::raw::c_long;
    let _: cty::c_ulong = 0 as std::os::raw::c_ulong;
    let _: cty::c_longlong = 0 as std::os::raw::c_longlong;
    let _: cty::c_ulonglong = 0 as std::os::raw::c_ulonglong;
}

ping

@japaric Any chance you can look at (or merge) this?
It's very easy to hit this issue, since c_char is (obviously) very widely used.


Fixes #1841 Start debugging says no python interpreter available

Fixes #1841 Start debugging says no python interpreter available
Handles "(default)" value correctly.
Also fixes handling of relative paths (e.g. "env\scripts\python.exe")
Fixes build issue on VS "15"

Creating a new PR - this one ended up against origin rather than my fork somehow.


Deconz 3.7+Conbee 2 stick sudden failure of the network

Hello, today all my ZigBee network stopped responding until I restarted image. That never happend before and I haven't done any changes in my network for maybe a week. Can somebody explain me what has happend and how to prevent it in the future?

07:02:50:707 device state timeout ignored in state 3
07:02:51:658 device state timeout ignored in state 3
07:02:52:614 device state timeout ignored in state 3
07:02:53:615 device state timeout ignored in state 3
07:02:54:613 device state timeout ignored in state 3
07:02:55:614 device state timeout (handled)
07:02:56:376 dev /dev/ttyAMA0
07:02:56:376 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:56:376 COM: --dev: /dev/ttyACM0 (ConBee II)
07:02:56:515 start reconnect to network
07:02:56:515 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
07:02:56:515 device state timeout ignored in state 2
07:02:56:597 0x00158D0003967782 error APSDE-DATA.confirm: 0xA7 on task
07:02:56:754 0x00158D0003CF03AD error APSDE-DATA.confirm: 0xA7 on task
07:02:57:152 dev /dev/ttyAMA0
07:02:57:152 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:57:152 COM: --dev: /dev/ttyACM0 (ConBee II)
07:02:57:183 dev /dev/ttyAMA0
07:02:57:183 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:57:183 COM: --dev: /dev/ttyACM0 (ConBee II)
07:02:58:162 dev /dev/ttyAMA0
07:02:58:162 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:58:162 COM: --dev: /dev/ttyACM0 (ConBee II)
07:02:58:191 dev /dev/ttyAMA0
07:02:58:191 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:58:191 COM: --dev: /dev/ttyACM0 (ConBee II)
07:02:59:156 dev /dev/ttyAMA0
07:02:59:156 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:59:156 COM: --dev: /dev/ttyACM0 (ConBee II)
07:02:59:186 dev /dev/ttyAMA0
07:02:59:186 COM: /dev/ttyACM0 / serialno: DE1995779
07:02:59:186 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:00:161 dev /dev/ttyAMA0
07:03:00:161 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:00:161 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:00:191 dev /dev/ttyAMA0
07:03:00:191 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:00:191 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:01:156 dev /dev/ttyAMA0
07:03:01:156 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:01:156 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:01:186 dev /dev/ttyAMA0
07:03:01:186 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:01:186 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:01:613 failed to reconnect to network try=1
07:03:02:156 dev /dev/ttyAMA0
07:03:02:156 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:02:156 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:02:186 dev /dev/ttyAMA0
07:03:02:186 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:02:186 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:03:165 dev /dev/ttyAMA0
07:03:03:165 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:03:165 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:03:196 dev /dev/ttyAMA0
07:03:03:196 COM: /dev/ttyACM0 / serialno: DE1995779
07:03:03:196 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:04:114 wait reconnect 15 seconds
07:03:04:158 dev /dev/ttyAMA0
07:03:04:158 COM: --dev: /dev/ttyACM0 (ConBee II)
07:03:05:114 wait reconnect 14 seconds
07:03:06:114 wait reconnect 13 seconds
07:03:06:615 failed to reconnect to network try=2
07:03:07:113 wait reconnect 12 seconds
07:03:08:114 wait reconnect 11 seconds
libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)

Seeing a similar issue after upgrading to 3.7 last night

Meantime, we have upgraded the add-on. Has the situation improved?

The situation, for me at least, was resolved with a restart. So not a show stopper. I'll see about upgrading tonight when everyone is asleep and will report back 👍

The situation, for me at least, was resolved with a restart. So not a show stopper. I'll see about upgrading tonight when everyone is asleep and will report back
The same for me. After restarting my server everything looks ok. And so after upgrading to the last version

Hmm, I have no issue with my ConbeII with 3.7

Upgrade from 3.7 to 3.9 went smoothly

Well, let's close it up for now!
Please let me know if it happens again 👍

Ok, so this issue has resurfaced. I got the exact same error after a snapshot create/restore when moving to a larger SD card. If I use the old SD card everything works but when I try the new card (with a restored full snapshot of the old card) I get this error. Rebooting does not solve the issue, nor restore the snapshot.
I am on HA 106.2 with DeCONZ addon 5.2.

After a reboot, I seem to be having the same issue - is this a problem with the network ?
10:21:47:877 failed to reconnect to network try=5 10:21:47:877 wait reconnect 11 seconds 10:21:48:876 wait reconnect 10 seconds 10:21:49:876 wait reconnect 9 seconds 10:21:50:876 wait reconnect 8 seconds 10:21:51:876 wait reconnect 7 seconds 10:21:52:876 failed to reconnect to network try=6 10:21:52:876 wait reconnect 6 seconds 10:21:53:876 wait reconnect 5 seconds 10:21:54:876 wait reconnect 4 seconds 10:21:55:876 wait reconnect 3 seconds 10:21:56:876 wait reconnect 2 seconds 10:21:57:876 failed to reconnect to network try=7 10:21:57:876 wait reconnect 1 seconds 10:21:58:198 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2154040-if00 (RaspBee) 10:21:58:234 device disconnected reason: 4, index: 0 10:21:58:876 wait reconnect 15 seconds 10:21:59:200 COM: --dev: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2154040-if00 (RaspBee)

Yes On the latest update I am now have this issue where it loses the network. extremely annoying.
deconz 5.3.4
Supervisor 225
HassOS 4.8
Any help would be appreciated


Fix info on UnconstrainedMeasurementException

This change fixes broken exception name and link to its documentation, as well as the reference to its namespace.

Docs Build status updates of commit 8ad4a72:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machines/qc-trace-simulator/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

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.

Updated base branch to master

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
AcrolinxScore
LowestCategoryScore
Issues
Scorecard
Processed

articles/machines/qc-trace-simulator/index.md
83
43
13
link
:white_check_mark:

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

Docs Build status updates of commit d951ba0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machines/qc-trace-simulator/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

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.


Complete Mac OS X Support

The equivalent of #690 is needed for osx-arm64
https://github.com/microsoft/clrmd/blob/a2c23aa4525a237d33e84fcfbfb5d02215797db4/src/Microsoft.Diagnostics.Runtime/src/Utilities/Platform/MacOSFunctions.cs#L27-L30
I am also not sure if we to do something special for universal binaries.
/cc @nxtn @leculver

It looks like the check for the cpu type can just be removed. The header magic field should be validated instead. @sdmaclea this code doesn't handle MachOFat binaries yet. Is that going to be important?
I can do this change in my current single-file work. It may be a while before the single-file changes are ready so if you want it sooner.

I was think clrmd needed MachOCpuArch & MachOCpuType too for completeness, but it is probably not required to unblock SOS.

MachOFat binaries yet. Is that going to be important?

Eventually it will be important.  We haven't decided whether we will support for .NET 6 yet though.  Current plan doesn't include universal binaries, but it may change in a month.

I'm using this issue to track completing Mac OS X support for all scenarios.  This will be my next major project in ClrMD aside from bugfixes.

@leculver Hi! I made changes for macOS support (both, x64 and ARM64) to be able to walk through the stack frames using EnumerateStackTrace(). Could you please review #915, #916, and #917?

@leculver Hi! Can you please release a new package with these changes?

Hello!  I plan to release a package next week that includes these changes and Mach-O coredump support.
Thanks!

@leculver Hi! Can you please release a new package with these changes?

New package is listed here:  https://www.nuget.org/packages/Microsoft.Diagnostics.Runtime/2.0.226401
Mach-O support is not yet implemented though.  =(

AFAIK we are complete with full OS-X support.  I'm closing this general issue.  If any problems are found please file a new, more specific issue with details.


rust-end-of-defun and rust-beginning-of-defun inconsistent around impl blocks

Similar to #227
If outside of an impl block, rust-end-of-defun will jump to the end of that block, but using rust-beginning-of-defun immediately after will stop at each nested function definition.
[cursor]impl MyStruct {
    fn f1() {
    }

    fn f2() {
    }

    fn f3() {
    }
}

Call rust-end-of-defun
Call rust-beginning-of-defun
impl MyStruct {
    fn f1() {
    }

    fn f2() {
    }

[cursor]    fn f3() {
    }
}

For consistent behavior, I would expect either the cursor is back where it started (if impl is considered a function block) or at the beginning of f1 (if it is not).

Can you test it with the tree-sitter support: https://github.com/rust-lang/rust-mode?tab=readme-ov-file#tree-sitter

If outside of an impl block, rust-end-of-defun will jump to the end of that block, but using rust-beginning-of-defun immediately after will stop at each nested function definition.

From my testing, treesit-end-of-defun jumps to the end of the block and using treesit-beginning-of-defun jumps to the start of the block.

For consistent behavior, I would expect either the cursor is back where it started

I believe this is fixed via the tree sitter support.

I'm closing this issue for now as I haven't been able to reproduce it recently using tree sitter and haven't heard back. Please feel free to reopen it if you encounter the issue again in the future.


helm list doesn't show the release

I tried to fix bunch of helm releases with pending-upgrade status by deleting the secret with last  release versions. After I re-run the CD for failed charts to restore the version.
As a result some of helm chart doesn't shown via helm list.
> helm ls -a --namespace default | grep my-release
>

Meantime I can see it with --filter flag:
helm ls --namespace default --filter my-release
NAME                          	NAMESPACE   	REVISION	UPDATED                              	STATUS  	CHART              	APP VERSION
my-release                      defaultx	7       	2022-01-07 10:41:24.357165136 +0000 UTC	deployed	my-release-0.1.117	0.1.117

I deleted all helm secrets and re-run CD again but the result the same. Secret appeared but list doesn't show the release.
kubectl get secrets --field-selector type=helm.sh/release.v1 | grep my-release
sh.helm.release.v1.my-release.v1                      helm.sh/release.v1   1      70m

Output of helm version:
CD version: 3.4.2
Local version 3.7.2
Output of kubectl version:
v1.23.1
Cloud Provider/Platform :
EKS

@iusergii Does it work when you use --A flags? In other words, with the following command: helm ls -A.

@hickeyma

helm ls -A
helm ls -A --namespace <ns>

Both don't show the release.

Ok, what's the output of these commands:

kubectl get secret -l owner=helm,name=my-release --all-namespaces
kubectl get secret -l owner=helm,,status=deployed,name=my-release --all-namespaces

This can be tricky to track down the exact cause. Do you mind trying to following to see if it sheds some light on the issue:

Confirm that kubectl and helm are pointing to the same cluster. Both use kubeconfig files for connecting to a cluster.
What version of Helm are you using? Just confirm that the binary you are running is Helm 3 and one of the latest releases.
Check that the storage backend that the Helm binary is using is Secrets. Check that HELM_DRIVER env var is not set to something else like configmap, sql etc.  You can also check by running helm env and see if is set there also.


TypeError when unmounting component

Hello,
after I unmount the component I get this error:
Uncaught (in promise) TypeError: a.value.map is not a function
    at vue3-select-component.js?v=5fca8a25:170:24
    at ReactiveEffect.fn (chunk-MC3FMTAG.js?v=5fca8a25:1241:13)
    at ReactiveEffect.run (chunk-MC3FMTAG.js?v=5fca8a25:427:19)
    at get value (chunk-MC3FMTAG.js?v=5fca8a25:1254:107)
    at Proxy.<anonymous> (vue3-select-component.js?v=5fca8a25:259:29)
    at renderComponentRoot (chunk-CRHHUGQT.js?v=5fca8a25:936:17)
    at ReactiveEffect.componentUpdateFn [as fn] (chunk-CRHHUGQT.js?v=5fca8a25:5156:26)
    at ReactiveEffect.run (chunk-MC3FMTAG.js?v=5fca8a25:427:19)
    at instance.update (chunk-CRHHUGQT.js?v=5fca8a25:5206:17)
    at updateComponent (chunk-CRHHUGQT.js?v=5fca8a25:5022:18)

It is also hard to debug since the package is already minified.

@foxhound87 can you share how are you unmounting the component please? Is it with the :is-multi="true" prop?
I believe it is related to the following lines: https://github.com/TotomInc/vue3-select-component/blob/master/src/Select.vue#L151-L153
Or it could also come from the .map used to set the :aria-label: https://github.com/TotomInc/vue3-select-component/blob/master/src/Select.vue#L381

Yes I'm using is-multi prop
the lines from the error are:
      if (l.isMulti)
        return a.value.map(
          (t) => l.options.find((p) => p.value === t)
        );

and
            "aria-label": y.value.length ? y.value.map(e.isMulti ? e.getMultiValueLabel : e.getOptionLabel).join(", ") : "",

I don't know how to share my code since is a little complex.
My options are not removed (they are computed)
I tested with a check on the options when doing the map:

Sorry I sent the message for mistake before finishing writing , I edited the post with more info.
Please I need this fix!

I'm not sure the fix belong to the component, as the v-model you are passing at the time of error is wrong.
When you're using the component with the :is-multi="true" mode, you should ensure the v-model type is an array even when no values are selected ([]).
In your case, I believe that the ref you are passing as a v-model to the component, is at some point undefined or null after a certain user-interaction, which is not valid for :is-multi="true" mode.
Could you please check and ensure the v-model passed is valid?
If possible, attach a screenshot or video with Vue devtools showing the vue3-select-component states/variables.
Note that there's also a custom v-model validator defined here that will throw an error on the user-side, if the v-model isn't an array when setting :is-multi="true".

Thank you for your support,
I think I will revert my changes, because before it was not happening.

I'm doing more debugging and I can't find a solution to this issue.
Right now the v-model is assigned in a watch and it's working.
If I move the assignment to onMounted it breaks.
The v-model is valid and this are the component props from the vue devtools:

From the debug:
      if (l.isMulti) <--- isMulti is true
        return a.value.map( <--- value is string instead array of string
          (t) => l.options.find((p) => p.value === t)
        );

With more testing could be fixed with:
if (l.isMulti && Array.isArray(a.value))

please let me know

@foxhound87 can you please try with the v0.5.2? I've pushed a fix to ensure this user-land error doesn't throw anymore (and break the component). It is now gracefully handled, and should return an empty array during the time the v-model type is invalid when used with isMulti.
Please see the merge-request details for more info.

Thank you for the release, it seems working now!


Port new doc infrastructure from gaffer 2.0 alpha 1 into Gaffer 1.

As part of Gaffer 2.0 work, a new doc structure & tech has been developed which will make it easier to document Gaffer better in future.
This is a non-breaking change, so port this into Gaffer 1 and release.

Closing as the Gaffer 1 README currently does point to the new v1docs, as added by https://github.com/gchq/Gaffer/issues/2565


fix signed/unsigned integer comparison

Change Description

The PR fixes the signed/unsigned integer comparison in the repo and add -Wsign-compare for clang build.
Change Type
Select ONE

[ ] Documentation

[ ] Stability bug fix

[x] Other

[ ] Other - special case

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

@huangminghuang Please fix the conflicts and then @b1bart will review and approve.

Superseded by #9681


Fixed opening vim

Fix for https://github.com/Bash-it/bash-it/issues/1030

This looks good - thanks! Before I merge this, could you please provide one or two sentences as to what this change is doing and why it's fixing the vim issue?

Of course. For example vim.aliases.bash provides alias v=/usr/bin/vim. Command complete -p /usr/bin/vim from alias-completion.plugin.bash returns empty string(as $new_completion). So to a tmpfile, which will be sourced on the end, goes " v"($alias_name), because:
new_completion="${new_completion%` *} $alias_name"
echo "$new_completion" >> "$tmp_file"

The v is alias for /usr/bin/vim so vim is invoked. But why vim was invoked in szymonpk I don't know. Maybe probably in the same way.

Got it, thanks for the explanation! You're basically checking whether that command has a valid completion defined, and don't include it in the new completion script if it does not have a completion - that makes sense.
Thanks for fixing this - nice!

Thanks @dracorp, this PR fixed $EDITOR issue for me as well.


Form not showing

Since Grav 1.1.16 the contact form is not shown. Tested also with clean install, but nothing.
Edit: Workaround -> set up a manual position

Thanks for reporting this issue. I will take a look.

Just tested on Grav 1.2.4 entirely through the Admin panel (Admin v1.4.2) and also not showing up for me on a fresh install on a new, otherwise empty page.

Also seeing no form on page using default template. Frontmatter is configured correctly.
Grav 1.2.4

Sorry, I haven't been available to fix this. If you anyone wants to put up a PR, that'd be great, otherwise, I'll try to keep this on my radar to get it dealt with.

Possible solution:
https://github.com/aradianoff/recaptchacontact/pull/38
Waiting for approval.

New release pushed. Please reopen if you still have problems. Thanks, @BartoszBartniczak .


URL signing has usability issues

This is several problems added together which make this library difficult to use for signing without looking at the source code.
In all of the examples, the f variable is a ListAPIResponse from the ListFilesAsync method.
Problem 1: Specifying both .Path and .Src does not result in an exception but is not valid.
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation().Width(400).Height(300))
    .Path(f.Url.Replace(urlEndPoint, "/"))
    .Src(f.Url)
    .Signed();
var url = imagekit.Generate();

This should result in an exception - behavior here is undefined as Path and Src could be pointing at different locations. This results in no exception and ignores the Src value since Path is checked first in code.
Problem 2: Specifying both .Src and .Signed does not result in an exception but is not valid.
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation().Width(400).Height(300))
    .Src(f.Url)
    .Signed();
var url = imagekit.Generate();

This does not result in a signed url and does not throw an exception. I think signing should be allowed when Src is used, but if there is some reason why this shouldn't be allowed, an exception should be thrown when these options are used together.
Problem 3: .Path cannot be set to relative path as it is for other functions
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation().Width(400).Height(300))
    .Path("/myfolder/image.jpg")
    .Signed();
var url = imagekit.Generate();

If the Path does not start with a /, an exception will be thrown because the Generate function treats this as a file path even though it should not. You can see some commented out code where the person who wrote this went back and forth:
//parsedURL = new Uri((string)options["urlEndpoint"] + (string)options["path"]);
parsedURL = new Uri((string)options["path"]);

parsedURL is set to file:///myfolder/image.jpg now and with the commented out code would have been https://ik.imagekit.io/myendpoint//myfolder/image.jpg (note the two slashes). I think this should do some checking and probably not create a new Uri out of the specified Path since it is not intended to be a URI.
Update: Actually it only works at all on unix-based systems. When running on Windows, .Path("/myfolder/image.jpg") creates UriFormatException.
Horrible workaround:
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation().Width(400).Height(300))
    .Path("https://localhost/myfolder/image.jpg")
    .Signed();
var url = imagekit.Generate();

All of the examples in the README set Path as a relative path rather than a full URI.
Problem 4: The signing function is named Generate
You can't change this without breaking backwards compatibility, but it should really be named something like GeneratedSignedUrl.
Problem 5: Transformation is required by SDK but not API
You cannot call Generate without having specified a Transformation.
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation())
    .Path(f.Url.Replace(urlEndPoint, "/"))
    .Signed();
var url = imagekit.Generate();

This code generates a url like this, which results in a 404: https://ik.imagekit.io/myendpoint/tr:/myfolder/image.jpg?ik-s=mysignature
This is a valid signed url with no transformation: https://ik.imagekit.io/myendpoint/myfolder/image.jpg?ik-s=mysignature
Problem 6: You can't sign a thumbnail URL
An example thumbnail URL is https://ik.imagekit.io/myendpoint/tr:n-media_library_thumbnail/myfolder/image.jpg. Note that it has a transformation of n-media_library_thumbnail specified.
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation().Width(100).Height(100))
    .Path(f.Thumbnail.Replace(urlEndPoint, "/"))
    .Signed();
var url = imagekit.Generate();

This code generates a url like https://ik.imagekit.io/myendpoint/tr:h-100,w-100/tr:n-media_library_thumbnail/myfolder/image.png?ik-s=mysignature which is not valid.
I would expect to be able to do something like .Url(new Transformation().Thumbnail())
I did find a workaround for this which took me a couple of hours of debugging through the library source code and reading the API docs:
var imagekit = new ServerImagekit(publicKey, privateKey, urlEndPoint)
    .Url(new Transformation().Add("n", "media_library_thumbnail"))
    .Path(f.Url.Replace(urlEndPoint, "/"))
    .Signed();
var url = imagekit.Generate();

Fixed in b86e70ec1f44a5996652fed6835240d6f5cd6a6a


Add rake task validate_hypertext_links

Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

Caching checked results turns out to be important.  Most hyperlinks are the same in every locale, so the cache of seen results greatly reduces the number of links that need to be checked.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #874   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          45     45
  Lines        1451   1451
=====================================
  Hits         1451   1451

Continue to review full report at Codecov.

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

Perhaps we should use HTTP HEAD, not GET, since we don't need the entire result (we just want to see if it's available).

Sure, but then you lose being able to do it in a one-liner. ;-(

I've updated, and yes, the one-liner is lost.  But not downloading big PDFs, just to see if something is there, is a waste of time.

Drat.  Some websites (including Apple's) are crazy; a GET returns the material, while HEAD returns 404.  That's not the way websites are supposed to work. But it looks like you have to retrieve documents to see if they exist. Grr.

This will fix #868.  I've already fixed a large number of broken links.  There were many more than I expected, so while this task was a pain, it was worth it.  A lot of potential problems for users have been proactively fixed, and we can quickly detect any new problems.

I've resolved the issues identified & plan to merge in a moment.


When I remove the google link for Lobster, the font don't change to Monospace

Challenge http://www.freecodecamp.com/challenges/waypoint-specify-how-fonts-should-degrade has an issue. Please describe how to reproduce it, and include links to screen shots if possible.

This works fine for me. Please show me your code. Are you doing this?
font-family: Lobster, Monospace;

+1
Am seeing the same issue, doesn't seem to matter where I comment the code.
Related screenshots:
http://i.imgur.com/BoxJ9Fs.png
http://i.imgur.com/rn4msf4.png


S04380110_Padded_grch37_with_M.bed not in reference archive

just found that S04380110_Padded_grch37_with_M.bed is not in the reference archive for testing.  Not that big of a deal because I will test with another bed file.
Also which .yaml file should I use to just do the variant caller steps.
Thank you

hmm...seems to be stopping after alignment.  I am new to snakemake so maybe I did not specify the output targets correctly?

@davidroberson Sorry about that - I'll add the S04380110_Padded_grch37_with_M.bed file to the reference genome. In the current version of the pipeline, it is used only for filtering germline variants, and will not change somatic variant or neoantigen prediction results.
How are you running snakemake, with what arguments? Are you trying to run the entire pipeline or just variant calling? If the latter, you can use https://github.com/openvax/neoantigen-vaccine-pipeline/blob/master/test/idh1_config_dna_only.yaml as a model.

Fixed now


Node, Yarn and Docker version check added in dev.sh file

fixed #168
@jayantbh Sir please check

Please add a screenshot or screen recording of the change in action in the PR description

@sahitya-chandra Please Add a video and some description to explain why this approach is good.
Great job 😄👍

You removed this line, and then in the last commit added it back in a different way, why? :D

I'd have literally approved and merged it without that change right now. :D

@jayantbh  Sir, I completly mised that


Update Bagger for potential bag of words use

@zupon, this may or may not be useful for your bag of bigrams task.


[9.101-x-prod] Update quarkus extensions to the right groupId: io.quarkus

Description of the change:
Motivation for the change:
Checklist

[X] Add or Modify a unit test for your change
[X] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Here is the PR from last time for reference

to answer myself, those Quarkus artifacts only exist on io.quarkus groupID, so I'm approving the PR


Issue with flow typings

Description
I've been using the library with flow and there seems to be issue with flow in using launchImageLibrary method
How to repeat issue and example
Simply used the method as follows:
ImagePicker.launchImageLibrary({ mediaType: 'photo' }, (response) => {
  ...
})

After running flow I notice the following error:
Error: src/services/image/index.js:40
 40:     ImagePicker.launchImageLibrary({ mediaType: 'photo' }, (response) => {
                                        ^^^^^^^^^^^^^^^^^^^^^^ object literal. This type is incompatible with the expected param type of
 65:   launchImageLibrary(callback: (response: Response) => any): void,
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^ function type. See: node_modules/react-native-image-picker/index.js.flow:65
  Callable property is incompatible:
     65:   launchImageLibrary(callback: (response: Response) => any): void,
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^ function type. Callable signature not found in. See: node_modules/react-native-image-picker/index.js.flow:65
     40:     ImagePicker.launchImageLibrary({ mediaType: 'photo' }, (response) => {
                                            ^^^^^^^^^^^^^^^^^^^^^^ object literal

Solution
After spending some time I went into the flow typings in index.js.flow and noticed the last default export has the following:
launchImageLibrary(callback: (response: Response) => any): void,

Also there seems to be multiple typings in the following block (not sure why):
declare export function showImagePicker(options: ?Options, callback: (response: Response) => any): void;
declare export function showImagePicker(callback: (response: Response) => any): void;

declare export function launchCamera(options: ?Options, callback: (response: Response) => any): void;
declare export function launchCamera(callback: (response: Response) => any): void;

declare export function launchImageLibrary(options: ?Options, callback: (response: Response) => any): void;
declare export function launchImageLibrary(callback: (response: Response) => any): void;

In order to resolve it I fixed the last default export typing to the following:
launchImageLibrary(options: ?Options, callback: (response: Response) => any): void,

This seems to fix the typings for me. Please let me know if this sounds good, I can send a PR.
Additional Information

React Native version: 0.52.0
Platform: both (NA)
Development Operating System: MacOS
Dev tools: NA

I have the same question.
Why don't you like the code below?
We should want to pass an options to launchImageLibrary.
  declare export default {
    showImagePicker(options: ?OptionsType, callback: (response: ResponseType) => any): void,
    showImagePicker(callback: (response: ResponseType) => any): void,

    launchCamera(options: ?OptionsType, callback: (response: ResponseType) => any): void,
    launchCamera(callback: (response: ResponseType) => any): void,

    launchImageLibrary(options: ?OptionsType, callback: (response: ResponseType) => any): void,
    launchImageLibrary(callback: (response: ResponseType) => any): void,
  };

This is still an issue


pidgin: fixes, updates

WIP: I noticed OfBorg for darwin is live again 😄

@GrahamcOfBorg build pidgin

☹
@GrahamcOfBorg build pidgin

🤔 let me merge the darwin fix now and do the update a little later.


Finish up

Separate commits:

Add GitHub Actions

Add current Freckle maintainers list

Implement actual add/remove

Exit non-zero if issues were found

Only if we didn't also --fix them
Behavior can be disabled with --exit-zero

Log warnings at WARNING

Adjust Freckle maintainers automatically on CI
As automatically as we can, anyway. Leave removals to be manually fixed.

On second thought, I'm going to consider this PR "for visibility" and merge away.


Problem with updated antismash rule - rule execution fails if no previous data present

Hi, I stumbled across a problem running the antismash rule -  execution fails (error message says one of the command resulted in non-zero return value in this new segment. If I roll back to the previous version of the antismash rule everything works smoothly. Strangly it also works, if I manually run the code block in the antismash environment...
https://github.com/NBChub/bgcflow/blame/21f9a65d586b2586e5c313bd1d6e810532c7ccf3/workflow/rules/antismash.smk#L72-L82

Another thing: all the logfiles are completely empty


'content-type' header included in GET requests

The https://www.eventbriteapi.com/v3/users/me/owned_events/ request doesn't respect the filter parameters (e.g., ?status=live) if the Content-Type header is set in the request. The Content-Type header should probably not be set for any GET requests, as GET requests with bodies are generally not supported or defined.

3.0.5 is live and on PyPI: https://pypi.python.org/pypi/eventbrite


Should references to markdown files point to the GitHub link or use relative paths?

Currently, README.md and other files point the GitHub.com link whenever referencing another markdown file that is part of this repository. Other repositories such as the WinUI repository have chosen to use relative links which would also allow browsing the files on your local machine without a browser opening.
Would this be a welcome change to the documentation or should we keep things as is?
If the former is the case, I would gladly contribute these changes.

Yes, I believe that change would be fine.

Relative would be great! Thank you for asking :smile:


JENKINS-61336 fix: make dashboard view plugin integration optional

Currently if you don't have the dashboard view plugin installed, the Rich Text Publisher will throw an error in the system log, and we don't want that to happen.
I'm replicating this fix from how this was fixed for a couple other plugins

JENKINS-20027 m2release-plugin - Fix
JENKINS-11398 cobertura-plugin - Fix

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Not sure how to test this, I'm hoping that by opening a PR some CI builds will run

Fixes: JENKINS-61336

This error doesn't look related to my changes 🤔

[2022-06-23T16:28:09.417Z] [ERROR] [ERROR] Some problems were encountered while processing the POMs:
[2022-06-23T16:28:09.417Z] [FATAL] Non-resolvable parent POM for org.jenkins-ci.plugins:rich-text-publisher-plugin:1.5-SNAPSHOT: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.5 from/to maven-default-http-blocker (http://<IP_ADDRESS>/): Blocked mirror for repositories: [repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/, default, releases+snapshots)] and 'parent.relativePath' points at wrong local POM @ line 5, column 13

Looks like the changes from https://github.com/jenkinsci/rich-text-publisher-plugin/pull/4 are needed first


Add Starboard feature

Summary

Add of a new feature #67
Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[x] This PR adds something new #67
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

New SQL Structure:
CREATE TABLE IF NOT EXISTS `table_starboard`
(
    `reference_message`   VARCHAR(100) NOT NULL,
    `display_message`     VARCHAR(100) NOT NULL,
    `star_count`          SMALLINT unsigned NOT NULL,
UNIQUE(`reference_message`)
)
ENGINE = InnoDB,
CHARACTER SET utf8mb4,
COLLATE utf8mb4_unicode_ci;


TREC News

Dataset Information:
Task from 2019-2021. Includes 2 subtasks: background linking and Wikification. This is a placeholder as I learn more about this task.
Links to Resources:

http://trec-news.org/

Dataset ID(s):
<propose dataset ID(s), and where they fit in the hierarchy>
Supported Entities

[ ] docs
[ ] queries
[ ] qrels
[ ] scoreddocs
[ ] docpairs

Additional comments/concerns/ideas/etc.
How will background linking and wikification fit into this framework?

wapo collection added for #51

Related: #90


MS Examples are crashing on MemoryStorage

I took the example source code - Example38_Pinecone, and pasted it into my simple WinForms application.
The made some changes. Specifically I delete the all the existing indexes and collection before I do any operations, like creating index, etc. The entire code is below:
`
public static async Task RunAsync()
{
using (Log.VerboseCall())
{
string apiKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";
string pineconeEnvironment = "us-west1-gcp-free";
            string openAiKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";

            PineconeMemoryStore memoryStore = new(pineconeEnvironment, apiKey);
            using var pinecone = new PineconeClient(pineconeEnvironment, apiKey);

            // Delete all existing indexes
            List<string> indexNames = new List<string>();
            IAsyncEnumerable<string> IAsyncEnum = pinecone.ListIndexesAsync();
            await foreach (var item in IAsyncEnum)
            {
                await pinecone.DeleteIndexAsync(item);
            }

            try
            {
                int i = 0;
                IAsyncEnumerable<string> collections = memoryStore.GetCollectionsAsync();
                await foreach (string collection in collections)
                {
                    collection.Remove(i);
                    Console.WriteLine(collection);
                    i++;
                }
            }
            catch(Exception ex)
            {
                Console.WriteLine(ex.Message);
            }

            try
            {
                // Create new index
                await pinecone.CreateIndexAsync(new("pinecone-index")
                {
                    Dimension = 1536,
                    PodType = PodType.S1X1,
                    Metric = IndexMetric.Cosine
                });
            }
            catch(Exception ex)
            {
                Console.WriteLine(ex.Message);
            }

            Task<PineconeIndex> idx = pinecone.DescribeIndexAsync("pinecone-index");
            idx.Wait();
            Console.WriteLine("idx.Status: {0}", idx.Status);

            IKernel kernel = Kernel.Builder
                .WithOpenAITextCompletionService("text-davinci-003", openAiKey)
                .WithOpenAITextEmbeddingGenerationService("text-embedding-ada-002", openAiKey)
                .WithMemoryStorage(memoryStore)
                .Build();

            Console.WriteLine("== Printing Collections in DB ==");

            IAsyncEnumerable<string> collections2 = memoryStore.GetCollectionsAsync();
            await foreach (string collection in collections2)
            {
                Console.WriteLine(collection);
            }

            Console.WriteLine("== Adding Memories ==");

            Dictionary<string, object> metadata = new()
            {
                { "type", "text" },
                { "tags", new List<string>() { "memory", "cats" } }
            };

            string additionalMetadata = System.Text.Json.JsonSerializer.Serialize(metadata);

            Log.Verbose("Calling CreateIndexAsync...");

            try
            {
               //  !!! THIS LINE THROWS EXCEPTION, ALWAYS, NO MATTER WHAT...!!!
                string key1 = await kernel.Memory.SaveInformationAsync(MemoryCollectionName, "british short hair", "cat1", null, additionalMetadata);
                string key2 = await kernel.Memory.SaveInformationAsync(MemoryCollectionName, "orange tabby", "cat2", null, additionalMetadata);
                string key3 = await kernel.Memory.SaveInformationAsync(MemoryCollectionName, "norwegian forest cat", "cat3", null, additionalMetadata);

                Console.WriteLine("== Retrieving Memories Through the Kernel ==");
                MemoryQueryResult lookup = await kernel.Memory.GetAsync(MemoryCollectionName, "cat1");
                Console.WriteLine(lookup != null ? lookup.Metadata.Text : "ERROR: memory not found");

                Console.WriteLine("== Retrieving Memories Directly From the Store ==");
                var memory1 = await memoryStore.GetAsync(MemoryCollectionName, key1);
                var memory2 = await memoryStore.GetAsync(MemoryCollectionName, key2);
                var memory3 = await memoryStore.GetAsync(MemoryCollectionName, key3);

                Console.WriteLine(memory1 != null ? memory1.Metadata.Text : "ERROR: memory not found");
                Console.WriteLine(memory2 != null ? memory2.Metadata.Text : "ERROR: memory not found");
                Console.WriteLine(memory3 != null ? memory3.Metadata.Text : "ERROR: memory not found");

                Console.WriteLine("== Similarity Searching Memories: My favorite color is orange ==");
                IAsyncEnumerable<MemoryQueryResult> searchResults = kernel.Memory.SearchAsync(MemoryCollectionName, "My favorite color is orange", 1, 0.8);

                await foreach (MemoryQueryResult item in searchResults)
                {
                    Console.WriteLine(item.Metadata.Text + " : " + item.Relevance);
                }
            }
            catch (Exception ex)
            {
                Log.Verbose(ex);
            }
        }
    }`

The indicated line with the comment above throws exception, no matter what... and this behavior is observed not only in this example but in QDRANT example as well: Example19_Qdrant. The same line throw exception. So, at this point it looks like a general problem... Am I the only one trying these examples?
Just to note that I did deployed the correct resource in Azure with correct model "text-embedding-ada-002". Any my Pinecone key and environment that I got from Pinecone are correct, as well as ApiKey of OpenAI.
Anything else maybe I need to do?
The exception is:
Microsoft.SemanticKernel.Connectors.Memory.Pinecone.PineconeMemoryException: 'Index creation is not supported within memory store. It should be created manually or using CreateIndexAsync. Ensure index state is Ready.'
But, I do create index in the code as shown below and it ran to completion. (idx.Status = RanToCompletion)
Screenshots
Stack Trace:
at Microsoft.SemanticKernel.Connectors.Memory.Pinecone.PineconeMemoryStore.d__2.MoveNext() in /home/vsts/work/1/s/semantic-kernel/dotnet/src/Connectors/Connectors.Memory.Pinecone/PineconeMemoryStore.cs:line 68
at Microsoft.SemanticKernel.Memory.SemanticTextMemory.d__3.MoveNext()
at GptModelTrainer.MainForm.d__21.MoveNext() in C:\Projects\GptModelTrainer\GptModelTrainer\MainForm.cs:line 376
Desktop (please complete the following information):

Windows 11
IDE: VS2022
NuGet Package Version: 0.15.230531.5-preview

I see also errors in some of these Memory samples.

It has been 2 weeks since I posted my bug report. Is there any update on the status? Had it been reproduced? resolved? being worked on?
I managed to successfully produce a tool that can answer questions about private data - but I had to do it using OpenAI Embeddings API in C# + Pinecone C# bindings + OpenAI Completions. However, my goal is to be able to achieve it with SK.
I think Microsoft need to hurry with SK as the open-source development with LangChain gains momentum (unfortunately in Python)

@dmytrostruk can you take a look please?

If you guys need me to share my screen and demo to you - I can do it.

The exception is: Microsoft.SemanticKernel.Connectors.Memory.Pinecone.PineconeMemoryException: 'Index creation is not supported within memory store. It should be created manually or using CreateIndexAsync. Ensure index state is Ready.'

@securigy The reason why you receive this exception on SaveInformationAsync method is because SemanticTextMemory logic checks whether collection exists and if not, it tries to create it. This flow works fine for other memory connectors, but not for Pinecone. That's because collection creation in Pinecone is asynchronous, meaning that when you receive HTTP response from Pinecone API after collection creation request, the creation process has been started on Pinecone side, but collection (i.e. index) is not provisioned yet, provisioning is in progress. As mentioned in exception message, index state should be Ready before usage.
There are two ways how to resolve this problem:

You can use CreateIndexAsync in your code, but you have to add logic on your side to perform HTTP polling with your preferred strategy to get to the point, when index state on Pinecone side is Ready, so then you will be able to proceed with other operations.
You can pre-create your indexes manually on Pinecone portal and re-use it in the code when the state of your index creation will be Ready.

But, I do create index in the code as shown below and it ran to completion. (idx.Status = RanToCompletion)

Pinecone index state can have values: Initializing, ScalingUp, ScalingDown, Terminating, Ready.
In your case, status RanToCompletion it's not a state of Pinecone index creation, it's a status of your Task (documentation: https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.taskstatus?view=net-7.0#fields).
You output status of Task, because in your example there is no await when calling DescribeIndexAsync method, and you are working with Task. You can either add await or get index state details by using idx.Result.Status.State.
Task<PineconeIndex> idx = pinecone.DescribeIndexAsync("pinecone-index");
idx.Wait();
Console.WriteLine("idx.Status: {0}", idx.Status);

and this behavior is observed not only in this example but in QDRANT example as well: Example19_Qdrant

It would be really helpful if you can provide more details about exception you are receiving in Qdrant example, so we can investigate the problem.
Thanks a lot!

Dmytro, your post is really detailed and seems helpful - I will try it as soon as I can.
THANK YOU!
========
I wonder if you can provide a general guidance (not sure where else to ask):

I see now that the training of the models is possible now with SK and in conjunction with many other vector DBs. However, I also see that:
MS came out now with Azure Cognitive Service Vector Search:
https://github.com/Azure/cognitive-search-vector-pr
and it is not clear what vector DB is used there...
And then there is ADX, which is also quite new (Azure Data Explorer) that I also have problem to run its samples.

The bottom line is: my head is spinning from multitude of option for model training through Embeddings (due to vector DB search options). Where can I find a top-level guidance or comparison between all options?  and which can be used locally on my machine with or without complication of Docker...

@securigy In general, there is no specific recommendation what vector DB to use, because it all depends on what scenario you want to cover and what result you want to achieve. All options are different in terms of cost, performance and set of available features.
My recommendation would be to try each available option manually and see which one works best for your scenario. In repository we have an integration with multiple vector DBs including examples. Some of them can be used locally on your machine using Docker containers (e.g. Redis, Postgres, Qdrant, Chroma):
https://github.com/microsoft/semantic-kernel/tree/main/dotnet/src/Connectors
I would also suggest joining our Discord so you will be able to discuss this question with wider community:
https://aka.ms/SKDiscord
If you don't mind, I will close this issue, because your use-case has expected behavior due to limitations on Pinecone side. If you encounter any problems with Pinecone or any other functionality - feel free to open another issue, this will be very helpful.
Thank you!


missing click library on requirements

there's one library (click) missing on requirements.txt

Yes, you are right.


CLOUDP-187012: Create Dockerfile for AtlasCLI

Proposed changes
Jira ticket: CLOUDP-187012
Includes a Dockerfile to build a container running the CLI. Installation done with yum so that both the CLI and mongosh are included.
Setup
You can build the container by running the following command:
docker buildx build -t atlas --platform= .
Where  is either linux/amd64 or linux/arm64 dependant on the platform you are building for.
Commands can then be executed by running:
docker run atlas
Current issues:
Mongosh doesn't do anything at the moment except for creating a log directory after which it gets stuck, which might be mitigated in a follow up PR.

Would it be possible to have GitHub actions to build a container in order to ensure that docker file changes are correct.
Github action can run only when dockerfile is modified so it will run rarely. Asking @matt-condon as we had requested to remove it?

Sure that SGTM

Point 3 and 3.1 seems to be solved now.


Examine synchronized Block Usage

Possibly replace with reentrant locks to avoid pinning virtual threads.

This article of Java 21 Virtual Thread mentioned that:
A virtual thread cannot be unmounted during blocking operations when it is pinned to its carrier. A virtual thread is pinned in the following situations:

The virtual thread runs code inside a synchronized block or method

Do the usages of synchronized methods also need to be examined?

Yes, this includes those.

This needs to be fixed too. See the linked Boot issue.
https://github.com/spring-projects/spring-amqp/blob/c5489e291249d3da7b8c771b673441099ffcc84f/spring-rabbit/src/main/java/org/springframework/amqp/rabbit/listener/SimpleMessageListenerContainer.java#L174

Raised separate issue: https://github.com/spring-projects/spring-amqp/issues/2568 since that one is not so trivial to fix.
Therefore better to tackle it in its own narrowed scope.


Support release/debug build

Hi
Debug feature is really useful.
However looks like cargo currently does not support enabling/disabling features based on debug/release build mode. I'd like to have some workaround like some feature enabling transparent debug/release build.
I guess something like following would be enough:
if env::var("CARGO_FEATURE_AUTODEBUG").is_ok() {
        info!("CARGO_FEATURE_AUTODEBUG set");
        #[cfg(debug_assertions)]
        cmd.arg("--enable-debug");
    }

Is there a cargo issue open about this?

Sure.
See https://github.com/rust-lang/cargo/issues/2911

I might have misunderstood this issue then. I thought this was about allowing you to enable the debug feature if -C debug-assertions was enabled, but I see no mention of that there.

My use-case is to enable "debug" for jemallocator automatically when crate built in debug and/or dev mode. Unfortunately cargo does not allow enabling features based on debug mode. See https://github.com/rust-lang/cargo/issues/2911#issuecomment-234841039
So for now, I am stuck with manually changing Cargo.toml adding features = ["debug"] each time.
Debug assertions was chosen merely as an inspirational example.

cc @ehuss

An alternative to editing Cargo.toml is to run cargo build --features jemallocator/debug.  That can be set to an alias to make it easier to use.  It still is a bit awkward, though.
Instead of using an env var, you could use a feature ("autodebug"), and set --enable-debug based on one of the environment variables (DEBUG, OPT_LEVEL, PROFILE, whichever makes sense).

I don't think adding a cargo feature for this is a good idea.
At best I could have jemalloc-sys query whether an environment variable (e.g. JEMALLOC_SYS_AUTO_DEBUG=1 is set, and then handle things depending on DEBUGs value.
This means that you'd need to write JEMALLOC_SYS_AUTO_DEBUG=1 cargo build instead of cargo build --features jemallocator/debug, with the only advantage that you could export the JEMALLOC_SYS_AUTO_DEBUG variable to avoid it.

But to me this sounds like something that belongs in the ./cargo/config or the profiles of a crate.

@ehuss

Instead of using an env var, you could use a feature ("autodebug")
That was my original suggestion.

@gnzlbg

JEMALLOC_SYS_AUTO_DEBUG=1
That requires some external knowledge.
I'd like to avoid writing too much docs/howtos to build my project.

That requires some external knowledge.
I'd like to avoid writing too much docs/howtos to build my project.

I'm open to better suggestions.


Remove [ ] wrapping icons.

Is it possible to remove the wrapping [ ] around the icons in the NERDTree? I think it would look cleaner without them.

Heh I actually messed around with some test code to do this a while ago but it broke some big things
So yes this is something I would like to improve, either directly or a PR on NERDTree (but that would be difficult to get one in I think)

You can always fork nerd tree and have people point Vundle to your fork if people want to avoid the extra [] characters.

That is true but my test code was essentially a fork of a specific part of code that displays the brackets. I think this is the one I was messing with:
let g:NERDTreeFlagSet.renderToString = substitute(g:NERDTreeFlagSet.renderToString(), "[", "x", "")

I just realized something - wouldn't there be a way to use the vim conceal capabilities? You could add a concealment for each GLYPH such as: [GLYPH] => GLYPH.
You would probably need to have concealcursor=nvc for it to look good, and that's okay except it would conflict with the very small set of people that wish to use concealcursor for other purposes with a setting different than nvc. If they use nvc, it should be fine.

That is an interesting idea! Thanks I'll have to try it!

Here's what will work best:
(You have to make sure it only ever runs in the nerd tree syntax highlighting - not other panes).
" Replace any `[` or `]` with underscore.
" We'll hide the underscores anyways.
syntax match hideBracketsInNerdTree "[\]|\[]*" conceal cchar=_

" Must be completely hidden otherwise cursorline doesn't highlight the concealed bg color correctly.
set conceallevel=3
set concealcursor=nvic
This seems to work great - I just don't know where in the plugin is best to place this.
Also, when concealed, you'll probably want to add one extra space after the icon (can't be done with conceal and has to be done in the plugin) just so it doesn't look as cramped.

Looks like just placing all that above code in the NERDTreeWebDevIconsRefreshListener method works. It also doesn't seem to interfere with other buffers that have conceal since conceal settings seem to be per buffer.

:smile: Great sounds like you have probably the best solution. Do you want to submit a PR ? If not I will eventually get to making your changes myself (just might take a little longer that way)

See my note, it didn't work and I don't understand Vim plugin architecture well enough.

Ah okay no problem. What you have given me is good info to make an attempt, so stay tuned :+1:

:+1:

fixed with v0.4.0 release

:+1:


bulkdata task supports NULL DATETIME

Critical Changes
Changes

cumulusci/tasks/bulkdata.py

EpochType.process_result_value supports a None value
Updated test TestEpochType.test_process_result_value in `.../tests/test_bulkdata.py'

Issues Closed

@ davisagli , made the change
I'm getting weird behavior too.  Console shows two js resources were blocked from being loaded: Failed to find a valid digest in the 'integrity' attribute for resource:
-  https://github.githubassets.com/assets/frameworks-fd774724.js
-  https://github.githubassets.com/assets/github-bootstrap-6f10bc82.js


TST: skip test_kendalltau ppc64le

test_kendalltau() can hard crash on
ppc64le, circumventing the xfail, so
it is now marked with a skip to prevent
execution entirely on that platform;
this has been causing issues in our CI

Noted by Ralf here: https://github.com/scipy/scipy/pull/10972#issuecomment-545949804
But it has been happening too regularly to put up with for much longer I think.

Merged, thanks @tylerjereddy


Scala 3 Migration seems incompatible with Gradle

Current Behavior
When importing a Scala 3 library to a Scala 2 project it doesn't seem possible to compile with the way Gradle is built for Scala.
Gradle resolves the correct Scala library based on the classpath: https://github.com/gradle/gradle/blob/master/platforms/jvm/scala/src/main/java/org/gradle/api/tasks/ScalaRuntime.java#L100
However, when using the Scala 2's flag to read the Scala 3 source code I keep running into
could not find package scala.annotation.internal whilst reading annotation of package utilities (source)
Looking closer, we can find that package here in the Scala 3 library wrapper.
The solution should be simple: Scala 3 is now part of my library's api, I just need to set it as such, correct?
This results in Gradle picking up Scala 3 as the compiler for the entire project and Scala 2 includes a good deal of features that are not supported in Scala 3.
This creates a problem that I don't believe is possible to solve without changing how Gradle resolves the scala compiler / version. I tried other compiler flags as well like -Ytasty-no-annotations which seemed promising but I still had the same issue.
Expected Behavior
I would expect this to be possible in gradle as it is supported in scala: https://docs.scala-lang.org/scala3/guides/migration/compatibility-classpath.html#a-scala-213-module-can-depend-on-a-scala-3-artifact
Context (optional)
No response
Steps to Reproduce
I created the gradle sample project which does compile here:
https://github.com/dylanowen/gradle-scala-bug/commit/9c02820fda8a1b86a454b0db0efd67ba6a68bd43
You can find the changes necessary to create the first error about the missing annotations in this commit:
https://github.com/dylanowen/gradle-scala-bug/commit/a74d28cb08c87b5afab8b27c7bcdbfc8ca8503b9
You can find the changes where I show that setting scala 3 as part of my library's api switches us over to the Scala 3 compiler for the full project here: https://github.com/dylanowen/gradle-scala-bug/commit/3be65ffcd2b1703df7ca3b814e36225679d874fe
You can find my attempt at using -Ytasty-no-annotations here: https://github.com/dylanowen/gradle-scala-bug/commit/217c50b76a20d9cf5925d6a765b0b5ddb6dca42a
Gradle version
Gradle 8.7
Build scan URL (optional)
No response
Your Environment (optional)
No response

The issue is in the backlog of the relevant team and is prioritized by them.

If you are interested in contributing to Gradle, this issue is actionable and ready for contribution but might be challenging for first-time contributors.
See CONTRIBUTING.md for more information.

This seems to be a use case where auto-detection of the Scala version gets in the way. One solution could be to have a way to specify this from configuration, which would take precedence over auto-detection.

I was also wondering if it'd be possible to determine which scala libraries were direct vs transitive dependencies and choose based on that criteria?

Is it possible to add a jar to the compile classpath without declaring it in the dependencies block? This could be a viable workaround for now.

I believe the workaround is to change
implementation(project(":utilities"))
to
api(project(":utilities"))
https://github.com/gabrieljones/gradle-scala-bug/commit/5b3ee7f0fcf0a5d3243e6082cb7981b1e843a0ab
api makes all direct dependencies of project(":utilities") act as direct dependencies of app


NdrDevSupport::Daemon::Stoppable uses the Rails.logger

NdrDevSupport::Daemon::Stoppable uses the Rails.logger and therefore can't work outside the Rails environment. Should we add the following to Stoppable or add a Loggable concern?
attribute_write :logger

def logger
  @logger ||= defined?(Rails) ? Rails.logger : Logger.new(STDOUT)
end

cc @joshpencheon

Yep I think that's fine to add directly. I would say generally to use $stdout rather than STDOUT though, as the former can be redirected if needed.
I notice it also references Rails.env.test?; I think that whole line can just be deleted in favour of logging just to the logger.

Being able to log to somewhere other than the Rails log or $stdout is becoming more urgent.


Hotfix: compilation issue, target Android API level 31

Problem

Compilation issue descibed here: https://github.com/facebook/react-native/issues/35210
Warning from Android Play Store:

App not available to new users on Android versions higher than your target API level
App must target Android 12 (API level 31) or higher

Solution

Updated configuration in build.gradle.
Bump SDK version to 31.
Declare the android:exported in the activities that use intent filters.
Remove unused dependency that caused upgrade issue (react-native-background-fetch).

@Wayonb thanks, fixed.


CF Release

Bump Capital Framework to 3.4.1. No components were updated.
Review

@cfpb/front-end-team-admin

I am a bot. If I did something wrong, blame a human.

:+1:


The performance of adding elements in CommandBarFlyout.SecondaryCommands is poor

Describe the bug
I want to create context menus with CommandBarFlyout, but adding elements in SecondaryCommands takes much longer than adding elements in MenuFlyout.
In my environment, CommandBarFlyout.SecondaryCommands.Insert() takes 50ms to 70ms while MenuFlyout.Items.Insert() takes less than 5ms.
This makes it difficult to switch to CommandBarFlyout.
Steps to reproduce the bug

Create a CommandBarFlyout instance and  an AppBarButton instance.
Insert the AppBarButton to CommandBarFlyout.SecondaryCommands.
It takes long time.

Expected behavior
Adding elements in CommandBarFlyout.SecondaryCommands should have same performance of adding elements in MenuFlyout.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.2.5: 1.2.230313.1
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

I can reproduce this behavior as well

Yes, it takes a long time but fetching context menu from Windows takes more than that so this is not obviously,
But I also agree that CommandBarFlyout should be faster without questions.

We're getting many requests to make context flyout more swiftly fast.
I don't get why this has been unthouched at all over a year.
I know the team working on many prioritized things but this issue should be significantly noticeable in File Explorer too.


WIP 🐛 pkg/virtual/apiexport/authorizer/maximal_permission_policy: deny apibinding mutations

Summary
This forbids API binding mutations in the virtual API export service. Although these resources can be claimed, no maximum permission policy can be applied (becaus it is a system kcp resource) and thus a consumer can accidentally allow the service provider to bind anything in its workspace.
Related issue(s)
Fixes #2239

/close

closing as this solution is too naive to solve the problem. See https://github.com/kcp-dev/kcp/issues/2493 for details.


func DomainGetInfo("mydomain.com") don't work?

2018/09/05 05:24:53 strconv.ParseBool: parsing "NotAlloted": invalid syntax panic: strconv.ParseBool: parsing "NotAlloted": invalid syntax

Error raised in case of whois guard is not allowed. Namecheap devs made a typo on "NotAllowed".
Hotfix: in domain.go, find struct  Whoisguard and change option Enabled from bool to string.
It will compile and work, but I'm don't sure if this change does not break anything.

It's not a typo. It means that you didn't purchase Whoisguard for that domain. You might not be able to purchase it for some domains, but I've seen NotAlloted for domains where it is available but just not purchased yet.
Anyways, this is fixed in my PR.


Missing file: json_authenticated_controller_base

bundler: failed to load command: rackup (/usr/local/bin/rackup)
LoadError: cannot load such file -- /Users/firat/ci/app/features-json/json_authenticated_controller_base
  /Users/firat/ci/app/features-json/build_json_controller.rb:1:in `require_relative'
  /Users/firat/ci/app/features-json/build_json_controller.rb:1:in `<top (required)>'
  /Users/firat/ci/launch.rb:152:in `require_relative'
  /Users/firat/ci/launch.rb:152:in `register_available_controllers'
  /Users/firat/ci/launch.rb:36:in `take_off'
  /Users/firat/ci/config.ru:8:in `block in <main>'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/builder.rb:55:in `instance_eval'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/builder.rb:55:in `initialize'
  /Users/firat/ci/config.ru:in `new'
  /Users/firat/ci/config.ru:in `<main>'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/builder.rb:49:in `eval'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/builder.rb:49:in `new_from_string'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/builder.rb:40:in `parse_file'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/server.rb:319:in `build_app_and_options_from_config'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/server.rb:219:in `app'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/server.rb:354:in `wrapped_app'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/server.rb:283:in `start'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/lib/rack/server.rb:148:in `start'
  /usr/local/lib/ruby/gems/2.5.0/gems/rack-2.0.5/bin/rackup:4:in `<top (required)>'
  /usr/local/bin/rackup:23:in `load'
  /usr/local/bin/rackup:23:in `<top (required)>'
rake aborted!
Command failed with status (1): [bundle exec rackup --host <IP_ADDRESS> --port 8...]
/Users/firat/ci/Rakefile:6:in `block in <top (required)>'
/usr/local/lib/ruby/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/cli/exec.rb:74:in `load'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/cli/exec.rb:28:in `run'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/cli.rb:424:in `exec'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/cli.rb:27:in `dispatch'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/cli.rb:18:in `start'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/exe/bundle:30:in `block in <top (required)>'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/usr/local/lib/ruby/gems/2.5.0/gems/bundler-1.16.2/exe/bundle:22:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => prod
(See full trace by running task with --trace)

Thanks for reporting this @firatakandere, we just merged a fix into master, can you give it another try?


Adopt crate for test cases

My tests are leaning towards re-using the same "example" test case data structures. I could replace most of them with a few test functions that operate on many instances of that structure.
Rust has some creates which provide functionality for this. Try to adopt an  "explicit list of test case" crate. Ideally we could do this as well as adding property tests.

I've ported the existing solution tests to use test-crate, saving something on the order of 300 lines of code