Forget: show reason why oldest snapshot in a group is kept

Output of restic version
restic 0.16.4 compiled with go1.21.6 on linux/amd64
What backend/service did you use to store the repository?
local
Problem description / Steps to reproduce
I setup a new repo and did manually 3 snapshots.
All the same day, two in the same hour (09:00).
I try to specify forget -keep-hourly 24, which should keep for the latest 24 hour max one snapshot per hour.
The forget --keep-hourly keeps too many backups.
The 09:36:51 and 09:41:06 (same day) both keeps with reason hourly. But only the 09:41:06 should be kept.
$restic forget -r [path_to_repo] --prune  --keep-hourly 24  --dry-run

repository 0fc3d186 opened (version 2, compression level auto)
Applying Policy: keep 24 hourly snapshots
snapshots for (host [xxx-machine], paths [/etc, /home, /root, /usr/local, /var/spool/cron]):
keep 3 snapshots:
ID        Time                 Host         Tags        Reasons          Paths
----------------------------------------------------------------------------------------
0729c5c9  2024-05-17 09:36:51  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron

fdee0afa  2024-05-17 09:41:06  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron

f03c4f42  2024-05-17 11:54:19  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron
----------------------------------------------------------------------------------------
3 snapshots

Expected behavior
The older backup in the hour 09:xx (0729c5c9 at 09:36:5) should be deleted, because in the same hour there is a newer one.
So command output should display:
$restic forget -r [path_to_repo] --prune  --keep-hourly 24  --dry-run

repository 0fc3d186 opened (version 2, compression level auto)
Applying Policy: keep 24 hourly snapshots
snapshots for (host [xxx-machine], paths [/etc, /home, /root, /usr/local, /var/spool/cron]):
keep 2 snapshots:
ID        Time                 Host         Tags        Reasons          Paths
----------------------------------------------------------------------------------------
fdee0afa  2024-05-17 09:41:06  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron

f03c4f42  2024-05-17 11:54:19  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron
----------------------------------------------------------------------------------------
2 snapshots

Actual behavior
The backup 0729c5c9 stays and is not forgotten by restic which is wrong in my opinion.
Do you have any idea what may have caused this?
No.
I found already different problems in the forum and issues. But mostly regarding time zones or confusing between the -keep-within and -keep-* option.
Did restic help you today? Did it make you happy in any way?
Restic is awesome. Thank you very much for all your work.
I used already to often to get a older config file version.

Ok. It seems, that this is only not working like excepted for the initial snapshot. This initial one stays what ever happens later.
But for all other snapshots it's working like excepted.
I think it would be helpful to leave this issue to avoid initial confusion for others.

This is actually intended behavior, see https://restic.readthedocs.io/en/stable/060_forget.html#removing-snapshots-according-to-a-policy :

If there are not enough snapshots to keep one for each duration related --keep-{within-,}* option, the oldest snapshot is kept additionally.

That special case isn't particularly relevant for --keep-hourly. However, for --keep-yearly 2 with a backup that contains only a few months of snapshot it's rather helpful to keep the oldest and the latest snapshot of this year.

Oh sorry. Did not see this.
Thank you very much for your answer and all your work!
Maybe too less confuse, we could add this also as a reason in the restic forget command. Then everyone would understand this.

Here you go: https://github.com/restic/restic/pull/4820

@MichaelEischer: Thank you for your effort. just to be clear. I think it would be helpful to add the info about this into the forget command output (not the help).
So in the column reason where we have currently hourly snapshot there should be the additional reason: oldest-snapshot
$restic forget -r [path_to_repo] --prune  --keep-hourly 24  --dry-run

repository 0fc3d186 opened (version 2, compression level auto)
Applying Policy: keep 24 hourly snapshots
snapshots for (host [xxx-machine], paths [/etc, /home, /root, /usr/local, /var/spool/cron]):
keep 3 snapshots:
ID        Time                 Host         Tags        Reasons          Paths
----------------------------------------------------------------------------------------
0729c5c9  2024-05-17 09:36:51  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron

fdee0afa  2024-05-17 09:41:06  xxx-machine              hourly snapshot  /etc
                                                                         /home
                                                                         /root
                                                                         /usr/local
                                                                         /var/spool/cron

That is the reason i was confused. Because i just checked this column. I guess others could be confused easily too, if this info is there missing. For me it's kind of uncomplete. If a reason is displayed, then all reason should be displayed.

Any suggestion for a compact reason that would be understandable? Would oldest hourly snapshot work maybe?

To keep the terms like in the doc maybe with the term additional. e.g. additional oldest hourly snapshot.
It will just be one for each keep criteria, so at least I would not mind about a line-breaked reason.

I'm wondering if the snapshot keyword is necessary in general. forget lists a list of snapshots by definition.

@MrJack91
Here is the list of snapshots before running prune:
konidev@lima-vm-1:~/restic$ ./restic snapshots
repository b02926f5 opened (version 2, compression level auto)
ID        Time                 Host        Tags        Paths                    Size
-----------------------------------------------------------------------------------------
44f7711e  2024-09-02 23:54:46  lima-vm-1               /home/konidev/test-data  1.024 GiB
2e4b4772  2024-09-02 23:55:47  lima-vm-1               /home/konidev/test-data  1.024 GiB
2881c5f0  2024-09-02 23:57:34  lima-vm-1               /home/konidev/test-data  2.040 GiB
b6d26123  2024-09-02 23:57:45  lima-vm-1               /home/konidev/test-data  2.040 GiB
-----------------------------------------------------------------------------------------
4 snapshots

Here is the sample output after the change:
konidev@lima-vm-1:~/restic$ ./restic forget --keep-daily 24 --dry-run
repository b02926f5 opened (version 2, compression level auto)
Applying Policy: keep 24 daily snapshots
keep 2 snapshots:
ID        Time                 Host        Tags        Reasons                Paths                    Size
----------------------------------------------------------------------------------------------------------------
44f7711e  2024-09-02 23:54:46  lima-vm-1               oldest daily snapshot  /home/konidev/test-data  1.024 GiB
b6d26123  2024-09-02 23:57:45  lima-vm-1               daily snapshot         /home/konidev/test-data  2.040 GiB
----------------------------------------------------------------------------------------------------------------
2 snapshots

remove 2 snapshots:
ID        Time                 Host        Tags        Paths                    Size
-----------------------------------------------------------------------------------------
2e4b4772  2024-09-02 23:55:47  lima-vm-1               /home/konidev/test-data  1.024 GiB
2881c5f0  2024-09-02 23:57:34  lima-vm-1               /home/konidev/test-data  2.040 GiB
-----------------------------------------------------------------------------------------
2 snapshots

Would have removed the following snapshots:
{2881c5f0 2e4b4772}

If there is consensus, I can add the word additional into the reason for consistency with the documentation. IMO I think it should be fine to leave it out, since the word oldest already conveys that it's an additional reason for being retained.

@konidev20 Great, that looks good for me.
Yes sure, it's ok for me, "additional" is not necessary,
Thank you very much for your work!


Enable Dependabot updates

enable Dependabot monitoring of Go, GitHub Actions and Dockerfile updates
add "canary" Dockerfile so that PRs will be generated to remind me to generate fresh binaries for the latest version of Go

I have intentionally set this to an older version to verify that the configuration is setup as intended

fixes GH-5

Markdown linting issue to be fixed by #3.


changed author id to url. Also added POST author/id/friends api endpoint (from previous sprint still unmerged)

Do all the privacy tests still pass?


change range hover background color

Is it possible to change the hover color in range mode? (default color is blue)
I had read the docs but nothing was found.

Yes, you can do it with CSS, Here is an example:
https://codesandbox.io/s/datepicker-range-hover-color-f47fe7
There is also an example in the documentation that provides a CSS file that you can use:
https://shahabyazdi.github.io/react-multi-date-picker/colors/#red


Update Launch-file-different-formats.rst

https://docs.ros.org/en/rolling/Tutorials/Intermediate/Launch/Launch-system.html#writing-the-launch-file
fix launch file names to follow recommended format

depends on https://github.com/ros2/demos/pull/588

With my latest changes, and the merge of the associated PR, this looks good to me.  So I'm going to go ahead and merge this, thanks for the contribution!


Error starting docker compose

General information
version of ShellHub): 0.4.0 (ShellHub is running on localhost in a docker-compose container
Mac OSX: 10.14.6 (macOS Mojave)
Problem description
The command ./bin/docker-compose up -d is not working and produces following output in my terminal:
readlink: illegal option -- f
usage: readlink [-n] [file ...]
usage: dirname path
ERROR: .FileNotFoundError: [Errno 2] No such file or directory: './docker-compose.yml'
Problem story

I created a fresh folder on my drive and cloned the new version of ShellHub via git clone -b v0.4.0 https://github.com/shellhub-io/shellhub.git shellhub
cd shellhub and ./bin/keygen worked fine without any problems
After ./bin/docker-compose up -d I got the error

Suggestions
I think the pointer to the docker compose file is missing a dot. Within the shell script it should create the file path ../docker-compose.yml
Side node
When starting docker compose with the command docker-compose up -d, then everything gets downloaded and installed as expected

General information
version of ShellHub): 0.4.0 (ShellHub is running on localhost in a docker-compose container
Mac OSX: 10.14.6 (macOS Mojave)

ShellHub is not supposed to work on MacOSX because none of our contributors has a Apple workstation.

readlink: illegal option -- f

It seems that the readlink command from MacOSX does not support the -f flag.
Is there any alternative to readlink command to work on Mac as it works on Linux (coreutils)?

I just googled a bit around and found a question about that on stackoverflow: https://stackoverflow.com/a/4031502
I tested this on my Mac with greadlink -f name, where name could be a filename or folder name and it worked as expected. The command gave me the absolut path to the given name


TypeScript error in config.ts: Conversion of type 'undefined' to type 'PromiseConstructorLike' may be a mistake

RxJS: 6.5.3
TS: 3.6.2
src/internal/config.ts
export const config = {
  /**
   * The promise constructor used by default for methods such as
   * {@link toPromise} and {@link forEach}
   */
  Promise: undefined as PromiseConstructorLike,

Fails with compilation error:

TypeScript error in D:/Dev/OpDashBoard/FrontEnd/ClientApp/node_modules/rxjs/src/internal/config.ts(12,12):
Conversion of type 'undefined' to type 'PromiseConstructorLike' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.  TS2352

I think the fix would be to define it as:
  Promise: undefined as unknown as PromiseConstructorLike

Or maybe another, cleaner way.
Repro in Playground

I got this error when accidentally imported a RxJS file under src/internal/ into my project

In the interim, you could - should, IMO - specify skipLibCheck in the compiler options in your tsconfig.json. There really is little point in having TypeScript check the internals of packages within node_modules when those packages contains .d.ts files that have already passed through the TypeScript compiler.

I'm going to close this as it's a sub-case of a known issue: the TypeScript compiler options used to build RxJS are insufficiently strict. In particular, strictNullChecks is false. See https://github.com/ReactiveX/rxjs/issues/4968


Transition speed

Is it possible to set the transition speed to 1 hour instead of 30 seconds? I know there isn't an option in the GUI so I was wondering if it could be set in a config file.

We will add it - the xflux app is now building against identical core code as the Mac and Windows, so it should be easy.


WIP: Add support for adding item attributes to generated types

This adds support for parsing attributes in combination with the tree being generated. The idea is that the parsed attributes added to each item associated with the types being generated. That way, it's possible to selective add compile-time constraints like feature flags.
This patch only adds support for parsing feature flags right now. Also the generated attributes only apply to functions, see below for more.
Example
windows_macros::generate!(
    #[cfg(feature = "coreaudio"]
    Windows::Win32::CoreAudio::*,
    #[cfg(feature = "xaudio2")]
    Windows::Win32::XAudio2::*,
)

This would for example cause XAudio2CreateWithVersionInfo to be generated like this:
#[cfg(feature = "xaudio2")]
pub unsafe fn XAudio2CreateWithVersionInfo(/* ... */) -> ::windows::ErrorCode {
    #[link(name = "XAudio2_9")]
    extern "system" {
        pub fn XAudio2CreateWithVersionInfo(/*  */) -> ::windows::ErrorCode;
    }
    XAudio2CreateWithVersionInfo(/* ... */)
}

Motivation
I want to be able use feature flags to determine which which linked libraries should be required for compiling my crate, and the above is enough to avoid a linker error in case XAudio2_9 is not available and the feature is disabled.
The attributes are currently only added to functions, because these are the only items which include #[link] attributes. Filtering these allows tree shaking in rustc to do the rest of the work right now. But in principle these could be added to any item that is recursively included.
WIP
This is currently in WIP to garner feedback.
What I want to do before it's merged is:

Clean up TypeConstraints. It is currently used to recursively add any(...) dependencies for the complete intersection if features in use for any given item, but it's a bit messy.
Add parsing for all(...) and any(...).

Thanks, I'll take a look later this week. Just to set expectations, I'm in the middle of adding features for namespace lightup - to reduce build time - and we also have another project to deal with linker issues so this PR is likely to collide with both of those. So I'm happy to see the experimentation and ideas flowing but may not be able to accept something like this at the moment.

That's all right. Looking forward to have a look at what you come up with. And feel free to use anything in here if you find it useful.

Thanks, I'll take a look later this week. Just to set expectations, I'm in the middle of adding features for namespace lightup - to reduce build time - and we also have another project to deal with linker issues so this PR is likely to collide with both of those. So I'm happy to see the experimentation and ideas flowing but may not be able to accept something like this at the moment.

@kennykerr I just wanted to ask. Is this project public somewhere so I can follow it?

For the DLL imports: https://github.com/rust-lang/rust/issues/58713
For the features: https://github.com/microsoft/windows-rs/issues/432


Mismatched type in date spine macro

#101 seems to have broken the date_spine macro for datepart day. I'm running the macro with the following syntax:
{{
  dbt_utils.date_spine(
    datepart="day",
    start_date="'2010-01-01'",
    end_date="date_add(current_date(), interval 3 month)")
}}

When I run the macro, I get this error in BigQuery: No matching signature for operator <= for argument types: DATETIME, DATE. Supported signatures: ANY <= ANY at [142:11]
The offending SQL is here:
select (
    datetime_add(
        cast( '2010-01-01' as datetime),
    interval row_number() over (order by 1) - 1 day
    )
) as date_day
...
select *
from all_periods
where date_day <= date_add(current_date(), interval 3 month)

I believe that date_day used to be of type date instead of datetime, which is causing the error with the comparison. It seems this change was introduced by #101 to macros/cross_db_utils/dateadd.sql.

A related thought that I would be happy to move to a new issue: this repo is big enough and widely used enough that it should probably maintain versioned release branches so that potentially breaking changes like this aren't automatically introduced by running dbt deps.
The revision option in dbt's packages.yml (here) isn't as useful unless there's a distinct branch for each version that I can lock in to or update to.

hey @joshtemple - thanks for opening this issue. We actually made this change to bring the dateadd macro in line with the other implementations of dateadd for snowflake/redshift. This is deeply distressing to me, but date_add on BigQuery doesn't work with sub-day time parts (like hour/min/sec). The corresponding timestamp_add doesn't work with super-day parts (like week, month, year). So, datetime_add is the only function that will actually accept all of the different time parts that the rest of this package's date macros support.
I really didn't want to use datetime here, but I unfortunately didn't see a good way around it. If you have other ideas for how this could work, I'd be super interested in hearing them! If you're cool with datetimes, i'd recommend casting the column returned by dateadd to a date to suit your needs.
To your last point, we cut releases that are (mostly) semantically versioned. You can supply a tag name in the revision part of your packages.yml specs to pin your dep to a specific version. I highly recommend doing that for all of your dependencies. You can find the list of tags here: https://github.com/fishtown-analytics/dbt-utils/releases

Makes perfect sense, I'm totally fine with using datetime in this instance. Thanks for the heads up on the release tags, that's exactly what I was looking for! I figured you had already thought of this and I was just missing something...
Going to go ahead and close this issue.


24h time is counted incorrectly

Describe the bug
The time is not reset at 23:59 and the day gets +1.
The time runs until 29:59 and then the day becomes +1 then the time starts at 06:00.
To Reproduce
Steps to reproduce the behavior:
Change the time in the config to 24H
use24HourClock=true
Screenshots

Server (please complete the following information):

OS: Debian 12
Minecraft: 1.20.2
Fabric: 0.15.3
Mod: 4.2.0

Whoops, that's what I get for not testing this enough. I'll have a fix out in a bit.


Allow workflow execution to use cached values

The runtime performance of subsequently executed workflows could be drastically increased if a value cache could be used so that some steps don't need to be executed again. Subsequent workflow execution will occur in the ECT WebAPI service, which is an implementation detail of issue #32.
Caching shall occur only if allowed by a certain workflow step. Actually, caching shall only occur for steps, whose operation can be said to be a pure function - the function output depends solely on the function input, with no side-effects, and no random values generated.
Therefore, an operation's meta-info header should include information of whether its output values are allowed to be cached or not.

Implemented today


Alpha 1.0.15 has the wrong server version mapped to it

Alpha 1.0.15 maps to server a0.1.2_01.jar instead of a0.1.0.jar

This is an issue for BetterJSONs for V2 version format (supported by RMCP v1.0) and an issue for MCPHackers.github.io for V1 version format.
Closing as this issue is in the wrong repository.


fix isShutdown always return true

change isShutdown to isTerminated

Please synchronize the origin/master branch to resolve the problem of CI check failure

Codecov Report

Merging #1426 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1426      +/-   ##
==========================================
- Coverage   31.57%   31.56%   -0.01%
==========================================
  Files         682      682
  Lines       33035    33035
  Branches     6592     6592
==========================================
- Hits        10432    10429       -3
- Misses      20750    20753       +3
  Partials     1853     1853

Impacted Files
Coverage Δ

...a/com/alibaba/dubbo/common/utils/ExecutorUtil.java
0% <0%> (ø)
:arrow_up:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
41.66% <0%> (-8.34%)
:arrow_down:

...bo/remoting/transport/netty/NettyCodecAdapter.java
55.22% <0%> (-1.5%)
:arrow_down:

...om/alibaba/dubbo/rpc/filter/ActiveLimitFilter.java
83.33% <0%> (+5.55%)
:arrow_up:

Continue to review full report at Codecov.

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

@lovepoem ok, please review it.

Review the commit , change isShutdown to isTerminated.

java.util.concurrent.ExecutorService#isShutdown will return true , after invoking shutdown or shutdownNow.
java.util.concurrent.ExecutorService#isTerminated will return true, after all tasks have completed execution.

It is correct about this modification.

@cvictory
No, isShutdown() will always return true when you invoke shutdown() or shutdownNow().
please confirm this, thank you

I don't understand what is the purpose of this pull request. What problem have encountered? Can you file an issue to describe it?

@ralf0131
我用中文表述一下
当调用-ExecutorService的shutdown方法之后无论ExecutorService是否关闭再次调用shutdown都会返回true。
有段代码if (!isShutdown(es)) { newThreadToCloseExecutor(es); }其条件永远都返回false，也就是说下面的关闭线程并不会启动

Hello, thanks for the clarification, I've figured out what you mean.
I think you are correct.
However,  I argue that it cannot solve the problem completely. ShutdownNow uses Thread.interrupt to try to interrupt the running threads, if a thread does not respond to the interrupt signal, it will never stop even if you call the shutdownNow for multiple times.

Anyway, I will merge this pull request. Thanks for the pull request!

@ralf0131    Thank, if a thread does not respond to the interrupt signal, newThreadToCloseExecutor will work to wait thread finished.


Prevent use of GenericClass[T.untyped]

Problem
It is very easy to accidentally instantiate a generic class without passing a type parameter, which results in GenericClass[T.untyped] (as documented here.) This pokes a rather large hole in Sorbet's type safety for a few reasons:

It is easy for consumers of classes with generics to be completely unaware of the presence of type parameters
At a glance, sig { returns(GenericClass) } is visually identical to sig { returns(String) }, but one is safe and the other is not

(It seems likely that I'm missing a restriction that led to this design decision, possibly related to gradual typing.)
Proposed solution
Add a configuration option that would cause Sorbet to fail to typechecks if a sig includes a class containing unspecified type parameters. In future versions of Sorbet, I would expect this to be the default.

This is already an error:
https://sorbet.org/docs/error-reference#5046
for legacy reasons, it's reported at # typed: strict when the generic class is a class defined in the standard library

https://sorbet.run/#%23 typed%3A true
extend T%3A%3ASig

class Box
  extend T%3A%3AGeneric
  Elem %3D type_member
end

sig {returns(Box)}
def foo%3B Box.new%3B end

Oh, looks like I hadn't quite isolated my problem. Perhaps in this playground, the bug that I'm seeing isn't a failure to require an annotation on L18, but rather a failure of L18's box instance to infer the Elem type parameter's type as Integer? Is there a way for me to modify this playground so that it will fail checking without requiring the author to remember to specify the correct type parameter (as on L19)?


Custom shapes should implement IConvertibleToXML

Just because art and polygon shapes need a vertex mapping to fit in a level, doesn't mean they need a vertex mapping to print individually - just set the vertex id to zero and that's an OK representation of an individual shape. Make the ToXML() method use a default vertex mapping that always outputs zero and it should just work.

Done in commit https://github.com/ultrako/LevelXML/commit/d93d4795c9bbd72e7eb99c92dd615c3703334fa6.


Update fails with fontawesome pro in .npmrc

Versions
Angular CLI: 6.0.0-rc.8
Node: 8.11.1
OS: darwin x64
Angular: 6.0.0-rc.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.11
@angular-devkit/build-angular     0.5.11
@angular-devkit/build-optimizer   0.5.11
@angular-devkit/core              0.5.11
@angular-devkit/schematics        0.5.11
@angular/cli                      6.0.0-rc.8
@ngtools/webpack                  6.0.0-rc.9
@schematics/angular               0.5.11
@schematics/update                0.5.11
rxjs                              6.0.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

Install private scoped package with configuration in .npmrc through npm
Run ng update

Observed behavior
Not found : @fortawesome/fontawesome-pro-webfonts

Desired behavior
ng update should use .npmrc and work as usual
Mention any other details that might be useful (optional)

This seams to work with 1.7.3 or with global and not per project .npmrc
Sorry but this is the only comparable project I had for a fast test.

This should have been fixed by https://github.com/angular/angular-cli/pull/13025


Fix the test data reference set checksum

This is computed as MD5("90977a37195d3fd247e4916b5b4cbae8") per the documentation.

Assigning to compliance dataset wrangler @macieksmuga .

@macieksmuga is this good to merge? I'm mainly concerned that this implies a bug in the reference server (I'm assuming the current version passes against the reference server), so it would be good to propagate that information back.

@calbach yes, this is good. Sorry I didn't get around to it before.


wasmtime: 24.0.0 -> 25.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bytecodealliance/wasmtime/releases.
meta.description for wasmtime is: Standalone JIT-style runtime for WebAssembly, using Cranelift
meta.homepage for wasmtime is: https://wasmtime.dev/
meta.changelog for wasmtime is: https://github.com/bytecodealliance/wasmtime/blob/v25.0.0/RELEASES.md
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 25.0.0 with grep in /nix/store/4ai8khvkjsp1wkscxqm35cxsaijl0aqs-wasmtime-25.0.0
found 25.0.0 in filename of file in /nix/store/4ai8khvkjsp1wkscxqm35cxsaijl0aqs-wasmtime-25.0.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wasmtime

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/f5061b9fb6e8188f279da0ca7841cb2775adaf8b#wasmtime

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4ai8khvkjsp1wkscxqm35cxsaijl0aqs-wasmtime-25.0.0
ls -la /nix/store/4ai8khvkjsp1wkscxqm35cxsaijl0aqs-wasmtime-25.0.0/bin

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

2 packages built:

wasmtime
wasmtime.dev

Maintainer pings
cc @ereslibre @matthewbauer for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Result of nixpkgs-review pr 343379 run on x86_64-linux 1

2 packages built:

wasmtime
wasmtime.dev


ci: fix failures in code coverage uploads

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


[SDAA]Add Tecorigin SDAA backend

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.TecoriginSDAA seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Entity rendering is bugged

No idea why this is happening, but entities are not lit properly. Dropped blocks and items work fine.
From my experience with shaders, the entities might be a different render pass and that might be the problem.

@catfoolyou It's because of some changes I made to the lighting to try to help with performance, I reverted the changes but forgot to recompile before pushing the commit, to fix it just recompile the project, this will be fix in the next update.

Ah, alr.


[HIGH LEVEL] Enable emojis in richtext

update storyblok-renderer package to enable NODE_EMOJI resolver
install gemoji to get Name to Emoji mapping
Storyblok sense us only the emoji name as a string and we have to map that to an emoji hence the installation of a mapping library

@Zahra-8d it doesn't fail if emoji doesn't exist, it just returns undefined so I've just done a check for undefined and returned null if it doesn't exist


Input radio

Not sure what the right place for this is, but provide a description of how to work with input type=radio based on the comment in this bug https://github.com/aspnet/AspNetCore/issues/5579#issuecomment-548061223

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

ID: eef47457-c8cf-74a4-b884-c1fe5c2ef52d
Version Independent ID: 09a02d10-2834-467d-d8c2-3fd19ceb3863
Content: ASP.NET Core Blazor forms and validation
Content Source: aspnetcore/blazor/forms-validation.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

To get it going right now, see this workaround.  It works fine.
https://github.com/aspnet/AspNetCore/issues/5579#issuecomment-548061223


Compatibility with Typescript

Any plans on creating Typescript type definitions for this library? I'd like to use it in an angular project that is written in Typescript, and was wondering if they are plans to have official support, or if I should look into writing my own type definitions.

+1 ?

That seems like a great idea, I would you like to be involved in creating a definition for ASF?

There is actually a project for this to happen: https://github.com/json-schema-form/json-schema-form/wiki/Current-projects#typescript-definition
Anyone have any experience with creating DT-definitions? I haven't before.

Also, I would recommend waiting until the core has been broken out, as I suppose that there will be a jsf interface and and asf-interface in the end.

I was looking for an example how to include schemaform.io in an ionic 2.0 project which uses typescript. I'm not an expert in javascript and a newbee for typescript and I would love a simple example how to use this together.
Schemaform is really brilliant and exactly what I was looking for. I'm just in the need to use it in an app instead of a website :-((

Well, actually, it should be possible.  We are using ASF as is, using @angular/upgrade in an Angular 2 project, a description of that is here:
https://github.com/OptimalBPM/of-admin/wiki/App-Entry-&-Bootstrapping
I don't know how well Ionic works with ASF in other ways, though.
I have actually considered creating an implementation for react-native or react-native-renderer. Because after 1.0, and Angular 2 implementation is the next major thing.


cli: replace pyyaml with ruamel.yaml

The popper CLI tool uses pyyaml for parsing YAML. However, pyyaml only supports the old 1.1 YAML format. Since the work on pyyaml module has been abandoned we can use ruamel.yaml module instead, which follows the new 1.2 YAML format.
More information about the differences between the two modules can be found here
For this issue, we need to replace pyyaml by ruamel.yaml

Think this can be closed now?


[Feature Request] Allow to register a language provider using a language selector instead of a single language

Context

[X] This issue is not a bug report. (please use a different template for reporting a bug)
[X] This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description
all register*Provider methods in monaco.languages take a languageId as first parameter.
However, they are just calling the register method from LanguageFeatureRegistry which can take a whole LanguageSelector as parameter.

A reasonable feature request, thanks for also providing the PR. What is your use-case?


Pixel intensity overflow in HDR mode

Hi Thomas,
I noticed that the new HDR view of 'tev' encounters some kind of overflow/non-monotonicity when cranking up the exposure and bright pixels (EXR value ~ 5) are visible. This happens in the green/red visualization of signed images -- try opening the attached EXR file on a Mac in HDR mode and increase the exposure -- suddenly, many of the pixel flip from red to black.
I tried to capture a screengrab, but curiously the problem isn't visible there. It's possible that there is some kind of max intensity value for floating point buffers (e.g. 64K) that is being reached.
Thanks,
Wenzel
bwd.exr.zip

Hi Wenzel, I can't reproduce the issue on my macbook, unfortunately -- the pixels just keep getting brighter and eventually saturate to white. The attached screen recording is representative.
https://user-images.githubusercontent.com/4923655/148978423-5f08c2fc-2063-4c63-9a00-ffb54e6e6696.mov
You can also see flickering that I've started to experience since switching my M1 Max that I mentioned recently. Seems at first like a separate issue (no overflow behavior), but who knows -- might be related in the end.

Before I start digging deeper into tev, could you check whether the same overflow occurs when cranking the brightness in one of the nanogui samples?

It's on a Pro Display XDR in my case, but with the not-quite-latest macOS version (which may be relevant here, Apple has been doing a lot of work on HDR support in the OS). I plan to give this another try with Monterey when I receive my M1 machine in February.

The magic value seems to be 64, and this fixes it:
diff --git a/src/UberShader.cpp b/src/UberShader.cpp
index 91d9a8a..68b4d88 100644
--- a/src/UberShader.cpp
+++ b/src/UberShader.cpp
@@ -355,9 +355,8 @@ UberShader::UberShader(RenderPass* renderPass) {
                         ),
                         1.0f
                     );
-                    if (clipToLdr) {
-                        color.rgb = clamp(color.rgb, 0.0f, 1.0f);
-                    }
+                    color.rgb = clamp(color.rgb, clipToLdr ? 0.f : -64.f,
+                                                 clipToLdr ? 1.f :  64.f);
                     return color;
                 }

@@ -377,9 +376,8 @@ UberShader::UberShader(RenderPass* renderPass) {
                     ),
                     1.0f
                 );
-                if (clipToLdr) {
-                    color.rgb = clamp(color.rgb, 0.0f, 1.0f);
-                }
+                color.rgb = clamp(color.rgb, clipToLdr ? 0.f : -64.f,
+                                             clipToLdr ? 1.f :  64.f);
                 return color;
             })";
 #endif

https://user-images.githubusercontent.com/1203629/148985978-3c13dd65-dbab-466a-801f-d1cf1aaae47d.MOV
Here is that that looks like by the way.

Thanks for checking! 64 seems rather low, to be honest, but still a factor of ~4 above what my highest dynamic range display (the laptop) can output. So... I doubt the extra clamp affects anyone as of now. :)


Different point cloud topics different

Hello,
What is the difference between these point cloud topics published by LIO-SAM?
/lio_sam/mapping/cloud_registered
/lio_sam/mapping/cloud_registered_raw
/lio_sam/mapping/map_global
/lio_sam/mapping/map_local
Thanks,

I would also be interested into an answer.
Thanks


Tech Stack Update ( LOGO add )

I will like to add tech stack logo used in our project this will make our project attractive !! Will start to work on this issue as soon as i get assigned !!

Have a look should i add something new or change  alignment or is it ok ?


Tenants, global tenant name, fixes...

new field Global Tenant Name -> #1228
Interpret Tenant-Level from right -> #1324
hide Superadmin flag in UI
new action Update Tenant in UI (only for change in tenant database table: Comment, Project, ViewAllDevices)
merge some catches
eliminate several warnings
some smaller cleanup and fixes

@abarz722 could you resolve the conflicts from Nils' PR, please - sorry for the inconvenience.

merging for now and solve remaining issues later


tox-pytest workflow generates a mostly empty cache

Brought up in this comment.
This is not high priority until we start tackling our test times.
Scope:

[ ] the Zenodo cache generated by a tox-pytest run contains the actual data instead of just the datapackage.jsons

Next steps:

[ ] Find a short subset of tests to run that downloads actual data to the local cache, without --gcs-cache set
[ ] Verify that setting --gcs-cache will not download actual data and just download the datapackage.json

The long CI times are definitely annoying, but I think we might be more concerned with the resulting data egress fees -- if GitHub is downloading ~1GB of data from GCS every time we run CI how much does that cost? I guess 1GB is only about $0.12, but we do run CI dozens of times a day sometimes.

Now that #2329 is merged we see a real cache in main and also it gets used in other branches!

If we keep merging dev into main more frequently, the main cache should stay fresh too.


[Web] Fix serve.py utility on Windows

IPv6 dual stack is disabled by default, and Windows resolves wildcard addresses to an IPv6 by default, so connecting through the local IPv4 address would not work.
This enables IPv6 dual stacking for the HTTP server by default like done in upstream python when launching the module from CLI.
Fixes #90695 .

Thanks!


Dracula for zsh-syntax-highlighting

New Theme -- zsh-syntax-highlighting

Implemented from the dracula template.

Implementation
This theme attempts to cover all possible zsh-syntax-highlighting options for the main highlighter. The coloring was implemented/modelled after the official Dracula color specification as much as logically possible.
As such, the theme is grouped by Dracula spec section; Each section in the spec is 1:1 with a ## <header> in the theme file. For settings that didn't seem to fall under any of the Dracula spec, they are under the ## No category relevant in spec section.
Within a section, the options occur in the same order they do on the main highlighter doc page.
Notes/Todo
The spec doesn't really line up 1:1 with this sort of work, so I tried to model as close as possible; I would not mind additional eyes inspecting my choices for the specific settings/associated spec groupings where possible (or maybe arguments on "ungrouped" ones being grouped into a different category).

This is great! As a user of zsh-syntax-highlighting myself, I really appreciate the work you've done here ;D
Can you transfer the repo now?
Cheers!

🚀
Done! Thanks Zeno.

https://draculatheme.com/zsh-syntax-highlighting 🎉 🎉 🎉


missing "subscription" type

when I use the CLI to generate type for my schema, one specific type is missing: "subscription"
Here's subscription_aggregate exists but missing "subscription"
/**
 * aggregated selection of "subscription"
 */
export interface subscription_aggregate {
  __typename?: "subscription_aggregate";
  aggregate?: Maybe<subscription_aggregate_fields>;
  nodes: Array<subscription>;
}

This means the generated schema is broken from the get go :(

I'm suspecting some kind of collision with GraphQL's 'Subscription'

I ended up using @graphql-codegen with the same config as gqty and added import {subscription} from ... to schema.generated.ts which seems to have solve the problem.
Less than ideal however...

gqty uses @graphql-codegen under the hood with some transformations, e.g. queries with inputs into functions, you cannot use substitute with types generated with @graphql-codegen directly.
I have been using gqty's generated types for AppSync subscriptions and is having no problem so far.
Would you help us reproducing the issue? Please share a minimum reproducing copy of the followings,

Your introspection source (*.graphql or endpoint)
The version of gqty
Your gqty config
Your working config for @graphql-codegen/typescript

No problem whatever I can do to help this awesome tool :)

I have a graphql.schema.json produced by @graphql-codegen is it good enough? graphql.schema.json.txt
"gqty": "^2.1.0"
gqty config:

/**
 * @type {import("@gqty/cli").GQtyConfig}
 */
const config = {
  introspection: {
    endpoint: "http://localhost:8080/v1/graphql",
    headers: {
      "x-hasura-admin-secret": "password",
    },
  },
  destination: "./src/utils/gqty/index.ts",
  scalarTypes: {
    ID: "string",
    String: "string",
    Boolean: "boolean",
    Int: "number",
    Float: "number",
    bigint: "number",
    bpchar: "string",
    date: "string",
    json: "any",
    jsonb: "any",
    numeric: "number",
    smallint: "number",
    time: "string",
    timestamptz: "string",
    uuid: "string",
  },
  preImport: 'import { subscription } from "./graphql";', \\ this is my hack :)
  enumsAsStrings: true,
  subscriptions: false,
  react: false,
  javascriptOutput: false,
};

module.exports = config;

codegen config:

module.exports = {
  schema: [
    {
      "http://localhost:8080/v1/graphql": {
        headers: {
          "x-hasura-admin-secret": "password",
        },
      },
    },
  ],
  overwrite: true,
  generates: {
    "./src/utils/gqty/graphql.ts": {
      plugins: [
        {
          typescript: {
            declarationKind: "interface",
            addUnderscoreToArgsType: true,
            scalars: {
              ID: "string",
              String: "string",
              Boolean: "boolean",
              Int: "number",
              Float: "number",
              bigint: "number",
              bpchar: "string",
              date: "string",
              json: "any",
              jsonb: "any",
              numeric: "number",
              smallint: "number",
              time: "string",
              timestamptz: "string",
              uuid: "string",
            },
            namingConvention: "keep",
            enumsAsTypes: true,
            allowEnumStringTypes: true,
          },
        },
        "typescript-operations",
      ],
      config: {
        skipTypename: false,
        withHooks: false,
        withHOC: false,
        withComponent: false,
      },
    },
    "./src/utils/gqty/graphql.schema.json": {
      plugins: ["introspection"],
    },
  },
};

I'm suspecting some kind of collision with GraphQL's 'Subscription'
BTW when I use @graphql-codegen it works fine, I have my subscription type. Is there an easy way to hook gqty with my generated types?

I did had a collision back then with a custom type: Subscription and ended up changing it's name (note: the missing type is subscription in lower case).

One more detail that might be relevant (not sure, just because it's that subscription again :): For some reason this specific snippet keeps complaining that: [gqty] Warning! No data requested.
  const subscription_id = await resolved(() => {
    const { id } = mutation.insert_subscription_one({
      object: {
        user_id: userId,
        bluesnap_plan_id: planId,
        bluesnap_subscription_id: subscriptionId,
      },
    });
    return id;
  });

  console.log(subscription_id);

I've used this exact pattern (with different entities) in multiple places but here for some reason it breaks, on the console I get:
[gqty] Warning! No data requested.
undefined

Switching to traditional gql client and query solved this problem but it's really curious.
I'm really not sure these are related issues, but that subscription is causing troubles all around laughing

The mutation require a refetch: true or noCache: true option, or you can use the mutate function helper that is exported by the client, which has automatically adds it, and it has the mutation object as parameter, instead of an empty object as the resolved function

const subscription_id = await mutate((mutation) => {
    const { id: subscription_id } = mutation.insert_subscription_one({
      object: {
        bluesnap_plan_id: String(planId),
        bluesnap_subscription_id: String(subscriptionId),
        user: {
          data: {
            is_premium: true,
          },
          on_conflict: {
            constraint: "user_pkey",
            update_columns: ["is_premium"],
            where: { id: { _eq: userId } },
          },
        },
      },
    });
    return subscription_id;
  });

still getting [gqty] Warning! No data requested. :cry:

After transforming it into a schema.graphql file, which is the standard SDL of graphql, it can be easier to see that it seems to be a name conflict
schema.graphql: https://gist.github.com/PabloSzx/b37cb0db6f7c0e4a06db8ec4189f26f7
In gqty the type "subscription" is reserved, you cannot use it as a regular type that can be returned from a query/subscription
here you can see that "gqty" uses the "subscription" name for the "subscription_root" in this case

and the schema.graphql defines it as a regular type

there is no plan to fix this use case, using "subscription" as a not actual GraphQL subscription is a bad practice

I'm suspecting some kind of collision with GraphQL's 'Subscription'
BTW when I use @graphql-codegen it works fine, I have my subscription type. Is there an easy way to hook gqty with my generated types?

Yes, exactly what I suspected...
Well, I found a workaround using @graphql-codegen,but will probably change the type's name eventually.
Thanks for the thorough investigation and concern for my issue, very much appreciated! :bow:


additional cow amm data

work with mike B what we can add additionally to AR

We'll stick to surplus apr for now


New Feature

Hello!
I use this tool and I thought it would be great if you could introduce a new function. It would be useful to have the option to create child skills that require 2 or more root skills to be complete. This would make it possible to illustrate tasks that require multiple prerequisites. I apologize if this feature is already present and I missed it.
Thanks,
V. Arui

Hello,
nice that you are using the tool and thanks for the feature request!
Our free and open source tool Easy-skilltree uses another open source code for the skilltree functionality:
React beautiful skilltree
The feature should be made possible in this software first, before I can incorporate it in the web application Easy-skilltree.
Therefore, it will be better if you request the feature on that repository! If the feature is accepted, I will then include it in the web application.
It sounds like a very interesting feature! And it does not yet exist.
Cheers,
Roeland

It even looks like someone else requested a similar feature on BST:
https://github.com/andrico1234/beautiful-skill-tree/issues/56


added wipeAppwriteCollection function in kotlin

Fixes https://github.com/appwrite/appwrite/issues/4104
Summary
This PR adds an example for Kotlin to wipe all documents in an Appwrite Collection.
Screenshots

Hello @Meldiron, Can you please review my PR?

Thank you so much for the PR 🤩. We're adding the hacktoberfest-accepted label to ensure this PR counts towards your Hacktoberfest contributions count. With that said, please stay active on this PR to address any comments once you receive a review. Happy Hacktoberfest! 🎃

Hey there 👋
We are temporarily closing your PR as there has been no activity on it. Feel free to re-open it when you're ready to start working on it again 😇


How to access the resource (model object) in a controller callback?

Let's say I want to increase the view count of a Post object in the controller below
class PostsController < ApplicationController
  include JSONAPI::ActsAsResourceController
  after_action  :increment_counter,         only: :show

  private

  def increment_counter
    # ???
  end
end

How do I access the model? I did a workaround on @request object like this:
  def json_api_resource
    operation_results = create_operations_processor.process(@request)
    resource_operation_result = operation_results.results.first
    resource_operation_result.try(:resource)
  end

  def resource
    json_api_resource.try(:model)
  end

But it breaks on 0.6.2. I know there's a callback on the OperationsProcessor, but on the README it's like for every resource, not on the individual resource level.

You should have access to the model as an instance variable @model. You can see the docs use it under attributes.

If you create an after_show_operation callback on a custom OperationsProcessor you will be able to access the @result, which will have the found resource as a member called @resource.
class CountingActiveRecordOperationsProcessor < ActiveRecordOperationsProcessor
  after_show_operation do
    #Do some counting related to
<EMAIL_ADDRESS>  end
end

If I'm reading it correctly, that's JSONAPI::Resource object. The
question is inside the controller.

Does that occur on every controller? How do I set this custom
OperationsProcessor to run the callback only to a certain controller?

Yes, it's a global callback for the OperationsProcessor. You could simply check the @operation.resource_klass. The operations are abstracted away from the controller, so if you really need to track per controller access to a resource this won't work.

@apraditya, you can hook in before rendering like this
class PostsController < ActionController::Base
  include JSONAPI::ActsAsResourceController

  def show
    define_singleton_method(:render_results) do |operation_results|
      result = operation_results.results[0]
      increment_counter(result.resource._model) if result.code == :ok
      super(operation_results)
    end

    super
  end
end

@apraditya (if you have no more questions, please close the issue)

Not bad. I'll use that for now. Thanks @vrybas

Another way to dig to the model is:
@operation_results.results.first.resource._model


fixing issue with number of 'active' panels

In a project, I used the side-reveal animation to go from one panel to another.
But I noticed that the number of 'active' panels on the page increases on each panel change.
This patch removes the 'active' class from the panel to hide, also when using the -reveal animations.
Thanks in advance for considering merging it.

A few people have reported issues around this.  One thing I'm worried about is transitions to new views and the active class being removed.  I'll pull this down and test it out.

Hey @jeroendeswaef .  I pulled this down.  You can see in some transitions with the active class removed, it creates a white background.  Check out the kitchen sink and click touch events in the bottom.  When it slides up, the previous view/panel is white.
If you can resolve this, I'll be happy to merge it!

This was resolved in another fix.  Thanks for this PR though


Add cancelOnDropOutside flag to improve UX on manual sorting

When Tree component is used to manual sort items, the user might drag items outside of the droppable area -- especially when trying to move it to the top or the bottom of the list. If we restrict the drop to only the tree area, we might have some weird behaviors, like rendering the placeholder somewhere, but not accepting a drop when the user releases
the mouse button for example.
The default is still only allowing drop inside the tree area, but by setting cancelOnDropOutside as false we allow drops outside of the tree whenever there's a placeholder being rendered.
This is an example of the original issue:
https://user-images.githubusercontent.com/836386/150551213-773a2696-ac69-47b9-abdd-c17523f4936f.mov

@lpagliari Thank you for contributing!
As you pointed out, there is indeed a problem with the drop being canceled even though the placeholder is visible. I also cloned and tested your repository.
One thing I'm having trouble with is that if I set cancelOnDropOutside = false, the drag will be dropped even if I explicitly try to cancel it with the ESC key.
I looked at the official documentation for react-dnd, but so far there is no way to determine why it was cancelled (ESC or Drop on outside) in the end of useDrag.
I'm wondering if I should accept the fact that if I set cancelOnDropOutside to false, the ESC key will also drop. (Although there may be few cases where the ESC key cancels the drag operation in the first place).

Oh, good point! I didn't check that scenario, we definitely should not call onDrop when ESC is pressed. Let me try to research a bit about this, will try to find a way to handle that.

@lpagliari Roger that. I haven't found a good solution yet either. I'm sorry for the PR you've done.
However, the problem you pointed out seems to have room for improvement, so I'll leave it as an Issue.


[Outlook] Fix NAA event sample not loading on older runtime versions

Q
A

Bug fix?
yes

New feature?
no

New sample?
no

Related issues?

What's in this Pull Request?
Older versions of Outlook Win32 event-based runtime does not support ECMAScript version that @azure/msal-browser dependency uses, so it is causing issues loading the launchevent.js bundle. Configure webpack to target ES6 when producing the bundle.

Approving, but isn't this only required in the "-IE" version of the NAA sample?

It also applies to the JavaScript runtime used by Outlook launch events for older versions of Office. The older versions don't support Nested App Auth, but they should by able to execute fallback logic.


Computed properties are cached we need method.

https://vuejs.org/v2/guide/computed.html#Computed-Caching-vs-Methods
closes #67
Signed-off-by: Yanko Belov<EMAIL_ADDRESS>

@belov91 this commit should fix it for you. Try running npm i  again just to play safe
https://github.com/ModusCreateOrg/beep/commit/7077abb7f5d34ad9341dbaa279933c763ce0c5ff

Otherwise good catch 👍

@grgur @belov91 I'd like to test this first, as the issue was present before it was refactored into a computed property


Non-enumerable properties on Array

Stanislas,
Thought you might like to use this version of your base.js which uses non-enumerable properties on the Array prototype. We were using your library and it caused some issues because another library was using for...in on arrays and got unexpected results.
Cheers,
Ben

require('./lib/base');

var a = [1,2,2,3,3];
console.log(a);

a.remove(2);
console.log(a);

console.log(a.unique());

for( var i in a ) console.log(i);

Great fixes. Thanks!

0.1.6 published with your fixes included!

Thanks for the speedy turn around!

np! :)


Where is the colour picker?

Hi,
Sorry for the noise, I am bit ashamed to ask this question but I am unavailable to find how to change the color for a metric (serie). Can you tell me how to do it and/or where I should look at? I am using 0.4.0-dev (81fd3f8). At the same time if someone - as a bonus question - what's the purpose of 'autoname series'.
I read to try to figure out:

https://github.com/facette/facette/issues/124
https://blog.facette.io/2014/07/31/facette-101/ (too old I guess)

Thank you and "Desole"
Thomas

Hi Thomas,
There is nothing to be ashamed of. We implemented the feature so naturally it seemed obvious to us. But I can understand that someone who never used it might not get it.
Please see the screenshot below:

Regarding series' auto-naming, it was designed as an helper to get all selected series having a unique name and it basically works like this:

by default series name contains only the metric name: cpu.0.idle
when the same metric is added multiple times for the same source, they are suffixed: cpu.0.idle (n) where n is an incremented counter
if the same metric is added for different sources, those sources are used as prefixes: source1/cpu.0.idle and source2/cpu.0.idle, the same goes for origins

Auto-naming if used by default when appending metrics to a graph. The button you mention in the UI serves to force series renaming, when their names have already been modified in the next creation steps or when you edit a graph afterwards.
Hope it helps.
Vincent

Hi Vincent,
Thanks for the quick reply. It's all crystal clear now.
I have to say the colour picker is well hidden, I think I would have
never found it. I kept looking on the right hand side of the series...
I reckon a doco update for that would be good. Hopefully noobs like me
will find this github issues to help them ;)
Thanks again, you can resolve the issue (if I can't ;-)
Otherwise, facette is great I kept an eye on it for more than a year and
I finally found the time to use it. When I have the time I will see if I
can build a RPM spec.
Cheers,
Thomas

Resolving. Questions have been answered.


WIP: critest: added a validation case for SupplementalGroups with the pre-defined groups in the container image

What type of PR is this?
/kind feature

What this PR does / why we need it:
In most cri implementations, at least containerd and cri-o, when the container's primary UID belongs to some groups in the container image, SupplementalGroups are just added to them even if SupplementalGroups does not include them (see https://github.com/kubernetes/kubernetes/issues/112879).
However, the behavior is not clearly stated in the API descriptions of SupplementalGroups both in kubernetes and cri-api.
To improve the situation, in https://github.com/kubernetes/kubernetes/pull/113047, I try to clarify the behavior in the API description of SupplementalGroups both in kubernetes and cri-api.
This PR added a test case to critest to validate the behavior as @haircommander recommended in  the k/k PR.
Which issue(s) this PR fixes:
ref: https://github.com/kubernetes/kubernetes/pull/113047#discussion_r997217751

Special notes for your reviewer:
Does this PR introduce a user-facing change?

/retest

I'm not sure why most ci jobs are canceled. How to rerun these jobs??


opentelemetry-instrumentation-aws-lambda silently fails to instrument files with the extension.cjs

What version of OpenTelemetry are you using?
Will be upgrading to the latest
"@opentelemetry/api": "^1.3.0",
"@opentelemetry/exporter-trace-otlp-http": "^0.34.0",
"@opentelemetry/instrumentation": "^0.34.0",
"@opentelemetry/instrumentation-aws-lambda": "^0.34.0",
"@opentelemetry/instrumentation-aws-sdk": "^0.33.0",
"@opentelemetry/instrumentation-http": "^0.34.0",
"@opentelemetry/sdk-trace-base": "^1.8.0",
"@opentelemetry/sdk-trace-node": "^1.8.0",
What version of Node are you using?
v16.x
What did you do?

https://github.com/baselime/lambda-node-opentelemetry-serverless-stack-v2
Here is a repo reproducing the issue
What did you expect to see?
Traces sent
What did you see instead?
lambda handler is not instrumented
Additional context
https://github.com/open-telemetry/opentelemetry-js-contrib/blob/96055281717d54305ff5c7b02b7a9d16c38dcea7/plugins/node/opentelemetry-instrumentation-aws-lambda/src/instrumentation.ts#L103 issue is this line of code does not handle all possible options supported by lambda node runtime

@willarmiros can you please look into this and the linked PR?

Thanks for getting this published!
I just saw this https://github.com/open-telemetry/opentelemetry-js/pull/3698 pr was closed!
I realize that makes my fix a little half baked. sorry .mjs files...
Should I make a new issue to track that @dyladan

Yes


Setting user passwords after tablet registration

Android user registration doesn't require the user to select a password, and therefore cannot login to kegbot server if they want to.  We need some kind of mechanism for a password-less user to set a password without logging into kegbot server (because they can't)

+1


✅ Add ConsumerMessageStore GenServer test

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#778  👈 (View in Graphite)
#776
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


MNE Recreations of EEGLAB processing pipelines

Proposed documentation enhancement
A while ago I was trying to recreate an EEGLAB Time-Frequency analysis pipeline in MNE and was having trouble getting my results to match. I made a forum post related to one of the MNE TFA parameters as well. See link. The answer was very helpful, but I still had trouble getting my results to match.
I was wondering if I (and others if anyone who is well versed in EEGLAB wants to help) could create some examples of showing how to recreate results from EEGLAB step-by-step.

crossref: #10750. Anyone interested in advancing this effort should comment there, not here.


Font size variables to be more precise and fail-proof

We've wondered with @Tumppex what's the best way of describing --font-size CSS vars. var(--font-size-extra-large) doesn't really tell enough. If we have layout that has a typographic scale from 14px all the way to 22px it causes us to form vars like var(--font-size-hugest-huge) which makes no sense (okay nobody has named that stupid yet but I'm trying to make a point).
This PR proposes to change this. From now on

We define font vars with initial pixel equivalent we can then transform to something else in-between breakpoints, here's an example:

:root {
  // Heading font sizes
  --font-size-h1: 51px;
  --font-size-h2: 38px;
  --font-size-h3: 28px;
  --font-size-h4: 21px;
  --font-size-h5: 17px;
  --font-size-h6: 14px;

  // Heading font sizes in mobile
  @media (max-width: $container-mobile) {
    --font-size-h1: 32px;
    --font-size-h2: 24px;
    --font-size-h3: 21px;
    --font-size-h4: 18px;
    --font-size-h5: 14px;
    --font-size-h6: 12px;
  }
}

And most notably:
  // Paragraph font sizes
  --font-size-14: 14px;
  --font-size-16: 16px;
  --font-size-17: 17px;
  --font-size-18: 18px;
  --font-size-20: 20px;
  --font-size-22: 22px;

  // Paragraph font sizes in tiny phones like iPhone 5S
  @media (max-width: 420px) {
    --font-size-16: 14px;
  }

At the same time we get rid of @mixin responsive-font although it may still come useful but nowadays we rarely find suitable use cases for it. In paragraphs it's insanity to scale in real time like 1-2 pixels and in headings the sizes will not always match so there's always a risk using it. Better to define breakpoint font sizes manually when needed and have some reliable sizes (as previous) as base.

Like in any other elements (like colors for example) we have defined some "pool of variables" which we can then use with --font-size-paragraphs for example. This way we can change it on the fly if needed without having to replace or rename whole bunch of vars. This gives us more flexibility.

We have media queries RIGHT UNDER so we can instantly see what the changes will be in different breakpoints.

What do you think?

Sounds like feasible and something that makes thing cleaner! Didn't spot any issues that would prevent merging.


fix(managers): correct manifest shared configuration

Description

correct manifest shared configuration
enable noImplicitAny: true
add sharedManager.normalizedOptions test

Related Issue
https://github.com/module-federation/core/issues/3101

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Checklist

[X] I have added tests to cover my changes.
[X] All new and existing tests passed.
[X] I have updated the documentation.

Amazing!


'collections[0].view_filters' should NOT have fewer than 1 items when NOT using view_filters

Describe the bug
I'm using the netlify-cms-app in order to leverage the cms as a static route within my react-static app. I'm very much using this experience as a template => https://formidable.com/blog/2020/oss-cms/
I'm using the netlify-cms-proxy-server
For some reason I keep getting this error when I am NOT using view_filters at all.
Error loading the CMS configuration
Config Errors:
'collections[0].view_filters' should NOT have fewer than 1 items
'collections[0].meta' should NOT have fewer than 1 properties
'collections[1].view_filters' should NOT have fewer than 1 items
'collections[1].meta' should NOT have fewer than 1 properties
Check your config.yml file.

My config.js file looks like this:
module.exports = {
  backend: {
    name: "proxy",
    proxy_url: "http://localhost:8081/api/v1",
    branch: "master" /* optional, defaults to master */,
  },
  media_folder: "public/uploads",
  public_folder: "/uploads",
  collections: [
    {
      name: "blog",
      label: "Blog Post",
      folder: "src/_blog-posts",
      create: true,
      slug: "{{year}}-{{month}}-{{day}}-{{slug}}",
      fields: [
        { label: "Layout", name: "layout", widget: "hidden", default: "blog" },
        { label: "Title", name: "title", widget: "string" },
        { label: "Publish Date", name: "date", widget: "datetime" },
        {
          label: "Featured Image",
          name: "thumbnail",
          widget: "image",
        },
        { label: "Body", name: "body", widget: "markdown" },
        { label: "test button", name: "testButton", widget: "string" },
      ],
    },
    {
      name: "events",
      label: "Event",
      folder: "src/_events",
      create: true,
      slug: "{{year}}-{{month}}-{{day}}-{{slug}}",
      fields: [
        { label: "Layout", name: "layout", widget: "hidden", default: "event" },
        { label: "Title", name: "title", widget: "string" },
        { label: "Publish Date", name: "publish_date", widget: "datetime" },
        { label: "Event Date", name: "event_date", widget: "datetime" },
        { label: "Featured Image", name: "thumbnail", widget: "image" },
        { label: "Body", name: "body", widget: "markdown" },
      ],
    },
  ],
};

My understanding is that view_filters is optional, and that meta is not even something that can be updated.

This error doesn't come up all the time. But if I make changes to my config.js, it will definitely come up.

Hi @AJTJ, can you share your config.yml as well and the way you initialise the CMS with the config.js file?
A link to the site/repo would help too

@erezrokah I don't have a config.yml (well, I do, but everything is commented out)
the repo is here: https://github.com/AJTJ/ylc_website
Here is how I've initialized the CMS: https://github.com/AJTJ/ylc_website/blob/master/src/CMS/index.js
And it is loaded as a static route here (through react-static):
https://github.com/AJTJ/ylc_website/blob/master/static.config.js

Same comment as https://github.com/netlify/netlify-cms/issues/3996#issuecomment-658061682

Closing due to https://github.com/netlify/netlify-cms/issues/3996#issuecomment-662981049


pulsar-mel2 temporarily offline

Setting pmel2 offline for a short time to reboot the pulsar head VM

cannot reboot the head with running jobs, I'll close this


SEO related: canonical tags of 44 URLs need to be replaced

The issue: The canonical tags of 44 URLs are pointing to redirected pages. As a result, search engines fail to crawl and index the pages properly. https://docs.google.com/spreadsheets/d/13ILZY5Hh3CyuwX3qNlAn-hyEpr-HN0iDMHUL9FBzr74/edit#gid=0
The solution: To replace the current canonical URLs with self-referencing canonical tags.
If additional info is needed, please let me know.
Resources to look at:
1. Previous discussions on slack: https://aiven-io.slack.com/archives/C01SY3QU54P/p1654697321714689
Also, Angeline suggests: "we can use Netlify redirect for the issue with index.html (row 23-44)
But there is also this sitemap that has index.html and .html in all places https://developer.aiven.io/sitemap.xml -> this can also be configure i assume"
2.Educational useful materials:

Canonical tags: https://www.semrush.com/blog/canonical-url-guide/?kw=&cmp=DE_SRCH_DSA_Blog_Core_BU_EN&label=dsa_pagefeed&Network=g&Device=c&utm_content=515771357185&kwid=dsa-1057183191115&cmpid=11794204941&agpid=114887190419&BU=Core&extid=23661292104&adpos=&gclid=CjwKCAjw14uVBhBEEiwAaufYx7izGDIDsuLlNGvFyz9l24yrht5c5sqRK1JtFhkiLJCA4aONTJZHmBoCLMMQAvD_BwE

Redirection - https://djtechblog.com/seo/redirect-default-index-html-to-root-seo-basics/#:~:text=In simple words we should,should always redirect to root

@edithyeghiazaryan, one clarifying question -  "fail to crawl and index the pages properly" - what do we mean by "properly" here? are they ignored completely go google search engine?

@anelook
Olena, thank you for the question. From the crawlers’ perspective, these pages are canonicalized to non-indexable URLs, which is a paradox for them. As a result, the rankings, impressions, and clicks will drop for these pages if they haven’t dropped already.
Let me give more info; Crawlers assign crawl budget (time) to websites because they don't have unlimited resources. To benefit from this situation, our goal is to help crawlers find and understand our indexable pages as many and quickly as possible and not face barriers during that process (such as now). For that, we need to eliminate the technical issues (part of tech SEO), optimise the content and keywords (on-site SEO) and increase the authority of our website (off-site SEO). If all these problems are solved and opportunities are grabbed, we witness better ranking on search engines, can be easily found by users on diff. search engines, beat our competition easily, get higher clicks and conversion etc. So, these are the goals we are trying to achieve. I hope I could answer your question :))

Findings after looking into the issue deeper.
Different scenarios and behaviours:

Every page can be accessed using suffix .html. When accessing following pages

https://developer.aiven.io/docs/products/opensearch/index.html
https://developer.aiven.io/docs/products/m3db/index.html
https://developer.aiven.io/docs/products/opensearch/index.html
will work without redirects, no 301

When accessing the root folder, the server recognises that we look for index.html and returns us correct page, for example

https://developer.aiven.io/docs/products/opensearch/
https://developer.aiven.io/docs/products/m3db/
https://developer.aiven.io/docs/products/opensearch/
will work without redirects, no 301

"index" without ".html" is not a valid page name and the server will need to redirect. This seems to rely currently on Netlify functionality, because when running locally, or in sphinx-docs website (https://www.sphinx-doc.org/en/master/usage/index.html) entering path without ".html" will return 404: Not Found

My understanding that our issue comes from the fact that we use pages without ".html" suffix as canonical links. for example
<link rel="canonical" href="https://developer.aiven.io/docs/products/clickhouse/index" /> These pages are not canonical. This setting comes from _templates/base.html
Possible solutions:

Taking the example from https://www.sphinx-doc.org/ (reference - https://github.com/sphinx-doc/sphinx/blob/5.x/sphinx/themes/basic/layout.html)we can change the template from <link rel="canonical" href="https://developer.aiven.io/{{ pagename }}" /> to <link rel="canonical" href="{{ pageurl }}" />. This gives a proper url of the page with .html. Works for both "/index.html" and "/" and always sets canonical to "/index.html".
However, the problem of this solution - Google will need to reindex all our pages again, because they all already indexed without ".html".

Use the solution of @ftisiot  to exclude "index" for all our "index" pages. This is more difficult to maintain and potentially error prone, but this will be aligned with how Google already indexed all the pages.

@lornajane let's discuss this as well, I'm curious if you might have other ideas how to approach this :)

I intentionally indexed without the .html because I don't think it makes the URLs easier for people to read, so it was a UX decision - I didn't realise that the index pages were special. I wondered if we could stop using index pages altogether and have, for example in /docs/products both the landing page clickhouse.rst for a URL of /clickhouse and then the pages inside a clickhouse/ directory as we do now. The concept/howto/reference sections work with way with same-named pages and directories, and don't seem to display the same problem. I am not clear if this would be an option though.

@lornajane you suggestion will fix current SEO issue. However, this solution will mean that
http://<IP_ADDRESS>:8000/docs/products/kafka/kafka.html <- will work
http://<IP_ADDRESS>:8000/docs/products/kafka/ <- won't work any more by default
And I think this is inconvenient for users, when we open a folder we want to redirect to the main page of it.
Possibly it can be changed with Netlify settings so that default page to open no longer index, but the page with the same name as the folder? But this will require additional logic we need to support later.
Also, many would expect index to be main page of the folder, this change might add confusion.
@edithyeghiazaryan , do you know if search engines treat "index" pages differently and if there are any other risks if we rename them?

@anelook  Search engines do not care much about the endings a URL has.
However, if we make a URL structure change now, it will be considered a website restructuring. This means crawlers need to reindex those pages, which will take time. Meanwhile, we will have traffic drop (highly not desirable). Moreover, that kind of URL structure is not UX friendly. Therefore, the best approach would be to keep the current URLs as they are now (Column B https://docs.google.com/spreadsheets/d/13ILZY5Hh3CyuwX3qNlAn-hyEpr-HN0iDMHUL9FBzr74/edit#gid=0) and change only the canonical tags.

@anelook  Search engines do not care much about the endings a URL has.
However, if we make a URL structure change now, it will be considered a website restructuring. This means crawlers need to reindex those pages, which will take time. Meanwhile, we will have traffic drop (highly not desirable). Moreover, that kind of URL structure is not UX friendly. Therefore, the best approach would be to keep the current URLs as they are now (Column B https://docs.google.com/spreadsheets/d/13ILZY5Hh3CyuwX3qNlAn-hyEpr-HN0iDMHUL9FBzr74/edit#gid=0) and change only the canonical tags.

@edithyeghiazaryan for me it feels that in the column B we should have URL with full path to the file, meaning all files with + "index.html", for example https://developer.aiven.io/docs/products/postgresql/index.html <- this is the real full URL.

@anelook If this is the real full URL https://developer.aiven.io/docs/products/postgresql/index.html
we have no issue keeping it.
Overall we need to consider the following things;

keeping only one version of the URL, the other one should be redirected. 1 URL = 1 piece of content otherwise duplication is created. (https://developer.aiven.io/docs/products/postgresql/ should be 301 redirected to the above-mentioned one if we decide to keep that one)
every URL should contain a self-canonical tag
keeping the number of redirects as low as possible and not create redirect chains (https://www.contentkingapp.com/academy/redirects/faq/redirect-chains/ )

Regarding 1. - Redirection is not needed in this case.  "https://developer.aiven.io/docs/products/postgresql/" is the same as "https://developer.aiven.io/docs/products/postgresql/index.html". Both will show same canonical URL (if you check their source code), there is no redirection there - the web server is smart enough to know that when we open  the folder "https://developer.aiven.io/docs/products/postgresql/" we mean that we want to see a default page inside it (usually index.html) "https://developer.aiven.io/docs/products/postgresql/index.html"

The current flow seem to be tangled with behaviour of Netlify.  When not using the server, opening a page without ".html" leads to 404.
To see it, you can run the developer portal locally and try opening
http://<IP_ADDRESS>:8000/docs/products/postgresql/index -> 404
http://<IP_ADDRESS>:8000/docs/products/clickhouse/getting-started -> 404
Because we're moving away from Netlify, we need to understand if the current flow will continue to be supported. This can influence which of the solutions we need to use.
@angelinekwan, do you know by any chance what settings in Netlify are responsible for default directory listing (where it is set to use index.html)? Maybe there we have also a setting which redirects "index" to "/"?

@lornajane, related to our conversation on Friday, I found a long thread on quora about including or excluding ".html" from SEO urls. Supports your reasoning that generally doesn't give any advantage  -  https://www.quora.com/Is-it-beneficial-for-SEO-to-end-URLs-with-html

@anelook If we do not put a redirection, then both pages will continue to rank as it is happening now (status 200), resulting in a duplication issue.
Please see the screenshot illustrating that both pages are generating traffic currently. Any thoughts?

@edithyeghiazaryan  Adding an artificial redirection (with 301) from https://developer.aiven.io/docs/products/postgresql/index.html  to https://developer.aiven.io/docs/products/postgresql/ feels to be wrong to be honest. Maybe it fixes SEO, but it delays the page load  and requires a separate request that is not needed.
I also wonder if the number for "https://developer.aiven.io/docs/products/postgresql/" will go down if we remove redirects from "https://developer.aiven.io/docs/products/postgresql/index" to "https://developer.aiven.io/docs/products/postgresql/".

@anelook It's vice versa, putting 301 from https://developer.aiven.io/docs/products/postgresql/ to https://developer.aiven.io/docs/products/postgresql/index.html  since you mentioned in previous messages that the latter is the real full URL.
The idea is to have only one version of the URL (1 URL=1 piece of content, and the URL structure's ending doesn't matter for this case). This is not only for the SEO but for you or other team members as well; in the future, when you link any content to this URL, it will be easier to know which URL to link to since there will be only one version instead of 2.
Moreover, if you have these backlinks divided between 2 versions of the same page (e.g. you create a piece of content and link to https://developer.aiven.io/docs/products/postgresql/, another person creates another content and links to https://developer.aiven.io/docs/products/postgresql/index.html), then the page authority for these pages won't increase as it supposes to, affecting the webpages' rankings negatively.
Then, since the rel=:canonical" attribute is a hint, not a directive, they may be ignored by search engines resulting cannibalization issue. It means that both pages compete with each other resulting a traffic drop.

Regarding the speed - Please let me know how you think it will affect for each page and after which exact actions? This is how I see the picture;
the https://developer.aiven.io/docs/products/postgresql/  will be disappeared after some time from the search engines,
https://developer.aiven.io/docs/products/postgresql/index.html will not have any changes regarding the speed. If there is anything else that doesn't come to my mind, please let me know.

Regarding being right from the SEO perspective but not suitable from a technical standpoint - both of their goals are the same - to be present on search engines properly (eventually, our target audience finds the content on google search engine). Thus, following their documentation/rules should not be wrong, I believe.
Sending you some useful documentation from Google on how websites need to be structured technically correct so that it doesn't harm the overall website.
https://developers.google.com/search/docs/advanced/guidelines/duplicate-content
https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls

Regarding your last question - I don't follow, which redirect? Please paraphrase it if I haven't covered the answer in this message yet.

@edithyeghiazaryan, taking example from https://developers.google.com/

they have both https://developers.google.com/search/index.html and https://developers.google.com/search/ and there is no redirections between those pages even though they have the same canonical url. They both point to the same resource. Does it mean they also do it incorrectly?

Let's stick to the topic. Thanks @edithyeghiazaryan for the explanation of what's needed. We'll work on this when we can and keep you posted!

@lornajane @anelook Thank you for the updates! Everything looks good, except these 2 links.

https://developer.aiven.io/index.html
https://developer.aiven.io/

Could you also please

put a 301 redirect from https://developer.aiven.io/index.html to https://developer.aiven.io/
put a self-canonical tag on the https://developer.aiven.io/

I will send the rest of the URLs to get indexed.

I indeed left one index page  - https://developer.aiven.io/index.html, as I couldn't come up with a good alternative name for it.
@lornajane what's your opinion? should we replace "index" with "main"? I can also add a redirect from  https://developer.aiven.io/index.html to  https://developer.aiven.io/, which will be much cleaner for a starting page. Though I'm not really happy with adding extra redirect for SEO only.

@edithyeghiazaryan, we covered 43 links as part of the merged PR.
The landing index.html has to be solved differently.  I'd suggest that we close this ticket and create a specific one for https://developer.aiven.io/index.html and https://developer.aiven.io/ ? This will make it easier to organise the work and keep an eye on this part.


Ensure warnings fail

Current dependencies on/for this PR:

main:

PR #3 👈

This comment was autogenerated by Freephite.


Catching solver errors to py logging

I'm using the python API (v7.1) to solve MIPs with CPLEX; is there a way to use the Python logging library to also catch errors from linear_solver.cc such as the one shown below?
E0722 16:43:13.275576 17668 linear_solver.cc:1511] No solution exists. MPSolverInterface::result_status_ = MPSOLVER_ABNORMAL

I've got python setup to log all STDERR but the message above doesn't seem to get caught.

This is cplex output. I do not know where it is send.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le lun. 22 juil. 2019 à 09:53, Constantino Schillebeeckx <
<EMAIL_ADDRESS>a écrit :

I'm using the python API (v7.1) to solve MIPs with CPLEX; is there a way
to use the Python logging library to also catch errors from
linear_solver.cc such as the one shown below?
E0722 16:43:13.275576 17668 linear_solver.cc:1511] No solution exists. MPSolverInterface::result_status_ = MPSOLVER_ABNORMAL
I've got python setup to log all STDERR but the message above doesn't seem
to get caught.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1442?email_source=notifications&email_token=ACUPL3LTH5NGQWBDIYY27XTQAXQYJA5CNFSM4IF2LDA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAVYSUA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3NEJ2IMIEPT76O6J4LQAXQYJANCNFSM4IF2LDAQ
.

Sorry, answered too fast.
Do you see some comments about InitLogging not called ?

Do you see some comments about InitLogging not called ?

I do yes, but wasn't sure what to do with it. I couldn't find much documentation on it.

So, in python, I do not yet call InitLogging automatically with the linear solver. It is done with the CP-SAT. So it outputs the first error message. Now, there is no easy way to change the output of the glog library from python.
This being said, this is an error message. You are trying to access the solution, while (1) you have not called Solve(), or (2) the solve did not find a solution, and you forget to check the return status before querying the solution.


convert twitter additional entities to csv + date_limit for not streaming accesses

The function to convert twitter additional entities to csv is now tested for all the possible entities of a tweet (hashtags, user_mentions, urls, media), of a user (urls), and for place (including bounding box)

Includes date limit functionality to tweets method for rest api (i.e. not streaming). Api of the method does not change. The param date_limit has different meaning when either streaming or not; in streaming it is a date in the future, if not, it is a date in the past

Thanks @lrnzcig.  It would be good to have some demo code for this new functionality, either in the twitter_demo.py file or else in the iPython notebook. I might try to restructure twitter_demo.py to make it easier to add new examples while still making it possible to select which demo to run.


ASG Failed scale up after update aws_launch_template with aws provider 2.61.0 (currently latest version)

I have an issue when I update aws_launch_template with provider.aws=2.61.0.
I'm submitting a...

[x ] bug report
[ ] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
The latest terraform provider rolled out a new improvement with in MR. It will set "partition_number" to 0 when you not handle it at placement. This will cause ASG failed to launch instance with error
Launching a new EC2 instance. Status Reason: Could not launch Spot Instances. InvalidParameterValue - You cannot use PartitionNumber with a Placement Group that does not exist. Specify a valid Placement Group and try again. Launching EC2 instance failed.
If this is a bug, how to reproduce? Please include a code sample if relevant.
Use aws provider 2.61.0 (currently latest version), update any launch template and apply
What's the expected behavior?
ASG will failed to scale up
Are you able to fix this problem and submit a PR? Link here if you have already.
NA
Environment details

Affected module version:
OS: mac
Terraform version: 0.11.14

Any other relevant info

I've put a fix in #875. Can you confirm that it fixes your issue?

HI @dpiddockcmp , thanks for fix. It do solve our issue when we didn't set "launch_template_placement_group" in "var.worker_groups_launch_template".
But since we do not handle "partition_number" in "placement" block, for users want to set "group_name" to "Partition", the partition_number would be become 0 which is an illegal value. I guess this depends how they gonna fix for issue #13236 in terraform-aws-provider.

Reopening until a fix is merged upstream or in this module.

For us reverting to provider 2.60.0 didn't fix the problem. No proposed changes by TF (likely simply ignores anything related to partition number).
Reverting to previous launch template version stopped the bleeding (be sure not to revert to incompatible AMIs or anything).
Trick to fix if having broken asg via provider 2.61.0: Pin provider to 2.60.0, trigger a new launch template version by for example increasing disk space from 100 to 105.


Broken PR comment report for Bitbucket Cloud

Hi there, first, thanks a lot for this fantastic project!
I've integrated infracost in our Terraform CI and for some reason the UI markdown for comments in PRs (Bitbucket Cloud) are broken. The "Cost details" h3 is rendered within a row in the summary in plain markdown.
.
I'm using the Docker image infracost/infracost:ci-0.10 and the command I'm using to post the comment is:
infracost comment bitbucket --path infracost.json --repo $BITBUCKET_WORKSPACE/$BITBUCKET_REPO_SLUG --pull-request $BITBUCKET_PR_ID --bitbucket-token $BITBUCKET_TOKEN --behavior update

My Bitbucket pipeline looks like the following:
pipelines:
  pull-requests:
    '**':
      - step:
          name: Terraform plan
          image: hashicorp/terraform:1.6.6
          script:
            - terraform init
            - terraform plan -out plan.binary
            - terraform show -json plan.binary > plan.json
          artifacts:
            - plan.json
      - step:
          name: Infracost
          image: infracost/infracost:ci-0.10
          script:
            - infracost diff --usage-file infracost-usage.yml --path plan.json --format json --out-file infracost.json
            - infracost comment bitbucket --path infracost.json --repo $BITBUCKET_WORKSPACE/$BITBUCKET_REPO_SLUG --pull-request $BITBUCKET_PR_ID --bitbucket-token $BITBUCKET_TOKEN --behavior update

I suspect it has to do with the markdown template.
Please let me know if I can help in any way! Thanks a lot!

hi @keyvanakbary, thanks for reporting this. This looks like a degredation that was introduced in the 0.10.31 release. We'll put out a fix for it which will go into the next release. In the meantime I recommend you pin your pipeline to the 0.10.30 release as this doesn't have this bug

I'll do that, I'll keep an eye for the next release too :)
Thanks a lot @hugorut!

BTW It looks like it happens in 0.10.30 too :sweat_smile:

@keyvanakbary yup, thanks for checking back, the 0.10.29 should be safe to use

@hugorut is the fix live? if so, can you please close this?

yes it is live

Thanks a lot folks!


feat: Add documentation for the stages

Feature or Bugfix

Documentation

Detail

Add documentation for the stages

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: d7462a21b89e0c9dd8728712168c81f7df0e953d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


SSH2Stream: Add openssh_authAgent method

Hi! I didn't find a way to open authentication agent channel on server stream which has been a major drawback for my application to utilize SSH. I'd be happy to implement agent forwarding feature in mscdex/ssh2 once this gets merged.

Thanks, but support for this was already added recently.


Refactor & Test & Docs

[x] Refactor for readability
[x] Test
[x] Support oneof
[ ] Docs

Wonderful work. How about adding test cases involving following attributes?

prost_type
omit_type_errors
use_default_for_missing_fields
ignore_unknown_fields

@segfault87 I added the test for options(omit_type_errors, use_default_for_missing_fields, and ignore_unknown_fields)(prost_type is not a option, but for parsing prost type for oneof handling)


[full-ci] Test Async Uploads

Testing pipeline with async uploads

Closing as follow-up is here https://github.com/owncloud/ocis/pull/5268


Fine-tuning

Hi Guilla, I'm trying to fine-tuning a previous model that I trained. After I load the weights I get an error (shapes mismatch). I saw in the code that the shapes are [None,None ...].
Should I reshape ( Will I lose information doing that? )
I just need to retrain the last layer everything else will work as feature extractor.
I appreciate any help on that.

Hi,
I just pushed a new version with a new function in the base model reinitialize_weights that reinitializes the variables of a given scope. This should do what you want. (call it on the "proj" layer, like I wrote in train.py)
You shouldn't have shape mismatch. Check that you load the correct files and you haven't modified the graph you are trying to load.
Once you have reloaded your weights, you can also choose to add new parts of the graph (like a final layer with more items) but in that case, it should be a new element of the graph, with a different name and scope (otherwise tf.saver will try to load the model into this tensor and you'll get a shape mismatch). So if that's what you want to do, I advise you to create new elements of the graph. Consider also defining a new loss that only depends on the variables of the last layer.
Best,
Guillaume

Thanks Guillaume, was exactly what I needed.
Regards
Rafael


can this plugin autocompile java file?

https://github.com/artur-shaik/vim-javacomplete2/issues/55
some config in my .vimrc
Plugin 'artur-shaik/vim-javacomplete2'
Plugin 'airblade/vim-rooter'
let g:rooter_patterns = ['Rakefile', 'web.xml']
let g:JavaComplete_LibsPath = 'classes/:lib/:/home/wsdjeg/tools/apache-tomcat-8.0.24/lib'

in the WEB-INF dir contains  classes/   lib/   src/ and    web.xml
the plugin rooter helps me set the pwd WEB-INF/
all the necessary jar is  included in lib/
java file is included in the src/
class file is included in the classes/
I want to compile the file when save it!
Maybe this function would be the best solution?
Like add this to vimrc
let g:javacomplete_compile_on_save = 1  "default is 0
let g:javacomplete_compile_outputdir = 'classes'

You don't need syntastic for that.  Set up Vim to compile your project when you run :make (in particular, see :help :make_makeprg and :help compiler-select).  When this is working to your liking, automate it with an autocmd:
autocmd BufWritePost * nested make

it does not work ,misss the jar in lib/

It's up to you to make it work.  It still has nothing to with syntastic, which is about checking syntax, not about running builds.