granite_orm vs granite-orm

I noticed that we have underscore for the name and then dash for the github repository.  I think it would be better to have some consistency here to make it easier to configure.

I agree although the convention from ruby is definitely underscores except
for urls. Crystal seems to have the same standard in the core and most of
the projects.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER>
On Mon, May 22, 2017 at 4:38 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

I noticed that we have underscore for the name and then dash for the
github repository. I think it would be better to have some consistency here
to make it easier to configure.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kemalyst/granite-orm/issues/37, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHmpN4EHXeTKYZLt6Ls5G6NWtVyShV3ks5r8g5wgaJpZM4Ni-G4
.

Most of the github repos for crystal are using dashes in the project name. I would stick with that convention.
Sent from my iPhone

On May 22, 2017, at 4:58 PM, Isaac Sloan<EMAIL_ADDRESS>wrote:
I agree although the convention from ruby is definitely underscores except
for urls. Crystal seems to have the same standard in the core and most of
the projects.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER>
On Mon, May 22, 2017 at 4:38 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

I noticed that we have underscore for the name and then dash for the
github repository. I think it would be better to have some consistency here
to make it easier to configure.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kemalyst/granite-orm/issues/37, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHmpN4EHXeTKYZLt6Ls5G6NWtVyShV3ks5r8g5wgaJpZM4Ni-G4
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Actually, I take that back. I see a mix of project names with both underscores and dashes. Hhmm.
Sent from my iPhone

On May 22, 2017, at 6:00 PM, Dru Jensen<EMAIL_ADDRESS>wrote:
Most of the github repos for crystal are using dashes in the project name. I would stick with that convention.
Sent from my iPhone

On May 22, 2017, at 4:58 PM, Isaac Sloan<EMAIL_ADDRESS>wrote:
I agree although the convention from ruby is definitely underscores except
for urls. Crystal seems to have the same standard in the core and most of
the projects.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER>
On Mon, May 22, 2017 at 4:38 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

I noticed that we have underscore for the name and then dash for the
github repository. I think it would be better to have some consistency here
to make it easier to configure.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kemalyst/granite-orm/issues/37, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHmpN4EHXeTKYZLt6Ls5G6NWtVyShV3ks5r8g5wgaJpZM4Ni-G4
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I asked on 2 separate days in the crystal gitter and the consensus was
underscores although some programs do use hyphens. I believe everything in
at github.com/crystal-lang/* used underscores though. It's your project
though and either work. I've been in ruby so long that hyphens just seem
really weird to me though.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER>
On Mon, May 22, 2017 at 7:09 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

Actually, I take that back. I see a mix of project names with both
underscores and dashes. Hhmm.
Sent from my iPhone

On May 22, 2017, at 6:00 PM, Dru Jensen<EMAIL_ADDRESS>wrote:
Most of the github repos for crystal are using dashes in the project
name. I would stick with that convention.
Sent from my iPhone

On May 22, 2017, at 4:58 PM, Isaac Sloan<EMAIL_ADDRESS>wrote:
I agree although the convention from ruby is definitely underscores
except
for urls. Crystal seems to have the same standard in the core and most
of
the projects.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER> <(435)%20669-5005>
On Mon, May 22, 2017 at 4:38 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

I noticed that we have underscore for the name and then dash for the
github repository. I think it would be better to have some
consistency here
to make it easier to configure.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kemalyst/granite-orm/issues/37, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/
AAHmpN4EHXeTKYZLt6Ls5G6NWtVyShV3ks5r8g5wgaJpZM4Ni-G4>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kemalyst/granite-orm/issues/37#issuecomment-303261685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHmpHIpd6UNkui5AP98kdAwAFjVnnVdks5r8jHBgaJpZM4Ni-G4
.

:+1:


queue:listen --tries not working with --delay

When I'm running php artisan queue:listen --tries=10 --delay=10 failed jobs are not moved to the failed_job table after 10 tries, they are only delayed for 10 minutes.

The queue.failed.database setting was incorrect.


The progress thingy doesn’t seem to show the data wasted

I ran it for a min now and it still have 0 speed and 0 mb wasted

 I ran it for a min now and it still have 0 speed and 0 mb wasted

First of all thank you for creating issue xd its my first issue
Second i looked into the system and saw the server was down from where the waste data comes froml.
In simple words i have fixed the server and now its back into its working state.
Mark Close if it solved you're issue

Ok thanks
yea i was wondering why there was no issue


TraceRunnable does not let you to get delegate and extract context data.

Hi,
when I use TaskExecutor and tracing autoinstrumentation from spring-cloud-sleuth then it is problematic to handle rejected tasks.
My task are custom implementations of Runnable, and they contain tenant info.
If the task fails, I want to get this tenant info and process.
But unfortunatelly, that is not possible, as TraceRunnable does not have methods that would allow me to get the delegate Runnable - in my case my custom Runnable implementation.
Example lines of code:
    private RejectedExecutionHandler createRejectedExecutionHandler(ServiceInitializer serviceInitializer) {
        return (task, executor) -> {
            if (task instanceof XXXRunnableClass) { // this will never be the case, as it always will be `TraceRunnable`, which is created in `org.springframework.cloud.sleuth.instrument.async.LazyTraceAsyncTaskExecutor#execute(java.lang.Runnable)`

Describe the solution you'd like
I would be happy if TraceRunnable provides method Runnable getDelegate()
Describe alternatives you've considered
Alternatively, i could use TaskExecutor which is not wrapped with LazyTraceAsyncTaskExecutor and do tracing on my own, but i dont like reimplementing and maintaining that solution.
The second approach could be to use reflection with casting but, ... that would be ugly as well...
Additional context
I am using spring boot 2.7.8

I don't see a problem with adding that - are you willing to file a PR ?

Same thing could be done for TraceCallable

I also have the same use case, I could file a PR for it.

Be my guest. Please do it for the trace runnable and callable.


Search Engine

Make up the search engine. Until several users ask in this post, this is a very low priority task.

+1


Upgrading the styled component packages

Upgrading the styled-components and babel styled components packages!

@mxstbr could you have a look?


Error output after install Aurora SDK

After install SDK: aurora-cli sdk install --install-type offline in terminal show info about install SDK.

Fix


Add xz as a standard Compressor

xz is a better compressor than bzip2 in many cases. I propose to add it to backup as one of the standard Compressors.

This should probably be moved to https://github.com/backup/backup-features . Sorry, I haven't noticed that repo before.

Hi @gdubicki you can already really easily add another compression method http://backup.github.io/backup/v4/compressor-custom/


options: add uninstallUnused option

This PR introduces the capability to automatically uninstall unused packages by running flatpak uninstall --unused during activation or a scheduled update execution.
A new services.flatpak.uninstallUnused option is added, defaulting to false. This option is independent of services.flatpak.uninstallUnmanaged.
However, enabling services.flatpak.uninstallUnmanaged will automatically enable services.flatpak.uninstallUnused.
Closed #96

This is light on unit tests, but coverage should improve after a planned refactoring of installer.nix.


grappling-hook

Hi @vkarpov15
First a little background before I come to my question. I'm a core team member of keystone and recently we needed some hooking functionality. So I started scouring over the many hooking modules (hooks, hooks-fixed, kareem, etc) and thought kareem definitely looked the most promising. However, we also needed a bunch of things that weren't provided out-of-the-box so at first I tried to adapt kareem to our needs. As it always goes, I ended up writing my own hooking module from scratch, thinking it would be faster to write one than adapting yours (it probably wasn't :smile: )
Anyway, this became grappling-hook. Due to the fact we use and expose mongoose in keystone I really wanted to make the pre and post registration API compatible to mongoose's, in order to present users with a single hooking API, whether they're hooking into mongoose or keystone. It's not 100% compatible ATM, but will be pretty trivial to do so.
Anyway, I can imagine you have a LOT of work with mongoose and was wondering if you'd be interested in considering using grappling-hook in mongoose. I had a superficial look at mongoose and it seems to me it would cost me very little effort to make grappling-hook a drop-in replacement for both kareem and hooks-fixed, but providing a bunch of extra functionality out-of-the-box, e.g. parameter passing to pre middleware, more granular control over post sequencing, a number of sugary methods which allow you to introspect middleware et cetera.
Granted, it was a superficial look and I'd definitely need to compare performance with kareem. In our case performance is not such an issue, so I definitely haven't optimised the hell out of it.
Just giving you a heads-up that I wrote something similar, and will actively maintain it, with promises integration on the roadmap for instance.
Please do not misunderstand me, I'm not suggesting this because kareem is badly written or so AT ALL (again: AT ALL). My main motivation is that I really want to help make keystone the best it can become and to us it would be really cool to be 100% sure the hooking mechanism in keystone and mongoose is identical. And the benefit I think it could have for you is being freed of a small yet essential part of functionality of mongoose.
If it doesn't interest you: I TOTALLY understand, if so, sorry for bothering you with this silliness.

Worth noting - I consider hooks and hooks-fixed to be deprecated. hooks-fixed only exists because I don't have push access to hooks and hooks has several critical bugs. grappling-hook is worth investigating, I like the idea of collaborating on code where possible, but there are 3 features / things that I really need from a hooks library going forward -

Executing hooks attached to a different object. In mongoose we need to recreate hooks every time we create a new doc or subdoc, which is pretty wasteful (see Automattic/mongoose#2809). Much of the point of kareem was "attach hooks once to schema, call them from wherever" as opposed to "execute complex logic to add hooks to prototype every single time a doc is created." I may be able to implement this with callHook's context param but I want to be sure.
100% test coverage. It's not a guarantee of being bug-free, but it's a good start.
Promises support. See Automattic/mongoose#2754. Mongoose does a lot of nasty things to make hooks play nice with promises. Kareem doesn't have built-in support for promises, but being able to do execPre(), execPost(), and wrap() gives me the ability to just use mongoose's promises.

I'm curious to see if I can do 1) and 3) with grappling-hook. What do you think?

Unless I misunderstood you 1) is already possible with context. And 3) is top of my wish list :smile:, i.e. it's the next thing I'll be working on.
Agreed on 2) and I think there's still some edge cases to be investigated there. If you start warming up to the idea, I'll aim for getting grappling-hook pass all mongoose hook-related tests.

@vkarpov15 just a heads-up on the release of v3.0.0 of grappling-hook, which has full promise support. It's library-agnostic, i.e. you can use any Promises A+ compliant library with it.
There are some notable differences with how kareem does things: functions registered to post are executed before the final callback is called. E.g.
instance.pre('save', function(){
  console.log('pre:save');
});

instance.post('save', function(){
  console.log('post:save');
});

instance.save = function(cb){
  console.log('saving');
  cb();
};

instance.save(function(){
  console.log('final callback');
});

#output:
pre:save
saving
post:save
final callback

Would you consider having this kind of changes to mongoose pre/post? Or do you want it to be 100% backwards compatible?

Sorry, forgot to mention the features: (terminology: hooks=the functions you register other functions to, middleware=the functions you register to hooks, i.e. in the above example 'save' is the hook and the functions registered to pre:save and post:save are middleware)

sync hooks
async hooks
thenable hooks (i.e. hooks that return a promise)
sync middleware
async serial middleware
async parallel middleware
thenable middleware (i.e. promise returning functions)
custom qualifiers (i.e. you can use something else than pre/post)
presets (i.e. configure once, reuse everywhere)
wrapping of existing methods
direct calling of hooks
executing middleware in a different context
optimised enforced synchronicity, i.e. asynchronous/thenable hooks always finish asynchronously, but as fast as possible
full error consistency: synchronous hooks bubble, asynchronous hooks pass thrown errors to the callback's err object and thenable hooks catch all errors (thrown or otherwise) and call the rejectedHandler of the final promise.
and some extra sugar for introspection and leeway for special cases

Kareem actually does the same thing re: post hooks being executed before the final callback. Mongoose really should be doing that going forward.
Grappling hook is looking pretty sweet, I'm gonna take a look at it when I get a chance. Thanks for the great work :)

@vkarpov15 ah, now I see, you're using both hooks-fixed and kareem in mongoose.
If there's anything I can help out with, let me know!


Typeguard is not applied inside following anonymous function

🔎 Search Terms
typeguard anonymous function
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about typeguards and anonymous functions
I was unable to test this on prior versions because it happens in earliest possible version, 3.3.3

⏯ Playground Link
https://www.typescriptlang.org/play?ts=5.5.0-dev.20240330#code/C4TwDgpgBAkgdgS2AghgGwCrmgXigbwFgAoKKBAEwC4oBnYAJwTgHMoAfKOAVzTQG4SZOCgC2EGvSasOXXgJIBfQcRIAzbnADGyAPZwowFAxYRgAMU06E+gBSVJjZiwA0XMRLpPWASgJCoBjNuBgMAbUo3EXEAXRVFEnUrPQMwYwg4C2SbOFtdACMAKxp4JFRMbD8iUnI1KFsAQgLCgDpKDk4mopboiCqAsiDgELgVMgTVGq19eigUKDwjEzNLbRS87sioZp6PHzGoabhZ-IX6vxwAPkNjUyy1nI3WrZ3e-agAeg+oCAYGXQYUAAFr8IEoSEA
💻 Code
type InitialType = {
  id: string | null;
  name: string | null;
};

function targetFunction(id: string, name: string) {
  return [id, name];
}

function parentFunction(obj: InitialType) {
  if (!obj.id || !obj.name) {
    return;
  }

  const a = targetFunction(obj.id, obj.name);
  const b = () => targetFunction(obj.id, obj.name); // error here
}

🙁 Actual behavior
It gives following error when passing parameters to targetFunction for b assignment (line 16). It happens after typeguard that checks both props of object for null values, so this value is already not null. It happens when doing it inside anonymous function.
Argument of type 'string | null' is not assignable to parameter of type 'string'.
  Type 'null' is not assignable to type 'string'.

🙂 Expected behavior
Expected no error here. Same function is called in line 15 without error.
Additional information about the issue
No response

Duplicate of #9998

Then is there known workaround for my use case? Other than making identical typeguard inside function?

Note that in this case the error is correct - obj may be mutated before b is called, and the compiler would have no way to know.  Workaround: Assign the value of obj.id and obj.name to a local variable after narrowing.


使用prometheus-agent，config.toml [global.labels] 失效

Relevant config.toml
[global]
# whether print configs
print_configs = false

# add label(agent_hostname) to series
# "" -> auto detect hostname
# "xx" -> use specified string xx
# "$hostname" -> auto detect hostname
# "$ip" -> auto detect ip
# "$hostname-$ip" -> auto detect hostname and ip to replace the vars
hostname = "$ip"

# will not add label(agent_hostname) if true
omit_hostname = false

# global collect interval, unit: second
interval = 15

# input provider settings; optional: local / http
providers = ["local"]

# The concurrency setting controls the number of concurrent tasks spawned for each input.
# By default, it is set to runtime.NumCPU() * 10. This setting is particularly useful when dealing
# with configurations that involve extensive instances of input like ping, net_response, or http_response.
# As multiple goroutines run simultaneously, the "ResponseTime" metric might appear larger than expected.
# However, utilizing the concurrency setting can help mitigate this issue and optimize the response time.
concurrency = -1

[global.labels]
#region = "shanghai"
env = "dev"
host= "$ip"

[log]
# file_name is the file to write logs to
file_name = "stdout"

# options below will not be work when file_name is stdout or stderr
# max_size is the maximum size in megabytes of the log file before it gets rotated. It defaults to 100 megabytes.
max_size = 100
# max_age is the maximum number of days to retain old log files based on the timestamp encoded in their filename.
max_age = 1
# max_backups is the maximum number of old log files to retain.
max_backups = 1
# local_time determines if the time used for formatting the timestamps in backup files is the computer's local time.
local_time = true
# Compress determines if the rotated log files should be compressed using gzip.
compress = false

[writer_opt]
batch = 1000
chan_size = 1000000

[[writers]]
url = "http://pt.datakit.guance.dbt.com/prom_remote_write"

## Optional TLS Config
# tls_min_version = "1.2"
# tls_ca = "/etc/categraf/ca.pem"
# tls_cert = "/etc/categraf/cert.pem"
# tls_key = "/etc/categraf/key.pem"
## Use TLS but skip chain & host verification
# insecure_skip_verify = true

# Basic auth username
basic_auth_user = ""

# Basic auth password
basic_auth_pass = ""

## Optional headers
# headers = ["X-From", "categraf", "X-Xyz", "abc"]

# timeout settings, unit: ms
timeout = 5000
dial_timeout = 2500
max_idle_conns_per_host = 100

[http]
enable = false
address = ":9100"
print_access = false
run_mode = "release"

[ibex]
enable = false
## ibex flush interval
interval = "1000ms"
## n9e ibex server rpc address
#servers = ["<IP_ADDRESS>:20090"]
## temp script dir
meta_dir = "./meta"

[heartbeat]
enable = false

# report os version cpu.util mem.util metadata
#url = "http://<IP_ADDRESS>:17000/v1/n9e/heartbeat"

# interval, unit: s
interval = 10

# Basic auth username
basic_auth_user = ""

# Basic auth password
basic_auth_pass = ""

## Optional headers
# headers = ["X-From", "categraf", "X-Xyz", "abc"]

# timeout settings, unit: ms
timeout = 5000
dial_timeout = 2500
max_idle_conns_per_host = 100

[prometheus]
enable = true
scrape_config_file = "D:/opt/in_cluster_scrape.yaml"
## log level, debug warn info error
log_level = "info"
## wal file storage path ,default ./data-agent
# wal_storage_path = "/path/to/storage"
## wal reserve time duration, default value is 2 hour
# wal_min_duration = 2

Logs from categraf
无

System info
0.3.44
Docker
No response
Steps to reproduce
[prometheus]
enable = true
[global.labels]
不起作用
Expected behavior
[global.labels] 添加到指标中
Actual behavior
[global.labels] 没添加到指标中
Additional info
No response

prometheus-agent 是单独的agent，现在不支持config.toml的配置

但使用prometheus-agent就不会出现上述情况，但是使用prometheus-agent后不支持config.toml的配置

prometheus-agent 也支持全局label，在prometheus-agent对应的yaml中配置

但使用prometheus-agent就不会出现上述情况，但是使用prometheus-agent后不支持config.toml的配置

把完整的指标 和 input.prometheus 采集的完整指标 都发一下。


Postgres UNNEST insertion gives compiler error on slice of options when target col is nullable

Bug Description
mismatched types expected reference &[i16] found reference `&[std::option::Option]
Account.Unit is optional, and in the DB it is nullable, yet SQLX refuses to allow the bulk insertion
(Yes I already used a derive macro to convert from array of structs to struct of arrays.)
There may be a way around this but I'm either not big brain enough or this is just a bug.
Minimal Reproduction
#[derive(Debug, Deserialize, StructOfArray)]
pub struct Account {
    pub last_name: String,
    pub first_name: String,
    pub street_address: String,
    #[serde(deserialize_with = "deserialize_unit")]
    pub unit: Option<i16>,
    pub city: String,
    pub state: String,
    pub zip: i32,
    #[serde(deserialize_with = "deserialize_dob")]
    pub dob: NaiveDate,
    #[serde(deserialize_with = "deserialize_ssn")]
    pub ssn: i32,
    pub email_address: String,
    pub mobile_number: i64,
    pub account_number: i64,
}

INSERT INTO account (
    account_number,
    mobile_number,
    email_address,
    ssn,
    dob,
    zip,
    account_state,
    city,
    unit,
    street_address,
    first_name,
    last_name
) SELECT * FROM UNNEST (
    $1::BIGINT[],
    $2::BIGINT[],
    $3::VARCHAR[],
    $4::INT[],
    $5::DATE[],
    $6::INT[],
    $7::CHAR[],
    $8::VARCHAR[],
    $9::SMALLINT[],
    $10::VARCHAR[],
    $11::VARCHAR[],
    $12::VARCHAR[]
)

sqlx::query_file!("queries/upload_accounts.sql",
        &accounts.account_number[..],
        &accounts.mobile_number[..],
        &accounts.email_address[..],
        &accounts.ssn[..],
        &accounts.dob[..],
        &accounts.zip[..],
        &accounts.state[..],
        &accounts.city[..],
        &accounts.unit[..],
        &accounts.street_address[..],
        &accounts.first_name[..],
        &accounts.last_name[..]
    );

Info

SQLx version: 0.7.1
SQLx features enabled: ["bigdecimal", "postgres", "runtime-tokio-rustls", "time"]
Database server and version: Postgres 11.18
Operating system: Ubuntu
rustc --version: rustc 1.72.0

You need to add as &[Option<T>] to your bindings.
cf. #576


”Iezer”, ”Lălești”, ”Rotari”, ”Ruși” are listed in the drop-down menu

Description:
When user writes ”Iezer”, ”Lălești”, ”Rotari”, ”Ruși” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 3
Write in the search bar "Lălești"

Expected results
The location appears in the drop-down menu as "Sat Lălești, VASLUI (Puiești)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Rotari"

Expected results
The location appears in the drop-down menu as "Sat Rotari, VASLUI (Puiești)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Ruși"

Expected results
The location appears in the drop-down menu as "Sat Ruși, VASLUI (Puiești)".


CI: Add testing based on Centos containers

In the release loop upstream changes are merged to Centos every two weeks. This creates a delay in error detection when new tests being added upstream.
Running tests in Centos based containers for every pull request should solve the issue.
https://issues.redhat.com/browse/COMPOSER-2125

In the gitlab CI, we build CS9 manifests (on CS9 in AWS) already.  https://gitlab.com/redhat/services/products/image-builder/ci/osbuild/-/jobs/6155161065
They might be as comprehensive as the unit tests (we might not be covering all supported stages in those manifests), but the stage unit tests are all actually Fedora manifests.  Which is also fine, we're testing if osbuild runs properly on CS9 I suppose, but I think the existing tests are both more realistic (building CS9 on CS9) and less likely to break due to unsupported features (trying to build a Fedora manifest with a btrfs disk on CS9).
I think we would be better served by having a job that updates the content in the manifests more frequently than running the Fedora-based unit tests.

What I am doing here precisely is:

Spawn c8s and c9s centos images prepared by @thozza here:https://github.com/osbuild/containers/pull/63
In the action I am reusing testing scripts directly from the centos repo: https://gitlab.com/redhat/centos-stream/rpms/osbuild/-/tree/c9s/tests/unit-tests?ref_type=heads
Normally those scripts are used by ZuluCI when upstream release is pushed to centos repo by centos-bot every 2 weeks.
Result is donsteam-like testing of every upstream PR to check if it will not break the centos stream (and rhel stream as result)

From time to time we have a situation when centos testing fails due to upstream changes and we detect this with the 2 weeks delay. I know it will delay PR review as running centos tests takes more than 2h. I think we should mark this as optional from the review point of view or run nightly. Still, we would be able detect "potential" centos / rhel issue way faster than in 2 weeks from PR being merged.

I know it will delay PR review as running centos tests takes more than 2h. I think we should mark this as optional from the review point of view or run nightly.

Right, that makes sense.  Thanks for the explanation!

Lets get an opionion from @thozza and @ochosi \o/

@achilleas-k and @ochosi - thank you both for the review. I will update the code tomorrow with:

running nightly
removing duplicated jobs by change to matrix strategy

I think we should wait for @thozza final verdict as I am using some centos downstream scripts bit "nasty" way instead of copying them to repo (as usually our upstream feeds downstream, not the other way around:) )

Centos based tests unwraps to different pytest settings.
Centos8 settings:
sudo python3 -m pytest
--rootdir /osb/workdir/osbuild/osbuild-111
--ignore /osb/workdir/osbuild/osbuild-111/test/src
--unsupported-fs btrfs
-k 'not (TestBoot and boot) and not (test_qemu[ext4-vdi] or test_qemu[xfs-vdi]) and not (TestStages and test_qemu)'
-v /osb/workdir/osbuild/osbuild-111/test/

Centos9 settings:
sudo python3 -m pytest
--rootdir /osb/workdir/osbuild/osbuild-111
--ignore /osb/workdir/osbuild/osbuild-111/test/src
--unsupported-fs btrfs
-k 'not (TestBoot and boot)'
-v /osb/workdir/osbuild/osbuild-111/test/

I have encapsulated this final pytest parameters into the new CI jobs and removed dependency from downstream code.

@thozza @ochosi I think this one is ready to go.

@thozza thanks for the review \o/

Could you please try testing the action as a PR in your own repo against main? Because from what I can tell, the action was not executed as part of this PR, so I can't tell if it works.

As @ochosi suggested I switched from calling this action on every PR to a nightly schema. I will add run result from my fork in comment.

Clicked the rebase button.

FTR, this PR is good to go from my PoV, I'm waiting only on a proof of a successful run of the pipeline (on a fork).

Just as a fast recap: This PR has been tested on my other repo and both c8s and c9s are passing. As we discussed in Brno - I will wait for c10s image to be available (https://github.com/osbuild/containers/pull/74) and will drop c8s in favor of c10s.

@thozza I have just updated the code and triggered run on my private repo:
c10s: https://github.com/elkoniu/osbuild/actions/runs/9646685253/job/26603713866?pr=1
c9s: https://github.com/elkoniu/osbuild/actions/runs/9646685253/job/26603713188?pr=1
In the main PR CI will be running nightly instead of every PR.


Information about Wifi MFA unlock needs to be corrected

Hi,
I've lost some time on this since in the documentation there's a typo in the example for the Wifi configuration (example #4)
Current version:
"<rule version="1.0">
<signal type="wifi">
Correct version should be:
"<rule schemaVersion="1.0">
<signal type="wifi">
Thanks.

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

ID: 38f8c2ce-8edb-60d3-ebf9-bdb625bf66dc
Version Independent ID: ee1ed0a8-b05c-c499-6504-40b5b298c53b
Content: Multifactor Unlock - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

Any update on this minor change which impacts deployments for users that are unaware of this error in the documentation?
Thanks

Closing via merged PR #6823


Draw Icons & fitScreen

PR Checklist:

[x] I have tested this extensively and it does not break any existing behavior.
[x] I have added/updated examples and tests for any new behavior.
[ ] If this is a significant change, an issue has already been created where the problem / solution was discussed: [N/A, or add link to issue here]

PR Description

Minor organization.
fix: fitScreen was breaking chart rendering on call.
feat: First experimental implementation of draw icons using ImageSource (included in BarChart example).

@DimitrisRK awesome job thanks!


Great app and a useful tiny mod

Hello,
This is a great little app. I'm just getting started on Storj, and being able to see that I am making connections and things are (mostly) working well is useful and reassuring.
I have a couple of suggestions /ideas:

I have a slightly modified launch script that scans the whole log file and then follows along with the current state:

docker logs --follow storagenode -f 2>&1 | node app
This means that the stats for "Upload Sucess Rate:" and   "Download Sucess Rate:" reflect the state of  your Storj node since that instance was launched. For me, at least, that makes these numbers more useful. The app goes a little crazy for a few seconds whilst it scans through the file, but quickly settles back to monitoring the current connection status.

Spelling mistake "Success" rather "Sucess" - if you do a further version you might want to fix this.

Cheers.


Opening "Windows Settings" results in an error

When clicking on the Windows Settings menu option in the Cairo menu, nothing happens for around ten seconds. Afterwards an error message appears
explorer.exe "File system error (-2147219200)."
This error only occurs when CairoShell is set as the user shell.
I'm guessing it's something to do with some initialising not happening where needed?

By the way
OS: Windows 10 Pro
Build: 16299
CairoShell: 1fa3337b95678efc29ec824b95f54e60b10acdcb

Good catch, the Settings app is a UWP app, which depends on Explorer as shell in order to run. I’ll remove this item when Explorer isn’t shell.

This is fixed in the latest release.

Hi, still running into this on Windows Server 19.


Wrong implementation of yield/yield* in dartdevk

dartdevk doesn't implement yield/yield* behavior described in https://github.com/dart-lang/language/blob/master/accepted/future-releases/async-star-behavior/feature-specification.md
There are several issues.

If execution is paused on yield/yield* and stream is cancelled, then yield* should act like a return; statement. But it isn't so and it causes failure of the following co19 tests

co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A03_t01
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A03_t01
co19/Language/Statements/Yield_and_Yield_Each/Yield_Each/execution_async_A03_t07
co19/Language/Statements/Yield_and_Yield_Each/Yield_Each/execution_async_A03_t08
co19/Language/Statements/Yield_and_Yield_Each/Yield_Each/execution_async_A03_t09

In an asynchronous function, an await for (var event in stream) ... loop first listens on the iterated stream, then for each data event, it executes the body. If the body performs any asynchronous operation (that is, it does not complete synchronously because it executes any await, wait for or yield* operation, or it blocks at a yield), then the stream subscription must be paused. It is resumed again when the body completes normally. But it isn't so and it causes failure of

co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A05_t02

If execution is paused then execution should be blocked at yield. See failures of

co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t01
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t02
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t03
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t04
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t05
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t06
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t07
co19/Language/Statements/Yield_and_Yield_Each/Yield/execution_async_A01_t08
See full log at https://dart-ci.firebaseapp.com/cl/253664/1

We're receiving bugs about this inconsistency internally as well. Another repro by a Googler:
Stream<int> f() async* {
  var count = 0;
  yield* Stream.fromIterable([1, 2, 3]).map((x) {
    count++;
    return x;
  });
  expect(count, 3);
}

final s = f().listen(null);
s.onData((x) => s.cancel());

which fails on DDC with:
Expected: <3>
  Actual: <1>

since DDC resumes execution of the body despite canceling the stream.

Potential duplicates or related issues:
https://github.com/dart-lang/sdk/issues/53062
https://github.com/dart-lang/sdk/issues/47764
https://github.com/dart-lang/sdk/issues/47342
https://github.com/dart-lang/sdk/issues/42764
https://github.com/dart-lang/sdk/issues/35624
https://github.com/dart-lang/sdk/issues/54411


Restrict access to K8s secret token

The most of the containerized workloads do not need to interact with the Kubernetes API server and
they don't need to read the token that is associated with the ServiceAccount used to create the Pod.
This path can be blocked /var/run/secrets/kubernetes.io

@mjura do we really need to add the whole lockc.toml to the helm chart too? I think the container image should come with the default lockc configuration we create.
It's fine to allow the user to overload the configuration via helm, but I wouldn't use that a a mechanism to get our default config into kubernetes.

@flavio I actually like the idea of adding the whole config to the helm chart. It gives people a reference and lets them adjust the configuration by editing it.
What worries me a bit is that we have multiple files where we need to put new configuration options, which starts becoming quite a hassle. I have no clear idea how to solve that yet, but it would be nice to have some one file for defining options and then generate all the others (.rs, /etc and configmap) based on it.  Of course I wouldn't do that in this PR, rather as an follow up issue.

Also, there is a typo in the commit message and PR name - s/secter/secret/

What worries me a bit is that we have multiple files where we need to put new configuration options, which starts becoming quite a hassle.

That's exactly my main concern. Just to reiterate over what I've already said,  I would leave the default configuration inside of the lockc repo on GitHub, have that tagged and automatically added to the container image at build time.
As for the users, we can address your concern ("how do they find a sample of the configuration file?") by adding a simple comment inside of the helm chart. The comment can point to the configuration file on the GitHub repo

I have updated also baseline restricted paths

Linter is complaining, but it's not related to changes in this PR, let me fix it with a new PR and let's keep this one on hold.

@flavio we are going to remove a duplicated config from helm chart (and instead use the .toml file from the container image) as a follow up change.


Standalone executable possible

Hi
we use a previous version of DSSP, where we have a standalone executable that we can easily transfer and run on different machines. Is this possible for DSSP4.0, as well?
I followed the installation instructions, including mrc, and am able to use mkdssp on my machine. The executable depends on Boost, stating

./mkdssp: error while loading shared libraries: libboost_program_options.so.1.73.0: cannot open shared object file: No such file or directory

after transferring to and running it on a different machine. Is it possible to create a standalone executable as before?
Thanks in advance for your answer.
Best wishes,
Niclas

Hi Niclas,
Yes, this is possible. However, in that case you have to build boost
yourself. In theory, this is not difficult. However, you must make sure
you remove the system installed boost development packages first to
avoid running into the problem of mismatches between the system
installed boost and privately installed boost and header files.
After removing the boost-dev packages, you can download boost from
boost.org, unpack it and then build it using:
./bootstrap.sh (needed only once)
./b2 link=static stage
./b2 install --prefix=/somewhere/on/your/disk
That should create only static libraries in the specified location. Now
you can specify this location you used as parameter to configure for
libcifpp and dssp and the result will be a libcifpp and a dssp that is
no longer dependent on libboost' shared libraries.
Hope this helps.
regards, -maarten
Op 03-05-2021 om 14:03 schreef JNWolf:

Hi
we use a previous version of DSSP, where we have a standalone
executable that we can easily transfer and run on different machines.
Is this possible for DSSP4.0, as well?
I followed the installation instructions, including mrc, and am able
to use mkdssp on my machine. The executable depends on Boost, stating
./mkdssp: error while loading shared libraries:
libboost_program_options.so.1.73.0: cannot open shared object
file: No such file or directory

after transferring to and running it on a different machine. Is it
possible to create a standalone executable as before?
Thanks in advance for your answer.
Best wishes,
Niclas
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PDB-REDO/dssp/issues/15, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADNA47CK4RZ3BSZ3FUPLEKTTL2GHTANCNFSM44AWE5OQ.

--
Maarten L. Hekkelman
http://www.hekkelman.com/


Added separate method in chaise.page.js to performlogin

This PR adds a separate method performLogin to chaise.page.js that performs login on behalf of a user when passed a cookie.
Documentation can be found here

@chiragsanghvi has anyone review this PR prior to merging?

@hongsudt The change was in the test framework and had no side effects. It was just some code optimization.

OK. So this feature should now be available on the dev server, correct?


Please provide API to update the animations by time elapsed from animation start

First of all, thanks for doing this library ... this got me finally motivated to add some animations to my dlang imageviewer :)
In my usecase it would be simpler to just take the time at the beginning of an animation and feed Clock.currTime - startOfAnimation e.g. into a Tween.
an implementation for tween could look like this:
    struct Tween {
    .
    .
    .
    float elapsedTime(float elapsedTime)
    {
        final switch (mode)
        {
        case TweenMode.bomb:
            if (elapsedTime < 0.0f) {
                time = 0.0f;
            } else if (elapsedTime >= duration) {
                time = duration;
            } else {
                time = elapsedTime;
            }
            return now;
        case TweenMode.loop:
        case TweenMode.yoyo:
            assert(0);
        }
    }
    .
    .
    .

So if I understand correctly, you want a way to set the time to something and get the value at that time on the same line?
Like update() but without adding/subtracting from time?
Thanks for trying the library.

Yes ...with update i have to always store update the time of the last call to update, with the additional API I just take the time at start of the animation and subtract the same value from the current time.
Btw. This was for me a just works (tm), well done.

Thanks a lot ... Will update my local git and use it from there ... But not before this evening ;)

Nice .. works for me ...
I like also the implementation .. nice how you dont repeat yourself by reusing update in elapsedTime. Perhaps it would be more "efficient" to reuse elapsedTime in update instead (elapsed time just needs to set the time (plus clamping), wheras update always needs todo the +dt thing.

Actually that's not a bad idea. I don't know about performance but it makes more sense I think.

I also do not know about performance (probably not much difference in the end) ... but still :)

Looks good for me as well ... at least I do not see a difference in my animation :)
you even added some ddocs ;-)
one thing i do in other parts of my program is to use https://dlang.org/library/std/algorithm/comparison/clamp.html ... makes the clamping shorter ... not sure if you want to depend on those parts of std though ... but this is for sure something for another issue :)


Possibly Broken

When I generate with txt2img, the result displays the first time. But running it a second time, the new result does not show.
When I move the output to img2img, I get a message "Connection errored out."
I've already tried rerunning "Start Stable-Diffusion" in the Colab. That did not fix it. I also checked "Update Repo" when setting it up.

^C means it interrupts the process because the lack of RAM (not VRAM)
https://github.com/TheLastBen/fast-stable-diffusion/issues/645


Visualization and a short analysis of layoffs.fyi_20240208_004032.csv

Closes #5 partially
All stages are described in pandas_analyse.ipynb.

It's okay. I also looked at graphs. What you wanted to show with it? What
does X axis called index means?
On Tue, Feb 13, 2024, 11:48 AM Volodymyr @.***> wrote:

@.**** commented on this pull request.
On src/AirTable_CompanyParcer/layoffs.fyi_20240208_004032.csv
https://github.com/MIT-Emerging-Talent/2024-group-02-cdsp/pull/13#discussion_r1488416253
:
Oh... That's an accident mistake. Just wanted to make folder in src to
distibute all the info.
—
Reply to this email directly, view it on GitHub
https://github.com/MIT-Emerging-Talent/2024-group-02-cdsp/pull/13#discussion_r1488416253,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIOWMBUAYSHQRA7C7ESXF6DYTOYPVAVCNFSM6AAAAABDEQ23OCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQNZYG4YDANBSG4
.
You are receiving this because you commented.Message ID:
@.***
com>


Add the additional built in types

Ran into a problem where I needed to declare the type for my Schema as array and didn't know it was already a built in type. This will help someone with a similar problem

Not relevant anymore as we are rolling out new version with a new API.


(swedish) Update items_swedish.vdf

I translated the latest update note. But, there is probably many spelling mistakes there, I tried my best.


wfreerdp.exe Segmentation fault connecting to Gnome remote desktop

wfreerdp connects to Gnome remote desktop, displays/updates the desktop, etc.
crashes as soon as mouse enters the remote desktop.
mstsc works
wfreerdp.exe    /v:x.x.x.x
[16:30:21:199] [63180:0000b038] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[16:30:21:199] [63180:0000b038] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[16:30:21:199] [63180:0000b038] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[16:30:21:199] [63180:0000b038] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[16:30:21:199] [63180:0000b038] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc
[16:30:21:226] [63180:0000b038] [INFO][com.freerdp.primitives] - primitives autodetect, using generic
[16:30:21:239] [63180:0000b038] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
[16:30:21:239] [63180:0000b038] [INFO][com.freerdp.core] - freerdp_tcp_default_connect:freerdp_set_last_error_ex resetting error state
[16:30:21:288] [63180:0000b038] [INFO][com.freerdp.crypto] - known_hosts=1
[16:30:27:059] [63180:0000b038] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRX32
[16:30:27:059] [63180:0000b038] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32
[16:30:27:093] [63180:0000b038] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
[16:30:27:093] [63180:0000b038] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx
[16:30:27:258] [63180:0000b038] [INFO][com.freerdp.client.windows] - Window is shown!
Segmentation fault

wfreerdp /buildconfig
This is FreeRDP version 3.0.0-dev (391f2f7c4)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H= HAVE_EXECINFO_H= HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_STRNDUP= HAVE_SYSLOG_H= HAVE_SYS_EVENTFD_H= HAVE_SYS_FILIO_H= HAVE_SYS_SELECT_H= HAVE_SYS_SOCKIO_H= HAVE_SYS_TIMERFD_H= HAVE_TM_GMTOFF= HAVE_UNISTD_H= WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_FREERDP_DEPRECATED=OFF WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_MEDIA_FOUNDATION=ON WITH_NATIVE_SSPI=ON WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSSL=ON WITH_PROFILER=OFF WITH_PROGRESS_BAR=ON WITH_SAMPLE=OFF WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SOXR=OFF WITH_SSE2=ON WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VERBOSE_WINPR_ASSERT=ON WITH_WIN8=OFF WITH_WINDOWS_CERT_STORE=ON WITH_WINMM=ON WITH_WINPR_DEPRECATED=OFF WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=OFF WITH_ZLIB=OFF
Build type:          Release
CFLAGS:              /DWIN32 /D_WINDOWS  /Gd /W3
Compiler:            MSVC, 18.0.40629.0
Target architecture: x64

@akallabeth Very likely that wfreerdp accesses the andMaskData unconditionally (it should be NULL here).

@pnowack where should that happen? If andMaskData == NULL lengthAndMask == 0 or do I miss something there?

If andMaskData == NULL lengthAndMask == 0 or do I miss something there?

Yes, with g-r-d andMaskData == NULL and lengthAndMask == 0 are always true. I had to fix an issue in Remmina over a year ago, where Remmina went in a disconnect-reconnect loop, since it had a superfluous NULL check on the andMaskData.
Also OR mentions:

crashes as soon as mouse enters the remote desktop.

In that case g-r-d sent the pointer data. g-r-ds pointer data is always 32bpp xorMaskData without andMaskData.

where should that happen?

I did not check directly the code, but the assumption is based on these two indicators here.

@pnowack well, _update_read_pointer_color disagrees, there lengthAndMask > 0 andMaskData != NULL is enforced. So, it might trigger a disconnect, but never a segfault.


Common shortcuts for tmux

I would like to use tmux, but default shortcuts are kinda hard to use. May some of us who use it could share config or write a simple description for setting it up?

@chyrta, see my config with comments: https://github.com/datarockets/.dotfiles/blob/tmux/tmux.conf

Thank you so much.

It's in master now: https://github.com/datarockets/dotfiles/blob/master/tmux.conf.


LASB-1095 - Add integration tests for authorization controller

What
Link to story

[x] Added integration tests for the Autorization controller endpoints.

Checklist
Before you ask people to review this PR:

[x] Tests should be passing: ./gradlew test
[x] Github should not be reporting conflicts; you should have recently run git rebase main.
[x] Avoid mixing whitespace changes with code changes in the same commit. These make diffs harder to read and conflicts more likely.
[x] You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
[x] You should have checked that the commit messages say why the change was made.

Good point, the way I've set up the tests doesn't actually trigger the RestController that handles the error cases. I'll use the MockMVC to call the method via its endpoint rather than calling it directly.


add function to list dependencies of a template

Get a list of the unique values a template depends upon.
e.g.
const { listDependencies } = require('adlib')
const template = 'Injuries: {{CRASHID}}<br />Fatalities: {{ISREPORTONSCENE}} Date: {{Date:toIso}}'
const deps = new Set(listDependencies(template));
assert.deepEqual(deps, new Set('CRASHID', 'ISREPORTONSCENE'));

apparently in node you cannot maintain the api of
adlib()
adlib.function

@dbouwman I've updated this according to your feedback

The ember addon is already looking for dist/adlib.js
https://github.com/ArcGIS/ember-arcgis-adlib-service/blob/master/index.js#L26

It works as is with
adlib()
adlib.listDependencies()
If you don’t mind the slightly awkward api then I think we should merge as is and avoid a breaking change.

@dmfenton works for me - lmk if you don't have privs to publish this package


Fix Nightly Builds on Windows

Pull Request Description
The PR #1947 accidentally broke nightly builds on Windows due to an oversight that the correct npx command on Windows is actually npx.cmd and just using npx when starting a process leads to the command failing. This fixes that issue. Still there are some problems with starting npx on Windows, so this PR for now disables it in the nightly builds, as the only affected thing is the formatting of standard library's package.yaml files. So for now to fix nightlies, the formatting is disabled.
Important Notes

[ ] A nightly workflow is running on enso-staging to verify that the fix is enough.

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, and Rust style guides.
[x] All documentation and configuration conforms to the markdown and YAML style guides.
[ ] All code has been tested where possible.

To fix the nightlies this disables the formatting of package.yaml in nightly builds (so it only affects the indentation of these files, no functionality is affected).
@iamrecursion is it acceptable for longer term (it seems like this formatting isn't crucial for nightlies) or should we create an issue to do a 'proper' fix, which is to make npx work on the Windows CI in this context?


Using starter package seems not to work on github pages

Checklist

[X] I have read the tutorials and know the correct effect of the functional design.
[X] There are no similar reports on existing issues (including closed ones).
[ ] I found the bug on the latest code of master branch.

Describe the bug

Using the starter template and made url changes does not render a exspected result in the gh-pages output.
To Reproduce
Steps to reproduce the behavior:

Create a respository from the starter template to https://github.com/Calteo/ChripStarter
Changed baseurl to '/ChripStarter'
Change url to https://calteo.github.io/ChripStarter
gh-pages get build
Output does only read "--- layout: home # Index page --" in index.html

Expected behavior

To see at least an empty template.
Screenshots

Software

Ruby version:
Gem version:
Bundler version:
Jekyll version:

Desktop

Smartphone

Additional context

[x] I have read the tutorials and know the correct effect of the functional design.
[x] There are no similar reports on existing issues (including closed ones).

I don't buy it 😞

[x]  I have read the tutorials and know the correct effect of the functional design.
[x]  There are no similar reports on existing issues (including closed ones).

I don't buy it 😞

I have same problem. Only rendering "--- layout: home # Index page --"

Same Problem me too

This is still an issue


fix #156: tuples encoding at depth 0

Well the binding tester failed, so this might be breaking current code.

Too bad that it would be too much work having to maintain two branches of the same kind that only diverge because of a single commit

I haven't yet had time to figure out what this commit breaks to cause the binding tester to fail.

So bindingtester, on one of the pushes, does a TupleUnpack instr.code. TupleUnpack before this commit would push 6 items into the stack, in this commit, it pushes a single Tuple(Vec(Len:6)) item into the stack. The stack is not expecting such a low number and it fizzles out. I am not sure if bindingtester is supposed to be changed, but here's what I changed on TupleUnpack, it passes Bindingtester + cargo test.

TupleUnpack => {
                let data: Vec<u8> = self.pop_item();
                let mut data = data.as_slice();

                while !data.is_empty() {
                    let (val, offset): (Element, _) = Decode::decode_from(data).unwrap();
                    match val {
                        Element::Tuple(v) => {
                            v.iter().for_each(|va| self.push_item(number, &va.to_vec()))
                        }
                        _ => {
                            let bytes = val.to_vec();
                            self.push_item(number, &bytes);
                        }
                    }
                    data = &data[offset..];
                }
            }

Again, if this is wrong, then I will continue to look into it

Any updates on this? Hope everything's doing well especially in this season

The change you made is correct. I also can't figure out a way to merge this commit without a breaking change.

Well maybe decode_from should not try to decode the whole set of bytes for some types. (ie. Element)
Your code could be simplified to:
TupleUnpack => {
                let data: Vec<u8> = self.pop_item();
                let mut data = data.as_slice();

               let vec: Vec<Element> = Decode::decode(data).unwrap();
               for v in vec {
                   self.push_item(number, &v.to_vec())
               }
}

That would work if we differentiate the behavior between decode and decode_from. If it's not and we attempt to simplify the code, it will cause errors to pop up.

Differentiating between decode and decode_from will minimize the impact but it's still a breaking change due to the fact data are now encoded according to the official spec (decoding allows both the old and the official spec).
Maybe a feature flag to enable this set of fixes is better.
To be true, I just want to provide peoples a 0.3 version that works but I don't want to spent a lot of time on it. The 0.4 branch is what matter the most to me (async, safety, no more clone() everywhere).
You seem to be a 0.3 version user, so your opinion matter more than mine on this.

A flag would work for sure.
To be honest, the only reason why I hang onto this branch is because there are some packages that I use as dependencies that haven't released their async/await branch yet. Once they do that I'll be rewriting to comply with futures 0.3, async/await and all that jazz. But for now what I aim for is to have data encoded and decoded the same way in both branches so that when I rewrite for the other one I don't have breakage due to how we encoded or decoded it thru 0.3


Added implementation for "containsIgnoringWhitespaces"

Check List:

Contributes to #2060
Unit tests : YES
Javadoc with a code example (on API only) : YES
PR meets the contributing guidelines

Following the contributing guidelines will make it easier for us to review and accept your PR.
I personally prefer small PR's when being a reviewer. So one PR for the "containsIgnoringWhitespaces" mentioned in #2060 (so it contributes to it, but does not fix it compeletly. If you are fine with this, I might the normalizing and newlines variants.

@joel-costigliola everything should be fixed now.

Integrated thanks @beckerjohannes!


Mac OS support for older versions

The Issue
In 0.21.2 / previous LBRY app release, we supported Mac OSX 13 and above (Darwin 10.9)
Per https://pyinstaller.readthedocs.io/en/stable/usage.html#making-mac-os-x-apps-forward-compatible, we need to compile the daemon under an older xcode version. See available xcode versions on Travis here: https://docs.travis-ci.com/user/reference/osx/. The lowest available is 6.4, with support going away in Jan 2019 unless we specifically ask Travis to continue supporting:  Running builds with Xcode 6.4 in Travis CI is deprecated and will be removed in January 2019. If Xcode 6.4 is critical to your builds, please contact our support team at<EMAIL_ADDRESS>to discuss options.

Darwin
OSX
xcode
Date
Codename

13.0.0
OS X v10.9.0
6.2 (not on Travis)
June 11, 2013
OS X Mavericks

13.4.0
OS X v10.9.5
6.2 (not on Travis)
September 17, 2014
OS X Mavericks

14.0.0
OS X v10.10.0
6.4 (Travis support ending soon)
September 18, 2014
OS X Yosemite

14.5.0
OS X v10.10.5
6.4 (Travis support ending soon)
August 13, 2015
OS X Yosemite

15.0.0
OS X v10.11.0
8
September 16, 2015
OS X El Capitan

Working build on xcode 6.4: https://github.com/lbryio/lbry/pull/1659
Users who accessed LBRY since Sept on Darwin 13-14: 478
Active users in same period (more than 5 accesses): 20
Users who accessed LBRY since Sept on Darwin 13 only: 106
Active users in same period (more than 5 accesses): 4
We can send these users an email letting them know that the LBRY app won't work on OSX 13/14 anymore.
Once we get python 3.7 switched over, I'll create a PR to test xcode 8 with Travis changes.
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Internal Use
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

We decided to go ahead with Xcode8.3 since it doesn't cause any build issues. Anyone on a lower version than 16.5 (Sierra) will not be able to run the app/daemon. I was thinking we could release a community build for these users if they cannot upgrade their OS for some reason. I'll be sending them an email.


upgrade rails (Security updates)

I get notifications via Gemnasium, so thought I'd clear this one.

Nice one! +1
On 17 Mar 2015 14:12, "Abraham Petrillo"<EMAIL_ADDRESS>wrote:

I get notifications via Gemnasium, so thought I'd clear this one.
You can view, comment on, or merge this pull request online at:
https://github.com/GavinJoyce/rubyjobs2/pull/11
Commit Summary

upgrade rails (Security updates)

File Changes

M Gemfile
https://github.com/GavinJoyce/rubyjobs2/pull/11/files#diff-0 (3)
M Gemfile.lock
https://github.com/GavinJoyce/rubyjobs2/pull/11/files#diff-1 (81)

Patch Links:

https://github.com/GavinJoyce/rubyjobs2/pull/11.patch
https://github.com/GavinJoyce/rubyjobs2/pull/11.diff

—
Reply to this email directly or view it on GitHub
https://github.com/GavinJoyce/rubyjobs2/pull/11.

Coverage increased (+0.03%) to 96.09% when pulling c4bf94a78565ed6aaeba79f03b09aa679c78f7b9 on abepetrillo:master into c45a40717b7df51266a90823f41baeab64f699bd on GavinJoyce:master.


KAFKA-9887 fix failed task or connector count on startup failure

Moved the responsibility for recording task and connector startup and failure metrics from the Worker class  into the status listener that gets passed into the WorkerTask. The status listener is decorated to record the metrics when onStartup or onFailure occur (if failure happens before startup).
This gets around the previous issues where these metrics were not being recorded because
the WorkerTasks/WorkerConnectors were either not propagating exceptions upwards, or were unable to do so easily because they were running on completely different threads.
Also split out WorkerMetricsGroup from being an inner class into being a standard class. This was to make sure the Data Abstraction Coupling checkStyle rule for the Worker class was not violated.
Testing involved adding some unit tests for the decorated listeners to ensure they recorded metrics correctly. Some manual testing was done with Connectors and Tasks that deliberately threw exceptions in the startup phase to ensure JMX metrics were reported correctly.
Some of the unit tests for the Worker class had some assertions around startup statistics removed, as setting these statistics is no longer the direct responsibility of the Worker class,
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

ok to test

Failing unit test kafka.admin.ReassignPartitionsUnitTest.testModifyBrokerThrottles is unrelated to this pull request and is tracked by: https://issues.apache.org/jira/browse/KAFKA-10155
https://issues.apache.org/jira/browse/KAFKA-10147

retest this please

Is this something you could review @C0urante ?

Thanks for reviewing this @C0urante.
"if the framework successfully instantiates a connector and is able to call start on it, should that alone qualify as a "successful" startup, or does the call to start also have to go off without a hitch?" --- That’s an interesting point and not one that I'd considered. My fundamental assumption in approaching this was that the ‘connector-startup-failure-total’ metric, described in the KIP as ‘The total number of connector starts that failed’, was intended to be a numerical record of failures within the ‘start’ method of the connector (And likewise for the task based metrics). Or in other words, they represented the health of the worker in an integration sense. (e.g. Does the worker have the right connectivity to do its job? Are people submitting valid configurations or are the users of Connect not understanding how to use it?) This to me seems like a useful aggregate metric that relates to the use of the worker as a whole more than a record of any individual connector failure.
The way I encountered this was someone on my team was attempting to run a CloudWatch connector, but hadn’t got the configuration quite right, so the ‘start’ method would throw an exception and the connector would enter the failed state every time. However, the worker recorded this as a successful startup (which we all felt to be a bit misleading). With my interpretation of the metric’s intention, this confused the investigation into what the problem was and upon finding the cause. seemed like a bug in the metric (and a big surprise).
FWIW, I would say that it still seems like the most natural interpretation of the metric to me, but if this isn’t the intention, then I’d probably suggest renaming the metric to something that de-conflicts its meaning with the connector’s ‘start’ method. E.g connector-start-preparation-failure-total or something like that (And similarly for task start-ups).

Thanks for the insight @michael-carter-instaclustr. This type of direct user feedback and perspective is invaluable! I'm convinced that your interpretation is likely the more useful of the two (assuming that we don't exclusively count failures during start and also include failures while trying to instantiate plugins, etc., which it seems like you're on board with).
I haven't reviewed the tests for this change yet but the design seems good and as soon as the code review comments are addressed I'm happy to do another round and, if everything still looks good, give my plus one.

OK, I've made the changes that we discussed.

I've made changes to those test now @C0urante .  I couple of things worth noting: Changing the mock of the WorkMetricsGroup to a real object needs a fair few more mocks that relate to each other, so I've organised those into a @Before method instead of injecting them via a @Mock annotation, I hope that's okay. Doing so had the benefit that the tests are now more explicit about the values of the metrics being recorded, which may make the deletion of lines in WorkerTest more palatable. Having a look at the tests I'm modifying there, most of them actually already do have expectations on the statusListener being called, so I think it that case it's fair to say that the responsibility has simply moved to the WorkerGroupMetrics class (and therefore the WorkerGroupMetricsTest). For the test that doesn't seem to have any expectations on the status listener (testAddRemoveTask), I believe this might be because it's the WorkerTask's job to call the status listener once it's running, but that aspect is mocked away in that particular test.

Is this something you'd be willing to look at @gwenshap ?
(Apologies if this isn't of interest to you, I'm not very familiar with which committer would be best placed to have a look)

Perhaps this is something you would be interested in @rhauch  ?

Perhaps it's something you could look at @mjsax ?

What do you think @kkonstantine  ? Is this something you could look at?

Hey @C0urante, I'm not sure how long it usually takes for a committer to get around to looking at things like this, maybe several months is normal, but just thought I'd check with you, do you have any tips on how to get a committers attention?

Hi @michael-carter-instaclustr--unfortunately, it can take some time. Usually I tag @rhauch and @kkonstantine on GitHub since they're the committers that work most closely with the Connect framework, but I see you've already done that. You could try reaching out to the dev mailing list and asking for review there? This is a good bug fix and deserves a look; ideally, it shouldn't take months to get something like this reviewed.

@C0urante said this:

I'm also on the fence about the reshuffling of where recordConnectorStartupSuccess and recordTaskSuccess are called. The descriptions of the connector/task startup metrics in KIP-196 are a little thin; for example, the doc for connector-startup-success-total is "The total number of connector starts that succeeded.". A question that we'll want to answer before merging this is: if the framework successfully instantiates a connector and is able to call start on it, should that alone qualify as a "successful" startup, or does the call to start also have to go off without a hitch?

Later, @michael-carter-instaclustr replied:

My fundamental assumption in approaching this was that the ‘connector-startup-failure-total’ metric, described in the KIP as ‘The total number of connector starts that failed’, was intended to be a numerical record of failures within the ‘start’ method of the connector (And likewise for the task based metrics). Or in other words, they represented the health of the worker in an integration sense. (e.g. Does the worker have the right connectivity to do its job? Are people submitting valid configurations or are the users of Connect not understanding how to use it?) This to me seems like a useful aggregate metric that relates to the use of the worker as a whole more than a record of any individual connector failure.

Indeed the original intent for connector-startup-success-total metric was to represent the number of connectors whose start() method ran without throwing an exception. The connector-startup-failure-total metric OTOH was to represent the number of connectors whose start() method did throw an exception.
Likewise, for tasks and the corresponding task metrics.

Thanks for having a look at this @rhauch . I've updated with the suggested log messages, and reordered the methods and lines in the ConnectorStatusListener. I've also put back in most of the assertStartupStatistics. There were a couple that I couldn't leave in there without breaking the unit test. I believe this is because the recording of the statistic is now deferred to a piece of code submitted to the execution service, rather than something that is set directly by the startTask method. The only thing I could think of to keep them in there was to fake an executor service that would call things as soon as they were submitted, but since that isn't how it would work in reality, it didn't seem like the right thing to do. Neither did keeping them in there and just asserting that they were 0 the whole time.

Did you have any further comments on this @rhauch ?

Thanks again, @michael-carter-instaclustr. And I apologize for the unacceptably long delay on my part with this PR.
FYI: I merged from trunk to get the onRestart(...) method that KIP-745 (PR #10822) added recently (prior to the creation of the 3.0 branch). I then implemented these methods by simply calling the delegate, as with the other methods. Simple enough change, but necessary before merging.

Awesome. Thanks @rhauch !


Migrate from travis-ci

Now that travis cut the number of builds for open source projects, builds are very slow. I think moving to github actions should be good?

Hey, just a little ping that this should be closed as it's been completed by GH-389. My apologies if I'm mistaken.

Yeah, this can be closed. Thanks!


AttributeError: 'Namespace' object has no attribute 'max_motion_length'

Hi Author,
I am trying to train momask on my customized data. I get the following error:

Thank you!

Try to make your own configure for your data, e.g. opt.max_motion_length = xxx

hi @Murrol ,
Thanks for your reply.
1. I comment the eval part, the training works well. Does this parameter have influence on performance?
2. Do you have standard rule of defining the max_motion_length? How to define it in HumanML3D dataset?
Thank you

Hi, thanks for your interest.

hi @Murrol ,
Thanks for your reply.

I comment the eval part, the training works well. Does this parameter have influence on performance?

It would not affect training. While, sometimes, it would be helpful to use the eval part to select the checkpoint for the best performance. Besides, you can either select checkpoint manually or based on the accuracy/loss curve.

Do you have standard rule of defining the max_motion_length? How to define it in HumanML3D dataset?

We do not have a standard to define the max_motion_length. Most of the motions in the dataset fall within this length. (Actually, we obtained the motion dataset first, processed them to a suitable length which is ~10s, and then annotated them to build HumanML3D.)

Thank you

hi @Murrol ,
Thanks for your reply.
1. That's what I want to know. How to select the checkpoint by using your eval part. The problem is I don't have a pre-defined opt.txt. So I would like to know, how you do that?
2. If you processed your dataset ~10s, would I say the max_motion_length == 10x30fps is a good setting for max_motion_length parameter? Thanks

hi @Murrol ,
Thanks for your reply.

That's what I want to know. How to select the checkpoint by using your eval part. The problem is I don't have a pre-defined opt.txt. So I would like to know, how you do that?

The eval part can calculate the FID on the validation set. Thus, we are able to select the checkpoint with the best validation FID. You can train a motion feature extractor through a reconstruction objective or text-motion clip objective on your own data. You may refer to our prior work text-to-motion for the details.

If you processed your dataset ~10s, would I say the max_motion_length == 10x30fps is a good setting for max_motion_length parameter? Thanks

You are right. While HumanML3D is at 20fps, so the maximum frame number is about 200. It's not very strict especially on your own dataset; you can adjust it based on your needs.

Hi @Murrol ,
Thanks for your reply.
That's my question. After training RVQVAE. How to evaluate the checkpoints and get the best checkpoint with the highest FID score? Thanks

If I understood your question correctly, that's the simplest answer I can provide:
Save the checkpoint every 500 iterations, load each checkpoint, run an evaluation round on the validation set, note down the results, and then compare the results from all the checkpoints you have. This way, you'll be able to determine which checkpoint suits your needs the best.

@Murrol  thank you.


pasting content from a webpage using dark theme results in white background

copy content from a webpage (white background, black text color) to a page in bookstack
and save
the resulting page in bookstack shows white bars with the black text instead of changing the text color to grey or white and showing the page with a black background as intended
tested with BookStack version v0.29.0

Hi @Knaui,
Could you provide an example of a source website that causes this for you?
Would also be great to confirm what browser/operating system you're using.

Since no further information was provided I'll close this off.


Text Extractor doesn't extract

Microsoft PowerToys version
0.69.1
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
TextExtractor
Steps to reproduce
https://user-images.githubusercontent.com/113242950/232063418-a4736df4-fbb6-451d-b80d-46ca9be14542.mp4
✔ Expected Behavior

Copying of text in Clipboard after being selected.
After the copying of text, closing of text extractor interface(Interface to select text).

❌ Actual Behavior
The extractor doesn't copy the text, neither closes itself upon selection.
Other Software
No response

Found the problem, looks like the extractor cannot work if the text isn't in plain text format or if the selection field is too small.


New buffer

Could you be more specific?

Not sure if this is the issue @zwj741 was posting about, but I'm getting this error (i believe from nan 2.3.2 included by ketyar, but it's hard to find the actual trace).
DeprecationWarning: Using Buffer without `new` will soon stop working. Use `new Buffer()`, or preferably `Buffer.from()`, `Buffer.allocUnsafe()` or `Buffer.alloc()` instead.

Update: manually copied over 2.4.0 (latest) to the keytar dir, still getting the above deprecation notice under node 7.0.0


Exception raised : portalocker.exceptions.LockException: [Errno 9] Bad file descriptor

https://github.com/python-cachier/cachier/blob/5776ee8d63c8a5719ccd3737f0f504bc1a7eb679/cachier/pickle_core.py#L145C67-L145C67
On linux system, the cache file seems to be closed twice. When replacing this part of code with:
#with portalocker.Lock(fpath, mode='rb') as cache_file:
cache_file = portalocker.Lock(fpath, mode='rb')
if cache_file is not None:
try:
self.cache = pickle.load(open(cache_file.filename,"rb"))
except EOFError:
self.cache = {}
the  cachier seems to work fine.

I'm sorry, that's not enough information to address the bug.
The package is tested and used on Linux, and this is the first report of such an issue. Also, you didn't explain in anyway how this hampers in any way use of the package.
Also, I would not move from a context manager - which is the correct and more safe way to lock a file - to a simple use of Lock without a much better explanation.
This is issue is marked with wontfix until the issue is shown to be reproducible on any Linux machine, and we get a better explanation of what you believe might be causing the redundant locking, the negative effects of this phenomena and possibly even a better suggestion for a fix (I can't see why portalocker's context manager will cause double locking but their Lock method will not).

I am not suggesting a solution with the modification on my first comment : this is really uggly and should not be used. However cachier is not usable for me at this time.

In fact it seems to be the same as #86 with NFS mount. When forcing the cache_dir on the local directory (like /tmp) everything is working

@lordjabez Yes, it works when you move the cache_dir to a local disk. Most of my apps are using NFS shares and do depend on a single computer. After looking for solutions, I found that it is not a problem with cachier but portalocker.
In fact I'm trying to use an app in which cachier is used on a network with share disk spaces

Perhaps you can create an issue with portalocker and link here? We can update the dependency when it's fixed?

Great, I've responded in the portalocker issue you've created with a link to the first NFS-related issue. Let's see when does this gets solved.

[like]  Coat, Alain reacted to your message:

From: Shay Palachy-Affek @.>
Sent: Tuesday, December 5, 2023 7:08:26 PM
To: python-cachier/cachier @.>
Cc: Coat, Alain @.>; State change @.>
Subject: Re: [python-cachier/cachier] Exception raised : portalocker.exceptions.LockException: [Errno 9] Bad file descriptor (Issue #128)
Great, I've responded in the portalocker issue you've created with a link to the first NFS-related issue. Let's see when does this gets solved.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/python-cachier/cachier/issues/128*issuecomment-1841456651__;Iw!!ElGdukoduuk!WBpC30Z7nsrQTXukPgXZY70clmdtC80EKE8g072MC4z_hRs79yygzQVxex0pjdMIZ6-I199ZZ8bnifHUpDQWIE3n0R8$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AXHLAOMMYH52V4STKUDGCNDYH5WKVAVCNFSM6AAAAABAFCJCEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRGQ2TMNRVGE__;!!ElGdukoduuk!WBpC30Z7nsrQTXukPgXZY70clmdtC80EKE8g072MC4z_hRs79yygzQVxex0pjdMIZ6-I199ZZ8bnifHUpDQW6hyf_Oo$.
You are receiving this because you modified the open/close state.Message ID: @.***>


Update unknown_order to 0.6

New version of dependency was just released, would be great to have libpaillier compatible with it. Let me know if you would be interested in PR for bumping dependency.

I see that dependency was updated, thanks!


PauseBeforeServiceDiscovery is not consumed anywhere in the library

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[*] Android
[] tvOS
[] macOS
[] .NET Standard
UWP IS NOT SUPPORTED DURING THE BETA PERIOD - ONLY PRs ARE WELCOME FOR NOW

Version of Library
6.1
Expected Behaviour
PauseBeforeServiceDiscovery affects app behavior in some way on Android.
Actual Behavior
There are no consumers of CrossBleAdapter.PauseBeforeServiceDiscovery on Android in the source code.
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

This is a variable which I haven't decided which I need long term or not.  Please file things that are actually causing issues.


Differential download of electron-updater doesn't work because of version mismatch

Describe the issue / bug.
Differential download of electron-updater doesn't work because of version mismatch, it looks like that electron-builder included in the boilerplate doesn't work well with latest electron-updater
How can I reproduce this problem?
I was using vue-cli to create the project as the doc suggests. Then I got the following version of electron-builder in my package.json.
"electron-builder": "^19.19.1"
Later after some work, I added the latest the electron-updater in the index.js as the doc suggests.
"electron-updater": "^3.1.2"
It mostly worked well except for the differential download, which always failed because it can't find the old installer file "__installer.exe", while there was an installer.exe in the %APPDATA% instead.
Error log:

[2018-09-30 22:58:07.574] [error] Cannot download differentially, fallback to full download: Error: ENOENT: no such file or directory, open 'C:\Users\xxx\AppData\Roaming\app-product-name\__installer.exe'

After some dig, I found that it's a version mismatch issue that newer version electron-updater was expecting __installer.exe while older version electron-builder was generating installer.exe.
It would be great to lock the version of electron-updater in the package.json of the boilerplate.
Tell me about your development environment.

Node version: 8.2.1
NPM version: 5.6.0
YARN version: 1.9.4
vue-cli version: (if necessary) 2.9.1
Operating System: Windows 10 x64

After updating electron-builder, differential download works again, it still would be great to lock the electron-updater version in some regard.
"electron-builder": "^20.19.2"


Update the SDK codebase to work with the latest channel version

Oh, nice! When you said make a PR I thought you meant to just pin the dependency with a hash without the API changes :D
The bad news is I will get a lot of conflicts when rebasing my work on #73 on top of this :scream:

The bad news is I will get a lot of conflicts when rebasing my work on https://github.com/frequenz-floss/frequenz-sdk-python/issues/73 on top of this :scream:

This one is easy to redo,  if you want to take #73 first.

I will give the rebase a chance and let you know if it messes up my stuff too much.


Tiles scrambler assumes 4 tiles

The tiles scrambler takes a parameter num_tiles which allows the user to specify the numer of tiles that should be generated, but the implementation assumes that the number of tiles should always be 4.
The tiles scrambler function should be adapted to correctly generate a variable number of tiles.

Fixed by #26


Selectors are broken for tags-dropdown

tags-dropdown isn't working as expected due to broken selectors.
Actual:

Expected:

Investigated this issue for a while and it seems that links to tags aren't replaced correctly.


Consider implementing a node client for the WildFly DMR API

Ref: https://github.com/hal/dmr.js
Ref: http://hpehl.info/independent-jboss-admin-console.html

Adding in the link for the Wildfly HTTP management API
https://docs.jboss.org/author/display/WFLY10/The+HTTP+management+API

More operations:
http://www.mastertheboss.com/jboss-server/jboss-script/managing-jboss-wildfly-using-httpjson-api

More operations:
http://middlewaremagic.com/jboss/?p=2488

Some work started:
https://github.com/bucharest-gold/ndmr
The idea is to 'translate' the dart version to javascript

Implementing this is likely a complex and large job, and Lance and I are wondering if there is strong enough demand from the Wildfly team for this functionality.
@lance is going to follow up with the original post and see what sort of demand is on this work.

Great move!
...and risky : https://github.com/bucharest-gold/ndmr/issues/18

@balunasj I've emailed Galder who was originally asking for this, but have not heard back. Unless we want to reach out directly to the WildFly team, I'd say this is done. There doesn't seem to be great demand for it.

I am closing this for now, and if we find that there is a demand for a DMR client, we can pick it back up with a new issue.


[SP-3367] - Backport of PDI-16049 - getVariable does not return variable set by setVariable in same Javascript step

Update the step's variable space as well when calling the setVariable
function.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesAddedFunctions.java
  engine/test-src/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesModTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.14%:small_red_triangle_down:
Complexity Change: -7.69%:small_red_triangle_down:

org.pentaho.di.core.util.JavaScriptUtils

Branch Change:  + 1.69%
Complexity Change:  + 2.50%
Instruction Change:  + .99%
Line Change:  + 1.00%

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -.39%:small_red_triangle_down:
Complexity Change: -.51%:small_red_triangle_down:
Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change:  + 1.01%
Complexity Change:  + 1.06%
Instruction Change:  + .17%

org.pentaho.di.job.entries.ftpsget.JobEntryFTPSGet

Branch Change:  + .53%
Complexity Change:  + .56%
Instruction Change:  + .07%

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.28%:small_red_triangle_down:
Line Change: -3.87%:small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2.08%:small_red_triangle_down:
Complexity Change: -2.11%:small_red_triangle_down:
Instruction Change: -.14%:small_red_triangle_down:
Line Change: -.37%:small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2.00%:small_red_triangle_down:
Complexity Change: -1.89%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.ldapinput.LDAPInputMeta

Branch Change: -1.61%:small_red_triangle_down:
Complexity Change: -.97%:small_red_triangle_down:
Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -.06%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 4.71%
Complexity Change:  + 5.41%
Instruction Change:  + .18%
Line Change:  + .48%

org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesAddedFunctions

Branch Change:  + .56%
Complexity Change:  + .36%
Instruction Change:  + 1.30%
Line Change:  + 1.58%
Method Change:  + 2.02%

org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesAddedFunctions.new Object() {...}

Complexity Change:  + 100.00%
Instruction Change:  + 87.88%
Line Change:  + 100.00%
Method Change:  + 100.00%

org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesAddedFunctions.VariableScope

Complexity Change:  + 25.00%
Instruction Change:  + 6.90%
Method Change:  + 25.00%

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -.53%:small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change:  + .10%
Complexity Change:  + .14%
Instruction Change:  + .09%
Line Change:  + .11%

org.pentaho.di.www.TransformationMap

Branch Change: -1.14%:small_red_triangle_down:
Complexity Change: -1.54%:small_red_triangle_down:


Raster Conversion is missing in QGIS 3.16

Description
I have installed QGIS 3.16 on my windows 11 and unfortunately when I click on "Raster" it doesn't give me the "Conversion" option. I need to polygonise something and I'm even unable to activate processing tool box to search it there!
The thing is I have the same problems with other versions of QGIS including 3.10 and 3.14!
Can anybody help with that?

Turn on Processing in the Plugin manager.
FYI, this is the issue report for QGIS website (https://qgis.org) not the one for the software which is at https://github.com/qgis/QGIS/issues (as indicated in the issue report form)

Thank you for your email. It was the biggest help!
Also, thank you for mentioning the correct place to put the issue. I'm a
new comer to this environment
On Tue, Feb 1, 2022 at 1:48 PM Harrissou Sant-anna @.***>
wrote:

Turn on Processing in the Plugin manager.
FYI, this is the issue report for QGIS website (https://qgis.org) not the
one for the software which is at https://github.com/qgis/QGIS/issues (as
indicated in the issue report form)
—
Reply to this email directly, view it on GitHub
https://github.com/qgis/QGIS-Website/issues/971#issuecomment-1026806459,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXR54XDRM2XH6UAIKO4OW53UY7JBZANCNFSM5NJBHZBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello,
How can I get help for the following error I receive while working with the
raster calculator in attribute table?
I receive  "syntax error" after putting in the commands in the Expression
part and then I'm unable to click okay.
Thank you,
Shaghayegh
On Tue, Feb 1, 2022 at 2:45 PM Shaghayegh Firouzbakhsh <
@.***> wrote:

Thank you for your email. It was the biggest help!
Also, thank you for mentioning the correct place to put the issue. I'm a
new comer to this environment
On Tue, Feb 1, 2022 at 1:48 PM Harrissou Sant-anna <
@.***> wrote:

Turn on Processing in the Plugin manager.
FYI, this is the issue report for QGIS website (https://qgis.org) not
the one for the software which is at https://github.com/qgis/QGIS/issues
(as indicated in the issue report form)
—
Reply to this email directly, view it on GitHub
https://github.com/qgis/QGIS-Website/issues/971#issuecomment-1026806459,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXR54XDRM2XH6UAIKO4OW53UY7JBZANCNFSM5NJBHZBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Response is 409 when app exists

Description
Currently there's no check of whether an app exists or not, so that an Internal Exception is thrown by the server.
Solution
Added a check in PushApplicationService. When an existing app is being added again, an IllegalArgumentException will be thrown. This exception is handled by the endpoint when trying to add the app, in that case a 409 Conflict will be sent back to the client.
JIRA
https://issues.jboss.org/browse/AGPUSH-1996
This is the equivalent of #906 for the master branch.

ok
On Fri, 25 Aug 2017 at 10:02, Jose Miguel Gallas Olmedo <
<EMAIL_ADDRESS>wrote:

@josemigallas commented on this pull request.
In
service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/PushApplicationServiceImpl.java
https://github.com/aerogear/aerogear-unifiedpush-server/pull/905#discussion_r135203862
:

     pushApp.setDeveloper(loginName.get());

   pushApplicationDao.create(pushApp);

   final String pushApplicationID = pushApp.getPushApplicationID();

   if (findByPushApplicationID(pushApplicationID) != null) {

       throw new IllegalArgumentException("PushApplicationID exits already: " + pushApplicationID);

   } else {

       pushApplicationDao.create(pushApp);

I think that querying the DB before is more robust. As @ziccardi
https://github.com/ziccardi suggested, the transaction might not be
committed right away so the "ID already exists" error wouldn't be caught by
the time the client is trying to add the app. By querying the DB prior the
create, we can handle this and for instance warn the client that it is
performing an illegal transaction.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/905#discussion_r135203862,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJnznc1zpBsmTxGv8Hs47sAhCZ4fp9Jks5sbn-sgaJpZM4PBTID
.

--
Sent from Gmail Mobile

I think it's ok.
If you want the other, imo more verbose way, make URI final
On Fri, 25 Aug 2017 at 09:58, Jose Miguel Gallas Olmedo <
<EMAIL_ADDRESS>wrote:

@josemigallas commented on this pull request.
In
jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java
https://github.com/aerogear/aerogear-unifiedpush-server/pull/905#discussion_r135203216
:

     }

   pushAppService.addPushApplication(pushApp);

   URI uri = UriBuilder

Don't you think it's a bit long code to be inline?
return Response.created(UriBuilder.fromResource(PushApplicationEndpoint.class)
.path(pushApp.getPushApplicationID())
.build())
.entity(pushApp)
.build();
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/905#discussion_r135203216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJnzmm75YQ_IWrBi5qFzBAUoiN05BzGks5sbn67gaJpZM4PBTID
.

--
Sent from Gmail Mobile

On Fri, 25 Aug 2017 at 10:36, Massimiliano Ziccardi <
<EMAIL_ADDRESS>wrote:

@ziccardi commented on this pull request.
In
jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/PushApplicationEndpoint.java
https://github.com/aerogear/aerogear-unifiedpush-server/pull/905#discussion_r135209465
:

     }

   pushAppService.addPushApplication(pushApp);

   URI uri = UriBuilder

@josemigallas https://github.com/josemigallas Nope. If you assign it to
a variable, when I read the code I think you will use the variable
somewhere else too. If you inline it, I automatically understand it won't
be used in any other place.

right, and the var is mutable that way
—

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/905#discussion_r135209465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJnzlr2Ca0r9XbgeC-feytpOT1EaiPdks5sboeZgaJpZM4PBTID
.

--
Sent from Gmail Mobile

LGTM but my previous comment.

@ziccardi I think I "solved" your previous comment here? https://github.com/aerogear/aerogear-unifiedpush-server/pull/905/files#diff-c5411a9eca95c43b3205797aceafa013R54

@josemigallas I think so. Sorry, didn't see that change


Remove Private Keys

Hi,
I was participating in owncloud bug bounty program on hackerone and found out that you are leaking private keys at https://github.com/owncloud/nexus/blob/master/configs/ssl/private-key.pem. Even if they are test keys, this is not a good security practice.
Further, you are also leaking JWT secret key at all the files under https://github.com/owncloud/nexus/tree/master/configs/reva  folder.
Please, remove the keys and rotate them!
Regards
Vikas Rawat
https://hackerone.com/mr_r0w07

It's not planned to remove the files, they are used for development and local testing.

hi @tboerger
I was asked to open an issue here by owncloud's security team on hackerone.
Just wanted to confirm this only if they are for testing or deployed officially.
Closing this issue now!
Thanks,


Airtable integration

I've been using Airtable to mock up my course assignments and grading structure recently. If you haven't used it, it's essentially a really good UI for a relational database/spreadsheet similar to smartsheet, but with extensive api support. This seems like a tool perfect for HAX integration, everything is json :)
To show a use case, I mocked up a feedback system similar to the elms studio feedback tool @nikkimk and I talked about forever ago, with pre-made feedback terms that you can pull into different categories. Using this to manage rubrics, and presenting things into a student-facing lms/site would be a killer use case.

that's cool, what would an integration look like in your mind? Ability to embed these via HAX?

Embed would be low hanging fruit. But fields integration would be truly awesome! Similar to hooking up content types to web components in Drupal. You can export and download the airtable data, so if you wanted permanence for archiving purposes, I think it meets that goal as well, though you'd need the option to point to and extract data in a file versus a rest call.

New issues opened around this and grade book takes into account these screenshots (and without airtable)