UX for multiple code generators in a single ServiceX end-point

As an end-user of a ServiceX datastream, I'd like to be able to specify which code generator is used to generate the code that will power my requested transform. This will allow me to use powerful new transform tools to change the data from an experiment's binary format.
Assumptions

ServiceX needs only a string to tell it what the code generator should be
The string is embedded in the JSON that is part of the initial transform request API call (see post callback).
The string is simple and user-friendly. Like "atlas-xaod-r21" or "cms-miniaod" or similar.
The service can report the list of supported code generators
Code generators should be named like docker hub images (atlas/xaod:22)

Discussion

Places where this could be specified, and its UX implications.

In the servicex.yaml file

This means your endpoint name will always be associated with a particular code generator.
You would use different endpoint names for different generators in your code, tho they would all end up going to the same web address.
This also implies that once you create a dataset in your code, where you specify the end point, you'll always use the same code generator for that data set.

As an argument to the creation of the ServiceXDataset.

The image argument already exists here, which gives you the tag your transformer will run.
Tigly ties the code generator to the data, not the end-point, which makes sense from a design POV.

As an argument to the get_data_xxx method that renders the request to ServiceX.

Ties the code-generator specification tightly to the qastle (or whatever) query.

The code generator is mainly tied to the dataset, so it seems to make sense to specify it when you specify the dataset. However, this also means that you have to specify a bunch more info when you create the dataset - so the dataset creation is now getting more complex. However, most users will only be using a single code generator, so that will add noise to the code.
At some level, most users will see this interface through something up one level - in another library, like func_adl_servicex (or func_adl) or similar. So some of the above is about making the capabilities available in an easy-to-use way in those libraries.
How will other libraries use this?
Here is a current example query for a xAOD transform:
   ds =  SXDSAtlasxAODR21("rucio://mc16_13TeV:mc16_13TeV.361106.PowhegPythia8EvtGen_AZNLOCTEQ6L1_Zee.deriv.DAOD_PHYS.e3601_e5984_s3126_s3136_r10724_r10726_p4164", backend="xaod_r21")
    jets = (ds
            .SelectMany(lambda e: e.Jets())
            .Where(lambda j: (j.pt() / 1000) > 30)
            .Select(lambda j: j.pt() / 1000.0)
            .AsAwkwardArray('JetPt')
            .value())

A few things of note:

The xaod_r21 already implies a backend web address and a generator.

First, if the user has only a single end point in their servicex.yaml file:
   ds =  SXDSAtlasxAODR21("rucio://mc16_13TeV:mc16_13TeV.361106.PowhegPythia8EvtGen_AZNLOCTEQ6L1_Zee.deriv.DAOD_PHYS.e3601_e5984_s3126_s3136_r10724_r10726_p4164", codegen="xaod_r21")
    jets = (ds
            .SelectMany(lambda e: e.Jets())
            .Where(lambda j: (j.pt() / 1000) > 30)
            .Select(lambda j: j.pt() / 1000.0)
            .AsAwkwardArray('JetPt')
            .value())

And the backend could still be a valid argument incase they had multiple places they were running services queries (this would be mostly a developer or tester feature).
From the point of falling into a pit of success it might be nice if this just worked:
   ds =  SXDSAtlasxAODR21("rucio://mc16_13TeV:mc16_13TeV.361106.PowhegPythia8EvtGen_AZNLOCTEQ6L1_Zee.deriv.DAOD_PHYS.e3601_e5984_s3126_s3136_r10724_r10726_p4164")
    jets = (ds
            .SelectMany(lambda e: e.Jets())
            .Where(lambda j: (j.pt() / 1000) > 30)
            .Select(lambda j: j.pt() / 1000.0)
            .AsAwkwardArray('JetPt')
            .value())

And similarly for the SXDatasetUproot assuming a servicex.yaml file followed some naming conventions (which are currently implemented).
Regardless, this feels more natural than specifying the code generator as an argument to the value.
Proposal
In order of precedence:

Allow a codegen argument to dataset creation
Allow a default code generator to be specified in the servicex.yaml file.

Things that need to be tracked

Make sure the code generator is part of the local cache hash algorithm so the same dataset with different code generators causes a different cache key!

Concerns
Some of these will have to be understood before we code this up, others are longer-term.

How do we properly support reproducibility. For example, if a code generator is updated and produces different results, how do we go back to reproduce what we had before (e.g. compare)?
Is the current image argument to ServiceXDataset too useful to ignore? Can it be replaced by func_adl predicates? DOes it make sense if we also specify the code generator (accidentally use the uproot code generator and the xaod transformer. Good times).

Hi Gordon, Tal,
A couple of things that come to mind (some discussed at the last ServiceX meeting) -

specifying a code generator amounts to specifying a codegen/transformer stack if it's going to make sense (though for testing reasons it would be good to still be able to specify the transformer image independently).
this would seem to imply some kind of codegen-transformer pairing registry
it would be nice to avoid the proliferation of classes like SXDSAtlasxAODR21 throughout the frontend codebase - it ties the frontend code unnecessarily to the evolution of the transformers (like, why should we need a new frontend release if ATLAS bumps its release numbers?). I'd hope that flexible codegen choice + hosting multiple transformers in a single instance allows for a single, uniform entrypoint for the user.

specifying a code generator amounts to specifying a codegen/transformer stack if it's going to make sense (though for testing reasons it would be good to still be able to specify the transformer image independently).

@ponyisi - the deployed code generators know about their preferred transformer image, so users don't have to specify an image. However, as always there is a property in the transform request where a user can provide a specific image they want to use. If the transformer doesn't match the code generator it will fail in many wonderful ways.

it would be nice to avoid the proliferation of classes like SXDSAtlasxAODR21 throughout the frontend codebase - it ties the frontend code unnecessarily to the evolution of the transformers (like, why should we need a new frontend release if ATLAS bumps its release numbers?). I'd hope that flexible codegen choice + hosting multiple transformers in a single instance allows for a single, uniform entrypoint for the user.

@ponyisi - I don't know how to avoid this - you need to send down some type information to ServiceX code translator. And you'll want it locally anyway to try to detect mistakes where you make them.
BTW, you can avoid this if you want - it is just you'll get a lot less error checking before the request is sent down to ServiceX. Also, you would lose, on xAOD, the ability to do corrections and systematic errors.
Under the hood, this is just the dataset created with some typing information, as it turns out. So this is a very thin wrapper.
Maybe there is a way around this, but lets get this working and then go from there. But it was the first solution to the issue of not updating the backend everytime ATLAS modified the xAOD release.

Hi all,
I've just published an alpha release here: https://github.com/ssl-hep/ServiceX_frontend/releases/tag/2.6.2a1, meant to be used to test the new backend against. This release just adds an optional codegen argument to the ServiceXDataset constructor which is added to the json query under the "codegen" key.
The plan is to make this more elegant and include logic to read from the default config and user-defined servicex.yaml file, but for now this can be used to test the backend just fine.

Thanks! This is done, then! :-)


ci: Use datadog agent-github-action

Proposed changes:

Replace the custom DataDog agent docker setup with the official GitHub Actions
Enable pytest profiling in the CI

UNIX only
No Windows. Multi-process profiling on windows does not work becuase it requires os.register_at_fork(), which only supports Unix (Source)

Definition of Done:

[X] DataDog CI works fine with the new DataDog agent GitHub Actions
[X] pytest profiling data is shown in DataDog APM in real time

Would really appreciate if someone has the bandwidth to take care of this PR since I cannot push any commits to the branch.


Update Perspective badge to operating

Thank you for your pull request and welcome to our community! We require contributors to sign a Contributor License Agreement and we don't seem to have CLAs on file for these contributors to the Pull Request: (@antonyleons). In order for your PR to be reviewed and merged, please follow the directions at the link above.
Project team: please do not merge this Pull Request until Foundation staff have confirmed that a CLA is in place for the new contributor(s) listed above.
If you still have any questions or just don't know what to do next, please email<EMAIL_ADDRESS>/CC @finos-admin

Dear @AntonyLeons , the activities.json file is automatically generated from our internal metadata system. Based on FINOS lifecycle criteria, the Perspective project is still not considered active.
Please let me know if you have further questions.

the README file has an operating badge in the perspective repo, please correct

Thanks @AntonyLeons , we will definitely check and fix our internal metadata.


Void Space after commande line

environment

vim: 7.4
vim-airline: last
OS: OS X 10.10.5
terminal: iTerm and default terminal

actual behavior
Hello, I have a black line on the bottom from my terminal. In this line, isn't possible to do anything. It's simple black line and showing only if the terminal is Full Screen !
expected behavior
It's possible to remove this supplementary line and have only one line for the command?

looks like this is caused by the terminal being not large enough to have vim draw a new line. There is nothing vim-airline can do about it.


Error parsing Cloudflare IUAM Javascript challenge. Cloudflare may have changed their technique, or there may be a bug in the script.

In text:
Trying to login...
Traceback (most recent call last):
  File "anime_dl\__main__.py", line 18, in <module>
  File "anime_dl\__main__.py", line 75, in main
  File "anime_dl\AnimeDL.py", line 30, in __init__
  File "anime_dl\sites\crunchyroll.py", line 46, in __init__
  File "anime_dl\sites\crunchyroll.py", line 82, in webpagedownloader
  File "requests\sessions.py", line 521, in get
  File "site-packages\cfscrape\__init__.py", line 47, in request
  File "site-packages\cfscrape\__init__.py", line 77, in solve_cf_challenge
  File "site-packages\cfscrape\__init__.py", line 107, in solve_challenge
ValueError: Error parsing Cloudflare IUAM Javascript challenge. Cloudflare may have changed their technique, or there may be a bug in the script.

Please read https://github.com/Anorov/cloudflare-scrape#updates, then file a bug report at https://github.com/Anorov/cloudflare-scrape/issues.
[6788] Failed to execute script __main__

https://github.com/Xonshiz/anime-dl/releases/tag/2018.01.27.a

Sorry, didn't notice the update.
Thank you very much.


Rename C module map libraries with prefix C-(libraryname)

I suggest we rename our modulemap repositories to match the Swift recommended convention to use "C-(libraryname)".

[x] Kitura-HttpParserHelper becomes CHttpParser
[x] Kitura-Pcre2 will be removed
[x] Kitura-hiredis becomes CHiredis
[x] Kitura-CurlHelpers becomes CCurl
[x] Change import HttpParserHelper' to import CHttpParser' in Kitura-Net
[x] Change import CurlHelpers' to import CCurl' in Kitura-Net
[x] Change the URL in Package.swift in Kitura-Net to new repos
[x] Change the URL in Package.swift in Kitura-Router to new repos
[x] Change the URL in Package.swift in Kitura-CouchDB to new repos

Much of this is now relevant now that our helpers no longer are built C static libraries, rather modulemaps with a header file that helps Swift interface with the problematic C functions (such as variadic). Plus, these might be useful out of the context of Kitura, altogether- as a dependency for external projects needing similar functionality.

I think this will break master, so we have to change both branches in parallel.

Rename the repositories in Github appropriately
Change the URL paths in Package.swift in both develop and master
Change the modulename to C-(libraryname)
Tag the latest

Validated during peer programing process.


Error after several minutes

Hello, after 45min - 1 hours
I have a lot of error

I have take testing on divers Apple Device. I think this issue can come when divers Apple devices is connected in same time  AirPlay.
Sorry for bad english :)

Could you try with the branch feature/audio-sync ?


Create QGIS instructions for identifying training data

We'll want to create instructions for users to make their own training data.
Right now, this procedure would be to draw polygons on a sample Planet image (e.g. define snow and no-snow areas) in QGIS or ArcGIS. Then the functions in planetsca use these polygons and the image to build a training data set.
I think a written guide on how to do this, plus a short video tutorial would be helpful.
We can think of fancier ways of making the training data later.

This was completed with #36


Bump to Electron 1.7.12

It turns out Electron 1.7 is based on Node 7.9.0 [1] I moved the engines /
devEngines limits for node and npm down to the associated versions. The theory
is we should lift them when we adopt Electron 1.8, which is in beta now and
based on Node 8.2.1 [2]
[1] https://github.com/electron/electron/releases/tag/v1.7.0
[2] https://github.com/electron/electron/releases/tag/v1.8.1

This version is stable now, correct?

"Electron versions < 2.0 did not conform to the semver spec. Major versions corresponded to end-user API changes. Minor versions corresponded to Chromium major releases. Patch versions corresponded to new features and bug fixes."
https://github.com/electron/electron/blob/master/docs/tutorial/electron-versioning.md#version-1x
1.8 is in beta, and there's another security bugfix release, 1.7.12 that I just pushed.

Going to close this in favor of a pending Electron 1.8 PR.


What is the function of LS/RS TOGGLE ？？

What is the function of LS/RS TOGGLE ？？Can I customize it to other buttons？

Please read the documentation.
The LR/RS toggle is meant to toggle between dpad, left stick, and right stick. With dpad being the default.
If you are referring to a toggle on a specific board, speak with the vendor. Please do not use GitHub for asking general questions. Please use the OpenStick Discord #support channel. The maintainers and other community members can provide help and answer your questions there.


Correcting a copy and paste forgotten word

It is "footer" instead of "header"

seems like a good enhancement to me, but you have to fix the tests before maintainer can consider on merging it :)

I did something wrong, only the first commit should be in this pull request...

I'm closing it...


Exclude temporary layers from permalink

The permalink module currently registers for changes to all layers in the OL layer list and incorporates the state of all layers in it's link URL. As described in #240 we should mostly ignore non application wide layers, particularly those added on a module level since those won't work unless the state of the module is restored too.
A possible solution could look like this:

The layer factory will add a custom attribute 'supportsPermalink' to the OL layer list and default this flag to true (maybe with an option turn it off via config).
Permalink controller evaluates this flag to enable/disable layers for inclusion.
Static ignore list in permalink controller can be removed

By default we will then have permalink support for application wide layers but not dynamical layers added by application code. However the latter can still decide, whether it makes sense to flag its own layers as usable for permalink and set the attribute 'supportsPermalink' on layer creation.

I just implemented this. I'm out of time for today but will provide the PR tomorrow.


use_single_id_space in imposm mapping

Resolves #281
Only possible thanks to the research of @ImreSamu in #281.
*This is how I understand it, please correct me @ImreSamu *
use_single_id_space=true will divides the id range up into three ranges.
id < - 1e17: Ways
0 < id > - 1e17 : Relations
id > 0: Points
What I can do now is to map the relations back into the negative range (by adding 1e17).
And ways back to the positive range (by making them absolute). And then the functions we created previously (osm_id_linestring, osm_id_polygon, osm_id_point, osm_id_geometry handle the rest because they make the decision based on geometry type and whether it originated from a relation.

just 1 quick comment:

your graph is correct,

but here  need reverse  ways <-> Relations :
id < - 1e17: Ways
0 < id > - 1e17: Relations

imho - the correct :
id < - 1e17: Relations
0 < id > - 1e17: Ways

see my examples - from the test data #281
realtions
 -100000000000000003 | archipelago       | r3-place-archipelago-UPDATED!!!!!
 -100000000000000002 | island            | r2-place-island
 -100000000000000001 | residential       | r1-landuse-residential

ways
                  -3 | aboriginal_lands  | w3-boundary-aboriginal_lands-inner
                  -2 | islet             | w2-place-islet-inner

nodes
                   1 | neighbourhood     | n1-place-neighbourhood
                   2 | hamlet            | n2-place-hamlet
                   3 | isolated_dwelling | n3-place-isolated_dwelling

imho - the correct :

Ups switched ways and relations in the written example.
Thanks for the review and detailed example.
So what the code now does is for relation it takes the relation and get's back the real OSM id (but still negated if it is a relation.

Relation
 -10000000000000003 + 1e17 = -3
If it is a polygon for example the osm_id_polygon function will now do
(abs(-3) * 10) + 4 = 34
If it would not have been negative it means it is a polygon was not made out of a relation
and the osm id looks like this.
(3 * 10) + 2 = 32

as usual ..  it is a matter of taste ..
but

with the #284  patch there will be a problem, because we will lost the geometry information ( osm_id_geometry() )   [ this is polygon or not ? ]
so there will be a problem with the proposed  2 step conversion , without redesign.

my alternative solutions:

-- specification : https://www.mapbox.com/vector-tiles/mapbox-streets-v7/
-- osm_ids :  imposm3 single space id
CREATE OR REPLACE FUNCTION osm_ids2mbid (osm_ids BIGINT, is_polygon bool ) RETURNS BIGINT AS $$
BEGIN
 RETURN CASE
   WHEN                      (osm_ids >=    0  )                    THEN (       osm_ids          * 10)       -- +0 point
   WHEN (NOT is_polygon) AND (osm_ids >= -1e17 ) AND (osm_ids < 0 ) THEN ( (abs( osm_ids)       ) * 10) + 1   -- +1 way linestring
   WHEN (    is_polygon) AND (osm_ids >= -1e17 ) AND (osm_ids < 0 ) THEN ( (abs( osm_ids)       ) * 10) + 2   -- +2 way poly
   WHEN (NOT is_polygon) AND (osm_ids <  -1e17 )                    THEN ( (abs( osm_ids) -1e17 ) * 10) + 3   -- +3 relations linestring
   WHEN (    is_polygon) AND (osm_ids <  -1e17 )                    THEN ( (abs( osm_ids) -1e17 ) * 10) + 4   -- +3 relations poly
   ELSE 0
 END;
END;
$$ LANGUAGE plpgsql IMMUTABLE;

CREATE OR REPLACE FUNCTION is_polygon( geom geometry) RETURNS bool AS $$
BEGIN RETURN CASE
        WHEN ST_GeometryType(geom) IN ('ST_Polygon', 'ST_MultiPolygon') THEN true
        ELSE false
      END;
END;
$$ LANGUAGE plpgsql IMMUTABLE;

select osm_id
      ,osm_ids2mbid ( osm_id,   is_polygon( geometry ) )  as from_real_geom
      ,osm_ids2mbid ( osm_id,   false                  )  as from_fake_geom_false
      ,osm_ids2mbid ( osm_id,   true                   )  as from_fake_geom_true
from osm_place_geometry ;

       osm_id        | from_real_geom | from_fake_geom_false | from_fake_geom_true
---------------------+----------------+----------------------+---------------------
 -100000000000000003 |             34 |                   33 |                  34
 -100000000000000002 |             24 |                   23 |                  24
 -100000000000000001 |             14 |                   13 |                  14
                   1 |             10 |                   10 |                  10
                  -3 |             32 |                   31 |                  32
                  -2 |             22 |                   21 |                  22
                   2 |             20 |                   20 |                  20
                   3 |             30 |                   30 |                  30
(8 rows)

and carefully - we can use the  is_polygon parameter for tables - without checking real geometry.
now
 SELECT osm_id_geometry(osm_id, geometry) as osm_id
             , geometry
              , barrier_line_class(type) AS class
          FROM barrier_line_z14

But if we knows that barrier_line_z14  is not contains polygons,
then we can use the 'false' constant - to the 'is_polygon' information.
[  and  we can add a Check Constraints for safer implementation ]
so the optimal will be:
 SELECT osm_ids2mbid ( osm_id,   false  )  as osm_id
             , geometry
              , barrier_line_class(type) AS class
          FROM barrier_line_z14

This is not perfect yet ,   but  maybe you can reuse some ideas ..

whatever you choose  please double check the  id: place_label  - osm_id conversion,

because everything will be a node. (  after this change:  #284  )

https://github.com/osm2vectortiles/osm2vectortiles/blob/436c1b028276a7fc5edff2519be871bcd6108582/osm2vectortiles.tm2source/data.yml#L645

my alternative solutions:

That's my dream scenario - having a osm_ids2mbid function.
Can you push the osm_ids2mbid function to this branch?
I gave you contributor access on osm2vectortiles as we really appreciate your input and work.

with the #284 patch there will be a problem, because we will lost the geometry information (osm_id_geometry() ) [ this is polygon or not ? ]

Yes what happens there is that the Mapbox osm_id will be wrong for place points from polygons.
Was already thinking about creating another table in the mapping so we can keep the information
but with the osm_ids2mbid the problem can be solved easily because there are only points and polygons in the table we can call osm_ids2mbid(osm_id, true) and it will choose the correct one.

added the functions : https://github.com/osm2vectortiles/osm2vectortiles/pull/290

We gave you contributor access on osm2vectortiles as we really appreciate your input and work.

Thank you! :)

With osm_ids2mbid it has gotten much easier.
Transformed the tm2source project.

Where we used osm_id_point we now use osm_ids2mbid(geom, true) since we only make points out of polygons
Where we used osm_id_linestring we now use osm_ids2mbid(geom, false)
Where we used osm_id_polygon we now use osm_ids2mbid(geom, true)
Where we used osm_id_geometry and the possible geometries where only point and polygons we now use osm_ids2mbid(geom, true)
Where we used osm_id_geometry and the possible geometries where ways and polygons (road, barrier_line) we now use osm_ids2mbid(geom, is_polygon(geom))


Upgrade dependencies

The lodash update is a biggie. We need to walk through that one. Some more discussion here: https://github.com/balderdashy/waterline/pull/837

#837 is more of a broad refactor aimed at migrating some bare-metal looping craziness into lodash. This PR just upgrades some stuff

So someone can say confidently that the lodash and should major version upgrades are safe?
https://github.com/lodash/lodash/wiki/Changelog#v300
https://github.com/shouldjs/should.js/wiki/Breaking-changes#changes-for-5x

The lodash 3.0 major version was a big one. If the tests pass then it should be good but needs some QA. No idea about the should upgrade.

Any updates on this?

Manually merged for the lodash dependency. Thanks @listepo and sorry this took so long!

Dependencies are now green, good stuff!


No entries made in db.topology for server address: '1666', dest address: '' and serverID: ''.

System: DSM 7.2.1-69057 Update 5
Release: HelixCoreServer-24.1-0041-x86_64-7.2.spk
I installed the perforce server on /volume3 and P4ROOT on /volume1. I had some problems with the first installation, but I eventually solved them, logged in successfully in p4v on Windows, and uploaded some files.
Then I realised that using the p4d command was always accompanied by the error: Perforce password (P4PASSWD) invalid or unset., and the error persisted even after logging in.
After analysing the problem I found out that it was caused by not having write access to P4TICKETS, but I didn't know how to fix it, so I deleted the perforce server as you mentioned in #1 and reinstalled it:

XXX@XXX:~$ export P4PASSWD=XXX
XXX@XXX:~$ cd /volume1/p4
XXX@XXX:/volume1/p4$ sudo -u Perforce p4dctl-ng new
Password: XXX
✔ Perforce Service name: jasonmap4
✔ Perforce Server root (P4ROOT): /volume1/p4/jasonmap4
✔ Perforce Server unicode-mode: Yes
✔ Perforce Server case-sensitive (Not recommended for compatibility with Windows clients): No
✔ Perforce Server address (P4PORT): 1234
✔ Perforce super-user login: jasonma
✔ Perforce super-user password: XXX
✔ Initialize the server with the recommended settings: Yes
✔ Start the server after the configuration: Yes
✔ Service config path (where to save the .conf file): /var/packages/HelixCoreServer/etc/p4dctl-ng.conf.d/jasonmap4.conf
Configuring p4d service 'jasonmap4' with the information you specified...
Service conf file saved as /var/packages/HelixCoreServer/etc/p4dctl-ng.conf.d/jasonmap4.conf
Enabling unload and spec depots
Populating the typemap
Initializing protections table...
Error when initializing the server: Perforce password (P4PASSWD) invalid or unset.

You can see that even though I set the password in advance using export P4PASSWD=XXX, I still get Perforce password (P4PASSWD) invalid or unset.
At this point, even though the database has been successfully created at  /volume1/p4/jasonmap4, attempting to start the service will result in the error:

XXX@XXX:/volume1/p4$ p4d
Perforce db files in '.' will be created if missing...
Perforce Server starting...
Perforce server warning:
        Pid 26185
        Operation: topologyRegistration
        No entries made in db.topology for server address: '1666', dest address: '' and serverID: ''.
        ServerID for the server should be set and a server restart is required.

Additional information is as follows:

XXX@XXX:/volume1/p4$ p4 info
User name: XXX
Client name: jasonmap4
Client host: jasonmap4
Client unknown.
Current directory: /volume1/p4
Peer address: <IP_ADDRESS>:60796
Client address: <IP_ADDRESS>
Server address: localhost:2333
Server root: /volume1/p4/jasonmap4/root
Server date: 2024/08/29 22:17:14 +0800 CST
Server uptime: 00:00:55
Server version: P4D/LINUX26X86_64/2024.1/2625008 (2024/07/15)
ServerID: jasonmap4
Server services: standard
Server license: none
Case Handling: insensitive

XXX@XXX:/volume1/p4$ sudo cat /var/packages/HelixCoreServer/etc/p4dctl-ng.conf.d/jasonmap4.conf
Password: XXX
{
  "Name": "jasonmap4",
  "ServerType": "p4d",
  "Owner": null,
  "Execute": "/volume3/@appstore/HelixCoreServer/usr/local/bin/p4d",
  "Enabled": true,
  "Environment": {
    "P4ROOT": "/volume1/p4/jasonmap4/root",
    "P4PORT": "1234",
    "P4SSLDIR": "/volume1/p4/jasonmap4/root/ssl"
  }

The problem is still reproducible after deleting and installing again, am I doing something wrong?

I also noticed something strange, some of the files in /volume1/p4/jasonmap4/root appear in /volume1/p4, which doesn't seem right, since I didn't have this problem when I first installed to /volume1/Perforce/jasonmap4

Hi! I found that the service is actually running successfully.

No entries made in db.topology for server address: '1666', dest address: '' and serverID: ''. It's just because I'm calling p4d incorrectly.
Error when initializing the server: Perforce password (P4PASSWD) invalid or unset. This is probably due to special characters in the password, and will cause the password to be changed when logging in from p4v, and then get stuck.

After I installed P4ROOT to /volume1/Perforce/XXXX with a password that does not contain special characters, everything works fine!


Automatic unpause / pause fails

Hi,
It seems that the automatic pause / unpause is broken in V13 when the console is opened in the OpenTTD server gui.
In the console it gives the following error:
Command '@@@@_UnpauseCommand_1677323989205_@@@@' not found.
Experienced this:

The game does not autopause when all players are disconnected or spectating
The game does not unpause after a manual savegame was made
When the player connects, it pauses the game but DOES actually unpause it again.
When the console is not open, it works like it should.
The game is however able to be unpaused manually in the console.

Hi,
The behavior of the feature in the new version remains unchanged and is exactly as intended. If the console is opened, all auto features are disabled. In order for these features to work properly, the terminal must be set to English (the server should automatically set the terminal language to English).

Server check if the terminal is open. If open all auto actions are skipped.
Server checks if a player action was loggend in the terminal like:

has started a new company
has joined company
has left the game
closed connection
has joined spectators

If these logs occrued the server checks if it must be paused or unpaused.
The server checks every 30 seconds whether the game needs to be paused or unpaused, but only if no terminal is currently open.

Internally, all auto features involve reading and writing to the terminal. If the terminal is left open in the UI, it can become cluttered with unwanted information. For this reason, all auto actions are intentionally skipped when the terminal is open in the UI.
If the auto feature fails to work after the terminal has been closed for more than 3 minutes, this is considered a bug.

Thanks for the quick info. This might be worth mentioning in the README.
I thought it was a bug due to the "Command '@@@@UnpauseCommand_1677323989205@@@@' not found." message in the console.

Closed as not a bug but considered a feature.

Closed as considered not a bug but a feature ;)

The string: Command '@@@@UnpauseCommand_1677323989205@@@@' that u see is used to find the starting point of an issued pause command. The system searches for that and then the next lines to se if the command was executed.
By the way its documented directly in the UI ;)

Ah ok, I see. I'm not that familiar with the OpenTTD console (in fact I was not until today).
Thanks for pointing out. I'm an official idiot:P


Task 158 update to pit 1.6.8

Closes #158

@echebbi shall I merge?

Sure, please proceed. Thanks for the quick update!
Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg

From: Lorenzo Bettini @.>
Sent: Tuesday, July 27, 2021 10:54:59 AM
To: pitest/pitclipse @.>
Cc: Emmanuel Chebbi @.>; Mention @.>
Subject: Re: [pitest/pitclipse] Task 158 update to pit 1.6.8 (#159)
@echebbihttps://github.com/echebbi shall I merge?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pitest/pitclipse/pull/159#issuecomment-887335484, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGFZWIPIFA4O3YTPGCL44U3TZZX6HANCNFSM5BBYKHDA.

@JKutscha now you can access PIT keyset for mutators :)


USing this as a desktop background...

what would it take to use this as a desktop background? i know it would be horrible on a laptop but i would love it on my macpro!

Wallsaver offers this option and it works on all screen savers.
http://wallsaver.en.softonic.com/mac

Or better, just open Terminal, and type the following:
/System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background

#37

@JimmyPco, this application that I wrote uses a launch agent.
https://github.com/MichaelDimmitt/Aerial_Desktop
It never opens more than one instance of Aerial. It loads from sleep or from startup. It automatically selects Aerial as the screensaver but that can be changed rather easily. It is meant to be incredibly simple click to install/enable click to uninstall/disable.
Want to switch to a new video after its already running? click uninstall and install and your desktop background will be different.
Meant to be super user friendly for my friends who are not programmers.
Does exactly what you are looking for and if you do not want it on all the time you can click uninstall and install it whenever you want. My laptop MacBook Pro (13-inch, Mid 2012) can run for 6 hours without needing a charge. So it does not consume a lot of resources. Chrome usually more expensive. Regards, Michael Dimmitt.

@glouel Close this


Transition exception should show failed validation

I have a state machine like:
class AbsenceValidator < ActiveModel::EachValidator
  def validate_each(record, attribute, value)
    unless value.nil?
      record.errors[attribute] << (options[:message] || "must be nil")
    end
  end
end

class SurveyTaking < ActiveRecord::Base
  belongs_to :pending_question

  state_machine :state do
    state :started {validates :pending_question, :presence => true}
    state :completed {validates :pending_question, :absence => true}

    event :complete do
      transition :started => :completed
    end
  end
end

st = SurveyTaking.new
st.pending_question_id = nil
st.valid? #=> false
st.errors #=> {:pending_question=>["must be nil"]}
st.complete! #=> StateMachine::InvalidTransition: Cannot transition state via :complete from :started

ActiveRecord (without state_machine) will actually give you the validation in the exception, which is quite helpful:
me = User.find(1)
me.gender = 'neither'
me.valid? #=> false
me.save! #=> ActiveRecord::RecordInvalid: Validation failed: Gender is not included in the list

I think this was at the root of my #121 issue.

Hey @jaylevitt -
I had actually made this change as a fix for #138.  I had admittedly forgotten about #121.  Can you validate that this solution (released in 1.1.0) solves the problem you were seeing?
Thanks.

Great, we'll update - thanks!


Hash numbers in the files names don't change every production build I make

When I do a minor change to my react app like changing a link, and make a new production, hash numbers don't change and that will affect the deployment because of the browser cash, but that is with minor changes only. If I make big changes to my app, hash numbers changes

https://create-react-app.dev/docs/production-build/#static-file-caching
I Think it updates other chucks of Js if it is minor change but not main.chunk.hash.js.  It updates based on content changes in subsequent builds. We can find  js and css mappings in asset-manifest.json in build folder


[Feature Request] Add more ITs around tiered caching stats

Is your feature request related to a problem? Please describe
As part of tiered caching we have added a new cache stats API, where individual ICache implementations keep track of their own stats. This approach makes it easier to plug in new cache implementations. We have some ITs around this, but we should add more to make sure there aren't any unknown issues.
Describe the solution you'd like
We should add more ITs combining different cache types with different level aggregations for the stats, across a wider variety of clusters.
Related component
Search:Performance
Describe alternatives you've considered
No response
Additional context
No response

[Triage - attendees 1 2 3 4 5 6 7 8]
@peteralfonsi Thanks for creating this issue, looking forward to a pull request.
In the future when creating issues, could you include the specific tests that are missing so its clearer to know when this issue is resolved?


How do you set com.mixpanel.android.MPConfig.EventsEndpoint at runtime

mixpanel-swift has a function called setServerURL but the android sdk does not provide such a method, is there a way to dynamically set this at runtime?

hi @dl748 , yes, please refer to this doc https://developer.mixpanel.com/docs/self-hosted-tracking in the Android SDK section.

No, those instructions set the variable at COMPILE time, which is completely different.

hi @dl748 , sorry about that. We will consider providing it in the next couple of versions.

hi @dl748 , we just released 5.9.0, now you can use setServerURL to set it in the run time. I'm closing it now, please feel free to reopen it if you find any issues in this API.


Remove mistaken addition

Accidental "test" line for sphinx functionality made it through in a
previous branch. This removes it.
There is no change note due to modifying content for which one already exists in this pending set.

Aaaaand already in the HL interface branch, nvm.


Fix name of 301+-nondb directory to stop at Spark 3.2.0

fixes https://github.com/NVIDIA/spark-rapids/issues/3463
Signed-off-by: Thomas Graves<EMAIL_ADDRESS>

build


Add github workflow

We will be migrating from Travis.

@kokosing, @ssheikin, @losipiuk AC

@kokosing, @ssheikin, @losipiuk AC

GHA report - https://github.com/Praveen2112/docker-images/actions/runs/474219550

GHA report - https://github.com/Praveen2112/docker-images/actions/runs/474219550

GHA report-  https://github.com/Praveen2112/docker-images/actions/runs/476956771

GHA report-  https://github.com/Praveen2112/docker-images/actions/runs/476956771


Remove unneeded chain declaration

Hello - I've been reviewing the Redux source and was trying to figure out what the purpose of assigningchain to an empty array was in applyMiddleware. There doesn't seem to be a scenario where chain is not immediately updated to middlewares.map(middleware => middleware(middlewareAPI)). Please let me know if I'm missing something here and thanks for a great library.

Hmm.  I appreciate the PR, and I'm inclined to agree, but I'm also very hesitant to merge any changes to this file at this point.  We've had numerous PRs over the last few years trying to "tweak" or "fix" things (usually related to the declaration of dispatch in here), and they've almost all been wrong.  The current code is there, it works, and I don't see a particularly pressing need to change it further.
I'll ping @timdorr and @jimbolla just to get their thoughts.

LGTM

OK, at least we're all equally culpable.


Al/set transport

This change brings in a load of dependencies from a different branch. Suggest we close this and push again as a separate branch.


HDDS-10164. Replace GenericTestUtils temp dirs with @TempDir in hadoop-hdds

What changes were proposed in this pull request?
Replace temporary directory functionality of GenericTestUtils with JUnit's @TempDir. The latter is automatically cleaned up.

Usage of File getRandomizedTestDir(), File getTestDir(), and File getTestDir(String) can be directly replaced by @TempDir. If the temp directory is stored in a local variable, convert it to a field for it.
For usages of String getRandomizedTempPath() and String getTempPath(String) we still need to add a Path or File as a field, and use toString() where needed.
Post-test deletion of the dir can be removed.
If @BeforeEach and @AfterEach methods are only used to create/delete the dir, they can be deleted as well.
Any unused imports should be removed.

What is the link to the Apache JIRA
HDDS-10164
CI
https://github.com/wzhallright/ozone/actions/runs/7705620392

@adoroszlai Thanks for your review! I have fixed the comments.PTAL...Thanks.

Thanks @wzhallright for the contribution.


new install: station attributes should be set not-null default false in station table

station attribute water_heater set null in database causes error


Missing package product 'MicrophonePitchDetector' on build

On Xcode Version 15.0.1 (15A507) when I try to build the project, aways crash on error "Missing package product 'MicrophonePitchDetector'"

Can you please share more information on how you’re building and more details about the error?
The latest commit passed all CI jobs including building and testing on iOS, macOS and watchOS.


How to change color of particles ?

How to change color of particles ? default have white color , what if i would like to set this attr on red ?

I added new options. https://github.com/rohanrhu/nodes.js/releases/tag/v1.5


No syntax support (highlight or autocomplete) for action.yml files

Describe the bug
Works for workflow.yml files, but not action.yml files
To Reproduce
Steps to reproduce the behavior:

In the same repository, create a workflow/test.yml and an action/action-name/action.yml
Create any simple workflow
See lack of highlight for action.yml

Expected behavior
Equal support for YAML syntax
Screenshots
In action.yml:

In workflow.yml:

Extension Version
[0.25.5] based on changelog

Manually changing the Language Mode to "GitHub Actions Workflow" will enable the highlight, but autocompletion is still missing.

This is currently not supported, we do not have any immediate plans to add support for action.y(a)ml files.

@cschleiden The extension name is confusing in that case. Please rename the action to vscode-github-workflow instead

The product is called GitHub Actions not GitHub Workflows.
Supporting action.y(a)ml files does seem like a useful feature addition and maybe it can be revisited in the future.

For autocompletion support, add this to your .vscode/settings.json, and you're golden 👌🏽
"yaml.schemas": {
  "https://json.schemastore.org/github-action.json": ".github/actions/*.{yml,yaml}"
},

For autocompletion support, install this YAML extension from RedHat and update .vscode/settings.json with the config below:
"yaml.schemas": {
  "https://json.schemastore.org/github-action.json": ".github/actions/*.{yml,yaml}"
},

I tried this but still not working for autocompletion. Using M1 mac with vscode 1.9


Improve desyncs on different-FPS streams

We already know of severe issues when two streams have different frames per second, stemming from some yet unexplained delay in frame arrival times. That's on a single camera.
Here we have a reproduction of a case where multiple cameras are connected via hardware sync, with one master and one or more slave cameras. The slaves wait for a signal from the master, and frames get delayed. We end up with a similar effect, where the delay causes a different (calculated) FPS leading to eventual desync between the Depth and Color streams.
Two main fixes:

When considering whether to wait for a missing frame, the syncer now takes into account the FPS from all known matchers

Before, only the main matcher was used
This fix helps the desync by itself
It also invalidated one of our other unit-tests - when going over it, I saw some behavior I didn't like so made another change:

When more frames are available for a better sync later, the syncer now releases earlier frames

E.g., an extreme case: Depth FPS of 100 and Color FPS of 10 (this is the diff-fps unit-test)
D@0, D@10, C@0, D@20 ... D@60, D@70, D@80, D@90, D@100, D@110, C@100
This used to sync D@60 and C@100 ... now syncs D@100 and C@100

The latter change is riskier.
Tracked on [TBD]

Sorry, I totally forgot about the failure in the syncer-throughput test in LibCI.
I'll take a look and fix it, but the code-review can continue...

Closing pending other investigations first.


Let unused variable be an error

I think a good extension would be to let unused variables be an error.

Having them as an error would block development when you are using Error Prone as your development compiler, as we do inside Google.  It would make a good warning though, and you could configure your CI to promote it to an error and block submit if you have an unused variable.

How would it block development? Is there a scenario in which unused variables are ever desired?

What is the recommended way to configure our CI? From what I can tell, there isn't a rule in error-prone or the default jdk compiler to detect it, and I want to avoid adding findbugs just for this.

@agrieve It's pretty common to have unused variables while you are coding.  For example, you might comment out the only use of a variable while debugging.  I agree it would be useful in a CI or code review bot though.
@justinuang This isn't a rule in Error Prone, and we don't have plans to make it one.  The only suggestion I can make is to find some other tool that does it.  PMD does it and might be easier to integrate than Findbugs.

We now have support for Unused analysis in ErrorProne (under a bugpattern named Unused). It's disabled by default while we evaluate the performance cost of running it in ErrorProne, but you're welcome to enable it and give it a spin!


ci: add github actions

run mix test
run mix dialyzer

Couldn't find a way to run mix format but just fail the CI if there's a formatting issue. So I just added https://github.com/mhinz/vim-mix-format in my own vim config to automatically do it when I save a file.

Let me actually test this first.

Ok, passes on my fork. A bit slow, but it works.


[multiplayer] Host lobby screen: make entire join code clickable to copy. Show toast on copy.

Fixed in https://github.com/microsoft/pxt/pull/9210


Enforced binary claims for structs too

This has no issue associated but I was investigating if we need any more fixes before 0.16.0 and this came up. Look the above code:
defmodule TestStruct do
  defstruct a: nil, b: nil
end

token = %Joken.Token{}
|> with_json_module(Poison)
|> with_claims(%TestStruct{a: 1, b: 2})

This would produce a Joken.Token with claims: %{a: 1, b: 2} instead of claims: %{"a" => 1, "b" => 2}. Since we opted to go all binary, this PR ensure that using with_claims will produce binary keys for claims.
Also, again, in the same commit, I changed the default with_exp, with_iat, with_nbf to use generators instead of fixed values. I know this should have gone in a separate PR but one thing led to the other...
As I said I am investigating if we need any more patches to make everything align for 0.16.0. Expect more PRs like this \o/

:+1:


Asp.net with Angular dev tunnel returns 404

A project created in a template asp.net with angular.
Dev tunnel creates only one port. When the SPA project is ready it is redirected to the new port. Normally here the angular app would show up. However after redirected, it returns 404 error 'page can't be found'.
When I check dev tunnel, there is only one port, which is the initial while SPA is not ready yet.

Sure, I'm here to help while using ngrok))
Here is the normal behavior without dev tunnel:

On F5 the local host starts on port 7245:

Once SPA proxy is ready, it automatically redirected to port 44476. And the app works from this new port as usual:

Now will do the same with dev tunnel.

First port 7245 gets launched:

Once the SPA proxy is ready, it gets redirected to port 44476:

We can see that there is only one channel was created for port 7245. And this is the problem.

Time of launch is 12:53 PM Turkey time zone, 13 November. Not sure how to retrieve the timestamp.
Dev Tunnels during test:
https://localhost:7245  ->  https://zhhxnj80-7245.euw.devtunnels.ms/
https://localhost:7245  ->  https://8rflcxbs-7245.euw.devtunnels.ms/
https://localhost:7245  ->  https://vf30p0jx-7245.euw.devtunnels.ms/
Let me know if any more is required

Thanks for the details.
Port 44476 can be added via the "Dev Tunnels" pane in VS.
This would allow that port to also be made available on the tunnel.

Sure, could you please send some screenshots on how to add the port to the tunnel?
I could not find how to do it. Therefore created this issue.

In the Tools Window, there should be a "+" button. I believe that should allow you to add a port.
https://learn.microsoft.com/en-us/aspnet/core/test/dev-tunnels?view=aspnetcore-8.0#dev-tunnels-tool-window

Derek,
Thanks for the answer. The '+' button adds a new dev tunnel, not a port.
Currently I don't see the way to add a new port to existing tunnel, nor assign a specific port to a new dev tunnel.

Another option is to use the devtunnel CLI to host both ports simultaneously.
Documentation on hosting is available at https://learn.microsoft.com/en-us/azure/developer/dev-tunnels/cli-commands#host-a-dev-tunnel


dark mode - style group nodes

any help on how to style the group tags in dark mode ?

Have a play around with the CSS file, and make your own customisation: https://github.com/shentao/vue-multiselect/blob/master/dist/vue-multiselect.css
The CSS needs to be inserted separately into your app, so instead of referencing the CSS that is part of the library, you can reference your own file
Alternatively, feel free to start a discussion about it


Improve location of end proof symbol

Look at Section Tag 00DY at the placement of the end proof symbol of first lemma. This also happens on the current website. I am not sure how worth fixing this is because I am against adding more vertical space in general. (I can easily fix this in the latex for example.)

Commit 2fa166e is an example for how we could fix this, at least in the case of list items. I don't see an easy general way to fix all these issues. Personally, I think it's just good mathematical/LaTeX-ical style not to end proofs in lists, equations, etc. But I guess I am rather particular about my LaTeX...

Yeah, I think you are right this should just not happen. For this lemma somebody else wrote the proof if this lemma a looooooooong time ago so it isn't even my fault!


Adding DB support to the whole app

Adding db support and the appropriate schema and the api endpoint.
Currently read only.

LGTM!
I'll review it and tweak it if necessary.

A few comments here, can you explain why you re-added the example-config.json file? We've moved to SQLite so I don't think we have a use for JSON files.
Also I see you installed compression and sirv but haven't used them, is there something you're planning to do with them or are they leftovers?
The other changes look good to me, again I have to test them but I am currently travelling.
-Safeboot

Oh no
Just forgot to remove them
Also the two lib is the code from yours

I can still help you with the code but might need a little more effort to do.
I moved to turso and it's the exact same code except the way the query works
So mine is
app.use('/api/settings', async (req, res) => {
  const stmt = await db.execute('SELECT * FROM settings');
  let data = []
  for(let each of stmt["rows"]) {
    data.push({"name":  each[0], "value": each[1]})
  }
  res.json(data);
});

Don't worry
I will still be able to contribute but due to needing to rewrite every piece of the api handler before push might be a bit of work but ok.

Also another update
Motion won't work with SSR
https://github.com/vueuse/motion/issues/58

Do I push my changes
cause I have fixes for the animation and turso lib support all local sqlite and libsql servers

Closing as the database implementation has been completed. Please take a look and test it yourself. Obviously we will need changes but this is a good starting point.


AzureAOAIに対応

review this please

review this please

review this please

review this please

review this please

review this please

review this please

review this please

test this please

review this please

review this please

reivew this please

review this please

review this please


featherpad: init at 0.9.1

Motivation for this change
I like to use featherpad @ nixos ;-)
Things done

[ ] 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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build featherpad

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: featherpad
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: featherpad
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/sjangg7akmizl7w7f5908w8w0yna779l-featherpad-0.9.1
shrinking /nix/store/sjangg7akmizl7w7f5908w8w0yna779l-featherpad-0.9.1/bin/featherpad
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/sjangg7akmizl7w7f5908w8w0yna779l-featherpad-0.9.1/bin
patching script interpreter paths in /nix/store/sjangg7akmizl7w7f5908w8w0yna779l-featherpad-0.9.1
checking for references to /build in /nix/store/sjangg7akmizl7w7f5908w8w0yna779l-featherpad-0.9.1...
postPatchMkspecs
postPatchMkspecs
postPatchMkspecs
/nix/store/sjangg7akmizl7w7f5908w8w0yna779l-featherpad-0.9.1

Success on aarch64-linux (full log)
Attempted: featherpad
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/fw2cfzf8h4mlc1qwbxzc4mxynw3igv5r-featherpad-0.9.1
shrinking /nix/store/fw2cfzf8h4mlc1qwbxzc4mxynw3igv5r-featherpad-0.9.1/bin/featherpad
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/fw2cfzf8h4mlc1qwbxzc4mxynw3igv5r-featherpad-0.9.1/bin
patching script interpreter paths in /nix/store/fw2cfzf8h4mlc1qwbxzc4mxynw3igv5r-featherpad-0.9.1
checking for references to /build in /nix/store/fw2cfzf8h4mlc1qwbxzc4mxynw3igv5r-featherpad-0.9.1...
postPatchMkspecs
postPatchMkspecs
postPatchMkspecs
/nix/store/fw2cfzf8h4mlc1qwbxzc4mxynw3igv5r-featherpad-0.9.1


Issue 116

This pull request has a lot of conflicts and, I believe, many of them are due a not so good practice.
@albertohata kept working on this branch although it was merged here. Therefore, the commits b5f2cd and 868e20 are one that matters and the others are just duplicated ( as they were already merged).
I advise to create a new branch from the master and them, apply the two last commits.

What's the decision on this one?

What's the decision on this one?

We can close this pull request. Made some commits by mistake in this branch, but we can ignore them.


Update home to 0.4

r? @nrc
(rust_highfive has picked a reviewer for you, use r? to override)

Can this include the patch version (0.4.2)?  A previous PR noted that 0.4.1 has an issue (https://github.com/rust-lang/cargo/pull/7225#issuecomment-519399960).

Oh, sure !

@bors r+

:pushpin: Commit dd20d69e4928e3d66aba7afc83f9d1a68e7bf502 has been approved by ehuss

:hourglass: Testing commit dd20d69e4928e3d66aba7afc83f9d1a68e7bf502 with merge 60b7bf0045cdd616324ce24e2079751b73983ec0...

:sunny: Test successful - checks-azure
Approved by: ehuss
Pushing 60b7bf0045cdd616324ce24e2079751b73983ec0 to master...


Test for <IP_ADDRESS> fails in Appveyor

https://ci.appveyor.com/project/jpboyce/cb-cis-windows-2016/builds/24740386#L1142

Resolved by 9cc4dbe


Separate the userstore operations in to different layers.

Currently no there is no DAO layer seperation, instead all the DAO methods have been added to the service layer itself. When achieving the requirement of allowing userstores to be persisted in different repositories as database, file etc. the seperation is needed.

https://github.com/wso2/carbon-identity-framework/pull/2243

Please add the content to docs: https://docs.google.com/document/d/1ITziujnC_DupPq9D_aLugXqqknc3fReLTpky52IssyQ/edit

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Add LessRealThanReal

Fixes #7660, which was submitted by the mod author.
ckan compat add 1.7

#rebuild


Restart HA when TV powered off...

Restart HA when TV powered off generate a lot of errors socket.timeout: timed out in log:

Is any way to suppress this errors?

set app_list in your config as described in the readme

i think i have a solution for the issue, but it won't be available until next release, setting the app_list manually should make it go away though.

Thx, it works. But the automatic list of applications is much more convenient =)

The new version should handle getting the app_list a bit better, but I still recommend setting it manually for best performance.


Use entity_instances table for entity information

With all the necessary information within the entity_instances table, we can now dispose of the per-entity tables and rely solely on the central one.

We're effectively using the central entity tables. We just haven't deprecated them yet. That will be done in a separate work stream. So I closed this.


Multilingual support

Translate all the interface in English.

Can you make some kind of strings file?
I could translate it to german.

Yes, no problem! I will do that shortly. This is a very good initiative ;-)

Here is a first "draft" of all french strings present in the application. Hope this will help you translate the interface in german. I will work on this issue as soon as possible.
translation-draft.txt

This issue will be closed soon: I will open a new issue for the German language support. Thanks for your future contribution.


chore: notification toggle missing when import from backup

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
Fixes #677
Type of change
Please delete any options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[ ] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

@louislam: Can you deploy this as 1.22.1?
This bug was reported on Oct 12, 2021


Sync download/uploadExcludeFile parsing

When using either download or uploadExcludeFile under dev.sync[*] with following .gitignore style entries
!/some/path/in/my/repo/

Devspace is complaining that !/some/path/in/my/repo/ should be used instead of !some/path/in/my/repo.
But as you can see exactly that is used and when I use excludePaths instead of file the warnings disappear.
OS: Mac Catalina
Devspace: 5.18.4
K8s: 1.20

@kickthemooon thanks for creating this issue! Did you maybe use it like this:
- !/some/path/in/my/repo

Since ! is a special character in yaml, you need to use instead:
- "!/some/path/in/my/repo"

@kickthemooon thanks for creating this issue! Did you maybe use it like this:
- !/some/path/in/my/repo

Since ! is a special character in yaml, you need to use instead:
- "!/some/path/in/my/repo"

The issue is about excludeFile i. e. When using an external file with a list of gitignore style items.
The issue is not about the config yaml file. In the config yaml file using excludePaths and quotes around the items seema to work fine

@kickthemooon ah yeah sorry, my bad. Yes you are correct, seems like the function we use internally cuts those leading / from the exclude paths. We'll issue a fix for this shortly

@kickthemooon this should be fixed with the new v6 beta version, can you confirm this?


Connect keycloak behind reverse proxy fix

I have a fix for using connect-keycloak behind a reverse proxy. To make it work you have to enable 'trust proxy' in your node app (so express will process the X-Forwarder-For headers) and keycloak will build the correct redirect url.
This is the nginx configuration I'm using and it works with my node app, deployed behind nginx+ssl .
location /{
                proxy_set_header Host               $host;
                proxy_set_header X-Real-IP          $remote_addr;
                proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto  $scheme;
                proxy_set_header X-Forwarded-Port   443;
                proxy_pass http://<IP_ADDRESS>:3000;
        }

P.S.
It is very hard to install the modules from a github repo because you use sub-directories and npm can't handle taht [1] . If you made modifications to the modules and you wish to use them in the your deployed applications you will need npm registry or separate individual repos.
Right now I'm using a copy of 'connect-keycloak ' in a separate github repo which is not desirable.
[1] https://github.com/npm/npm/issues/2974

I need to lobby the keycloak guys for more repos. I understand the problem.
--
Sent from my iPhone

On May 25, 2015, at 4:28 PM, Ioan Eugen Stan<EMAIL_ADDRESS>wrote:
I have a fix for using connect-keycloak behind a reverse proxy. To make it work you have to enable 'trust proxy' in your node app (so express will process the X-Forwarder-For headers) and keycloak will build the correct redirect url.
This is the nginx configuration I'm using and it works with my node app, deployed behind nginx+ssl .
location /{
proxy_set_header Host               $host;
proxy_set_header X-Real-IP          $remote_addr;
proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-Port   443;
proxy_pass http://<IP_ADDRESS>:3000;
}
P.S.
It is very hard to install the modules from a github repo because you use sub-directories and npm can't handle taht [1] . If you made modifications to the modules and you wish to use them in the your deployed applications you will need npm registry or separate individual repos.
Right now I'm using a copy of 'connect-keycloak ' in a separate github repo which is not desirable.
[1] npm/npm#2974
You can view, comment on, or merge this pull request online at:
https://github.com/keycloak/keycloak-nodejs/pull/6
Commit Summary
Fix for keycloak behind proxy
Fixed logout to work behind reverse proxy
File Changes
M connect/middleware/logout.js (13)
M connect/middleware/protect.js (19)
A connect/proxy-utils.js (11)
Patch Links:
https://github.com/keycloak/keycloak-nodejs/pull/6.patch
https://github.com/keycloak/keycloak-nodejs/pull/6.diff
—
Reply to this email directly or view it on GitHub.

Thanks. I hope the repos will be splited.

+1 Here, the connect module is unusable as is, a PR that fixed it was apparently merged yesterday but no-one republished to NPM, and I can't put it in my package.json because it is not a valid path.
I'll need to fork it, put everything in the root folder, and then use my git repo as the source, but then I won't be able to merge upstream changes. How does this need lobbying as public repositories are free and unlimited?

Because I'm not the admin of the Keycloak organization.
--
Sent from my iPhone

On Sep 24, 2015, at 6:23 PM, Tristan F<EMAIL_ADDRESS>wrote:
+1 Here, the connect module is unusable as is, a PR that fixed it was apparently merged yesterday but no-one republished to NPM, and I can't put it in my package.json because it is not a valid path.
I'll need to fork it, put everything in the root folder, and then use my git repo as the source, but then I won't be able to merge upstream changes. How does this need lobbying as public repositories are free and unlimited?
—
Reply to this email directly or view it on GitHub.

@stianst do you think we can split these folders into repositories to make it more Node-ish? //cc @bobmcwhirter

Yes, a split would be very much more Node-friendly.
Also, having just gone through this with WildFly Swarm, git subtree is a useful command, if you want to split sub-dirs into their own repos retaining just the portion of history for each that applies to each.
StackOverflow has the instructions, but it's not horribly difficult with a modern git (if you have git-subtree).

regarding the actual PR about reverse-proxying, it sounds like a great idea, but I have no clue about this codebase any more regarding applicability of this change.


PBKDF-OpenSSL SecretKeyFactory not available since 1.53 release.

Hey all, I'm reposting an issue that appears since 1.53 releases: https://github.com/box/box-java-sdk/issues/168, and here http://bouncy-castle.1462172.n4.nabble.com/Issues-when-migrating-to-1-53-td4657955.html.
I wonder if there's any plan to resolve it so that people like me don't need to resort to 1.52 for development. Thanks a lot.

Are you able to provide an example where it's happening with either 1.54 or 1.55? The secret key factory is definitely there.

Thanks for the update. Here's the snippet.
JcaPEMKeyConverter converter = new JcaPEMKeyConverter().setProvider("BC");
PEMDecryptorProvider decryptionProvider = new JcePEMDecryptorProviderBuilder().build("key".toCharArray());
PEMKeyPair decryptedKeyPair = ((PEMEncryptedKeyPair) object).decryptKeyPair(decryptionProvider);

stacktrace?

Caused by: org.bouncycastle.openssl.PEMException: Unable to create OpenSSL PBDKF: PBKDF-OpenSSL SecretKeyFactory not available
at org.bouncycastle.openssl.jcajce.PEMUtilities.getKey(Unknown Source)
at org.bouncycastle.openssl.jcajce.PEMUtilities.crypt(Unknown Source)
at org.bouncycastle.openssl.jcajce.JcePEMDecryptorProviderBuilder$1$1.decrypt(Unknown Source)
at org.bouncycastle.openssl.PEMEncryptedKeyPair.decryptKeyPair(Unknown Source)
at xxxxxxxxxxxxxx.(xxxxxx.java:44)
... 28 more
Caused by: java.security.NoSuchAlgorithmException: PBKDF-OpenSSL SecretKeyFactory not available
at javax.crypto.SecretKeyFactory.(SecretKeyFactory.java:122)
at javax.crypto.SecretKeyFactory.getInstance(SecretKeyFactory.java:160)
at org.bouncycastle.jcajce.util.DefaultJcaJceHelper.createSecretKeyFactory(Unknown Source)
... 33 more

Yep, it's not using the BC provider - you have to configure it to use BC. The DefaultJcaJceHelper does exactly what it says, it uses the default provider mechanism. You will not see this stack trace if you have called setProvider("BC");

@bcgit Thanks for the heads up. However as you can see from my code snippet above, I did call  setProvider("BC") and I was getting those struck trace with it.

The stack trace shows: org.bouncycastle.jcajce.util.DefaultJcaJceHelper.createSecretKeyFactory() You might have called setProvider("BC") but someone else hasn't.

I have added Security.addProvider(new BouncyCastleProvider()); before above code and working fine for me.


[Common] Only the last 20 comments are displayed (The page pagination is not work).

Environment: Windows 10 Pro (64-bit), Google Chrome 81.0.4044.138 (64-bit)
Reproducible: Always
Build: commit 0140903
Spets to reproduce:

Go to DataBase and use  this file (https://drive.google.com/file/d/1FonV39b4yk9WSfuCOtqKRuR3J74cupbu/view?usp=sharing) to insert comments to the news.
Go to https://ita-social-projects.github.io/GreenCityClient/#/welcome ( login<EMAIL_ADDRESS>password: Qw@rt111 )
Found the news with title 'Very simple test like previous. verify contentType filed with more than 20 characters' or go throuhg the link https://ita-social-projects.github.io/GreenCityClient/#/news/1660
Go to the comment block.

Actual result:
The pagination shoud be with 4 number of pages.
Expected result:
The pagination with only 2 number of pages.

User Story #767

Only the last 20 comments are displayed (10 per page), although a total of 50 comments have been written:

Please, check one more time. Not relevant


Lint update

R: @jeffposnick @addyosmani
This was the worked required to bump the linting of eslint-config-google.

Is it eslint:recommended or the update to google that mandates the () around arrow function parameters? I've never been a fan of that.
If it's made it into the official google rules, then I'll relent. Otherwise, if it's part of eslint:recommended, I'd argue that we should ignore that rule.

@jeffposnick Looks like it comes from Google but I @philipwalton may be able to confirm.

Google style doesn't strictly require it for single-argument arrow functions, but it does recommend it in all cases to avoid ambiguity. Since the ESLint rule is only granular enough to either always require it or always omit it, I thought it was best to always require it.
Here's the text from the style guide (unfortunately it's still not public or I'd just link to it):

Tip: It is a good practice to use parentheses even for single-argument arrows, since the code may still parse reasonably (but incorrectly) if the parentheses are forgotten when an additional argument is added.

Do the options as-needed and requireForBlockBody help tune it?

Do the options as-needed and requireForBlockBody help tune it?

as-needed enforces not using parens in certain cases. Since the Google style guide recommends using them in all cases, I wouldn't want to add a rules that would prevent someone from following that advice.

I suppose technically you could argue the rule could be turned off, which would allow folks to use whatever style they want, but it would come at the cost on consistency within a project.
@jeffposnick and @ithinkihaveacat if either of you feel strongly about this, it probably makes sense to move further discussion to the main repo issues: https://github.com/google/eslint-config-google

I've made peace with this PR given that the restriction is coming from the latest google ruleset. 👍


Unprotect / disable protection for one or more volumes

Problem
Some dynamically / imperatively defined applications, e.g., Cloud Pak for Data, need to exclude volumes from disaster recovery dynamically.
Impact
The impact of recovering volumes that should not be is application dependent.  For Cloud Pak for Data, recovery fails as described in #1101.
Solution
Scope
Sync and Async VolumeReplication volumes are addressed by this issue.  Unprotecting VolSync volumes is tracked by #879.
Requirements

VRG's ReplicationState must be primary to unprotect its PVCs
Unprotected PVCs like they are when deleted with #828:
Remove volumereplicationgroups.ramendr.openshift.io/vr-archived annotation
Delete its PersistentVolume and PersistentVolumeClaim object replicas from the stores specified in VRG's Spec.S3Profiles
Delete its VolumeReplication object
Change PV's ReclaimPolicy to Delete and remove volumereplicationgroups.ramendr.openshift.io/vr-retained annotation if it is set
Remove volumereplicationgroups.ramendr.openshift.io/pvc-protection finalizer from PVC
Remove its protectedPVC from VRG's status

Constraints

Limit S3 read and write rate to 1 / minute / VRG

Noobaa cannot tolerate a rate of 1 write / 3 sec https://github.com/RamenDR/ramen/pull/882#issuecomment-1542969558

Assumptions

A VRG's PVC selector is immutable

This is not enforced for VRGs but is for DRPCs

PVC selector may be specified in a recipe which includes both a label selector and, with PR #1090, a list of namespaces

A VRG's S3 profile names are immutable

This is not enforced for VRGs but is for DRClusters

A PVC may be selected by at most 1 VRG

This is not enforced for VRGs but there is a PR to enforce it for DRPCs

A PVC is excluded from a VRG's protection by modifying its labels

Unprotected PVC discovery

VRG controller discovers PVCs to protect or unprotect due to deletion by querying the API server for PVCs matching the VRG's PVC selector

Deselected PVCs, to be unprotected, won't be discovered

Approaches to discovering formerly protected PVCs

Get list from VRG's S3 stores

Query each S3 store

Drawback: rate limiting required due to Noobaa issue

Get list from VRG's Status.ProtectedPVCs

VRG is already queried at the beginning of reconcile

Drawback: A PVC and its PV may be stored in S3, and its VR created, but VRG status update that adds PVC may fail

Get list from API server

Label each PVC with which VRG is protecting it

#627 proposes annotations, but labels leverage more efficient, built-in API server-side filtering

The first persistent step to protecting a PVC is updating it in API server with its VRG finalizer.  If this update fails, it will not be protected.  In the same update, I propose the PVC be labeled with its protecting VRG's name and namespace name.
On VRG reconcile as primary, the API server is queried for the set of VRG-owned PVCs and those currently matching the VRG's PVC selector.  Those owned but no longer matching are unprotected. To unprotect a PVC:

Delete replicas of it and its PV from each of the VRG's S3 stores and remove associated annotation
Unretain its PV and remove associated annotation
Delete its VolumeReplication resource and remove associated annotation
Delete its ProtectedPVC from VRG status
Delete its VRG-protected finalizer

#627 proposes at most one VRG own a PVC.  This solution maintains that assumption.  Supporting multiple VRGs protecting a PVC would require:

only the last one to unprotect it unretain its PV and remove its finalizer
a way to label multiple owners to find formerly protected PVCs

The impact of this issue to Cloud Pak for Data is recovery failure #1101

The first persistent step to protecting a PVC is updating it in API server with its VRG finalizer. If this update fails, it will not be protected. In the same update, I propose the PVC be labeled with its protecting VRG's name and namespace name.
On VRG reconcile as primary, the API server is queried for the set of VRG-owned PVCs and those currently matching the VRG's PVC selector. Those owned but no longer matching are unprotected. To unprotect a PVC:
* Delete replicas of it and its PV from each of the VRG's S3 stores and remove associated annotation

* Unretain its PV and remove associated annotation

* Delete its VolumeReplication resource and remove associated annotation

* Delete its ProtectedPVC from VRG status

* Delete its VRG-protected finalizer

The above scheme is fine, trusting what is marked as protected on the API server and pruning those that are extra.
I suggest limiting the initial implementation to only the sync case, i.e not handle VR and VolSync backed PVC (IOW the async case). This limits the changes to the code in addressing it for the current urgent need at hand.


Styles in node_modules are only loading while in develop

I'm using the bootstrap npm library in my este app. In development, the app is loading the css fine. I have the following in my src/client/app/app.styl:
@import '../../../node_modules/bootstrap/dist/css/bootstrap.css'
But when my app's NODE_ENV is set to production, the bootstrap css isn't being loaded. Do you know why it would fail to load the ccs in production?

Sorry, no. But feel free to send PR if you found error in Este.

You can try use
import 'bootstrap/dist/css/bootstrap.css';
in your js file


Does not work with ESLint v8 (ESLint: Invalid Options: - Unknown options: object-shorthand)

I have started a new project and VS Code ESLint (v2.2.3) would not work. This message popped up. ESLint from console was working fine. The problem persisted even after removing all ESLint configuration. The issue was resolved after downgrading to ESLint 7.x
`[Error - 5:44:09 PM] Error: Invalid Options:

Unknown options: object-shorthand
at processOptions (/home/.../project/node_modules/eslint/lib/eslint/eslint.js:281:15)
at new ESLint (/home/.../project/node_modules/eslint/lib/eslint/eslint.js:428:34)
at Object.e.newESLintClass (/home/.../.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:170158)
at Ce (/home/.../.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:189261)
at /home/.../.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:183220
at /home/.../.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:184587
`

Which version of VS Code are you using? VS Code ships with a node version and I guess that one is too old. You can either use eslint.runtime to point to a newer node version or ensure that you are using the latest version of VS Code.

I'm using 1.67.1, which is currently the latest version.
Version: 1.67.1
Commit: da15b6fd3ef856477bf6f4fb29ba1b7af717770d
Date: 2022-05-10T21:35:59.370Z
Electron: 17.4.3
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.17.4

@mckravchyk can you try validating the file in the console using a node version 16.13.
If this works fine can you please provide me with a GitHub repository I can clone that demos what you are seeing.
If it doesn't work use the eslint.runtime option to ask the ESLint server to use a different node executable.

Hey @dbaeumer, sorry for the late reply.  I have been ignoring the issue but now I'm keen on finally resolving it as it's probably a matter of time when using an older version of Eslint blocks me from upgrading other packages.

I have verified that CLI linting works with Node 16.14
I have reproduced the problem in this most basic fiddle

Please let me know if there's anything I can do to gather more debugging info.
My current Code version:
Version: 1.73.0
Commit: 8fa188b2b301d36553cbc9ce1b0a146ccb93351f
Date: 2022-11-03T14:04:08.642Z
Electron: 19.1.4
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.0.7
Sandboxed: No

I am not able to reproduce this:

Could it be that there is a eslintrc config file in a parent directory that is considered. You can stop looking up the chain using   root: true

There's no parent directory. I have added root: true though and it had no effect.
It looks like the error is due to an invalid "object-shorthand" option being passed to the ESLint constructor.
I have added the following to the local ESLint module:
/**
 * Main API.
 */
class ESLint {

    /**
     * Creates a new instance of the main ESLint API.
     * @param {ESLintOptions} options The options for this instance.
     */
    ...
    constructor(options = {}) {
        console.log('Initializing ESLint');
        console.log(options);

        // Injecting this fixes the  issue
        if (typeof options['object-shorthand'] !== 'undefined') {
            delete options['object-shorthand'];
        }
       ...

CLI gives me:
Initializing ESLint
{
  allowInlineConfig: true,
  cache: false,
  cacheLocation: '.eslintcache',
  cacheStrategy: 'metadata',
  errorOnUnmatchedPattern: true,
  fix: undefined,
  fixTypes: undefined,
  ignore: true,
  overrideConfig: {
    env: undefined,
    globals: undefined,
    ignorePatterns: undefined,
    parser: undefined,
    parserOptions: undefined,
    plugins: undefined,
    rules: undefined
  },
  overrideConfigFile: undefined,
  reportUnusedDisableDirectives: undefined,
  resolvePluginsRelativeTo: undefined,
  rulePaths: undefined,
  useEslintrc: true,
  extensions: undefined,
  ignorePath: undefined
}

Extension output gives  me:
Initializing ESLint
[Object: null prototype] {
  'object-shorthand': [ 'error', 'always' ],
  cwd: '/home/.../eslint-bug'
}

Injecting code to the ESLinnt constructor to remove the option before it's being processed fixes this issue.

I am a little bit puzzled as well. If I add an object-shorthand to the eslintrc file everything works for me:

It is hard to say without steps on how to reproduce this.
BTW: the options passed to the ESLint class constructor are not rule definition. These options are documented here: https://eslint.org/docs/latest/developer-guide/nodejs-api#-new-eslintoptions

It took me going up the call stack to find that  I had the below in my global settings.json :)
      "eslint.options": {
          "object-shorthand": ["error", "always"]
      },

I know these constructor options are different but for whatever bizzare  reason I defined it in the options a few years ago and forgot about it. It seems like ESLint introduced option validation in v8, so it went on unnoticed in the previous versions.

Good to heat that you were able to solve this.


remove getMassDensity

Description
Remove getMassDensity since its never called with an arg and does the same thing as density()
(undoes refactor in #818)

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

Tagging @drewj-usnctech and @sombrereau just as a heads up for their projects in case this will affect them adversely.

Yes, if there are adverse effects we can rename getMassDensity to getMassDensityOfNucs or something to that effect. none of our plugins had picked it up in the 8 months, but if yours had let us know.


 Switch between Dvorak and Japanese IME is untenable due to other bugs with East Asian support Windows introduced in the past months.
WSL logs:
No response
WSL dumps:
No response
Expected behavior:
I expect to be able to type with Dvorak (or any custom layout) inside of WSLg windows, even if using an IME.
We should be allowed to manually set the WSLg keyboard layout. I want to just set my layout to US-Dvorak w/ ctrl+alt remapping and forget about it. Guessing what the user wants makes no sense, for example Korean IME isn't based on romanization and it makes no sense to default to Qwerty. A user (like myself) could easily learn Korean on a Qwerty, but use Dvorak for romanized IME input.
This is particularly important for developers (possibly the main users of WSL?). Not having a comfortable typing experience seriously ruins my nearly $3k Surface and large time investment this past year.
Actual behavior:
It is defaulting to US QWERTY:
convert_rdp_keyboard_to_xkb_rule_names: matching model=pc105 layout=jp variant=(null) options=(null)

@CarlOlson, this issue is reported at https://github.com/microsoft/wslg/issues/173, thanks!


Remove unsafe from nRF uarte and improve doco with rationale

The constructors themselves are not strictly unsafe. Interactions with DMA can be generally unsafe if a future is dropped, but that's a separate issue. It is important that we use the unsafe keyword diligently as it can lead to confusion otherwise.
I've also provided some rationale re. the usage of [Uarte] vs [BufferedUarte].

bors r+


Support unicode-display_width v2

Adds support for v2 of unicode-display_width. This version emits a warning when requiring the no_string_ext version, since omitting String extensions is the default. To compensate, I've reverted to the normal require, but this will of course include String extensions when the gem version is < 2. (It may make sense to require the unicode-display_widthversion be >= 2, to avoid unintentionally using a conflicting String API, let me know which approach you'd prefer.)
The only use of this library appears to be an invocation of Unicode::DisplayWidth.of in lib/rubocop/cop/mixin/alignment.rb, so this should be compatible with the v2 library changes.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!

Thanks!


How to search for particular things stored this can be anything that is stored I would like either time or something and is there a way to earase all data of a particular user

Hello @furkanshaikh313,
Can you be more explicit? What are you trying to search? This library is to search based on embeddings

I want to be able to save different types of data inside a vector database with having the ability to retrive data easily @JoanFM

What kind of data you want to store. Right now, vectordb allows to store data in a specific format schema

Like mainly text but it would be amazing if i can save images and audio as well

You can define the schema like this:
from docarray import BaseDoc
from docarray.documents import ImageDoc, TextDoc, AudioDoc

class MyDoc(BaseDoc):
    text: Optional[TextDoc]
    image: Optional[ImageDoc]
    audio: Optional[AudioDoc]
    embedding: NdArray

so should i use this with vector db?

yes, u can use this, define a schema that satisfies ur needs, and u can do this

by the way @JoanFM do you know a way i can like host this 24/7 on cloud for free?

I do not think there are options to host for free.

hmm Listen I am thinking of using this on a big project of mine and it need to be able to handle different customers and not intermix anything is that possible?

multitenancy is not supported. You would need to create an index for each of ur customers


Database Models and Associations

Database Models
Your database should contain the following four models, including the requirements listed for each model:

Category

id

Integer.

Doesn't allow null values.

Set as primary key.

Uses auto increment.

category_name

String.

Doesn't allow null values.

Product

id

Integer.

Doesn't allow null values.

Set as primary key.

Uses auto increment.

product_name

String.

Doesn't allow null values.

price

Decimal.

Doesn't allow null values.

Validates that the value is a decimal.

stock

Integer.

Doesn't allow null values.

Set a default value of 10.

Validates that the value is numeric.

category_id

Integer.

References the Category model's id.

Tag

id

Integer.

Doesn't allow null values.

Set as primary key.

Uses auto increment.

tag_name

String.

ProductTag

id

Integer.

Doesn't allow null values.

Set as primary key.

Uses auto increment.

product_id

Integer.

References the Product model's id.

tag_id

Integer.

References the Tag model's id.

Associations
You'll need to execute association methods on your Sequelize models to create the following relationships between them:

Product belongs to Category, and Category has many Product models, as a category can have multiple products but a product can only belong to one category.

Product belongs to many Tag models, and Tag belongs to many Product models. Allow products to have multiple tags and tags to have many products by using the ProductTag through model.

Make sure you set up foreign key relationships that match the column we created in the respective models.


Added how to build the apps on README

Closes #18

.env, Env.swift, and gradle.properties are git-ignored and need to continue that way because they contain environment variables.
The environment variables are listed on the notion page, which only Ditto members have access: https://www.notion.so/getditto/Environment-Variables-78261e05a2b44a299ee388f06e9ff86a

@magicwave

Should DITTO_AUTO_PROVIDER= be DITTO_AUTH_PROVIDER=?

Created #25, thanks for catching!

N.B.
Build fails with SwiftHEXColors error:
File not found: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_iphoneos.a

@magicwave Can you test #26 to see if it works?


fix broken ogImage link in blog posts

the approach taken for the solution if not the best but works for now.
Since og images needs to be served as static, the blog image then needs to be duplicated in public and src/assets folder. All images in blog posts lives in src/assets since astro optimizes them when placed in that specific folder.
Thus for now, blog header image has to be placed in both public and src/assets and used in .md blog posts accordingly.


Respect Alchemy.admin_path

Alchemy 3.3 has the ability to change the path the admin is located at. This PR makes alchemy-usermanual respect that path.

Nice! thanks @ajoneil


Question: Is there a way to make logging less verbose?

This is just a glimpse of a log. It is not event an Action-related piece. What is the correct way to make the logging silent?

UPD. Sorry, viable for closing. The solution is simple:
Code from sample:
	// create chrome instance
	c, err := cdp.New(ctxt, cdp.WithLog(log.Printf))

	if err != nil {
		log.Fatal(err)
	}

change to
// create chrome instance
	c, err := cdp.New(ctxt) // no WithLog() option

	if err != nil {
		log.Fatal(err)
	}


Insert minus sign at the start

I used the following code to configure an input element where the user can enter a number positive or negative between -99.9999 and 99.9999.
$('#AddressLatitude').inputmask('[-]99.9{0,4}',
            {
                digits: 4,
                integerDigits: 2,
                digitsOptional: true,
                placeholder: '0',
                showMaskOnHover: true,
                rightAlign: false,
                showMaskOnFocus: true,
                allowMinus: true
            });

...This works so far.
But I’ve one problem.
The user cannot insert a minus sign at the start of the input after he has already entered one or more numbers.
Is it somehow possible to make this work?

@DaveSenn ,
You are mixing options from the numeric alias with another mask.  Remove the mask and use the numeric alias instead.
$('#AddressLatitude').inputmask('numeric',
{
digits: 4,
integerDigits: 2,
digitsOptional: true,
placeholder: '0',
showMaskOnHover: true,
rightAlign: false,
showMaskOnFocus: true,
allowMinus: true
});

Thanks for your response.
I tried your code but it still does not work.
I’ve created a fiddle: JSFiddle
Steps to reproduce:

Enter any number (matching the mask)
Set the cursor to the start of the input and try to add a minus sign
-> This does not work.

The only way the user can enter a minus sign, is to enter it, before the input contains anything else.

@DaveSenn ,
It seems a bug when using the   integerDigits: 2, option.  Remove it and it will work.
I will see how to fix this.


Issue with generating

After running it stops after 4 tasks and doesnt send anything

Same issue

+1

same

@BlackSnowDot

fixed


Workflow parameterization

This PR was merged with PR #35, but this wasn't fully finished. So I'm reopening this PR as I continue to build out the simulation setup workflow. Here is the PR notes from the original PR
Reason for the PR
I think a lot of friction for getting simulations setup and running are because the force field parameter generation and assignment was setup to run in the examples directories, instead of directly in the simulation workflow. This PR is meant to put the simulation setup, running and analysis all in one place. Additionally, this PR is meant to take a lot of the hand tuning required to setup simulations.
Features

Based on specific parameter YML files parameterization can be handled by different workflows (whether we need to parameterize with OpenFF-2.0 or a Bespoke-Fit FF).
Build system with packmol in a signac workflow. These workflow functions should check for specific software they need to run, or they can be provided in the input files.
Move REMD simulations and MD simulations into a signac workflow that is in analysis_workflows

To Do's

[x] Add workflow function to build foldamer
[x] Add workflow function to solvate system with chloroform (and minimize). This will require the system to have packmol installed (or at least an input option that points to packmol or make it a subpackage)
[ ] Add workflow function to build topology file for any system
[ ] Add workflow function that sets up and submits REMD simulations
[ ] ...

@mattwthompson Do you know the best-practice way to include an OpenEye license for testing with GHAs? I see OpenFF-toolkit has tests with and without OpenEye

Do you know the best-practice way to include an OpenEye license for testing with GHAs? I see OpenFF-toolkit has tests with and without OpenEye

Yeah, you don't want to include OpenEye in any release package.

In terms of packaging, you want to keep it an optional dependency. Both because your users might not have a license and because you can't bundle it with a released version (licensing details, to my understanding) nor include it as a required dependency, at least with conda-forge infrastructure.
If you want to include it in CI runs, and I'm not totally sure you do, OpenFF's setup is to store a license we're permitted to use in CI (we might have special permission, I don't know the terms of the Shirts license) as an org-level secret that's accessible from actions. (https://github.com/organizations/ORG_NAME/settings/secrets/actions, stored as OE_LICENSE as a secret, which is encrypted and not visible even to us.) This is then accessible in actions and dumped into an encrypted file in a way that's not accessible in logs, and for that matter the secret isn't even accessible when CI is run from a fork.
My $0.02, not knowing what functionality you actually need in automation, is to keep things RDKit/open-source in CI and roll with OpenEye in your local development/production environment. This is how the toolkit is designed to work, including both the high-level API and skipping tests if OpenEye is not installed.

Okay, sounds good! I was asking because I had a testcase that assigns parameters for a small foldamer that would go faster on an install with OpenEye, but since it's using the OpenFF toolkit it can still run without OpenEye, it just takes a bit longer (~40 minutes). I might just skip that test all together when running tests with GHAs.

Yeah, I wouldn't worry about the OpenEye interface.


Revert "chore: replace puppeteer with playwright"

Reverts dotansimha/graphql-yoga#3540
Due to the additional latency in the CI, for now we decided to keep using puppeter

FYI @ardatan I'm seeing if I can get Playwright install times on CI down here https://github.com/dotansimha/graphql-yoga/pull/3543.

The other PR is rfr. I brought Playwright cache-hit install times down to 4s. It also removes post install hook stuff. I expect this to mean it is also faster than our previous setup with Puppeteer.


vCD API logging in Terraform examples

What this PR does / why we need it:
It introduces a new, optional variable for the vmware-cloud-director terraform example: logging.
When set to true it will log all vCD API activities into the logfile "go-vcloud-director.log". The default value is false, so nothing changes for existing configurations.
Which issue(s) this PR fixes:
Not necessarily an issue that is being fixed by this PR, but it allows for actively debugging vCD API interaction if there is a problem.
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
NONE

Documentation:
NONE

/test pull-kubeone-verify-codegen

/test pull-kubeone-verify-codegen


Vimeo only plays when one accepts statistics cookies

Created:
https://support.cookiebot.com/hc/en-us/requests/105481
(credentials are in 1Password for Cookiebot Support)

Sciety - Video embedding and cookie consent.pdf


Slow UI rendering

What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
I have a simple html on the layout (it can be on the page the same), and during some ms it doesn't load the styles, so it glitches the loading of the website
https://youtu.be/ADwgf3reHTE
In which browser(s) did the problem occur?
No response
Steps To Reproduce
Make a simple html
Use the Svelte UI Beta components (Button for example)
refresh the website
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Relevant Assets
https://youtu.be/ADwgf3reHTE

What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
I have a simple html on the layout (it can be on the page the same), and during some ms it doesn't load the styles, so it glitches the loading of the website
https://youtu.be/ADwgf3reHTE
In which browser(s) did the problem occur?
No response
Steps To Reproduce
Make a simple html Use the Svelte UI Beta components (Button for example) refresh the website
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Relevant Assets
https://youtu.be/ADwgf3reHTE

I've been checking the issue deeper. Maybe is related to Vite
https://github.com/vitejs/vite/issues/7608
My impression is that it's related to this late styles update. Maybe you can investigate more about

This is related to the SSR setup we have, see here. Basically we need to inject our CSS when the page is being built and not only when it's passed to the client


Preserving Positions after Scope Injection

The positions information can be useful. For both error reporting and maybe some post processors can use some information from the positions.

LGTM.

I will release tomorrow my release machine is without a power cord due to the summer school.

Thanks :)


Unable to create project with sqlite3 database

When running suspenders foobar --database sqlite3 I get the following error
Specified 'sqlite3' for database adapter, but the gem is not loaded. Add `gem 'sqlite3'` to your Gemfile (and ensure its version is at the minimum required by ActiveRecord). (Gem::LoadError)

Have you tried installing the sqlite3 gem?

I have not, I was under the impression suspenders would load all required gems into the new projects gem file upon creation.  It seems there is actually a running list of prerequisite one needs before using this gem.

@Yanchek99 I know it's been some time, but thank you for reporting this issue! :heart:
I'm closing this ticket in favor of the following one:
https://github.com/thoughtbot/suspenders/issues/1082


sigil: 0.7.4 > 0.9.6

Motivation for this change
When I tried installing sigil it downloaded the source code and then failed to build it.
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Pushed to master (0efd18746abd338d670ab82fa0d9e5411fd53329). Thanks!