Fix negative issue count set by Check Repository Statistics

Please, make sure you are targeting the develop branch!
More instructions about contributing with Gogs code can be found here:
https://github.com/gogits/gogs/wiki/Contributing-Code
num_issues and num_closed_issues don't contain the PR-issues.

Nice catch @roblabla

The whole checking if it has to be updated and then updating it one by one is unnecessary. We could replace the whole block with just one execution of
UPDATE `repository` SET num_closed_issues = (SELECT COUNT(*) FROM `issue` WHERE repo_id = `repository`.`id` AND is_closed = 1 AND is_pull = 0)

@tkausl Is your query compatible with all database backend ? Don't forget that

What do you guys think of not actually using this column, but count for the open issues when needed? So, no need to update it manually.

@andreynering I already thought about that. Not sure why it was implemented like this, probably performance reasons.

@tkausl Count queries are fast with proper index, I think performance wouldn't be a problem.

Thanks!

@andreynering It would be ideal, but since we can now keep this column value correct, I think it would be not be necessary.

@tkausl: @BurakDev pointed out one part of the reasons, another reason it would be nice to show which repository is been updated for debugging purpose. And since we only do this on start time and the loop is usually small (most of time 0), it would not hurt performance at all in my opinion.

Any suggestion about the best way to fix it once the database contains the incorrect values ? I currently have "Issues: -3" on Gogs <IP_ADDRESS>7. Or will it automagically be fixed when the update is applied from the debian package ?

@FGM
the debian package ? is out of our hands and have been failed to build latest Gogs for quite a while, but once you use latest Gogs connect to your existing database, it fixes automatically.

@Unknwon thank for the confirmation.


Convert type alias to interface?

TypeScript allows for declaration merging of interfaces, which appears to be something that people do to extend types for react-native-web, whereas this cannot be done with type aliases. So it might be preferable to convert to interfaces.
interface X { foo: string }
interface X { bar: string } // merge declaration
const x: X = { foo: "foo", bar: "bar" }

In case it makes things easier, perhaps as a first step, we could also create a temp type alias and use it to extend an empty interface with:
type $1 = { foo: string }
interface X extends $1 {}
interface X { bar: string } // merge declaration
const x: X = { foo: "foo", bar: "bar" }

This might be something we just do selectively using overrides. Cases like RN’s ViewProps definitely make sense from an error reporting perspective too. Errors where type aliases are involved show the full typing, whereas an interface shows only an interned name.
https://github.com/microsoft/TypeScript/issues/13095


[oceanbase] support case-insensitive column name

Try to bypass  issue #2556.

if set column.case-sensitive=false config, the column name cotains capital letter also read null, for example a column name is 'productTitle'
@whhe

if set column.case-sensitive=false config, the column name cotains capital letter also read null, for example a column name is 'productTitle' @whhe

You are right, so when it is set to be false, user shoud use lowercase fileds in flink sql.

if set column.case-sensitive=false config, the column name cotains capital letter also read null, for example a column name is 'productTitle' @whhe

I thought about it again and realized that the insensitive fields in flink sql should also be supported at the same time. The latest commit is made for it.

We may need consider more case-sensitive with Flink SQL‘s case-sensitive


Fatal Unhandlen Exception with Ray Init Method

Expected Behavior

Ray library works without breaking
Actual Behavior

calling ray.init() throws error
Reproducing the Problem

class Algo(QCAlgorithm): 	def Initialize(self): 		import ray 		ray.init()
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Hey @varuk! this has been fixed with the latest foundation update, see https://github.com/QuantConnect/Lean/pull/6558

Reopening because initializing ray seems to be causing a segmentation fault when python is shutting down

Hey!
It seems ray needs to be shutdown explicitly too, see the following working example
# region imports
from AlgorithmImports import *
# endregion

import ray
class AlertBlackGoshawk(QCAlgorithm):

    def Initialize(self):
        self.SetStartDate(2021, 3, 6)  # Set Start Date
        self.SetCash(100000)  # Set Strategy Cash
        self.AddEquity("SPY", Resolution.Minute)
        ray.init()

    def OnData(self, data: Slice):
        if not self.Portfolio.Invested:
            self.SetHoldings("SPY", 0.33)

    def OnEndOfAlgorithm(self):
        ray.shutdown()


Add timers to animation and measuring views

To show how much it takes to do things.

Not implementing animations or counters to animation view. Measuring view is enough.


How to generate private key using NIOOpenSSL or CNIOOpenSSL?

I need to generate rsa private key on my server for my api

I’m afraid that NIOOpenSSL is not intended as a general purpose cryptography library, and does not provide tools for generating private keys. While it is possible to use CNIOOpenSSL to do it I strongly advise against it, as that interface is not stable and may break without warning.
In this case I recommend using a general purpose cryptography library to do this: something like BlueCryptor or Vapor/crypto would do the trick.


Allow .yml file ending for configuration files

Feature Overview
Allow .yml file extenstion for tfaction and tfaction-root config files
Why is the feature needed?
YAML files can have .yml or .yaml as file extension. If you name use tfaction.yml instead of tfaction.yaml the target is not picked up which is confusing at first.
Example Code
No response
Note
I guess you would need to think about situations where you have a tfaction.yml and a tfaction.yaml in the same folder

Thank you for your feedback.
I think you can change file names with the environment variable TFACTION_CONFIG and the configuration working_directory_file.
export TFACTION_CONFIG=tfaction-root.yml

tfaction-root.yml
working_directory_file: tfaction.yml

Thank you for your feedback. I think you can change file names with the environment variable TFACTION_CONFIG and the configuration working_directory_file.

Ah that's nice to know. Thank you.
We had the issue that we did use .yml and had to search a while and read code to figure out what our problem was. We now changed to yaml and everything works.
The feature request was more about helping others in the same situation by either reading both files or maybe give an error or something?

We now changed to yaml and everything works.

Sounds good.

The feature request was more about helping others in the same situation by either reading both files or maybe give an error or something?

I think reading both files is good.


dask cluster (sometimes?) dies after some time

I don't know if this is possible at all, but I have several times run into an issue where the dask cluster on lsst-dev (even on the "normal" queue) dies for unknown reasons after some (somewhat long) amount of time.  Is there some default implicit time limit in the dask-jobqueue slurm job?

It defaults to the debug cluster that has a 30 min limit. On the normal cluster it should be unlimited according to https://developer.lsst.io/services/verification.html?highlight=slurm
Maybe we should ask? I think we can also explicitly set a wall time in dask-jobqueue

Yes, no time limit:
(lsst-scipipe) [dharhas@lsst-dev01 ~]$ sinfo
PARTITION AVAIL  TIMELIMIT  NODES  STATE NODELIST
debug        up      30:00      3   idle lsst-verify-worker[46-48]
normal*      up   infinite     12 drain* lsst-verify-worker[37-40,43-44,55-60]
normal*      up   infinite      8  alloc lsst-verify-worker[01-08]
normal*      up   infinite     37   idle lsst-verify-worker[09-36,41-42,45,49-54]

I know the normal queue has default unlimited time; I was wondering whether dask-jobqueue creates the job with an implicit time limit if one is not specifically requested.


network activity graph is -blank- in Debian Bullseye Mate

new glitch: this network activity graph is -blank- in Bullseye.
the text is still active...

this screenshot is from one of several Debian 10 systems, I like it.
I have tried several fresh installs of Debian 11 in several machines and get the same result in all.
I tried it with no packages installed but Conky, and then I did my best to duplicate the installed packages on the other Debian 10 systems.
(Debian 11 aka Bullseye.. still in Testing mode).

On Debian 11, what does the system return when running the following in command line:
ls -l /sys/class/net/*

peter@z820-2rc1:~$ ls -l /sys/class/net/*
lrwxrwxrwx 1 root root 0 May 15 20:26 /sys/class/net/eno1 -> ../../devices/pci0000:00/0000:00:19.0/net/eno1
lrwxrwxrwx 1 root root 0 May 15 20:26 /sys/class/net/enp1s0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/enp1s0
lrwxrwxrwx 1 root root 0 May 15 20:26 /sys/class/net/lo -> ../../devices/virtual/net/lo
peter@z820-2rc1:~$

root@z820-2rc1:~# ls -l /sys/class/net/*
lrwxrwxrwx 1 root root 0 May 15 20:26 /sys/class/net/eno1 -> ../../devices/pci0000:00/0000:00:19.0/net/eno1
lrwxrwxrwx 1 root root 0 May 15 20:26 /sys/class/net/enp1s0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/enp1s0
lrwxrwxrwx 1 root root 0 May 15 20:26 /sys/class/net/lo -> ../../devices/virtual/net/lo
root@z820-2rc1:~#

Devices seem ok, please post a screenshot from Debian 11. Also run conky from command line, and see if there are informative error messages:
conky -c /path/to/lean-conky-config/conky.conf

peter@z820-2rc1:~$ conky -c /home/peter/.config/conky/lean-conky-config-master/conky.conf
conky: warning: invalid head index, ignoring head settings
conky: warning: invalid head index, ignoring head settings
conky: desktop window (e00006) is subwindow of root window (5ba)
conky: window type - normal
conky: drawing to created window (0x5400002)
conky: drawing to double buffer

@mexsudo LCC has no problem identifying your network interface (enp1s0), you might want to check this with Conky developers why upspeedgraph/downspeedgraph show no activity on Debian 11.

thank you for your efforts.
Debian 11 is in the final stages of testing. I will sit and wait.
Maybe we will get lucky and the official release will be compatible.

FYI: https://sourceforge.net/p/conky/support-requests/41/

FYI: https://sourceforge.net/p/conky/support-requests/41/

Conky development has moved here: https://github.com/brndnmtthws/conky
You might want to first try a simple config first and see if the issue can be reproduced, like the following:

conky.config = {
    alignment = 'top_left',
    background = false,
    border_width = 1,
    cpu_avg_samples = 2,
    default_color = 'white',
    default_outline_color = 'white',
    default_shade_color = 'white',
    draw_borders = false,
    draw_graph_borders = true,
    draw_outline = false,
    draw_shades = false,
    use_xft = true,
    font = 'DejaVu Sans Mono:size=12',
    gap_x = 5,
    gap_y = 60,
    minimum_height = 5,
    minimum_width = 5,
    net_avg_samples = 2,
    no_buffers = true,
    out_to_console = false,
    out_to_stderr = false,
    extra_newline = false,
    own_window = true,
    own_window_class = 'Conky',
    own_window_type = 'desktop',
    stippled_borders = 0,
    update_interval = 1.0,
    uppercase = false,
    use_spacer = 'none',
    show_graph_scale = false,
    show_graph_range = false
}

conky.text = [[
${scroll 16 $nodename - $sysname $kernel on $machine | }
$hr
${color grey}Uptime:$color $uptime
${color grey}Frequency (in MHz):$color $freq
${color grey}Frequency (in GHz):$color $freq_g
${color grey}RAM Usage:$color $mem/$memmax - $memperc% ${membar 4}
${color grey}Swap Usage:$color $swap/$swapmax - $swapperc% ${swapbar 4}
${color grey}CPU Usage:$color $cpu% ${cpubar 4}
${color grey}Processes:$color $processes  ${color grey}Running:$color $running_processes
$hr
${color grey}File systems:
 / $color${fs_used /}/${fs_size /} ${fs_bar 6 /}
$hr
${color grey}Networking:
Up:$color ${upspeed eth0} ${color grey} - Down:$color ${downspeed eth0}
${downspeedgraph eth0}
${upspeedgraph eth0}
$hr
${color grey}Name              PID   CPU%   MEM%
${color lightgrey} ${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${color lightgrey} ${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${color lightgrey} ${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${color lightgrey} ${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}
]]

Replace eth0 with the actual network interface you on your system, from your screenshot above it should be enp1s0.

I also found this problem in my arch linux.
I think it is not caused by distribution's version, because it conky can detect my device wlan0.
I did some tests, the one is to directly show upspeedgraph wlan0 32,130  and it worked properly.
So I think this problem may caused by conky ifaces.

It surely related to conky bug, see https://github.com/brndnmtthws/conky/issues/1109


first batch

Cannot accept such a big number of files.. Make sure to add only 1 or 2 jupyter notebooks ...Rest provide the link to the dataset @Divyansh3021


Revert "Relax LGTMs"

This reverts commit e073febd8714374d6b459924cb0e2f2f998f6252.
This could only change with a proper vote by the project maintainers.
Pushing this through with only 2 maintainers was not acceptable.
Furthermore, if there are problems getting PRs through, it usually has
nothing to do with the number of maintainers on the project. It
typically comes down to the level of engineering work put into making
sure that a change is a clear and accurate solution to the problem. If
it is unclear whether or not a change has impact, then the default
reaction is to not merge the PR.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

I'm agree with this revert. LGTM

Furthermore, if there are problems getting PRs through, it usually has
nothing to do with the number of maintainers on the project. It
typically comes down to the level of engineering work put into making
sure that a change is a clear and accurate solution to the problem. If
it is unclear whether or not a change has impact, then the default
reaction is to not merge the PR.

@stevvooe does that explain why this one never got merged?

LGTM.

@FlorianLudwig This project is no longer actively maintained, which is the core issue. Steven is right that in an actively-maintained project with multiple active maintainers, the 2-LGTM rule is rarely an issue. However, the project has the same maintenance issues as it did when the 1-LGTM change was merged, sort of proving Steven's point.


[SYSTEMML-153] Read file with extension 'csv' not require mtd file

If a read statement reads a file with a .csv extension with no format parameter specified, such as read("m.csv"), the file is considered to be a csv file so that a metadata file is optional and not required.

Did we actually arrive at a consensus on this JIRA?

Tried this out on Spark and it works great.  Having the ability to automatically infer a CSV format for a ".csv" file extension is smart, and avoids confusion for the new user.  This doesn't affect any existing options such as supplying a format="csv" argument to the read(...) statement, and instead will simply add a much-needed convenience.
Also, I ran this using our standalone distribution, and received a java.lang.ClassNotFoundException: org.apache.commons.io.FilenameUtils error.  No problems on Spark though.

Great catch @dusenberrymw . I had assumed commons-io was already added to the libs for standalone since it is such a common library, but I was mistaken. I'll update the standalone assembly to include it.
@mboehm7 I don't believe there was a consensus. My main concern with this issue is that I would prefer not to intimidate new users by requiring them to do things like echo '{"rows": 306, "cols": 4, "format": "csv"}' > data/haberman.data.mtd when they first try to use one of the main algorithms. The required metadata file for csv (if there was no format parameter) was one of the things I first felt frustrated by when I started using SystemML. If I created a csv file containing "1,2,3,4", I did not want to also have to create a JSON-formatted metadata file. Perhaps we can get feedback from some new users to find out if others feel the same way?

As a new user of SystemML I vote for the idea. When I first started to use SystemML the accidental errors in meta data was the most frustrating part. It took me awhile to search through documentations to find my mistakes only to find the error was a typo in mtd.
To build a simple sample I had to write 3 mtds manually:

For the original data file

echo '{
    "data_type": "frame",
    "format": "csv",
    "sep": ",",
    "header": false,
    "na.strings": [ "NA", "null", "NULL", "NaN" ]
}' | hadoop fs -put - my.data.file.csv.mtd

For the type file as an input argument of the transform() function:

echo '1,2,2,1,1' | hadoop fs -put - file-type.csv
echo '{"rows": 1, "cols" : 5, "format":"csv"}' | hadoop fs -put - file-type.csv.mtd

For splitting percentage file as input of 'sample.dml'

printf "0.7\n0.3" | hadoop fs -put - split-perc.csv
echo '{"rows": 2, "cols": 1, "format": "csv"}' | hadoop fs -put - split-perc.csv.mtd

I think the first one is not avoidable though.

@ethanyxu Thank you for your comments. I had a very similar experience. Your #2 and #3 examples are exactly the kinds of situations where I don't want to supply metadata.

Since no consensus could be reached and the MLContext API allows data input without what I would consider burdensome mandatory metadata requirements, I'll close this PR.


Maps not rendering correctly on Angular 4

Issue description
I see the maps in the following manner

Let me know what is the solution for this. Everything other than this works to fine

Any updates here?

Seems like your css breaks it. Might be related to https://stackoverflow.com/posts/14381314/revisions

Tried it but no use. I am not using any CSS that can break! I am using a default angular 4 application.

Can we see your code? Of even better, create a plunker or a demo repo.


Security Fix: don't buffer reads from /dev/urandom

This avoids the weird behavior of IO::Buffered that always buffers reads (and only stops buffering writes). This is a security issue in the case of Random::Secure. Let's switch to direct C calls to completely avoid such issues (now and in the future).
Also unifies the urandom implementation for UNIX (generic) and Linux (getrandom fallback).

Note that I'm not fond of this pull request. I wish there were some nice structs/modules to quickly and safely leverage open/stat/fnctl/read/write/close and creating events without having to go bare libc, but without requiring full crystal either.

@ysbaddaden too many layers of abstraction are also a bit of a bad thing.

Well, it already is:

File end-user interface;
IO::FileDescriptor —supposed fd abstraction, forcefully includes IO::Buffered, and duplicated code with Socket;
Crystal::System::FileDescriptor —actual fd abstraction;
IO::Syscall —actually handles pending read/write events, maybe it should be a generic IO::Evented module to transparently handle evented read/write calls;
Scheduler —to create the fd read/write events but limited to IO::FileDescriptor and Socket (more duplicated code).

I wish fd related IO modules were more composable and reusable for different scenarios. For example here I'd love to extend IO, include Crystal::System::FileDescriptor (maybe IO::FileDescriptor if bare enough) as well as IO::Evented (just in case) but certainly not IO::Buffered, yet, I can't choose that.

This sounds like IO::FileDescriptor might need a review?

@ysbaddaden i'd rather just make File more configurable. If we made sync = true turn off read buffering then we could continue to use File here.
IO::Syscall and Crystal::System::FileDescriptor and Scheduler are pretty much implementation details, I agree they could be done better or rethought but that can be done at any time after 1.0.

Sadly, using File for reading from /dev/urandom is only pushing for more security issues down the line.
I'm not even sure we should go through the event loop at all (we may buffer crypto related data for longer than required), so I'll remove O_NONBLOCK and only rescue the EINTR errno.

I just checked how go handled this (evented or not), but... they use a bufio to buffer reads from /dev/urandom :fearful:

What's the status of this?

To decide whether we 1. merge this (use low level libc calls) or 2. merely fix IO#sync to stop buffering reads in addition to writes or 3. merge both.

I think we'll go with "fix IO#sync to stop buffering reads". But maybe we should rename sync to buffered, because "sync" means "as soon as I write something, I want it written, so writes are synced with their corresponding operations (and not delayed)". But "sync" when reading makes no sense.

Sounds good.

It wasn't immediately clear to me what the "weird" behavior is, and what the security issue is, care to explain them a bit, or point me to a link where it is described?  Thanks!

Buffering caused an immediate bug with fork, where all child processes (and parent) had the exact same random sequences until the buffer was emptied.
You also don't want to read 8KB of random data from the system CSPRNG into memory, when all you need is 8 bytes to initialize the Hash seed (for example), leaving 8184 bytes sitting in memory forever or for long enough that someone may eavesdrop (someone said spectre?) and know further random byte sequences in advance, among other things :(

OK fair enough.  Though if somebody is able to access random memory bytes I'd call that an even bigger problem (startup penalty is pretty minimal... :)


use Commons-IO where possible (DAT-17634)

Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

@StevenMassaro whoops, approved but build is broken ...


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/eventing-writers
/assign knative-extensions/eventing-writers
Produced by: knative-extensions/knobots/actions/update-deps

@creydr it looks like the 1.26.6 KinD tests are failing here, should we bump the job to 1.27 as that's the new min k8s version?

@creydr it looks like the 1.26.6 KinD tests are failing here, should we bump the job to 1.27 as that's the new min k8s version?

sounds good. Maybe we can update https://github.com/knative-extensions/eventing-natss/blob/a4d703860a577feccce37172b3360647c5508b00/.github/workflows/kind-e2e.yaml#L20-L21 too (in a separate PR)

sounds good. Maybe we can update
https://github.com/knative-extensions/eventing-natss/blob/a4d703860a577feccce37172b3360647c5508b00/.github/workflows/kind-e2e.yaml#L20-L21
too (in a separate PR)

@creydr I opened #490 and #491


Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d23qh8upztegq2
Region: us-east-2
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

It looks like the most recent update on your domain is failed DNS verification, the easiest thing to do is to remove and re-add your custom domain from the Console and make sure the DNS records are entered correctly, it can then take up to 24 hours for DNS validation to succeed: https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#custom-domain-troubleshoot-guide
Please reopen if you're still experiencing issues after this


The image that rdesktop is based on has been deprecated

Deprecation notice refers to a replacement image.

Removed in #126


Kubefed binary missing from the tar ball in 1.9 v

Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind bug
/kind feature
Labels:
/ sig federation
What happened:
kubefed install not working right...
I did the following.....
Step 1:
curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/kubernetes-client-linux-amd64.tar.gz
tar -xzvf kubernetes-client-linux-amd64.tar.gz
Step 2:
sudo snap install kubefed --classic
kubefed version
Error:
/snap/kubefed/260/kubefed: 1: /snap/kubefed/260/kubefed: Syntax error: redirection unexpected
What you expected to happen:
kubefed version should display the right version number
Like kubefed version #(like 1.7.0)
How to reproduce it (as minimally and precisely as possible):
Clean Install of K*s 1.9 and then the above Step1 and step 2
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version): 1.9
Cloud provider or hardware configuration: GCP
OS (e.g. from /etc/os-release): Ubuntu 16.04
Kernel (e.g. uname -a): 4.13.0-1002-gcp #5-Ubuntu SMP Tue Dec 5 13:20:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Install tools: snap
Others:

Binaries available as per the release notes.
/close


TS error when using custom()

The property schema: 'object' gives me a TS error and I can't put it to work.
const FormSchema = v.object(
  {
    dataFimValidadeFim: v.nullable(
      v.optional(v.coerce(v.date('validation.date'), (input) => new Date(input as number | string | Date))),
    ),
    dataFimValidadeInicio: v.nullable(
      v.optional(v.coerce(v.date('validation.date'), (input) => new Date(input as number | string | Date))),
    ),
    dataInicioValidadeFim: v.nullable(
      v.optional(v.coerce(v.date('validation.date'), (input) => new Date(input as number | string | Date))),
    ),
    dataInicioValidadeInicio: v.nullable(
      v.optional(v.coerce(v.date('validation.date'), (input) => new Date(input as number | string | Date))),
    ),
    dataPedidoFim: v.nullable(
      v.optional(v.coerce(v.date('validation.date'), (input) => new Date(input as number | string | Date))),
    ),
    dataPedidoInicio: v.nullable(
      v.optional(v.coerce(v.date('validation.date'), (input) => new Date(input as number | string | Date))),
    ),
    idEstado: v.optional(v.coerce(v.string(), String)),
    idInterno: v.optional(v.coerce(v.string(), String)),
    identificador: v.optional(v.string()),
    nome: v.optional(v.string()),
  },
  [
    v.custom((inputs) => {
      if (inputs.dataInicioValidadeInicio && inputs.dataInicioValidadeFim) {
        if (dateRangeValidator(inputs.dataInicioValidadeInicio, inputs.dataInicioValidadeFim)) {
          throw new ValiError([
            {
              input: inputs.dataInicioValidadeInicio,
              message: 'validation.minDateExceeded',
              origin: 'value',
              reason: 'date',
              validation: 'custom',
              path: [
                {
                  input: inputs,
                  key: 'dataInicioValidadeInicio',
                  schema: 'object', <--- Object literal may only specify known properties, and 'schema' does not exist in type 'PathItem'.
                  value: inputs.dataInicioValidadeInicio,
                },
              ],
            },
          ]);
        }
      }

      return true;
    }),
  ],
);

Don't throw inside of custom. Instead always return a boolean: https://valibot.dev/api/custom/

Hum, I saw some issues where people were throwing inside custom.
Imagine this scenario, how can I achieve the same result without throwing in custom?
codOutrasNacionalidades: v.array(v.string([v.minLength(1, 'required.otherNationalities')]), [
    v.minLength(1, 'required.otherNationalities'),
    v.custom((input) => {
      const duplicates = input.filter((item, index) => input.indexOf(item) !== index);

      const issues: v.SchemaIssues = [] as unknown as v.SchemaIssues;

      if (duplicates.length > 0) {
        input.forEach((val, index) => {
          if (duplicates.includes(val)) {
            issues.push(
              createValibotIssue({
                fieldPath: `pessoa.codOutrasNacionalidades.${index}`,
                input: { 'pessoa.codOutrasNacionalidades': input },
                message: 'validation.uniqueNationalities',
                reason: 'array',
              }),
            );
          }
        });
      }

      if (issues.length > 0) {
        throw new v.ValiError(issues);
      }

      return true;
    }),
  ]),

export const createValibotIssue = ({
  message,
  reason,
  input,
  fieldPath,
}: Pick<SchemaIssue, 'message' | 'reason'> & { input: Record<string, unknown>; fieldPath: string }): SchemaIssue => ({
  context: '',
  expected: null,
  input: input[fieldPath],
  message,
  path: [
    {
      input,
      key: fieldPath,
      origin: 'value',
      type: 'object',
      value: input[fieldPath],
    },
  ],
  reason,
  received: '',
});

I would return false instead of throwing and error and add the error message as the second parameter to custom. But currently there is no way to return multiple issues, but I am in the process of rewriting Valibot and it will be easier then.

Also we have a some and every validation action specifically for arrays:

https://valibot.dev/api/some/
https://valibot.dev/api/every/

I would return false instead of throwing and error and add the error message as the second parameter to custom. But currently there is no way to return multiple issues, but I am in the process of rewriting Valibot and it will be easier then.

I've seen the discussion, I'm waiting for that :).

Also we have a some and every validation action specifically for arrays. You could use every to check for duplicate values.

https://valibot.dev/api/some/
https://valibot.dev/api/every/

I didn't try it yet, but do every put the error at the index of the element?

I didn't try it yet, but do every put the error at the index of the element?

No, but that's an interesting idea!

I've seen the discussion, I'm waiting for that

With my current code pipeline actions accept a dataset as the first argument and return a dataset as a result. This will allow you to easily write your own actions and add as many issues as you want. I plan to publish a first draft next week.

No, but that's an interesting idea!

I think so, in my current implementation, this is important to select the duplicated option, and with the code that I've shared here, it works.

With my current code pipeline actions accept a dataset as the first argument and return a dataset as a result. This will allow you to easily write your own actions and add as many issues as you want. I plan to publish a first draft next week.

Those are good news, I'm looking forward to testing it.

Although it's not recommended, I'll let v.custom with throw as it is working as I need, I'll come here again when the rewrite is done to update it. And perhaps close the issue then with a solution.
In summary, I would like to have:

An option to validate every element of the array and add the issue to the index of the occurrence (in this example, otherNationalities.2.
An option to add issues globally to the schema based on field relations:

const Schema = v.object(
  {
     mainNationality: v.string([v.minLength(1, 'required.nationality')]),
     otherNationalities: v.array(v.string([v.minLength(1, 'required.otherNationalities')]), [
        v.minLength(1, 'required.otherNationalities'),
        (custom valiration to check duplicated)
     ])
    (...other fields)
  },
  [
    v.<someMethod>((inputs) => {
      // If some element in otherNationalities is equal to the mainNationality,
      // add an issue to the otherNationalities item index
    }),
  ],
);

Hi @fabian-hiller I saw your comment on the rewrite PR, I was thinking about testing the new implementation of pipe in this context, do you have any suggestion on where I can start? Or there are no way to do this yet?

It is possible, but you have to write your own action. The concept is very simple. Here is an example where I have called the action "items":
import {
  _addIssue,
  type BaseIssue,
  type BaseValidation,
  type ErrorMessage,
} from 'valibot';

/**
 * Items issue type.
 */
export interface ItemsIssue<TInput extends unknown[]>
  extends BaseIssue<TInput> {
  /**
   * The issue kind.
   */
  readonly kind: 'validation';
  /**
   * The issue type.
   */
  readonly type: 'items';
  /**
   * The expected input.
   */
  readonly expected: null;
  /**
   * The validation function.
   */
  readonly requirement: (input: TInput[number]) => boolean;
}

/**
 * Items action type.
 */
export interface ItemsAction<
  TInput extends unknown[],
  TMessage extends ErrorMessage<ItemsIssue<TInput>> | undefined,
> extends BaseValidation<TInput, TInput, ItemsIssue<TInput>> {
  /**
   * The action type.
   */
  readonly type: 'items';
  /**
   * The action reference.
   */
  readonly reference: typeof items;
  /**
   * The expected property.
   */
  readonly expects: null;
  /**
   * The validation function.
   */
  readonly requirement: (input: TInput[number]) => boolean;
  /**
   * The error message.
   */
  readonly message: TMessage;
}

/**
 * Creates an items validation action.
 *
 * @param requirement The validation function.
 *
 * @returns An items action.
 */
export function items<TInput extends unknown[]>(
  requirement: (input: TInput[number]) => boolean
): ItemsAction<TInput, undefined>;

/**
 * Creates an items validation action.
 *
 * @param requirement The validation function.
 * @param message The error message.
 *
 * @returns An items action.
 */
export function items<
  TInput extends unknown[],
  const TMessage extends ErrorMessage<ItemsIssue<TInput>> | undefined,
>(
  requirement: (input: TInput[number]) => boolean,
  message: TMessage
): ItemsAction<TInput, TMessage>;

export function items(
  requirement: (input: unknown) => boolean,
  message?: ErrorMessage<ItemsIssue<unknown[]>>
): ItemsAction<unknown[], ErrorMessage<ItemsIssue<unknown[]>> | undefined> {
  return {
    kind: 'validation',
    type: 'items',
    reference: items,
    async: false,
    expects: null,
    requirement,
    message,
    _run(dataset, config) {
      if (dataset.typed) {
        for (let index = 0; index < dataset.value.length; index++) {
          const item = dataset.value[index];
          if (!this.requirement(item)) {
            _addIssue(this, 'item', dataset, config, {
              input: item,
              path: [
                {
                  type: 'array',
                  origin: 'value',
                  input: dataset.value,
                  key: index,
                  value: item,
                },
              ],
            });
          }
        }
      }
      return dataset;
    },
  };
}

Now you can write the following code:
import * as v from 'valibot';
import { items } from './your-path';

const Schema = v.pipe(
  v.array(v.string()),
  items((item) => item.startsWith('foo'), 'Your message')
);

I'll try that, do you plan on implementing it in valibot?

Yes, I will consider it. Do you have some good alternatives names for the action?

The only one that I could think of is iterate.

I was thinking, it would be nice if the callback had 2 or 3 arguments (item, index, items) => boolean.
With that we could create validations based on other items, for example, identify duplicated values.
(item, index, items) => items.filter((v)=> v===item). length > 1

The only one that I could think of is iterate.

Thanks! Will think about it! Both names could work.

I was thinking, it would be nice if the callback had 2 or 3 arguments (item, index, items) => boolean.

I agree!

To validate that the primaryEmail is not present in...

This requires a custom validation in the pipeline of the object definition with a forward to the appropriate field. Note: We renamed custom to check with the rewrite.

Oh, that's what I need, I thought that the custom was deprecated. Thanks. I'll play a bit with the current state of the lib.
Please update this issue when this action gets done.

@fabian-hiller I was playing around and find that the forward action is missing.

You are right. I will probably add it today or tomorrow. I will ping you then.

Done

Thanks, I'll play with it again.

Is this issue resolved? I will close it for now, but will reopen it if not.

Feel free to create a new issue (or PR) to add an items action in the next weeks.

Is this issue resolved? I will close it for now, but will reopen it if not.

I'll check it ASAP and let you know.

Feel free to create a new issue (or PR) to add an items action in the next weeks.

I'll open one issue latter today.

I'm not able to put a schema to work with this requirement, can you help here?

{
    "primaryEmail"<EMAIL_ADDRESS>    "otherEmails"<EMAIL_ADDRESS><EMAIL_ADDRESS>}

To validate that the primaryEmail is not present in otherEmails the items action doesn't work, I need some actions that allow me to add issues globally.

The forward action doesn't work because I cannot put the key and index of the duplicated email, in this case otherEmails.1.

Maybe we should add an advanced refine method (similar to Zod) that allows you to directly interact with the input and output dataset of the method and not only with the raw value.

I agree, let's do the following, I'll close this issue and open a new one with a recap of this one.


Events page

please remove archery tag.
Women's Bible Study date should say- starting Oct 2/3
let's add:
equip class

I removed archery tag.
I don't have a great way right now to show 2 start dates on the events page...
I also don't have a great way of adding equip classes to the event page, but I did add it to the homepage for now.

thanks adam

On Sep 19, 2017, at 1:37 PM, Adam Garrett-Harris<EMAIL_ADDRESS>wrote:
I removed archery tag.
I don't have a great way right now to show 2 start dates on the events page...
I also don't have a great way of adding equip classes to the event page, but I did add it to the homepage for now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Mountainview-WebDesign/lifestonechurch/issues/134#issuecomment-330650468, or mute the thread https://github.com/notifications/unsubscribe-auth/AXfBrVHI5ftpKmgqvBWi9RkRQcXg-sIvks5skBf4gaJpZM4Pcza6.

All For Jesus,
Keely Williams
Administrative Assistant
Lifestone Church Riverton
817.598.9567
lifestonechurch.net


[SPARK-16512] Adding a insertNullOnErrors option.

This is the change that allows an option to render errors when parsing such as number format exceptions as nulls.
It was in this pull request, https://github.com/databricks/spark-csv/pull/298 but I thought it would be cleaner to create a new one.

@rachelwarren as you know this package is in maintenance mode and does not accept patches that modify the API. I suggest you send this patch to Apache Spark, where CSV data source has been in-lined since 2.x.


Update docs on LangChain agent memory

Thank you for contributing to LangChain!

[ ] PR title: "package: description"

Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..."  for template changes, "infra: ..." for CI changes.
Example: "community: add foobar LLM"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change
Twitter handle: if your PR gets announced, and you'd like a mention, we'll gladly shout you out!

[ ] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/docs/integrations directory.

[ ] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

#sign-off

@baskaryan


Miner AI change: do not flee/ripcord or launch in to sectors with enemy ships

Currently the miner AI has it to where it will enter in to a sector if there are these conditions:

A friendly base.
If enemy ship, friendly base + one friendly ship.
A friendly sector with enemy ship if miner is in adjacent sector (and moves to the friendly base).

These three things can seriously get miners killed. I don't know how many times I've had to save miners because they decided to wander in to a ref with scouts roaming around only to decide that they wanted to leave the sector AFTER they got inside and saw the enemy.
The first item of business - not allowing undocking or ripcording if there are enemy ships even in the presence of friendlies - is something that would greatly benefit many commanders, as they don't have to keep their eye on the sector at all times and constantly reordering miners in to base. I understand that a new command is in the works for this very thing, but I think this change would also be beneficial in case the commander for some reason forgot to do #dock or whatever it is. The #dock command wouldn't work for ripping miners or cons, though, as they'd still ripcord to a sector if out of base and filled with a substantial amount of He.
However, the second business item simply states that a miner would wise up to do a couple of things before entering a friendly sector:

Before entering a sector, check to see if there's an enemy ship inside it.
If there is, flee back to base.
This in itself would save many miners from being killed, as sometimes they decide that as soon as they're in a safe sector and no longer under attack, they want to mine again in the same place they just came from. The Death Turnaround, I call it. So if we could get rid of this...yeah, that's be lovely.

Imported from trac ticket #173,  created by anonymous on 07-24-2010 at 10:14, last modified: 07-28-2010 at 22:56

Replying to anonymous:

I understand that a new command is in the works for this very thing
The AI is dumb and it's not going to change w/o complete approval.  What has been approved AFAIK is what you mention above and that's allowing the commander more controls that he or she can act upon, not having the actions done for them; What you propose to enhance would be refereed to as "major changes to gameplay".  sidelined....for now

see also #48
Trac comment by Imago on 07-25-2010 at 14:41

I've marked this invalid until the reporter posts a link to community discussion/approval.  I personally do not approve of making miners smarter on their own, certainly not these sweeping game play changes and especially w/o community approval.
Trac comment by Imago on 07-28-2010 at 22:55

Replying to Imago:

I've marked this invalid until the reporter posts a link to community discussion/approval.  I personally do not approve of making miners smarter on their own, certainly not these sweeping game play changes and especially w/o community approval.

-- endorsed by Bard
Trac comment by Bard on 07-28-2010 at 22:56


Update to official BouncyCastle package

Portable.BouncyCastle is the official portable version of BC.

:+1: cool thanks


[Feature request] Context menus are released

Quote from discord developer discord:
_Context menus
We've just rolled out support for context menu commands on desktop clients!
You can register context menu actions on users and messages.  These commands are visible when you right click on a user/message or click the three dots next to a message.
Head over to #context-menus to mingle with other context menu aficionados.  We're excited to see what you build :grin:
Docs for user commands: https://discord.com/developers/docs/interactions/application-commands#user-commands
Docs for message commands: https://discord.com/developers/docs/interactions/application-commands#message-commands_

Already working on integrating.

Glad to hear!

Implemented as of release 3.0.0.


Document OpenColorIO Development Process

Following discussion on transparency and openness of new feature development, and related TSC discussion, I've added a PROCESS.md document to outline a feature proposal process. The process is based on current practices adhered to by the project with two changes:

Push up proposal discussion and issue creation in the timeline where possible. In short, it's up to the contributor when a design is proposed, but accepting the risk of potential redesign requested by the community.
Adding accepted proposals to a new Roadmap GH Project for progress tracking and transparency.

All of this is up for discussion of course. All comments/suggestions are welcome and appreciated.
Resolves #1124
Signed-off-by: Michael Dolan<EMAIL_ADDRESS>

Hi @michdolan,
Looks great at first glance! It covers pretty much what I was hoping to see. I haven’t checked the roadmap project yet though.
Cheers,
Thomas

Thanks for the feedback! @doug-walker I will take a pass at revising that section based on your feedback. Great points.

Was that discussed yesterday in the TSC meeting? I thought it would have made sense to publicize/advertize the document on Slack and/or the mailing list to see if the community was fine!
It is a bit of a chicken and egg situation but I will quote the new document itself:

All core changes begin with community discussion, which can involve informal conversation in Slack or on ocio-dev, but are ultimately brought to a TSC meeting where consensus can be reached around the proposal's relevance and approach. TSC meetings are public and meeting notes are posted to the OCIO repo within days of a meeting for a permanent record of decisions.

So to go back to some of the last bullet points:

Large or significant changes must receive both approvals from Committers that are not affiliated with the author or their company.

If approval does not happen within two weeks of opening a pull request and there are no raised objections or unresolved discussions happening about the feature, a Committer that is affiliated with the author may approve it. At some point, we have to assume that the people who know and care are monitoring the PRs and that an extended period without objections is really assent. Notice must be given in the pull request between 2 and 4 days in advance of the intended merge date. This gives a windows for reviewers to comment or request additional time for review.

Isn't this still empowering a group of affiliated people to steer the project where they want? It is Christmas break, Michael is taking some holidays, and we get a raytracer in OCIO at New Year's Eve, because, well nobody really looked at the project... :) I think that Core changes should not have an escape door.
Besides this point, it looks fine!

Damn, sorry to have jumped on that too late!


Make Rot90 direction clear

First off thanks so much for this tool! I think it's really helpful for preparing datasets.
I just wanted to mention something I found while working with the Rot90 augmenter. I was rotating my images with PIL and found that the direction of rotation was opposite. PIL rotates images counterclockwise (ROTATE_90 means to the left), while Rot90 rotates the bounding box clockwise. So I had to do 3 Rot90's to get the same as PIL's ROTATE_90.
Guess it's not really an issue with the implementation, just would be useful to note this in the documentation. Thanks again!

The documentation actually already says that, see e.g. https://imgaug.readthedocs.io/en/latest/source/api_augmenters_geometric.html#imgaug.augmenters.geometric.Rot90 . Though it was changed quite recently from counter-clockwise to clockwise and I think at that point the word "clockwise" was also added to the docs (before there was no note about the direction). So it's possible that you looked at an older version of the documentation or code that didn't contain the direction yet. Or did you expect to see such a note somewhere else?

Ah, looks like I missed that, thanks for clarifying. I think I was looking at the main README, but the docs should be the definite answer. I guess it's up to you whether you think it's worth updating in the readme as well.


Chinese great firewall cause test-tcp-connect-timeout fail

test-tcp-connect-timeout.c has a hard coded google dns <IP_ADDRESS> .  Test passed after I changed this address to a Chinese local dns address. It seems great firewall dns pollution on google dns cause the test failed.

It's a sort-of known issue in that we're aware that hard-coding IP addresses is not a good idea.  I'm afraid I don't know of a good way to fix it, though - we still need a way to test that functionality.

Do the OpenDNS servers work there? That's <IP_ADDRESS> and <IP_ADDRESS>.  I wouldn't mind changing to one of those.


ARROW-8777: [Rust] Parquet.rs does not support reading fixed-size binary fields.

Fixed length binary fields require some extra context to be passed to
the data conversion functions; the byte width of the data field.
This change also adds more specific converters for reading timestamp
types into Arrow. Previously an error would be raised because the schema
type (ie: Timestamp(Microseconds, _)) was different than the
converter-generated column type (UInt64).

Apologies for the hiccups in getting this green but it's sorted now.


"Termin" URL is always the same - tool still working?

When setting up the environment file (.env) I noticed that all link behind "Termin buchen" are always the same.
--> https://service.berlin.de/terminvereinbarung/termin/day/
BOOKING_URL=The link to the appointments page. Use the link behind "Termin buchen" or "Termin berlinweit suchen" buttons.
The url makes no sense, because it seems the real data will be loaded elsewise while clicking on it.
So I wonder whether the tool is still working and or did the website logic change?
Here are clearly slots available, but the link above

But the result is the following:

Try right clicking the "Termin buchen" or "Termin berlinweit suchen" button to copy the url. The url contains the type of appointment and the location. A valid link looks like this:
https://service.berlin.de/terminvereinbarung/termin/tag.php?termin=1&dienstleister=327334&anliegen[]=120703&herkunft=1

Thanks, I tried it already.
For test purposes I tried to get appointments where there are usually slots open.
I get the links from this category: https://service.berlin.de/dienstleistung/121921/#wohin
https://service.berlin.de/terminvereinbarung/termin/tag.php?termin=1&dienstleister=122058&anliegen[]=121921&herkunft=1
https://service.berlin.de/terminvereinbarung/termin/tag.php?termin=1&dienstleister=324673&anliegen[]=121921&herkunft=1
Both have several free slots, but I receive the following error:

When I try to get an appointment for my real purpose in this category:
https://service.berlin.de/dienstleistung/318998/
I fetch the following link:
https://service.berlin.de/terminvereinbarung/termin/tag.php?termin=1&dienstleister=327427&anliegen[]=318998&herkunft=1
This is the result:

But I don't know whether the result is valid or not, because there's no slot free as of now.
This is my -env settings:

I just tried out your .env and could reproduce the error.
The 404 HTTPError is thrown, when the script tries to reach out to Telegrams API to send a message. As you have no bot token or chatId set, the assembled URL is not correct.
I'm gonna improve the script a bit, to make the error more clear.

Thank you for that hint. That did the trick.
I filled the missing input to the .env file, my bot is now repsonding to me.
Yes, a adjustment of the error message would be helpful for others I think.

Adressed this issue in https://github.com/similicious/berlin-buergeramt-bot/commit/37b1b9d432f8093f87d37ca463b7b61d34cf6464


allresults.py bug fix

In pull request https://github.com/darrencroton/sage/pull/14 I've proposed
a bug fix for commit a186562 .  It seems to me that 2be3027 should fix the
bug. Just to repeat the bug report here (also give in the pull request), since this is
the Issues section:
Python 2.7.12 tolerates feeding floats to the np.histogram
function with a warning that the behaviour will soon be deprecated.
Consistently with that warning, python 2.7.13 gives a fatal error:
TypeError: 'numpy.float64' object cannot be interpreted as an index

Using the floor function is not enough, because it
gives float values such as 32.0 instead of integers such as 32.
The int function is needed too. In general, using int(floor(x)) is
not the same as int(x), since int(floor(-2.7)) is -3 while int(-2.7) is -2,
at least in fortran and C, so it could be the same in python. For positive
floats, int(x) should be OK, I presume.

Thanks @broukema . I'll be having a look and updating a number of things soon. Appreciate the feedback.

hi @darrencroton - I saw you implemeted this in commit 0fec63735eaa , so I'll close this issue. :)

Thanks. Sorry it took so long! Fell off my radar.


Mixture model with gaussians fails to create

Hello!
I have written some code to model GMM and further prob some data points. I already have weights and other params for initialization. Here is the code:
ds = tf.contrib.distributions
gaussians = []
for i in range(0, len(weights)):
    mns = means[i]
    covs = covariances[i]
    gaussians.append(ds.MultivariateNormalFullCovariance(loc=np.array(means).astype(np.float64), covariance_matrix=np.array(covariances).astype(np.float64)))

gmm = ds.Mixture(
  cat=ds.Categorical(probs=weights.astype(np.float64)),
  components=gaussians
)

However in this stage:
 cat=ds.Categorical(probs=weights.astype(np.float64)),
there is this error:

Traceback (most recent call last):
File "D:\Programs\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 560, in merge_with
self.assert_same_rank(other)
File "D:\Programs\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 605, in assert_same_rank
other))
ValueError: Shapes () and (32,) must have the same rank

I have 32 gaussians per mixture, data has 26 features.
Weights is a list of floats, means - list of floats for each gaussian, covariances - matrix in form of list of lists for each gaussian.
I started to see why Shapes is just empty, and found this piece of code from tf from exception:
  @property
  def batch_shape(self):
    """Shape of a single sample from a single event index as a `TensorShape`.

    May be partially defined or unknown.

    The batch dimensions are indexes into independent, non-identical
    parameterizations of this distribution.

    Returns:
      batch_shape: `TensorShape`, possibly unknown.
    """
    return self._batch_shape()

So, the problem might be somewhere in self._batch_shape() function. And in categorical.py, I found this lines of code:
 def _batch_shape(self):
    return self.logits.get_shape()[:-1]

When debugging, I found out that this exact function is hit when Shape check is performed. And self.logits.get_shape() does return Shape(32,), but taking [:-1] from it, leads to an error.
Is this an intended behaviour?

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Use middleware

Use middleware for quickstart.

This work is continued here with a new version of the middleware. So closing this.


Deprecate old syntax for parametrized functions

This adds deprecation warnings for the old syntax (using .remote on the class, NOT using .remote on the method) as well as deprecating the mixin (since it's no longer needed)

@prbot approve


Could not find module ember-cli-deprecation-workflow

Am working on upgrading from Ember 3.28.  Installed this add-on via
pnpm add -D ember-cli-deprecation-workflow

made the recommended code changes and then ran
ember test --server

which results in
not ok 1 Chrome 127.0 - [undefined ms] - Global error: Uncaught Error: Could not find module `ember-cli-deprecation-workflow` imported from `<my_package_name>/app` at http://localhost:7357/assets/vendor-a8e01cf449f0c2e23842103a14893ffb.js, line 259

I can see the library in node_modules . . . feels like I am missing something simple . .  .
Update: ran
DEBUG="ember-auto-import:*" AUTO_IMPORT_VERBOSE=true ember test

and can see this at least:
  {
    "specifier": "ember-cli-deprecation-workflow",
    "path": "<my_package_name>/app.js",
    "isDynamic": false,
    "package": "<my_package_name>",
    "treeType": "app"
  },

what's your app.js look like?
imported from `<my_package_name>/app`
```?

in my projects, it looks like this:

```js
import './deprecation-workflow';

import Application from '@ember/application';

import loadInitializers from 'ember-load-initializers';
import Resolver from 'ember-resolver';

import config from '<package-name>/config/environment';

export default class App extends Application {
	modulePrefix = config.modulePrefix;
	podModulePrefix = config.podModulePrefix;
	Resolver = Resolver;
}

loadInitializers(App, config.modulePrefix);

and then, in app/deprecation-workflow.js:
import setupDeprecationWorkflow from 'ember-cli-deprecation-workflow';

setupDeprecationWorkflow({
	throwOnUnhandled: true,
	workflow: [
		// Add your deprecation handlers here.
		// See docs:
		//    https://github.com/ember-cli/ember-cli-deprecation-workflow
	],
});

After running into this error I just added the import to app.js, like so, still failing:
import Application from '@ember/application';
import Resolver from 'ember-resolver';
import loadInitializers from 'ember-load-initializers';
import config from '<my_package_name>/config/environment';
import setupDeprecationWorkflow from 'ember-cli-deprecation-workflow';

export default class App extends Application {
  modulePrefix = config.modulePrefix;
  podModulePrefix = config.podModulePrefix;
  Resolver = Resolver;
}

setupDeprecationWorkflow();
loadInitializers(App, config.modulePrefix);

Notably, ember-cli-deprecation-workflow and ember-resolver are both in devDependencies, both present on disk, both with identical output when building with ember-auto-import debugging on.

what's your ember-cli, ember-auto-import and @embroider/* (if any) versions?
do you happen to have a reproduction of this I can poke at?

ember-cli: 5.10.0
ember-auto-import: 2.7.4

When run in my package root:
> ember --version
ember --version
ember-cli: 5.10.0
node: 18.17.1
os: darwin arm64

I don't have any direct dependencies on embroider packages but there are plenty of transitive dependencies.  Any particular package might matter?  I am guessing
@embroider/macros: 1.15.1
@embroider/util: 1.13.0

I don't have a shareable repro but maybe I can put one together, but I might just try some debugging first.

Okay it was something dumb.  Unbeknownst to me, it was already a dev dependency pinned to version 2.2.0.  Updating to the latest version fixed the issue.


Change links

The packages were not building because the links were wrong - I just changed them from aquasecurity/... to IntelligentDX-LLC/...

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

Hey @kmeenan-indx - guess you decided against this PR, changing the paths shouldn't be needed. Shout if you need assistance


Add a tfjs-tflite-node codelab checkpoint with webnn inference working

Depends on https://github.com/tensorflow/sig-tfjs/pull/23

This change is

@pyu10055, @mattsoulanille, @huningxin, PTAL, thanks!

@mattsoulanille, @huningxin, thanks for your review! Comments addressed, PTAL again.


test-branch/execute-job/wrong-comment-on-pr/b4e22db9-2424-4b8f-89a6-46845ac0ad83

PR for testing 4aaabb63bbbd48b3d635f98e12800b5efefd3c64

comment 1


New Exchange: ForkDelta

API Reference: https://www.reddit.com/r/ForkDelta/comments/7pen41/api_for_forkdelta/

Merging with #22


Create the Rank and IsScalar shared functions | feat(torchlib)

This change introduces two shared operators Rank and IsScalar. They are used to replace the Size(Shape()) pattern for code reuse and readability.
I used a hack to always include these shared functions in the model proto because without #834 we cannot dynamically add these functions to the model as they are used. I added a TODO for this.
The first usage is in aten_all. I will update the rest of the functions in a separate PR.
#1095

@BowenBao PTAL


Email notifications

How does email notification actually work? I would like to use smtp on my CentOS 6.6 to relay messages to our primary email server. Is this possible or do I need to use Exim?
Thanks!
Andrew

Do you have sendmail configured? 411 just calls the mail() function, so if everything is set up it should work.

I think it is configured properly. I will test though and let you know.

Yep, works fine. Sendmail was not running (I though I started it). Thanks!


Is this project alive?

Hi @lloyd!
I'm active user of yajl. I've seen many opened issues and PR. Is that normal? Or you don't have time for support?

Maybe @lloyd could use some help?

A long time ago, I have done a ticket:

https://github.com/lloyd/yajl/issues/219


Noob Install

So i've installed LAMP stack on a LXC , but i've read the documentation and i'm still a bit lost on what to do next.
Can anyone give me some pointers? (its gonna be a local machine only, no connection to the outside world, via local IP, so defaults usernames and ports are fine)

Hi now you can clone the repository and execute the setup script, inserting all database parameters needed.
Then you can proceed to login page with default admin credentials.


is there an equivalent of bash's herestring ?

does elvish have or plan to have an equivalent of bash's here string
idk, i prefer this
cut -d. -f2 <<< hello.world

more than this
echo hello.world | cut -d. -f2

Elvish doesn't have it now, although it does look an ergonomic feature in some cases.

It's not obvious adding another feature to the Elvish grammar just to avoid an explicit pipe is worth the cost -- both implementation and documentation. One of the reasons I switched from zsh to fish was I got fed up with additions to the zsh grammar that were seemingly implemented without regard to whether the added complexity was justified and the new feature meshed well with existing features and couldn't be accomplished in some other way. Read man zshexpn for the primary example of what I'm talking about then look at the scripts in /usr/share/zsh. For example, I challenge you to tell me what this line from _absolute_command_paths does:
local -a matches=( "${(@)commands[(R)${~i}[^/]#]}" )

I'll also point out that the first time I read this issue I thought the O.P. was talking about "here documents". That is, a construct such as this:
> echo << EOF
hello
EOF

The fact it is extremely easy, and likely, for someone to read <<< word as a here-doc, rather than a here-string, is another reason not to introduce this syntax.

Yeah, I agree that in its POSIX form, herestrings don't seem to be worth the hassle.
But generalize it to value inputs it can be more useful. To recap, many commands in Elvish take input either via (1) value input, or (2) as a final list argument (see https://elv.sh/ref/builtin.html#supplying-input for examples). If it's very concise to build value inputs, they only need to support the first form; the second form can just be a redirect. Hypothetical example:
// Instead of:
each [x]{ + 1 $x } [10 100]
// Write:
each [x]{ + 1 $x } << [10 100]

This might just seem to be more verbose, but the advantage is that it doesn't require the implementation of each to support 1 or 2 arguments. Another benefit, in terms of readability, is that redirections can appear anywhere, so you can write:
each << [10 100] [x]{
  + 1 $x
}

This will allow each to eventually fully replace for. Although TBH, in this example it is still less readable than for, so more work on the syntax of input redirection may still be needed.

#991 is also relevant here.

I like the idea of changing the syntax so that functions, like each, which use the $input-list? pattern would instead always read from a value pipe -- possibly implicitly created by the << operator.
What about a single value not enclosed in brackets? That is, would count << 1 and count << [1] be equivalent? The current behavior special-cases strings as a list of characters. So count abc and str:split '' abc | count are equivalent. But note that count (float64 1) is an error since the float64 type is not iterable. In fact, AFAICT, no builtin types implement the Iterable interface as I write this so only strings are special-cased in the context of an $input-list? argument. I appreciate why implicitly splitting a string into its constituent code-points is  useful. But note that these two examples are not equivalent:
> put abc | count
▶ 1
> count abc
▶ 3

As a greybeard I understand why those two statements produce different results. But it is a subtlety that is even more likely to confuse users if count << abc is implemented. Should the "here-value" form be equivalent to the first or second example above?


Defcustom org-journal-search-results-order-by

This is a light suggestion PR

I like it! Thank you very much!


Keyboard users are forced to use esc or tab through the calendar to use the datepicker and then move focus to next element..

Describe the bug
A keyboard only user should be able to tab to the datepicker, type a date, hit tab once and go to the next focusable element on the page.
Because we auto-open the bib when you start typing, a keyboard user is forced to hit the esc key or tab all the way through the calendar.
To Reproduce
Steps to reproduce the behavior:

Go to http://auro.alaskaair.com/components/auro/datepicker
Click use the tab key to get to a datepicker
Type a date
hit tab again

Expected behavior
I would like to be able to just type a date and then move one without having to manually escape the calendar.

@leeejune to look over this issue with Kayla.

Will review after completion of https://github.com/AlaskaAirlines/auro-dropdown/issues/183 And/or native popover support implementation.


Faithlife.Logos version <IP_ADDRESS>3

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @ torculus,
The package prompts for language:

I wasn't able to find an installer switch to clear this. Are you aware of one?

Unfortunately, I'm not aware of all of the possible installer switches. Is there a way to re-submit this as "needing user interaction" ?

Unfortunately, I'm not aware of all of the possible installer switches. Is there a way to re-submit this as "needing user interaction" ?

Yes - this PR is blocked by:

https://github.com/microsoft/winget-cli/issues/910

No recent activity.


Display Europe Air Quality index

Q
A

Bug fix?
no

New feature?
yes

Fixed tickets
#5

Codecov Report

Merging #14 (5d15ee7) into main (d4515cb) will decrease coverage by 6.07%.
The diff coverage is 62.50%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@              Coverage Diff              @@
##                main      #14      +/-   ##
=============================================
- Coverage     100.00%   93.93%   -6.07%
- Complexity        28       34       +6
=============================================
  Files              5        5
  Lines             84       99      +15
=============================================
+ Hits              84       93       +9
- Misses             0        6       +6

Files Changed
Coverage Δ

app/Command/Current/DefaultController.php
83.33% <62.50%> (-16.67%)
:arrow_down:


HTTPClient polled multiple times

I am trying to use the library and that it comes by default exporting to html5 with godot 3.5, but when I receive a chat message, it goes into a loop with the following error:
tmp_js_export.js:369 WARNING: HTTPClient polled multiple times in one frame, but request cannot progress more than once per frame on the HTML5 platform.
tmp_js_export.js:369    at: poll (platform/javascript/http_client_javascript.cpp:270) - HTTPClient polled multiple times in one frame, but request cannot progress more than once per frame on the HTML5 platform.
and from there everything stops working.

This is because threads are not supported on the HTML5 platform. I will rewrite this to use the HTTPRequest node instead with Godot 4.0.

That's right, I was researching and saw what that was, thanks :)

I close the thread, because I understand that it will be solved in godot 4


build(deps): update transitive deps

With pnpm update

#437  👈
main

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

Join @davidlj95 and the rest of your teammates on  Graphite


SODA installation fails on a Ubuntu 18.04 VM on VirtualBox

Issue/Feature Description:
Attempted SODA installation using "INSTALLATION GUIDE USING ANSIBLE" (https://docs.sodafoundation.io/soda-gettingstarted/installation-using-ansible/)
SODA installation failed while "install keystone with the docker" step.
Error message : ""ERROR: keystone didn't come up. Aborting...""
Why this issue to fixed / feature is needed(give scenarios or use cases):
This is a standard installation. It should work on a supported Environment (Ubuntu 18.04 Virtualbox VM).
How to reproduce, in case of a bug:
Run this command to install soda with default configuration
ansible-playbook site.yml -i local.hosts -vvvv

Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)
Environment:
Ubuntu 18.04 VM on VirtualBox.
Network adaptor: NAT, Host-only.

Workaround
The retry count in "installer/ansible/script/keystone.sh" is 12.
Increased the retry count in "installer/ansible/script/keystone.sh" to 40.
wait_for_keystone () {
    local count=0
    local interval=${1:-10}
    local times=${2:-12}    <<<<<


DeepKE/example/ee/standard gives an Error.

根据步骤，pip install -r requirements.txt 出错。
conda 环境是新环境，不存在别的包污染问题。
错误信息：
 pip install  -r requirements.txt
Collecting torch==1.10.0 (from -r requirements.txt (line 1))
  Using cached torch-1.10.0-cp38-cp38-manylinux1_x86_64.whl (881.9 MB)
Collecting transformers==4.26.0 (from -r requirements.txt (line 2))
  Using cached transformers-4.26.0-py3-none-any.whl (6.3 MB)
Collecting hydra-core==1.3.1 (from -r requirements.txt (line 3))
  Using cached hydra_core-1.3.1-py3-none-any.whl (154 kB)
Collecting tensorboardx==2.4 (from -r requirements.txt (line 4))
  Using cached tensorboardX-2.4-py2.py3-none-any.whl (124 kB)
Collecting lxml==4.9.1 (from -r requirements.txt (line 5))
  Using cached lxml-4.9.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (6.9 MB)
Collecting beautifulsoup4==4.9.3 (from -r requirements.txt (line 6))
  Using cached beautifulsoup4-4.9.3-py3-none-any.whl (115 kB)
Collecting bs4==0.0.1 (from -r requirements.txt (line 7))
  Using cached bs4-0.0.1.tar.gz (1.1 kB)
  Preparing metadata (setup.py) ... done
Collecting stanza==1.2 (from -r requirements.txt (line 8))
  Using cached stanza-1.2-py3-none-any.whl (282 kB)
Collecting sentencepiece==0.1.95 (from -r requirements.txt (line 9))
  Using cached sentencepiece-0.1.95-cp38-cp38-manylinux2014_x86_64.whl (1.2 MB)
Collecting ipdb==0.13.9 (from -r requirements.txt (line 10))
  Using cached ipdb-0.13.9.tar.gz (16 kB)
  Preparing metadata (setup.py) ... done
Collecting deepke (from -r requirements.txt (line 11))
  Using cached deepke-2.2.3.tar.gz (256 kB)
  Preparing metadata (setup.py) ... done
Collecting typing-extensions (from torch==1.10.0->-r requirements.txt (line 1))
  Using cached typing_extensions-4.6.3-py3-none-any.whl (31 kB)
Collecting filelock (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached filelock-3.12.2-py3-none-any.whl (10 kB)
Collecting huggingface-hub<1.0,>=0.11.0 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached huggingface_hub-0.15.1-py3-none-any.whl (236 kB)
Collecting numpy>=1.17 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached numpy-1.24.4-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
Collecting packaging>=20.0 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached packaging-23.1-py3-none-any.whl (48 kB)
Collecting pyyaml>=5.1 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached PyYAML-6.0-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (701 kB)
Collecting regex!=2019.12.17 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached regex-2023.6.3-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (772 kB)
Collecting requests (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached requests-2.31.0-py3-none-any.whl (62 kB)
Collecting tokenizers!=0.11.3,<0.14,>=0.11.1 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached tokenizers-0.13.3-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (7.8 MB)
Collecting tqdm>=4.27 (from transformers==4.26.0->-r requirements.txt (line 2))
  Using cached tqdm-4.65.0-py3-none-any.whl (77 kB)
Collecting omegaconf<2.4,>=2.2 (from hydra-core==1.3.1->-r requirements.txt (line 3))
  Using cached omegaconf-2.3.0-py3-none-any.whl (79 kB)
Collecting antlr4-python3-runtime==4.9.* (from hydra-core==1.3.1->-r requirements.txt (line 3))
  Using cached antlr4-python3-runtime-4.9.3.tar.gz (117 kB)
  Preparing metadata (setup.py) ... done
Collecting importlib-resources (from hydra-core==1.3.1->-r requirements.txt (line 3))
  Using cached importlib_resources-5.12.0-py3-none-any.whl (36 kB)
Collecting protobuf>=3.8.0 (from tensorboardx==2.4->-r requirements.txt (line 4))
  Using cached protobuf-4.23.3-cp37-abi3-manylinux2014_x86_64.whl (304 kB)
Collecting soupsieve>1.2 (from beautifulsoup4==4.9.3->-r requirements.txt (line 6))
  Using cached soupsieve-2.4.1-py3-none-any.whl (36 kB)
Requirement already satisfied: setuptools in /anaconda3_public/envs/deepke/lib/python3.8/site-packages (from ipdb==0.13.9->-r requirements.txt (line 10)) (67.8.0)
Collecting ipython>=7.17.0 (from ipdb==0.13.9->-r requirements.txt (line 10))
  Using cached ipython-8.12.2-py3-none-any.whl (797 kB)
Collecting toml>=0.10.2 (from ipdb==0.13.9->-r requirements.txt (line 10))
  Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Collecting decorator (from ipdb==0.13.9->-r requirements.txt (line 10))
  Using cached decorator-5.1.1-py3-none-any.whl (9.1 kB)
INFO: pip is looking at multiple versions of deepke to determine which version is compatible with other requirements. This could take a while.
Collecting deepke (from -r requirements.txt (line 11))
  Using cached deepke-2.2.2.tar.gz (256 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-skjeqsh5/deepke_dc1c5aa904624b7f9c35adab64fa291a/setup.py", line 4, in <module>
          with open("requirements.txt") as requirements_file:
      FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

试一下pip install deepke==2.2.3

 requirements.txt
torch==1.10.0
transformers==4.26.0
hydra-core==1.0.6
tensorboardx==2.5.1
lxml==4.9.1
beautifulsoup4==4.9.3
bs4==0.0.1
stanza==1.2
sentencepiece==0.1.95
ipdb==0.13.11
deepke==2.2.3

requirements.txt 修改成这个就可以了。


Compile error: 'SigV4A' is not a member of 'Aws::Crt::Auth::SigningAlgorithm'

Confirm by changing [ ] to [x] below to ensure that it's a bug:

[x] I've gone though Developer Guide and API reference
[x] I've searched for previous similar issues and didn't find any solution

Describe the bug
Compilation error during make.
SDK version number
1.9.97
Platform/OS/Hardware/Device
CentOS 7
To Reproduce (observed behavior)

Download .tar.gz from GitHub Releases https://github.com/aws/aws-sdk-cpp/releases

Run ./prefetch_crt_dependency.sh

Run cmake:
 build> scl enable devtoolset-3                                                          \
   "cmake3 ..
 Scanning dependencies of target aws-cpp-sdk-core
 [ 88%] Building CXX object aws-cpp-sdk-core/CMakeFiles/aws-cpp-sdk-core.dir/source/AmazonSerializableWebServiceRequest.cpp.o
 In file included from /aws-sdk-cpp-1.9.97/aws-cpp-sdk-core/include/aws/core/AmazonWebServiceRequest.h:16:0,
          from /aws-sdk-cpp-1.9.97/aws-cpp-sdk-core/include/aws/core/AmazonSerializableWebServiceRequest.h:9,
          from /aws-sdk-cpp-1.9.97/aws-cpp-sdk-core/source/AmazonSerializableWebServiceRequest.cpp:6:
 /aws-sdk-cpp-1.9.97/aws-cpp-sdk-core/include/aws/core/auth/AWSAuthSigner.h:48:49: error: 'SigV4A' is not a member of 'Aws::Crt::Auth::SigningAlgorithm'
 ASYMMETRIC_SIGV4 = static_cast<int>(Aws::Crt::Auth::SigningAlgorithm::SigV4A),
                                          ^
 make[2]: *** [aws-cpp-sdk-core/CMakeFiles/aws-cpp-sdk-core.dir/source/AmazonSerializableWebServiceRequest.cpp.o] Error 1
 make[1]: *** [aws-cpp-sdk-core/CMakeFiles/aws-cpp-sdk-core.dir/all] Error 2
 make: *** [all] Error 2

I have this error too; 1.9.145

Facing this with v 1.9.146 as well.


Sporadic error starting up MediaPipe - attachToGLContext

Sometimes MediaPipe crashes on startup (~ 1 out of 10 times) with the following error in my Android app.
android.graphics.SurfaceTexture in attachToGLContext at line 289
com.google.mediapipe.components.ExternalTextureConverter$RenderThread in setSurfaceTextureAndAttachToGLContext at line 15
com.google.mediapipe.components.ExternalTextureConverter in lambda$setSurfaceTextureAndAttachToGLContext$2 at line 3
com.google.mediapipe.components.ExternalTextureConverter in a at line 1
com.google.mediapipe.components.h in run at line 9
android.os.Handler in handleCallback at line 873
android.os.Handler in dispatchMessage at line 99
android.os.Looper in loop at line 193
com.google.mediapipe.glutil.GlThread in run at line 54
Is there any way to catch this error and prevent my app from crashing? I've added an error listener to ExternalTextureConverter temporarily to pass Exceptions back to my app but wandering if there was a better way that doesn't involve editing the library.
Thank you

Hello @magic-fit,
Could you please elaborate your query with complete details, Also, We recommend you to fill the issue template to get relevant information to reproduce it And provide the possible solution in the error you are facing. Thank you!!


Attach some mtl training exp results

I conducted several experiments using ctc, rnn-t, and attention loss on zipformer. Attach WER results on librispeech test clean and test other here for reference.

Exp
Attention loss scale, CTC loss scale
greedy search
fast beam search
modified beam search
ctc greedy search
transducer fast beam search nbest attention rescoring

exp1
0, 0.2
2.23 & 5.17
2.21 & 5.06
2.21 & 5.06
2.49 & 5.77
-

exp2
0.5, 0.2
2.26 & 5.16
2.24 & 5.07
2.25 & 5.03
2.54 & 5.8
-

exp3
1.0, 0.2
2.21 & 5.12
2.2 & 5.10
2.18 & 5.06
2.48 & 5.86
2.19 & 4.98

Codes: https://github.com/yuekaizhang/icefall/blob/mtl/egs/librispeech/ASR/run.sh#L11 Seems like attention loss didn't help comparing with ctc loss + transducer loss training.

Thanks. We will also build a system with the auxiliary attention decoder, following the network style in zipformer code, to see if there is any performance gain.


Request: pls add flow cards with timeline data

Please consider making flow cards available with time line data. E.g. : XYZ has opened the door, to be able to change presence in Homey.

You can use this card for it now.

Thx - indeed since end of December the LOQED app (test version) has been updated to carter for this.


Try connect with IPv6 not IPv4

sorry about my english
after update my proxy not working:
when i run with -v :
{"level":"info","ts":1580219153.4684043,"logger":"telegram.direct","msg":"Cannot dial to Telegram","address":"[2001:b28:f23d:f001::a]:443","error":"dial tcp [2001:b28:f23d:f001::a]:443: connect: network is unreachable"}
my server has only ipv4 but it want to connect on ipv6, may it cause my problem.
Thanks

Thanks


Windows 11 RDC - Protocol error 0xd06 when server max_bpp<32

xrdp version
0.10.0
Detailed xrdp version, build options
# xrdp -V
xrdp 0.10.0
  A Remote Desktop Protocol Server.
  Copyright (C) 2004-2024 Jay Sorg, Neutrino Labs, and all contributors.
  See https://github.com/neutrinolabs/xrdp for more information.

  Configure options:
      --build=x86_64-redhat-linux-gnu
      --host=x86_64-redhat-linux-gnu
      --program-prefix=
      --disable-dependency-tracking
      --prefix=/usr
      --exec-prefix=/usr
      --bindir=/usr/bin
      --sbindir=/usr/sbin
      --sysconfdir=/etc
      --datadir=/usr/share
      --includedir=/usr/include
      --libdir=/usr/lib64
      --libexecdir=/usr/libexec
      --localstatedir=/var
      --sharedstatedir=/var/lib
      --mandir=/usr/share/man
      --infodir=/usr/share/info
      --enable-fuse
      --enable-pixman
      --enable-painter
      --enable-vsock
      --enable-ipv6
      --with-socketdir=/run/xrdp
      --with-imlib2
      build_alias=x86_64-redhat-linux-gnu
      host_alias=x86_64-redhat-linux-gnu
      CFLAGS=-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
      LDFLAGS=-Wl,-z,relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld
      CXXFLAGS=-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
      PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig

  Compiled with OpenSSL 1.1.1k  FIPS 25 Mar 2021

Operating system & version
Rocky Linux 8.10
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
xorgxrdp
What desktop environment do you use?
Xfce
Environment xrdp running on
Microsoft Hyper-V VM
What's your client?
Windows 11 Remote Desktop Connection
Area(s) with issue?
Compatiblity aginst clients, Network
Steps to reproduce
In the xrdp.ini file, set
max_bpp=16 or
max_bpp=24
to reduce latency/overhead and restart the xrdp server.
Try to establish a connection from a default settings Windows 11 RDC client

The default settings have colour depth set to "Highest Quality (32 bit)"
✔ Expected Behavior
It is expected that the client and server will negotiate to agree to use the lower colour quality level configured on the server side.
❌ Actual Behavior
With the default setting of max_bpp=32 in the xrdp.ini file, the Windows 11 RDC client with default colour settings ("Highest Quality (32 bit)" will successfully connect to the server.
However, if the server max_bpp is reduced to 16/24 to reduce latency/overhead then the Windows 11 client will fail to connect. The window will open, display an error message:
"Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again."
The dropdown details show
Error code: 0xd06
Extended error code: 0x0
As soon as OK is pressed, the window closes.

Anything else?
Changing the windows client to any lower colour quality
"True Colour (24 bit)"
"High Colour (16 bit)"
"High Colour (15 bit)"
will allow it to connect as expected - even if that colour quality is still higher than the setting configured on the server.
The only combination that seems to be a problem is "Highest Quality (32 bit)" on the RDC client side with anything lower than max_bpp=32 configured on the server side.

Duplicate of #3118.


Add docstring comment to Style to reference CSS

Mention the fact that the UI layout system is based on the CSS layout
model through a docstring comment on the Style type.
Objective
Explain to new users that the Bevy UI uses the CSS layout model, to lower the barrier to entry given the fact documentation (book and code) is fairly limited on the topic.
Solution
Fix as discussed with @alice-i-cecile on #2918.

there is one difference with CSS that should be mentioned: Bevy is upside down, with the vertical axis inverted

Who's doing the final review? Is that only @cart? If so, ping, this is very short to review and ready for merge, thanks! 🙏

Generally only Cart. @mockersf has merge writes for "uncontroversial" PRs however, which I think this qualifies for.

Yup this is uncontroversial. But I'll merge it because I'm here :)

bors r+


Add missing AL2 header to NameServerTest.java

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1205/
Test PASSed.


Add a guard to the session screen so that sessions can only be joined by logged-in users

closed by #81


Sql Server Management Studio fails to remove the installer.

trying to install Sql Server Management Studio:
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Microsoft/SQLServerManagementStudio/18.5.yaml
fails to remove the installer
microsoft/winget-pkgs#10 [Bart]: winget install "sql management studio"
Found SQL Server Management Studio [Microsoft.SQLServerManagementStudio]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://go.microsoft.com/fwlink/?linkid=2125901&clcid=0x409
  ██████████████████████████████   534 MB /  534 MB
Successfully verified installer hash
Installing ...
Successfully installed!
An unexpected error occurred while executing the command:
remove: Access is denied.: "C:\Users\Bart\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\TempState\WinGet\Microsoft.SQLServerManagementStudio.18.5.exe"
microsoft/winget-pkgs#11 [Bart]:

https://github.com/microsoft/winget-cli/issues/418

This bug will be fixed when we implement #418

Duplicate of #418


chore: remove dead links

Name
Link

Resource name here
Resource link here

Resource description here

[ ] My item is in the right category
[ ] My item is logically grouped below similar items
[ ] My item's name and description respects the conventions of the list
[ ] My item is awesome
[ ] My item is in line with the Tailwind brand usage guidelines
[ ] I have read and followed the contribution guidelines

Thanks!


[Bug]: Can't extend browserslist config

Version
System:
    OS: macOS 13.5.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 66.70 MB / 16.00 GB
    Shell: 3.6.1 - /opt/homebrew/bin/fish
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome Canary: 127.0.6503.0
    Safari: 16.6
  npmPackages:
    @rsbuild/core: ^0.6.15 => 0.6.15
    @rsbuild/plugin-react: ^0.6.15 => 0.6.15

Details
Hi here 👋
I want to report that when using rsbuild (see the repo with a fresh create-rsbuild project), we can't extends a browserslist config from the npm package through the package.json (same thing if I do through a .browserslistrc file):
"browserslist": [
  "extends @getaround-eu/browserslist-config"
]

error   Failed to build.
error   Cannot find module '@getaround-eu/browserslist-config'
    at Function.webpackEmptyContext [as resolve] (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/compiled/browserslist/index.js:1913:10)
    at Object.loadQueries (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/compiled/browserslist/index.js:1424:51)
    at Function.select (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/compiled/browserslist/index.js:1159:26)
    at /Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/compiled/browserslist/index.js:353:29
    at Array.reduce (<anonymous>)
    at resolve (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/compiled/browserslist/index.js:343:34)
    at browserslist (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/compiled/browserslist/index.js:445:21)
    at browserslistToESVersion (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+shared@0.6.15_@swc+helpers@0.5.3/node_modules/@rsbuild/shared/dist/getBrowserslist.js:92:59)
    at handler (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+core@0.6.15/node_modules/@rsbuild/core/dist/plugins/target.js:41:69)
    at async Object.call (/Users/me/Dev/projects/rsbuild-browserslist/node_modules/.pnpm/@rsbuild+core@0.6.15/node_modules/@rsbuild/core/dist/initHooks.js:45:22)
 ELIFECYCLE  Command failed with exit code 1.

Note: When I passe that config directory through the output.overrideBrowserslist property in the rsbuild.config.ts config file, it works correctly.
Reproduce link
https://github.com/CPatchane/rsbuild-browserslist-issue
Reproduce Steps
Just run pnpm dev or pnpm build

SWC uses browserslist-rs and its unreleased version supports the extends syntax:
https://github.com/browserslist/browserslist-rs/commit/04fcad2dcd30979c686f22eff289dbc8d6d6b47e
So we need to wait for browserslist-rs and SWC to release a new version, it will take some time.

SWC uses browserslist-rs and its unreleased version supports the extends syntax:
https://github.com/browserslist/browserslist-rs/commit/04fcad2dcd30979c686f22eff289dbc8d6d6b47e
So we need to wait for browserslist-rs and SWC to release a new version, it will take some time.

Oh thanks a lot for your quick actions and response, until then I guess passing through the output.overrideBrowserslist is a good workaround 👍

So we need to wait for browserslist-rs and SWC to release a new version, it will take some time.

@chenjiahan They just released the v0.16.0 version that support that feature :)
https://github.com/browserslist/browserslist-rs/releases/tag/v0.16.0

Nice 👍 The next step is to make SWC bump the dependency version, can you create an issue in the SWC repo?

Actually, it's already there https://github.com/swc-project/swc/pull/9023

There is some discussion about switching from browserslist-rs to oxc-browserslist, which may take some time to resolve.

They chose to upgrade browserslist-rc, so we should be good :)


Spike: Temporary storage for a secret store password.

closes #42
It's kinda a proposal for the implementation of temporary storage for a secret store password. New ideas, suggestions, etc, are very welcome.

The problem I am trying to solve is about the notebook usage. Most notebooks need access to the secret store where we keep all sorts of configurations. Some of them are sensitive, like for example the database connection details. Therefore the store is protected by a password. Currently, the user has to enter the password in every notebook, which is a bit tedious. The idea is to let the user enter the password and put it into an in-memory store. Ideally, we would also limit the lifespan of this storage.
Each notebook runs in its own process. There is no parent process that we can control. So the notebooks have to use the temporary store in some sort of cooperative manner. There is no way one process can pass some kind of multiprocessor object, like a Queue, to another process. Also, we don't want to use files. Jupyter notebooks have their own way of sharing data, but it involves writing it to a file. So we don't want to use it.

This is a spike. The Ticket #42 will be closed, this PR will stay open for later reference.