Phrases in .dict hang the analyzer

Nearly empty .DICT file  with a few phrases causes analyzer to hang.
(No double space found there.)
@dehilsterlexis
phrase.dict file is as below:
############## PHRASES
dealer ' s s=dealer possessive=1
second - hand s=secondhand
second hand s=secondhand

@amnonma I have found the problem. It will be fixed soon. takes about 30 minutes for github to generate the new libraries so it should be within the hour.

@dehilsternexis
Thx David.  I've placed code in every pass to exitpass() if G("ERROR") is
set.
This is an easy way to test the "noop" analyzer, where the only things that
operate are the tokenizer, kb and dictionary.
This is good practice (and why every rules pass type should also have a
code section.
On Sat, Apr 29, 2023 at 4:21 PM David de Hilster @.***>
wrote:

@amnonma https://github.com/amnonma I have found the problem. It will
be fixed soon. takes about 30 minutes for github to generate the new
libraries so it should be within the hour.
—
Reply to this email directly, view it on GitHub
https://github.com/VisualText/nlp-engine/issues/412#issuecomment-1528894397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACFWQONKR6YODWDSR3PSPTDXDWO6VANCNFSM6AAAAAAXQP52HA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Amnon Meyers
CTO
Conceptual Systems LLC (California)
web: conceptualsystems.biz
mobile:<PHONE_NUMBER>
(landline:<PHONE_NUMBER>)


touchpad stopped working upgrading from 21.11 -> 22.05

Describe the bug
I have a brydge+ keyboard/trackpad as my keyboard mouse. When I upgraded to 22.05 the touchpad aspect of it stopped working.  it still showed up when I checked with libinput and the touchscreen on my laptop still worked as well.  I don't really know how to debug in wayland/gnome.
libinput output
Device:           Brydge 10.5 Go+ Mouse
Kernel:           /dev/input/event8
Group:            7
Seat:             seat0, default
Capabilities:     keyboard pointer
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Steps To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
touchpad works as a mouse
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

was able to get it working by pointing
hardware.bluetooth.package = pkgs.oldstable.bluezFull;

where oldstable is 21.11


Update docs with already existing mapping variables

There are three keymaps already present in the code that aren't included in the docs. I am currently using these mappings (g:NERDTreeMapPreview, g:NERDTreeMapPreviewSplit and g:NERDTreeMapPreviewVSplit) in my .vimrc and can confirm that they work correctly.
This pull requests updates the documentation to mention these mappings.

Good catch @asnr. Thanks for the update.


Assertion arguments were passed in incorrect order.

Describe the technical debt
Assertion arguments were passed in incorrect order.
file location: src/androidTest/java/de/dennisguse/opentracks/settings/PreferencesUtilsTest.java on lines (312, 315, 316, 313)
Proposed solution
Issue Fixed.
If applicable

le:
Technical information

Device: [Android Emulator]
OS: [e.g. AndroidOS 13]
OpenTracks version: [e.g. v3.2.4]

PR Created: #14


test(apps/prod/tekton/setup/triggers): upgrade triggers component to v0.21.0

We will upgrade it v0.24.0 later.

/approve


Fix heading spacing

There should typically be less space between headings and respective paragraph content, and more spacing between headings. Spacing on the website should match what's in the UI Kit
Example: spacing before and after H2s looks equal on Getting Started page, when it should be 32px before and 24px after
Notes from discussion with Adam:

When headers appear on content pages, then we should follow this rule of thumb: headings should be closer to the text they introduce than the text that precedes them (use at least 1.5 times the amount of whitespace above the heading as below it).

For this reason, we want whitespace between the top of a header and the bottom of the content that precedes it.
The amount of white space should be relative to the size of the header. For example, an H2 on a page will most likely indicate a new section of content. Therefore it warrants significant white space above it.

That rule above does not apply when there is no content above the header. For example, the H2 in the featured hero card does not need space above it

@kmbrlygl  Here what we currently have, we are using design tokens, it looks like you are right about H2, we need to fix it. Is there anything anything else would alarm you?

I think it looks good. Nothing glaring for me, the H2 fix should definitely improve the spacing throughout.
On a related note, do we have anything in the CSS that tames the line height?
I think line height affects the spacing we are adding in so that it's hard to get things pixel-perfect to the Figma. Here's an article on that. Not a priority though, it's for type refinement.

@kmbrlygl we have separate ticket for line heights, I am waiting for you to set them in stone. As soon as you do it in figma I will add line-height properties to headings.
But here are preliminary line-hight tokens for your reference:
  --font-lineheight-xs: 0.95;
  --font-lineheight-sm: 1.1;
  --font-lineheight-1: 1.25;
  --font-lineheight-2: 1.375;
  --font-lineheight-3: 1.5;
  --font-lineheight-4: 1.75;
  --font-lineheight-5: 2;

@kkoryaka Thank you. Apologies, I wasn't tagged back on that ticket so I check back on it.

Seeing the design tokens here is helpful.
Let's think about how to document that header spacing in Figma and/or the Visual Design Style Guide.

@adam-little @kmbrlygl  please confirm this is working as expected in https://1-0-1-rc-post-launch-fixes.pr.designsystem.webstandards.ca.gov/

@jaredwyee yes, this should be good to go. We still need to work out how to document spacing on the Visual Design style guide but this is implemented. Will create a separate ticket for documentation.

Thanks!


Implement miden::sat::faucet::mint and miden::sat::faucet::burn procedures.

There is an open question about how the current balance of an asset is tracked.  We could consider introducing the concept of "reserved" storage slots.  For example, for an fungible asset faucet we could set slot 255 to be the total issuance of the asset and as such we could use this to assert that we don't issue more than the maximum amount.  @bobbinth what are your thoughts?

For example, for an fungible asset faucet we could set slot 255 to be the total issuance of the asset and as such we could use this to assert that we don't issue more than the maximum amount.

Yes, this is how I was thinking about it as well. Specifically:

For fungible faucets, slot 255 would contain total balance of issues assets.
For non-fungible faucets, slot 255 would contain a root of a TSMT holding all issued non-fungible assets.
Transaction kernel would ensure that if we are in the context of a faucet account, the user would not be able to write to slot 255 manually (i.e., via account::set_item procedure).

Or, alternatively, we could make this slot inaccessible for all accounts.


akamaiDAPIdSystem doc Update

Documentation for a new userId submodule, akamaiDAPId

I had a document change requested for my Prebid.js PR so incorporated the same here as well

Hi @bretg , I have added a row to the bid adapter implementation table and updated the PR.

QQ: why isn't Akamai present on the prebid download page though this PR is merged?

ID adapters don't automatically show up on the download page. They have to be added in a PR.
Generally I don't do this for ID adapters -- they may have their own reasons for not wanting to be on the download page.
In this case, several people have asked me about it, so I'll go ahead and do it. Heads-up @amishra11j

Done in https://github.com/prebid/prebid.github.io/pull/3129


Better handling of canvas width

This PR implements both suggested solutions from #113:

The "canvas" is only rendered once we have an actual width. To achieve this I've lifted part of the <Mafs> component into an internal <MafsCanvas> component. Now all the hooks and render logic in <MafsCanvas> can safely assume the width is non-zero.
If the user passes an explicit pixel value (i.e. not "auto") to the width prop, that value will be used directly and the useResizeObserver is disabled. To disable the resize observer, I used the method suggested here: https://github.com/ZeeCoder/use-resize-observer#opting-out-of-or-delaying-resizeobserver-instantiation.

The code requires some cleaning up still:

[ ] Passing each prop from <Mafs> to <MafsCanvas> individually is annoying, but I think it is necessary in order for the docgen to pick up the default values. But maybe there is a better way?
[ ] There is a visible state that is enabled after the component is mounted, triggering a re-render to actually show the contents. I think this might not be necessary anymore, since we now always ensure the canvas has a size?

Fixes #113

Not sure why Vercel is complaining, but I'm merging this!


Macros

A slightly different design with less in the store and substitutions happening at render time.

This is looking good with me, merged with latest changes to master branch. Ready to go @willrogers


Simplify test for callable

Closures and other objects implementing __invoke are callable
Function method_exists accepts any 'object' parameter
Strong typing is coming in php7 for objects

This test can be completely removed if it is replaced by the callable typehint.
This requires PHP 5.4

It doesn't brake tests and still handles only callable objects and closures,
'Real' callable 'validation' only during getting element.

@GromNaN Pimple does not accept any callable here, to avoid issues when storing string parameters in case they match the name of a function (and so become callables)


Use accessible design for approve/deny buttons

In this PR

Add a destructiveSecondary variant to the <Button /> component.
Create a Storybook story for the <Button /> component.
Use the new variant in <ApproveDeny />, and simplify that component to always use the same design.

Closes #711

comparing these two, I rather prefer keeping the orange approval dialogue and warning symbol, but we should increase the brightness and shade of the color. Additionally, currently the padding creates dead black space on the right side in the approval dialogue. We should extend it to fill that space or center it.

The resizing is also broken.

#779 known for a while

Addressed @TalDerei 's comments, but I'm not able to reproduce the issue of the black bar at the right. I'm going to merge this for now and follow up with @TalDerei re: the black bar separately.


Question: AbstractPollingScheduler Delete From Source

The property ignoreDeletesFromSource in the AbstractPollingScheduler is used to remove properties that are deleting from the source that backs the Property provider. The current implementation has just one property store in memory which has the environment properties and also the properties that are dynamically loaded from a configuration source.
If the ignoreDeletesFromSource is set to false, the properties that are loaded as part of environment variables or other sources that are not from the dynamic configuration source will all be deleted when the configuration is installed. Can this be prevented somehow?

I am also interested in this fix.

V1 is deprecated and no longer maintained. V2 does not have this flag.


Clarification on singularity configuration to access files outside the working directory.

Snakemake version:
7.3.5
Describe the bug
I would love some clarification on  symlinks  and containerized rules. In my hands, it seems like running R scripts from containers on symlinked files or files outside the working directory fails. Any advice would be appreciated!
What I want to do
I want containerized rules to be able to access files outside the working directory, such as shared resource files link database indexes etc.  No issue running such rules with conda, but with singularity it seems like these files are not visible to the container.  This might be able to solved with playing with the systems singularity settings.
What I end up doing
I've been using locally-executed rule to copy such files to the working directory temporarily.  Symlinking doesn't seem to work.
Logs

Minimal example
I made a repo with an example workflow, script, inputs, and outputs: https://github.com/nickp60/snakemake-singularity-issue
What happens is the containerized rule relying on copied files succeeds, as does the rule run with conda.  However the containerized rules accessing a remote file or accessing a remote file symlinked to the working directory fail.
Additional context

I think you might need to provide a simpler example with some output. I tested this and I didn't get any errors using  singularity-ce version 3.8.1 and snakemake 6.7.0.

In general, singularity won't be able to resolve symlinks unless both the source and destination paths are included in the bind paths. For example:
ln -s /var/lib/dpkg/alternatives/rename ~/rename
singularity exec docker://bash ls -l ~/rename

will produce

(ie can't resolve the source filename)

@nickp60 Have you bound the location of these external files?  For example, I run snakemake from my home directory, which is automatically bound by snakemake + singularity (it binds $HOME), but I wanted it to also have access to my scratch user directory where my data and results are stored.
To do this, I ran: snakemake --use-singularity --use-conda --singularity-args "--bind /scratch/<myusername>/
This gives singularity read/write permissions to my scratch folder and solved my problems

Thanks @rdenham and @jksull .  What I've learned is that (a) linking works sometimes but is prone to fail on certain architectures found on HPC systems, and (b) the binding needs to be in place for all external files outside the home directory or the working directory.
I wish there was a CLI flag to auto-bind all remote files; this seems like a pretty common occurrence. But there are probably considerations I am unaware of...


Blog service is banned

General hosts (adware+malware) includes liveinternet.ru and www.liveinternet.ru.
Liveinternet is a Russian blog service, which exists since 2003.
Could you be so kind to white-list it?

Hi @sergeevabc, it appears that liveinternet.ru is flagged by

Badd-Boyz line 1924
someonewhocares.org line 10722
yoyo.org line 122

so therefore, no.
Maybe you could contact liveinternet.ru and ask them to stop being scumbags on the Internet?
Alternately you could clone this repo, add liveinternet.ru to a file named whitelist, and use python to build your own version.

@StevenBlack, the creator of Liveinternet, German Klimenko, is the Kremlin’s official Internet adviser since January 2016. Is that reference enough for you to doubt that mentioned scumlists made a mistake? Verify liveinternet.ru by yourself. It is just a blog service, a Livejournal alternative.

@sergeevabc liveinternet.ru is listed by three independent sources who study these things.
This repo is just an aggregation of many sources with options to customize and extend.
I can't help you with this; I trust the sources we use here.

Have you ever questioned how those so-called independent sources are populated? For example, the first one, Badd-Boyz, is curated by a single person, Mitchell Krog aka @mitchellkrogza and his policy is, I quote, “this list of hosts is compiled from server logs on my own servers”. Now ask yourself, what makes some South African photographer an expert on Russian blog services to list one as scumbag? Ridiculous.
The only reason I could think why liveinternet.ru were ever mistakenly listed is that it displays ads for sure, but uses dedicated sub domain for that purpose (ad.liveinternet.ru which I did not ask to remove) like Youtube's s.youtube.com.

@sergeevabc that's completely unwarranted.
Get lost.


Could this be set as a github template?

Is this repository ready to be used as a starting point? If yes, could you please set it up as a template? This way it would be easier to start working with this template.
Link for clearer definitions on what I mean:
https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository

Thanks for your comment! We have now set the repository as a GitHub template.


Frost Roc has ranged instead of melee strikes

frost roc's talon & beak attacks are incorrectly ranged attacks with range 15ft, instead of melee with reach 15ft

They were given the range trait instead of reach, fixing it


Deserialized into None when an error is expected.

I have a table that looks like this:
[beam]
polarization = "linear"
angle = 45.0
angle_units = "degrees"

and I deserialize it into these structures:
#[derive(Debug, Deserialize, Serialize)]
struct BeamDef {
    polarization: PolType,
    #[serde(flatten)]
    angle: Option<AngleDef>,
}

#[derive(Debug, Deserialize, Serialize)]
#[serde(rename_all = "lowercase")]
enum PolType {
    Linear,
    Circular,
    Elliptical,
}

#[derive(Debug, Deserialize, Serialize)]
#[serde(rename_all = "lowercase")]
enum AngleType {
    Degrees,
    Radians,
}

#[derive(Debug, Deserialize, Serialize)]
#[serde(deny_unknown_fields)]
struct AngleDef {
    angle: f64,
    #[serde(rename = "angle_units")]
    units: AngleType,
}

using toml::from_str.
When the table has the data that I expect in it (what's shown above) everything works great. However, if I replace angle: 45.0 with angle: "foo" i.e. replace the expected type (f64) with an unexpected type (String) I don't get an error. Instead, I get None for the Beam.angle field. I'm a little confused as to why the attempted String -> f64 conversion doesn't yell and scream at me. Any idea what's going on?

We don't currently have a way to determine whether an optional flattened struct is present in the input other than by attempting to deserialize it.
If there is some application-specific logic that determines whether an optional flattened struct is considered present, that would need to be implemented in a deserialize_with function:
use serde::{de, Deserialize, Deserializer};

#[derive(Deserialize, Debug)]
struct BeamDef {
    polarization: PolType,
    #[serde(flatten, deserialize_with = "decide_angle_def")]
    angle: Option<AngleDef>,
}

fn decide_angle_def<'de, D>(deserializer: D) -> Result<Option<AngleDef>, D::Error>
where
    D: Deserializer<'de>,
{
    let value = toml::Value::deserialize(deserializer)?;
    if value.get("angle").is_some() {
        AngleDef::deserialize(value).map(Some).map_err(de::Error::custom)
    } else {
        Ok(None)
    }
}

I don't think I follow. If the only way to tell that it's there (the flattened AngleDef struct) is to attempt to deserialize it, would it not attempt to deserialize the angle = "foo" field and then return an error since "foo" is not the correct type?

In order to treat an error from deserializing AngleDef as an error when deserializing BeamDef, you are presupposing that AngleDef is present in the input. Notice that an AngleDef that is not present would also give an error if you try to deserialize the AngleDef.
In any use of flatten on an Option there will be application-specific logic that decides whether to consider it as Some or None. That logic will be different in different cases.

I see, that makes sense. Thank you!


Silene Sprockets deprecation message

Overview
There is a PR already trying to solve the issue but seems like failing for CI.
Hope this PR can silence deprecation while satisfying different versions of Sprockets, adopting the tips shared by @schneems in this comment.
CI Build
The CI build failed but seems like master is already broken(?), and these 2 look like identical, at least this sprockets 2 were passed which failed on #73.

Related issue: https://github.com/sass/sassc-rails/issues/75

Working on it on #77 once i'm done you can rebase against master and your tests should pass.

@kinopyo Could you please rebase now?

rebased and CI passed 🎈 👏

Thanks!


Tests: use PHPUnit exception methods

Follow up to: #156
For upgrade changes in PHPUnit, see https://thephp.cc/news/2017/02/migrating-to-phpunit-6 by Sebastian Bergmann
Ready to merge

:party:

Thanks. Currently I have some personal issue and less time but I work hard to get back :)

Take your time to solve it - put yourself first.
No worries :)


app is not supported on macOS 13

Ah yeah it needs to be trusted first, usually a right click -> open does the trick.


converted bios to uefi showing as not uefi

Describe the bug
i have converted a few computers recently from BIOS to UEFI
but when running si.osInfo its still showing UEFI as false?
To Reproduce
Steps to reproduce the behavior
const si = require('systeminformation');
runcode = async () => {
    si.osInfo(data => {
        console.log(data);
    });
}
runcode()

Current Output
{
  platform: 'win32',
  distro: 'Microsoft Windows 10 Pro',
  release: '10.0.19041',
  codename: '',
  kernel: '10.0.19041',
  arch: 'x64',
  hostname: 'Unit1',
  fqdn: 'UNIT1.SERVER.COM',
  codepage: ' 850',
  logofile: 'windows',
  serial: '00330-80000-00000-AA847',
  build: '19041',
  servicepack: '0.0',
  uefi: false,
  hypervisor: false,
  remoteSession: false
}

Expected behavior
UEFI to be true?
Environment (please complete the following information):

systeminformation package version: 5.7.8
OS: [e.g. macOS] Windows 10 Pro
Hardware [e.g. MacBook Pro 13] Dell Optiplex 790

Additional context
findstr /C:"Detected boot environment" "%windir%\Panther\setupact.log" returns the following:
FINDSTR: Cannot open C:\windows\Panther\setupact.log
this is expected because it wasnt setup with UEFI so this file wont exist
echo %firmware_type% returns the following:
UEFI
this is returning correctly, so im not sure why its still returning false for UEFI?

found the issue! and fixed it for you! #562
it was carrying on and returning the last false, rather than waiting for the exec to finish and returning that instead

@si458 Version 5.7.12 just released. Can you check it on your side?

Hi @sebhildebrandt sorry for my delay been off work...
sadly ive tried that and NOPE it made no difference its still showing FALSE even tho it should be true!
but again my patch #562 fixes the issue and it returns true as expected no problems

@si458 thank you for your response. Checking my code I was sure, that there were more issues with missing returns. This is, why I made other changes ... need to check, why this still does not work ... sorry.

The issue is because it's returning resolve(false) before the exec of the %firmware% has finished...

So then the current line 400 (in my code here on github)  should be removed ...

@si458 ... sorry forgot to mention you in my answer ... maybe you can have a look on my suggestion in comment above ..

@sebhildebrandt sorry for delay, popped out the office haha!
if i indeed remove line 400 completely it does indeed return true now!
and ive tried it on 3 different computers and all return true!

@si458 Thank you so much!!!!! Version 5.7.13 just released.

@sebhildebrandt no no, thank you for such an amazing piece of open source software! ❤
i do have another weird issue with staticinfo taking 6 seconds to process before it carry ons?
even though the staticinfo is a promise so should carry on straight away, but ill open another issue for that...

@si458 yes please feel free to open another issue. Best regards.


acme: added nginx integration

Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[x] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Fits CONTRIBUTING.md.
[ ] Documentation
[ ] Code cleanup

Consider this WIP. This adds better Nginx integration for ACME. When Nginx was used with ACME, there's a chicken+egg problem: ACME needs Nginx to host files over HTTP, the Nginx configuration needs certificates to actually start. This problem (and solution) was covered in #12655. This PR makes sure Nginx always has certificates: if they are non-existant, it'll create self-signed ones. Once ACME created the proper certificates, Nginx is reloaded. This is based on the solution from @domenkozar.
Basically it adds the option security.acme.enableNginxIntegration. When enabled, it creates an one-shot service for each ACME cert that runs before Nginx. It creates a self-signed certificate if there is no certificate yet.
I'd like to know whether this PR is the right direction. Maybe we want a single service that creates self-signed certificates for all ACME certs, instead of separate services? Separate services have the advantage that they can be individually disabled. A single service will probably make the Nix expression less complex.
I also considered doing this in a separate module, but since I wanted security.acme.enableNginxIntegration I needed to add the option to acme.nix anyway. Let me know what is considered best-practice in this regard.
For apache/httpd support the same service can be reused. I haven't added this in this PR because I don't have a apache setup atm.

Can we try to remove the nginx specific parts on this?
I'd rename enableNginxIntegration to something like preliminarySelfsigned.
Remove the reload nginx command from PostStop and. In my opinion the nginx service should watch for file changes of the certificate and execute reload accordingly, this way it will also automatically pickup a change when the timer renews the certificate.
Will the initial ACME certificate-request be triggered automatically when nginx is started? Or will it wait until the timer is fired the first time?
The dependency could be made configurable so a user can pass in "nginx.service" or "httpd.service" which is then used for the fake-cert-service.(WantedBy,Before).

CC @globin (module maintainer)

@groxxda Indeed, having it independent of nginx would be nice. I've changed the PR to have preliminarySelfsigned. When enabled, the acme-selfsigned-certificates and acme-certificates targets can be used from any other service to specify when it needs to start.
Example configuration:
  security.acme.preliminarySelfsigned = true;
  systemd.targets."acme-selfsigned-certificates" = {
    before = [ "nginx.service" ];
    wantedBy = [ "nginx.service" ];
  };
  systemd.targets."acme-certificates" = {
    wantedBy = [ "nginx.service" ];
  };

Thanks for making it independent so quickly :+1:
I added a few more comments. Maybe it's also a good idea to create the output directory in preStart and then set systemd.service.PermissionsStartOnly and systemd.exec.{User,Group} just like the acme service does. This way openssl client will not be run as root.
I'm not sure if it's worth it though.
cc @fpletz

@groxxda I've integrated your suggestions including using PermissionsStartOnly. It seemed fitting as the original ACME services uses that as well.
The documentation now includes examples on how to use security.acme.preliminarySelfsigned with Nginx.
I still would like there to be some kind of simple way to make Nginx (or Apache) work without needing to copy example-configuration from the documentation though. This would require reloading Nginx when the files are changing (even though Nginx doesn't do this out-of-the-box). It might be a good idea to create systemd.path files that watch the certificates and reload Nginx, but that would be something that needs to be configured in the Nginx module. Probably outside the scope of this PR atm.

Looks mergeable to me :tada: for the documentation.
Out of the original scope of this PR but might be added: acme service will not work without routable network so it should really have After = network-online.target and Requires = network-online.target.
Using systemd.path is a good idea but should be added to nginx module itself and is out of scope of this PR

Alright, added nginx rules to make sure it is started after self-signed certificates are created. Removed the section from the docs where it instructs people to add this themselves.

Do we need an explicit configuration option? If for example nginx & acme are enabled, does the user have any reason to disable the bootstrap process? I can’t think of any.
Since you generalized it, maybe configure a few combinations that use it by default:
config = mkIf c.security.acme.enabled {
  security.acme.preliminarySelfSigned =
    mkIf (c.services.nginx.enabled || c.services.httpd.enabled) true;
}

@Profpatsch If it should be enabled by default, I'd rather go for default = true in mkOption. Enabling it based on nginx.enable and httpd.enable adds more complexity than it's worth. Having it set in mkOption is more obvious for people that look at the option documentation that way. Otherwise it says default = false, but is actually enabled in most cases.
I do agree that having this enabled by default would help out most people. There seem to be little to no negative consequences to creating the self-signed certificates first.
Let me know if anyone is against enabling this by default.

You are right. I haven’t reviewed the code, but +1 if it works. :P

Ok I think this is ready to be merged. To summarize, this PR:

Creates self-signed certificates before creating actual ACME certificates
Makes sure nginx is started after the self-signed certificates are created
Adds option security.acme.preliminarySelfsigned to turn off creating self-signed certificates

ping @fpletz

I've added some more explanation to the .nix file and squashed the commits into one for merging.
I've tested whether nginx starts when it's configured to use acme using: https://gist.github.com/bobvanderlinden/6c604ccb3f5a0127a117f269a674ae7a. It unfortunately cannot test for real ACME support.
My development server now has a similar addition. It seems to work nicely there.

I've deployed this on 16.03 with following example:
  services.nginx.httpConfig = ''
    server {
      server_name          kamdanes.si;
      listen               80;

      location /.well-known/acme-challenge {
        root /var/www/challenges;
      }

      location / {
        return 301 https://$host$request_uri;
      }

    }

    server {
      server_name kamdanes.si;
      listen 443 ssl;

      ssl_certificate     ${config.security.acme.directory}/kamdanes.si/fullchain.pem;
      ssl_certificate_key ${config.security.acme.directory}/kamdanes.si/key.pem;

      location / {
        root ${kamdanesFrontend};
        index index.html;
      }

      location /api/ {
        proxy_pass http://localhost:3000/;
        proxy_set_header Host $http_host;
        proxy_set_header REMOTE_ADDR $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      }
    }
  '';

  security.acme.certs."kamdanes.si" = {
    email =<EMAIL_ADDRESS>    user = "nginx";
    group = "nginx";
    webroot = "/var/www/challenges";
    postRun = "systemctl reload nginx.service";
  };

Notes:

it would be useful for nginx integration example to be self-contained. Copy/paste, replace domains, etc and it should work
webroot is not automatically mkdired, could also do that?
since preliminarySelfSigned is now on by default, last part of documentation addition is confusing, I would just remove it.
to use this on 16.03, replaceopenssl.bin with openssl

Great work!!

Also looks too to me. Thank you very much! :beers:
One thing: We've added support for acme to the nginx module which we will finally PR later today. I think the nginx service ordering hack shouldn't be in the acme module but rather dependent services like nginx should order themselves if they depend on it. We can merge it in the current state, though, and later remove it with the nginx PR.

Thanks for all the feedback.
@domenkozar The last part of the documentation is now removed/altered.
mkdir of webroot is somewhat outside the scope of this PR. For preliminary self-signed certificates the webroot isn't really needed. I can do a separate PR, because I think the code needs some cleanup/refactor anyway. Maybe after or combined with the PR of @fpletz?
@fpletz Sounds good. The ordering is related to both ACME and Nginx. I was thinking of having separate integration modules for nginx<->acme that can be enabled separately, but that might be overkill.
I'm interested in seeing the additional ACME - Nginx support PR!

@bobvanderlinden sure it's out of scope, but I'd like acme example to be self contained. I'm all for adding docs it has to be mkdir-ed, but I'd never expect that to be a requirement.

I see now this part is already documented at http://nixos.org/nixos/manual/index.html#module-security-acme - maybe we should just change behavior to chown to the acme user. But I agree it's out of scope.

I'm merging this for now as it works as documented. This is very close to being smooth :D Thank you!

Thanks!


Is there a Chebyshev analogue to Estrin's scheme?

We know that Clenshaw's algorithm is a degree-graded analogue of Horner's algorithm.  Is there a Chebyshev analogue of Estrin's scheme?
https://en.wikipedia.org/wiki/Estrin's_scheme
This question has little to do with ApproxFun.jl, except that if there is an analogue then the algorithm may be useful for it.

Estrin's scheme doesn't have the best reputation. Even with a pre-allocated array, it's not faster than Horner's method, though maybe the way I wrote it SIMD didn't kick in.
julia> using ApproxFun

julia> const ret_estrin = Vector{Float64}(2^20);

julia> function estrin(c::AbstractVector{Float64},x::Float64)
           n = length(c)
           if isempty(c)
               return zero(Float64)
           end
           @assert ispow2(n)

           for k=1:n
               ret_estrin[k] = c[k]
           end
           nn = n >> 1
           while nn > 1
               @simd for k = 1:nn
                   k2 = 2k
                   @inbounds ret_estrin[k] = muladd(x,ret_estrin[k2],ret_estrin[k2-1])
               end
               x = x*x
               nn >>= 1
           end
           muladd(x,ret_estrin[2],ret_estrin[1])
       end
estrin (generic function with 1 method)

julia> c = rand(2^13).*exp(-0.005collect(1:2^13)); x = 1.0;

julia> @time for j=1:1000_000 ApproxFun.horner(c,x) end
 17.508116 seconds (1000.00 k allocations: 15.259 MB, 0.02% gc time)

julia> @time for j=1:1000_000 estrin(c,x) end
 17.908365 seconds (1000.00 k allocations: 15.259 MB, 0.02% gc time)

Ok I added one more SIMD and it's a bit faster than Horner's method now.

I think this is less of an issue and more of a discussion, so is more appropriate for Julia-spectral group

Will Estrin (and Chebyshev analogues) be more appropriate with the introduction of multi-threading in v0.5? The experiments conducted by G. Reynolds in his M Sc thesis are across multiple processors, while multi-threading on the same core could give the parallel schemes an edge.

I think threading in 0.5 is listed as experimental, so we may want to wait to 0.6 unless there's a pressing need
Sent from my iPad

On 17 Sep. 2016, at 1:27 am, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Will Estrin (and Chebyshev analogues) be more appropriate with the introduction of multi-threading in v0.5? The experiments conducted by G. Reynolds in his M Sc thesis are across multiple processors, while multi-threading on the same core could give the parallel schemes an edge.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Refactor RED.history to add docs and types

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Refactor RED.history to add docs and types.

I added some notes to check.
There are some parts that I could not document because I did not understand the reason/logic.
var replaced by const or let.

Todo:

Check that I haven't broken anything in onDelete.
Finish the documentation.

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run npm run test to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

I have documented and typed as much as possible. I will document the rest as we resolve the todo points.


Workshop participant requests Phaster as part of PATRIC

PHASTER (PHAge Search Tool Enhanced Release) is a significant upgrade to the popular PHAST web server for the rapid identification and annotation of prophage sequences within bacterial genomes and plasmids.
There was some discussion of phage annotation in PATRIC during the workshop.  Seems like people would like this

Moving it to PATRIC4, as future enhancement to the annotation system.


correct value-latest of console and operate tag

Which problem does the PR fix?

Bump tags in value-latest of console and operate, as they are not correct (see HC version matrix)
It was reported internally in slack & we have a support ticket.
What's in this PR?

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[ ] In the repo's root dir, run make go.update-golden-only.
[ ] There is no other open pull request for the same update/change.
[ ] Tests for charts are added (if needed).
[ ] In-repo documentation are updated (if needed).

After opening the PR:

[ ] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[ ] Did all checks/tests pass in the PR?

Aaarrg, will install the tool-versions and push a new commit!

In my fork I tested that renovate creates PRs like this after this branch gets merged:
https://github.com/jessesimpson36/camunda-platform-helm/pull/45


also compile svg

the logo has recently changed to svg and needs to be compiled too
otherwise it wont be shown
bsc#1062878
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>

 Bug 1062878 - CaaS Platform logo missing


wayvnc not working since 8c36136

Hyprland Version
 System/Version info
Hyprland, built from branch HEAD at commit 8c3613632a6ccebf9fb797ec756ecfce99514eec dirty (renderer: nuke lastFrameDamage and rework finalDamage).
Date: Fri Feb 23 09:02:32 2024
Tag: v0.35.0-83-g8c361363

flags: (if any)

System Information:
System name: Linux
Node name: aorus
Release: 6.7.6-zen1-1-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:32:48 +0000

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1) (prog-if 00 [VGA controller])
10:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c3) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

Bug or Regression?
Regression
Description
screen from wayvnc server in Hyprland freezes and not updating
How to reproduce
Start a wayvnc server in Hyprland e.g. wayvnc -L debug <IP_ADDRESS> (or wayvnc -L debug :: for ipv6), and connect to it.
Mouse and keyboard inputs were fine, but display freezes at the first frame and is not updated as expected.
Crash reports, logs, images, videos
Bisect log:
git bisect start
# status: waiting for both good and bad commits
# bad: [21f7f32dc98521025cea76e530204ea64f2630f0] screencopy: avoid dangling client ptrs on client destroy
git bisect bad 21f7f32dc98521025cea76e530204ea64f2630f0
# status: waiting for good commit(s), bad commit known
# good: [ddf022d61c63fb36b4abba392682772690c06b5c] feat: Add css style gaps (#4723)
git bisect good ddf022d61c63fb36b4abba392682772690c06b5c
# bad: [ca59bd57393a386c9c6c9707ef6a9de4a9235fe1] opengl: check bottom/bg layers for required introspection
git bisect bad ca59bd57393a386c9c6c9707ef6a9de4a9235fe1
# good: [9a6956fe67801f6a22e4d77d5226dc2401fcc8c6] deps: update wlroots
git bisect good 9a6956fe67801f6a22e4d77d5226dc2401fcc8c6
# good: [c353b7c4f75e53af006bc2cf686b02c9a6495b60] renderer: minor fixes for introspection detection
git bisect good c353b7c4f75e53af006bc2cf686b02c9a6495b60
# good: [c1ef361e02e4c4a52fbc5dbd9e67b79e0afab4f3] renderer: fix logs
git bisect good c1ef361e02e4c4a52fbc5dbd9e67b79e0afab4f3
# bad: [f389f77015ebeee30a2527b8eb7488879dd626e0] core: Try to fix the exit hang (#4811)
git bisect bad f389f77015ebeee30a2527b8eb7488879dd626e0
# bad: [8c3613632a6ccebf9fb797ec756ecfce99514eec] renderer: nuke lastFrameDamage and rework finalDamage
git bisect bad 8c3613632a6ccebf9fb797ec756ecfce99514eec
# first bad commit: [8c3613632a6ccebf9fb797ec756ecfce99514eec] renderer: nuke lastFrameDamage and rework finalDamage

perhaps there's something wrong with 8c3613632a6ccebf9fb797ec756ecfce99514eec, or in progress?

patch.txt
try

patch.txt try

this patch works, wayvnc running normally again


Add config checker to validate the id is not a reserved key

Description
Because the entities (data nodes, tasks) are exposed as properties of parent entities using their config_ids, each config_id must be a valid python identifier, but it must also not be an existing attribute or property of the parent entity. For instance, if a data node config as "name" for id, there will be a conflict between the name property and the name datanode when calling scenario.name.
To avoid such conflicts add a checker for ScenarioConfig, TaskConfig, and DataNodeConfig to ensure the id is not a reserved keyword. The reserved keywords are all the attributes and properties of scenarios, tasks, data nodes, and parent classes.
Solution Proposed
Add a new checker, ReservedKeyWordChecker, which returns an error when the ID of a section is among a list of reserved keywords.
Acceptance Criteria

[ ] Ensure the new code is unit tested, and check that the code coverage is at least 90%.
[ ] Create related issues in taipy-doc for documentation and Release Notes.
[ ] Ensure any change is well documented in the Ref man (in the Config.configure_... methods) and the userman.

Code of Conduct

[x] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

For instance, if a data node config as "name" for id, there will be a conflict between the name property and the name datanode when calling scenario.name

This is already implemented.
The missing part is when the datanode config id overlaps with a scenario or task property.


PE: parse Rich headers

A PE rich header is a not-officially-documented header that the Microsoft linker adds between the DOS stub and the PE NT headers.
It has been widely reversed-engineered and documented. Several Python parsers are available.
That would be good that object implements such a parser as well.
It's on my todo-list to add this to object one day and upstream it here, unless someone wants to do so more quickly than I will.

This is really only useful for malware researchers?

If you don't want to add a parser for it to object, maybe object could the return rich headers as raw bytes and leave it up for interpretation by the user?

Well, I've written a quick and dirty implementation that kind of works. Give me a few days to polish it and I'll make a MR :-)


Our Team Section

Includes:

Executive Committee
Advisory Board
Community Co-ordinators

Should include the name, photo, designation of community coordinators.
Ref: http://kucc.ku.edu.np/community-coordinators/

WIP

@Amarmandal I will add the image assets tomorrow. Make sure to pull the upstream branch :D

@sabint017 sure.


Create organization publication(s)

In order to publish data from collection to client, create server-side publication(s) for organization collection.
Definition of done

[ ] Publication for "all" organizations exists.
[ ] Publication for single organization exists.

[ ] Single organization publication takes organization id as argument.

jykae interested

This issue was moved to Digipalvelutehdas/dipor-dashboard#4


Links in top-level pages (Getting Started, Modules etc.) throw 404

 Issue by execudev
Wednesday Jun 17, 2015 at 19:20 GMT
Originally opened as https://github.com/Wyamio/Wyam.Web/issues/1

Links in these pages are of the form: "wyam.io/getting-started****concepts" It looks like this is coming from _ChildPages.cshtml in the /Shared folder. Does this need to be fixed in the main Wyam repo?

<a href="/@PathHelper.RemoveExtension(childDoc.Metadata.Get<string>("FileRelative"))">@(childDoc.Metadata.Get<string>("Title", childDoc.Metadata.Get<string>("FileBase")))

 Comment by daveaglick
Wednesday Jun 17, 2015 at 19:30 GMT

Yikes! I hadn't noticed that - it looks like both Chrome (which I normally use) and IE convert the slash to one that works (and as a result the links work fine in those browsers). Which browser are you using?

 Comment by daveaglick
Wednesday Jun 17, 2015 at 20:10 GMT

Thanks for reporting this! I just fixed it, all that was needed was to add .Replace("\\", "/") to the link location code. It happened because the "FileRelative" metadata value (really, all the file metadata) is based on the file system (which uses forward slashes) and the links need back slashes. I'm hoping to add some additional helpers soon to make creating navigation and links easier and less error-prone.

 Comment by execudev
Thursday Jun 18, 2015 at 05:36 GMT

:thumbsup: I am using Firefox 38.0.5.


Use core and alloc crates for no_std compatibility

Partially Closes:  #1158
Description
In this PR I search for the use of std:: imports and change them to use core or alloc. The unsupported constructs are left to be imported from std and be fixed through other PRs for #1158.
A notable change in this PR is that we are now using BTreeMap instead of HashMap, and BTreeSet instead of HashSet. The reason is that the formers are not supported in the alloc crate, as they depends on random sources which are not available in no-std. I'm not sure if this change would break anything, so we might want to investigate further on this.

For contributor use:

[ ] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

What's the advantage of doing this rather than use something like no-std-compat?

What's the advantage of doing this rather than use something like no-std-compat?

core and alloc are officially maintained by Rust itself. So we can be confident that they will be supported in the long run.
The author of no-std-compat has sadly passed away, and the library is likely no longer maintained.
Std wrapper crates tend to get outdated quickly when new versions of the standard library is released. I have experienced similar issue in Haskell, where the base-noprelude package which wraps base got outdated when new version of GHC is released, and that caused a lot of pain to update / workaround all dependents to that wrapper package.
Polyfill std libraries do not necessarily follow the exact behavior of the original std constructs. This means we cannot easily refer back to the vanilla Rust std documentation. On the other hand core and alloc guarantee the same implementation as in std, and drops the unsupported constructs otherwise.
If we are using constructs unsupported by core and alloc such as std::io, it is likely that any polyfill crate would have custom implementation of the constructs. In such case we should use the polyfill crate directly whether in std or no-std mode, so that there is less maintenance burden of switching between two versions of the code.

The polyfill crate can still switch between std mode and polyfill mode behind the scene. But from the perspective of ibc-rs as the user of the library, that should be transparent.
Using the polyfill crate directly means that we are aware of its existence and always refer to the polyfill's documentation instead of the official Rust documentation. So in practice it is the same as us using a third party library instead of std for that functionality.

Very good points, thanks @soareschen! Let's go with that then!
Some follow-up questions:
a) Can also add a workflow to the CI to build the ibc crate in no-std mode, to ensure we don't accidentally introduce dependencies on std and friends?
b) I am wondering why we are doing this changes in the ibc-relayer, ibc-relayer-cli, ibc-telemetry and ibc-proto-compiler crates when those crates are not meant to be compiled with no-std?
c) Were the changes in the ibc-proto crate done manually? If so, can we automate that somehow? eg. via a prost flag/feature or within the proto-compiler crate as a post-processing step?

a) Can also add a workflow to the CI to build the ibc crate in no-std mode, to ensure we don't accidentally introduce dependencies on std and friends?

The current change do not support no-std just yet. There are still use of constructs from std such as std::error::Error. So we will need further PRs to fix that. The purpose of this PR is so that we can minimize the later changes required when no-std support is ready.

b) I am wondering why we are doing this changes in the ibc-relayer, ibc-relayer-cli, ibc-telemetry and ibc-proto-compiler crates when those crates are not meant to be compiled with no-std?

I think it is good to be consistent with the convention so that we do not need to switch between the conventions when developing on different crates. The use of core and alloc also makes it more clear of which features we are using are only supported in std, in case we want to support no-std in those crates later on.

c) Were the changes in the ibc-proto crate done manually? If so, can we automate that somehow? eg. via a prost flag/feature or within the proto-compiler crate as a post-processing step?

That's a good point! I have reverted the changes and created #1164 to address the issue separately.

@soareschen What do you think about defining our own prelude which re-exports commonly used types such as Vec, String, FromStr, ToString, etc?

What do you think about defining our own prelude which re-exports commonly used types such as Vec, String, FromStr, ToString, etc?

I can see that having such prelude would make it more convenient to use common constructs. However I would advise against building our own prelude library, as it can be tedious to keep the exports in sync with a proper "subset" of std. When there are inconsistencies, it can also cause confusion when developers are referring to the official Rust documentation.
What we could do instead is to create a minimal prelude that re-exports everything from core::prelude::v1 and alloc::prelude::v1. That way we are still delegating the management of what is being exported to core and alloc.
Note that the alloc prelude is currently nightly only. So I think it is fine to have custom re-exports for now that mirror what is available in alloc::prelude::v1. Looking at the definitions, it also seems like core::prelude::v1 is already made available in no_std. So the constructs from alloc::prelude::v1 are probably the only ones we need to add on top of it.

What we could do instead is to create a minimal prelude that re-exports everything from core::prelude::v1 and alloc::prelude::v1. That way we are still delegating the management of what is being exported to core and alloc.

Note that the alloc prelude is currently nightly only. So I think it is fine to have custom re-exports for now that mirror what is available in alloc::prelude::v1. Looking at the definitions, it also seems like core::prelude::v1 is already made available in no_std. So the constructs from alloc::prelude::v1 are probably the only ones we need to add on top of it.

Sounds good to me!

What is the status of this PR? I think we should move forward with it.

Are there any implications of using BTreeMap and BTreeSet, performance, or correctness, that we should be aware of?

I don't see any implications on correctness as I don't believe we every relied on the iteration order of elements of a HashMap or HashSet (which would be dumb anyway as it is non-deterministic).
As for performance, most operations on BTree-based data-structures have worse asymptotic complexity than their Hash-based counterparts, see the table below.
I don't believe that's an issue at the moment, as we do not maintain any data structure large enough for it to matter (especially as most operations in Hermes are IO-bound anyway).

— source

I have made a few more changes to this PR after merging with master:
#![no_std] with extern crate std
I have now activated #![no_std] in the ibc crate, with an extern crate std to explicitly re-import the std crate. This in effect remove the implicit imports from std::prelude, so that we do not accidentally use features that are implicitly exported by std prelude, such as println!.
Custom crate::prelude Crate
With #![no_std] activated, this means that std prelude constructs such as format!, vec!, String, and Vec are no longer implicitly imported in every Rust module. To compensate with this, I have added a private prelude crate that can be imported with use crate::prelude::* inside the ibc crate. The prelude essentially re-exports everything from core::prelude::v1 and alloc::prelude::v1, but excludes std-only prelude constructs such as println!.
Unfortunately, it seems like Rust still do not allow us to set a custom prelude inside a crate. (https://github.com/rust-lang/rfcs/pull/890) So it is necessary to call use crate::prelude::* in every individual modules that need to use prelude constructs. Nevertheless, this should hopefully make the developers' life easier as compared to having to import from modules such as alloc::format, alloc::string::String, etc everywhere.
Remaining std Uses
With the two changes above, there are only a few places remaining in the ibc crate that still uses std:

std::error::Error - This use can be removed once we upgrade to new version of tendermint-rs.
std::thread::sleep and std::printlnt - These are only used in tests, so we can probably conditionally allow std in #[cfg(test)].
std::time::SystemTime - This seems to be the only tricky bit left that is being used by the protobuf code generated by prost/tonic. We may want to investigate whether it is possible to generate no-std-compliant structs from prost that do not use SystemTime.

Thanks for the update @soareschen! This all sounds good to me.

std::time::SystemTime - This seems to be the only tricky bit left that is being used by the protobuf code generated by prost/tonic. We may want to investigate whether it is possible to generate no-std-compliant structs from prost that do not use SystemTime.

This seems to be the main remaining issue. If there is no support for this directly in prost/tonic, do you see a way of working around that?

This seems to be the main remaining issue. If there is no support for this directly in prost/tonic, do you see a way of working around that?

It seems like SystemTime is not directly used, rather as an intermediary conversion between tendermint::Time and prost_types::TimeStamp.
We will have to fix tendermint::Time, as it is actually a newtype wrapper for chrono::DateTime without providing access to the underlying value. (Reminder that if we are defining newtypes next time, please do expose the underlying values as public fields) Once that is done, we should be able to convert chrono::DateTime to the nanos and seconds values directly.

@romac shall we merge this?

Let's go, we just need an entry in the .changelog folder using unclog.

we just need an entry in the .changelog folder using unclog.

Done.


Fixes a destroy error in Sprites with a shared texture

If you have 2 sprites, with a shared texture, then try to destroy(true) both of them, the first one destroys correctly, but the second one will error because it's texture has already been destroyed. This PR adds a flag to fix that.

Actually looking at it now, it might be because I had a reference to a sprite that I called .destroy(true) on, but also had called .destroy(true) on it's parent container.
In any case, there's no harm in having this extra flag check IMO :)

I actually like having it error when things like that happen. Just like if you delete a memory address twice, it is UB.
We could add some // @if DEBUG checks in here and let the user know what they did know though.


Run aurad-status.py in systemd

I'm not sure but at first look it looks like aurad-status.py doesn't run in the background. I couldn't find any nohup or systemd command.

That's correct, on its own it's just a python script.
I recommend to use screen (which is preinstalled on many distros) to run it in the background.
A screen is like a container in which a program can run and continues to run even when you close the connection to your server/machine. You first need to start a screen with screen -S <NAME>, then run aurad-status inside there. You can detach from the screen by CTRL + A + D. When you want to re-attach to it, type screen -r <NAME>


Bump dependencies

Bump dependencies

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7067726369

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7067726369
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7068320959

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7068320959
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7068370237

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7068370237
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7068585551

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7068585551
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7068634713

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7068634713
Status: failure


How to predict a single target with multivariables?

Dear authors, I found that the implement of all linear models aligns the input channels and output channels. However, I need to predict a  single target varibale with multivariate inputs, and how should I modify the code? I think an extra nn.Linear module is required, and where should I insert? Thanks for your kind reply!

Hi, the hyperparameter "feature=MS" might meet your requirement. But since linear didn't consider the relation between variates, you can add a linear layer to merge the input information. You can choose to place the linear layer before or after the original linear layer based on validation performance. For example add a linear layer that is M->1 in lines 33-34 of Linear.py

Thanks for your response! I have tried your DLinear model on my task and achieved good results, though the relation between varaites were not considered. I will think about your solution and try to extract potential multivariate relations. Thanks again for your reply and your great contributions!

@cybisolated can you add a working example for multivariable input if possible? :)

@baniasbaabe Actually, as the author mentioned, taking NLinear as an example, I just add a linear module nn.Linear(M, target_size)  between line 86 and 87. This can extract feature relations to some extent but maybe not enough. I think a hidden layer nn.Linear(M, d_model) => nn.Linear(d_model, target_size) can be added to enhance the fitting ability of model.


unique symbol from the same source text position via multiple construction should be incompatible

Bug Report
🔎 Search Terms
unique symbol
🕗 Version & Regression Information
Tested on 4.7.0
⏯ Playground Link
Playground link with relevant code
💻 Code
declare let cond: boolean
function z() {
    const a = Symbol()
    return { a: a } as const
}
let x = z()
let y = z()

// Expected Error: Type 'typeof a' is not assignable to type 'typeof a'. Two different types with this name exist, but they are unrelated.
if (cond) {
    x = y
} else {
    y = x
}
export {}

🙁 Actual behavior
No type error
🙂 Expected behavior
Type 'typeof a' is not assignable to type 'typeof a'. Two different types with this name exist, but they are unrelated.

Duplicate of https://github.com/microsoft/TypeScript/issues/40106


Read all player-class data from configuration

Ensure that no dependencies have been created for rpg style games. Only generic pojo's are allowed to map with the config.

Done.


LTD-1453-serial-number

It would also be good to see a test showing that the second question gets skipped depending on the value selected.


possible bug in Frontend Code

In the most recent version in develop, with the new GUI, there is a possible hidden bug in the rendering of the frontend code.
AppHeaders is rendered multiple times, maybe due to some problem in handling the status in React. Same things happen for other parts of the code in other sections. To be investigated (first step, check output in the console log)

I get a blank page when I attempt to load greedybear

please add more information, screenshots, logs,etc otherwise we can't help

Hi, I see the issue with multiple rendering, but for reaching there I need to fix some warnings shown in the console, even if i try to update the type of spinner to border or grow,  the warnings will have no effect, could you help approach this issue ?

Hi dodaa, are you sure that is the correct spinner ? One I found a similar warning related to a component imported by the certego-ui dependency. I suggest to check if it's the spinner in the code or in the dependency

Okay, I'll recheck and get back to you.

import { Spinner } from "reactstrap";  I think  it's imported from reactstrap throughout the project, So, is it because of the nested usage of both the libraries ?

Hi dodaa, are you sure that is the correct spinner ? One I found a similar warning related to a component imported by the certego-ui dependency. I suggest to check if it's the spinner in the code or in the dependency

ok, in this case it's imported from reactastrap. Yes, reactstrap and the spinner is used directly from intelOwl, but also in the certego-ui and it's not up-to-date and it could be the reason for this error. Even if in the jsx file you are viewing there is not the certego-ui import, it could be in a component that use the component you are inspecting.


docs: update changelog

coverage: 94.092% (-1.2%) from 95.258%
when pulling 1cf1837484db5bac84d07a4f75db5c99eb38ac22 on release-v2.1.1
into db9f880038bbb96154869d072075443684e134c1 on main.


Enable to fetch pull requests by specifying assignee

@kachick
Do you think this pull request satisfy your suggestion? https://github.com/ohbarye/review-waiting-list-bot/issues/24
(Please check README)

Thank you... 😂
If we specify author A and assignee B, a PR created by A and assigned to B shows which state? 🤔

If we specify author A and assignee B, a PR created by A and assigned to B shows which state? 🤔

That's the cause of my headache.
If we follow the search page specification, those conditions are combined with AND. Then a command like@bot ls author:A assignee:B shows only case 1 below.

🆗  author:A and assignee:B
🆖  author:A and assignee:A
🆖  author:B and assignee:B
🆖  author:A and assignee is undefined

Does that make sense to you?

Let me close once since it's too conflicted.


Recursive Use of force_insert Causes Issues with References

Define a document that has ReferenceFields to other objects. Try to create a new instance of that Document, giving it references to existing objects. If that instance is saved with force_insert=True, it will try to force_insert all of its references as well which causes duplicate key errors. There needs to be a way to only force_insert the main instance.

@mankyd added cascade_kwargs to the dev branch, which allows you to override any set kwargs to save.  See the diff / testcase for more detail!


test/dnf-json: fail the test if dnf-json is not available

osbuild-dnf-json-tests requires dnf-json to be available in the current directory. This confused many people in the past. This commit adds a check if dnf-json is present in the current directory. If not, it prints a helpful message and fails the test immediately.
Another solution is to change the cwd in the test but that would make running the test locally a bit harder, so I chose a more conservative approach. Happy to dicuss though.

I'm not sure I like this approach, because we might forget adding such a check when we use rpmmd again somewhere else.
Could we just always run dnf-json from where it is installed, in /usr/libexec/dnf-json? We're hard-coding /usr paths in other places as well (albeit in cmd/, not internal/).

Not sure either. But I like that this doesn't break anyone's workflow, yet it gives you a meaningful error when you run it from a wrong directory.

Which workflow would we be breaking?
Alternatively, we could pass the libexec path to NewRPMMD, and default to the current working directory.

Which workflow would we be breaking?

Someone might want to run the test from the git checkout but that's probably a niche use-case.

Alternatively, we could pass the libexec path to NewRPMMD, and default to the current working directory.

I like this! I made NewRPMMD take the path to dnf-json and used the fullpath to dnf-json in the test.

I like this! I made NewRPMMD take the path to dnf-json and used the fullpath to dnf-json in the test.

Awesome, thanks! I'm ok with this as is, but would like to get @teg's opinion too.

superseded by #746


Added restrictions to up|down({ to: ... }); fixes #36

Check that there is a migration that matches to to parameter.
Check that the migration is pending/executed.

nice

v1.7.1


Private network is enabled but network is missing

Hi!
We're trying to use the exasol/docker-db:6.0.0-d1sc for running local tests before deploying them to the real cluster.
On some machines running the image works perfectly, on others it fails like this:
$ docker --version
Docker version 1.13.0, build 49bf474

docker pull exasol/docker-db:6.0.0-d1sc
6.0.0-d1sc: Pulling from exasol/docker-db
Digest: sha256:851bdc7da8e562e99528ce1a1fcaf62ffd0c86f5ef22813751fafe7e046850bd
Status: Image is up to date for exasol/docker-db:6.0.0-d1sc

$ docker run --rm --privileged exasol/docker-db:6.0.0-d1sc
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000761793 s, 1.4 GB/s
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000747259 s, 1.4 GB/s
Traceback (most recent call last):
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/exainit.py", line 11, in <module>
    from exainit.config import config
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/exainit/config.py", line 18, in <module>
    exaconf = EXAConf(None, True)
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/devel/docker/libexadt/EXAConf.py", line 108, in __init__
    self.validate()
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/devel/docker/libexadt/EXAConf.py", line 454, in validate
    raise EXAConfError("Private network is enabled but network is missing in section '%s'!" % section)
libexadt.EXAConf.EXAConfError: "ERROR::EXAConf: Private network is enabled but network is missing in section 'Node : 11'!"

What kind of network is the error message talking about? Is that a docker network?
Any other clues what might go wrong here?
Thanks!

Interestingly, when I start the container with sh and run the sc_init.sh script manually (which should exactly correspond to the used CMD ["/bin/sh" "-c" "/bin/sh /exa/etc/sc_init.sh"]) it's working:
sh-4.1# /bin/sh /exa/etc/sc_init.sh
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000716441 s, 1.5 GB/s
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000657235 s, 1.6 GB/s
[2017-04-26 15:39:53] stage0: Run stage 'stage0'
[2017-04-26 15:39:53] stage0: Run service environment_conf
[2017-04-26 15:39:53] stage0: Run service license_check
[2017-04-26 15:39:53] stage0: Run service next_stage

In /exa/etc/sc_init.sh exists one tricky place, which may be do not work in your configuration:
    14  CURIP="$(/sbin/ip addr | awk '{ if (n>0) { n+=1; } if (n==3) { print $2; n=0; } } /state UP/{ n=1; }')"
    15  sed -i "s+XXX.XXX.XXX.XXX/XX+$CURIP+" /exa/etc/EXAConf

It is possible, that if it starts in your envirenment, the network interface is not UP fast enough, it would explain, why it works if you start it manually. May be a sleep or a active white loop before line 14 would be good....

Hi @ooke, thanks for your help!
I think you're right with your diagnose:
If I start the container and directly execute the sc_init.sh script (as it effectively is by the CMD) it fails:
$ docker run -it --privileged=true exasol/docker-db:6.0.0-d1sc sh /exa/etc/sc_init.sh
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000785147 s, 1.3 GB/s
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000743975 s, 1.4 GB/s
Traceback (most recent call last):
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/libexec/exainit.py", line 11, in <module>
    from exainit.config import config
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/exainit/config.py", line 18, in <module>
    exaconf = EXAConf(None, True)
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/devel/docker/libexadt/EXAConf.py", line 108, in __init__
    self.validate()
  File "/usr/opt/EXASuite-6/EXAClusterOS-6.0.0/devel/docker/libexadt/EXAConf.py", line 454, in validate
    raise EXAConfError("Private network is enabled but network is missing in section '%s'!" % section)
libexadt.EXAConf.EXAConfError: "ERROR::EXAConf: Private network is enabled but network is missing in section 'Node : 11'!"

If however I wait a little before running the script everything works:
$ docker run -it --privileged=true exasol/docker-db:6.0.0-d1sc bash -c 'sleep 3 && sh /exa/etc/sc_init.sh'
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00286304 s, 366 MB/s
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.000715008 s, 1.5 GB/s
[2017-04-27 11:04:55] stage0: Run stage 'stage0'

Directly running line 14 from sc_init.sh without sleeping
$ docker run -it --privileged=true exasol/docker-db:6.0.0-d1sc bash -c "/sbin/ip addr | awk '{ if (n>0) { n+=1; } if (n==3) { print $2; n=0; } } /state UP/{ n=1; }'"
$

and with sleeping
$ docker run -it --privileged=true exasol/docker-db:6.0.0-d1sc bash -c "sleep 3 && /sbin/ip addr | awk '{ if (n>0) { n+=1; } if (n==3) { print $2; n=0; } } /state UP/{ n=1; }'"
    inet <IP_ADDRESS>/16 scope global eth0
$


router/jwt_authn: remove support for v2 deprecated regex and cors.

Risk level: Low
Testing: Unit tests modified.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

/assign-from @envoyproxy/maintainers

/assign-from @envoyproxy/maintainers

oh, and needs merge :-/

/wait

Conflict fixed, PTAL and please merge if looks good as I'm OOO. Thanks.

cc @phlax just to make sure this one was on your radar


pull request for e2e test at 12/08/2016 20:26:02

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


Fix release pipeline to correctly post release changelogs

I write the changelog to the PR to the release branch . However, for some reason, it takes the commit message of the last commit instead.

This was resolved by #379


Error while importing uploadcare modules

I have encountered the exact same error attempting to import the UploadClient module as well as the @uploadcare/react-widget module.
My stack is node.js 14LTS with React over next.js.
I have attempted to import using a standard import statement, import() function, as well as next/dynamic. Each behaves the same way and results in a similar stack with the same error message.
Interestingly enough, this fails:
import {UploadClient} from "@uploadcare/upload-client";
But this works:
import {UploadClient} from<EMAIL_ADDRESS>I can't use the 2nd method, for obvious reasons, but it seems like the importer is choosing the wrong file to import for some reason.
My package.json:
{
  "name": "sim",
  "version": "1.0.0",
  "description": "",
  "main": "src/server.mjs",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "next build",
    "start": "node src/server.mjs",
    "dev": "nodemon src/server.mjs -e json,js,cjs,mjs",
    "remoteDev": "nodemon -- --inspect=<IP_ADDRESS>:9229 src/server.mjs -e json,js,cjs,mjs"
  },
  "author": "Ronald Barbosa<EMAIL_ADDRESS>  "license": "UNLICENSED",
  "dependencies": {
    "@omarmfs98/nextjs-orgchart": "^1.0.8",
    "@sendgrid/mail": "^7.6.2",
    "@uploadcare/react-widget": "^2.2.0",
    "@uploadcare/upload-client": "^5.1.0",
    "ajv": "^8.11.0",
    "axios": "^0.21.4",
    "bcrypt": "^5.0.1",
    "copy-webpack-plugin": "^10.2.4",
    "formidable": "^2.0.1",
    "graphql": "^15.5.1",
    "iron-session": "^6.1.3",
    "mongo-sanitize": "^1.1.0",
    "mongoose": "^5.13.0",
    "next": "^11.0.1",
    "next-connect": "^0.12.2",
    "next-routes": "^1.4.2",
    "qrcode": "^1.5.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "semantic-ui-css": "^2.4.1",
    "semantic-ui-react": "^2.0.3",
    "speakeasy": "^2.0.0",
    "tesseract.js": "^2.1.5",
    "validator": "^13.7.0"
  },
  "devDependencies": {
    "nodemon": "^2.0.8"
  }
}

The stack is shown here:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module<EMAIL_ADDRESS>require() of ES modules is not supported.
require() of<EMAIL_ADDRESS>from /com.omnivertical.apps/sim/.next/server/pages/api/passport/create.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.node.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from<EMAIL_ADDRESS>
    at new NodeError (<node_internals>/internal/errors.js:322:7)
    at Object.Module._extensions..js (<node_internals>/internal/modules/cjs/loader.js:1102:13)
    at Module.load (<node_internals>/internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (<node_internals>/internal/modules/cjs/loader.js:790:12)
    at Module.require (<node_internals>/internal/modules/cjs/loader.js:974:19)
    at require (<node_internals>/internal/modules/cjs/helpers.js:101:18)
    at Object.@uploadcare/upload-client (/com.omnivertical.apps/sim/.next/server/pages/api/passport/create.js:132:18)
    at __webpack_require__ (/com.omnivertical.apps/sim/.next/server/webpack-runtime.js:33:42)
    at eval (webpack-internal:///./src/pages/api/passport/create.js:12:83)
    at Object../src/pages/api/passport/create.js (/com.omnivertical.apps/sim/.next/server/pages/api/passport/create.js:88:1)
    at __webpack_require__ (/com.omnivertical.apps/sim/.next/server/webpack-runtime.js:33:42)
    at __webpack_exec__ (/com.omnivertical.apps/sim/.next/server/pages/api/passport/create.js:230:52)
    at /com.omnivertical.apps/sim/.next/server/pages/api/passport/create.js:231:28
    at Object.<anonymous> (/com.omnivertical.apps/sim/.next/server/pages/api/passport/create.js:234:3)
    at Module._compile (<node_internals>/internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (<node_internals>/internal/modules/cjs/loader.js:1114:10)

There's a possibility this is fixed by updating next.js.
I'm evaluating that now

Updating all the modules appears to have resolved this issue. I'm not sure specifically which one and unfortunately, I have a time crunch that doesn't allow me time to investigate.
But after wiping my npm-shrinkwrap.json and reinstalling ... everything is working as expected.


Delete Google+ but Add Google Account Login/Registration

Q
A

Bug report?
[ ]

Feature request?
[X]

Support request?
[ ]

Hello Cocorico team
I have a proposal, due to “Google+ is no longer available for consumer (personal) and brand accounts” it’s no need for Google Share (not it;s three bottons Fb, Twitter, Google+). But a lot of people (as minimum all who have Android phones) has Google Account and can be very helpful to add Registration/Login not only with Facebook Account but also with Google Account

Thanks in advance

Hi @igorcherry,
Thanks for this pertinent suggestion :)

Not planned for now


Are the color of the boxes the same among images for multiple class models.

Is it that the first class gets one color in each image, or that same class gets the same color in every image.

May you please elaborate more about this issues

Yes, the API is not quite stable, so this is an issue I am made for myself,
which is why it is brief.
I have noticed this in my prototyping that the boxes aren't getting the
correct color when logging images in multi-class models. All predicted
boxes are the same color, even though multiple classes are being predicted.
I sense this is a numeric versus character encoding issue. I will be
investigating this tomorrow. Can you elaborate on your use case? Have you
noticed a similar problem? Nothing about the code jumps out as me, but I
will be writing tests. It is a bit hard to write a test for the visual
appearance of an image, so it may take something creative.
On Mon, Mar 29, 2021 at 9:04 PM iam-sarthak @.***>
wrote:

May you please elaborate more about this issues
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/weecology/DeepForest/issues/159#issuecomment-809889848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJHBLC6NX3LEZTF5RF3PPLTGFET7ANCNFSM4XRX5UWQ
.

--
Ben Weinstein, Ph.D.
Postdoctoral Fellow
University of Florida
http://benweinstein.weebly.com/


Spark 2.0 - databricks xml 2.11:0.3.3 not working

Hello,
I have spark 2.0 running, built with scala 2.11.8. It seems this is not compatible with any version of the spark-xml library.
I keep getting NotImplemented errors for Decimal type? any idea if this is or should be supported?

Yup, I just submitted a PR here, https://github.com/databricks/spark-xml/pull/150
I will release 0.4.0 as soon as possible.
BTW, please let me mark this as a duplicated with https://github.com/databricks/spark-xml/issues/137 so that I can manage them all together!

Thanks @HyukjinKwon,


Update kubectl-commands.html

Minor correction to code block classes and a sentence correction.

/close
We don't fix generated docs here. Please propose your fix to the upstream kubernetes/kubernetes repo so that we can regenerate the fixed reference out of it.


Add TestResponse extends from \Illuminate\Http\Response

Test response have next mixin
<?php

namespace Illuminate\Testing;

// use imports ...

/**
 * @mixin \Illuminate\Http\Response
 */
class TestResponse implements ArrayAccess
{

So PHPStorm suggests use methods from base response like $response->getContent()
But Vscode (with some plugins) - don't.
If we add code to __ide_helper.php Vscode will suggests base response methods from TestResponse
    namespace Illuminate\Testing {
        class TestResponse extends \Illuminate\Http\Response{}
    }

same with VIM.
Because VIM and Vscode suggests methods via bmewburn/intelliphense (php language server)

I would suggest to rather lobby that the tool supports @mixin?


Propagate App Model User ID on Windows

This PR ensures that all of our processes that might create windows have the same AppUserModelID which should help with some of the pinning woes that we're seeing.

Looks good to me, thanks!


feat: test vectors

This PR adds blocks for each network upgrade and led to a few tweaks of the en/decoding implementation.

LGTM


[Bug] Cancelling a child workflow with CancellationType.Abandon after cancelling the parent leads to an invalid state

What are you really trying to do?
We have a workflow that kicks off a child workflow that shouldn't have a lifecycle tied to the parent -- so we start it with
    parentClosePolicy: ParentClosePolicy.PARENT_CLOSE_POLICY_ABANDON,
    cancellationType: ChildWorkflowCancellationType.ABANDON,

We'd like to be able to cancel these workflows independently of each other -- and these workflows might run cleanup activities after being cancelled (so the parent workflow can continue running long enough after receiving a cancellation signal such that it can observe the cancellation of the child as well).
Describe the bug
If we cancel the parent workflow first, and then cancel the child workflow before the parent workflow has finished cleanup, we end up with the following error:
WARN complete_workflow_activation: temporal_sdk_core::worker::workflow: Failing workflow task run_id=f163e4ca-6cb5-4043-b579-4562d4e10865 failure=Failure { failure: Some(Failure { message: "Fatal(\"ChildWorkflowMachine in state Cancelled says the transition is invalid during event EventInfo { event_id: 379, event_type: ChildWorkflowExecutionCanceled, has_next_event: false }\")", source: "", stack_trace: "", encoded_attributes: None, cause: None, failure_info: Some(ApplicationFailureInfo(ApplicationFailureInfo { r#type: "", non_retryable: false, details: None })) }) } completion=WorkflowActivationCompletion(run_id: f163e4ca-6cb5-4043-b579-4562d4e10865, status: Success())

Reading over the code, it looks like we put the child workflow state machine in state Cancelled once the parent workflow receives a cancellation signal:
https://github.com/temporalio/sdk-core/blob/edb8f4eb9e4ffbc0ec052659e37231460c4429e1/core/src/worker/workflow/machines/child_workflow_state_machine.rs#L294
Then, when the ChildWorkflowExecutionCanceled event comes in, there's no valid Cancelled --(ChildWorkflowExecutionCancelled) transition so the state machine errors.
I'm not familiar enough with this code to understand whether the right fix is to stop the child workflow from transitioning to Cancelled when the CancellationType is Abandon, or if it's to add a valid transition from Cancelled --(ChildWorkflowExecutionCancelled) --> Cancelled, or something else entirely -- happy to help out as needed to get a fix for this issue though!
Environment/Versions
Running on Temporal version 1.18 with Typescript SDK 1.6.2

@PenguinToast Thanks for the quality bug report. I'll check this out and get it fixed.

@PenguinToast Actually, if you could provide a minimal sample of some workflow code that does this, that would be really awesome. If the parent close policy is abandon, the child shouldn't get cancelled by that at all. And the cancellation type being abandon would also mean even when you explicitly cancel the child WF, it doesn't actually get cancelled, the promise just returns as cancelled in the parent workflow.
I tried this both directly in Rust, and in TS, and didn't get a repro. I wrote this in TS:
export async function childWorkflowAbandoner(): Promise<void> {
  const childPromise = startChild(signalTarget, {
    parentClosePolicy: ParentClosePolicy.PARENT_CLOSE_POLICY_ABANDON,
    cancellationType: ChildWorkflowCancellationType.ABANDON,
  });
  await CancellationScope.current().cancelRequested;
  try {
    await CancellationScope.cancellable(async () => {
      CancellationScope.current().cancel();
      await childPromise;
      throw new Error('ChildWorkflow was not cancelled');
    });
    throw new Error('Expected CancellationScope to throw ChildWorkflowFailure');
  } catch (err) {
    if (!(err instanceof ChildWorkflowFailure && err.cause instanceof CancelledFailure)) {
      throw err;
    }
  }
}

And, indeed, when I cancel this workflow I get the expected behavior - the child workflow is left running, and the parent finishes as cancelled.

@Sushisource thanks for the response -- we are indeed explicitly cancelling the child workflow externally (not from within the parent workflow). I'll work on getting a minimal reproduction

Oh! Interesting. OK that definitely changes things.


feat: Switch to sigs.k8s.io YAML library

Motivation
Supporting both JSON and YAML format is a pain. The way go-yaml/yaml works is not compatible with encoding/json.
These libraries support different functionalities (inlining), vary in a way they handle values (null values) and most importantly require defining separate tags and custom encoding methods. Furthermore, these encoding interfaces have different shapes, the go-yaml/yaml in its latest v3 release operates on yaml.Node for UnmarshalYAML custom decoder while encoding/json equivalent uses raw bytes.
Summary
We discussed (with @fourstepper) alternatives to make OpenSLO maintenance and development easier.

Stick to the v3 release and just make it work, it's tedious though and I think this PR shows why: https://github.com/OpenSLO/OpenSLO/pull/289
Downgrade to v2, but that would be just cringe, no idea what other problems we might encounter since this is a very old release.
Use https://github.com/goccy/go-yaml, this is the library we're using at Nobl9 and it works well, it shares tags with JSON and its native serde interfaces operate on bytes.
Use what k8s uses :) --> https://github.com/kubernetes-sigs/yaml

Overall, we chose the last approach. The problems we have were already encountered by a third, large party and solved. No need to reinvent the wheel. Additionally, since we want to be compatible with k8s CRDs, we'd be using the library under the hood anyway.
There's a blog post written by the library authors which is worth while reading: https://web.archive.org/web/20190603050330/http://ghodss.com/2014/the-right-way-to-handle-yaml-in-golang/.

This actually also closes https://github.com/OpenSLO/OpenSLO/pull/288 ? :D


Milestone 0.0.16

Changes Unknown when pulling 7aa1e07bd23d0e9107899afa8371db1d32e55ccd on milestone-0.0.16 into ** on master**.


Rename tap-readme command to tap-new.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Write the README but also a .travis.yml file (and in future perhaps a
Jenkinsfile).

Thanks, I didn't have a chance to get around to this. I'm testing the recommended travis.yml as we speak

@scpeters Let me know when you're tried it out.

I've tried it out, and I added a matrix so that I could run both 10.11 and 10.10 in travis since we only have one CI machine building bottles, and it's still on 10.10.
I tried pushing a style error to a formula in https://github.com/scpeters/homebrew-simulation/commit/ec18af36b3242b39e7f7c7bf6608c5ff82d3e11d but I guess test-bot doesn't check for style errors. We have some formulae that take a long time to compile, so I think that's why I opted for an alternate travis file in the past. I found a weird error in one of our bottles (Error: invalid byte sequence in UTF-8) with this build, so I need to investigate that now, but I think it's unrelated to this travis script.
I'll try another formula modification and see what happens.

I bumped a formula revision in https://github.com/scpeters/homebrew-simulation/commit/51eb4fec0922e24809d420b6cfa0dde6b10597f7 and both matrix builds timed out after 45 minutes. A similar build takes about 20 minutes on our multi-core mac mini, so I guess travis is not enough for these formulae.
I'll see if there's any test-bot args to skip the bottle build.
As an aside, we are working to split this monolithic project into separate packages and formulae, but that is a work in progress.

I bumped a formula revision in scpeters/homebrew-simulation@51eb4fe and both matrix builds timed out after 45 minutes. A similar build takes about 20 minutes on our multi-core mac mini, so I guess travis is not enough for these formulae.

Yes, there's nothing you can really do to make this build faster and as a result Travis is not useful for building huge things on macOS.

I think his PR is good for the general case, though the travis script doesn't work well for my tap at the moment.

What do you do in your tap instead that works for you, out of interest?

https://github.com/osrf/homebrew-simulation/blob/master/.travis.yml#L26-L29
  - brew audit `ls $(brew --repo)/Library/Taps/osrf/homebrew-simulation/*.rb | grep -v sofa.rb`
  - brew style `ls $(brew --repo)/Library/Taps/osrf/homebrew-simulation/*.rb`
  - brew fetch --force-bottle `ls $(brew --repo)/Library/Taps/osrf/homebrew-simulation/*.rb | grep -v sofa.rb`
  - brew unpack --patch `ls $(brew --repo)/Library/Taps/osrf/homebrew-simulation/*.rb | grep -v sofa.rb`

It runs audit, style, fetch and verifies that patches apply cleanly for all formulae in the tap (except one that his head-only). The tap is small enough that these operations fit in the travis build window.
I wouldn't mind if these operations were done only on the formula touched by a pull request, but I wasn't sure how to do that.

@scpeters You can do that for the changed formulae in a PR with --fast which will avoid building but just check checksums/audit.


nodal stresses/strains are not calculated for solid elements

This should be a pretty straightforward recovery given the stresses should be calculated at the integration points exactly.  Stresses should then be extrapolated to the nodes.  Not having this makes the stresses artificially low.
I don't know what the order of the polynomials is for the different elements (CTETRA, CPENTA, CHEXA) or if it changes based on the number of nodes/integration method, but hopefully wherever the centroidal stress is calculated, there's a pretty straightforward recovery step that can be easily extended.

This applies to all result formats.


Support for multiple fonts and fallbacks

It would be nice to be able to specify different fonts for normal, italic, bold and bold-italic aswell as fallback fonts.
In my current terminal e.g. I use a more "curly" font for italics:

Additionally, it would be great to be able to specify fallbacks. I use a non-patched font as default and have specified fallbacks for powerline symbols and for emojis

A configuration format like this or similar could work
font:
  ligatures: true  # Enable font ligatures e.g. render '≡' instead of '==='
  normal:
    - family: "my normal font"       # Font family. Find possible values for this by running 'darktile list-fonts'
      size: 16         # Font size
      dpi: 72          # DPI
    - family: "my normal fallback 1"       # Font family. Find possible values for this by running 'darktile list-fonts'
      size: 16         # Font size
      dpi: 72          # DPI
    - family: "my normal fallback 2"       # Font family. Find possible values for this by running 'darktile list-fonts'
      size: 16         # Font size
      dpi: 72          # DPI
  italic:
    - family: "my italic font"       # Font family. Find possible values for this by running 'darktile list-fonts'
      size: 16         # Font size
      dpi: 72          # DPI
    - family: "my italic fallback 1"       # Font family. Find possible values for this by running 'darktile list-fonts'
      size: 16         # Font size
      dpi: 72          # DPI
    - family: "my italic fallback 2"       # Font family. Find possible values for this by running 'darktile list-fonts'
      size: 16         # Font size
      dpi: 72          # DPI
  bold:
    # ...
  bold-italic:
    # ...

I would be thrilled if this would be possible. FWIW I find the most reasonable way to implement multiple fonts is to use CSS Unicode Character Ranges so users can map specific code points to specific fonts. This feature is what made me use Kitty terminal.

I don't know exactly how it's implemented, but wezterm allows for multiple fonts with a configuration like this:
	font = wezterm.font_with_fallback( {
		{family="Recursive Mono Linear Static", weight="Medium"},
		"Inconsolata Nerd Font Mono",
		"Noto Color Emoji",
	}),

You don't need to define specific ranges, it just takes the first font that happens to include the character. Just adding this as a thought, character ranges would probably more precise, but require a more complicated configuration.