sssd: 2.7.4 -> 2.8.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/SSSD/sssd/releases.
meta.description for sssd is: "System Security Services Daemon"
meta.homepage for sssd is: "https://sssd.io/"
meta.changelog for sssd is: "https://sssd.io/release-notes/sssd-2.8.0.html"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.8.0 with grep in /nix/store/qh9njznl57c0ab3hwqnarg5k095vr1x9-sssd-2.8.0
found 2.8.0 in filename of file in /nix/store/qh9njznl57c0ab3hwqnarg5k095vr1x9-sssd-2.8.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
autofs5
sssd

Instructions to test this update (click to expand)

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

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sssd https://github.com/r-ryantm/nixpkgs/archive/fadf7d61f27af7718fe7a5587dec4f0b3f7f7a81.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/qh9njznl57c0ab3hwqnarg5k095vr1x9-sssd-2.8.0
ls -la /nix/store/qh9njznl57c0ab3hwqnarg5k095vr1x9-sssd-2.8.0/bin

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

2 packages built:

autofs5
sssd

Maintainer pings
cc @outergod @illustris for testing.

@illustris This nixos teste seems to fail though? https://github.com/NixOS/nixpkgs/pull/195026/checks?check_run_id=8777289094

Weird... I did nix build github:/r-ryantm/nixpkgs/auto-update/sssd#nixosTests.sssd, which worked. Didn't notice the ofborg failure.
@ofborg test sssd

@ofborg test sssd-ldap

Not sure why it's failing on ofborg x86_64. Works on my machine.
[illustris@desktop:~/src/nixpkgs/.worktree/master]$ git rev-parse HEAD
7338069be813d94aec2d09eba6df7bb681bfd5f9
[illustris@desktop:~/src/nixpkgs/.worktree/master]$ git diff
diff --git a/pkgs/os-specific/linux/sssd/default.nix b/pkgs/os-specific/linux/sssd/default.nix
index 462151ff64f..ef92739ec27 100644
--- a/pkgs/os-specific/linux/sssd/default.nix
+++ b/pkgs/os-specific/linux/sssd/default.nix
@@ -13,13 +13,13 @@ let
 in
 stdenv.mkDerivation rec {
   pname = "sssd";
-  version = "2.7.4";
+  version = "2.8.0";

   src = fetchFromGitHub {
     owner = "SSSD";
     repo = pname;
     rev = version;
-    sha256 = "sha256-tPrximWUeG3wcuZZNo8l4QqC9ZwcZupIBZGF7bm7hqQ=";
+    sha256 = "sha256-i2RRvIFQLuFw9Q3pLOgomvCH9j8h3JAailoIww1dnLs=";
   };

   postPatch = ''
[illustris@desktop:~/src/nixpkgs/.worktree/master]$ nix log .#nixosTests.sssd-ldap | tail
warning: Git tree '/home/illustris/src/nixpkgs/.worktree/master' is dirty
machine # [    8.798436] slapd[909]: conn=1000 op=3 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadowMax shadowWarning shadowInactive shadowExpire
shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host rhost loginDisabled loginExpirationTime loginAllowedTimeMap sshPublicKey userCertificate;binary mail
machine # [    8.802210] slapd[909]: conn=1000 op=3 SEARCH RESULT tag=101 err=0 qtime=0.000012 etime=0.000187 nentries=1 text=
(finished: must succeed: getent passwd alice, in 0.04 seconds)
(finished: run the VM test script, in 9.24 seconds)
test script finished in 9.29s
cleanup
kill machine (pid 8)
machine # qemu-kvm: terminating on signal 15 from pid 6 (/nix/store/wyhbl43ycqn43d08v5fqj1j6ynf7nz73-python3-3.10.7/bin/python3.10)
(finished: cleanup, in 0.04 seconds)
kill vlan (pid 7)

From the ofborg logs, it looks like it might be a race condition in the test
machine: waiting for unit sssd.service
(finished: waiting for unit sssd.service, in 0.05 seconds)
machine: must succeed: getent passwd alice
machine # [    9.320404] sssd_be[902]: sssd.dataprovider.getAccountInfo: Error [1432158212]: SSSD is offline
machine # [    9.321507] sssd_nss[910]: CR #0: Could not get account info [1432158212]: SSSD is offline

I'll investigate further. Meanwhile, @viraptor or anyone else, can you please try building the ssd-ldap test yourself?

I'm able to reproduce the error now, by throttling openldap:
[illustris@desktop:~/src/nixpkgs/.worktree/master]$ git diff
diff --git a/nixos/tests/sssd-ldap.nix b/nixos/tests/sssd-ldap.nix
index 27dce6ceb98..c2a6077841c 100644
--- a/nixos/tests/sssd-ldap.nix
+++ b/nixos/tests/sssd-ldap.nix
@@ -85,6 +85,7 @@ in import ./make-test-python.nix ({pkgs, ...}: {
         ldap_default_authtok = $LDAP_BIND_PW
       '';
     };
+    systemd.services.openldap.serviceConfig.CPUQuota = "0.01%";
   };

   testScript = ''
diff --git a/pkgs/os-specific/linux/sssd/default.nix b/pkgs/os-specific/linux/sssd/default.nix
index 462151ff64f..ef92739ec27 100644
--- a/pkgs/os-specific/linux/sssd/default.nix
+++ b/pkgs/os-specific/linux/sssd/default.nix
@@ -13,13 +13,13 @@ let
 in
 stdenv.mkDerivation rec {
   pname = "sssd";
-  version = "2.7.4";
+  version = "2.8.0";

   src = fetchFromGitHub {
     owner = "SSSD";
     repo = pname;
     rev = version;
-    sha256 = "sha256-tPrximWUeG3wcuZZNo8l4QqC9ZwcZupIBZGF7bm7hqQ=";
+    sha256 = "sha256-i2RRvIFQLuFw9Q3pLOgomvCH9j8h3JAailoIww1dnLs=";
   };

   postPatch = ''

The issue is probably caused by CPU load on ofborg. If OpenLDAP isn't at a point where it can respond to requests by the time the getent command runs, the test fails. It can be fixed by adding machine.wait_for_console_text("Backend is online") to the test. This PR can be merged. I'll open another one with the change to the test.


[fix] [broker] correct compaction phase one timeout meaning

Motivation
Configuratioin brokerServiceCompactionPhaseOneLoopTimeInSeconds is defined as the total timeout of phase one.
    @FieldContext(
            category = CATEGORY_SERVER,
            doc = "Timeout for the compaction phase one loop, If the execution time of the compaction "
                    + "phase one loop exceeds this time, the compaction will not proceed."
    )
    private long brokerServiceCompactionPhaseOneLoopTimeInSeconds = 30;

But current implementation just set a timeout for a single message read operation, which is different with the meaning of brokerServiceCompactionPhaseOneLoopTimeInSeconds and will result into thousands of timer tasks be scheduled and cancelled in the scheduler because we may iterate many messages.
Modifications
Set a timer task for the tatol phase one.
Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/thetumbled/pulsar/pull/32

I think I have introduced a bad configuration name in https://github.com/apache/pulsar/pull/11206. Actually, it was the timeout for an entry read.
IMO, we should have a new configuration name and deprecate the existing one. I don't think it's reasonable to have a timeout for the whole phase one loop. After the first time the phase one loop get timeout, the subsequent phase one loop will almost always get timeout with more published messages unless changing phase one loop timeout.

I think I have introduced a bad configuration name in #11206. Actually, it was the timeout for an entry read.
IMO, we should have a new configuration name and deprecate the existing one. I don't think it's reasonable to have a timeout for the whole phase one loop. After the first time the phase one loop get timeout, the subsequent phase one loop will almost always get timeout with more published messages unless changing phase one loop timeout.

I agree. I have introduced a new configuration name and deprecate the existing one.
PTAL, thanks.

I have created a pip to change the conf name, please help review it, thanks!
https://github.com/apache/pulsar/pull/21910
@codelipenghui @poorbarcode @BewareMyPower

I have refactor the implementation to just modify the doc, so that we can avoid to create a pip and introduce a new conf name. PTAL, thanks.
@codelipenghui @poorbarcode @BewareMyPower

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (74f1cd5) 36.46% compared to head (4f977ff) 73.58%.
Report is 6 commits behind head on master.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #21908       +/-   ##
=============================================
+ Coverage     36.46%   73.58%   +37.11%
- Complexity    12381    32402    +20021
=============================================
  Files          1725     1861      +136
  Lines        131697   138589     +6892
  Branches      14400    15184      +784
=============================================
+ Hits          48019   101976    +53957
+ Misses        77278    28720    -48558
- Partials       6400     7893     +1493

Flag
Coverage Δ

inttests
24.13% <ø> (+0.02%)
:arrow_up:

systests
23.63% <ø> (-0.01%)
:arrow_down:

unittests
72.87% <ø> (+40.84%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...org/apache/pulsar/broker/ServiceConfiguration.java
99.39% <ø> (+1.41%)
:arrow_up:

... and 1437 files with indirect coverage changes


Trying to update deps just deletes all .go files recursively

13:15 ~/go/src/vm (master)
$ git status --short
13:15 ~/go/src/vm (master)
$ govendor fetch +v
13:15 ~/go/src/vm (master)
$ git status --short
 D vendor/github.com/dustin/go-humanize/LICENSE
 D vendor/github.com/dustin/go-humanize/README.markdown
 D vendor/github.com/dustin/go-humanize/big.go
 D vendor/github.com/dustin/go-humanize/bigbytes.go
 D vendor/github.com/dustin/go-humanize/bytes.go
 D vendor/github.com/dustin/go-humanize/comma.go
 D vendor/github.com/dustin/go-humanize/ftoa.go
 D vendor/github.com/dustin/go-humanize/humanize.go
 D vendor/github.com/dustin/go-humanize/number.go
 D vendor/github.com/dustin/go-humanize/ordinals.go
 D vendor/github.com/dustin/go-humanize/si.go
 D vendor/github.com/dustin/go-humanize/times.go
 D vendor/github.com/mitchellh/goamz/aws/attempt.go
 D vendor/github.com/mitchellh/goamz/aws/aws.go
 D vendor/github.com/mitchellh/goamz/aws/client.go
 D vendor/github.com/mitchellh/goamz/ec2/ec2.go
 D vendor/github.com/mitchellh/goamz/ec2/sign.go
 D vendor/github.com/vaughan0/go-ini/LICENSE
 D vendor/github.com/vaughan0/go-ini/README.md
 D vendor/github.com/vaughan0/go-ini/ini.go
 D vendor/github.com/vaughan0/go-ini/test.ini
 M vendor/vendor.json

vendor.json has been updated with origins and all actual dependencies are gone leaving the folders empty.
govendor list thinks it is all ok then.

Can you give me a way to reproduce? What is your source tree look like? A repo I can clone plus commands to run to reproduce?

I faced it working with journalbeat and our local aforementioned vm project.
export GOPATH=/tmp/`uuidgen`
go get -u github.com/kardianos/govendor
cd $GOPATH/src
git clone https://github.com/mheese/journalbeat.git github.com/mheese/journalbeat
cd github.com/mheese/journalbeat
govendor init
govendor fetch -v +o
find vendor -type f
du -chd1 vendor
govendor list +v
govendor fetch -v +v
du -chd1 vendor
find vendor -type f

Last command's output for me is this:
$ find vendor -type f
vendor/github.com/davecgh/go-spew/LICENSE
vendor/github.com/eapache/go-resiliency/LICENSE
vendor/github.com/elastic/beats/LICENSE
vendor/github.com/garyburd/redigo/LICENSE
vendor/github.com/klauspost/compress/LICENSE
vendor/github.com/mheese/go-systemd/LICENSE
vendor/github.com/urso/go-lumber/LICENSE
vendor/golang.org/x/net/LICENSE
vendor/golang.org/x/net/PATENTS
vendor/golang.org/x/sys/LICENSE
vendor/golang.org/x/sys/PATENTS
vendor/vendor.json

Another example (vm-alike in terms of dependencies):
create $GOPATH/src/some_folder, go there and create main.go containing this:
package main

import (
	"github.com/dustin/go-humanize"
	"github.com/mitchellh/goamz/aws"
	"github.com/mitchellh/goamz/ec2"
	"github.com/vaughan0/go-ini"
)

func main() {
	return nil
}

Run:
govendor init
govendor fetch -v +o
find vendor -type f
du -chd1 vendor
govendor list +v
govendor fetch -v +v
du -chd1 vendor
find vendor -type f

I've tried it with govendor, godep and coreos/etcd and could not reproduce the issue.
Your tool just works for them but not for journalbeat and our vm utility!..
P.S. I understand that coreos/etcd is a complex project and it is not relevant to this issue and perhaps it should not be treated this dumb way as desribed above but try to run the same procedure(fetch +o && fetch +v) there.
After govendor init(since etcd has no vendor folder in the project root) and govendor fetch +o:
$ find vendor -type f
     641
$ du -chd1 vendor
 16K    vendor/bitbucket.org
  0B    vendor/context
3,8M    vendor/github.com
4,1M    vendor/golang.org
272K    vendor/google.golang.org
380K    vendor/gopkg.in
  0B    vendor/net
8,6M    vendor
8,6M    total

After govendor fetch +v:
$ find vendor -type f|wc -l
     515
$ du -chd1 vendor
 16K    vendor/bitbucket.org
  0B    vendor/context
3,2M    vendor/github.com
3,7M    vendor/golang.org
272K    vendor/google.golang.org
304K    vendor/gopkg.in
  0B    vendor/net
7,5M    vendor
7,5M    total

There is some mess in govendor list so out of curiousity take a look at etcd as well.

@kardianos I've noticed one thing with github.com/mheese/journalbeat. Since Journalbeat has now vendoring enabled running govendor fetch +v does nothing but sets the origins of all dependencies as github.com/mheese/journalbeat/vendor/$ORIGINAL_PACKAGE_PATH, rewrites the commit hash and revision time likes this:
diff --git a/vendor/vendor.json b/vendor/vendor.json                                                                                [0/1553]
index 9578995..1aac4f9 100644
--- a/vendor/vendor.json
+++ b/vendor/vendor.json
@@ -4,297 +4,346 @@
        "package": [
                {
                        "checksumSHA1": "ufXIHqs0A7woV8TlcLc45Gh+hTc=",
+                       "origin": "github.com/mheese/journalbeat/vendor/github.com/Shopify/sarama",
                        "path": "github.com/Shopify/sarama",
-                       "revision": "1ab42258e720f894cc04e8d008bfa26cc69ec725",
-                       "revisionTime": "2016-06-09T20:05:44Z"
+                       "revision": "d9e4d846aed22858d74d9ab23fe8129c26c5d5e5",
+                       "revisionTime": "2016-06-21T15:24:17Z"
                },
                {
                        "checksumSHA1": "5rPfda8jFccr3A6heL+JAmi9K9g=",
+                       "origin": "github.com/mheese/journalbeat/vendor/github.com/davecgh/go-spew/spew",
                        "path": "github.com/davecgh/go-spew/spew",
-                       "revision": "5215b55f46b2b919f50a1df0eaa5886afe4e3b3d",
-                       "revisionTime": "2015-11-05T21:09:06Z"
+                       "revision": "d9e4d846aed22858d74d9ab23fe8129c26c5d5e5",
+                       "revisionTime": "2016-06-21T15:24:17Z"
                },

Working with internal projects not hosted anywhere leads to what is claimed in the Subject - deleting everything as in the above return nil example.

Fixed in https://github.com/kardianos/govendor/commit/4cd46d367e180051eccf5bda300339488648f272


Timeouts for client connections

Coverage decreased (-0.03%) to 46.199% when pulling e43ee75f3662d14a528dfffa8c626185ccb1828a on http_timeout into a0a14ee314ea8070baa25e25b95dd48de18f6a83 on master.


exists a way to define the charset for the connection?

Actually i'm using db2 as dat base, i'm looking if exists how to define the charset;
some special chars in spanish are changing once are inserted in the database

Check db drivers docs if it can be set in connection parameters or it might be set during db creation maybe or set separately when new connection is created with afterCreate callback that can be given in knex config.

Knex doesnt have any separate mechanish just for it.

Check db drivers docs if it can be set in connection parameters or it might be set during db creation maybe or set separately when new connection is created with afterCreate callback that can be given in knex config.

That's why i'm asking. I'm not found info about the charset.
thanks


[prim] Add an internal check flag

The check flag always disables upon reset.  When the first rising edge of the request is seen, it is then activated again until the next reset.  This ensures we check only during active periods and not accidentally across a reset, which is what caused the failure previously.

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

Thanks for taking care of this @tjaychen, LGTM !


add information about routes and graceful server termination

Description

Print routes
Change routes to not include the service prefix
Add close() method to Data layer
Add disconnect() method to Datastore, MetadataStore, and ArtifactStore
Add information about assertions

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Attention: 34 lines in your changes are missing coverage. Please review.

Comparison is base (34830a7) 80.33% compared to head (3349f1d) 66.97%.
Report is 132 commits behind head on main.

Files
Patch %
Lines

superduperdb/backends/dask/compute.py
47.05%
18 Missing :warning:

superduperdb/backends/base/compute.py
68.96%
9 Missing :warning:

superduperdb/backends/base/query.py
85.71%
3 Missing :warning:

superduperdb/backends/base/metadata.py
75.00%
2 Missing :warning:

superduperdb/backends/base/artifact.py
80.00%
1 Missing :warning:

superduperdb/backends/base/data_backend.py
80.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1416       +/-   ##
===========================================
- Coverage   80.33%   66.97%   -13.37%
===========================================
  Files          95      103        +8
  Lines        6602     7310      +708
===========================================
- Hits         5304     4896      -408
- Misses       1298     2414     +1116

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: check connected identity on connect()

Explanation
This PR changes checks if there is a connected identity before sending a new request to connect identity page.
Related Issues

Blocked by #966
Fixes #965

Screenshots
N/A
Manual Testing Steps
N/A
Pre-Merge Checklist

[ ] PR template is filled out
[x] Pre-commit and pre-push hook checks are passed
[ ] E2E tests are passed locally
[ ] IF this PR fixes a bug, a test that would have caught the bug has been added
[x] PR is linked to the appropriate GitHub issue
[x] PR has been added to the appropriate release Milestone

PR template source from github.com/MetaMask

@0xmad this change resolved this bug #992
https://github.com/CryptKeeperZK/crypt-keeper-extension/blame/b11cf8db7d7db566dbbc9172bb6745e9085dacef/packages/app/src/ui/pages/Login/useLogin.ts#L46-L52


Cannot build. Missing ImageEncodeOptions, VideoFrame, etc.

Cannot build an Angular 14 + TypeScript 4.7 with babylon 7 or 6. Workaround: Use version 5 of babylon.
Missing types:

ImageEncodeOptions
OffscreenRenderingContextId
OffscreenRenderingContext
VideoFrame

https://doc.babylonjs.com/setup/frameworkPackages/es6Support
Upgrading Angular and/or Typescript is currently impossible.
Is there a compatibility info? What version is depending on what dependencies. And how to handle it? Not sure, but I also could just define the missing types as any-type. Or babylon could support these type fallbacks/polyfill. It's great that babylon comes with types. But it's sad that TypeScript (indirect) types are blocking the use. Since types have no effect on runtime. It's just the d.ts behind in node_modules of babylon. At least we could provide some docs and how to handle this.

cc @RaananW

Those classes require a newer version of typescript. It's that possible for your project?

Adding the types is more than possible, we can look into that


FLPATH-861 Promote M2K workflow from examples to prod

updated Quarkus and SF versions to latest available
introduced swf-parent pom to isolate common configuration (will extend later to other SWFs in this repo)
updated notifications API and integrated changes in the m2k SWF (including input schema)

/lgtm


RuntimeError: The size of tensor a (128) must match the size of tensor b (289) at non-singleton dimension 1

I try to test the finetune with gradio_finetune.py
A little test database:
prepare complete
samples : 27333
time data : 27:42:51
min sec : 0.6
max sec : 38.14
file_arrow : data/hun_pinyin/raw.arrow
I got the following error at 1998 step with one rtx3090 or 999 with 2 rtx3090:
Building prefix dict from the default dictionary ...
Dumping model to file cache /tmp/jieba.cache
Loading model cost 0.397 seconds.
Prefix dict has been built successfully.
accelerate launch finetune-cli.py --exp_name F5TTS_Base --learning_rate 0.0001 --batch_size_per_gpu 3200 --batch_size_type frame --max_samples 64 --grad_accumulation_steps 1 --max_grad_norm 1 --epochs 10 --num_warmup_updates 2734 --save_per_updates 6834 --last_per_steps 34166 --dataset_name hun --finetune True
Using logger: wandb
wandb: Using wandb-core as the SDK backend. Please refer to https://wandb.me/wandb-core for more information.
wandb: Currently logged in as: arpadsantha (arpadsantha-hobby). Use wandb login --relogin to force relogin
wandb: Tracking run with wandb version 0.18.5
wandb: Run data is saved locally in /home/sarpba/F5-TTS/wandb/run-20241020_211115-4n6ufg52
wandb: Run wandb offline to turn off syncing.
wandb: Syncing run F5TTS_Base
wandb: ⭐ View project at https://wandb.ai/arpadsantha-hobby/CFM-TTS
wandb: 🚀 View run at https://wandb.ai/arpadsantha-hobby/CFM-TTS/runs/4n6ufg52
Loading dataset ...
Sorting with sampler... if slow, check whether dataset is provided with duration: 100%|██████████████████████████████████████████████████████████████████████████| 27333/27333 [00:00<00:00, 3117838.22it/s]
Creating dynamic batches with 3200 audio frames per gpu: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████| 27333/27333 [00:00<00:00, 3736609.34it/s]
/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/utils/data/dataloader.py:558: UserWarning: This DataLoader will create 16 worker processes in total. Our suggested max number of worker in current system is 12, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
warnings.warn(_create_warning_msg(
Epoch 1/10:   0%|                                                                                | 0/3127 [00:00<?, ?step/s]/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/conv.py:306: UserWarning: Applied workaround for CuDNN issue, install nvrtc.so (Triggered internally at ../aten/src/ATen/native/cudnn/Conv_v8.cpp:84.)
return F.conv1d(input, weight, bias, self.stride,
Epoch 1/10:  64%|████████████████████████████████████████████████████████████████████████████████▌                                             | 1998/3127 [12:04<06:49,  2.76step/s, loss=0.582, step=1998]
Traceback (most recent call last):
File "/home/sarpba/F5-TTS/finetune-cli.py", line 108, in
main()
File "/home/sarpba/F5-TTS/finetune-cli.py", line 102, in main
trainer.train(train_dataset,
File "/home/sarpba/F5-TTS/model/trainer.py", line 231, in train
loss, cond, pred = self.model(mel_spec, text=text_inputs, lens=mel_lengths, noise_scheduler=self.noise_scheduler)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sarpba/F5-TTS/model/cfm.py", line 273, in forward
pred = self.transformer(x = φ, cond = cond, text = text, time = time, drop_audio_cond = drop_audio_cond, drop_text = drop_text)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sarpba/F5-TTS/model/backbones/dit.py", line 139, in forward
text_embed = self.text_embed(text, seq_len, drop_text = drop_text)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sarpba/F5-TTS/model/backbones/dit.py", line 60, in forward
text = text + text_pos_embed
RuntimeError: The size of tensor a (128) must match the size of tensor b (289) at non-singleton dimension 1
Traceback (most recent call last):
File "/home/sarpba/F5-TTS/finetune-cli.py", line 108, in
main()
File "/home/sarpba/F5-TTS/finetune-cli.py", line 102, in main
trainer.train(train_dataset,
File "/home/sarpba/F5-TTS/model/trainer.py", line 231, in train
loss, cond, pred = self.model(mel_spec, text=text_inputs, lens=mel_lengths, noise_scheduler=self.noise_scheduler)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sarpba/F5-TTS/model/cfm.py", line 273, in forward
pred = self.transformer(x = φ, cond = cond, text = text, time = time, drop_audio_cond = drop_audio_cond, drop_text = drop_text)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sarpba/F5-TTS/model/backbones/dit.py", line 139, in forward
text_embed = self.text_embed(text, seq_len, drop_text = drop_text)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sarpba/anaconda3/envs/f52/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sarpba/F5-TTS/model/backbones/dit.py", line 60, in forward
text = text + text_pos_embed
RuntimeError: The size of tensor a (128) must match the size of tensor b (289) at non-singleton dimension 1
I test it under ubuntu22.04/24.04/win11 with python version 3.10 / 3.11 / 3.12 the error alwasy same.
Some info form my test audio splits:
0-1s: 6 file
1-2s: 2130 file
2-3s: 8625 file
3-4s: 7562 file
4-5s: 4608 file
5-6s: 2326 file
6-7s: 1137 file
7-8s: 503 file
8-9s: 210 file
9-10s: 113 file
10-11s: 60 file
11-12s: 31 file
12-13s: 10 file
13-14s: 6 file
14-15s: 5 file
15-16s: 0 file
16-17s: 1 file
17-18s: 0 file
18-19s: 0 file
19-20s: 2 file

20s: 4 file

I have one missing character in vocab: "ű"
I'm at a loss as to what could be wrong...

ah, as it is encountered by many people, we may just add a fix.
It is for including a multi-channel audio sample in your training set.

I red that commit befor opened thiis one.
Multi-channel audio sample aka stereo? Just because I checked all of the splits all in same format:
24000 Khz mono 16 bit wav.
I put the fix into the code, and unfortunately nothing changed. The finetune stoped with same error.

@sarpba If that was a new issue with the non-singleton RuntimeError, might you provide the text&audio facing this error?
@ZhikangNiu will help.

Here is the dataset:
https://huggingface.co/datasets/sarpba/test_dataset/tree/main

Hi @sarpba , what kind of text input are you using?
It would be better to provide the specific text input for us to figure out

Sorry I don't understand your question.
I created this the dataset and try to finetune with finetune_gradio.py. Just click click click... :)

Update the text_len in model/backbones/dit.py
def forward(self, text: int["b nt"], seq_len, drop_text=False):  # noqa: F722
        batch, text_len = text.shape[0], text.shape[1]
        text = text + 1  # use 0 as filler token. preprocess of batch pad -1, see list_str_to_idx()
        text = text[:, :seq_len]  # curtail if character tokens are more than the mel spec tokens
        text_len = text.shape[1]
        text = F.pad(text, (0, seq_len - text_len), value=0)

Sems to be good now.Thank you!

thanks for pointing out this bug. fixed!
will close this issue.


Building fails if environment variable $VYSE_PATH is not set.

In order for the project to build successfully, the variable $VYSE_PATH must be defined in rc profile.
There should be a fallback mode for when this var is not set.
pls fix.

Thanks, this has been fixed!


Enable tweets with geo tagging and post to twitter

Display geo tags if available on a small map tile
Fetch both the geo tag hash and the actual  location and also POST it to the loklak_server across that tweet.

@Orbiter , In case I get the locations of the tweets from twitter, it can be retrieved in both the hash format as well as the plain text format, we were having trouble last time to unhash the hash as discussed and i proposed this as a possible solution, I was rather thinking to use the id_str value of the tweet and is it possible to send the hash as well as the plain text back to the server for storing it there in the same tweet object ? Also in case the database has the mapping between hashes and locations would it get easier for us in the long run to automatically detect the location without having twitter to give it to us from the existing hash set

The Google service for location resolution from the name is too fuzzy and it is also a bad dependency for loklak. Here is what I propose to attach exact locations to loklak rich messages:

we must be compatible to 'normal' twitter tweets
we therefore must add exact location information within the tweet text
we therefore need a syntax to express exact locations
an openstreetmap url provides a standard form to set markers on a map, like:
www.openstreetmap.org/?mlat=1.28376&mlon=103.84371
the marker takes less space in the tweet since it is shortened (by twitter)
when you send the tweet, you can send along the location lat=1.28376, lon=103.84371 to twitter which will hopefully show up in twitter as "Singapore, Chinatown"
when we render the tweet, we detect the openstreetmap url and show a map with the coordinates and zoomed in with factor 19, like http://www.openstreetmap.org/?mlat=1.28376&mlon=103.84371#map=19/1.28376/103.84369

this affects https://github.com/loklak/loklak_webclient/issues/100 - please share the work for the display of geotagged tweets

@Orbiter I am currently encountering 404 errors on
http://loklak.org/vis/map.png?text=Test&mlat=1.28373&mlon=103.84379&zoom=18&width=512&height=256

the peer was not upgraded. now its working

please start working on this!

Moving to @prasht63 temporarily so that I can work on the new stable design.

@prasht63 This was assigned 6 days ago. What is the progress?

@loklak/loklak_developers I am facing a blocker over here.With hello.js I am not able to send image with the tweet which is required for this feature.
Hello.js  me/share POST request has two parameters
        message : tweet ,
        file : files
    }).then(log,log);

Here the message will contain the tweet text and the file contains the image data.
Now for this feature the server provides the image as http://loklak.org/vis/map.png?text=Test&mlat=1.28373&mlon=103.84379&zoom=18&width=512&height=256 . However the file parameter should be in html formdata file format. I have tried converting the image to formdata format taking help from here http://stackoverflow.com/questions/4998908/convert-data-uri-to-file-then-append-to-formdata but apparently Hello.js does not recognise it.
We have two options now
1.We can solve this by using a  tag in the form which will ask the user to enter the data but that is so against usability.
2.We try to encode the image data such that it can be accepted by hello.js
Any help will be appreciated.

I was trying to set the form data manually but that can't be done due to security reasons.
http://stackoverflow.com/questions/1696877/how-to-set-a-value-to-a-file-input-in-html
Does anybody have any other workaround.

I have incorporated get Location with the new twitter design.Preview

However I am still facing the blocker described above.

Where can we test it?

@prasht63 regarding https://github.com/loklak/loklak_webclient/issues/93#issuecomment-114548974 do you mean http-post form-data? Thats not a specific image encoding, thats a http request format. I don't see any way to do a 'form-data' output of the image because there is no such thing. Is this maybe simply a misunderstanding of the problem?

@mariobehling I am deploying it on my test server.I will update with link.
@Orbiter Problem is with hello.js limitations.Hello.js does something like this to send a image with tweet.
<input type="file" id="image"></input> // this lets you upload a image from computer
<script>
imagefile=document.getElementById("image").files[0]
hello('twitter').api('me/share', 'POST', {
        message : tweet ,
        file : imagefile
    }).then(log,log);
</script>

The problem is we have our location tile image as URL while hello.js supports through fie upload.

yes then you must download the image first before uploading that with hello.js. Is that not possible with javascript? I believe it should be.

We can not upload the image through Javascript.That is disabled due to security reasons.Refer https://github.com/loklak/loklak_webclient/issues/93#issuecomment-114939710 .Only the user can.

@sudheesh001 As @prasht63 has a lot of IoT tasks, please take over this task again. Cheers.

@mariobehling Sure :smile:

@prasht63 Can you send the diff of the code you have so far on the branch related to this issue

https://github.com/loklak/loklak_webclient/tree/Issue/%2393 has work done till now. Currently on clicking get location in the tweet modal, a location tile is displayed just below the tweet textarea.See preview above.

Regarding CORS @Orbiter made this comment in the gitter channel

CORS is ONLY necessary for JS loading external resources from OTHER domains. Both is not the case here. There should not be problem and implementing CORS would not solve it, it furthermore would open a problem.
Please correct me if I am wrong. But I don’t see it.

@sudheesh001 I have not seen a message from your about that. Any feedback?

Sending a header along with the $http request which is can be done by breaking the current request into
var req = {
 method: 'GET',
 url: 'http://localhost:9000/',
 headers: {
   'Content-Type': undefined
 },
 data: { test: 'test' }
}

but sending a header specifically is failing and still throwing up an XHR error on CORS as mentioned above.

I just added the CORS header in https://github.com/loklak/loklak_server/commit/be178b1f151da241cd71e232f078214afc2ebf6c
I'm still not convinced that we will need that in future production, but right now you are right: it's needed since in test environments the server ports of loklak_webclient and loklak_server are different.

Moving this to M3 because its a subset of #97

Please refer back to #100 when this is done, along with a query example results in a status with the rich content mentioned on top.

Still does not work for me
Step 1: I click "location"

Step 2: I activate share location

Step 3: Nothing happens

Just to clear this up: There are two distinct features

An "Add location" service, which is exactly the same as twitters "add location" to a tweet
An Attach map function, which is just like attaching an image to a tweet, but we attach an embedded map, that we show in loklak tweets (and we generate a photo for twitter when we crosspost it to twitter) Map attachments are discussed here: https://github.com/loklak/loklak_webclient/issues/97

Fixes https://github.com/loklak/loklak_webclient/issues/357 and https://github.com/loklak/loklak_webclient/issues/93   Fixed with https://github.com/loklak/loklak_webclient/commit/9133cb5833d3e21dbab941de080282575b3ddd72

Get location

Allow access to share

See the name of the place where you're posting from.

How do you get the location? It does not work here on Firefox on test.loklak.net. Please provide a link to live system with your changes.
How can the user correct the location if necessary like with twitter?

Please adjust the design closer to twitter

[ ] use twitter button as in main menu including the bird
[ ] correct the color of the buttons to blend in (like twitter)
[ ] change "post tweet" to "Compose new Tweet"
[ ] all buttons should have the same color
[ ] the blue fonts of your buttons should use the same blue color as the buttons in the top navigation bar
[ ] the 140 character count should blend in with a grey color and turn red when it gets to the end just like twitter
[ ] offer drop down menu as twitter and on the bottom "Turn off location"


Try running a sync automatically

absolutely no clue if this works, but it happens after the zulip message, so worst case we'll see the failure after the cron job did everything it currently does.

@bors r=RalfJung

:pushpin: Commit b55b7bc13f9d8e792a1d30046d510760056abf9f has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit b55b7bc13f9d8e792a1d30046d510760056abf9f with merge 59898f18fa1da587599fb1aed74d9ade94406367...


AUTH_KEY

Hi guys, how can I find AUTH_KEY in my firebase console?
thanks

Same issue here

i'm trying and i can't connect to firestore but after so long i got it with realtime database.
To connect in realtime go to menu

copy the all url

To find auth_url go to project settings

services account

database secrets and copy the secret

Its work to connect in the realtime but I still can not the firestore database

i'm trying and i can't connect to firestore but after so long i got it with realtime database. To connect in realtime go to menu
copy the all url
To find auth_url go to project settings
services account
database secrets and copy the secret

Its work to connect in the realtime but I still can not the firestore database

do you resolve this problems?


set helm with --client-only

i need to move helm to another server, so i follow a tutorial on how to setup helm with --client-only
and i ve read the helm doc as well.  :(
however when i run helm ls --tls  i get after few minutes  Error: context deadline exceeded  even if i export HELM_HOST=10.109.0.xx:44134
how can i say to my helm you must to connect to this till 10.109.0.xx ?
helm version : SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", tiller version : SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710",

Hi @zyriuse75
HELM_HOST is typically used for local development but should work if Tiller is actually available at that IP and port. Helm uses your .kube/config to reach the API server so make sure that kubectl is working too. You shouldn't really have to worry about Tiller location as the client should be using the API server for communication afaik.

thanks for the advice .
Do i've to setup kubectl on the second server ?

i've setup kubectl on my server and as well i copy the .kube/config
if i try to get some information with the api it's fine
`curl -k https://chgvas99:6443/api/v1/namespaces
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
}, `
however if i try with
helm ls --tls --host=10.109.0.XX --tls-cert .helm/cert.pem --tls-key .helm/key.pem  --debug
i get  Error: context deadline exceeded

it's work !!
thanks for your help


can't construct gradient of gradient

In general, I've had no trouble constructing the gradient of a gradient in Tensorflow, but I hit on a weird edge case involving complex numbers where I couldn't.  Below, I show a case where the double gradient works, and one that is minimally different where it doesn't.
Here's where double gradient works:
x = tf.Variable(tf.zeros([10]))
xx = x * x
g = tf.gradients(tf.reduce_sum(xx), x)
h = tf.gradients(tf.reduce_sum(g), x)

As expected, evaluating h produces:
>>> sess.run(h, feed_dict={x:10*[1.]})
[array([ 2.,  2.,  2.,  2.,  2.,  2.,  2.,  2.,  2.,  2.], dtype=float32)]

Here's where double gradient doesn't work:
x = tf.Variable(tf.zeros([10]))
xx = tf.real(tf.complex(x*x, tf.zeros([10])))
g = tf.gradients(tf.reduce_sum(xx), x)
h = tf.gradients(tf.reduce_sum(g), x)

Running the last line gives:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/gradients.py", line 494, in gradients
    in_grad.set_shape(t_in.get_shape())
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 404, in set_shape
    self._shape = self._shape.merge_with(shape)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/tensor_shape.py", line 570, in merge_with
    (self, other))
ValueError: Shapes (10,) and () are not compatible

I'm running version 0.9.0, CPU only, in OS X.

@girving Can you take a look?

In the complex case h = tf.gradients(tf.reduce_sum(g), x) is trying to take the gradient of 2 reals w.r.t. 10 reals, which TensorFlow doesn't support.  We only support gradients of single real scalars.  I believe h = tf.gradients(tf.real(tf.reduce_sum(g)), x) should work fine.

@girving, xx is a tensor of reals, so g is a gradient of a real w.r.t. reals.  Supporting this is the fact that the expression tf.real(tf.reduce_sum(g)) produces the following error:
>>> tf.real(tf.reduce_sum(g))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/math_ops.py", line 398, in real
    return gen_math_ops.real(input, Tout=input.dtype.real_dtype, name=name)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/gen_math_ops.py", line 1516, in real
    result = _op_def_lib.apply_op("Real", input=input, Tout=Tout, name=name)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 530, in apply_op
    _Attr(op_def, input_arg.type_attr))
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 61, in _SatisfiesTypeConstraint
    ", ".join(dtypes.as_dtype(x).name for x in allowed_list)))
TypeError: DataType float32 for attr 'T' not in list of allowed values: complex64, complex128

Whoops, you're right.  Apologies for misreading.

Assigning to @mrry to take a look, although he's currently out.

I think this was fixed by 946f515, which doesn't appear to be included in r0.9. It doesn't reproduce for me at HEAD, but it does with the 0.9 binary. Can you try upgrading to a nightly (or to the imminent r0.10rc0) and see if this is still a problem?

I'm going to assume this is fixed now, and close the issue. Feel free to reopen if the problem persists!


Fix adminSide

Hi again!
I've tweaked a little bit the adminSide pages.
In the login of the staff, I have included a validation to check if the staff is already logged in (checks if $_SESSION['logged_account_id']). If so every time someone visits the staff login page, it will redirect back to pos-panel.php.
In the posBackEnd, I have included a new file required in the panels pages called checkIfLoggedIn.php where it checks if $_SESSION['logged_account_id'] is not set, if so staff must log-in to access the dashboard.

Thank you for fixing the validation issues!!


[Bug Report] Obsolete Tag 1.0

Hello!
There is a tag without a release attached:  1.0.  This tag seems to originate from a pre-release which is not published as such, yet.  As there is another tag with an almost identical name, 1.0.0, I would like to suggest to either delete the 1.0 tag or to rename it such that an appropriate pre-release according to the Semantic Versioning-like conventions this project adheres to can be build from it.

Maintainers visiting https://github.com/Gladys-Magni/Magni/releases/tag/1.0 are allowed to click the "Delete" button on the top right corner of the tag description; this is the easiest way to delete the tag directly on the website.
@Ranplax


can't stop interactive renderer if left on and start a new scene

Noticed this as well:

Take default scene (using it for example)
Switch to render man
click the start interactive button in blender
close the IT window (optional, don't think it will change the out come, but what I was doing)
do NOT stop the interactive renderer in Blender
Start a new project
Switch to renderman
Notice that it still asks you stop the interactive renderer, if you click it you get the error below.

I have to close Blender for this to go away.
Traceback (most recent call last):
File "/Applications/Blender/blender.app/Contents/Resources/2.75/scripts/addons/PRMan-for-Blender-master/operators.py", line 142, in invoke
bpy.app.handlers.scene_update_post.remove(engine.ipr.issue_transform_edits)
ValueError: list.remove(x): x not in list
location: :-1
Traceback (most recent call last):
File "/Applications/Blender/blender.app/Contents/Resources/2.75/scripts/addons/PRMan-for-Blender-master/operators.py", line 141, in invoke
bpy.types.SpaceView3D.draw_handler_remove(engine.ipr_handle, 'WINDOW')
ValueError: callback_remove(handle): NULL handle given, invalid or already removed
location: :-1
Blender (hash): c27589e
Renderman: 20.1 and renderman for maya 2016 I think.
PRman: 92933cfd4f

Fixed.


Incorrect error in wrangler.toml

Cloudflare recently add new capability to configure Pages in the wrangler.toml file, one of the new properties is pages_build_output_dir. However the extension is reporting it as error. Please refer to Cloudflare's doc

Errors are based on the available schemas which are provided by SchemaStore. Since Cloudflare maintains their own schema, they have to update it.

For those who find this issue, a temporary workaround is to disable schema validation with: "evenBetterToml.schema.enabled": false
Not sure if there is a way to disable schema validation for specific files.


blog post

in no specific order yet
just my notes

[ ] HelpOut
[ ] RenameHelper
[ ] New Commands
[ ] Change command names
[ ] Confirmation of what works (win7/2000/azure,etc)
[ ] Azure Support Details
[ ] Book info
[ ] GitHub Sponsorship

@ClaudioESSilva - any suggestions?

gonna close cuz i got my outline


Add Gan-introduction to deep-learning

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] local build the book
[ ] review the artifacts from local build
[ ] local build the slides if appliable
[ ] Unit test if appliable

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have applied tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

It is pretty good, but still has some problems to be solved 👍

plz clear out all outputs
plz  add Acknowledge part, you can refer to others' files


Document external dependencies for COS lite

Bug Description
We need a list of external dependencies needed to have COS installed and working correctly.
This is mostly needed to communicate to customer how to configure proxy/firewall to allow COS setup.
Ideally this should include also dependencies that are not directly from components in the cos-lite bundle, but still they are core ones of a COS deployment like grafana-agent.
To Reproduce
Not applicable
Environment
Not applicable
Relevant log output
Not applicable

Additional context
No response

We have one customer reporting grafana-agent trying to talk with Google Cloud and we are unsure what this traffic is for.

I'm not exactly sure what you mean by external dependencies. As far as I can tell the answer is none. Can you give an example?
Note: For grafana-agent talking to google cloud, we expect that it is sending some telemetry home and we are looking in to it.

We should add a juju config toggle to allow opting out from sending telemetry, with the default being to send it.

Documentation will need to include egress requirements for things like:

Charmhub
Dockerhub
Juju registry
Snapcraft
Github (Promtail?)

The dependencies have been documented, both in the individual charms, and summarized here.


Harmonized line length style, spell-checked README

[x] I am the original author of this code and I am willing to release it under Unlicense

[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

[x] Improvement

I've made the line length more consistent (by 'un-blocking' a paragraph)

I've made minor changes to the help text of some options (and also changed them in the options.py file).

As part of 24pullrequests.com

It will overwrite on the next release. There is no point changing options in README manually.

Great!
I’ve learned something today :)


Configure GitLFS

While it will most likely not been an issue for this project it still would be good to get GitLFS configured for this repo and provide the necessary documentation for anybody to set it up (aka. write it down so I don't have to remember it).

There are some hints for this in the docs here: https://docs.godotengine.org/en/stable/tutorials/best_practices/version_control_systems.html


Unloading

I've added the possibility to "unload" the konami code.
Ps: In the documentation, there is no reference to that. The npm version of konami-js is not up to date, so while the PR is not merged you can use : npm install fberthelot.konami-code.js

This looks great to me. I'll merge and make sure the NPM version gets updated as well


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.6",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8984bba3b4c0b36be6cbcd7ac4a8779a045bd670"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "8984bba3b4c0b36be6cbcd7ac4a8779a045bd670",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "f2fs: set SBI_NEED_FSCK flag when inconsistent node block found\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.6 by commit 8984bba3b4c0b36be6cbcd7ac4a8779a045bd670. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002548


Use llvmPackages_7 explicitly for ccls

llvmPackages_latest picks too old LLVM for ccls on macOS. Which breaks
the build.
Motivation for this change
For some reason after merging https://github.com/NixOS/nixpkgs/pull/56673 llvmPackages_latest behaviour has changed. Instead of using the actual latest version on macOS, it uses a version that has Clang 5.x which is too old for ccls.
Things done

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

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Out of interest, what does
$ nix eval '(with import <nixpkgs> {}; llvmPackages_latest.llvm.name)'

return on your machine?

Out of interest, what does
$ nix eval '(with import <nixpkgs> {}; llvmPackages_latest.llvm.name)'

return on your machine?

"llvm-8.0.0rc2" so it actually finds 8. So I guess you are correct above that the problem is with 8. So forcing to 7 is accidentally the right solution to this I guess.


请问能否公开训练代码？

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Update to fuzzcheck 0.9

Good morning 👋
I have just released fuzzcheck 0.9.0 and thought I'd update the dependency for you. Here's what changed:

The grammar for the parser now uses functions instead of macros. There is also a new regex(..) function which makes the grammar easier to write.
The result of fuzzcheck::fuzz_test(..)....launch() is not ignored anymore
The syntax for cargo-fuzzcheck changed a bit.
This is more of an opinion than a rule, but I think it's nice to keep the defaults for the artefacts instead of using a custom folder, especially if the same folder is used to save artefacts of different types.
About the folders created by fuzzcheck, they have changed names, again. Sorry about that. Some day I'll stop being so indecisive, but not today :)

Also, I noticed that running cargo-fuzzcheck on the root of the workspace doesn't work. Instead, you have to cd into logic and then run cargo-fuzzcheck there. I'll try and figure out a way to make it work and to add nice errors for that in a later release.
I hope it works, and don't feel any pressure to merge it, this is mostly to save you some of the boring work of refactoring the previous grammar API to the current one.
You can always ask me if you have any questions/problems. The guide and docs are also a bit better now. And I checked the fuzzcheck-view tool on this repo, and it seems to work okay. Give it a try if you feel like it :)
I hope you're doing well! Cheers.

Sorry for the delay in getting back to you!
Thanks so much for this commit – I think the new grammar mutator API is a substantial improvement over the previous one (which was already really good).

About the folders created by fuzzcheck, they have changed names, again. Sorry about that. Some day I'll stop being so indecisive, but not today :)

Sorry for the delay in getting back to you!
Thanks so much for this commit – I think the new grammar mutator API is a substantial improvement over the previous one (which was already really good).

About the folders created by fuzzcheck, they have changed names, again. Sorry about that. Some day I'll stop being so indecisive, but not today :)

No worries!

The guide and docs are also a bit better now.

no worries! glad you like it :)


Add conversions from SwapCommitment to tct::Commitment

After #1713, we'll want to implement conversions from SwapCommitment to tct::Commitment, similar to the ones for note::Commitment, so we can insert swap commitments into the TCT.

Closing in favor of using the tct::Commitment type directly for swaps, see https://github.com/penumbra-zone/penumbra/pull/1723#issuecomment-1343242889.


🐕  Fix husky configuration

To enable husky you have to run yarn install once. There is a prepare step which will set it up.
Important: This works only for yarn < v2. For yarn v2 we need to do some changes

I guess we want the same for backend then as well?


The Json format of the log file is damaged

Please check the json format of the log of sparse4d v2 with backbone resnet50 as it seems damaged, can you upload a correct one? Thanks.

https://github.com/linxuewu/Sparse4D/releases/download/v0.0/sparse4dv2_r50_HInf_256x704.log.json

This link can be opened on my end.

Hi @linxuewu Thanks for your prompt reply, I tried to parse your json content with the tool http://json.parser.online.fr while failed again (SyntaxError: Unexpected non-whitespace character after JSON at position 19113 (line 2 column 1)), can you also have a try?

Each line in the file is one JSON object. Therefore, direct JSON parsing is not feasible.
[json.loads(x) for x in open("file_path").read().strip().split("\n")]
You only need to open it with any text reader. The first line contains configuration, while the lines below contain losses.

@linxuewu Hi, I wrote a program to parse your json file with env & config parts as below
sparse4dv2_r50_HInf_256x704.log, while I found there exists some difference between your log and given config & requirements file, e.g., mmdete3d version and some config parameters. Actually, I failed to reproduce your mAP with your given config and requirements.txt, so will it caused by those difference? Thanks.

The mmdet3d version needs to be >=1.0.0rc. Besides mmdet3d, are there any other parameters that are different? Also, how much difference is there in the reproduced metrics? @linxuewu

And, to reproduce sparse4dv2, you can search in the previous repository to see if there are similar issues that can be referenced.

Thanks @linxuewu, I can reproduce your v2 results now. Also, I believe the batch_size might be one of important factors and may cause 10-points fluctuation in dist_train.

10-point descent, did NaN occur during training?

Thanks @linxuewu, I can reproduce your v2 results now. Also, I believe the batch_size might be one of important factors and may cause 10-points fluctuation in dist_train.


jest-enzyme + typescript: non-string selectors are rejected

This is a valid code in JS:
const DummyComponent = () => <div />;
expect(wrapper).toContainMatchingElement(DummyComponent)

However, typescript rejects it:
Argument of type '() => Element' is not assignable to parameter of type 'string'.

Enzyme's own type definitions contain a much more flexible signature for selectors, where jest-enzyme defines only string selectors.
One possible workaround is rewriting original assertion to:
expect(wrapper.find(DummyComponent)).toExist();

but would be nice if the original code was accepted as is.

Although the provided example indeed solves that specific use-case, forcing the type of the other matchers to accept only string as input imposes several limitations for no real reason, which makes it impossible to achieve assertions that - without types - work just fine (meaning: the implementation surely seems to support it):
// Assert the number of instances of certain component
expect(wrapper).toContainMatchingElements(3, DummyComponent);

// Assert any component with certain prop
expect(wrapper).toContainMatchingElements({someProp: 'someValue'});

I'm not quite sure why assertion of a library that deals explicitly with matches for React should even mention React in it's function name :/
What caused the types to declared in such a way when no alternatives are provided for the usage of the matchers (and their usage) listed above? Wouldn't it make more sense to introduce types that match with current usage and then split the functions in the future when there's really a need for it?


IgnoreSslValidation Switch

I'm having difficulty establishing an SSL connection to an RMQ that is using a self-signed certificate.  Is there a way to disable SSL validation for troubleshooting purposes?  The following command works:
$c = New-RabbitMqConnectionFactory -ComputerName <IP_ADDRESS> -Port 5672 -vhost vhost1 -Credential $CredRabbit -Verbose -Ssl None
But the following command fails with a Broker error.  Port 5671 AMQPS is confirmed working using TLS 1.2.
$c = New-RabbitMqConnectionFactory -ComputerName <IP_ADDRESS> -Port 5671 -vhost vhost1 -Credential $CredRabbit -Verbose -Ssl Tls12
Exception calling "Invoke" with "5" argument(s): "None of the specified endpoints were reachable"
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSRabbitMQ\New-RabbitMqConnectionFactory.ps1:119 char:9
+         $CreateConnectionMethod.Invoke($Factory, "instance,public", $ ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : BrokerUnreachableException

Hiyo!  Missed this - you might consider something like this, keeping in mind the duration of that PowerShell session won't validate certs after that.
Closing this out for now, but if you still run into the issue, feel free to re-open
Cheers!


Deterministic, reproducible builds?

We've successfully used clue/phar-composer in a small (closed source) PHP library. Thank you so much for this awesome tool! 👏 🙏 🥳
That being said, we've really struggled in figuring out what is causing it to generate a different binary every time, even when keeping everything identical.
https://bugs.php.net/bug.php?id=77229&edit=1 pointed me to this probably being a problem with phar itself. But not even using the same approach as composer uses with https://github.com/Seldaek/phar-utils appears to work.
What am I missing? 🤓
See https://reproducible-builds.org/

@wimleers Thanks for reporting, I too am a big fan of reproducible builds :+1:
Have you checked how exactly the archives differ? Might be some timestamps or possibly some duplicate contents (#100). If anybody wants to pick this up, I'm happy to accept PRs! :shipit:
As much as I'd love to work on this myself, there are currently no immediate plans to build this from my end (no demand at the moment and more important outstanding issues currently). If you need this for a commercial project and you want to help sponsor this feature, feel free to reach out and I'm happy to take a look.

I'm closing this for now as it hasn't received any input in a while and I believe this has been answered. If you feel this is still relevant, please come back with more details and we can always reopen this :+1:


Locally, but exported, constants hurt minification (a little)

Came across the const below and its siblings: https://github.com/microsoft/vscode/blob/2d7aacfa927dde260b6602f5fd45ff14d99c76d6/src/vs/workbench/browser/parts/notifications/notificationsCommands.ts#L21
These are super long variable names which are exported but only used locally (inside the declaring file). This hurts minification because the export prevents its name from being shortened.

That would be a nice ESLint rule to have.


TableViewDragger.swift:279:18: 'dynamic' instance method 'panGestureAction' must also be '@objc'

Build error after installing  TableViewDragger

Hi @rajeshbeats
What's version of Library did you use? It looks old. Please, should use the latest version.

@KyoheiG3 I forget the version I used, but yea it is fixed when i updated the pods.
Thank you.


feat(client): use showPoints to hide points instead of mutating the points

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

After aligning the types, and removing the mutation of point to null, we can start using ShowPoints as a boolean to show the element, instead of changing the value of points, which isn't what point are.

I am pushing this into draft, until this PR #49956 is approved

Handling plurals correctly is a nightmare because in Arabic 2 isn't plural but a pair which is a different state of plural, and we would have to account for that as well.
I have used the text from https://github.com/freeCodeCamp/freeCodeCamp/issues/48234, it should be translated correctly, and it won't be grammerly wrong. here is the text Number of points: {{count}}

Fair point: it's probably overkill for this, but https://www.i18next.com/translation-function/plurals#languages-with-multiple-plurals exists. It talks about Arabic, so it might be useful at some point.
Anyways, back on topic: could you add a couple of simple tests for how this displays (or doesn't display) the points?


License.md is missing?

Please add a License.md file to the root.
A Readme.md would also be nice!

True! I just added a license file and some simple instructions in a readme


added most loved products section

Pull Request Format
PR Title added most loved products section
Issue #684 : ISSUE NAME solved
Type of PR

Add X in the box to specify the improvement type.
[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): ___________

Description
add a section for most bought and loved by people products section in the webpage just under the list of all products for sale
Screenshots / Videos (if applicable)
Before:
NA
After:

Checklist

Add X in the box to specify.
[X] I have performed a self-review of my code.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Additional Context
NA
Thank you for reviewing my pull request!

@swaraj-das pls check my pr


Problem using this module as it haveeval statements

I am using this module for my javascript libraries to render them browsers. One of the problems that I observed is that this module uses eval functions. I want to avoid eval altogether while executing my libraries on the browser.
I see you recommended options for extensions using target config. Can I safely use this and render the obfuscated code on the browsers? If not, what could be the problems that I can get?
Is it possible to avoid eval statements altogether for other environments as well?

Use target: 'extension'
In 0.15.0 i'll rename extension on browser-no-eval

Renamed target option value from extension on browser-no-eval now in master branch.

<EMAIL_ADDRESS>just published to the npm!


Why should uvcvideo be a module (rather than a built-in)?

My question is not specific to a sensor, but rather the library itself (thus I'm not including the device/model tags at the top of my question).
I noticed that the latest SDK release for NVIDIA Jetson TX1/TX2 boards (which was released only a few days ago) uses kernel v4.4 and the sources already contain the necessary patches for RealSense video formats, etc.
Right out of the box, I noticed that upon connecting my R200 to my Jetson TX1 board, dmesg indicated that the connected camera was correctly recognized:

Found UVC 1.10 device Intel RealSense 3D Camera R200

I could also confirm that uvcvideo was already available as a builtin. I proceeded with building the latest librealsense source. However, I noticed that upon trying to run any of the samples I would get:

uvcvideo kernel module is not loaded

I went ahead and built the kernel from the sources, from scratch. Except for forcing uvcvideo to be built as a module, I did not touch any of the other settings. Now the camera and the samples work fine without any issues.

Hi @Maghoumi
To the best of my knowledge there is no such limitation. When the pixel-formats are included in the Kernel, RealSense cameras function just like any other V4L2 streaming device.
When you were using the built-in drivers, did you notice anything unusual in dmesg when connecting the device? Was the device visible in lsusb | grep 8086 output? Was it connected to the USB3 port in the same way (using same hub and cables)?

I just recalled we have the following check in the V4L2 backend:
uvc-v4l2.cpp#L728-L744
This is a legacy precaution that does not contribute to normal operation of the library. We have tested internal releases of the library without it, so it can be safely removed.

@dorodnic Thanks.
I removed those lines and I can confirm that R200 works out of the box on a Jetson TX1 that's is newly flashed with Jetpack v3.1. For some reason, I didn't think of going into the code to see where that error message "uvcvideo kernel module is not loaded" was being thrown.
I'm guessing you'll be replacing those checks with something that can also check for builtin modules?

Actually, internal RS400-version of librealsense works just fine without such checks at all. The team has added a lot of extra checks into the public patching scripts / DKMS, with the ultimate goal of working on upstream kernels. A more practical way to double check that the kernel indeed supports RealSense is querying supported formats using ioctl(_fd, VIDIOC_ENUM_FMT, &pixel_format) and examining the resulting pixel_format.
If you would like, you are welcomed to submit a change (see CONTRIBUTING.md), it can save time for future TX1 users.
Take into account that librealsense is not optimized for Jetson. I just got one recently. There might be existing issues. Please share your experience.

@dorodnic Thanks for letting me know. Sounds good, I will look into that when I have time and (hopefully) submit a pull request with the necessary changes.
I've been a long time RealSense + TX1 user (as discussed here). I've never faced any issues with my R200 on TX1. The performance is mostly good.
As a matter of fact, for a personal project, I made small changes to probe for CUDA and if available, use CUDA forYUY2 to RGB conversion. The reason I did that was because I noticed the CPU-based conversion in the absence of SSSE3 was causing a bottleneck on TX1 with my particular application. That implementation is available in a fork I created a while back. I didn't know if you guys had any interest to support CUDA if available on the target machine, so I never bothered creating a proper pull request.
If there's any interest in that, I may work on adding proper support for CUDA as well.

We've completely removed the section since checking the presence of uvcmodule was found ineffective, and also introduced additional constrain on the kernel configuration.
We've also experimented with an alternative approach, but eventually it was abandoned as well in favor of removing the test altogether.


Parse {{syn}} and {{ant}} templates

Refs #2

Codecov Report

Merging #42 into master will decrease coverage by 0.09%.
The diff coverage is 16.66%.

@@           Coverage Diff            @@
##           master     #42     +/-   ##
========================================
- Coverage    59.9%   59.8%   -0.1%
========================================
  Files         166     166
  Lines       10611   10638     +27
  Branches     1672    1677      +5
========================================
+ Hits         6356    6362      +6
- Misses       3861    3881     +20
- Partials      394     395      +1

Impacted Files
Coverage Δ

...ukp/jwktl/parser/en/components/ENSenseHandler.java
58.27% <0%> (-10.38%)
:x:

...t/ukp/jwktl/parser/en/components/EnGlossEntry.java
71.87% <100%> (+6.49%)
:white_check_mark:

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 7187413...174d91c. Read the comment docs.


Remove examples folder

Using gvt (and presumably other tools that support automatic recursive dependency vendoring) leads to a bunch of dependencies being unnecessarily added when vendoring nosurf.
$ gvt fetch github.com/justinas/nosurf
2016/05/23 19:44:37 fetching recursive dependency github.com/hoisie/web
2016/05/23 19:44:41 fetching recursive dependency github.com/zenazn/goji
2016/05/23 19:44:46 fetching recursive dependency golang.org/x/net/websocket

It looks like this is because of the examples folder being in the main repository.
Renaming the examples directory to _examples would fix this for users of gvt. I'm unsure about other vendoring tools.
My gut feeling is it would be cleaner and safer to move these examples out of the main repository (where they're not actually needed) though. Perhaps to gists and referencing them from the readme instead? I'm happy to do that and send a PR.

Removed the examples for now, will consider re-adding them to Wiki. Updates to the examples are much needed anyway.

Using gvt (and presumably other tools that support automatic recursive dependency vendoring) leads to a bunch of dependencies being unnecessarily added when vendoring nosurf.

Should the dependency vendoring tools figure out which dependencies are actually used/needed (e.g., github.com/justinas/nosurf) and which ones are not (e.g., github.com/justinas/nosurf/examples), and only vendor those?


Issues while installing Opendistro on Debian

I used the installation guidelines on [https://opendistro.github.io/for-elasticsearch-docs/docs/install/deb/]
After typing "sudo apt install opendistroforelasticsearch", I get the following error.
Basedir: /usr/share/elasticsearch
This script maybe require your root password for 'sudo' privileges

Unable to determine Elasticsearch config directory. Quit.
dpkg: error processing package opendistro-security (--configure):
subprocess installed post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of opendistroforelasticsearch:
opendistroforelasticsearch depends on opendistro-security (>= <IP_ADDRESS>); however:
Package opendistro-security is not configured yet.
opendistroforelasticsearch depends on opendistro-security (<< <IP_ADDRESS>); however:
Package opendistro-security is not configured yet.
dpkg: error processing package opendistroforelasticsearch(--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
opendistro-security
opendistroforelasticsearch

Pls help

I did a fresh Install and realized there was some issue in Elasticsearch installation itself.
Now things are working fine thanks for your help.


Copy new development target

In GitLab by @jakebeal on Feb 1, 2019, 20:50
Our first target sheet for for development and testing will be the novel chassis titration experimental request
https://docs.google.com/document/d/1oMC5VM3XcFn6zscxLKLUe4U-TXbBsz8H6OQwHal1h4g/edit#
This is different than the one we did the proof-of-concept with: it's an experiment just about to get started, so if we make progress with it, there will be an immediate positive effect on the whole project.
It needs to be copied and placed in a development & testing location.
@jakebeal will identify additional sheets for cross-domain testing.

In GitLab by @jakebeal on Feb 1, 2019, 20:50
changed the description

In GitLab by @jakebeal on Mar 12, 2019, 10:42
This is in addition to the first one, not necessarily replacing it.

In GitLab by @jakebeal on Mar 12, 2019, 16:13
Three more new targets from #3, making our full collection:
Yeast States:

https://docs.google.com/document/d/1nDKQmrNooD9Fg3aW70cd6dVZqGKkApAo8-XYdGWhPtk/edit#
https://docs.google.com/document/d/1QgikpIsaPp2A3EIaWc4lFPv-hAsjheRw5dlvCgsFuUA/edit

Novel Chassis:

https://docs.google.com/document/d/13QqYqzp4bBXMCHFiX2PNqrYOL0iegXk1hBgEcAeQ4BI/edit
https://docs.google.com/document/d/1oMC5VM3XcFn6zscxLKLUe4U-TXbBsz8H6OQwHal1h4g/edit#

If we can handle these, we are probably in good shape generally.

In GitLab by @jakebeal on May 7, 2019, 11:06
overtaken by events: we're just going to do a live beta, since things look like they're working nicely.

In GitLab by @jakebeal on May 7, 2019, 11:06
closed


Adjustable Outdates for All Past Dates

For my project, a booking application, the user can only select today's date, or dates in the present. Is there a way to adjust the outdates in order to make them encompass all days before the present? And on a further note, can the outdates be made unselectable UIViews?

ok. Lets talk here. I do not understand what you mean -> https://gitter.im/patchthecode/JTAppleCalendar

Basically, Outdates are fixed.
Outdates are based on what you find on a real calendar. These cannot be adjusted.
If you are trying to prevent dates from being selected, then have you looked at the tutorial here-> https://patchthecode.github.io/DateCellConfiguration/
The main tutorial page is here -> https://patchthecode.github.io/

Basically my goal was to change all of the dates before the current date to unselectable dates, in order to prevent the customer from booking in the past. I did this by changing these two functions, just thought posting this might make a possible alternative easier for someone trying to do it in the future.
`
func configureTextColor(_ cellState: CellState) {
if cellState.isSelected {
dayLabel.textColor = textSelectedColor
} else if cellState.date.timeIntervalSince1970 < Calendar.current.startOfDay(for: Date()).timeIntervalSince1970
{
dayLabel.textColor = unSelectableColor
}
else
if cellState.dateBelongsTo != .thisMonth
{
dayLabel.textColor = previousMonthTextColor
} else {
dayLabel.textColor = textDeselectedColor
}
}
`
and
func calendar(_ calendar: JTAppleCalendarView, willDisplayCell cell: JTAppleDayCellView, date: Date, cellState: CellState) {         (cell as? CellView)?.setupCellBeforeDisplay(cellState, date: date)         if date.timeIntervalSince1970 >= Calendar.current.startOfDay(for: Date()).timeIntervalSince1970{             cell.isUserInteractionEnabled = true         } else {             cell.isUserInteractionEnabled = false         }     }

@aparkerryan27 this is exactly the way to do it.
Just compare the date. And if it is a date that you want disabled, then cell.isUserInteractionEnabled = false will do the trick.

Or handle it at didSelectDate delegate, like so:
`    func calendar(_ calendar: JTAppleCalendarView, didSelectDate date: Date, cell: JTAppleDayCellView?, cellState: CellState) {
    // Won't let dates before current date be selected

    let currentDate = Date()
    let formattedCurrentDateString = formatter.string(from: currentDate)
    let startDate = formatter.date(from: formattedCurrentDateString)!

    if date <= startDate {
        return
    }

    handleCellSelection(view: cell, cellState: cellState)
    handleCellTextColor(view: cell, cellState: cellState)

    print(formatter.string(from: date))
}

`

@glennposadas Its been some time since i last answered this question.
I think another way to handle this is by using the the following delegate function:
func calendar(_ calendar: JTAppleCalendarView, shouldSelectDate date: Date, cell: JTAppleDayCellView, cellState: CellState)

Hi @patchthecode , just experienced a bug in my code above. I managed to select a date past the current date. yikes. So I copied my implementation to the delegate function you gave. Will edit my code above.


increase test coverage for CoTS

Carl's #62 has added CoTS support. Test coverage is below the current threshold and therefore cannot be merged directly into main.
This issue tracks the development of additional tests in the CoTS area.

Done in https://github.com/veraison/corim/pull/64


Fix: yaml source workdir relying on scm

Signed-off-by: Olblak<EMAIL_ADDRESS>Spot while testing https://github.com/updatecli/updatecli/pull/838
This appears to be a regression where the source yaml didn't use the correct scmID

Test
To test this pull request, you can run the following commands:
go build -o bin/updatecli .
./bin/updatecli diff --config e2e/updatecli.d/success.d/githubPullrequest.yaml

Additional Information
Tradeoff
/
Potential improvement
This part should deserve better UT, but I don't really have the time atm

Oh! I'm wondering if it's not the same type of bug I've got in my pending PR...

Oh! I'm wondering if it's not the same type of bug I've got in my pending PR...

Which one? I am curious about this bug because I am pretty sure we use this workflow but can't remember where

https://github.com/updatecli/updatecli/pull/650
I'm struggling to debug e2e tests, but I think the errors I'm encountering could be related to this workdir.

well try.gitea.io seems to be dead.
I'll switch to codeberg when I have some time but for now I am gonna merge this PR and trigger a release


Add task + framework env vars into Dry Run Summary

Description
This PR adds an environmentVariables key into Dry Run Summaries. The data is broken down by the source (configured, and inferred), so it's easy to see how where it's coming from.  This PR does not include global env vars, but that will likely follow the same pattern.
Stacked PRs:

https://github.com/vercel/turbo/pull/4016
https://github.com/vercel/turbo/pull/4021
https://github.com/vercel/turbo/pull/4020 (this one)

Testing Instructions
The test cases should cover most cases, but we should run against examples also

[X] Auto label

Note to self and other reviewers: the changing hashes for the tests in basic_monorepo are expected because turbo.json was updated.


Populate table of contents with remaining subsection entries.

Subj. — :point_up:

She looks great ! :+1:


Pattern Problems

Printing the diagonal and sides of a Rhombus/Diamond
Printing Left and Right Arrows
Printing a solid and hollow Rhombus

@aritra-tech please assign me this issue.

Sure


No such file or directory: '../dataset/SHREC2017/train_gestures.txt'

Hello, I encountered this problem while running the code. I would like to ask how to obtain this train_gestures.txt file, it seems that it is not in the downloaded code file.

Hi, @ceb-jjgf ,
The train_gesture.txt is the input list of SHREC'17 dataset, you can download this datase from the website: SHREC.  Each line follow the following pattern:
id_gesture     id_finger    id_subject    id_essai    14_labels    28_labels    size_sequence


Add Webpack CSS/SASS/Style Loaders

Add the CSS Loader for Webpack.
Look at using import<EMAIL_ADDRESS>

Adds support for CSS, SASS and LESS loaders.
Use .global.(css|scss|sass|less) for global classes or .(css|scss|sass|less) for CSS modules.
Also, updates the login page to use Polaris instead the page from the Shopify Rails App gem


Generate one-way serializers for Compose protocol

This:

Eliminates allocation of surrogate instance
Dramatically reduces generated code by only including serialization half

For the Emoji Search JS module dedicated to Compose protocol serialization:
62040  before.js
44221  after.js

A 29% reduction in size.
Closes #714, but more size savings to come!

Before QuickJS bytecode: 29549
After QuickJS bytecode: 23658 (20% reduction)

Looking


Refactor lazy_regrid.py for wflow diagnostics

The recipe wflow.yml returns memory error if it uses e.g. 10 years of data. The diagnostics wflow.py uses regrid function with scheme area_weighted.  The memory error is explained in an open issue in SciTools/iris/issues/3808 .
With the new version of iris, the lazy_regrid script benefits from a refactoring. Note that the regrid preprocessor cannot be moved to the recipe because the format of wflow target grid file is .map.

Comparing the performance of wflow_recipe regarding refactoring lazy_regrid script before (wflow_master) and after (wflow_pr):

check the differences in one of the outputs wflow_ERA-Interim_Meuse_1990_2001.nc that includes three variables, as shown below, the differences are zero or very small.
check the cube shapes, they are both the same.
check the file sizes in the work directory, as can be seen below, after refactoring, the .nc and .XML files are smaller.
check the resource_usage.txt, as can be seen below, running the recipe after refactoring takes about half-hour more.

the differences in one of the outputs wflow_ERA-Interim_Meuse_1990_2001.nc
pr

tas

pet

the cube shapes

the file sizes

the resource_usage.txt
before resource_usage.txt and after resource_usage.txt

@SarahAlidoost Thanks for the nice report! What are your conclusions from this?

Ah, sorry, didn't see the conclusions, but they are there already. It's a bit worrying that there is a difference at all in the runtime and memory use. Do you think the runtimes could vary per run?

Nice comparison @SarahAlidoost ! Half an hour more on 1-1.5 hours in total is quite a big difference I'd say. I'd like to know how this is possible, but that might be out of scope for your current objective, or not?

Ah, sorry, didn't see the conclusions, but they are there already. It's a bit worrying that there is a difference at all in the runtime and memory use. Do you think the runtimes could vary per run?

with new commits, the performance is improved. Now the differences in the variable pet is zero too (see below). It seems that the runtime varies per run. Now, it took less than one hour (see new resource_usage.txt).
the differences in one of the outputs wflow_ERA-Interim_Meuse_1990_2001.nc
pet

Nice comparison @SarahAlidoost ! Half an hour more on 1-1.5 hours in total is quite a big difference I'd say. I'd like to know how this is possible, but that might be out of scope for your current objective, or not?

please see my comment here.

It seems that the runtime varies per run. Now, it took less than one hour

OK, that's good news, because the implementation I did in iris is almost identical, I would expect it to be very slightly more efficient, to what was here in ESMValTool. Therefore it would have been strange if there were big differences in runtime. Maybe the difference in runtime/memory use is because not all the nodes have the same hardware (assuming you're running on Cartesius: https://userinfo.surfsara.nl/systems/cartesius/usage/batch-usage#heading7) or because of other users also accessing the shared file system.


HOSTEDCP-1716: When running the HO locally it should no required a running pod

What this PR does / why we need it:
This PR covers the steps to run the HyperShift Operator locally without needing access to a full production environment.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #HOSTEDCP-1716
Checklist

[ ] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[x] This change includes docs.
[ ] This change includes unit tests.

/ok-to-test

@marcbrown2024 thanks for the contributions! I would suggest a slightly different track:

running a binary locally gives some useful input to the validity of the operator, but does not give signal on the associated requirements for the deployment
helpful guides in Markdown go stale faster than we can keep up with them

In test/integration an automated process already exists for spinning up a kind cluster on your machine and using your local content to run the HyperShift components in the management plane. I'd love to collaborate with you to make sure that the approach for the integration tests works for your use-cases.  I think such an approach will prove to be more holistic in what it helps us verify locally and more durable to boot.

@stevekuznetsov I think we need both, since they're for different scenarios. Running the hypershift operator locally while pointing to a fully deployed management cluster (on AWS or Azure) allows you to test/debug things that you would only see in an environment like that (say nodepool controller AWS specifics, or even the scheduler/scaler for ROSA). The integration environment lets you quickly validate other things, and is definitely useful, so we should also document it.

@csrwng the integration scripts have no requirements on what they are pointed at - why not use them to hot-replace the hypershift-operator binary running in the cluster?

I guess I'd just say - let's put some value on executable, re-usable functionality here. I think everyone doing development on HyperShift has their own assemblage of shell scripts, hack docs, whatever. It's a lot. Find some semi-reusable thing and eat the cost of it not being perfectly optimal for your specific/special use-case, and reap the benefits to collaboration and onboarding of having a common platform.

/approve

/retest

/lgtm


Handle channel events properly

Currently we do not act on the channel events, e.g. ChannelReady, ChannelClosed etc. We should update our channel state in regards to the events and update the user correspondingly.
e.g. only show that the channel is ready if we have received the ChannelReady event.

A dedicated channel view might be helpful to depict the individual channel state to the user - #338

where did you see ChannelReady event? I see only ChannelClosed, which is for "channels that are in the process of closure", so we can't really tell whether this got closed.
The way to ensure that a channel has been properly closed would be monitoring on-chain for the transactions resolving the channel.... - similar for opening a channel.

where did you see ChannelReady event? I see only ChannelClosed, which is for "channels that are in the process of closure", so we can't really tell whether this got closed. The way to ensure that a channel has been properly closed would be monitoring on-chain for the transactions resolving the channel.... - similar for opening a channel.

You can find the channel ready event on the maker side. We don't have to handle the channel events though, we could as well use the ChannelDetails is_channel_ready and is_usable. @bonomat was looking into that.

related to #485


Thank you for your submission to JetpackCompose.app

Thank you for submitting this wonderful project to JetpackCompose.app. It's now featured on the site and we really appreciate your contribution to the Android community!

Thanks for featuring it on JetpackCompose.app


Correctly get Primary Key when loading tables

When foreign keys and unique constraints were present, the primary key would be incorrect.

Excellent thank you!


Can't configure Itsybitsy m4 default SPI with sercom::v2 (new undoc ioset perhaps?)

The documentation correctly points out that:

An SPI peripheral can use up to four Pins as Sercom pads. However, only certain Pin combinations are acceptable. All Pins must be mapped to the same Sercom, and for SAMx5x chips, they must also belong to the same IoSet. This HAL makes it impossible to use invalid Pin combinations, and the Pads struct is responsible for enforcing these constraints.

The datasheet points this out too:

6.2.8 IOSET Configurations

The SAM D5x/E5x has multiple peripheral instances, mapped to different IO locations. Each peripheral IO location is called IOSET and for a given peripheral, signals from different IOSET cannot be mixed.
For a given peripheral with two pads PAD0 and PAD1:
- Valid: PAD0 and PAD1 in the same IOSETn.
- Invalid: PAD0 in IOSETx and PAD1 in IOSETy.

Yet...for the default SPI, Sercom1 is supposed to be configured using PA00, PA01 and PB23...The problem being that PA00 and PA01 are part of IOSET4 but PB23 lives in IOSET3.
Sounds like adding an equivalent to atsamd_hal::sercom::v2::pad::UndocIoSet1 could be a solution.

Type-level variant of IoSet representing an undocumented SERCOM IOSET
After implementing IoSet type checking, it became clear that some existing boards were using a combinations of pins that did not match any IOSET in the datasheet. From that, we infer that there must be at least one undocumented IOSET, and we added this new IoSet to account for it.
As of writing this documentation, only one undocumented IOSET has been discovered: PA16, PA17, PB22 & PB23 configured for Sercom1. Both the pygamer & feather_m4 uses this combination.
See the type-level enum documentation for more details on type-level variants.

Every time this happens I want to tell Microchip:


FYI: Highlight.js grammar for NestedText

I really like what you all are doing here with the idea of a dead SIMPLE spec... so I'm adding a grammar to Highlight.js:

https://github.com/highlightjs/highlight.js/pull/3114
We're in between major releases right now so it might be a while before it's released, but just thought I'd let you know.

Nice, thank you.  Be aware that we are in the throes of making an incompatible change to the language spec in an attempt to make it simpler. We plan to eliminate quoted keys and may replace them with multi-line keys. Both of these are infrequently used features.

We plan to eliminate quoted keys

Which is a good call, never even wasted a moments thought on them.

and may replace them with multi-line keys

Is this documented anywhere? Examples?

We have not settled on the syntax for a multi-line key yet, but we are close.  My best guess at the moment is that they will look like this:
: this is a multi-line key
: this is the second line of the key
    > This is the value

Interesting.  What is the use case for keys like that?  What does that evaluate to? Is there a space between "key" (1st line) and "this" (2nd)? How would it know?

That example maps to
{
    "this is a multi-line key\nthis is the second line of the key": "This is the value"
}

We do not see a compelling use case.  Adding it is more about completeness. Previously there were limitations on dictionary keys, and those limitations increased when we got rid of quoted keys.  With multiline keys there are no limitations. Any string that consists of printing characters can be a key.
You might want to take a look at this issue. It is where the idea first came up.

Oh, and if you wanted a space you would simply add it to the key. Leading and trailing spaces are retained, as are the newlines.:
: this is a multi-line key␣
:  this is the second line of the key
    > This is the value

which becomes
    "this is a multi-line key \n this is the second line of the key": "This is the value"
}

Well, that would be trivial to add if you go that route.

@KenKundert I actually think that multi-line key syntax has some nice properties (e.g. each line type still identifiable without the context of surrounding lines), which I'm sure was part of your careful deliberation. The main thing that's strange about it is that the key is appearing after a colon, making it appear like a value at first glance. It's also not based on any existing YAML syntax as far as I'm aware (multi-line strings in NT are precedent for this, but that doesn't necessarily mean adding more syntax that users are unfamiliar with is a good idea).
Anyway, I don't want to derail this issue thread - perhaps you'd consider opening an issue for discussion if you're thinking of adding this feature?


How to list pages from specific dir?

I have pages in /news directory on  semi-static website, How can I list this pages?
I can list routes via
<router-link
  v-for="route in $router.options.routes"
  :key="route.path"
  :to="route.path"
>
  {{ route.name }}
</router-link>

but

Can't access metadata
Should filter results

Example:
https://github.com/hannoeru/hannoeru.me
Get metadata part is in vite's config file. And list post is in src/components.


Recover blockstack wallet from HD private key

Currently I can't recover my blockstack wallet from a private key.  Will this be added so I can recover my wallet on a separate machine?

This will be possible in certain cases, provided that (1) you didn't set your private keys directly with e.g. import_wallet, and (2) you aren't using a multisig ownership or payment address (which requires multiple independent private keys).  The multisig support hasn't been deployed yet, but will be in a few weeks.
In the mean time, you can decrypt the wallet and extract the bare information (multisig or not) with the following script.  I'll add this into the CLI for the next release.
#!/usr/bin/python

import blockstack_client
import sys
import json
from getpass import getpass

if len(sys.argv) != 2:
    print >> sys.stderr, "Usage: %s /path/to/wallet.json" % (sys.argv[0])
    sys.exit(1)

wallet_path = sys.argv[1]
password = getpass("Wallet password: ")

with open(wallet_path, "r") as f:
    wallet_data = f.read()

wallet_data = json.loads(wallet_data)

ret = blockstack_client.wallet.decrypt_wallet( wallet_data, password )
print json.dumps(ret, indent=4, sort_keys=True)

sys.exit(0)

In 0.14.0, we've added a blockstack wallet command that will print out the base58check key information stored in ~/.blockstack/wallet.json.