Spyder says dependencies have wrong version, but it lists different versions than installed

Problem Description
When i start up spyder 4.0.1 it says i have missing dependencies. It lists that my jedi version is only 0.14.0, and should be 0.14.1. It gives a similar problem with qtconsole: it needs 4.6.0 and says i have version 4.5.1. When i actually go and use conda list, it says i do have jedi version 0.14.1 and qtconsole 4.6.0:

On my second computer i have the same package versions and everything works flawlessly on there, so i really don't get why it's acting up. I tried rebooting, reinstalling anaconda (and rebooting), resetting spyder, manually removing spyder, reinstalling it again, reinstalling anaconda again, and it just doesn't want to work.
Previous spyder version do work, but i'd like to just use the latest one (which i would think shouldn't be that hard, but i've been trying to fix this for the past 4 hours...)
What steps reproduce the problem?

Use conda update --all
Use conda update spyder
Start spyder

What is the expected output? What do you see instead?
I just want spyder to work normally, it misses dependencies and iconsole doesn't work.

Please look for jedi or qtconsole in your hard drive and remove the directory or directories (not part of Anaconda) where those packages were installed.
They are usually placed in
C:\Users\<your user>\AppData\Roaming\Python\

And for next time, please do not install packages with pip if they can be installed with conda.


Interface ...UserConfig incorrectly extends interface ...UserConfig

Describe the bug
When executing tsc, I get the following error:
node_modules/vitest/dist/config.d.ts:75:11 - error TS2430: Interface 'import("/mnt/c/XXX/node_modules/vitest/dist/config").UserConfig' incorrectly extends interface 'import("/mnt/c/XXX/node_modules/vite/dist/node/index").UserConfig'.
  Types of property 'test' are incompatible.
    Type 'InlineConfig | undefined' is not assignable to type 'InlineConfig'.
      Type 'undefined' is not assignable to type 'InlineConfig'.

75 interface UserConfig extends UserConfig$2 {
             ~~~~~~~~~~

Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-bqveyc
System Info
WSL

  System:
    OS: Linux 4.4 Ubuntu 22.10 22.10 (Kinetic Kudu)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 9.21 GB / 31.65 GB
    Container: Yes
    Shell: 5.2.2 - /bin/bash
  Binaries:
    Node: 19.9.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 9.6.3 - /usr/bin/npm
  npmPackages:
    @vitejs/plugin-react: ^3.1.0 => 3.1.0
    @vitest/coverage-c8: ^0.30.1 => 0.30.1
    vite: ^4.2.1 => 4.2.1
    vitest: ^0.30.1 => 0.30.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The error goes away if exactOptionalPropertyTypes is set to false.

I think this is simply a mismatch between https://github.com/vitest-dev/vitest/blob/f3c3607b24080bb306086a82941248b16c51d35d/packages/vitest/src/config.ts#L5 and https://github.com/vitest-dev/vitest/blob/f3c3607b24080bb306086a82941248b16c51d35d/packages/vitest/src/types/vite.ts#L10

I think this is simply a mismatch between

Check your package lock. You have several Vite versions enabled.

Good idea, but I don't think that is the case:
$ npm ls --all | grep vite
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY @vitest/browser@*
│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>deduped
│ │ ├──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├── UNMET OPTIONAL DEPENDENCY @vitest/ui@*
│ ├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped
│ ├──<EMAIL_ADDRESS>deduped

It seems to me like the typings of vite are included in types-c3c9754d.d.ts, but I'm not sure why.

I don't see any errors in your reproduction.

Can reproduce it now, you left the comment in tsconfig.

Sadly, the issue doesn't seem to be fixed. I updated the stackblitz to 0.31.0, but tsc still gives two errors:
node_modules/vitest/dist/config.d.ts:75:11 - error TS2430: Interface 'import("/home/projects/vitest-dev-vitest-bqveyc/node_modules/vitest/dist/config").UserConfig' incorrectly extends interface 'import("/home/projects/vitest-dev-vitest-bqveyc/node_modules/vite/dist/node/index").UserConfig'.
  Types of property 'test' are incompatible.
    Type 'InlineConfig | undefined' is not assignable to type 'InlineConfig'.
      Type 'undefined' is not assignable to type 'InlineConfig'.

75 interface UserConfig extends UserConfig$2 {
             ~~~~~~~~~~

node_modules/vitest/dist/config.d.ts:78:11 - error TS2430: Interface 'UserWorkspaceConfig' incorrectly extends interface 'UserConfig'.
  Types of property 'test' are incompatible.
    Type 'ProjectConfig | undefined' is not assignable to type 'InlineConfig'.
      Type 'undefined' is not assignable to type 'InlineConfig'.

78 interface UserWorkspaceConfig extends UserConfig$2 {
             ~~~~~~~~~~~~~~~~~~~

Found 2 errors in the same file, starting at: node_modules/vitest/dist/config.d.ts:75

I can confirm: the issue happens to me too with<EMAIL_ADDRESS>

Should be fixed in 0.31.1


add username and password as command options

Publish - Add options to pass username/password to be stored in keyring


Dkilgore eightfold/select improvements

SUMMARY:

Deselect option using backspace when using single select
Adds flip to Dropdown component floating-ui middleware
Adds disabled state to Pills
Only show tooltip if pill label is truncated
Adds UTs

https://user-images.githubusercontent.com/99700808/191388121-2413d684-610b-4a6a-a97d-01e39880f23c.mp4
https://user-images.githubusercontent.com/99700808/191388272-90d4141b-0540-4e54-bc23-fb0ae4591483.mp4
JIRA TASK (Eightfold Employees Only):
ENG-29954
CHANGE TYPE:

[X] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[X] I have added unittests for this change

TEST PLAN:
pull the pr branch and do yarn, then yarn storybook. Verify the Select stories behave as expected. You may also implement Select using Codesandbox CI.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f42be3f). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #384   +/-   ##
=======================================
  Coverage        ?   84.70%
=======================================
  Files           ?      485
  Lines           ?    13322
  Branches        ?     4500
=======================================
  Hits            ?    11285
  Misses          ?     2013
  Partials        ?       24

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Scalar list filter does not support case insensitive comparison

Problem
hasSome in scalar list filter obeys case sensitivity. I want case insensitive comparison.
Suggested solution
support mode:"insensitive" for hasSome and other scalar list filter operators.

This is a really needed feature in my opinion

+1

+1

Bump! Would love to see this feature added.

Bump !

When will this be implemented? It has been more than 2 years


Improve discoverability of Prisma.DbNull/Prisma.JsonNull

We should make the documentation about Prisma.DbNull and Prisma.JsonNull more discoverable.
The title of the section refers to "Filtering by null values", but the same also applies to create, insert and upsert operations (only Prisma.AnyNull is only used for filtering). This is, in fact, stated in the referenced section of the documentation, however it is hard to find.
This leads to confusion by our users who report expected and intended behavior as a bug: https://github.com/prisma/prisma/issues/9247

Thanks @aqrln, yes we definitely need to improve this; I even had trouble finding it. I might ping you with some questions soon.

Background slack thread here


Feature/sm/assig player on team

feat: add new player to team list
refactor: update player names
refactor: update addToTeamList method
feat: add player to team list on create
feat; add new player


/etc/hosts does not update

I changed C:\Windows\System32\drivers\etc\hosts, verified in an already open powershell window that the change is picked up. Then  closed my bash window (no other bash windows are open) and upon restart, the new entry was not added. I have # This file was automatically generated by WSL. To stop automatic generation of this file, remove this line. in my /etc/hosts.. I read https://github.com/Microsoft/BashOnWindows/issues/890#issuecomment-239684069 but it didn't help.

Please fill out the issue template. It looks like you are running a build that does not add windows hosts to the /etc/hosts file.

Sorry, it's  Ubuntu 16.04.2 LTS /  Microsoft Windows [Version 10.0.15063]

No worries. The functionality of adding windows hosts to /etc/hosts is currently only available in Insider builds.

Oh. That was a 2016 comment and since I am on Creator's Update I thought it's already in. Nevermind then!
Any workarounds? (cp when bash starts :) ? )

@chx , your suggestion works for me...  I'm doing this (in my .bashrc):
sudo cp /mnt/c/Windows/System32/drivers/etc/hosts /etc/hosts

Just have to log out/in after any changes.

For whoever ends up on this page for having the issue on the recent versions of windows.
I 'm on Ubuntu 18.04 on
Microsoft Windows [Version 10.0.18362.295]

and I have
[network]
generateHosts = true
generateResolvConf = true

in /etc/wsl.conf, but the files was not being regenerated when I was closing all the session.
My solution, in order to avoid a doing a restart,  was to go in the services tool (services.msc)  and restart the LxssManager* services.

@AsharLohmar - The files are updated when the session is launched, not when it exits.

AFAIK, the file is regenerated when the first session is started (might be wrong), that's why I mentioned that I was was closing all the sessions. The check it self was to fire up a new shell/session and cat the file.

@AsharLohmar - To ensure a new session is created you must terminate any running ones (wsl.exe --terminae )

Didn't know that, thanks, I usually use kill -9 -1 and brutally kill everything.

There is also the option to open the Windows Power Shell and run one of the following commands (no need to restart windows)
wsl --shutdown or wsl.exe --shutdown will regenerate the Linux hosts file according to the widows 10 hosts file.

The generated file seems to not be an exact copy of the Windows hosts file, but also includes some lines added by the distro, in my case Ubuntu. Can anybody tell me how these additional entries are generated/where they are stored? I want to add ::1 localhost to the /etc/hosts which for some weird reason has been removed by Ubuntu.


Fix flag handling in rubocop.

Codecov Report

Merging #196 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #196   +/-   ##
=======================================
  Coverage   88.79%   88.79%
=======================================
  Files          41       41
  Lines        2098     2098
=======================================
  Hits         1863     1863
  Misses        235      235

Impacted Files
Coverage Δ

lintreview/tools/rubocop.py
97.5% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


TypeError: y.getValue is not a function

Hi! When the page loads and I click on the sheet i get the error "TypeError: y.getValue is not a function"

I had the same problem on my side. It was because my application, after a yarn add mui-bottom-sheet had installed a version of react-spring (the 9.0.0-rc.3 in this case) not compatible with the getValue() used in BottomSheet.tsx.
When I cloned the repository and ran a yarn install it installed the 9.0.0-beta.33 version of react-spring for which the getValue() is not a problem.


Support of network-wide interface parameter

It looks like you can only set the interface attribute for the whole dhcpd server. It is not possible to assign a subnet to a specific NIC. I would expect to have an additional configuration parameter in the networks data bag, e.g.: interface: "eth1".

From what I understand if you declare a subnet the server will look for an interface on the same network to listen on.  So even if you globally set an interface if you declare subnets that it does not have an IP on it is just ignored.
[root@default-centos-64 dhcp]# dhcpd
Internet Systems Consortium DHCP Server 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.

No subnet declaration for eth0 (<IP_ADDRESS>).
** Ignoring requests on eth0.  If this is not what
   you want, please write a subnet declaration
   in your dhcpd.conf file for the network segment
   to which interface eth0 is attached. **

Not configured to listen on any interfaces!

I guess if your use case is that you have multiple interfaces on the same subnet you would want to specify which interface to actually use for that subnet.
Or maybe I'm missing something else as I'm not a DHCP expert. :wink:

Closing for now.  Feel free to reopen and respond to my last statement if I'm wrong.


GLS ReferenceRegion for GRCh37

Thank you for making these variant catalogs publicly available!
I think the GLS GRCh37 coordinates should be  2:191745598-191745646  based on liftover from GRCh38

And thank you for taking the time to correct it! Super - most grateful!


Design Reviews: Initial diagrams and ideas on high level design recipe

Initial cut at high level design criteria
Added example sequence + box diagrams
Fixed typo in the milestone/epic recipe

#133

@ScoGroMSFT please address the comments and then @alkofahi can re-review - hoping we can get this finalized and merged asap. Thanks!!
cc @wbreza


Normalize composer version range

Q
A

Bugfix
yes

This patch resolves #73.

@Ocramius I've started working on CI last year: https://github.com/laminas/laminas-ci-matrix-action/pull/62
The main idea was to create a directory where "projects" can be created with specific "files" and with a matrix.json. This would enable us to create fake-projects with the exact outcome we expect when these are "parsed" by this container.
But sadly, I haven't written down that so that some1 else could take over.


Synchronize local dev and production deployment environments

problem is that data science teams train and develop in an environment that's very different from production
use similar docker image for development, but with file watcher to enable rapid iteration of model creation, deployment, and testing
this also has the benefit of being able to reproduce and debug issues in prod since the dev environment is the same (except maybe the size of the dataset)

currently an issue with v1.12 Docker for Mac/Windows (beta) and MiniKube 1.3.  working through this.

immutable deployments:  1 model and runtime environment (docker image) per model
deployed with spinnaker or kubernetes or equivalent blue-green deployment
possibly include a redis/dynomite caching store for off-heap caching essentailly, but try to load in JVM memory if possible

another possibility:  give local dev's access live Kafka stream (sampled, shadowed traffic) with 24 hour persistence window.
allow them to replay from any given point in time
helps sync dev/local and prod environments by allowing devs/data scientists to tap directly into current, live production data stream during development and model training

related to https://github.com/fluxcapacitor/pipeline/issues/62

done through docker and tooling


FontVariants.Superscript only supports certain character

Describe the bug
When using FontVariants.Superscript in Run in XAML, only some characters are superscripted. Namely, numbers and the character n for example, but not other characters (x, q, f, ...).
Steps to reproduce the bug
When using this code in my XAML view file, the x stays inline with the 10 (10x).
<TextBlock>Velocity: 10<Run Typography.Variants="Superscript">x</Run></TextBlock>
Expected behavior
When using x within Run I expect it to be superscripted in a way in which n is.
Screenshots

Version Info
WinUI: v2.3.191211002
OS: Windows 10 Pro 1903
IDE: Microsoft Visual Studio Professional 2019, v16.4.2
NuGet package version:
Microsoft.UI.Xaml 2.3.191211002

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Additional context

This is weird. I repro the issue on the latest version of Windows and on RS4, so it appears this has been around for a while and still exists.
The font impacts this. The Segoe UI font showing proper superscript only for lowercase 'i' and 'n', along with the 0-9 digits. Arial and Times New Roman don't show superscript for any letters.
I don't know why this is happening, and I'm following up with some text experts for their ideas.

This is weird. I repro the issue on the latest version of Windows and on RS4, so it appears this has been around for a while and still exists.
The font impacts this. The Segoe UI font showing proper superscript only for lowercase 'i' and 'n', along with the 0-9 digits. Arial and Times New Roman don't show superscript for any letters.
I don't know why this is happening, and I'm following up with some text experts for their ideas.

Likely because that Typography.Superscript doesn't force rendering superscript characters - it only enables support for superscript characters the font itself actually declares as superscript variants. Arial and Times New Roman don't actually have superscript or subscript support inside their fonts, where as Segoe UI does for all numbers and i & n.
Same at the DirectWrite level underneath (which makes sense given that's what it uses).
So it's technically correct behaviour at a font level - you're asking for the Typographic Superset feature that the font doesn't actually support

Thanks @JohnnyWestlake, you are exactly correct.  The text dev I checked with provided a similar description:

There’s a difference between "real" superscript (invoking the sups typographic feature) and "fake" superscript (reducing the font size and moving the text up off the baseline). The Typography.Variants property is invoking a typographic feature, which is the superior approach in terms of typographic quality/legibility, but depends on font support. A font may provide superscript variants for only some characters, not at all.
When you select superscript in many editors, what you’re getting is "fake" superscript, in which it just scales the text and bumps it up off the baseline. This works regardless of the character and font, but is not as legible as superscript glyphs provided by a font. DirectWrite doesn't have a feature to do fake superscript.

As noted above, I've submitted a change to the Typography.Variants documentation to briefly mention that this depends on support in the font.

Thanks @DZetko for raising this issue. With the documentation updated, I'm closing this issue.


Call to a member function getProperties() on boolean

Hello,
After adding @Algolia\Attribute annotation on a property with a ManyToOne assocation I tried to index my entity using app/console algolia:reindex AppBundle:Project.
But this command returns me an error :
PHP Fatal error:  Call to a member function getProperties() on boolean in /home/elodie/workspace/hormann-phototheque/vendor/algolia/algolia-search-bundle/Indexer/Indexer.php on line 407
Here is my entity Project :
https://gist.github.com/elodie-nazaret/acc9765039385ec8f9aa
And there are versions I use :
"symfony/symfony": "2.8.*@dev",
"doctrine/orm": "^2.4.8",
"doctrine/doctrine-bundle": "~1.4",
"algolia/algolia-search-bundle": "^1.0"

Related to issue #27

Ok that's weird, let's try to narrow it down:
Can you try without this line => https://gist.github.com/elodie-nazaret/acc9765039385ec8f9aa#file-project-php-L16
Then if it's not working, can you also try without "OneToMany" attributes ?

I removed @Algolia\Index() but it did not work either.
When I delete all @Algolia\Attribute that are on OneToMany properties it works.

Ok cool, I will look into it asap

Thank you

ping @maxiloc do you have any ETA so we can adapt for this ingoing project that has a close shipping date ?

I starting right now, so probably today

I am still not able to reproduce the issue. I found another one related to oneToMany that I fixed (https://github.com/algolia/AlgoliaSearchBundle/commit/241bb848e03e2f62408d66af3c293f3767f87e9e)
It might also fix this one.
@elodie-nazaret @tristanbes Can you try with "algolia/algolia-search-bundle": "dev-master" in your composer.json and tell me if you still encounter the issue.
I also suspect some symfony/doctrine/composer cache, can you make sure you cleaned it before testing

I tried with "algolia/algolia-search-bundle": "dev-master" but it returns me the same error.

I am still not able to reproduce the issue.

Can you try to reproduce it inside a brand new Symfony2.8 standard edition please ? https://github.com/symfony/symfony-standard/tree/2.8
If I had the problem inside my other project (in 2.4) and this happens again in (2.8) the issue must be real.

I was on 2.6, tried on a clean 2.8 and it still working.
Any debugging you could do to could really help to find where it's coming from, in the meantime I will continue investigating

Ok I managed to reproduce. The issue comes when a relation is an Algolia\Attribute but this relation class does not have any Algolia\Attribute.

@tristanbes @elodie-nazaret There is no fix for this, what I did is throw an more explicit error so that it's easier to understand why it's failing

Sure, maybe you can elaborate on what we were doing wrong ? And add it in the documentation of the bundle so this won't happen again.

Yes when you are indexing a model in Algolia that have a relation the bundle will load this relation and get all indexable algolia attribute in an array and append it to the initial model object.
For example:
class Post
{
    private $title; // Algolia attribute
    private $content; // Algolia attribute
    private $author // Relation to the Author model + Algolia attribute
}

If the Author model don't have any Algolia attribute your were getting a non explicit error. To fix it you need to put Author::$name as an Algolia attribute so that the final record looks like :
{
  "title": "some title"
  "content": "some content"
  "author": {
     "name": "some name"
  }
}

Does that makes sense ?

yeap. Thanks. will close the issue once we test this and see if we get rid of this error. :-)

I tried to add @Algolia\Attribute() in my entity linked but it seems that it doesn't work either... I cleared cache and restarted php before.
There is a part of my Entity Project :
/**
 * Class Project
 *
 * @ORM\Entity(repositoryClass="AppBundle\Entity\ProjectRepository")
 * @ORM\Table(name="project")
 * @Algolia\Index()
 */
class Project
{
    /**
     * @var string
     *
     * @ORM\Column(type="string", name="realisation_name"))
     * @Algolia\Attribute()
     */
    private $realisationName;

    /**
     * @var RegionalManagement
     *
     * @ORM\ManyToOne(targetEntity="AppBundle\Entity\RegionalManagement")
     * @ORM\JoinColumn(name="regional_management_id", referencedColumnName="id")
     * @Algolia\Attribute()
     */
    private $regionalManagement;
}

And there is a part of my Entity RegionalManagement :
/**
 * Class RegionalManagement
 *
 * @ORM\Entity()
 * @ORM\Table(name="regional_management")
 */
class RegionalManagement
{
       /**
     * @var string
     *
     * @ORM\Column(type="string", name="label"))
     * @Algolia\Attribute()
     */
    private $label;
}

And when I tried to execute app/console algolia:reindex AppBundle:Project
It sends me the error :
[Algolia\AlgoliaSearchBundle\Exception\NotAnAlgoliaEntity]
Tried to index `regionalManagement` relation which is a `Proxies\__CG__\AppBundle\Entity\RegionalManagement` instance, which is not recognized as an entity to index.

Did I do something wrong?

@elodie-nazaret Can you send me the full file of Project and RegionalManagement ?

Of course :
Project : https://gist.github.com/elodie-nazaret/acc9765039385ec8f9aa
RegionalManagement : https://gist.github.com/elodie-nazaret/b8cb9a69dd472ee2bfdd

@elodie-nazaret I fix a potential issue with proxies, can you try again with "dev-master"

I changed version to "dev-master", updated composer, cleared cache, restarted php but I still have the same error. I checked that I have your corrective.

ping @maxiloc Do you have an idea of why it still does not work ?

Not yet I am not able to reproduce

@maxiloc to be more convinient, i've invited you to the repo in order you to reproduce the issue if you'd like. I'll remove your rights in an hour or so.
git checkout feature/YP-2147
composer install
php app/console do:da:cr
php app/console do:sc:up --force
php app/console do:fi:lo
app/console algolia:reindex AppBundle:Project

ok I'm checking that right now

Ok I found it !! I am on the fix

Great, thanks, ready to press composer update . ;-)

@tristanbes @elodie-nazaret I pushed to master, it should be good. It was due to the doctrine proxies that were interfering in the indexing

If it is working for you I will tag a new version

Thanks. :-) @elodie-nazaret will tell you if it's ok for tagging.

It works now !
Thanks you @maxiloc  :-)


Handle spawn, exec, execFile

I'm not 100% sure if this was working as designed or is a bug/missing feature. With these changes cp.execFile(..., () => {}) is correctly tracked across async boundaries, assuming that the exit event is considered a valid async boundary.
Instrumenting the stdio handles was required because there's magic that automatically tracks reads and close events and turns them into exit once the last stdio stream closes.
I tested the change with latest node 0.10 and 4.

this looks good to me, sorry for the delay. I haven't been using async-listener these days, so I haven't been watching this repo closely.  @Qard do you still depend on async-listener?
I have not run the tests, or looked at the child_process module closely yet, so not going to merge this, but I'll try to find some time to look at it more closely soon.

Yep, I do still use it. I've yet to see anyone use it with child_process though.

Well apparently this guy does!
On Mon, Feb 29, 2016, 5:53 PM Stephen Belanger<EMAIL_ADDRESS>wrote:

Yep, I do still use it. I've yet to see anyone use it with child_process
though.
—
Reply to this email directly or view it on GitHub
https://github.com/othiym23/async-listener/pull/49#issuecomment-190491612
.

We have an internal tool that spawns external commands during request handling (e.g. it interacts with local git repos). For now we just manually bind the exit callback to the current context (it's just one method) but I thought I'd raise it here in case it's useful to others.

One minor code style nit, but otherwise LGTM. :+1:

Changed the weird expression to a proper if block.


Install packages via rpm-ostree or flatpak

Is your feature request related to a problem? Please describe.
Tried to use linutil to install packages on atomic desktop version of Fedora (Kinoite), but rpm-ostree and flatpak are not supported.
Describe the solution you'd like
Include rpm-ostree or flatpak as supported package managers for installing packages.
Describe alternatives you've considered
n/a
Additional context
Atomic desktops are the future, man!
Checklist

[X] I checked for duplicate issues.
[X] I checked already existing discussions.
[X] This feature is not included in the roadmap.

I'm 99% sure Fedora Kinoite comes with rpm-ostree and the standard rpm. I don't see the issue here.

@adamperkowski  I don’t mean download the package managers, I mean download the other applications (alacrity, vscode, etc.) with rpm-ostree or flatpak. linutil only supports downloads with apt, pacman, or dnf (I think). Kinoite does not use those package managers.

I get what you mean. What I'm saying is I'm 99% sure Kinoite does also use the standard rpm. Linutil supports rpm:
https://github.com/ChrisTitusTech/linutil/blob/26d0adc829ac59893666559f1c126d05b7fddc6b/core/tabs/common-script.sh#L130

Sorry, I don’t see rpm in that list. Am I missing something?

Oh wait, you're right.
Well, we use dnf becuase it's based on rpm. In the current script layout, we'd need to add rpm-ostree as a separate package manager and modify every script.
Technically, we could also add rpm at the end of the list (this way when user has dnf and rpm on their system, dnf is selected).

i'm not using atmoic OS, but as far as i know this is called "layering" and it's not recommended in the community. adding as default may not be a right choice. using classic packages in distrobox is more common.
@adamperkowski do you think adding a flatpak check in every script is a good idea? maybe script can install flatpak if user agrees, or use dnf/apt/etc.. if not.

this is called "layering" and it's not recommended in the community. adding as default may not be a right choice.

I agree.

do you think adding a flatpak check in every script is a good idea? maybe script can install flatpak if user agrees, or use dnf/apt/etc.. if not.

If we were to do this, certainly not by adding a flatpak check in every script.
It should be done like this:

add flatpak to the package manager check in common script (make sure it's the last package manager being checked)
integrate it with the existing flatpak setup
make every script support it

Albeit there is one small issue I see with this: we don't want linutil to be a flatpak wrapper (this has been discussed over several times before).
I get that using flatpak != relying on flatpak but I still think idea this needs more input / a bigger general discussion.
Let me try and summon @nnyyxxxx @lj3954 @guruswarupa here.

I just think the ability to use linutil would be nice for us users that use atomic desktops like Fedora Silverblue, Bazzite, etc. Though, I can understand the hesitancy of building support for flatpaks or rpm-ostree (layering).

this is called "layering" and it's not recommended in the community. adding as default may not be a right choice.

I agree.

do you think adding a flatpak check in every script is a good idea? maybe script can install flatpak if user agrees, or use dnf/apt/etc.. if not.

If we were to do this, certainly not by adding a flatpak check in every script. It should be done like this:
1. add flatpak to the package manager check in common script (make sure it's the last package manager being checked)

2. integrate it with the existing flatpak setup

3. make every script support it

Albeit there is one small issue I see with this: we don't want linutil to be a flatpak wrapper (this has been discussed over several times before). I get that using flatpak != relying on flatpak but I still think idea this needs more input / a bigger general discussion.
Let me try and summon @nnyyxxxx @lj3954 @guruswarupa here.

Check for flatpak is implemented in https://github.com/ChrisTitusTech/linutil/pull/705 but only for the scripts and distros that require flatpak installation as of now.
If we were to implement it for every script along with existing package manager it depends we should discuss this over before adding them to every script

i am packing for fedora. currently we are in dependency hell. the seial-* crates are so old that we have to repackage everting. staging copr: https://copr.fedorainfracloud.org/coprs/solomoncyj/rust
buglist: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&columnlist=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority&email1=solomoncyj%40gmail.com&emailreporter1=1&emailtype1=substring&list_id=13517944&order=status%2C priority%2C assigned_to%2C id%2C &query_format=advanced&short_desc=rust&short_desc_type=anywordssubstr

@decathorpe he is a packager and package reviewer for fedora

/close not planned
while flatpak support exists in some scripts in linutil its best we do not add global support for them, not many people will want the packages being installed as flatpak. I'm pretty sure we have semi-support for detecting flatpak pkgs as of right now ( or i might be wrong and it hasn't been merged yet ).


Tweak glossary definition for Node

The services (eg kubelet) that run on a Node are not the kind of Service that the Kubernetes API knows about. Reword accordingly.
Also, highlight that Docker is one container runtime and that there are others.
Relevant to #5993

#14523 is another pull request with similar aims

Thanks @sftim for the update in #14523, has been closed to focus all efforts on this one.

/lgtm
please note that we might come back to the terminology once an agreement is reached out, is still very active debate on the mailer at this point.


Add allowOperators in DataClassContainsFunctions

Fixes https://github.com/detekt/detekt/issues/5321

Oh! And thanks for your contributions :)

Oh! And thanks for your contributions :)

Thanks :)

Hi @BraisGabin can you guide me why there is one check failing? Thanks


Example 02 is flaky

Haven't looked into it but tracking for now. This is causing our CI to fail, I'll set a max version in the yaml.

This probably isn't the issue, the example is sporadically failing. Need to pin it down, commenting it out for the moment.


install: Use the initially-cloned repo as the base /srv/zulip.git.

This ensures that the next upgrade-zulip-from-git has access to the
commit history of the initial install, if it was from a forked
repository.  /home/zulip/deployments/current and /srv/zulip.git
are not quite organized into the steady-state that they will have
after one upgrade-zulip-from-git:

/home/zulip/deployments/current is its own clone, not a worktree
/srv/zulip.git has an origin of /home/zulip/deployments/current
remote.origin.mirror is set on /srv/zulip.git
remote.origin.fetch is +refs/*:refs/*

All but the first are automatically cleaned up by
upgrade-zulip-from-git when it is next run, using the code added in
30457ecd02b5.  The additional complexity of making an existing
independent clone into a worktree seem not worth solving the first
point.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @alexmv!


Design-Choice: Roles

We have two roles atm:

Trainer creates plans
Player practices the exercises

Should we have

one design for each role, with different possible actions
or a single design with greyed-out buttons for the invalid actions?

single design to reduce workload.

decreases simplicity of design

increases shared mental image of UI between roles
quicker to design

Roles are:
User
Trainer
Manager


[clang-tidy] Vote: Add prefix rules for member variables and template parameters

This PR adds prefix rules for class/struct members and template parameters. In the current draft, the rules are as follows:

Member variables, constants, ... are prefixed with m_. Example: m_handle.

Exception: Class constants do not follow this rule. Example: static const int some_constant.
This does not apply to enum class.

Template parameters (all kinds) are prefixed with T. Example: TMyType.

Voting will close on Friday, 28 May 2021, 18:00 HZDR time.
Vote
Member variables

m_ prefix
Alternative naming (please include)
No prefix/suffix

1
0
0

Template parameters

T prefix
Alternative naming (please include)
No prefix/suffix

1
0
0

Member variables

m_prefix
Alternative naming (please include)
No prefix/suffix

2
0
0

Template parameters

T_prefix
Alternative naming (please include)
No prefix/suffix

2
0
0

Member variables

m_prefix
Alternative naming (please include)
No prefix/suffix

2
0
1

Template parameters

Tprefix
Alternative naming (please include)
No prefix/suffix

2
0
1

Member variables

m_prefix
Alternative naming (please include)
No prefix/suffix

2
0
2

Template parameters

Tprefix
Alternative naming (please include)
No prefix/suffix

3
0
1

Out of curiosity, what is the rational for prefixing template parameters with T? I though most people agree now that we can leave Hungarian notation behind?

Out of curiosity, what is the rational for prefixing template parameters with T? I though most people agree now that we can leave Hungarian notation behind?

In general case, maybe it is not necessary but alpaka provides a really good reason:
https://github.com/alpaka-group/alpaka/blob/2b52e2342e0d11f30c6d7777f7eba935b1900cce/example/helloWorld/src/helloWorld.cpp#L28-L29
https://github.com/alpaka-group/alpaka/blob/2b52e2342e0d11f30c6d7777f7eba935b1900cce/example/helloWorld/src/helloWorld.cpp#L99
And, if we would omit the T-prefix, it is more or less like a API change, because it is integral part of the documentation, in special the TAcc parameter of a kernel.

@SimeonEhrig I don't get your example with alpaka. What is wrong with:
struct HelloWorldKernel{
    template<typename Acc>
    ALPAKA_FN_ACC void operator()(Acc const& acc) const { ... }
};

And, if we would omit the T-prefix, it is more or less like a API change, because it is integral part of the documentation, in special the TAcc parameter of a kernel.

But we are setting guidelines for all future projects, not only for alpaka. And renaming TAcc to Acc in the documentation is almost automatic.

Technically nothing, but it suggest, that the Acc in the host code and the kernel parameter are the same.

Member variables

m_prefix
Alternative naming (please include)
No prefix/suffix

3
0
2

Template parameters

Tprefix
T_Prefix
No prefix/suffix

3
1
1

Voting closed. This PR can be merged.


Gem version and library version are different

Gem version as currently defined in the gemspec is 1.0.0.
But:
$ ruby -r csv -e "p CSV::VERSION"
"2.4.8"

@stomar Good catch... I missed it version before Ruby 2.5.0-rc1. I'm going to bump it version to 2.5.0 for final release.

@hsbt, @stomar - Based on the feature issue on ruby-lang I assumed that the CSV gem version would be independent of the Ruby version. Since the development of the two are independent, does it make sense to keep them the same?
This note in particular led me to believe that CSV/Ruby versioning would be separate:

BTW there should be process in place which ensures, that the libraries are properly versioned, i.e. if something is changed, it cannot have the same version as already released library (see #7761 and #7762).

Thoughts?

Yes. You're right.

@stevendaniels I don't think the gem and Ruby versions should or can be kept the same. I only wanted to point out that CSV::VERSION and gemspec version did not match, which IMO they should. I have no idea what the "correct" version of CSV should be.

I came into this issue as part of diagnosing a change to CSV.generate, described at https://bugs.ruby-lang.org/issues/9988.
In short it looks like CSV.generate changed functionality between Ruby 2.4.4 and 2.5.0, even though CSV::VERSION remains 2.4.8 between the two versions. I encountered this during a Ruby upgrade which broke some tests.
Before:
RUBY_VERSION
# => "2.4.4"
require "csv"
# => true
CSV::VERSION
# => "2.4.8"
::CSV.generate(headers: ["Foo"], write_headers: true) { |csv| }
# => ""

After:
RUBY_VERSION
# => "2.5.0"
require "csv"
# => true
CSV::VERSION
# => "2.4.8"
::CSV.generate(headers: ["Foo"], write_headers: true) { |csv| }
# => "Foo\n"

I'm trying to understand how this repo is used by Ruby as a gem versus Ruby's own csv.rb. Maybe someone could help me understand what's going on here?

The Ruby 2.5.0 release notes describe csv being promoted to a default gem.
Ruby 2.5.0 has its own lib/csv.rb: https://github.com/ruby/ruby/blob/v2_5_0/lib/csv.rb.
2.5.0 also has csv.gemspec: https://github.com/ruby/ruby/blob/v2_5_0/lib/csv.gemspec.
Ruby's own 2.5.0 sets CSV::VERSION as 2.4.8: https://github.com/ruby/ruby/blob/v2_5_0/lib/csv.rb#L211.

(The above seem true for 2.5.1, as well.)
If Ruby has csv.gemspec to pull in csv as a default gem, is a separately installed gem ever used instead of Ruby's own lib/csv.rb?  As recently as https://github.com/ruby/ruby/commit/5c1941a9be56a979c27d740370b781882d344f79 it looks like the csv gem is being vendored.

is a separately installed gem ever used instead of Ruby's own lib/csv.rb?

Yes.
NOTE: You should not reuse a closed issue. You should open a new issue with a link to a closed issue.

@kou I originally wrote my comment as a new issue, for that exact reason, but felt it potentially overlapped so much with this that a comment here was more appropriate, where the context lives. Would you prefer I move my question into a new issue? I have a further question about what "yes" means, since I wasn't clear in my original.

Yes please.


Release v. Next

Coming from https://github.com/ruby-grape/grape/issues/1769#issuecomment-407152519

Released 1.1.0. If other maintainers are reading this would be nice to see some initiative next time ;)


Use server response as stake, do not use local

Coverage remained the same at 30.32% when pulling 8c2d110b35954f2d55298311933f9aacb379b7a1 on qingweibinary:qingwei/major_fixes into 011ed04a93fe99696c7c8adfe43960c3f0efad76 on binary-com:master.


SAKIII-4151 change featured item count style

https://jira.sakaiproject.org/browse/SAKIII-4151

Merged via squash


Sgratzl/hide dialogs

more conservative dialog handling

one at a time
clean up others, too
first remove then reset data

please review again


CustomSSLSocketFactoryClassName is not working for HttpClient

I am trying to reconfigure ribbon HttpClient to trust sefl signed certificates
for that reason I set property in my application.yml file CustomSSLSocketFactoryClassName for custom SocketFactory class but it is not working. The validation of the cert is not successful.
When I debug I can see that RibbonLoadBalancingHttpClient is creating new HttpClient delegate but I want  to put TrustSelfSignedStrategy configuration.

@spencergibb could you please help with this topic.

if you are using spring-cloud-netflix open an issue there.


Improve conflict resolution process

Checking the conflicting file and clicking Commit doesn't feel right. Feels like you're committing a conflicted file and making things worse.

see #60 #47 #18

I think we're as good as we're going to get before we do too much that Git doesn't do. The conflicting goes away once you add a file, just like in command-line and there's a special monitor for checking if conflicting files are modified


Add each containers versions info in UI

We already have UI container info

Add the same for

api
migration

@pashidlos  I actually intended this to mean the VRT release version which corresponds to specific UI, API and migration version. For example, VRT version 5.0.2 will mean VRT_UI_VERSION=5.0.2, VRT_API_VERSION=5.0.3, VRT_MIGRATION_VERSION=5.0.1

@suratdas good point
as I see we passing UI container version in docker atm
https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/blob/master/docker-compose.yml#L19


Update to Gradle 8.6

This PR/commit builds on top of #227 to start from a stable Gradle 7.5 build.

Fix and clean up the pkl-commons-test build script.
Change tests to read test packages/certs directly from
the file system instead of packaging and reading them
from the class path, which is both slower and more complicated.
Update expected checksums of some test packages.
(Not sure why they changed.)
Work around a conflict between Pkl's and Gradle's
Kotlin libraries in the pkl-gradle project.
Fix build deprecation warnings.
Ensure Gradle distribution integrity with distributionSha256Sum.
Manually verify integrity of Gradle wrapper added by this commit.

Result: gw clean build buildNative succeeds with Gradle 8.6.
Hunting down the remaining build deprecation warnings shown
by --warning-mode all is worthwhile but not urgent.
Most (possibly all) of them are caused by Gradle plugins,
which I decided not to update in this commit.

If you can figure out why the hashes changed

Test package zip files are created with Gradle's Zip task, so perhaps something changed there. (I think it would be better to use the same code as pkl project package.) But I didn't have the nerve to investigate further, updated the hashes and moved on.

Thanks! Will review this after #227 is merged.

Test package zip files are created with Gradle's Zip task, so perhaps something changed there. (I think it would be better to use the same code as pkl project package.) But I didn't have the nerve to investigate further, updated the hashes and moved on.

But, as long as these hashes are reproducible, it doesn't really matter that much.

@translatenix can you rebase again? Thanks!

@bioball done

Instead of using a hardcoded string for the build directory we could also use project.layout.buildDirectory`

@StefMa What’s the benefit? It’s quite verbose.

There's also the need to parse the strings, and of course string paths can interfere on Windows...

Hm?

This option is meant for debugging, but I put it back. (At some point it didn't work.)

I think we should try to do the "right thing" and use layout.buildDirectory instead.

Can this be done in a separate PR? "build" is no worse than buildDir.

Some background:
https://github.com/gradle/gradle/issues/26234
Blindly replacing buildDir with layout.buildDirectory doesn't feel like the right solution.
Code such as
 argumentProviders.add(CommandLineArgumentProvider {
   listOf("--output-dir", outputDir.get().asFile.absolutePath) +
     fileTree("src/test/resources/codegenPkl").map { it.absolutePath }
 })

doesn't improve anything because methods such as fileTree() are already lazy.
It only adds unnecessary complexity and makes the build less readable.
And unless I'm missing something, .absolutePath is redundant because Files created with Gradle APIs (which is the only correct way to create Files) are always absolute.

@translatenix From the issue, this:
  testResults.from("${layout.buildDirectory.get().asFile}/test-results/testIntegration/binary")

Can actually be:
  testResults.from(layout.buildDirectory.dir("test-results/testIntegration/binary"))

@sgammon Yeah I wouldn't write such code. But my point still stands--just take a look at the suggested diff.

@translatenix I was just trying to make a case that it can be slightly less verbose than expressed in that issue.
args("--output-dir", "build/testConfigClasses")
args(fileTree("src/test/resources/codegenPkl"))

and
argumentProviders.add(CommandLineArgumentProvider {
   listOf("--output-dir", outputDir.get().asFile.absolutePath) +
     fileTree("src/test/resources/codegenPkl").map { it.absolutePath }
 })

Are not identical behavior, though, because the args in the former are computed immediately; the args are deferred as well as fileTree. layout.buildDirectory is deferred, so the CommandLineArgumentProvider is irrelevant anyway. Gradle, however, will output warnings for $buildDir/ and strings have the downside of parsing and path issues cross-platform; truthfully, I wish Gradle kept it less verbose, but here we are.

In any case, I'm just another PR filer / user, my only intent is to offer a less verbose route in case it is less of a change / less painful to implement. 👍

There's nothing to compute here unless you're trying to hypothetically save a microsecond.
I'm also not aware of any cross-platform issues that layout.buildDirectory solves.
I think a separate PR is the way to go.
I believe there are much more important things to improve (also in the build).

@sgammon Would it be possible, and make sense, to use buildless  for the Pkl build? Sounds like direct competition for Develocity. :-)

Sounds good. I'm not part of the team, just trying to help where I can.

Well I will still give you an instance if you want one, just fill in the form and we can get you in the next beta wave 😎. I am using it on my fork and it works great in the Pkl build. But I'm a build caching nerd and I don't expect everyone to be 🤣

I think you should demo buildless to the Pkl team!

@bioball 👀 if he'd have us we'd be glad! But anyway, it's not right to talk about buildless on your PR 😄 thanks for the Gradle upgrade because it will let me rebase a lot away.

@bioball Ready from my side.

@bioball CI is failing due to some missing task dependencies on createTestPackages. Will send a follow-up PR shortly.


⚠ Secret Website 3 has degraded performance

In 657c2b4, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2141 ms

Resolved: Secret Website 3 performance has improved in 60aa378.


WRN-9396: Samples: Samples are displayed at the wrong resolution

Enact-DCO-1.0-Signed-off-by: SJ RO<EMAIL_ADDRESS>

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


item inside CM disappear when broke

I am using the latest version of this mod, also it happens inside a Giant (diamond) compact machine. I have better barrels from JABBA inside, Tesseract from thermal expansion, conduits from Ender IO and liquids such as water and lava to create a cobble gen using transfer node (item) from Extra Utilities. when I break a blocks (any) inside the Compact Machine, it disappears into the void. Any idea how to fix this? maybe I am using too many entities with my cobble gen? (I have 35 transfer node with respectively 64 world interaction upgrade in them generating cobblestones). Any help is appreciated.

Two options:
a) Upgrade the CM with a Nether Star so it retains its content when being broken.
b) Set the maxDroppedStacks option in the config file to -1 to always drop all stacks when breaking a CM.

blocks broken INSIDE the compact machines disappears into the void, I did not break the compact machine and fyi it is already equiped with a nether star and the maxDroppedStacks is already set to -1


The last line cannot be seen sometimes

Seems that algorithm to calculate available lines have some bugs.

Can you provide some steps to reproduce this? or screenshots.

https://github.com/sourcelair/xterm.js/issues/389

This may be caused by the terminal padding css, I've reverted it (3ac7a5e2aec47b816bd1ae090d40e77ff01147ad, waiting for https://github.com/sourcelair/xterm.js/issues/946), it seems works. I'm going to close this issue.


Add Naresuan University

@kaninsos I am sorry, the domain alumni.nu.ac.th is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Defensive Domain Registration and DNS record creation

Story to cover work of registering 5 defensive domains and configuring standard DNS settings.
Speak to Tony for details

Done


Remove deprecated videojs-contrib-hlsjs

https://github.com/videojs/http-streaming is included in videojs bundle
Side question: would it be feasible to add support of DASH in videojs (using the http-streaming)?

Currently P2P Media Loader supports only Hls.js (p2p-media-loader-hlsjs) and Shaka Player (p2p-media-loader-shaka) HTML5 media playback engine. Video.js is supported only via videojs-contrib-hls.js plugin that enables Hls.js engine for video.js.
videojs-http-streaming is yet another different implementation of HTML5 media playback engine built into video.js and is not supported by P2P Media Loader.
Most likely integration can beimplemented as separater project (i.e. p2p-media-loader-vhs) that shares core functionality with others (p2p-media-loader-core). PRs are welcome.
I will try also investigate the ability of integration once I have spare time.

Oh okay sorry, I thought that videojs-http-streaming included the code of videojs-contrib-hls.js so there were
Thanks @mrlika!


Allow to parse just a lang sub-directory instead of all lang directory

Allow to specify a sub directory to parse, instead of parse everything inside the lang folder.
For example, if you have a js directory under lang directory, maybe you just want to parse what is under this directory instead of all lang directory.

@luiscoutinh Hey, thank you for your PR!
Please give me some time, until I'll be able to look deeper!
Thanks!

I think I'm more of a fan of excluding paths. Also, I think, it should be in a service provider and not in a config file, because we have no other config, it just adds extra complexity on installing/publishing/configuring.
I'll look for a good pattern on how to solve to extend easily the provider.

Since we are caching the parsed data, it has no performance concerns if the parsed data is a bit bigger or not. So, it's much easier to filter the data on the front-end and pass that to the JS class's constructor.
Thanks.


feat: assert code adjust

assert code adjust for volo

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


adafruit-ampy: init at 1.0.7

Motivation for this change
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

@FRidh Fixed :-)

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/52


feat(esl-utils): Transition duration utility

In the scope of this PR I added a utility to get a transition length

To be discussed on tomorrow's call.
We should have a utility to resolve a class of problems but not specific ones. (But you are really close to making this code universal btw) Also, the esl-utils can be extended only with unit tests provided for extending, until it's not agreed with a @exadel-inc/esl-core-team.

/** @example parseTime('.5s') // 500 */
function parseTime(timeStr: string): number;

/** @example parseTimeSet('.5s, 1ms') // [500, 1] */
function parseTimeSet(timeStr: string): number[];
```

:tada: This PR is included in version 4.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow VS Code extensions to trigger audio cues

👋
Feature request: I'm creating a VS Code extension, and I wish I could trigger audio cues!
These audio cues could be the ones that already exist.
It'd also be amazing if I could trigger custom audio cues (eg, a 440 Hertz tone for 150 milliseconds).
This would be particularly helpful for me when my VS Code extension fails early out of a command (eg, maybe there are no results to show for my custom search command) and an audio cue gets triggered so that I'm not relying only on hard to see visual cues.

cc @isidorn for thoughts

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Fair feature request, but backlog candidates for now is the right course of action imho.
@therobinkim can you provide more details about your extension? How would you use audio cues?

a use case of @jooyoungseo #176521

Hi vscode  members,
We should not treat accesssibility issue and normal user issues same. As screen reader users are very less in number compared to normal developer. So please consider this issue and move it to backlog so that team can implement soon.
Please consider this issue even if it does not get 20 upvotes. Thanks.

Hi @balajip881 what is your use case/ which extension would you like this to apply to?

extention name : bookmarks
https://github.com/alefragnani/vscode-bookmarks/issues/601

@meganrogge -- I have encountered the need of this feature again while proposing this feature: https://github.com/iamhyc/Overleaf-Workshop/issues/44
CC @iamhyc

@hediet what do you think about an API for this?

Generally, I think an API could make sense, but needs a lot of thoughts.
In particular, the API should prevent audio-cue reuse by sound (1) and encourage audio-cue reuse by semantics (2), especially if we ever want to consider contributable sound packs.
(1) e.g. when some extension author likes to use the "error" sound as indicator that some process finished successfully.
(2) when a process finished successfully, it should use an audio cue that reflects this semantics.
Maybe an extension could statically declare new audio cues and assign them a default sound (which could be changed by the user or sound-packs). Then, an extension could only play audio cues that it contributed itself.

Hi. I'm not sure if it's related but my needs are related with accessibility.
I'm totally new in vsCode extensions, I started to research today.
Having said that, I need to create an extension that produces tones of different frequencies, shape and duration. As a visually impaired developer, I frequently use tones for various cues. But it would be more useful to be able to implement this in an extension instead of coding it in my test files.
Although I can implement my own wave generator, the audio output is a problem.
So, an API should allow playing audio from files, or from a stream in case the audio waves are created in real time.
I'm sure sighted developers could also benefit from something like this, extensions shouldn't be restricted to just visual aspects.
Well, I think I can solve my needs by creating a Webview and communicating with it, but it doesn't seem like an optimal solution to me because I don't need a webview, it shouldn't even be visible!
In a webview I have access to audioContext, I have done tests and can access the oscillators, I have been able to play my own tones without implementing any wave generator, simply using audioContext from VSCode itself.
So why not make a small part of that API available to extensions without so much overhead?
I will be happy with an interface to play from file, from stream, and stop the current sound.
An event that fires when the sound has stopped would be useful too.
Parallel sounds should be allowed.
Access to the audioContext oscillators would be even better, but not essential.
Sorry if there is an approach to do what I want without webviews, on the webviews section it's suggested to use alternatives whenever they are available but I haven't found alternatives to play sounds from an extension.

I am trying to build an accessibility extension that plays sounds for each level of indent.

cursor moves to a new line.
if that line contains a different number of indent from the previous line, play indent tone.

0 indents plays 220 hz.
Each indent level (as configured by vscode) beyond that, is 1 half tone higher.
Timbre changes based on attributes of the line, I.E. method start, end of an if statement, if statement, for loop, etc.
Vscode's capabilities for playing sounds would be greatly enhanced if this were added. In the perfect world I'd like to be able to contribute signal sounds generated by the web audio api, but I could deal with generating signal sounds from a stream and providing a buffer. Right now, I would either be stuck with low latency options that are not cross platform and don't work on web,  or need to use a web view to get web audio.

The web audio api is not generally available for extensions in event handlers, etc. Spinning up web views is expensive, so I'd prefer to have a more efficient way of doing this.
Please lmk what you think HTH in designing further implementation.

Use case for this for the Copilot Vision Preview extension when alt text quick fix is selected/ resolved. cc @jooyoungseo


Error: unsupported operand type(s) for -: 'str' and 'str'

Updated to the latest HEAD this morning. Got this on restart of the bot.
Jun 11 09:20:31 gasgiant python[13806]: Welcome to Poloniex Lending Bot
Jun 11 09:20:31 gasgiant python[13806]: Started WebServer, lendingbot status available at http://<IP_ADDRESS>:8000/lendingbot.html
Jun 11 09:20:31 gasgiant python[13806]: WARN: Invalid setting for gapMode, using defaults...
Jun 11 09:20:31 gasgiant python[13806]: 2017-06-11 09:20:31 Error: unsupported operand type(s) for -: 'str' and 'str'
Jun 11 09:20:31 gasgiant python[13806]: Traceback (most recent call last):
Jun 11 09:20:31 gasgiant python[13806]:   File "/usr/src/poloniexlendingbot/lendingbot.py", line 79, in <module>
Jun 11 09:20:31 gasgiant python[13806]:     Lending.lend_all()
Jun 11 09:20:31 gasgiant python[13806]:   File "/usr/src/poloniexlendingbot/modules/Lending.py", line 227, in lend_all
Jun 11 09:20:31 gasgiant python[13806]:     usable_currencies += lend_cur(cur, total_lent, lending_balances, ticker)
Jun 11 09:20:31 gasgiant python[13806]:   File "/usr/src/poloniexlendingbot/modules/Lending.py", line 398, in lend_cur
Jun 11 09:20:31 gasgiant python[13806]:     orders = construct_orders(active_cur, active_bal, active_cur_total_balance, ticker)  # Build all potential orders
Jun 11 09:20:31 gasgiant python[13806]:   File "/usr/src/poloniexlendingbot/modules/Lending.py", line 300, in construct_orders
Jun 11 09:20:31 gasgiant python[13806]:     gap_diff = top_rate - bottom_rate
Jun 11 09:20:31 gasgiant python[13806]: TypeError: unsupported operand type(s) for -: 'str' and 'str'
Jun 11 09:20:31 gasgiant python[13806]: Unhandled error, please open a Github issue so we can fix it!

I believe this happened due to "permission denied" in the API calls to poloniex. My external IP changed and therefore my API calls were being blocked.
This should still be an active issue though to properly catch things like this.

I can confirm this bug, and my API calls should not be blocked (relevant IPs are whitelisted; I just double checked). That said, I have noticed that the site is running kind of slow today. Possibly a response to a request timeout?

Oh, glad to hear someone else is having issues. My log is flooded with these today:
2017-06-12 09:52:47 Error: The read operation timed out Requesting returnActiveLoans

I started using a VPN and couldn't tell if it was the VPN or Poloinex at fault.

Yeah, I'm pretty sure this is solidly on Poloniex's side. That said, this seems to be essentially a "cosmetic" issue—when it gets valid data, it works fine. Presumably an easy fix for error handling on request timeout.


Use the GHC specializer to remove pattern matches on era dictionary

This pull request experiments with a simplification of the Cardano.Wallet.Read.* hierarchy where the EraFun f g is removed in favor of a plain type
foo :: forall era. IsEra era => f era → g era

Here, foo pattern matches on the theEra :: Era era dictionary to select the appropriate era. Applying multiple functions of this kind might lead to repeated, redundant pattern matches. However, since era is a type-level argument, we can use the GHC specializer to apply this argument at compile-time — this pull request demonstrates how.
After compiling this module, there is a file dist-newstyle/**/Test.dump-simpl which contains the compile Core of the module. Noteworthy outcomes are:

The function Cardano.Wallet.Read.Test.$wgetHeaderHashLength does a pattern match on the era $dIsEra_s65W :: IsEra era_s65V, but the compiler was able to remove the intermediate match associated with getLength.

The function specializeShelley is completely specialized — the dictionary and any pattern matches on it have been removed.

Closing the pull request, but keeping the branch around. This demonstration has served its purpose.


Rest-auth: Exlamation mark comes before password

I am using rest-auth for authentication.
after registration when I try to login it show
{
"non_field_errors": [
"Unable to log in with provided credentials."
]
}
and when I saw the user on admin panel an an '!' mark comed before password for example
password ='!72wlGF0RiGRraz69sveb63FUrebNkAW9xmOoL16C'
please help

Hi,
as a user of rest-auth, thanks for offering contribution!
This repo is not maintained anymore, so the development moved to dj-rest-auth. (reference: https://github.com/Tivix/django-rest-auth/issues/568)
It may be best, if you move this PR there. (and upgrade to using dj_rest_auth)
new repo link: https://github.com/jazzband/dj-rest-auth (I'm not the upkeeper of that repo, it just makes sense for me to help you write where it brings value.)
Best,
Barney

Use password field is password1 = serializers.CharField(max_length=255, style={'input_type': 'password'})
Write this function on RegisterSerializer
def validate_password1(self, password):    return get_adapter().clean_password(password)
#============================My Code==============================

class RegisterSerializer(serializers.Serializer):
    username = None
    email = serializers.EmailField(required=allauth_settings.EMAIL_REQUIRED)
    full_name = serializers.CharField(required=True, write_only=True)
    phone_number = serializers.CharField(required=True, write_only=True)
    password1 = serializers.CharField(max_length=255, style={'input_type': 'password'})

    def validate_email(self, email):
        email = get_adapter().clean_email(email)
        if allauth_settings.UNIQUE_EMAIL:
            if email and email_address_exists(email):
                raise serializers.ValidationError("A user is already registered with this e-mail address.")
        return email

    def validate_password1(self, password):
        return get_adapter().clean_password(password)

    def custom_signup(self, request, user):
        user.full_name = self.validated_data.get('full_name', '')
        user.phone_number = self.validated_data.get('phone_number', '')
        user.save(update_fields=['full_name', 'phone_number'])

    def get_cleaned_data(self):
        return {
            'email': self.validated_data.get('email', ''),
            'full_name': self.validated_data.get('full_name', ''),
            'phone_number': self.validated_data.get('phone_number', ''),
            'password1': self.validated_data.get('password1', ''),

        }

    def save(self, request):
        adapter = get_adapter()
        user = adapter.new_user(request)
        self.cleaned_data = self.get_cleaned_data()
        adapter.save_user(request, user, self)
        self.custom_signup(request, user)
        setup_user_email(request, user, [])
        return user
`


Make Apalache error handling more robust

In f8defc24eaaa6ecfd021624e1bb3592574fdbabb Apalache error handling scans for any known error strings. This should be improved be instead using the fact that Apalache marks erroneous lines with the letter 'E' next to the timestamp.
Moreover, there are cases where Apalache writes stdout and stderr but this is not handled gracefully in modelator.
Additionally, the latest Apalache version considers found counterexamples to be errors, which when using the current error handling results in an incorrect Error.

Closed by #96


HTML style tags do not have syntax highlighting enabled

Prerequisites

[X ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
HTML style tag syntax highlighting does not work
Steps to Reproduce

Create html file
Write a style tag with a css declaration

Expected behaviour:
Styles would be syntax highlighted
Actual behavior:
Style tag content is not syntax highlighted
Reproduces how often:
100%
Versions
macOS : 10.14
Atom    : 1.31.2
Electron: 2.0.7
Chrome  : 61.0.3163.100
Node    : 8.9.3
apm  2.1.1
npm  6.2.0
node 8.9.3 x64
atom 1.31.2
python 2.7.10
git 2.17.1

Thanks very much for the report!
Would you mind reopening this issue in the language-html repository? When doing so please include some actual code to reproduce this with, thanks! We use multiple repositories to keep the work items tied to the code they apply to. This helps the maintainers spend more time working directly on Atom and less time triaging issues.
Thanks for meeting us halfway :+1:


Make sure indexes are correct in the styles key

Fixes CartoDB/cartodb#7422.
@fdansv can you please review this? Thanks!
cc: @javitonino

Looking good! I was only wondering if in the test, 'Tiled' covers also plain layers. I'm saying this because we often forget to consider plain layers when implementing new stuff and it'd be useful that the test fails whenever that happens.

Hey @alonsogarciapablo. I was going to take a look at this but it is closed, should I take a look anyway?

Not sure what happened. I reopened it again.

Works great!  I just wanted to test the case where a layer with no cartocss was above the rest of CartoDB layers.

Thanks guys!


Release v1.1.3

add rosa list account roles
hack: Add script to list JIRA tickets addressed on current release
add disable workload monitoring to ROSA
update user tag regexp to include unicode spaces
cluster: Support custom properties
Remove ROSA init account command
Add StopInstances action to support Hibernation
add kmskey for sts
RemoveSTSfrominit
Bump OCM SDK to v0.1.209
aws: Silently ignore AccessDenied errors when validating resources
SDA-4829 update getThumbprints to use http package instead of tls
policies: Allow compatible policies to create clusters

/lgtm


Add TSDF support for RealTimeCorrelativeScanMatcher.

Continues https://github.com/googlecartographer/cartographer/pull/1376.
RFC=0019

Merge requested by authorized user kdaun. Merge queue now has a length of 1.


Restrict tritonclient to 2.22.0

Restrict tritonclient to version 2.22.0
The latest version 2.22.3 has permission issue

@EmmaQiaoCh Can we ask for more information on why this is needed. We are trying to move away from version anchoring any packages that dont absolutely need it. And we rely on the proto message from the tritonclient so we would like to keep them as up-to-date as possible? @benfred @EvenOldridge for viz


fix(transliterate): installing snippet dependencies can fail due to scripts

Also added some other improvements to the installation step.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

💚 All backports created successfully

Status
Branch
Result

✅
maintenance/v5.3

✅
maintenance/v5.4

Questions ?
Please refer to the Backport tool documentation and see the Github Action logs for details


Update JavaThemis Secure Cell API

This PR makes preparatory changes for new passphrase API by updating existing API of Secure Cell in JavaThemis to more easy to use and similar to other Themis wrappers. The API is described in RFC 3.9.
User notes
SecureCell class now provides improved Secure Cell interfaces:

SecureCell.Seal
SecureCell.TokenProtect
SecureCell.ContextImprint

as well as new static factory methods for them, accepting symmetric keys:

SecureCell#SealWithKey
SecureCell#TokenProtectWithKey
SecureCell#ContextImprintWithKey

All of this can be used like this in Java:
import com.cossacklabs.themis.SecureCell;
import com.cossacklabs.themis.SymmetricKey;

SymmetricKey masterKey = new SymmetricKey();

SecureCell.Seal cell = SecureCell.SealWithKey(masterKey);

byte[] message = "precious message".getBytes(StandardCharsets.UTF_8);

byte[] encrypted = cell.encrypt(message);
byte[] decrypted = cell.decrypt(encrypted);

assertArrayEquals(message, decrypted);

Optional associated context
All encrypt and decrypt methods now have an overload without an optional argument for associated context. This makes the code that does not use it more concise. (Of course you can still pass null there if you must.)
Nullability annotations
New interface are properly annotated with @NotNull and @Nullable which improves IDE experience and enables more static checks.
SecureCellData usage
Note that with new interfaces you no longer have to construct SecureCellData objects to decrypt data. Just pass your byte[] with encrypted data directly to decrypt() methods. In Token Protect mode you pass encrypted data and authentication token as separate byte[] arrays too.
Similarly, Seal and Context Imprint modes return encrypted byte[] directly. You no longer have to getProtectedData() from the returned SecureCellData object.
Token Protect mode still returns SecureCellData from its encrypt() method. That's the way it is with Java, which has no multiple return values. This will be improved for Kotlin a bit later.
Pending deprecations
This PR does not deprecate the old API, but consider it deprecated.

Construction of SecureCell with new.
protect and unprotect methods.

(This list will be updated when the API is actually deprecated.)
Technical notes
Full rationale may be found in RFC 3.9. Main gripes with the old API were run-time mode-setting with its impact on API, syntactic noise when using more popular Seal mode, and idiosyncratic naming of methods, inconsistent with other wrappers and our own documentation.
New API does not accept String values. The old API encoded strings in platform-specific UTF-16 which was quite unique and not portable to other platforms. Furthermore, it suggested that strings can be used as passphrases, which is not secure in typical case.
At last, in order to decrypt Sealed data, instead of writing
byte[] decrypted = cell.unprotect(null, new SecureCellData(encrypted, null));

you can write much more readable code:
byte[] decrypted = cell.decrypt(encrypted);

And yes, the context now comes after the data, as in all other wrappers.
Last but not least, Secure Cell gets an expanded and updated test suite (translated from whatever was done for SwiftThemis). This will definitely come handy if we are going to reimplement JavaThemis in pure JVM code some day.
Note that JNI API and ABI does not change. We decided to keep compatibility here.
Targeting Java 7
I have discovered that Android compiles its code for Java 7 by default. I wanted to use Java 8 features in tests initially, but given the Android story I think we should use Java 7 even for desktop Java code.
Note that embedded Gradle wrapper still requires Java 8 to run. However, the compiled code will run on Java 7 too.
New TODOs and FIXMEs
This PR adds a bunch of new TODOs in the code. While it's not nice, I don't want to block further development with those issues. They will be resolved later:

Fix a bug in JNI code that crashes tests on Android.
Fix an issue in Themis Core which causes the same test to behave unexpectedly.
Signal exceptions from within JNI code instead of checking for null in Java code.

Next tasks

Add passphrase API. Can be done in parallel, will be submitted after this PR is merged.
Deprecate old API. Since we will have to deprecate a lot and provide good migration instructions, I decided to split this out into a new PR.
Add Kotlin tests. It will be nice to actually see how our code can be used from Kotlin. Adding it is trivial, but not quite trivial.
Improve Kotlin support. RFC 3.9 plans several additional changes in Token Protect API to improve its usability in Kotlin.
Update examples. Both in-repo and external ones. They are quite outdated so it may require additional refactoring.

Checklist

[X] Change is covered by automated tests
[X] Benchmark results are attached (we have no JVM benchmarks)
[X] The coding guidelines are followed
[X] Public API has proper documentation
[X] Example projects and code samples are up-to-date (will do later)
[X] Changelog is updated

Oh ffs, Android! :rage1:  :rage2:  :rage3:  :rage4: (ノಠ益ಠ)ノ彡┻━┻
It fails on CircleCI with a specific older API level:
10:01:41 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: stack=java.lang.NoSuchMethodError: No static method decodeBase64(Ljava/lang/String;)[B in class Lorg/apache/commons/codec/binary/Base64; or its super classes (declaration of 'org.apache.commons.codec.binary.Base64' appears in /system/framework/org.apache.http.legacy.boot.jar)
10:01:41 V/InstrumentationResultParser: at com.cossacklabs.themis.test.Base64$Decoder.decode(Base64.java:27)
10:01:41 V/InstrumentationResultParser: at com.cossacklabs.themis.test.SecureCellContextImprintTest.initWithFixed(SecureCellContextImprintTest.java:44)

But it's fine on my machines, obviously.
These unicorns seem to include Base64 from org.apache.commons.codec into their system library, making in impossible to use a proper dependency. java-stellar-sdk have had the same issue.
Now I'm tempted to either remove base64 tests, or just implement the decoder myself. Yes, it will be 36th base64 decoder implementation in the ecosystem. I guess all prior attempts were caused by similar frustration.
Unfortunately, Java does not make conditional compilation easy. Otherwise we might have used android.util.Base64 on Android, and a proper library on sane systems that don't believe they know better what library version the applications should use.


improve the doc to indicate how to get Spring

Hi,
First of all thanks for this great library.
as the first time using this library, the README did not help me to know how to get the Spring out of the library, it is not mentioned anywhere in the README and I think it is important as a "Getting Started".
The examples didn't help neither because they directly requires the Spring file (I think it should be better to extract the things from the library root).
So for now, maybe I'm wrong, but the only way to figure this out is to look at the library code.
Thanks

It says before this line that the library exports Spring, among others.
That being said, I guess not everyone sees that. Can you remove the space between {}? I'll merge this after.

done :)
I've used your neat library for a cool example I'm going to release soon, I'll show you ;)

Thanks!


CC-Tweaked compatibility in mc1.20.1/fabric/dev

I noticed that Create crashes whenever the mod cc-tweaked was installed as well.
Create-fabric previously was made compatible for CC:R v1.102.6 (or something similar), which is much older than the latest version we have in CC:T now. Some stuff changed within time, including how peripherals are registered, which is why the game now crashes.
Therefore, I adjusted the code to work within the latest version of ComputerCraft (cc-tweaked), instead of cc-restitched for mc1.20.1
I kept the changes as minimal as possible and it (hopefully) should work without any issues.

TL;DR

I would love this to be added

update the runtime cc dependency too and this should be good


Packages compatible with both 0.15 and 0.16 show up as "not updated for 0.16"

E.g. elmfire supports both Elm 0.15 & 0.16, but is shown in the section "The following packages have not been updated for 0.16 yet!".

But not all packages that support both Elm 0.15 & 0.16 are shown in that section. E.g., elm-drag-and-drop isn't.

Do you know how many packages are like this?
There's just some code that adds new libraries to this list if the contain 0.16 in their elm-version. Not sure how elmfire got through but I can add it along with anything else you know is like that.

Your particular case should be resolved, not sure about others though.


TvChannelManager Cluster errors

Problem

read tv-channel-lineup, current-tv-channel  not implemented yet

If added in my local with aEncoder.Encode(channelLineupInfo) and the chip-tool will response Wrong TLV type

ChangeChannel Request has no response

src/app/clusters/tv-channel-server/tv-channel-server.cpp, // TODO: Enable this once struct as param is supported

logs for read tv-channel-lineup
[1637755782706] [2809:25148] CHIP: [EM] Received message of type 0x5 with protocolId (0, 1) and MessageCounter:1 on exchange 56081i
[1637755782707] [2809:25148] CHIP: [EM] Rxd Ack; Removing MessageCounter:1 from Retrans Table on exchange 56081i
[1637755782707] [2809:25148] CHIP: [EM] Removed CHIP MessageCounter:1 from RetransTable on exchange 56081i
[1637755782707] [2809:25148] CHIP: [DMG] ReportDataMessage =
[1637755782707] [2809:25148] CHIP: [DMG] {
[1637755782707] [2809:25148] CHIP: [DMG]        AttributeReportIBs =
[1637755782707] [2809:25148] CHIP: [DMG]        [
[1637755782707] [2809:25148] CHIP: [DMG]                AttributeReportIB =
[1637755782707] [2809:25148] CHIP: [DMG]                {
[1637755782707] [2809:25148] CHIP: [DMG]                        AttributeDataIB =
[1637755782707] [2809:25148] CHIP: [DMG]                        {
[1637755782707] [2809:25148] CHIP: [DMG]                                AttributePathIB =
[1637755782707] [2809:25148] CHIP: [DMG]                                {
[1637755782707] [2809:25148] CHIP: [DMG]                                        Endpoint = 0x1,
[1637755782707] [2809:25148] CHIP: [DMG]                                        Cluster = 0x504,
[1637755782707] [2809:25148] CHIP: [DMG]                                        Attribute = 0x0000_0001,
[1637755782707] [2809:25148] CHIP: [DMG]                                }
[1637755782707] [2809:25148] CHIP: [DMG]
[1637755782707] [2809:25148] CHIP: [DMG]                                        Data =
[1637755782707] [2809:25148] CHIP: [DMG]                                        {
[1637755782707] [2809:25148] CHIP: [DMG]                                                0x0 = "postalCo",
[1637755782707] [2809:25148] CHIP: [DMG]                                                0x1 = "lineup",
[1637755782707] [2809:25148] CHIP: [DMG]                                                0x2 = "postalCode",
[1637755782707] [2809:25148] CHIP: [DMG]                                                0x3 = 0,
[1637755782707] [2809:25148] CHIP: [DMG]                                        },
[1637755782707] [2809:25148] CHIP: [DMG]                                DataVersion = 0x0,
[1637755782707] [2809:25148] CHIP: [DMG]                        },
[1637755782707] [2809:25148] CHIP: [DMG]
[1637755782707] [2809:25148] CHIP: [DMG]                },
[1637755782707] [2809:25148] CHIP: [DMG]
[1637755782707] [2809:25148] CHIP: [DMG]        ],
[1637755782707] [2809:25148] CHIP: [DMG]
[1637755782707] [2809:25148] CHIP: [DMG] }
[1637755782707] [2809:25148] CHIP: [ZCL] ReadAttributesResponse:
[1637755782707] [2809:25148] CHIP: [ZCL]   ClusterId: 0x0000_0504
[1637755782707] [2809:25148] CHIP: [ZCL]   attributeId: 0x0000_0001
[1637755782707] [2809:25148] CHIP: [ZCL]   status: Success                (0x0000)
[1637755782707] [2809:25148] CHIP: [ZCL]   attribute TLV Type: 0x15
[1637755782707] [2809:25148] CHIP: [ZCL] Failed to get value from TLV data for attribute reading response: ../../examples/chip-tool/third_party/connectedhomeip/src/lib/core/CHIPTLVReader.cpp:398: CHIP Error 0x00000026: Wrong TLV type
[1637755782707] [2809:25148] CHIP: [TOO] Default Failure Response: 0x87
[1637755782711] [2809:25148] CHIP: [EM] Piggybacking Ack for MessageCounter:1 on exchange: 56081i
[1637755782711] [2809:25148] CHIP: [IN] Prepared encrypted message 0x145812680 to 0x000000000001B669 of type 0x1 and protocolId (0, 1) on exchange 56081i with MessageCounter:2.
[1637755782711] [2809:25148] CHIP: [IN] Sending encrypted msg 0x145812680 with MessageCounter:2 to 0x000000000001B669 at monotonic time: 1346794 msec
[1637755782711] [2809:25148] CHIP: [DMG] Client[0] moving to [UNINIT]
[1637755782711] [2809:25143] CHIP: [-] ../../examples/chip-tool/third_party/connectedhomeip/zzz_generated/chip-tool/zap-generated/cluster/Commands.h:2054: CHIP Error 0x000000AC: Internal error at ../../examples/chip-tool/commands/common/CHIPCommand.cpp:84
[1637755782711] [2809:25143] CHIP: [TOO] Run command failure: ../../examples/chip-tool/third_party/connectedhomeip/zzz_generated/chip-tool/zap-generated/cluster/Commands.h:2054: CHIP Error 0x000000AC: Internal error
[1637755782737] [2809:25143] CHIP: [CTL] Shutting down the System State, this will teardown the CHIP Stack
[1637755782737] [2809:25143] CHIP: [DL] Inet Layer shutdown
[1637755782737] [2809:25143] CHIP: [DL] BLE shutdown
[1637755782737] [2809:25143] CHIP: [DL] System Layer shutdown

Please file this issue in the Test Harness repo. Closing it here.


Update sdpa function with enable_gqa=True

For the llama model, in the sdpa function call, set enable_gqa=True to use the inbuilt grouped query attention functionality

I think we should wait a bit to get this in, since a lot of users are still using the old version of PT which doesn't support enable_gqa.


Prisma Datamodel: Primary key as a combination of two relational models

I have a problem in Prisma data modeling where I have to constrain that a user can submit only one review for a product.  I have following design for the non-constrained situation.

Should Customer and Product be combined into a primary key in ProductReview model, or should this constraint be imposed at the application server level, and not at the database level?

Datamodel for now (non-constrained version):
type Product {
  id: ID! @unique
  title: String!
  reviews: [ProductReview!]! @relation(name: "ProductReviews", onDelete: CASCADE)
}

type Customer {
  id: ID! @unique
  email: String @unique
}

type ProductReview {
  id: ID! @unique
  forProduct: Product! @relation(name: "ProductReviews", onDelete: SET_NULL)
  byCustomer: Customer!
  review: String!
  ratinng: Float!
}

Describe the solution you'd like
It would help to have a model similar to my ER diagram, that is, a set of fields selected as the primary key.
Describe alternatives you've considered
As suggested in answers to my stackoverflow question on this issue, I should handle this constraint at the application server level.

Hey @devautor ,
thanks for reaching out to us and providing such a thorough feature request! 🙏
I think your issue could be adressed through combined unique indexes. They are not implemented yet but we already have a spec for it. I would be curious to hear if you think that this feature could solve your problems.

Hello @mavilein Thanks for your kind response! I did go through that spec, and it certainly seems to be the answer. On my own, I was trying to make a Type like the following, before realizing that @unique is reserved for scalar fields only:
type ProductReview {
  id: ID! @unique
  primaryKey:  ProductCustomerKey!  @unique
  review: String!
  ratinng: Float!
}

type ProductCustomerKey {
  forProduct: Product!
  byCustomer: Customer!
}

Hey @devautor, thanks so much for opening this issue. When I asked you on SO to create this FR I was not aware that we already had an open FR for this, you can find it here. I'm going to close this issue as a duplicate of #171, please leave your +1 on the other FR 👍 🙂

@devautor  This solution doesn't work because Prisma requires @id for one of each type field, which makes the


Design gmax

Allow user to set the type of design check to be run
<cmduser command="; CXL $MODULE STEELDESIGN" />
<cmdcalculation command="; CXL $MODULE CALC">
  <design>
    <!-- <cmax /> -->
    <gmax />
    <autodesign>false</autodesign>
    <check>true</check>
  </design>
</cmdcalculation>

https://github.com/strusoft/femdesign-api/blob/0779d5aa6580e245567cc141be29428fb54d05f6/FemDesign.Core/Calculate/Design.cs#L13-L16

There are no clue on what to use in Cmax and Gmax.
The example.fdscript does not show the the value to use in the xml attribute unfortunately.

it might be a:
cmax or gmax 😄

it worked!
The code will serialize cmax or gmax depending on the input


[UX] recommended 'follow' command does not work in windows shell.

Clicking the 'follow' link on the website and selecting 'command line with Keybase' recommends that you run 'keybase follow <>'. Opening the Keybase Shell on windows and running this command does not perform the follow operation, it instead returns "No help topic for 'follow'".
Whether this command is unimplemented in windows or requires different formatting and does not yet have help file information, this is a common user-story that does not go as expected.
my log id: 03bf967a57321afccce5f71c

CC @zanderz

We probably just haven't done a Windows release since changing the command.  keybase track should do the same thing as keybase follow does on the other platforms, for now.

Agreed
On Sunday, August 21, 2016, Jeremy Stribling<EMAIL_ADDRESS>wrote:

We probably just haven't done a Windows release since changing the
command. keybase track should do the same thing as keybase follow does on
the other platforms, for now.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/3989#issuecomment-241298392,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_84GncyX_P_kuCN3u91R_IVLW30zks5qiQBhgaJpZM4JpazC
.

I also noticed that if you haven't entered your pass phrase, look for a screen with one. I'm on Win7 64bit and the 'enter pass phrase for tracking' screen was hidden behind some other screens. My first keybase follow was 'stuck' at me answering the Publicly follow y/n question, the second follow in a new shell worked after I entered my pass phrase.
The shell with my first follow is/was still stuck, but using the same command in my second shell allowed keybase to process the request using cached data.
I sent a log, ID 20ef0fdbc5aa8f6b8fc9c01c


Light!

This PR adds lighting to the world. By default, lighting is disabled to keep fps high. To enable lighting, add -l to your launch args and your set! If you decide you want to turn lighting on, make sure your using a fresh map because any changes you make won't update the light map when lighting is off. Example:

TODO:

Document code
Clean up code
Multi-thread it!
There is a bug I'm aware of having to do with global lighting where, if the global light updates a chunk 2 chunks below where the block was destroyed, it won't update. But, the map is too small to run into this problem yet. Later I want to update the algorithm to make it smarter.
Make global light respond to time of day. There is a parameter in Chunk#calculateLighting(...) to set the global light for that chunk.

And please review and give feedback!

Hmm, a few conflicts with @Col-E 's branch. Will merge it a bit later ;)

I can try to fix them right now.

Thanks a lot ;)


buildGraalvmNativeImage: fix Unicode issue by setting encoding explicitly

Description of changes

Fixes https://github.com/NixOS/nixpkgs/issues/260161.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

CC @diegobfernandez @sg-qwt for testing.


Update Jenkins compatibility

Trello: https://trello.com/c/YMYfR7Xq/38-update-github-branch-plugin-for-ci-jenkins
This goes through and updates the various Jenkins XML files to be XML 1.1 and not have a trailing new line - this is to avoid puppet constantly changing them. I wasn't sure if all of these files were used or not but updated them all anyway.
It updates the application job builder for up to date versions of plugins, most notably github-branch-source-plugin which needed reconfiguring.
Finally it updates the remaining Jenkins plugins for CI.

What's with the no trailing \n thing?  That looks weird!

@sihugh I know it's very annoying. I had to reconfigure my text editor to not auto add them.
Without it the puppet runs for Jenkins are annoyingly like this:
Notice: /Stage[main]/Govuk_jenkins::Config/File[/var/lib/jenkins/hudson.model.UpdateCenter.xml]/content:
--- /var/lib/jenkins/hudson.model.UpdateCenter.xml	2018-04-23 10:06:01.151612090 +0000
+++ /tmp/user/0/puppet-file20180423-32321-1p4cxi2	2018-04-23 10:07:04.719172095 +0000
@@ -4,4 +4,4 @@
     <id>default</id>
     <url>http://updates.jenkins-ci.org/update-center.json</url>
   </site>
-</sites>
\ No newline at end of file
+</sites>


Official Zathura theme for Dracula

Hello, Dracula creator here 👋
I saw your post on Reddit and I noticed you created a Zathura theme for Dracula (https://github.com/OfficialOxide/dotfiles/blob/c9413c38c270db3755b8c650454fa98c159a5701/zathura/.config/zathura/zathurarc#L5).
What do you think of transforming that into an official Dracula theme?
Here's more info about that: https://draculatheme.com/contribute

Hello, I think you would find that the original Dracula colorscheme for Zathura is located here.


Publish package release with tiledbsoma==1.8

1.8 is available - need to release on top of it

Fixed by the https://github.com/chanzuckerberg/cellxgene-census/releases/tag/v1.11.1 release.