Fallback on deprecated SecTrustEvaluate function on macOS 10.13 and earlier

I am trying to use truststore on Mac OS X 10.11 (El Capitan). Both Python 3.10 and truststore would seem to work with this combination, but it is failing to load a symbol, which seems to have been introduced in 10.14 when verifying a certificate in a HTTPS request.
Are older macOS versions really tested with the current truststore?
Please let me know what additional debug info I can provide, but here is output from a Terminal with some useful steps to check if truststore is working properly:
Last login: Fri Oct 13 14:03:12 on ttys004
Mac-mini-ElCapitan-VM:~ jorik$ uname -a
Darwin Mac-mini-ElCapitan-VM.local 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 21 20:07:40 PDT 2018; root:xnu-3248.73.11~1/RELEASE_X86_64 x86_64
Mac-mini-ElCapitan-VM:~ jorik$ source ~/src/trust_test/venv/bin/activate
(venv) Mac-mini-ElCapitan-VM:~ jorik$ pip list
Package            Version
------------------ ---------
certifi            2023.7.22
charset-normalizer 3.3.0
idna               3.4
pip                23.2.1
requests           2.31.0
setuptools         68.1.2
truststore         0.8.0
urllib3            2.0.6
(venv) Mac-mini-ElCapitan-VM:~ jorik$ python
Python 3.10.13 (main, Oct 12 2023, 14:16:20) [Clang 8.0.0 (clang-8<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import requests
>>> R = requests.get('https://www.python.org/')
>>>
(venv) Mac-mini-ElCapitan-VM:~ jorik$ python
Python 3.10.13 (main, Oct 12 2023, 14:16:20) [Clang 8.0.0 (clang-8<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import truststore
>>> truststore.inject_into_ssl()
>>> import requests
>>> R = requests.get('https://www.python.org/')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/requests/api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 790, in urlopen
    response = self._make_request(
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 467, in _make_request
    self._validate_conn(conn)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1092, in _validate_conn
    conn.connect()
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/connection.py", line 642, in connect
    sock_and_verified = _ssl_wrap_socket_and_match_hostname(
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/connection.py", line 783, in _ssl_wrap_socket_and_match_hostname
    ssl_sock = ssl_wrap_socket(
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/util/ssl_.py", line 469, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls, server_hostname)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/urllib3/util/ssl_.py", line 513, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/truststore/_api.py", line 104, in wrap_socket
    _verify_peercerts(ssl_sock, server_hostname=server_hostname)
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/truststore/_api.py", line 300, in _verify_peercerts
    _verify_peercerts_impl(
  File "/Users/jorik/src/trust_test/venv/lib/python3.10/site-packages/truststore/_macos.py", line 437, in _verify_peercerts_impl
    sec_trust_eval_result = Security.SecTrustEvaluateWithError(
  File<EMAIL_ADDRESS>line 387, in __getattr__
    func = self.__getitem__(name)
  File<EMAIL_ADDRESS>line 392, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: dlsym(0x7fc3d9462db0, SecTrustEvaluateWithError): symbol not found
>>>

From this page, it seems  SecTrustEvaluateWithError is available since 10.14? Or maybe I'm misreading the documentation?

@versionbayjc Thanks for opening this issue. We haven't tested with older macOS and I see what happened. To support that version of macOS we'd need to use the deprecated SecTrustEvaluate function. I'm going to edit this issue's title to reflect that.

Hellos.
I started a PR here: https://github.com/sethmlarson/truststore/pull/156 to use the deprecated SecTrustEvaluate function.
Would love any help/pointers/testing :)
ps. AFAIK it seems this issue triggered pip dropping 10.9-10.13 support, which triggered python itself in a patch release 3.12.6 dropping support, which then caused cibuildwheel to drop support, which caused other packages to not be built with 10.9-10.13 support.

Thanks for working on this! I left a comment in the PR.

I can also confirm that after using pip install git+https://github.com/sethmlarson/truststore.git instead of installing truststore 0.9.2 from PyPI, the steps that caused the symbol not found earlier are now working correctly on my 10.11 El Capitan VM.
Thanks @sethmlarson, @ThomasWaldmann, @illume !!


Scam Account Submission

Duplicate Submissions

[X] Yes, I checked that the account name is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://www.youtube.com/watch?v=pDPV3ll-4AQ&lc=UgzO2qDLniF7EIwbeZN4AaABAg
(Optional) Screenshot of comments referencing the scam account
No response
(Required) List of the scam account names
staring

Not really a scam account imo

@Firecul If you think that it shouldn't be added, I understand. I'm not even 100% sure on this one.

Yea this one seems like a generic name, not someone promoting a scam


Link to relevant docs page in warning messages

I'm using latest Chrome and latest workbox rc.0
I'm importing Workbox as so:
const main = async () => {
  const wb = new Workbox('/static/service-worker.js');
  await wb.register();
}

main()

But it complains:
The current page is not in scope for the registered service worker. Was this a mistake?
It turns out that scopeURLBasePath is set to /static which prevents proper registering. I think it should not matter whether service worker is inside static directory or not.

Or is it a requirement?

The warning is to help prevent lots of accidental mistakes we've seen in the past with service worker scope mismatch.
If you register your service worker at the URL /static/service-worker.js, then that service worker will never be able to control requests on page /index.html. Its scope only lets it control pages under /static/*. You can read more about the scoping rules here.
This is not a Workbox requirement, it's a service worker requirement. Does that help explain why the warning is there?

Yes, but I have two notes:

The "scoping rules" page you've linked to tells "You can also set an arbitrary scope by passing in an additional parameter when registering." which can be misleading as it suggests I can override /static scope to /. A documentation update would be helpful there that for example tells instead "You can also reduce scope that service worker can control by passing in an additional parameter when registering."
I really like to warnings React shows in console because they link to relevant pages where I can learn more about these issues. Maybe Workbox could adopt this as well? For example you could link to the page you've just linked to directly in warning message as shortened link.

Agreed, we're planning to eventually link these warnings to documentation pages.

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


port to tokio

@alexcrichton if you're around, it'd be great to get a release with this. I don't think it's a breaking change as far as I can tell?

Published!


fetch serialised classification data from read replica

move this read query load off the primary db to the replica
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

Just an initial thought, I'm thinking it'd be good to add the classification_serializer_data_from_replica flag to this wiki page for future reference: https://github.com/zooniverse/panoptes/wiki/Feature-Flags

Added the flag docs - https://github.com/zooniverse/panoptes/wiki/Feature-Flags#classification_serializer_data_from_replica-on

Just one question - why is classification data a good candidate when it comes to retrieving data from the read replica? I vaguely agree with the choice, but off the top of my head can't think of the places where the api/classifications endpoint is hit in PFE and whether we need the data retrieved at that point to be the most-up-to-date data.

These end points aren't really used in PFE, rather they are used by some research teams to ingest their project classification data to their research databases for their own analysis.
That said the /incomplete route is used by ASM (i believe) to save a users partially completed classification data so they can access it at a later point. The ASM project is complete so not using this feature any more.

Awesome, thanks for the info!


Append conda tzdata location instead of overriding

This matches the behaviour of the zoneinfo module in python 3.9

conda-forge::python=3.9 builds only use conda-forge::tzdata:
$ python -c 'import sys, sysconfig; print(sys.version, sysconfig.get_config_var("TZPATH"), sep="\n")'
3.9.0 | packaged by conda-forge | (default, Oct 14 2020, 22:59:50)
[GCC 7.5.0]
/opt/conda/envs/tmp/share/zoneinfo:/opt/conda/envs/tmp/share/tzinfo

That isn't intended.

The duplication is because we have https://github.com/conda-forge/python-feedstock/blob/master/recipe/build_base.sh#L239 as well as https://github.com/conda-forge/python-feedstock/blob/master/recipe/build_base.sh#L444.

Yep, see https://github.com/conda-forge/python-feedstock/issues/403

From what you wrote, I assume you don't want https://github.com/conda-forge/python-feedstock/blob/master/recipe/build_base.sh#L239 but only https://github.com/conda-forge/python-feedstock/blob/master/recipe/build_base.sh#L444 ?
However, what is the advantage to have ours looked last? We probably have more up to date information than the system.

We probably have more up to date information than the system.

Yep. My ubuntu only offers 2020a, we are shipping 2020d.

I think it would be surprising for a user to install the latest tzdata but have Python use an older system version in preference to what the user installed.
I was thinking of refactoring the logic to be:
def reset_tzpath(to=None):
    global TZPATH

    tzpaths = to
    if tzpaths is not None:
        if isinstance(tzpaths, (str, bytes)):
            raise TypeError(
                f"tzpaths must be a list or tuple, "
                + f"not {type(tzpaths)}: {tzpaths!r}"
            )

        if not all(map(os.path.isabs, tzpaths)):
            raise ValueError(_get_invalid_paths_message(tzpaths))
        base_tzpath = tzpaths
    else:
        env_var = os.environ.get("PYTHONTZPATH", None)
        if env_var is not None:
            base_tzpath = _parse_python_tzpath(env_var)
        else:
            base_tzpath = [os.path.join(sys.base_prefix, "share", "zoneinfo")]
            if sys.platform != "win32":
                extra_tzpath = [
                    "/usr/share/zoneinfo",
                    "/usr/lib/zoneinfo",
                    "/usr/share/lib/zoneinfo",
                    "/etc/zoneinfo",
                ]
                extra_tzpath = extra_tzpath.sort(
                    key=lambda x: not os.path.exists(x)
                )
                base_tzpath += extra_tzpath

    TZPATH = tuple(base_tzpath)

    if TZPATH_CALLBACKS:
        for callback in TZPATH_CALLBACKS:
            callback(TZPATH)

Thoughts?

...but as @ocefpaf mentioned, since tzdata is a dependency none of the others would then ever be chosen because the first entry would always be present.


breaking change: Add more KCL reserved words

Addresses #4486. (not closed yet)
Add more reserved words to KCL. These cannot be used for user-defined variable or function names.
We may never do anything special with these, but it gives us the option.

_ (underscore)
new
interface
record
struct
object
as
array

Note: type and from weren't added yet due to collisions, like usage in the stdlib's ImportFormat. See the issue for details.
Implementation
winnow had a limit to the number of things that could be in an alt, so I used this as a trigger to change the implementation to parse full words and look them up in a hash map. This should be faster. I used the FNV hash function since it's faster than the hash function in std::collections::HashMap, and we don't need to worry about user input causing collisions. The members in the hash map never change.

LGTM -- will this break the KCL samples? If so, we should change them first.

https://github.com/KittyCAD/kcl-samples/pull/115


Local run and License

Hi, I have two questions:

Is it possible to run locally instead on the cloud?
What is the license of the software?

Hi mbenencase,
Thank you for your questions. Below are our answers:

Our library can run on both local and cloud machines, but we recommend that you prioritize local machines due to higher performance
Our library is released under MIT license


Does Quant-Noise Drops Weights Permanently?

❓ Questions and Help
Before asking:

search the issues.
search the docs.

What is your question?
In the source code of quant_noise, it looks like you apply the dropout mask directly on weight.data, without storing a copy of the original weight matrix. doesn't that lead to permanent dropping of weights?
Code
https://github.com/pytorch/fairseq/blob/master/fairseq/modules/quant_noise.py

What have you tried?
What's your environment?

fairseq Version (e.g., 1.0 or master):
PyTorch Version (e.g., 1.0)
OS (e.g., Linux):
How you installed fairseq (pip, source):
Build command you used (if compiling from source):
Python version:
CUDA/cuDNN version:
GPU models and configuration:
Any other relevant information:

relevent issue
#3195


Directly read ADBC to Spark Dataframe

What feature or improvement would you like to see?
Similar to JDBC, something like:
jdbcDF = spark.read \
    .format("adbc") \
    .option("url", "adbc:postgresql") \
    .option("dbtable", "schema.tablename") \
    .option("user", "username") \
    .option("password", "password") \
    .load()

That way help to leverage ADBC in Spark compute environment.

I think this is should be a Spark feature request?
What I would like to do here is provide a JNI driver that can leverage the better-optimized postgresql/snowflake drivers from Java, though.

I think this should be a Spark feature request?
What I would like to do here is provide a JNI driver that can leverage the better-optimized postgresql/snowflake drivers from Java, though.

Right, it should be a spark feature. I'm posting here to check if it is a meaningful feature, and someone from the arrow team is already working on it. :)
What do you mean by JNI driver?

I don't believe anyone is working on this. Best to take it to the Spark community.
The ADBC driver for postgres, snowflake in Java just wraps JDBC. It doesn't provide any benefits. If we had JNI bindings to the C++/Go drivers we might see some performance benefits.

make sense. let me post it in the Spark repo.

@HaoXuAI hey, fancy seeing you here 😄 I've started this a while ago and then abandoned it (changed jobs and was no longer using Dremio). Can help you bring it back from the dead if you have a use case.

Hey @tokoko ! Great to see you here as well. Not a direct use case on work, but thinking about using ADBC in a project to read data on spark. Do you want to directly contribute to spark or keep it a plugin?

@HaoXuAI My goal at the time was to get it to mostly working condition as a plugin and then contribute, but we can do it either way.
@lidavidm Even with JNI drivers, the adbc java interface itself will still look the same, right? spark data source implementation will be independent of how drivers are implemented.

Yes, the idea of JNI would be to implement the same Java-side interface


ActiveRecord 5.0+ incompability

Since ActiveRecord 5.0 the "[]" method is not called via method_missing: https://github.com/rails/rails/blob/v5.0.0/activerecord/lib/active_record/relation/delegation.rb#L39
So accounts[:outstanding, :liability, true] raises "ArgumentError: wrong number of arguments (given 3, expected 1..2)" exception.
I think that https://github.com/vitaly/debitcredit/blob/master/app/models/debitcredit/account.rb#L25 has to be renamed and "[]" can be an alias only (for backward compatibility)

I have created workaround: https://github.com/barges/debitcredit/commit/78285a237137305961f4a5faa915ef38bb18d021
It works


Page socket-binding;name=standard-sockets not found.

Socket Bindings -> standard-sockets produce this error

The page is not yet implemented.


Bad boolean Flag value is interpreted as Argument

Using boolean Flag, and trying to assign a value to it is not reported as an error, instead the value is interpreted as an Argument of the program:
func main() {
	var (
		app = kingpin.New(filepath.Base(os.Args[0]), "My App.").DefaultEnvars()
		testBool = app.Flag("test-bool", "test-bool").Bool()
		//args = app.Arg("my args", "arg list").Required().Strings()
	)
	kingpin.MustParse(app.Parse(os.Args[1:]))
	fmt.Printf("test-bool=%s\n",strconv.FormatBool(*testBool))
	//fmt.Printf("args=%s\n",*args)
}

This would report an error if you run it (expected):
go run main.go --test-bool=false --> main: error: unexpected false, try --help
Now if you remove the comments to run the program with Arguments, here is what you get:
go run main.go --test-bool=false myArg
test-bool=true
args=[false myArg]

Not only the list of arguments contains the string value false but the boolean is set to true.

Kingpin doesn't support this approach, you can use --no-test-bool to negate a flag.


[BUG] [v1.4.1-rc1] Physical node down test failed

Describe the bug (🐛 if you encounter this issue)
From https://longhorn.github.io/longhorn-tests/manual/pre-release/node/physical-node-down/
Set node-down-pod-deletion-policy = delete-deployment-pod and create deployment using PVC of 3 replicas volume, shutdown the node which pod attached to, the replaced pod will stuck at ContainerCreating status forever
Not see in v1.4.0
To Reproduce
Steps to reproduce the behavior:

Deploy longhorn with 3 replicas
Set node-down-pod-deletion-policy = delete-deployment-pod
Create volume with 3 replicas then create PV and PVC of this volume
Create a deployment using the volume PVC
After pod running, shutdown the node which node attached to
Old pod terminated success but replaced pod stuck at ContainerCreating
And the volume stuck at attaching also

Expected behavior
Volume attach to new node success and new pod running
Log or Support bundle
supportbundle_ec3950cf-3204-4890-b25e-3b073d005377_2023-03-03T04-08-28Z.zip
Environment

Longhorn version: v1.4.1-rc1
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:  v1.24.7+k3s1

Number of management node in the cluster: 1
Number of worker node in the cluster: 3

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): AWS
Number of Longhorn volumes in the cluster: 1

Additional context
If the volume have 2 replicas which was the test step in test case

No replica located on shutdown node, the replaced pod will create success
1 replica located on shutdown node, the replaced pod will stuck at ContainerCreating and volume stuck at attaching

This should be duplicated at https://github.com/longhorn/longhorn/issues/5464.
cc @weizhe0422 @longhorn/dev-data-plane

Verified in longhorn manager v1.4.x head 33359f with test steps
Result Pass
After https://github.com/longhorn/longhorn-manager/pull/1737 merged,  set setting node-down-pod-deletion-policy = delete-deployment-pod then shutdown node which deployment pod attached to,  there will be a replaced pod running and volume will attach to another node success


Upgrade webmock to version 1.24.5

Libraries.io has found that there is a newer version of webmock that this project depends on.
More info: https://libraries.io/rubygems/webmock/1.24.5

Fixed by @vitortalaia in #232


colicious.ga domain is dead

The http://colicious.ga/ URL es not working anymore.
Thanks so much for your work. It is so appreciated

Thank you for letting me know. The project is now available at kbrsh.github.io/colicious.


Fixed Multi Row Lazy loading and Multi Row order

Fixed the issue with the multi row bug.
And also the Multi Row order when choosing fill "Row" to be :+1:
1 | 2 | 3
4 | 5|  6
7 | 8 | 9

With 6 items order like a mess
1 | 3
2 | 6
4 | 5

Hi all, is this PR being considered? It would really help with a project I am working on.

This is a big issue for me, I can't use the slider if it can not do columns and row order properly.  I see the fixes, but how do I get it in a simple swiper.js file?

Closing as outdated and incompatible with current version of Swiper


SSH Auth failed with generated SSH Key

Thanks for this awesome Vagrant box! I had a little trouble getting it to work correctly the first go around because it would fail to authorize the SSH key. In the Vagrant up command it would say that it detected the insecure private key and then would regenerate a new one. However after it imported the new SSH key and try to authenticate it would always say that it failed. I was able to fix this by adding config.ssh.insert_key = false to the Vagrantfile and all seems to be working now. I am wondering if other people are running into this issue as well.

Hi @Yamaha32088 , I can't say I've seen that behavior before, but it's been a while since I've used this box so a newer version of Ubuntu might be causing it.  Actually, IIRC Ubuntu has been moving to stop using insecure hashes like SHA1 which might be the reason.  Can you send a pull for that config change?

I created a pull request.

Thanks for the pulls @Yamaha32088 !


SharedNotes activity: Text content overflows out of the notes container

hey, @llaske I came across a functionality break in the SharedNotes activity. Whenever we try to write text more than the size of the notes container it overflows out of the container, the scrollbar still works and we can view the entire text by dragging the scrollbar but as soon as the notes container is filled the text overflows out of it.
I have attached the screenshots for the same, please look and review them and give me your thoughts. If you find it as a issue then I would like you to assign this issue to me :)

This activity is useful for small notes. It has no sense for long text.

Sir, I have an idea. We can limit the text length in the notes container so that they do not exceed the container's limit. This will prevent our UI from breaking, and an alert can be displayed when the limit is reached.

Sir, I have an idea. We can limit the text length in the notes container so that they do not exceed the container's limit. This will prevent our UI from breaking, and an alert can be displayed when the limit is reached.

Good for the UX ! 👍


MM 20545 migrate components/user settings/display to type script

Summary

Migrate 'components/user_settings/display' module and associated tests to TypeScript
Rename the files to their associated TypeScript extensions (ie. js to ts, jsx to tsx)
Update any components using those to the correct imports
Fix any errors generated by the TypeScript compiler. You can run make check-types to display any errors.

Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/13696
JIRA Ticket https://mattermost.atlassian.net/browse/MM-20545

Hey @sridhar02, thanks for the pull request!
It looks like the PR is currently failing type check, make sure to run make check-types before you push up your changes. It looks like some additional work will need to happen to fully convert this module over to TypeScript.
Let us know if you need any help doing so.

@devinbinnie, Thanks I will ask, if there is an issue related to issue and I will try to resolve the errors as soon as possible.

@devinbinnie, Thanks I will ask, if there is an issue related to issue and I will try to resolve the errors as soon as possible.

I'm not sure what you mean here, are you interested in other TypeScript conversion tickets/PRs?

@devinbinnie, Thanks I will ask if there is an issue related to issue and I will try to resolve the errors as soon as possible.

I'm not sure what you mean here, are you interested in other TypeScript conversion tickets/PRs?

Sorry, my bad, I said I would ask your help if I need anything related to PR, there are a couple of tickets, I am working on , after those, I will again work on Typescript issues.

Hello @sridhar02 thanks for your contribution! I ran Cypress tests against this PR and it's failing to some user settings cases and looked like related to the changes here. Note that it's now failing on master. See https://mm-cypress-report.s3.amazonaws.com/709-webapp-pr-5988-327f8ca/mochawesome.html for reference. Could you please take a look at the failing tests? Let me know if you need help.

@devinbinnie can you help me here, while verifying the cypress test failing , i found that unit tests are also failing in two places is user_setting_display.tsx file, in which userAutomaticTimezone is one of them, observed that it is boolean used for the input element attribute which always a boolean but in redux it defined like this, I think I need to change the redux type which will solve the error here what are your thoughts?
export type UserTimezone = {
    useAutomaticTimezone: boolean | string;
    automaticTimezone: string;
    manualTimezone: string;
};

https://github.com/mattermost/mattermost-redux/blob/d465f41cf007b05e95b7d2a83d1234561a87afe4/src/types/users.ts#L76

@devinbinnie can you help me here, while verifying the cypress test failing , i found that unit tests are also failing in two places is user_setting_display.tsx file, in which userAutomaticTimezone is one of them, observed that it is boolean used for the input element attribute which always a boolean but in redux it defined like this, I think I need to change the redux type which will solve the error here what are your thoughts?
export type UserTimezone = {
    useAutomaticTimezone: boolean | string;
    automaticTimezone: string;
    manualTimezone: string;
};

https://github.com/mattermost/mattermost-redux/blob/d465f41cf007b05e95b7d2a83d1234561a87afe4/src/types/users.ts#L76

@sridhar02 I think the string | boolean type is being used because our server is sending down the value as a string but our app only treats it as a boolean. There's a bit more at play here.
I think for your case, we can just force the type to be a boolean by wrapping it in a Boolean().

@saturninoabril @devinbinnie I have fixed all the errors and cypress tests are also rectified, can you review the PR?


raise_errors doesn't work when chunked=True

Steps to reproduce:

Make a query that results in an error. In my case, I made a query that would cause a query-timeout limit exceeded error from the server
Set chunked=True

Expected result:
influxdb.exceptions.InfluxDBClientError: query-timeout limit exceeded
Actual result:
A result set is returned containing results from all chunks that arrived prior to the error. No exception is raised, and it is not possible to check for the error condition from the calling function.
Suggested fix
This code is being reworked in #531, but for now this change solves the issue at client.py:331
    @staticmethod
    def _read_chunked_response(response, raise_errors=True):
        result_set = {}
        for line in response.iter_lines():
            if isinstance(line, bytes):
                line = line.decode('utf-8')
            data = json.loads(line)
            for result in data.get('results', []):
+               if result.get('error'):
+                   raise InfluxDBServerError(result.get('error'))
                for _key in result:
                    if isinstance(result[_key], list):
                        result_set.setdefault(
                            _key, []).extend(result[_key])
        return ResultSet(result_set, raise_errors=raise_errors)

Just got burned by this, my queries were timing out and I was silently missing data.
Was going to propose a similar fix. Any reason to not make this change?


proxysql: 2.4.3 -> 2.4.4

Description of changes
https://github.com/sysown/proxysql/releases/tag/v2.4.4
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md

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

1 package built:

proxysql


json: Skip unknown fields on parsing

Skip child objects and arrays that are not specified in the given object descriptor when parsing a JSON input string.
This patch adds support for extra child arrays which previously were not supported by the parser as opposed to additional child objects.
Copied from: https://github.com/zephyrproject-rtos/zephyr/pull/47989

This should fix the "graph hydration error" when FW is confronted with a meta file with new fields in it.

The compilation fails with
/data/git/scorpio-fw/zephyr/lib/os/json.c:395:67: error: 'JSON_TOK_ARRAY_START' undeclared (first use in this function); did you mean 'JSON_TOK_LIST_START'?
  395 |  if (kv->value.type == JSON_TOK_OBJECT_START || kv->value.type == JSON_TOK_ARRAY_START) {
      |                                                                   ^~~~~~~~~~~~~~~~~~~~
      |                                                                   JSON_TOK_LIST_START
/data/git/scorpio-fw/zephyr/lib/os/json.c:395:67: note: each undeclared identifier is reported only once for each function it appears in
/data/git/scorpio-fw/zephyr/lib/os/json.c:396:46: error: 'struct json_obj' has no member named 'lex'; did you mean 'lexer'?
  396 |   while (field_count > 0 && lexer_next(&obj->lex, &kv->value)) {
      |                                              ^~~
      |                                              lexer
/data/git/scorpio-fw/zephyr/lib/os/json.c:403:9: error: 'JSON_TOK_ARRAY_END' undeclared (first use in this function); did you mean 'JSON_TOK_LIST_END'?
  403 |    case JSON_TOK_ARRAY_END:
      |         ^~~~~~~~~~~~~~~~~~
      |         JSON_TOK_LIST_END

If we intend to do this, we need to open a PR that's clearly identified as a "back port" PR (see, for example, #73) and as much as possible, git cherry-pick the changes rather than "copying" them. If this draft PR reaches a usable state, I would be happy to assist with that finalization.

I fixed the compilation issues and confirm that this works now. @berendo I would appreciate if you could assist with bringing this into the form you imagine. Only a few names had to be changed from the original commit.

Only a few names had to be changed from the original commit.

Yup, please give me an hour or so to sync our fork with the upstream, so that the commit that merged the PR we are "copying" is in our history and we can just git cherry-pick it (with minimal modifications).

Closed in lieu of #81 - thank you for digging this up and testing it @trojahner.


SW-5809 Toast error for no boundary

#3197  👈
main

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

Join @tommylau523 and the rest of your teammates on  Graphite


Wrong post dates

Nevermind, I just realised the dates are manually specified.

I just added that for testing purposes. I will edit the post.


Issue 536: Replace ActivityIndicator with ProgressView

This pull request replaces UIActivityIndicatorView with SwiftUI ProgressView.
It should be merged after #581 is merged since ProgressView is only compatible with iOS 14.0+
Closes #536

@ria-heikkila #581 has now been merged - could you fix the conflicts and we can get this merged!

@0xTim  done!


Do not use RAW socket on Unix to allows unprivileged user usage

On Unix platforms, SOCK_RAW usage is reserved to privileged users.
Fix "Operation not permitted" error on Linux and macOS.

Seems the tests faile with this messege:
thread 'basic' panicked at 'called `Result::unwrap()` on an `Err` value: IoError { error: Os { code: 35, kind: WouldBlock, message: "Resource temporarily unavailable" } }', tests/tests.rs:12:83

Seems the tests failed on macOS withoud sudo with this messege:
thread 'basic' panicked at 'called `Result::unwrap()` on an `Err` value: IoError { error: Os { code: 35, kind: WouldBlock, message: "Resource temporarily unavailable" } }', tests/tests.rs:12:83

That's odd I cannot reproduce on my M1 🤔

I'm using a intel mac book with big sur:
ProductName:    macOS
ProductVersion: 11.6
BuildVersion:   20G165

So this is a OS specified issue? But the tests won't passed on Linux too (Arch OS with latest kernel version which I have forgoten...)

IoError { error: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" } }

I have test this MR on my linux (arch) box, and it not works. According to https://stackoverflow.com/a/20105379 , the unprivilege icmp package is not works out of box on linux.
I think we should add a option or a new function to use the unprivileged ping.

I see. I tried this change on macOS and it worked. I'll try testing it on Linux if I can get my hands on one.

I have new idea, we should keep both the privileged / unprivileged implementations for specified usage. And a basic ping function as a alias to the new privileged_ping for backword compatibility. In future releases, we can use the most suitable for target platform.
Is this implemented in #11 , does anyone have suggestions?

I have new idea, we should keep both the privileged / unprivileged implementations for specified usage. And a basic ping function as a alias to the new privileged_ping for backword compatibility. In future releases, we can use the most suitable for target platform.
Is this implemented in #11 , does anyone have suggestions?

I think that's a great idea, will close this :+1:

I guess this is why I have to set PrivateUsers=false on systemd
Reporting this back to https://github.com/valeriansaliou/vigil/issues


waterfall

waterfall doesn't change color of space between lines.

fix by setting 'patchasBack' to true.
darkBackground('patchasBack', true)


Propogate greenplum removals to master

@mikecafarella

It looks like it failed on a fluke from a Scala library failing to download. The same commit a8b6f71 has a green build on Develop.
@mikecafarella Is merging OK?

@mikecafarella Build is green after no changes.


Replace gulp-eslint with eslint's CLIEngine

For #5449.
I replaced gulp-eslint in favor of the (more powerful and customizable) CLIEngine. This allows ESLint to use the --cache option, which brings npm run eslint from ~18s to ~2s.
Overall, the two affected tasks now look much less "nodey" and gulpy".
@mramato: It feels wrong to throw an Error, but it seems to be how you "fail" gulp tasks. Also, is it OK that this does not return a Promise or stream? Thanks!

Sounds cool.
Will CI also have the performance impact or is this just for incremental runs?

Unfortunately, just for incremental runs

Gotcha.

@mramato Mind doing a final review?

@omh1280 This PR is totally fine, but I ended up opening #5502 to replace this PR instead.  Let me know what you think and if you have any questions about it.


sqlalchemy-oso 0.27.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin please rerender

Blocked by https://github.com/conda-forge/oso-feedstock/pull/29


#NGG-125|publish bower components to npm as well

Change all bower components to private: false & assign our local npm, then publish it via wnpm.

one more thing - we should also sync between bower and npm versions, should I write a (temporary, at least until we'll completely move to npm) grunt task for that?

why is it important that they'll be synced?

the moving we'll be smoother, for example those who use wix-* with version: ^2.0.0 won't be able to get this version in our npm because it doesn't exist (all major versions are currently 0), they'll have to change the version number as well (to ^0.0.0). also semantic reasons and not confusing people.

I had to comment out the wnpm-release cuz it caused a lot of failures in CI. For some reason the bumping of the node version didn't work. @roymiloh plz investigate. Example: http://ci.dev.wix/viewLog.html?buildId=15422085&buildTypeId=Wix_Angular_WixAngular&tab=buildLog


create nop command test

Improving the test coverage.

Coverage increased (+0.22%) when pulling 7726acca6331bde61d923cee3de6afc1ea801837 on pongsanti:master into 2ece8413769443a04c12808b8377e77667e82559 on limetext:master.

LGTM, thanks.


Context  of parameters of a network in GPU is shown CPU

In the example predict-with-pretrained-model.ipynb if I do the following
# Load the pre-trained model
prefix = ROOT_PATH+"Inception_BN"
num_round = 39
model = mx.model.FeedForward.load(prefix, num_round, ctx=mx.gpu(), numpy_batch_size=1)

for i in model.arg_params.values():
    print i.context

All the output is cpu(0) even I guess the code is executed in GPU while prediction. I guess this is a bug.

All the parameters  of mx.model resides in are on cpu and will be copied to GPU before training and copied back after it finishes. This makes things easier to load  GPU trained models into CPU.

Thanks for the explanation.


Fix filtering of actions related to auto-scaling machine pools

https://issues.redhat.com/browse/ACM-7813

/test unit-tests-sonarcloud


Update dependencies, and format files using refmt

Hey @cullophid, I would like to add some new functions (for example fontFace), but first I think we need to clean up in this repo.
This PR updates dependencies to the latest versions and formats all reason files using the latest version of refmt.

Hi Thanks for the dependency updates!
refmt is disabled on purpose, so please do a PR without it :)

@cullophid I'm wondering, is there any reason why it's disabled? I think using refmt is beneficial to all contributors and it standardizes the code written by the developers

Yes there are a few.
I think refmt/prettier/etc. are great tools!
I use them frequently when ever i have large blocks of code with botched formatting. e.g.
Having said that I generally don't find that these tools improve the code. Actually i find that in some edge cases they can make it slightly less readable.
I dont care too much how developers (either my employees or OSS contributors) format the code as long as its still easy to read. Some things have a big impact:
let user = {
  name: "Andreas",
  email<EMAIL_ADDRESS>};
let user =
 { name= "Andreas"
  , email=<EMAIL_ADDRESS>  }

others are completely irrelevant:
let id = (v) => v;
let id = v => v;

I do care that developers are mindful about how their codes conveys the message they want to tell. formatting can be a tool for this (not the most important one but still a tool).
I would love it if refmt had an option to only format the lines that you just changed. then people who wanted to use it could, but it would not be forced on anyone else. Sadly to my knowlege this is not possible.

I am also seeing a worrying trend forming around formatting tools. I see a lot of developers argue that by using formatters we dont have to argue about formatting any more.
We never actually had to argue about formatting. We could have just accepted that people write code in slightly different ways. As long as the differences do not have significant negative impact on the code just let it go.
It seems to me that often formatters are not a way for teams to agree on formatting, but for individuals to force their preference on the whole team.
Trying to solve people problems with a code tool is a really bad idea!

leave out refmt

sure, will do that later today :ok_hand:
I decided to use it because there are few places where the code looks incoherent.
In general, I agree with what you just said, but on the other hand, I think in the project like this, where there are contributors with the different coding style, the tool like refmt/prettier/whatever might be helpful. Arguing about the formatting style is merely waste of time.
Anyway, thank you for more clarification about that 😉

@cullophid ✔ done :)

Thanks!!

thank you! 🎉


Crush, because of the performance?

Describe the bug
Sometimes, when I open extension, It crushes with
"Uh-oh, Gumbo is not responding anymore! Please use the button below to reload the extension."
To Reproduce
Steps to reproduce the behavior:
Press the extension button
Expected behavior
fast opening
Desktop (please complete the following information):

Windows 10 19044.1706
Google Chrome 102.0.5005.63

Additional context
Yes, my laptop is rather old (Inter Core i5-4200U with 16 GB RAM, Radeon HD 8670M with 1 GB dedicated VRAM, Samsung SATA SSD), but still extension needs some optimisations (it's much heavier than good old Twitch Now), it also happens on my Linux which is much faster.
One thing that already comes to mind as one of issues - we don't need to see "real-time tracking of seconds of all my 50 followed online streams", just do it like in Twitch Now - brief snapshot of online time until refreshing.

It's being caused by the background service worker randomly breaking, putting the extension in a limbo state. It's a known issue, which is unfortunately on the hands of the Chromium team: https://bugs.chromium.org/p/chromium/issues/detail?id=1271154


Error: Build Starter personalization-builder-io

Just wanted to try out the builder-vercel starter.
https://vercel.com/templates/next.js/personalization-builder-io
Following Error was thrown, during build stage:
[10:24:00.585] Failed to compile.
[10:24:00.585]
[10:24:00.587] ./pages/_middleware.tsx:10:59
[10:24:00.587] Type error: Argument of type 'NextCookies' is not assignable to parameter of type 'Record<string, string>'.
[10:24:00.588]   Index signature for type 'string' is missing in type 'NextCookies'.

Full Build Log from Vercel
[10:23:10.713] Running build in San Francisco, USA (West) – sfo1
[10:23:10.756] Cloning github.com/luctrate/personalization-test-builder (Branch: main, Commit: 994e176)
[10:23:10.902] Previous build cache not available
[10:23:11.823] Cloning completed: 1.067s
[10:23:11.983] Running "vercel build"
[10:23:12.559] Vercel CLI 28.15.3
[10:23:12.866] Installing dependencies...
[10:23:13.255] yarn install v1.22.17
[10:23:13.305] info No lockfile found.
[10:23:13.315] [1/4] Resolving packages...
[10:23:15.138] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client ><EMAIL_ADDRESS>The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws    For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
[10:23:15.173] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client ><EMAIL_ADDRESS>Use @graphql-toolkit/* monorepo packages instead. Check https://github.com/ardatan/graphql-toolkit for more details
[10:23:15.287] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client ><EMAIL_ADDRESS>This is a stub types definition. graphql provides its own type definitions, so you do not need this installed.
[10:23:15.348] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client > graphql-toolkit ><EMAIL_ADDRESS>GraphQL Import has been deprecated and merged into GraphQL Tools, so it will no longer get updates. Use GraphQL Tools instead to stay up-to-date! Check out https://www.graphql-tools.com/docs/migration-from-import for migration and https://the-guild.dev/blog/graphql-tools-v6 for new changes.
[10:23:15.373] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client ><EMAIL_ADDRESS>This package has been deprecated and now it only exports makeExecutableSchema.\nAnd it will no longer receive updates.\nWe recommend you to migrate to scoped packages such as @graphql-tools/schema, @graphql-tools/utils and etc.\nCheck out https://www.graphql-tools.com to learn what package you should use instead
[10:23:15.464] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client > graphql-tools ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[10:23:15.464] warning @builder.io/personalization-utils > @builder.io/admin-sdk > graphql-typed-client > graphql-toolkit > @kamilkisiela/graphql-tools ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[10:23:16.066] warning @builder.io/react > create-react-context > fbjs ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
[10:23:18.210] warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
[10:23:20.870] [2/4] Fetching packages...
[10:23:45.670] [3/4] Linking dependencies...
[10:23:45.673] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[10:23:45.673] warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[10:23:45.673] warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[10:23:45.674] warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[10:23:45.675] warning<EMAIL_ADDRESS>> @builder.io/admin-sdk > graphql-typed-client ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[10:23:45.676] warning<EMAIL_ADDRESS>><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
[10:23:45.677] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[10:23:45.677] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[10:23:45.677] warning "@vercel/fetch ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[10:23:45.677] warning "@vercel/fetch ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[10:23:55.406] [4/4] Building fresh packages...
[10:23:55.491] success Saved lockfile.
[10:23:55.498] Done in 42.25s.
[10:23:55.540] Detected Next.js version: 12.3.4
[10:23:55.543] Running "yarn run build"
[10:23:55.766] yarn run v1.22.17
[10:23:55.823] $ next build
[10:23:56.414] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[10:23:56.415] This information is used to shape Next.js' roadmap and prioritize features.
[10:23:56.415] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[10:23:56.415] https://nextjs.org/telemetry
[10:23:56.415]
[10:23:56.579] info  - Linting and checking validity of types...
[10:23:57.242] We detected TypeScript in your project and reconfigured your tsconfig.json file for you. Strict-mode is set to false by default.
[10:23:57.243]
[10:23:57.243] The following suggested values were added to your tsconfig.json. These values can be changed to fit your project's needs:
[10:23:57.243]
[10:23:57.243] 	- incremental was set to true
[10:23:57.244]
[10:23:59.187]
[10:23:59.188] ./pages/api/attributes.ts
[10:23:59.188] 11:1  Warning: Assign arrow function to a variable before exporting as module default  import/no-anonymous-default-export
[10:23:59.188]
[10:23:59.188] info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
[10:24:00.585] Failed to compile.
[10:24:00.585]
[10:24:00.587] ./pages/_middleware.tsx:10:59
[10:24:00.587] Type error: Argument of type 'NextCookies' is not assignable to parameter of type 'Record'.
[10:24:00.588]   Index signature for type 'string' is missing in type 'NextCookies'.
[10:24:00.588]
[10:24:00.588]    8 |
[10:24:00.588]    9 |   if (!excludededPrefixes.find((path) => url.pathname?.startsWith(path))) {
[10:24:00.588] > 10 |     const rewrite = getPersonalizedRewrite(url.pathname!, req.cookies)
[10:24:00.588]      |                                                           ^
[10:24:00.588]   11 |     if (rewrite) {
[10:24:00.588]   12 |       url.pathname = rewrite
[10:24:00.588]   13 |       return NextResponse.rewrite(url)
[10:24:00.627] error Command failed with exit code 1.
[10:24:00.628] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[10:24:00.655] Error: Command "yarn run build" exited with 1

hi, did you find a solution for this? I had the same problem.

No, sadly not.

Having the same problem. One click deploy for Vercel is broken.


Bug: GGML Compilation Error: undefined references to `iqk_mul_mat'

What happened?
When running make llama-server or make llama-bench I observe the following error:
/usr/bin/ld: ggml/src/ggml.o: in function `ggml_compute_forward_flash_attn_ext_f16':
ggml.c:(.text+0xbdde): undefined reference to `iqk_flash_attn_noalibi'
/usr/bin/ld: ggml/src/ggml.o: in function `ggml_compute_forward_mul_mat':
ggml.c:(.text+0x13aac): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml.c:(.text+0x14ae6): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml.c:(.text+0x15109): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml/src/ggml.o: in function `ggml_compute_forward_mul_mat_id':
ggml.c:(.text+0x15c49): undefined reference to `iqk_mul_mat_moe'
/usr/bin/ld: ggml/src/ggml-quants.o: in function `ggml_vec_dot_q4_0_q8_0':
ggml-quants.c:(.text+0x24a06): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml/src/ggml-quants.o: in function `ggml_vec_dot_q4_1_q8_1':
ggml-quants.c:(.text+0x24b86): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml/src/ggml-quants.o: in function `ggml_vec_dot_q5_0_q8_0':
ggml-quants.c:(.text+0x24d16): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml/src/ggml-quants.o: in function `ggml_vec_dot_q5_1_q8_1':
ggml-quants.c:(.text+0x24ee6): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml/src/ggml-quants.o: in function `ggml_vec_dot_q8_0_q8_0':
ggml-quants.c:(.text+0x250d6): undefined reference to `iqk_mul_mat'
/usr/bin/ld: ggml/src/ggml-quants.o:ggml-quants.c:(.text+0x28c26): more undefined references to `iqk_mul_mat' follow
collect2: error: ld returned 1 exit status
make: *** [Makefile:1458: llama-server] Error 1

System Specs
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         40 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  24
  On-line CPU(s) list:   0-23
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Xeon(R) Gold 5117 CPU @ 2.00GHz
    CPU family:          6
    Model:               85
    Thread(s) per core:  1
    Core(s) per socket:  1
    Socket(s):           24
    Stepping:            4
    BogoMIPS:            3990.62
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 p
                         cid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm 3dnowprefetch pti ssbd ibrs ibpb stibp fsgsbase smep arat md_clear flush_l1d arch_capabilities

What is interesting however is how this is failing only on this server and not for my other server with the following CPU in which I get >50% improvements in prompt processing and token generation.
Side Note: Thank you for all the great work with the llama.cpp project and the open-source community!
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          46 bits physical, 57 bits virtual
  Byte Order:             Little Endian
CPU(s):                   160
  On-line CPU(s) list:    0-159
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz
    CPU family:           6
    Model:                106
    Thread(s) per core:   2
    Core(s) per socket:   40
    Socket(s):            2
    Stepping:             6
    CPU max MHz:          3400.0000
    CPU min MHz:          800.0000
    BogoMIPS:             4600.00
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni
                          pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 invpcid_single intel_ppin ssbd
                           mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl
                           xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni a
                          vx512_bitalg tme avx512_vpopcntdq la57 rdpid fsrm md_clear pconfig flush_l1d arch_capabilities

Name and Version
./llama-server --version
version: 3432 (12bbdb8c)
built with cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 for x86_64-linux-gnu (Working)
The other server will not build
What operating system are you seeing the problem on?
Linux
Relevant log output
No response

I use cmake, so the Makefile is less solid than it shou be. Have you tried make clean && make -j? I'm away for a few days and will look at the problem when I come back.

Same error happens with those commands. No rush will try to build via cmake on this particular server.

So, I don't really see what could be wrong with the Makefile. The Makefile, inherited from llama.cpp, is of course useless as it does not reflect the actual build artifact dependencies. E.g., here is what we have as a build rule for ggml.o, which is the core of the whole system
ggml/src/ggml.o: \
    ggml/src/ggml.c \
    ggml/include/ggml.h
    $(CC)  $(CFLAGS)   -c $< -o $@

In reality ggml.o depends on several other files as one gets via
gcc -Iggml/include -Iggml/src -MM ggml/src/ggml.c
ggml.o: ggml/src/ggml.c ggml/src/ggml-impl.h ggml/include/ggml.h \
  ggml/src/ggml-quants.h ggml/src/ggml-common.h ggml/src/ggml-aarch64.h

But make clean && make does produce the correct build, both in mainline llama.cpp and in this repository, so the failure you get on this one server is a bit mysterious.
Can you post the full output of the make command?
Thanks!

I'm not getting a response, and without the full output of the make command it is not possible to see what might be going wrong, so closing.


Move the deploy feature out into its own release archives

I have received a question/report about some questionable network activity from Hugo on Windows. This is from a more complex setup that is not practical for me to set up, but I have inspected the code and my prime suspect is the hugo deploy command (the Microsoft Azure integration), which does static initialisation,  even if you don't use the feature. We really need to make this feature some kind of plugin (e.g. Wasm), but until then I suggest we pull it out into separate release archives.
We already have a nodeploy build tag for this, so that should not be too hard.

Does that mean we need to do something like this?

Edition name
File name

standard
hugo_0.136.5_linux-amd64.tar.gz

extended
hugo_extended_0.136.5_linux-amd64.tar.gz

standard/deploy
hugo_with_deploy_0.136.5_linux-amd64.tar.gz

extended/deploy
hugo_extended_with_deploy_0.136.5_linux-amd64.tar.gz

Does that mean we need to do something like this?

I thought about making it a little bit simpler and only create deploy variants for the extended images, so something ala:

Edition name
File name

standard
hugo_0.136.5_linux-amd64.tar.gz

extended
hugo_extended_0.136.5_linux-amd64.tar.gz

extended/deploy
hugo_extended_with_deploy_0.136.5_linux-amd64.tar.gz


CSS not loading on production

I deployed this app on ec2, if i use dev settings, all working well.But when i am using production settings, css is not loading.I am getting this error, "Resource interpreted as Stylesheet but transferred with MIME type text/html:"
"Uncaught SyntaxError: "
`server {
listen 80;
server_name 13.xx.xx.xxx;
location = /favicon.ico { access_log off; log_not_found off; }
location /static_dist/ {
    root /home/ubuntu/studykarma/django-react-redux-base/src;
}
location / {
    include proxy_params;
    include  /etc/nginx/mime.types;
    proxy_pass http://unix:/home/ubuntu/studykarma/django-react-redux-base/src/djangoreactredux.sock;
}

}`
This is my nginx config file

what to put in nginx config file in production, my static files are not rendering


Encryption fails on Windows 2012 R2 server VM's which have storage spaces

Please update this document with exact OS version details which supports Azure disk encryption for storage spaces configured. I see BitLocker encryption supports Windows 2012 R2 server VM's which have storage spaces. Also kindly update ADE pre-requisites page and cross reference at encryption-scenarios section
Error message :
We have detected that AzureDiskEncryption installed for virtual machine VM-test-55 has failed with the following status: ProvisioningState/failed/1.
Failed to configure bitlocker as expected. Exception: Encrypting storage spaces is only supported on Windows server 2016 and above., InnerException: , stack trace: at Microsoft.Cis.Security.BitLocker.BitlockerIaasVMExtension.DiskWmi.StorageSpacesDisksWrap.IsVolumeBackedByStorageSpace(String VolumePath, List`1& slotIds)

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

ID: 7c60e59e-b306-3b47-dcad-56a3c03de428
Version Independent ID: 95ea9500-3d2e-6bef-a743-86e660e1ca86
Content: Overview - Azure Disk Encryption for IaaS VMs
Content Source: articles/security/azure-security-disk-encryption-overview.md
Service: security
GitHub Login: @mestew
Microsoft Alias: mstewart

@dikadali Thank you for pointing out the same . We will investigate and update this thread accordingly.

@dikadali We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


fix(defineShortcuts): handle extract when using onSelect or onClick

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks! 😊


Fix NullPointerException on null partition insert

Port https://github.com/apache/spark/pull/31320 to close #1735
Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

build

#1735 is targeting the 0.4 release yet this is targeting branch-0.5.

I thought we merge to the latest branch first and then cherry-pick; changing

build

:eyes: into test failuers

build

The 3.1.1 shim has been updated and now Spark 3.1.1 is using the official artifacts.  @gerashegalov if you upmerge this PR to the latest on branch-0.4 then it should run with 3.1.1 and the tests should pass.

build

The 3.1.1 shim has been updated and now Spark 3.1.1 is using the official artifacts. @gerashegalov if you upmerge this PR to the latest on branch-0.4 then it should run with 3.1.1 and the tests should pass.

@jlowe
:heavy_check_mark: merged branch-0.4 into the PR branch and mvn -Pspark311tests clean test -Dcuda.version=cuda11 -DwildcardSuites=com.nvidia.spark.rapids.InsertPartition311Suite  passes


fixed descending ordering for window functions when specifying multple columns

Currently it only specifies the last key as DESC. Fixed so that all keys are specified as DESC when carrying out descending ordering for a window function.

Thank you and sorry for delay response.
I'll check it.

Mreged but I'll try to add ThenBy for window function

Thanks, I've modified following code finally.
context.From<Shakespeare>()
       .Where(x => x.corpus == "othello" && BqFunc.Length(x.word) > 10)
       .Select(x => new
       {
           x.word,
           x.word_count,
           row_num = BqFunc.RowNumber(x)
               .OrderByDescending(y => y.word)
               .ThenBy(y => y.word_count)
               .ThenByByDescending(y => y.corpus)
               .Value
       })
       .Limit(5);

as
SELECT
  [word],
  [word_count],
  ROW_NUMBER() OVER (ORDER BY [word] DESC, [word_count], [corpus] DESC) AS [row_num]
FROM
  [publicdata:samples.shakespeare]
WHERE
  (([corpus] = 'othello') AND (LENGTH([word]) > 10))
LIMIT 5


How to creating a Navbar with flexbox, like below image?

Hey,
I want to creating a Navbar, like below image, How can i do that with flexbox without grid?

Thank you for your help, That's what I want :+1:,
Sorry to ask here.
Regards,

@irkawajan Adam is incredibly self-giving. There are countless examples on the web of flexbox navbars. Also, the excellent Tailwind docs have examples that would have given you the answer.


Cannot create two nested arrays with only one element at the top level

Steps to reproduce
$x = @(@(1,2))
$x[0][1]

I also tried different variants of that using [array] etc.
Expected behavior
Should output '2'
Actual behavior
Doesn't output anything, as the two arrays are being folded into one.
Environment data

Name                           Value
----                           -----
PSVersion                      6.1.0-preview.3
PSEdition                      Core
GitCommitId                    v6.1.0-preview.3
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This is by design:
@(...) doesn't construct an array, it ensures that its operand is an array (i.e., loosely speaking, it wraps a scalar in a single-element array and leaves something that already is an array alone).
Thus, nesting @(...) is pointless and invariably has the same effect as a single @(...).
What you need instead is the array construction operator: ,
PS> $x = , (1, 2); $x[0][1]
2

Also note that you do not need @(...) to construct (non-nested) literals: instead of @(1, 2) use just 1, 2, and use (...) to clarify precedence, as shown above.
See also: #6329

Great, thanks!


Fix travis tests/builds failing due to timeout

Nightly builds and our most recent PR are failing because of issues like this on Travis: https://travis-ci.org/open-forcefield-group/smarty/jobs/211486127
It gets to a message listing a big block of packages to be installed then has something like this:
Proceed ([y]/n)?
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

I've seen this several times recently. It's unclear to me if Travis-CI just adjusted its timeout settings (so we just need to adjust our settings) or if something has changed that is making things stall or run slower than normal. We'll need to investigate.

@davidlmobley is there something I can do to get this fixed sooner rather than later? It would be good to get this fixed before pull request #234 is ready for final review.

I just fixed this in #182

The issue problem is discussed here: https://github.com/omnia-md/conda-recipes/pull/739 https://github.com/conda/conda-build/issues/1825

Here's the current workaround for future reference: https://github.com/open-forcefield-group/smarty/pull/182/commits/46d7c8314c3f1f31f26b8f85d24e7e85a2d054e3

I just merged #182 so I'm marking this as closed. Thanks, @jchodera .


Update template and instructions to install origin 3.9 using docker images

Add if then else block within the inventory template j2
Update instructions to install origin 3.9 using docker images

missing annotation

We can but that could take time .....


Splunk HEC

Hello,
Logrus is pretty awesome.
Splunk supports something called HEC.
You send the message through HTTP with your token and that's pretty much it.
Is there an option of near future to support it ? Or maybe provide an example on how to send the logs from logrus to a HTTP endpoint ?

@sirupsen  could you give a hand pretty please

@posito you can write a hook for this :)


Android - Don't create an input connection if client is null

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues
Fixes #10809

You can test this PR using the following package version. 11.0.999-cibuild0032432-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Disable MacOS builds

CI is failing for the Rune project due to a bug in one of our dependencies (https://github.com/hotg-ai/librunecoral/issues/43). As a hacky temporary workaround, this PR disables the MacOS builds so we can keep merging changes.

Note to self: when we revert this PR, make sure to re-enable the corresponding branch protection rule.


Print user friendly error messages

Optional TODO:

[ ] Find a place for format_error in libvast.

@Neverlord, wouldn't it make sense to register an error renderer in the actor_system instead of hand-rolling our own formatting function?

@mavam regarding the error renderer: we already have the renderers in the actor system. But an error renderer should only print an error in a concise manner. Ultimately, this function should do more and also look into the context and print some nicely-formatted text.
For example, if a user passes in import -x zeek then we get back a parser error and that -x is not an option. This function should actually go one step further and not only print the parser error, but also what the valid options for import are. Not for this PR, of course, but it's a customization point we want to have and definitely something that goes beyond simply printing the error itself.
For that reason, maybe we should pass the root command and the settings to format_error. Then we don't need to change the signature later (and break upstream code).

Thanks for elaborating, that sounds like a good strategy!

Looks good

Not to me, sorry.
All the side-effect discussion aside, let's look at the user perspective. What is the resulting behavior of this PR? We unconditionally print out the command help text and then print out the error without additional thought.
First, this means we put at the most important thing at the back. That's not what I would want as a user.
Second, the help text is irrelevant and misleading in many cases. Let's look into a couple of possible errors:

The command had wrong/misspelled arguments
We got an invalid query, e.g., a type clash
We couldn't connect to the node

Does it make sense to print the command help text in all three cases? To me that only makes sense in case 1. In the second case, we want instead to print out some help text regarding the query syntax. In the last case, there's not much to print other than "unable to connect". Any additional text only adds irrelevant or even confusing output.
For these reasons, I would approach this differently. Instead of printing in the command and return an error, I would return: command name, command arguments, and error. Then we can dispatch on the error first. Only in cases where the command's help text makes sense can we get the object by its name and have it print its text. For query-related errors, we can instead print something along the lines of "invalid query expression: ", followed by some help text for the query language.
Defining the help text for the query language can be a followup. However, I think dispatching on the error and only printing the command's help text where it makes sense is an important step for improving user experience.

Not to me, sorry.

No need to apologize. I wanted to get this out of the way a little too fast and didn't put the proper thought into it.
Implementing you suggestion for case 1 should actually be pretty easy, so i'll add another commit soon.


o: 2.58.0 -> 2.60.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/xyproto/o/releases.
meta.description for o is: Config-free text editor and IDE limited to VT100
meta.homepage for o is: https://github.com/xyproto/o
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.60.5 with grep in /nix/store/ls91y7rg4nfxqhnlvalddihrrwwx2j63-o-2.60.5
found 2.60.5 in filename of file in /nix/store/ls91y7rg4nfxqhnlvalddihrrwwx2j63-o-2.60.5

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
o

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

o

Maintainer pings
cc @sikmir for testing.

Project has been renamed from o to Orbiton as of https://github.com/xyproto/orbiton/releases/tag/v2.60.0

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

1 package built:

orbiton

Result of nixpkgs-review pr 225427 run on x86_64-darwin 1

1 package built:

orbiton


[Bug]: SAML RelayState not optional?

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
Self-hosted
Version
2.37.3
Database
CockroachDB
Database Version
23.1.14
Describe the problem caused by this bug
I tried to integrate Zitadel with Zammad but could not get it to work because Zammad does not use "RelayState" in its request.
Zitadels documentation state that this should be optional but I can't get it to work. I tried to add "&RelayState=Hello" to the end of the request and it worked just fine, so it looks like Zitadel still requires "RelayState" from SAML request to work.
To reproduce
Connect Zammad with Zitadel SAML and try to authenticate. You will just get redirected to an XML page. If you manually add &RelayState=Hello to the end of the request url it works. I have just tried this with Zammad, but I guess this issue is affecting all services that use SAML without an RelayState.
Screenshots
No response
Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

Hey @julianbrennum
I think you are using the stable tag version of zitadel. This has been updated recently, which also includes a fix of the SAML library.
Can you please update ZITADEL and check again?


Question about the paper: Parallelized Training

Hello, I read your paper and have several questions.
My question is about Section 4.2 / Appendix D - parallelized training.
I think I haven't fully understood why the use of ID Decoder enables parallelized training.

From my understanding, ID Decoder computes the prediction using Historical Trajectory information (and current detection token). Doesn't the historical trajectory still require serial processing?

In the paper, it is noted that only 4 frames are used for gradient recording and others are passed through gradient-free mode. In Appendix D, I see 2 frames are processed with grad out of 5. How are these numbers (number of frames with grad/number of forward passes) calculated?

Related to Question 2, why are only few frames selected with gradients? Does this mean the ID Decoder enables more robust learning, which allows sparser training of the detector?

Thank you for your great work and contribution!

Thank you for your interest in our work.
For your questions:

The historical trajectory modeling does not need serial processing. As we implemented in trajectory_modeling.py, we only use FFN for trajectory modeling from DETR's output embeddings.
In Appendix D, Fig 7 is just a schematic made for simplicity. So, the number of frames does not represent the real situation in our experiments. In our experiments, no matter how many frames are input, only 4 frames are used for gradient recording. This is due to the CUDA memory limitation while following the original Deformable DETR setting (BS=4 for each GPU).
As I discussed in 2., the CUDA memory limitation is the main reason. In this setting (4 frames for gradient recording), most of our experiments can be run on 24GB GPUs without the gradient checkpoint. For "Does this mean the ID Decoder enables more robust learning, which allows sparser training of the detector?" you mentioned, I do not understand what this means. To be honest, I did this (sparse training of the DETR) just to reduce resource usage and speed up the model training.

Thank you for your kind response!
To ensure I understand correctly, I have two more questions I'd like to clarify:

I understand that the target embeddings can be parallelized. According to the paper, the historical trajectory includes both target embeddings and ID embeddings. Then, is it correct to assume that ID embedding extraction is not parallelized as the ID Decoder requires ID embeddings from previous trajectories? Despite this, since DETR output embeddings can be processed in parallel, does this mean that the ID Decoder's processing time is relatively shorter than DETR's, thereby still allowing for an overall speed-up in the process?

Regarding sparser training, then would updating DETR with every frame enhance the overall performance? I'm curious if previous related works typically relied heavily on frequent updates of DETR for optimal performance.

I see! Now everything makes sense. Thank you, I appreciate your detailed response.


EOFError on MemoryIO with encoding

https://play.crystal-lang.org/#/r/sv4
It works if I don't set the encoding: https://play.crystal-lang.org/#/r/sv5

Mixing binary and text reads will cause that for the moment. It's said in the docs

@Exilor I'll expand a bit more about this.
Right now we are using iconv for encoding/decoding. The interface to it is:
size_t iconv(iconv_t cd,
                    char **inbuf, size_t *inbytesleft,
                    char **outbuf, size_t *outbytesleft);

You give it input and output buffers, and it will read from the input as much as inbytesleft bytes and write to the output buffer.
The problem is, there is no way to tell it "decode a single char". If we wanted to do that, we'd have to invoke it multiple times, first with 1 in inbytesleft, then with 2, etc. Super slow. So for now we have an intermediate buffer of about 4K, read raw bytes from the IO and then decode them all with iconv, hoping that the user won't mix binary and text. If the user does, then the requested bytes might come after the already decoded ones (the intermediate buffer is only used when reading text if there's an encoding).
Another library we considered is icu4c, but it has its own complications too. iconv was the simplest to implement right now.
We thought a lot about what to do, and in what cases you'd want to mix binary and text. If there's a protocol, it usually says how many bytes come next if there's a string, so you always use binary (and if you need to decode you can read the bytes and then decode them). There's also the case of Java (and I believe in C# it's similar), where you wrap an InputStream with an InputStreamReader to read text, but they recommend you to use a BufferedInputStream, but then it will read more then the request text (because it buffers), so then if you read from the underlying input stream you will face a similar issue than in Crystal.
The good news is that this can, and probably will, be improved in the future, if we implement the encoding/decoding ourselves. It's just that it would take too much time for us right now. Ruby does let you mix bytes and text and it works just fine.

Thank you for the explanation. I'm porting Ruby code that I more or less ported from Java and the protocol is that the string is terminated with [0, 0]. The original code moves the bytes to another object before reading a string from it, so I suppose they faced a similar issue. I solved it the same way.

The PostgreSQL wire protocol behaves that way too: each frame has an overall payload length then strings are null byte terminated. For example the Startup Packet is [Int32 len, Int32 protocol, String name, \0, String value, ... \0 ].
I'm not sure it will require any decoding, thought. Startup and ErrorResponse packets should only use ASCII chars, and Data Row Packets do specify a length for each value, so the current behavior shouldn't be a problem.

@ysbaddaden In my case a packet containing 1234 (int16), "hello" and<PHONE_NUMBER> (int32) looks like this: [15, 0, 210, 4, 104, 101, 108, 108, 111, 0, 0, 210, 2, 150, 73]. That's why I had to mix reading numbers and reading UTF-16LE strings.


Unable to open specific .vsi file with pyfast

Describe the bug
Tried to read .vsi file with pyfast, used latest release, resulted in Wrong JPEG library version: library is 90, caller expects 80
To Reproduce
Image can be provided, per request.
import fast

wsi_reader = fast.WholeSlideImageImporter.create(filename)
image = wsi_reader.runAndGetOutputData()

System:

OS and version: Ubuntu 20.04
GPU and OpenCL vendor: NVIDIA

Log:
Examples_rat_liver/11_02.vsi
INFO [140518223876736] EXECUTING WholeSlideImageImporter because PO is modified.
INFO [140518223876736] VSI was compressed with JPEG
INFO [140518223876736] VSI level: 0:<PHONE_NUMBER>76
INFO [140518223876736] VSI level: 1: 90368 69888
INFO [140518223876736] VSI level: 2: 45184 34944
INFO [140518223876736] VSI level: 3: 22592 17472
INFO [140518223876736] VSI level: 4: 11296 8736
INFO [140518223876736] VSI level: 5: 5648 4368
INFO [140518223876736] VSI level: 6: 2824 2184
INFO [140518223876736] VSI level: 7: 1412 1092
INFO [140518223876736] VSI level: 8: 706 546
INFO [140518223876736] EXECUTING EmptyProcessObject because PO is modified.
INFO [140518223876736] EXECUTING TissueSegmentation because PO is modified.
Wrong JPEG library version: library is 90, caller expects 80

Problem was an anaconda install of libjpeg colliding with the version used by Fast, which was not overwritten when Fast was installed.
Solved after switching from anaconda to Python venv.


How to change the color of barchart

How can I change the color of bar for each index like in the attached screenshot.  I am using ChartPointViewBar to generate the barchart but it has a option to change the color of all the bars.

ChartPointViewBar has a bgColor field you can set for this (just noticed there's no reason for this field to exist, it would be better to just set directly backgroundColor of the view. But for now it's what you have to use to set it).

It is only accepting the last color value in bgColor, not updating the colors specified in code. And can we add a label next to ChartGuideLinesForValuesDottedLayer, where the line ends.

Sure, you can request the screen locations from the axis layers ChartAxisLayer.axisValuesScreenLocs and depending where the label has to be maybe also add innerFrame.width or innerFrame.height. Alternatively you can also create a ChartPointsViewsLayer and pass chart points to it that represent your labels in model coordinates.


Modifying rows does not update a table using sorting

When adding rows to a table, it does not resort the items if the table is set to sort on the UI side.
Demo: http://codepen.io/properjon/full/dNbOyP
Repro steps in demo:

Open 2010
Click 'Add Rows'

Consolidating issue


Temperature for H5075 slightly wrong

The temperature for the H5075 is not correct, but the error is less than 0.1 °C. The problem is that the humidity is included in the temperature. You can see it in the example in the code: "88ec00 03519e 64 00 Temp: 21.7502°C Temp: 71.1504°F Humidity: 50.2%"
The last three digits in the temperature (Celsius) are the same digits as in the humidity. It seems to me that the description in  https://github.com/Thrilleratplay/GoveeWatcher is not correct. To get correct values I changed
"Temperature[0] = float(iTemp) / 10000.0;" to "Temperature[0] = float(iTemp/1000) / 10.0;"

The temperature for the H5075 is not correct, but the error is less than 0.1 °C. The problem is that the humidity is included in the temperature. You can see it in the example in the code: "88ec00 03519e 64 00 Temp: 21.7502°C Temp: 71.1504°F Humidity: 50.2%"
The last three digits in the temperature (Celsius) are the same digits as in the humidity. It seems to me that the description in  https://github.com/Thrilleratplay/GoveeWatcher is not correct. To get correct values I changed
"Temperature[0] = float(iTemp) / 10000.0;" to "Temperature[0] = float(iTemp/1000) / 10.0;"

I'm going to think on this one since I'm not near a real computer for another couple days.
Im pretty sure the claimed accuracy of any of these thermometers is only 0.2°C, so I might want to round to those increments and truncate.
Due to the nature of real number storage in computers I chose to do the conversion to floating point first and keep the extra digits created.

Hello William,
maybe I was not not clear enough. It is not about rounding or about the
accuracy of the sensors! After converting the hexadecimal number into
decimal the first three digits are the temperature and the last three
digits are the humidity. So "03519e" converts to "217502" which means 21.7
°C and 50.2% humidity without any rounding.
BTW, thanks for your software. You are the reason I bought 12 of this
sensors. :-)
Bye Dirk
On Thu, Jun 8, 2023 at 6:02 PM William C Bonner @.***>
wrote:

The temperature for the H5075 is not correct, but the error is less than
0.1 °C. The problem is that the humidity is included in the temperature.
You can see it in the example in the code: "88ec00 03519e 64 00 Temp:
21.7502°C Temp: 71.1504°F Humidity: 50.2%"
The last three digits in the temperature (Celsius) are the same digits as
in the humidity. It seems to me that the description in
https://github.com/Thrilleratplay/GoveeWatcher is not correct. To get
correct values I changed
"Temperature[0] = float(iTemp) / 10000.0;" to "Temperature[0] =
float(iTemp/1000) / 10.0;"
I'm going to think on this one since I'm not near a real computer for
another couple days.
Im pretty sure the claimed accuracy of any of these thermometers is only
0.2°C, so I might want to round to those increments and truncate.
Due to the nature of real number storage in computers I chose to do the
conversion to floating point first and keep the extra digits created.
—
Reply to this email directly, view it on GitHub
https://github.com/wcbonner/GoveeBTTempLogger/issues/49#issuecomment-1582928760,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BANR76ERW7VKETHEMACMDYDXKHZTFANCNFSM6AAAAAAY7OUNZE
.
You are receiving this because you authored the thread.Message ID:
@.***>

maybe I was not not clear enough. It is not about rounding or about the
accuracy of the sensors! After converting the hexadecimal number into
decimal the first three digits are the temperature and the last three
digits are the humidity. So "03519e" converts to "217502" which means 21.7
°C and 50.2% humidity without any rounding.
BTW, thanks for your software. You are the reason I bought 12 of this
sensors. :-)

Ah. I've been on a sailboat for the last two weeks and my brain is a little foggy. I'm not even sure what day of the week it is without switching to the calendar app.
Each of the different thermometers uses a slightly different data packing system, and your follow up clarification was greatly helpful. (I'll probably put it in the code comments when I get home and have a chance to look at things on a real computer)
It's always great to have appreciation for the code. I seem to have fallen into a rabbit hole of buying and playing with these devices. I've got them in refrigerators and freezers and have learned that different refrigerators use completely different cycling algorithms to keep their interior cool. Also having them outside produces almost useless relative humidity values, at least in Seattle.
Wim

@dirk754 I swapped in your equation and pushed the fix


Code Cleanup Master Issue

Comment any code cleanup issues here with checkboxes.

[ ] : Redo Tools to be imported with just their module names then access handlers with Tool.handler
[x] : Replace Linked List with regular JS List
[ ] setTool in index.ts should not be exported. This was likened to creating methods in the main() of a Java class. Figure out some fix!
[ ] Get rid of magic numbers in index.ts regarding enums (~line 250)

[ ]  Get rid of magic numbers in index.ts regarding enums (~line 250)
in pr #286


Integrate custom tasks into Pipelines

Changes
A Pipeline Task now can reference a custom task.  This causes the PipelineRun reconciler to create a Run instead of a TaskRun.
Pipeline parameters can be passed to the custom task.  The custom task's results can be used by other Pipeline tasks and by the Pipeline results.
/kind feature
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
In package pkg/apis/pipeline/v1alpha1, the type of field RunStatusFields.Results has changed from
v1beta1.TaskRunResult to v1alpha1.RunResult.

@ImJasonH @vdemeester This PR supercedes Jason's original PR #3115.  I made the following changes:

Rebased to latest master.
Resolved most of the TODOs.
Resolved the import cycle problem getting the v1beta1 PipelineRun status to include the v1alpha1 Run status.
Added code to propagate PR cancel request to Runs.
Added code to handle result references to results produced by custom tasks.
Improved unit test coverage for Runs.
Updated docs.

The main TODO which I did not address was to handle Conditions in pipeline tasks that use custom tasks. At the time of Jason's PR, I believe that "when" support was not yet merged. Now that "when" support is merged and Conditions are being deprecated, I would like to propose that Conditions NOT be supported in pipeline tasks that use custom tasks. If everyone agrees then I can update this PR to validate that restriction or I can do that in a follow-on PR.
Thanks in advance for your review.

Thanks so much for doing this Greg! 🎉

Now that "when" support is merged and Conditions are being deprecated, I would like to propose that Conditions NOT be supported in pipeline tasks that use custom tasks.

This seems reasonable to me, so long as it's documented and produces a descriptive error message. I'd prefer it to happen in a followup PR though to keep this one relatively narrowly scoped.

/test check-pr-has-kind-label

@GregDritschler could you fill in the checklist:

Discussed in OWNERS meeting today, sounds like merging this fixes #3133 (correct me if I'm wrong @ImJasonH @GregDritschler !)

Discussed in OWNERS meeting today, sounds like merging this fixes #3133 (correct me if I'm wrong @ImJasonH @GregDritschler !)

There are a few things left to do (as separate PRs since this one is already very big):

Disallow use of deprecated Conditions with custom tasks
Enable use of service account name and workspaces with custom tasks
Provide a sample custom task controller (I have started one)

What's the process of this implements? expect to try the customer task.

/test tekton-pipeline-unit-tests

@tektoncd/core-collaborators in the light of discussion around "feature-flags", should this feature be under a feature flag or not ? 🙃

I have added the feature flag.

@vdemeester @afrittoli this is urgent for us - any blocker now to merge?

/lgtm

Couple of questions:

When a pipelineRun is created with a custom task but the custom controller does not update pr.Status for some reason, does pipelineRun eventually time out? or does it keep waiting indefinitely?

I wrote a simple pipeline with one custom task and created a pipelineRun with that pipeline. Tekton controller logs says Creating a new Run object pipelinerun-with-custom-task-run-custom-task-g4dcc and creationTimestamp of that run object is set:

kubectl get run pipelinerun-with-custom-task-run-custom-task-g4dcc -o json
{
    "apiVersion": "tekton.dev/v1alpha1",
    "kind": "Run",
    "metadata": {
        "annotations": {
            "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"tekton.dev/v1beta1\",\"kind\":\"Pipeline\",\"metadata\":{\"annotations\":{},\"name\":\"pipeline-with-custom-task\",\"namespace\":\"default\"},\"spec\":{\"tasks\":[{\"name\":\"run-custom-task\",\"taskRef\":{\"apiVersion\":\"example.dev/v1alpha1\",\"kind\":\"Example\"}}]}}\n"
        },
        "creationTimestamp": "2020-11-19T06:04:00Z",

but no start time:
kubectl get run
NAME                                                                                SUCCEEDED   REASON   STARTTIME   COMPLETIONTIME
pipelinerun-with-custom-task-run-custom-task-g4dcc

Is it again custom controller updating the status of this run along with pipelineRun?

When a pipelineRun is created with a custom task but the custom controller does not update pr.Status for some reason, does pipelineRun eventually time out? or does it keep waiting indefinitely?

Alright, so, pipelineRun eventually timed out, updating the pr.Status with  "reason": "PipelineRunTimeout" and completionTime along with the run. But listing the run still shows blank for REASON, COMPLETIONTIME etc

When a pipelineRun is created with a custom task but the custom controller does not update pr.Status for some reason, does pipelineRun eventually time out? or does it keep waiting indefinitely?

We decided in the TEP not to have the PipelineRun controller be responsible for custom task Runs beyond creating them. So if there's no custom task controller handling and updating that Run object, it'll look like the Run just never starts until the PipelineRun itself times out. That's also why there's no startTime, there's nothing watching to update it.
We can revisit that decision and have the PipelineRun controller enforce some kind of "are you there?" check on custom task controllers, such that if a custom task Run isn't started within 30s or something (configurable) the PipelineRun controller can kill it and fail the PipelineRun as a safety mechanism.
I definintely don't think that needs to happen in this PR, and should probably only be decided on after users have played with it to see how big of a deal it is to not have the safety mechanism.

@GregDritschler @ImJasonH I'm not check the details, just a quick question: does task in finally section also could point to a customer task?   since finally can not support sequence run, so I guess customer task could help on this part.

I've opened issues for the follow-on work to this PR.
Custom Tasks: Disallow use of Conditions #3592
Custom Tasks: Allow use of workspaces #3593
Custom Tasks: Allow use of service accounts #3594
Custom Tasks: Support Pipeline Results #3595
Custom Tasks: Move all Run-related Go types to pkg/apis/run #3596
@vdemeester @afrittoli @pritidesai FYI.  I believe I've resolved all the review issues. If not let me know.  I'd like to get this one closed out.

arf, @GregDritschler needs yet another rebase, sorry :sweat: :bow:

@afrittoli @vdemeester Rebase completed.


fix send email error

Hi @alexisrolland:
This is my first time to submitted a pull request on an open source project.
If there are any deficiencies, please give me more advice.
#364 fix send email error when use other email server

Thank you for your pull request!
Could you please confirm this was tested and worked with QQ mail?
The previous code was working for Gmail so I would suggest to not change it. Instead I would propose the following:

Move the line connection = smtplib.SMTP(...) in the code block If config['host'] == "smtp.gmail.com":

Add a new code block If config['host'] == "smtp.qq.com": and place connection = smtplib.SMTP_SSL(...) in it

Add an else: code block to manage other fallback cases.

Thanks again!

Thank you very much for your suggestions.
I thought smtplib.SMTP_SSL(...) would not report an error when using gmail,but I was wrong.
I just did a test and found that smtplib.SMTP_SSL(...) cannot support the sending of gmail, it's my mistake.
And I confirmed that smtplib.SMTP_SSL(...) can support qq email.
I will modify code.
Thank you very much!

I was thinking, may i use try catch? like this：
try:
    connection = smtplib.SMTP_SSL(config['host'], config['port'])
except Exception:
    connection = smtplib.SMTP(config['host'], config['port'])

In this way, we don’t need to consider that type of email service. It will only have two options, and only one of them will take effect


Added  Recursive Program to remove consecutive duplicates from string S

Great work @foxylfg please give this repo a star if it really helped you to complete your PR.
Also follow me for follow back if you want to get connected with me for any such open source contribution program. Thank you 😊