slurm: <IP_ADDRESS> -> <IP_ADDRESS>

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/slurm/versions.
meta.description for slurm is: '"Simple Linux Utility for Resource Management"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sacct had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sacctmgr had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/salloc had a zero exit code or showed the expected version
/nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sattach passed the binary check.
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sbatch had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sbcast had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/scancel had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/scontrol had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sdiag had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sinfo had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/smap had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sprio had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/squeue had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sreport had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/srun had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sshare had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/sstat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/strigger had a zero exit code or showed the expected version
/nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/slurmctld passed the binary check.
/nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/slurmd passed the binary check.
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/slurmdbd had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin/slurmstepd had a zero exit code or showed the expected version
3 of 22 passed binary check by having a zero exit code.
0 of 22 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>
directory tree listing: https://gist.github.com/b8532cb83ff00410ae325f471574b1dd
du listing: https://gist.github.com/dd0f14a1006d890b8d30035f2c493a07

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

14 total rebuild path(s)
4 package rebuild(s)
4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python27Packages.pyslurm
python37Packages.pyslurm
slurm
slurm-spank-x11

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A slurm https://github.com/r-ryantm/nixpkgs/archive/f83dd11e5ccab3cbd4ce14a390f22594470f1ddd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>
ls -la /nix/store/vwpn8ri4j4zskc73i8p66ih2njw3zzrj-slurm-<IP_ADDRESS>/bin

cc @jagajaga @markuskowa for testing.

@GrahamcOfBorg build python36Packages.pyslurm
@GrahamcOfBorg build slurm-spank-x11

@markuskowa This is not blocked by pyslurm, it is already broken on master due to the previous slurm update.

@veprbl I did overlook that.


[Bug] --state flag is not being prioritized over $DBT_STATE environment variable

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
1.8.3 is not properly setting the --state flag if $DBT_STATE has already been set. We ran into this issue when trying to run dbt ls --select result:success --state target --resource-type model
I added debugging to state.py to get hte following output. In both examples we have $DBT_STATE set.
dbt 1.7.14
$DBT_STATE: ../docs/dbt-docs
state_path:  target

dbt 1.8.3
$DBT_STATE: ../docs/dbt-docs
state_path:  ../docs/dbt-docs

Expected Behavior
--state directory should be prioritized over the $DBT_STATE environment variable
Steps To Reproduce

Set $DBT_STATE to some arbitrary path that is not ./target
Run any dbt build command
Run dbt ls --select result:success --state target
Check the state_path variable that is set in contracts/state.py

Relevant log output
No response
Environment
- OS: MacOS Sonoma 14.5
- Python: Python 3.10.3
- dbt: 1.8.3

Which database adapter are you using with dbt?
Postgres -- v1.8.2
No response
Additional Context
No response

Thanks for raising this issue @tweavers!
This looks the same as https://github.com/dbt-labs/dbt-core/issues/10304, so I'm going to close this one as a duplicate.
Workaround
In the meantime, the workaround is to add the --state flag before the ls sub-command like this:
dbt --state target ls --select result:success

Could you let me know if that workaround doesn't behave correctly?

Thanks @dbeatty10 !


AMBARI-23999 Remove hardcoded logic in UI to create HDPCORE service group and create multiple service groups

How was this patch tested?
19688 passing (20s)
46 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2539/
Test FAILed.
Test FAILured.

2532486 [INFO] Ambari Web ......................................... SUCCESS [02:23 min]


Bug: crash when init built-in user

When a brand new user start to user casdoor, casdoor will insert the build-in user into database, which can lead to a panic in current version .
xxx@xxx:~/xxxxxxx/casdoor$ go run main.go
[xorm] [info]  2021/12/12 20:39:09.671852 PING DATABASE mysql
panic: Error 1364: Field 'ranking' doesn't have a default value

goroutine 1 [running]:
github.com/casbin/casdoor/object.AddUser(0xc00044a700, 0xc00044a700)
        /home/xxx/workspace/casdoor/object/user.go:326 +0x230
github.com/casbin/casdoor/object.initBuiltInUser()
        /home/xxx/workspace/casdoor/object/init.go:73 +0x21d
github.com/casbin/casdoor/object.InitDb()
        /home/xxx/workspace/casdoor/object/init.go:21 +0x2a
main.main()
        /home/xxx/workspace/casdoor/main.go:33 +0x2b
exit status 2

(sorry I need to hide some personal information with xxx)
The apperance rate of this bug is 100% for brand new users whose database hasn't got a table called 'casdoor'
I have fully examined this bug and I will explain the reason of this bug later ,and ask for further opinion from @hsluoyz  @nomeguy about how to fix it

The reason is as follow:
In a recent change introduced by @nomeguy in commit eca1d23e35174a26cdbd00bc8ee064b286b74e9c
https://github.com/casbin/casdoor/blob/94c78593fc693569c773df3f0bebe339ff82f8a6/object/user.go#L54
This attribute 'Ranking' was set to auto increment, while the primary key of this table is still another two attrubutes "Owner" and "Name"
https://github.com/casbin/casdoor/blob/94c78593fc693569c773df3f0bebe339ff82f8a6/object/user.go#L25
https://github.com/casbin/casdoor/blob/94c78593fc693569c773df3f0bebe339ff82f8a6/object/user.go#L26
However

Mysql doesn't support non-primary key to be set as "auto increment"
But setting ranking to primary key won't help, because

2.1 xorm doesn't support non-primary key to be set as  "auto increment". You can find out this in the xorm source code
https://gitea.com/xorm/xorm/src/commit/303b1aeb7772ebd6253c72ba4853ce8cd3dadb44/dialects/dialect.go#L324
2.2 xorm doesn't support auto increment on primary key when there are  more than 1 primary key,
see
https://gitea.com/xorm/xorm/src/commit/303b1aeb7772ebd6253c72ba4853ce8cd3dadb44/dialects/dialect.go#L320
and
https://gitea.com/xorm/xorm/src/commit/303b1aeb7772ebd6253c72ba4853ce8cd3dadb44/dialects/mysql.go#L647
so when the table is created, the "ranking " attribute in mysql  is actually int, without auto increament, without default value, which lead to the error "Field 'ranking' doesn't have a default value"

Done at: https://github.com/casbin/casdoor/commit/8d8c662e58a44e455936cd92853ed781db3f2614


Add new "retime" plugin to change PTS/DTS values

With this new plugin it's possible to modify the PTS/DTS values.

Hi @lelegard ,
I hope you agree with this new plugin.
However, I need your help to manage the time back in the counters. Any idea?
Regards.

Two questions:
Is it on purpose that the PCR are not modified? Normally, the PTS and DTS values are based on the PCR reference clock of the service. Modifying the PTS and DTS without modifying the PCR can make the stream unplayable.
Wouldn't it be better to implement this as an enhancement of  pcradjust ?

Two questions:

Hi,

Is it on purpose that the PCR are not modified? Normally, the PTS and DTS values are based on the PCR reference clock of the service. Modifying the PTS and DTS without modifying the PCR can make the stream unplayable.

No. Modifying the PTS and DTS values are for sub-stream synchronization. One example: you want to add a new data stream to a current service muxing it from an external source. And this data stream requires to be in synch with the rest of the sub-streams in the service. Then you can use this plugin to achieve this objective: after muxing it you can calculate the offset and apply it.

Wouldn't it be better to implement this as an enhancement of pcradjust ?

You're the developer of the TSDuck, and I take your opinion very seriously. However, for this particular case I suggest to not merge it.
Regards.

OK, that makes sense. The plugin pcradjust makes a global and automated modification while retime fixes a specify issue that was manually detected on individual PID's.
To comply with the usual policy in open source projects, please update the copyright header with your full name. I cannot claim copyright for a file I did not write.

To comply with the usual policy in open source projects, please update the copyright header with your full name. I cannot claim copyright for a file I did not write.

Done (partially)! A lot of code is copy-and-paste from your code, so you need to appear on it. Futhermore, I'm sure you'll continue contributing to it. :laughing:
Regards.

Please use your real name, TSDuck is an open and transparent project, see CONTRIBUTORS.txt.

Hi @lelegard ,
I do a small makeup change in the debug message. Please, merge this new plugin. I'm using it a lot in my processing. And it works with both: positive and negative offsets without troubles.
Thank you!

Hi @lars18th,
I have seen that you added the confused emoji to my request to provide your real name as contributor.
Let me clarify my position. The world of TV is roughly divided in industries, service providers, TV operators and pirates. I have worked in the first three categories and I have always fought against the fourth one. A toolbox such as TSDuck is useful to everyone, equally. I cannot prevent pirates to use TSDuck to build their infrastructure. And I know that some of them do. But it must be clear to everyone that TSDuck is made by engineers for engineers. I want TSDuck to be a fully transparent project: open source, identified web sites, identified authors and contributors.
In the world of Pay-TV, anonymity equals piracy. This may seem unfair but this is the way it is perceived by the industry. So, to maintain the trust in TSDuck, I keep anonymity away from it.
For small bug fixes, I can accept anonymous PR's because they are safe to validate. But when it comes to major contributions such as new plugins and their subsequent evolution, I need to keep a strict public policy.
I am sorry if you disagree, but this is a very sensitive topic in the TV industry.

Hi @lelegard,
I'm back from vacation these days. That's why it's been a long time since I've made any comments.
As for your position, I now understand your reasons. And I accept it. However, although I’m an engineer, I cannot mix my work with other projects. And for that reason I can only use an alias in Github. So in my case it’s impossible to meet your requirements. I hope you can at least understand my position. And if for any reason you think that my comments or collaborations with this project may be harmful, please tell me, as I wouldn't want to interfere with this great project.
I hope someday I can still meet you in person.
Regards.

However, although I’m an engineer, I cannot mix my work with other projects. And for that reason I can only use an alias in Github.

Well, all contributors in TSDuck are engineers. I am a full time employee of my company. I work at home on TSDuck and I work at the office for my company. The days where TSDuck was useful to me everyday at work are unfortunately gone (although some of my colleagues still find it useful). Unless you work for some secret service, you are free to work on personal projects from home.

I hope someday I can still meet you in person.

I will spend one day at IBC, for what it's worth...

Hi @lelegard ,

However, although I’m an engineer, I cannot mix my work with other projects. And for that reason I can only use an alias in Github.

Well, all contributors in TSDuck are engineers. I am a full time employee of my company. I work at home on TSDuck and I work at the office for my company. The days where TSDuck was useful to me everyday at work are unfortunately gone (although some of my colleagues still find it useful). Unless you work for some secret service, you are free to work on personal projects from home.

It seems to me that you haven't understood the reason. For sure, I'm not involved in any secret service or piracy company. But the truth is, I can't do what you're asking.

I hope someday I can still meet you in person.

I will spend one day at IBC, for what it's worth...

I can't attend it this year. Sorry!
I will try to continue collaborating with this project if you don't mind. Please let me know if at any time my participation is a problem. I don't want to interfere with this useful project.
Regads.

Hi @lelegard ,
I updated the plugin with the inclusion of the Visual files required to compile it for Windows. And I changed the attribution to Public Domain. So I don't need at all that you include my name (or nick) in the source code. And publishing it as Public Domain, I hope you can include it.
Regards.

I changed the attribution to Public Domain. So I don't need at all that you include my name

The license (public domain or whatever) and the contributor identity / anonymity are two independent data. I have published the transparency rule in the contributions guidelines. Originally, I did not imagine it was a problem for any developer to identify himself and I thought this rule was implicit. Now, it has become explicit.
And BTW, your source is not anonymous, it mentions my name. This is impersonation.

Hi @lelegard ,
I'm just looking for a comfortable solution for both of us.

And BTW, your source is not anonymous, it mentions my name. This is impersonation.

That's not my objective. The skeleton of the source is your code, and it uses your header. So I'm only adding this line // Plugin developed as Public Domain. to distribute my contribution as Public Domain.
I'm sorry if my (required) position does not meet your requirements. I only want to contribute. Please take note that:

I could use a pseudonym (fake name), but that would be hoaxing and I don't want to dirty your excellent work.
I honestly tell you that I don't work for any company that works on piracy (you can believe me or not).
I hope someday we can get to know each other. My problem is not that you can meet me personally (which I would like to be able to meet you, on the other hand).

So tell me what I can do to meet your rules.
Regards.

Closing this one (too old and not compliant with the contribution policy)

Hi @lelegard ,

Closing this one (too old and not compliant with the contribution policy)

I understand your position. No oposition to it.
Although perhaps you would like to implement an alternative by yourself. So you can provide a similar plugin to modify the PTS/DTS values, or enhance some already existent plugin for a similar functionality. One use case of such plugin is this: when you remux some services, if you want to merge/inject/transplant some pid from one service to another, then you need to sync the clock of the moved substreams with the clock of the target service. Then in this case such functionality is useful.
What you think?

Hi @lelegard ,
With all due respect, and with no intention of interrupting your great work, I would like to know your opinion about my previous comment. Please, could you say something?

Although perhaps you would like to implement an alternative by yourself. So you can provide a similar plugin to modify the PTS/DTS values, or enhance some already existent plugin for a similar functionality. One use case of such plugin is this: when you remux some services, if you want to merge/inject/transplant some pid from one service to another, then you need to sync the clock of the moved substreams with the clock of the target service. Then in this case such functionality is useful.

Thank you very much! :wink:


Move accumulator to from header gossip to history network

Move accumulator to the history network
Add definitions for content keys of master and epoch accumulator
Add Serialization for accumulator content
Add test vectors for accumulator content keys

This moves the accumulator definition from header gossip to the history network and adds the content keys as defined in https://github.com/ethereum/portal-network-specs/issues/153:

One difference is that the content key for the master accumulator is directly a Union type.

Not sure what to do with chain_id at this point? Get rid of it everywhere or use it everywhere? For now I did neither and left it untouched :)
The history spec could probably use some reorganization after this and some text is redundant, but that is not the scope of this PR. Scope right now is defining accumulator keys & content serialization and adding test vectors so that we can easily make the clients compatible. This is the current implemented state of Fluffy, but we can obviously adjust.

This all looks good to me, with the exception of my one question regarding the master accumulator key.

@pipermerriam Any thoughts on what we have here?


Bump Go to 1.18

Output of helm version:
None
Output of kubectl version:
None
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
None
Bump Go to 1.18

I wonder why  it's 1.17 in latest go.mod now ?
https://github.com/helm/helm/blob/44ec1c1575d405675272ee2d8131130a5decee7c/go.mod#L1-L5


Error page

Closes #82
Example Error page is not yet prepared in Storefront UI, so I have created this Error page basing on desing from https://www.figma.com/file/hrwE3VsMBHgdJoS86rVr4W/Desktop-and-Mobile-Vue-Storefront?node-id=551%3A93

We, the people from shopware-pwa project, thank you very much for this page!


[FEATURE] Allow for customization of "Enter database name" in

Is your feature request related to a problem? Please describe.
The  entry might semantically stand for something other than a database (e.g. a catalog). Yet, in the dropdown menu "Enter database name" is hardcoded.
Describe the solution you'd like
Allow for the customization of "Enter database name".
Describe alternatives you've considered
None
About You
Name: Ali Smesseim
Company: Databricks

internal tracking id : 1268963

This will be resolved as a part of the future Tableau 2021.4 release.


the data issue

Hi, I am very sorry to bother you again.
thanks for your reply.
I have run the code again, but i got an anther error, "FileNotFoundError: [Errno 2] No such file or directory: 'prepro/raw/cifar100/physical_entity/cloud/train_cloud_s_000462.png'", do I need to preprocess the data? there is any instruction to proprecess the data?

Sorry, I missed this when releasing the code. You can check the new readme for the download link.


Don't naively apply the bridging peephole to AnyObject? -> Any? -> AnyObject

Also, fix some logic in the peephole that was incorrectly recognizing
T? -> U? -> AnyObject as a force instead of a request to create NSNull.
In both cases, we ought to still be able to do much better than the
unpeepholed code by just applying the peephole and then merging in NSNull
in the nil case, but in the short term we need to fix this bug.
Fixes rdar://35402853

@swift-ci Please test and merge.

@swift-ci Please smoke test.

@swift-ci Please smoke test.


484/zenodo integration

Read/write files from zenodo
Create catalog from single or multiple repositories
Added tests
Added read/write function to package
Made changes to control class and plugin class
fixes #484

Search by status was not working as expected so I will report it.
Please make sure that all the checks pass. Please add here any additional information regarding this pull request. It's highly recommended that you link this PR to an issue (please create one if it doesn't exist for this PR)

@roll this is ready for review. Thanks!

Thank you @aivuk!.
I have added the comments and also replied in PR.
I have made new changes it is ready for review! @roll @aivuk


Should not have ftdetect for sbt file

I have vim-sbt installed but if it is load before vim-scala then *.sbt will have the scala filetype and the syntax highlighting will be wrong.

Seems like it would make sense if vim-scala's ftdetect changed from:
au BufRead,BufNewFile *.scala,*.sbt set filetype=scala

to:
au BufRead,BufNewFile *.scala set filetype=scala
au BufRead,BufNewFile *.sbt setfiletype scala

The setfiletype form will not change it if already set by something loaded earlier. That should continue to work well for people that only have vim-scala installed. Maybe you can submit a PR?
Further, it might be nice if vim-sbt did set filetype=sbt.scala. I'd probably like my regular Scala snippets, abbreviations, whatever to work in sbt files if I used vim-sbt. But that's another matter :grin:

I've applied this fix, the extra syntax highlighting from vim-sbt should now work if you have it installed.
Keep an eye on derekwyatt/vim-sbt#2 also, but you should still get the sbt syntax highlighting showing up with or without that change merged once you've updated to the latest vim-scala.


When adding duplicate line_items to a Distribution, it does not combine them

Steps to Reproduce

Sign in as a user
Distributions -> New
Fill out fields like normal
For line items, choose an item type and enter some number
Click "Add Line Item"
Choose the same item type and enter a quantity
Save
View the distribution

The line_items should be combined. They already do this for barcode items. There's an existing combine! method in itemizable that will handle the logic of combining them; it just needs to happen. I'm not sure if this is also happening for any of the other itemizable models (Donation, Transfer, Adjustment, Purchase) -- should check those too.
Desired behavior
It's OK that the line items are duplicated, but if you wanted to make them combine in the UI, that's OK too as long as it's accurate. The main thing is that the line_items get combined before it commits.
Criteria for Acceptance
The behavior should function correctly, as above. Provide proof with a test -- if this behavior is happening across all itemizable models, you can add it to the itemizable shared example.

Thank you @mdworken !!


Bundle Omise-PHP to the project

1. Objective
Bundle a library, Omise-PHP, to the project. Omise-PHP will be used to interface with Omise API.
Related information:
Related issue: -
Related ticket: -
Required pull request: #12
2. Description of change

Add Omise-PHP to the project in the directory, libraries\omise-php
A directory and files of Omise-PHP in the list below are not added to the project.
1 tests\
2 .gitignore
3 circle.yml
4 composer.json
5 phpunit.xml

3. Quality assurance
Environments:

Platform: PrestaShop <IP_ADDRESS>
Omise plugin: Omise-PrestaShop <IP_ADDRESS>
PHP: 5.6.28
Omise-PHP: 2.5.0

Details:
This pull request does not required testing.
4. Impact of the change
-
5. Priority of change
Normal
6. Additional Notes
-

@nimid can you upgrade omise-php library to the latest one? (2.6.0)
Thanks & ok for the rest 👍

@nimid  fyi, going to rebase #12

rebased #12 feature/create-card-token => feature/bundle-omise-php

fyi, rebased with #12

fyi, rebased with develop

@guzzilar https://github.com/omise/omise-prestashop/pull/13#issuecomment-271860607
Done. 99b05488adae98849db7e919ad6da50de32d78a3

👍


[5.7] Don't modify default connection when running Migrations

A pain-point for me with the Migrator process is the fact that I always have to store the default connection, run the migrations and then restore it back, like the following:
        // We need to store the current default connection name in order to
        // restore it back later.
        $defaultConnectionName = config('database.default');

        // When setting a connection in the migrator, Laravel will override the
        // application's default connection with the one provided here.
        $migrator->setConnection($connectionName);

        if (! $migrator->repositoryExists()) {
            $migrator->getRepository()->createRepository();
        }

        $migrationsExecuted = $migrator->run([$migrationPath]);

        // After migrating, we can restore the default connection to it's original
        // value to prevent undesired behavior from components that rely
        // on the default database connection.
        $migrator->setConnection($defaultConnectionName);

        return $migrationsExecuted;

If I don't do this, any code that relies on the default connection will fail because the Migrator switches it.
This pull request changes the strategy to resolve the connection instead of override the default connection, allowing us to keep relying on default connection even if we're running migrations on the fly.

Can you explain more about your situation that requires this so I understand it better? Maybe something with real code examples of your application?

While I was extracting some real world example code into a clean laravel installation, I noticed that this proposed solution does not work. The runMigration method will still try to resolve the default connection. I'm closing this down until I can propose a better solution.

Essentially I'm guessing this is to allow multiple database multi-tenant.
In order to do something similar this what happening under my tenanti package
https://github.com/orchestral/tenanti/commit/33066173740701d54d881cd3775977d669dcf58c


Lint-rule warning you when using AsyncValue.value inside a widget / build method

Is your feature request related to a problem? Please describe.
Not really, just something we have seen happen in production once or twice.
Essentially, you are trying to read a nullable AsyncValue value, with a fallback, but if the AsyncValue is in error state, you unintentionally throw the error e.g. in your build method.
Describe the solution you'd like
A lint rule in which you could specify that using e.g. provider.value?.isEmpty ?? false  is dangerous, and that you should prefer provider.valueOrNull?.isEmpty ?? false to avoid runtime errors.
Describe alternatives you've considered
I guess being more careful when reviewing code. The docs are pretty clear about this difference, but still it seems like a nice lint rule.
Additional context
N/A

Rather than a lint rule, a breaking change is made in 3.0. value essentially becomes valueOrNull

@rrousselGit
We are using
flutter_riverpod: 3.0.0-dev.0
riverpod: 3.0.0-dev.0
riverpod_annotation: 3.0.0-dev.0

So, i suppose you mean it will be part of the official 3.0 release?

The dev branch isn't up-to-date. I don't plan on updating the dev version for now.
But the current implementation of 3.0 already has an AsyncValue.value that doesnt throw.


sirtunnel.py: command not found

I have this error how can I get the path sirtunnel.py on the server?

Hi @joseyapor21, you'll need both sirtunnel.py and Caddy on the server. Easiest way is to log in to the server and do a git clone, then run the install script. SirTunnel is a bit more hands on. You'll need a decent understanding of SSH tunnels and reverse proxies (Caddy in particular). You might check this list for some more user-friendly options:
https://github.com/anderspitman/awesome-tunneling

Thanks for the reply I was able to find the sirtunnel.py on the server and able to make a tunnel,
I have a question there is an API call made by sirtunnel.py where is this request going to and where are those files, I'm new to this Thanks in advance.

This is not an issue is more like user documentation I was able to figure out the sirtunnel.py and the API comes from <IP_ADDRESS>:2019
that comes with CADDY is a way to send CADDY the information of the tunnels and add the routes thanks I just read about Caddy it is very helpful,
Thanks for this great app.

No problem glad you figured it out!


Unexpected token

I have a problem with SVG files, when i run npm run sitemap  is generating the following error:

@focampo92 maybe it is same problem? https://github.com/kuflash/react-router-sitemap/issues/80


Error when request contains function without parameters

When calling chat completions endpoint with "tools" parameter which contains a function without parameters the following error is thrown:
Invalid schema for function 'myFunctionName': [] is not of type 'object'
Example request:
$request = [
    "model" => "gpt-4",
    "messages" => [
        [
            "role" => "system",
            "content" => "You are a helpful assistant",
        ],
        [
            "role" => "user",
            "content" => "hello",
        ],
    ],
    "max_tokens" => 300,
    "tools" => [
        [
            "type" => "function",
            "function" => [
                "name" => "myFunctionName",
                "description" => "My dummy function",
                "parameters" => [
                    "type" => "object",
                    "properties" => [], // Error is here
                ],
            ],
        ],
    ],
];

$client = OpenAI::client($yourApiKey);
$client->chat()->create($request);

This happens because empty array $request['tools'][0]['function']['parameters'] is json encoded into [] instead of {} as required by OpenAI API:
https://platform.openai.com/docs/api-reference/chat/create
To describe a function that accepts no parameters, provide the value {"type": "object", "properties": {}}.

@vadimpronin Thank you for raising the issue. You should be able work around this by using "properties" => (object) [],.
But I haven't tested it. Would love to hear if this solves your problem.
The other option would be to use JSON_FORCE_OBJECT when we do json_encode in the client. But I am currently not sure if this would break other stuff.

"properties" => (object) [] did help, thank you!


Shibboleth (Ping Federator) - "Internal Server Error" presented when user is denied access.

Rancher server version - 1.6 build from master
Steps to reproduce the problem:
Enable Shibboleth (Ping Federator)  auth and set access control to ""Allow members of Environment,plus Authorized Users and Organization".
Log in as a user (with valid password) who does not have access.
User is presented with "Internal Server Error"  message:

Server logs:
time="2018-04-11T20:03:04Z" level=error msg="HandleSAMLPost: Error doing POST /v1/token: Bad response statusCode [403]. Status [403 Forbidden]. Body: [baseType=error, message=Your account does not have access, code=AuthError] from [http:/<ip>/v1/token], data: map[givenName:[Test] memberOf:[CN=testgroup1,CN=Users,DC=tad,DC=rancher,DC=io] sAMAccountName:[testuser3] displayName:[Test User3]]"
time="2018-04-11T20:03:04Z" level=error msg="GetSamlAuthToken failed to Get token from cattle with error Bad response statusCode [403]. Status [403 Forbidden]. Body: [baseType=error, message=Your account does not have access, code=AuthError] from [http://<ip>/v1/token]"

Thanks for your report!
With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.
If you think we should keep this issue open, please let me know.


[Bug]: Pagination is not working properly

What happened?
I found a BUG 🐞
If you go to the last page still the next button is showing.
If you go to the first page still the previous button is showing
i would like to work on this for gssoc 2023
Add screenshots
Add screenshots
What browsers are you seeing the problem on?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

assigned to you @suzy-g38

Completed. Thanks for your contributions 🎉 ❤


Elicit the Requirements

Elicit the requirements from the customer. Ask proper questions and write down the elicited requirements.

Requirements are elicited and added under the wiki page for New Requirements.


require-dev.craftcms/ecs : NULL value found, but a string is required

Description
When running anything with Composer e.g. composer require x/y I get an error craftcms/ecs and craftcms/phpstan mainly because I opted out of these when using the generator. I resolved this by just removing it from require-dev in composer.json but obviously the generator doesn't need to add this in.
Steps to reproduce

Run generator to make a plugin
Opt out of ecs and phpstan
Try installing any composer package

Additional info

Craft version: <IP_ADDRESS>
PHP version: 8.1.12
Database driver & version: MySQL 5.7
Plugins & versions: n/a

Thanks for reporting that! Just released Generator 1.2.0 which includes a fix.


Issue 5383: Added Content-Encoding header check when content encoding is disabled.

Just simple TODO implementation.

This seems to be last TODO in Http1Connection so I linked issue #5383 here to be closed with the merge.

Rebased on top of the main branch.


Add help output for the module as PSReadLine.txt artifact

I published platyPS v 0.3.0 which should fix Update-Help interactive problem https://ci.appveyor.com/project/lzybkr/psreadline/build/1.0.14

"Get-Help calling Update-Help and CI is non-interactive" problem is fixed in platyPS 0.3.1


Prefer mavenCentral

Description
Fork of https://github.com/googleads/googleads-mobile-flutter/pull/488, which was automatically closed when the main branch of the repo was renamed.
Adds mavenCentral() to android build.gradle files, for https://blog.gradle.org/jcenter-shutdown.
Related Issues
*Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the [Flutter Style Guide].
[x] I signed the [CLA].
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

I removed jcenter() altogether, since according to https://blog.gradle.org/jcenter-shutdown support will be removed in future versions of gradle.


Not scrobbling tracks whose titles contain umlauts

Hi and thanks for your awesome work!
I'd like to note that the script won't scrobble tracks whose titles include German umlauts (ä, ö, ü).
IINA's/mpv's logs don't contain any info whatsoever about why this is happening.
Manually running the script while a track is playing also won't output anything; the script will exit with code 0, but nothing scrobbled.
The mpv socket returns valid data, so that's not the cause.
I might have a look into this tomorrow or the next couple of days but I don't have much experience with Perl.
Greets from Germany :)

Should be fixed in the latest commit, please let me know if it's still broken :)


kv,restore: log which value caused conversion failure

What problem does this PR solve?

When there is invalid data, the current log is not able to reveal what is the cause.
When a column is missing, Lightning will fill in default values for these columns, but this behavior may not be obvious.

What is changed and how it works?

When KV encode failed, log the file path, row content, column index, name and type in additional to the error.
When a column is missing, log a warning about the missing column.

Check List
Tests

Integration test

Side effects
Related changes

/run-all-tests

/run-all-tests tidb=pr/9880

/run-all-tests

Rest LGTM

LGTM

/run-all-tests


stage0: added support for fetching plugins, refactored docker/http(s)

Adds support for having images fetched via a plugin. Plugins take the
form of a binary on the user's path named "rkt-fetcher-%s", with the %s
taking the place of the schema, so for example fetching
docker://alpine is redirected to the rkt-fetcher-docker binary.
When the plugin is started it has a JSON configuration written to it on
stdin, and its stdout and stderr are forwarded on to the user. The
configuration contains paths to write the ACI and ASC files to, which
rkt will then verify (unless the insecure image option is specified).
This isn't done yet, just putting this up for review to see what people think before I work on it further.
Things done:

Wrote the plugin fetcher in rkt
Moved the logic for fetching docker images into a plugin

Things left to do:

Pull the http(s) logic out into another plugin
Write docs
Tweak autotools to build the plugins

Questions:

Is putting the plugins on the path ok? Should they instead live in a known directory like stage1s can? Maybe support both?
Does the config look versatile enough? Should there be more things in its schema?

To try it out:

go build -o rkt-fetcher-docker rkt/image/fetchers/remote-aci/main.go
put rkt-fetcher-docker on your path
build this version of rkt
fetch something

Related issue: https://github.com/coreos/rkt/issues/1831

cc @sgotti, @runcom

Does the config look versatile enough? Should there be more things in its schema?

As an example, there's the need to both send and receive http caching information to an http plugin (like ETag and Cache controls saved in the store remote data).
Since in this way every plugin may have different input/outputs I'm not sure which is the best way to make generic input config and outputs or every plugin should have different inputs and outputs.

@sgotti The hope is that this change would enable 3rd parties to write plugins without our intervention, and tweaking the config for each plugin means you need rkt support added in for each additional plugin. Maybe the answer here is just in the input include all the possible information the plugin could want, and each one will probably only need a subset of it?
Also as far as an output config, I could only pass the plugin's stderr through to the user, and have plugins write a report in json to stdout that rkt can parse, so as to pass rkt Etag and Cache controls and such.

Just pushed a change that moves the https fetching logic into a plugin. Also changed the plugins, such that they're expected to write a result json to stdout when they're finished. This is used to pass things like cache data back to rkt.

Status update: haven't forgotten about this. Currently working through the broken tests and figuring out what functionality I'm still missing.

bump

I'm currently in the middle of refactoring hell, getting the https plugin to have all the functionality of the previous code. As I'm not working today/tomorrow, I hope to have this finished sometime next week.

On Jul 14, 2016, at 06:47, Jonathan Boulle<EMAIL_ADDRESS>wrote:
bump
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@dgonyeo
before commenting on the code I have a broader doubt.
In relation to #2925 looks like these are plugins for fetching given an input scheme. But the input scheme used with rkt (http://, docker://) isn't a transport scheme but covers the distribution concept. To be clear http:// is not just the transport but covers returning an aci and optionally a provided signature url, the docker:// covers calling docker2aci the return an aci using as a distribution a docker registry
Did I get it right?
I originally thought (reading the linked issues) that the idea was to provide plugins for a transport, also for being able to lower some privileges.
So, for example for http:// will just be a plugin to fetch a file from http. docker:// instead doesn't make great sense being a plugin since the transport is done inside docker2aci and I can't see a strong need for different implementations.
Additionally there're other parts that fetch to a remote for example the appc pubkeys are fetched in rkt/pubkey/pubkey.go.
Perhaps I missed some discussions around this. @lucab?

@sgotti I had been implementing this with the assumption that distribution and image format would remain bundled like they are in rkt today, but after reading over https://github.com/coreos/rkt/issues/2925 I think this is just splitting out the distribution mechanism, and we could evaluate making the image format logic more pluggable after this.
This implementation hands a plugin a string, and the plugin is expected to perform the distribution logic to convert that string into a local ACI (and possible ASC), after which the stage0 binary imports this into the store. In the case of the docker:// scheme, this means that the distribution also involves the image conversion. I intend for this PR to have the stage0 binary do AppC discovery and hand the resulting URI off to a plugin after doing the template substitution, and the stage0 itself would fetch the public key over https (I didn't want to have to worry about introducing any security concerns there by offloading that work to plugins).
The objective of all this is to allow users to write their own plugins without needing to modify rkt. If a user wants to fetch images using some specialized s3 protocol, they could create a fetching plugin and it would just work, instead of needing to make a feature request from us.
I could see it possibly making more sense to only allow fetching ACIs via plugins, and keeping the docker:// schema logic in the stage0, as it involving image conversion makes it a little different than the other schemas, but at this point I think I like the separation of also pulling that out into a plugin.

intend for this PR to have the stage0 binary do AppC discovery and hand the resulting URI off to a plugin after doing the template substitution, and the stage0 itself would fetch the public key over https (I didn't want to have to worry about introducing any security concerns there by offloading that work to plugins).

Ok, Just to clarify my concepts (but I may be wrong :smile:) I think of distribution as the whole process, starting from an input string, to fetch the required image. In this case since the discovery will be done by the stage0 the plugin is just doing the transport logic (http, s3, bittorrent, ipfs). So I'm going to call them transport plugin.

I could see it possibly making more sense to only allow fetching ACIs via plugins, and keeping the docker:// schema logic in the stage0, as it involving image conversion makes it a little different than the other schemas, but at this point I think I like the separation of also pulling that out into a plugin.

Seems Good. As an example, when rkt will support native OCI images the 'docker://' distribution should check the docker registry/manifest version and choose to use docker2aci for v1 and directly handle oci for v2, oci images fetched from a docker registry (the docker:// will mean docker registry distribution). Additionally when natively fetching the OCI blobs they aren't just one file but multiple blobs with different mediaType so I'm not sure how a full distribution plugin could handle this, instead this logic could use an http transport plugin.

Much closer now. I believe all the relevant tests should pass, but I have yet to tweak autotools to build the plugins.
Also after talking to @sgotti I think I'd like to hold off on merging this until the new store work gets further along, as it's not clear to me how that will impact this.

Still, if anyone has further feedback or would be willing to give this another review pass, that would be awesome.

From an out-of-band update: this should be receiving more attention and an update around the end of this week.

I've been too busy to give this much attention, and am busy this week with LinuxCon. I was going to focus on this next week.
Unless you mean someone else got impatient and is going to pick this up for me.

On Aug 22, 2016, at 08:14, Jonathan Boulle<EMAIL_ADDRESS>wrote:
From an out-of-band update: this should be receiving more attention and an update around the end of this week.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Nope, just capturing that you'll be back to it soon ;-)
On 22 August 2016 at 16:47, Derek Gonyeo<EMAIL_ADDRESS>wrote:

I've been too busy to give this much attention, and am busy this week with
LinuxCon. I was going to focus on this next week.
Unless you mean someone else got impatient and is going to pick this up
for me.

On Aug 22, 2016, at 08:14, Jonathan Boulle<EMAIL_ADDRESS>wrote:
From an out-of-band update: this should be receiving more attention and
an update around the end of this week.
―
You are receiving this because you were mentioned.
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/coreos/rkt/pull/2830#issuecomment-241436557, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN8LusbefONB0IqkN749FfRf-o8n0ks5qibZkgaJpZM4I8SJs
.

This is stale and has a ton of conflicts. Closing.


Add option to allow fuzzy translations

I'd like to allow fuzzy translations in my application. It should be an easy change.

Wow! Thanks, seems like a nice to have feature!

this option is available in<EMAIL_ADDRESS>:tada:

Thank you!

Could you create a matching ttag-cli release?


CHAOS-4002 Resilience probes create, use, edit

Resilience probe introduction, usage
Preview

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c46578e27f70340f9d0695--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d31a053a6c78d72bc32df6--harness-developer.netlify.app

https://github.com/harness/developer-hub/pull/5784 new PR since the structure of docs was changed


Add Compatible Node Version

Summary of Changes
Add compatible node version in the documentation section
Related Issues
Please reference here any issue #'s that are relevant to this PR, or simply enter "N/A" if this PR does not relate to any existing issues.
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

@realabbas Needs to have DCO as per the Linux Foundation rules. You can probably rebase and add it or maybe --amend

Instructions described in the check (https://github.com/hyperledger/aries-mobile-agent-react-native/pull/436/checks?check_run_id=8302558742):
git rebase HEAD~1 --signoff

Instructions described in the check (https://github.com/hyperledger/aries-mobile-agent-react-native/pull/436/checks?check_run_id=8302558742): git rebase HEAD~1 --signoff

Yeah okay, thanks. I ran the commands and now its signed off.


EntityDeathEvent Issue ( Citizens B1465 )

Hello, as I dont have a clue where to post issues for Citizens I took my chances and placed it here. ( I hope I did correct by this action )
Anyway, right after I start up the server this error takes place ( Without even logging in )
Error:
http://one.denizenscript.com/haste/38973
Citizens Build: 1465
Spigot Build: (MC: 1.11.2) (Implementing API version 1.11.2-R0.1-SNAPSHOT)

Did you potentially delete/remove an entity in the death event?

The issue was solved by adding a delay on the - remove on the death event. Thanks for the info!


Cancel all running tasks with ctrl+c

Frequently ctrl+c does not work to cancel the running tasks. This seems
to be because the signal handler is bound to a specific instance of
evaluate task but there may be multiple instances of evaluate task
running at any given time. Shutting down just one of the running engines
does not ensure that task evaluation stops. To work around this, we can
globally store all of the completion services in a weak hash map and
cancel all of them whenever a signal is received. Closing the service,
which happens at the end of task evaluation will remove the service from
the map so hopefully this shouldn't introduce a memory leak.

I was motivated by running mimaReportBinaryIssues in the sbt project, immediately cancelling it and then having to wait 45 seconds for mima to run anyway. After this change, cancellation worked as expected.


New async-safe interface

This PR changes the interface to allow usages where TLS is read from asynchronous callbacks. This fixes #2.
Since this is already an API change, I take the opportunity to follow naming conventions more closely.
Before I contribute some code, we should consider the question of licensing. Given that this is in the MIT license, there is the possibility of switching to a license which is more protective of contributions, e.g. LGPL. My preference goes for LGPL + linking exception. Which do you prefer? This is your repository, it's as you prefer.

Thank you for the PR, it looks good! The new API is better indeed.
I'd rather keep this MIT, as it's a license that facilitates use by the maximum number of people, if you don't mind.

I'm happy to license this small contribution under MIT. I just wanted to make sure this was a deliberate choice of license when you took over the code.

Ah yes, indeed. Makes sense. Thank you for the contribution :)


Support migration of the FireFly contract from one location to another

In a chain with #821.
Depends on https://github.com/hyperledger/firefly-common/pull/8 being merged and integrated here.
Summary of changes:

Support a list of contract addresses in the blockchain config.
New config example:

blockchain:
- name: blockchain0
  type: ethereum
  ethereum:
    ethconnect:
      url: http://ethconnect_0:8080
      topic: "0"
    fireflyContract:
    - address: 0xb347e9de7d9f312c24c375fff7632e189bf1dd43
      fromBlock: 0
    - address: 0x3c1bef20a7858f5c2f78bda60796758d7cafff27

New contractIndex field added to namespaces.
Currently the active contract is recorded globally against the "ff_system" namespace, but as part of https://github.com/hyperledger/firefly-fir/pull/12, this would be per-namespace.

New /network/migrate API and SubmitOperatorAction blockchain plugin call (naming up for discussion).
Sends a specially formatted "BatchPin" transaction to signal that all members should migrate to a specific version of the contract.

Codecov Report

Merging #820 (e999cad) into main (3cf5f35) will decrease coverage by 0.31%.
The diff coverage is 58.27%.

@@             Coverage Diff             @@
##              main     #820      +/-   ##
===========================================
- Coverage   100.00%   99.68%   -0.32%
===========================================
  Files          304      306       +2
  Lines        18960    19044      +84
===========================================
+ Hits         18960    18984      +24
- Misses           0       58      +58
- Partials         0        2       +2

Impacted Files
Coverage Δ

internal/apiserver/routes.go
100.00% <ø> (ø)

internal/events/event_manager.go
100.00% <ø> (ø)

internal/events/operator_action.go
0.00% <0.00%> (ø)

internal/orchestrator/bound_callbacks.go
94.73% <0.00%> (-5.27%)
:arrow_down:

pkg/core/namespace.go
100.00% <ø> (ø)

internal/orchestrator/orchestrator.go
98.39% <16.66%> (-1.61%)
:arrow_down:

internal/blockchain/fabric/fabric.go
97.16% <23.07%> (-2.84%)
:arrow_down:

internal/apiserver/route_post_network_migrate.go
33.33% <33.33%> (ø)

internal/blockchain/ethereum/ethereum.go
97.08% <76.62%> (-2.92%)
:arrow_down:

internal/blockchain/ethereum/config.go
100.00% <100.00%> (ø)

... and 3 more

Continue to review full report at Codecov.

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

I think this will now need to slot in after #826

Now rebased on mainline after the merge of #826

each namespace will have its own blockchain plugin and therefore its own contract index.

I think I'm right interpreting this as:

Each unique remote namespace will have it's own blockchain plugin. Noting that there might be multiple local namespaces on the node that have separate root identities registered in that business network, and they can choose to share a single blockchain plugin, or each have a separate blockchain plugin.

k - feel like we need to net that out in FIR-12. Some of it might be terminology, but if you really have to define an individual plugin for each namespace and those configurations can't be re-used... it feels odd that you don't just define them directly in the namespace.

if you really have to define an individual plugin for each namespace

@peterbroadhurst yea I think it's mostly terminology here. From a configuration perspective, you can reuse a plugin configuration in many namespaces. From an internal instantiation perspective, there will be a separate plugin instance+event loop created for every one of those namespaces.


refactor: move __get_parser to helpers

https://github.com/tokitou-san/MangaAPI/blob/e09ad4d36c7001a95c9ece318cb5d3c23bc6fa97/app/api/scrapers/base_manga.py#L13-L15

Hi, again) Do u need to new class, for example, HTMLHelper  in new file helpers/html.py or move to helpers/string.py?

And I can use moved __get_parser() for most_viewed.py, topten.py, popular.py because it use __get_parser().
I think change to:
class HTMLHelper:
   @staticmethod
   def __get_parser(url: str) -> HTMLParser:
       res = requests.get(url)
       return HTMLParser(res.content)

Hi @issamansur :)

HTMLHelper in new file helpers/html.py

Yes, create a new file html.py sounds good -> HTMLHelper class ( remove __ naming convection )
Yup sounds good
class HTMLHelper:
   @staticmethod
   def get_parser(url: str) -> HTMLParser:
       res = requests.get(url)
       return HTMLParser(res.content)


src :  set cell height to “auto” when cell Height is -1

allow to set GridList cellHeight as 'auto' with set in as -1

What is this fixing? Wouldn't it be better just to accept 'auto' as a cell height?

My problem was that I can't use dynamic height of GridTile. Because of it have "div" tag between GridList and GridTile that set div height as a number (cellHeight * childRows + padding) and no way to adjust that value to 'auto'  without change this line of code.


Remove default assignment hint

Description
We want to get rid of DEFAULT scenario in Compass. Because of that we also want to remove the default assignment hint in the Compass console.
Changes proposed in this pull request:

Remove default assignment hint in Compass console

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


docs: remove mention of bug on sort_by: creation

It's been closed.

Thanks a lot! I'll merge it once Yazi 0.3 is released (should be this week)

You're welcome!


mv interface.py parsuite.py

mv interface.py parsuite.py

dis old
also, things are being updated to support installation via pip: pip3 install parsuite
you'll just have a parsuite subcommand now :)


Fatal error: "Expected a new writer but got the same one back!!!" IndexingFilter line 220

For now I'm changing the fatal error to a warning as this condition might be ok and not fatal after all.
I need to know what happened just before the error so please turn on debug logging for the IndexShardWriterImpl and IndexShardWriterCacheImpl and keep a look out for the warning.
  <logger name="stroom.index.server.IndexShardWriterImpl">
    <level value="debug"/>
  </logger>
  <logger name="stroom.index.server.IndexShardWriterCacheImpl">
    <level value="debug"/>
  </logger>

Still happening in beta 28


No ability to set custom headers for webseed client

There is a case when the need arises to add headers for webseedClient (code link). However there is not method/config setup to set it. Can you add method for example SetWebseedHeaders or config param to implement additional headers for webseedClient?

Yes, I can do that. What's the use case? Do you need to set a header for every webseed download or for a specific domain? Why is this needed?

There is need to store stats on weeb seeds side. I use this functionality in libtorret for example. For me it's enough to set user-agent header for session.

Sorry, I couldn't understand how this feature is going to be used. Can you give more detail please?
Is this header feature required to use a specific tracker or are you building something custom yourself?


update CSS and JavaScript with website

The plugin needs to update along with the new code for the website

fixed via e40c5d082e4cef252b97afb0e2276da83e0d1106


Integrate Circle CI and Codecov for testing

Circle CI and Codecov can help to monitor and test the project. Therefore please integrate them.

Claiming It

Organization admin must opt-in to using third party orbs in Organization Security settings right?


Use Pytorch 2.1 for CUDA 11.8+ and ROCm builds

For most systems, the wheels built on Pytorch 2.0.1 work fine with 2.1.
However, for unknown reasons, some systems seem to not work at all unless the wheel is built with Pytorch 2.1.
This PR changes the workflows to use the official Pytorch 2.1 release with CUDA 11.8+ and ROCm.
It also adds some basic error correction as I noticed that Mamba will not always report an error and stop the workflow if CUDA Toolkit fails to install.
I also commented out the PyPI upload functionality for non-sdist builds for convenience as it can't be used at the moment.
Should now only try to upload the JIT-compile wheel and the sdist itself.
I added a comment on line 179 detailing how to only upload the wheel and can add that change to this PR if you want.
Additionally, I made the following changes to the Powershell code that reads the package version number in the release workflows:

Made the code more readable
Now uses the exllamav2/version.py file for detection
Now uses the release tag format of: v{version_number}

To clarify, it's purpose is to determine the package version number for uploading the wheels to a release using that version number.
It prevents automatic uploading to a release and will notify you in the event that the version number is not detected for some reason.

Thanks. I'm going to give these a try in a minute. :+1::+1:

Saw the error in your recent build.
From what I can tell, cuda_fp8.h is only present in CUDA 11.8.

Yep, I disabled it for 11.7 for now.


N+1

In this milestone, my coding partner and I;

Detected the n + 1 issue using log
Included (:author) to post and comment to improve performance and solve the n+1 issue.
Installed Capybara
Wrote tests in spec/features director. To run these tests, please run "rails spec:features"

@Alfredbis29 Thank you for reviewing our project. I will work on it asap

@AnselemOdims Thank you for reviewing our project


invites: Update error message when max limit for the day is reached.

This PR updates the error message returned when the maximum
invite limit for the day is reached to mention that the user can
use multi-use invite link. We show this part only on the frontend
linking to the help page because we cannot use links with proper
format in backend.

GIFs or screenshots:

@timabbott I am not sure whether we can send the error message with link formatting from the backend. I tried sending it using <a> tag, but since it is sent as string it is not rendered correctly in the frontend. That's why I modified the error message slightly to have separate sentence for mentioning that users can use multi-use link and use it only in frontend.
Any suggestions.

@timabbott updated the PR as suggested above in comments to not show email and instead linked to https://zulip.com/help/contact-support.

Merged, thanks @sahil839!
I think we could likely do a lot better by having reusable invitation links be less hidden in the /help/ page about invitations; @alya FYI as something you might want to put on your TODO list.


chore(docker): adapt to run MongoDB v5+ in docker-compose

I figured out how to run v5 and v6 for our Replica Set setup, which I often use for reproductions and reflected that in the config.

I removed the authentication to simplify things along the way.
and switched to unless-stopped everywhere, it's a better default

Errors from

CI / Tests / Client (func/win+mac) (windows-latest, 16, library, 2/2) (pull_request) Failing after 8m
CI / Tests / All pkgs (win+mac) (windows-latest, 16, library) (pull_request) Failing after 12m
are unrelated and flaky


Copy button's borders are cut off

When the paring string is displayed during the connect Hashpack wallet user journey, clicking the copy button causes the button's borders to become slightly cut off.

I think I'm stuck on this one. I've been trying to chip away at this issue but am most likely just spinning my wheels at this point now. Adding my analysis on the issue and what I've tried so far:
Analysis
It appears that the button's box-shadow styling is being cutoff by the div's container/border. If we look at the button's parent element, we can see that the description div (line #205 from webapp/src/components/MainHeader.vue) sets the overflow to be hidden. This is why the box-shadow is being hidden on the div's borders.
Things I've Tried

Setting the overflow to visible on the copy button element directly. After making these changes, the button's shadow was still being cutoff.
Removing the copy button from the description div (like the other buttons are) and resizing. This fixed the shadow issue, but introduced additional issues where the copy button would display on unexpected screens.
Removing the overflow properties from the description div and moving them to each element individually. This fixed the shadow issue, but introduced additional issues where the paragraph text and pairing string would overflow horizontally.

@bugbytesinc - Do you have any recommendations on what to try next?


Announce first release

Blog post
linkedin
slack

https://trino.io/blog/2023/09/28/trino-gateway
Also done on slack and linkedin


Oncofuse

I have an error running bcbio 0.9.5 for RNA-Seq, when including Oncofuse in the pipeline. The error is
_Could not find java jar Oncofuse in /apps/bcbio-nextgen/0.9.5/rhel6-x64/share/java/oncofuse _
It seems the Oncofuse file is in /apps/bcbio-nextgen/0.9.5/rhel6-x64/bin/oncofuse and not in java share.
Please can you investigate?
Thanks.

Hi Sally,
Thanks for posting about the issue, we don't do too much fusion calling so this one slipped by. We swapped over to using wrappers for JAR files so oncofuse gets called with oncofuse and not java -jar path-to-oncofuse-jar, but we forgot to swap this call over.
I swapped it over and ran our tests and it seems to be fixed.


Fix the tcp_connection metrics for the missing port and tcp_state labels

Test evidence:

This introduced some stray tabs, which were fixed in #102.


Multi line comment not working.

Since the decorator gets one text node at a time, multi-line comments with /* */ are not color coded as comments. Not sure how this can be fixed. Maybe marks should be applied as transform() onChange instead of plugin decorator. Any thoughts ?

This problem does not exists if your code nodes contain a single text node, with newlines character inside.
However, that generally leads to poor performance when writing inside large code chunks. That's why in slate-edit-code we took the approach to split code in multiple line nodes. The problem with that approach is that Prism is not fed the whole text.
Maybe slate-prism could ask which code block each code line belongs to. The plugin would manage a dictionnary of code blocks, code lines, and their texts, so that when it has to decorate a specific line, it has all the necessary context.
I don't know what would yield the use of marks. Maybe @SamyPesse had thought about it. I see one big downside though, that it affects the document data. slate-prism should ideally has just  rendering implications.

@Soreine I think slate-prism could take an optional argument like blockPerLine: true, and then the match function of the decorator rule could match the parent, and pass the block.text of the parent to Prism. But then apply the tokens to the text.

Fixed by #5


PUB-1239 Create DB and update charts

JIRA link (if applicable)
PUB-1239
Change description
Add Terraform for Database
Add Terraform to put secrets into Key Vault
Update Charts Vaules.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x ] No

changed


missing default retry policy for local activity

Expected Behavior
LocalActivity should be retried even when no retry policy is specified.
Actual Behavior
LocalActivity is not retried if no retry policy is specified. Or if retry policy is specified with only MaxAttempt=3 and all other fields left as unspecified.
additional
Need to add unit test AND integration test to verify both remote activity and local activity is retried when no retry policy is specified. Also, when retry policy is specified with only MaxAttempt = 3 and all other fields unspecified.

If no retry options are set, they will be nil, and this code is what will preventing LA retries.
In this case LA will not be retried upon failure within the same workflow task but instead will be relying on workflow task retries. Given that we retry workflow tasks until workflow itself times out this provides a natural catch all here.
Let's discuss if we want to change this behavior.

Why would the workflow task fail? The LA will return error without retry and workflow code will move on.


Content Search

It would be helpful for you to be able to find certain Stroom content, e.g. XSLT, with a free text search as it is often quite hard to remember which content contained a useful bit of XSLT, splitter etc. (gh-1630, gh-1631)

This feature is now present but is slow to search. It would benefit from a search index to make searching much faster.


Add Python 3.10 to CI

The latest release of PyTables does not work with python 3.10 so it has to be pip installed from its github url in order to work. When a new release of pytables is available this should be changed

Codecov Report

Merging #2 (fcd36c5) into main (f3d49d3) will decrease coverage by 100.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##              main      #2        +/-   ##
============================================
- Coverage   100.00%   0.00%   -100.00%
============================================
  Files           10      10
  Lines          590     590
============================================
- Hits           590       0       -590
- Misses           0     590       +590

Impacted Files
Coverage Δ

simweights/utils.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/fluxes.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/pdgcode.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/spatial.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/powerlaw.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/weighter.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/nugen_weighter.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/corsika_weighter.py
0.00% <0.00%> (-100.00%)
:arrow_down:

simweights/generation_surface.py
0.00% <0.00%> (-100.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Create FAQ page

#403  👈
main

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

Join @jvmi7 and the rest of your teammates on  Graphite


Patch for /trunk/BurningGround/src/hooks/game_hooks.cpp

바이킹 변신부분

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 21 Dec 2013 at 2:23
Attachments:

game_hooks.cpp.patch

Translation(?):

Part of Viking transformation

I'm sure Viking refers to some SC unit.  Or the translation is just completely terrible.

The Viking is an SC2 Terran unit that can transform from a Ground-to-Ground walker unit to a Air-to-Air plane unit.

Thanks for the clarification.  It looks like this patch adds in that type of functionality to an example project for one of the hero units.
Hard to tell from just looking at the code though since there are no comments.


Make it easy to see what has changed when clinical data is updated

Feature request from @jburos

We currently use https://github.com/tavinathanson/hyper's "Peek at Text Changes" to see what numbers have changed in a paper after any update. Would be great to have a related feature within/working with cohorts itself.


Add bevy

Adds link to the Bevy Engine official discord server.

Oops, didn't realize they were sorted! Fixed now.
Also, I've seen that some have a <br /> after them, so I've added one too. Should I remove it?


Feat / Team management - Create "My teams" view for customer adding element in navigation

🗒NOTES
🏁PREREQUISITES

[x] DOR
[ ] DOD

📜CONTEXT (User Story)
As a customer
I want to manage the teams linked to my company
In order to be able to change their captains, see their activity, etc...
🪜STEPS TO FOLLOW

[x] Step 1: Add new file : TeamListView.vue in "yaki_admin/src/ui/views"
[x] Step 2: Add route path team_list in "yaki_admin/src/router/router.ts" in children of dashboard path
[x] Step 3: Add side-bar-menu-link component in "yaki_admin/src/ui/views/SideBarContent.vue" from line 58 if we have userCredentials.customer true
[x] Step 4: Add translation for the page name
[x] Step 5: Update redirection method in line 29 of "yaki_admin/src/ui/views/SideBarContent.vue" with the new route path

✅ACCEPTANCE CRITERIA

✅ Customer can access to a new view named "My Teams" by the side bar
✅ Captain can't access to a new view named "My Teams" by the side bar

📛BLOCKERS
🔍AFFECTED COMPONENT(S) (Scope)
yaki_admin/src/ui/views
yaki_admin/src/router/router.ts
yaki_admin/src/ui/views/SideBarContent.vue
⛓LINK TO OTHER ISSUES
🪟SCREEN SHOTS & MOCKUPS
📋TEST STATUSES
What are the test cases required to validate this issue?

[ ] Test case 1: Customer can access to "My Teams" view
[ ] Test case 2: Captain can't access to "My Teams" view

What kind of tests has been put in place to ensure the issue is resolved?

[ ] Manual Tests
[ ] Unit Tests
[ ] Integration Tests
[ ] Functional Tests
[x] End To End Tests
[ ] Other (elaborate)

Customer access to "Teams" view


Add code for agglomerative clustering

New clustering algorithm for agglomerative clustering in new files.
Put under option - default off
Past comments from below PR resolved:
https://github.com/The-OpenROAD-Project-private/OpenROAD/pull/409

@shrey-bansal please check the new comments.

@mathursanjiv is this still live?  Its been 20 days with no update.

@mathursanjiv is this still live? Its been 20 days with no update.

Well the developer is now not working on OpenROAD. I'll try to fix code for feedback over next few days.


Update quick-start.md

It's actually a reducer but not reducers field at -> Add Slice Reducers to the Store section
Deleted nonsense sentence at -> Full Counter App Example section

:memo: Documentation Fix

Thanks, but that was the correct parameter. But the other dangling sentence should go.

@timdorr I know the sentence is confusing but this is my understanding of the concept and why I think the reducer should be used as a key value. When we are using createSlice function it accepts an object as its argument which indeed should have a field/key reducers however in case of using configureStore function its object argument must have reducer property. Honestly I don't like the paragraph since it's sloppy I would write it like ... idk something like this: By defining a field (counter) inside of a reducer property, we tell the store to use a value of the field (which is a slice reducer function) to handle all updates to that state (counter).  Well I bet you can enhance it further .  BTW this is a screenshot of redux and redux toolkit docs reducers vs reducer:

Oh, my bad. I was thinking this was about createSlice, not configureStore. I'll fix that up now.


Idea: align host app with gopass jsonapi, make extension support both host apps

Hey @martinhoefling, I've seen you implemented native messaging support for gopass, as well as your work on gopassbridge. First of all - nice job!
This got me thinking: instead of maintaining two separate projects that essentially do the same thing, how difficult would it be possible to join forces?
I noticed that while the browser extension part in this project is being changed and improved often, the host app changes much more rarely.
I didn't dig much into the native messaging part of gopass yet, but I imagine it works pretty much similar to browserpass, communicating JSON back and forth, requesting domain and returning credentials back.
We could maybe make the API of the browserpass host app compatible with gopass API (basically align JSON structure, I think), and thus make the browser extension work with any host app, browserpass or gopass.
I think more and more people will be switching to gopass over time, having a feature rich browser extension that supports both gopass and older pass via browserpass host app would be very beneficial.
People who use gopass would not require the backend part of this project, they would only need the browser extensions. People who continue using pass would need to install both native host app as well as a browser extension.
I'd even want to split the project into two, one hosting a browser extension and another hosting the native host app.
What are your thoughts? What would be the challenges, difficulties? Is it even feasible?
Everyone else is of course welcome to add your input!

I don't mind either way, so long as support for pass doesn't go away. Adding gopass support does seem like something that would be useful, and unification of the API makes sense.


Fixes wrong file extension

Not sure you did this on purpose or if it was a mistake, but I fixed an example file extension from .swif to .swift

@vittoriom nice catch :+1:


Add block for MIDI

Hello,
just a suggestion, why not add the possibility of adding midi blocks in the music category?
I realized a project based on arduino connected to an ipad to play music. It would be nice, with my students, to realize the project with a micro: bit.
It seems quite simple, in python, to produce notes in midi format.
thank you.
Regards,
Stéphane

See https://github.com/microsoft/pxt-midi


Add ERA-5 database to server as proxy-observed weather data

We need to add some reference observation data for hydrological modelling (calibration, simulation, eventually forecasting). As of now there is no data source. ERA-5 is a reanalysis product that covers 1979-2018 globally at a ~31km resolution. We can distribute it freely conditionally on mentioning the source:

Please acknowledge the use of ERA5 as stated in the Copernicus C3S/CAMS License agreement:

"5.1.2 Where the Licensee communicates or distributes Copernicus Products to the public, the Licensee shall inform the recipients of the source by using the following or any similar notice:

'Generated using Copernicus Climate Change Service Information [Year]'.

5.1.3 Where the Licensee makes or contributes to a publication or distribution containing adapted or modified Copernicus Products, the Licensee shall provide the following or any similar notice:

'Contains modified Copernicus Climate Change Service Information [Year]';

5.1.3 Any such publication or distribution covered by clauses 5.1.1 and 5.1.2 shall state that neither the European Commission nor ECMWF is responsible for any use that may be made of the Copernicus Information or Data it contains."

Format is NetCDF and is an hourly product. The hourly properties will require converting from GMT to local time for averaging over a given catchment.

See https://github.com/Ouranosinc/pavics-sdi/issues/144

I've collected a fair amoint of data from ERA5 at Ouranos. The extracts using the CDSAPI tool don't follow CF-Conventions but I have some treatment scripts that can help in getting them closer to it. This is worth planning out in greater detail.

@richardarsenault Could you include here what you need in terms of variables, frequency, spatial coverage, etc.
@Zeitsperre Are the original files themselves cf-compliant ? Or is the extraction process to blame for removing metadata ?

Precip, Tmax and Tmin, ideally daily time step, coverage all of North America. Longest possible time series also (i.e. 1979-most recent).

@huard The extraction process is to blame for removing most of the metadata. The way that the data extraction is set up, I don't think one can download source files in any case.
@richardarsenault I have all of these extracted and they are currently stored in a somewhat CF-like format. If we can navigate data access rights, I can place on copy on our prod server with relative ease.

@Zeitsperre Is this something worth a bug report to the cds toolbox folks ? I'm concerned that existing ERA-5 users access our repo, find the the files are different from those they're using, and end up being confused. Suggestions to make the whole thing as transparent as possible ?
Have you agreed something with Nathalie/Agnès regarding data access rights and credits ?


Bump packages

Migrated to 14.1
https://github.com/appany/AppAny.HotChocolate.FluentValidation/pull/114


EmptyConditionalBody autocorrect can result in breaking logic changes

Looking at EmptyConditionalBody spec, some autocorrect scenarios (in expect_correction blocks) actually result in logic-breaking changes. For example:
https://github.com/rubocop/rubocop/blob/3f24b822a37f08e54a3e076e3a091f808adc6fa9/spec/rubocop/cop/lint/empty_conditional_body_spec.rb#L115-L133
To make it clearer here's the same case but with more real-world-y variable names:
# before
if show_version
  puts VERSION
elsif dry_run
elsif delete_files
  `rm -rf *`
end

# after
if show_version
  puts VERSION
elsif delete_files
  `rm -rf *`
end

After an autocorrect run, dry_run flag is no longer used which is a breaking change.
RuboCop version
1.60.2 (using Parser <IP_ADDRESS>, rubocop-ast 1.30.0, running on ruby 3.2.1) [arm64-darwin22]
/the latest on the main branch

The autocorrect is already marked as unsafe, but it could be improved to replace internal elsif branch bodies with nil, as opposed to removing them.
if show_version
  puts VERSION
elsif dry_run # internal branch, replace with `nil`
  nil
elsif delete_files
  `rm -rf *`
end


Added context managers for automatically closing fds

Issue Reference
This PR address the issue to with forgetting to close file descriptors.
Summarize
Used with context manager for cleaner and better code.

I could have used comprehensions, but was only going for where it was
crutial.
@bhumilharia Yeah, need to find out how it gets hit, and some form of
caching/memoization should be done.
On Fri, Aug 17, 2018 at 10:09 PM, Bhumil Haria<EMAIL_ADDRESS>wrote:

@bhumilharia commented on this pull request.
In mainapp/admin.py
https://github.com/IEEEKeralaSection/rescuekerala/pull/374#discussion_r210966941
:

@@ -49,47 +48,49 @@ class VolunteerAdmin(admin.ModelAdmin):
readonly_fields = ('joined',)
list_display = ('name', 'phone', 'organisation', 'joined')
list_filter = ('district', 'joined',)

def download_csv(self, request, queryset):

Shouldn't we be caching/memoizing the result for this? This probably adds
to the performance/uptime issues.
How often is this hit?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IEEEKeralaSection/rescuekerala/pull/374#pullrequestreview-147298683,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQMnnIrNYL4XYwrNLZ7M-qceYaR5iBmsks5uRvGngaJpZM4WBmKz
.


PHP 8.1.5 Throwing Deprecated Error on Iterator Class

Any plans to develop this and bring it up to speed with PHP 8.1.5?
I'm running your sample code and getting the following error:
Deprecated: Return type of TournamentGenerator\Containers\BaseContainer::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .\sandbox\bracket-may-2022\vendor\heroyt\tournament-generator\src\TournamentGenerator\Containers\BaseContainer.php on line 122

Hi, I'm planning on bringing the library to PHP 8.1, but currently, I'm preoccupied with other work.
The warning you're getting is only due to missing return type hint but should not affect functionality itself. You can add a '@' sign before the function call which will mute the warning.


View All Menu Button is not working in the home page !

Hello PA,
There is a wrong entered in the View all menu button
Screenshot -

Can you please assign me this issue, I want to fix this.

Hi @khushi-joshi-05 can u pls assign me this issue.


Make script to prepare dataset

This commits changes the following:

Adds script to convert dataset from its format to format, where there are only two columns "input" and "output"
Moves dataset-specific code to this script

add to benchmark section how to use datasets

@SpeedOfMagic can we close this PR since we are already going with another approach?

OK


ingress-nginx: Upgrade to 0.17.1

Upstream Changes:

ingress-nginx 0.17.1 (https://github.com/kubernetes/ingress-nginx/releases/tag/nginx-0.17.1)
Remove duplicated securityContext (https://github.com/kubernetes/ingress-nginx/pull/2705)

Our Changes;

Revamp ingress-nginx-controller from DaemonSet to Deployment, reduce duplicted resource usage with replicas: 1 (https://github.com/kubernetes-incubator/kubespray/pull/2991)
Follow upstream with svc-ingress-nginx.yml.j2, resolve dnsPolicy related issues (https://github.com/kubernetes-incubator/kubespray/pull/2999)
Remove hostNetwork and nodeSelector support, in favor of Service with NodePort/LoadBalancer

Close #2991
Close #2998
Close #2999

There is now 0.17.1

Ok will update for 0.17.1; moreover I am working with weave pre-2.4.0 upgrade too so once ready we could revamp DaemonSet with Deployment as upstream ;-)

ci check this

@hswong3i thanks, I was looking for the version bump ;)
Removing hostNetwork in favor of NodePort/LoadBalancer break backwards compatibility: until now ingress_nginx_enabled: true would make the ingress controller listen on TCP/80 and TCP/443 (by default) for all nodes in the kube-ingress group.
With the new defaults in this PR, the ingress controller would listen on TCP/30000 and TCP/30001 (default NodePort range is 30000-32767): that's going to break things when people upgrade.
I would suggest to split the version bump and addition of NodePort/LoadBalancer into 2 different PR.

Yes using deployment + service is a braking change, but generally you will no care about it, anymore.
This reason is about HTTPS + ProxyProtocol: you will need AWS ELB or at least a haproxy in order to capture client request ip, else your backend, eg Apache will not able to works well in log or ip filtering. With the use of cert-manager + letsencrypt, you have no reason not to do so.
Therefore the external load balancer will be the one who handle your 80/443, and so you also have no reason to enforce using 80/443 on ingress-nginx for direct connection

In the current version of Kubespray no external load balancer is required and it captures the client IP just fine. I think it is good to keep that as an option.
Not all deployments have an LB service available: bare metal requires something like MetalLB, OpenStack LBaaS (Octavia) is rarely deployed (7% of production deployments according to the 2017 user survey).

I agree, a LoadBalancer should not be mandatory. This was why I added hostport to the upstream chart: https://github.com/helm/charts/pull/3097
If the default is changed could you add a variable to support the current behaviour?

Another though: shall we clone as much as functionality from chart version? Therefore options with hostport will also implement.
Because now I just clone the deploy example from upstream directly, so I would like to keep it simple stupid and only keep single implementation style; if we keep sync with chart then we should clone options as much as possible.

IMHO this change will break to much. Right now you cannot count on having a loadbalancer on all systems kubespray is supporting. As mentioned above you rarley find external load balancers on bare metal
I would suggest as mentioned above to separate this change into a new pull request and add the option to still use Hostport
I love to be upstream as much as possible but in this case this would be a bad move.
Or we think about to push MetalLB into I kubespray. There is already a pull request for it.

So let's keep it simple stupid, and focus on 0.17.1 only ;-)

Could we clarify how to deploy the ingress_nginx to all nodes?  The documentation for the node selector component is not as straight forward as the old [kube-ingress] selector.
I am specifically speaking of k8s-cluster.yml file and its old [kube-ingress] selector tag and the commit https://github.com/kubernetes-incubator/kubespray/commit/a0defefb3ffa20042b1fddb55e5456bdf290f47b.
# ingress_nginx_nodeselector:
#   node-role.kubernetes.io/master: "true"

For deploy to all nodes just simply under the value:
ingress_nginx_nodeselector: ~

Could this PR now simple and straightforward enough for merge?


fix backpack and duffels in hand display

About the PR
Fixes #10147.
This appears to be caused by #9706. Just needed to add the Item component to each of the backpacks and duffels.
Screenshots

Changelog

:cl:

fix: backpack and duffels no longer only display default gray back when held


"noEmit": true

It's common to have noEmit set to true, but ncc needs true. Maybe it should override this key.

I just tried it in Now 2 and it probably still uses previous NCC version.

Still not deployed in Now 2.


Backlight mode on TS0001, TS0002, TS0003[BUG]

Backlight mode don´t works on ZHA (TS0001, TS0002, TS0003). In configuration appear as select.
But works on tuya or local tuya integrations and this option appear as a boolean switch.
Sorry, i´m using google translate
ZHA:

TUYA:

Can you attach the logs for the HA backlight operation.
I would expect that at least the Off and LightWhenOn should work. Any errors in the logs?

@javicalle ,
Could you instruct me how to get the log?
Thanks

Is none of the values working? Neither the Off or the LightWhenOn options?
Here is some instructions to enable the debug logs:

https://www.home-assistant.io/integrations/zha/#debug-logging

Be carefull because can be very verbose. Don't keep long time after get the logs you want.

I tried all 3 options.
I'll follow the instructions to enable debug.
Are there any keywords to look for?

backlight.txt
@javicalle ,
I hope it helps.

I can't see the logs from the quirk.
Can you attach the signature or the diagnosis from any of the failing devices?
Can you check if devices are loading any quirk?

zha-dba4ffd11e8899871583d5f3cd82eea8-_TZ3000_bmqxalil TS0001-2a3c9be3eeb5b383eb0863a323f4c8cc.json (1).txt
"Can you check if devices are loading any quirk?"
How do I do it?

home-assistant.log
Full log.

@javicalle
If there's anything else I can do, please let me know.

Hi @javicalle !!
Any news?

Out of time right now.
I'll check in the weekend.

Hi @javicalle !
Any good news?

Same issues here too. I need the backlight to go off as it really bothers me at night. Also if the backlight can go off on other devices like ZB-SW03
Or can anyone suggest which device can i buy that can switch off backlight in ZHA.

Any news here?

It still doesn't work. I'm migrating to Z2M.


Move dashboards to use go API

Please, add the jira issue that is being solved in the title of each PR with [] so Jira can make the binding.
I hope that with COO 0.3.1 we also have "Datasource" object to be able to add PrometheusDatasource object via API instead of just spitting plain yaml like we do here: https://github.com/openstack-k8s-operators/telemetry-operator/blob/main/pkg/metricstorage/dashboard_datasource.go#L46-L59

I added the Jira number to the title. Regarding the Datasource, I also saw that piece of yaml. There is no "Datasource" type in OBO: https://github.com/rhobs/observability-operator/blob/main/pkg/apis/uiplugin/v1alpha1/types.go .
The issue with this yaml is, that it's not actually a CR. This is saved as a ConfigMap: https://github.com/openstack-k8s-operators/telemetry-operator/blob/main/controllers/metricstorage_controller.go#L720

/lgtm


[Feature]: Open/Close buttons for curtains

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
The current mushroom card for covers gives you 2 arrows (up and down) for curtains. This isn't very intuitive for curtains that close from left to right/right to left or (in my case) even from the middle.
Describe the solution you'd like
Provide an extra option to replace the arrow buttons for 2 simple text buttons. Open and Close.
Describe alternatives you've considered
No response
Additional context
No response

Showing the device as a gate or a awning in HA gives you 2 buttons that are better. But I would like to keep it as a cover and just have the open/close buttons.

Desperately need this :)

Mushroom rules for icons are the same for mushroom and official home assistant cards. We don't have the information about the direction of opening so we can not propose other icons for this.
I'm not fan about proposing an option for everything because Mushroom card will become more complicated with more and more features.
Mushroom card, tile card and entities card

Device page

Cover more info

weird, Home Assistant shows this icon
yet Mushroom shows the up/down icon

What's the device class of your entity? Can you provide the state using dev tools?

I think the issue is that it's a group, and it doesn't take over the device class. Any way to change that?

You should be able to set curtain device class on your group using entity settings. It will fix your issue.

Mushroom rules for icons are the same for mushroom and official home assistant cards. We don't have the information about the direction of opening so we can not propose other icons for this. I'm not fan about proposing an option for everything because Mushroom card will become more complicated with more and more features. Also, as the issue is present for every Home Assistant card, Mushroom card is not responsible to fix it.
Mushroom card, tile card and entities card
Device page
Cover more info

I don’t think I understand. I understand you can not now what is open or close but isn’t that the same with up or down? That is why you always have the option to invert.
And I would say that down is closed and up is open.

@WorlockM please provide some screenshot and state information of your entity. I don't really understand.


Calendar not removing all events

The last version caused a bug where the method removeAll was not removing all the events. I have removed the lastest version from the README so that people don't use the latest version. The newest version adds a method to fetch all events for a month, so it's the previous version is probably fine for most people.

Fixed in branch @bug/fix_clearing_events, will release a new version today. I added a unit test for this case to it that it won't happen again.

fixed in:
dependencies {
    compile 'com.github.sundeepk:compact-calendar-view:1.8.7'
}


Segmentation fault (core dumped)

I've successfully compiled Godot from github source code. commit 87517c564b832
when I run the output I get:
$ ./godot.x11.tools.64
Segmentation fault (core dumped)
halp!
(using ubuntu gnome 15.04 64bits)

Can you try running it through gdb so that there is more info about the crash?
Also, were you able to run earlier versions fine?

No I wasn't able to run previous versions it gave me the same error. I'll try to debug and will update you.

Okay I switched machines and the bug no longer occurs so it does not affect me anymore.
but it did happen on the old machine it was a core dual machine by the way.

It would still be quite interesting to get the output from gdb, you can run it as:
gdb ./bin/godot.x11.tools.64
Then run and after the crash bt to get the backtrace.

I will as soon as I can. I'm in a challenge to create a game in 7 days now so I don't have that much time but I'll do it later today.

BTW, it might be from old OpenGL or drivers version...

Also, related to #67, #2067 and #977 (segmentation fault, linux)

most likely OpenGL not supported

Yeah, closing as a duplicate of #156.

Sorry I couldn't debug it guys. It wasn't my computer. it was a computer in a co-working space that I had access to for a limited amount of time.


Typewriter text "escape"

In most VNs, the behavior of display all the string once is to tap.
In EKVN, if we do this, the system pass to the next string (not tested).

Fixed it, it should look more normal in the newest version.

Thanks you !


Added children property to SinglePickerMaterialDialog

What's your use case for this?
To approve the PR I'd also need you to please update the documentation.

Closed because of inactivity


Make pack/unpack benchmarks have same amount of elements for all benchmarks

The shape is derived from working_set_size. If the number is not a multiple of 4, The final number of elements could have large variants between avx2 and avx512 configurations.
E.g., I tried benchmarking 384x512xf32, the working_set_size is 1572864 in this case. However, the total elements passed to avx512 is 1.5x of avx2. It misleads the metrics in terms of latency. Now I realize that we should mostly look at bandwidth from the report, not latency. Maybe we should compute the shape correctly, so they will pack the same amount of elements? Or maybe it's just an approximation to get memory bandwidth and we don't really care about the actual number of elements passed to benchmarks?

I'm good if we don't land the PR. Because I can get what I want now. I send out the PR for checking if my understanding is correct; exposing what I found to public users.