Simulations don't run on a centos 7 installation

Hi, For all I know I have tried to run the demo on a centos6 and centos7 installations. Definitions were set identically by following the readme instructions.
1_flow_demo runs fine on Centos6, including simulation and plots.
On Centos7, all the steps before the simulation run fine, but the simulation itself hangs. It throws an error after several minutes (timeout probably).
Is the demo verified to run on Centos7/RHEL7? If so, am I missing some path definition?
Traceback:
using existing BagProject
computing layout
ext_w0 = 1, ext_wend=1, ytop=2592
final: ext_w0 = 1, ext_wend=1, ytop=2592
{'s': WireArray(TrackID(layer=3, track=7, num=9, pitch=2), 1109, 1265, 0.001), 'd': WireArray(TrackID(layer=3, track=8, num=8, pitch=2), 1231, 1387, 0.001), 'g': WireArray(TrackID(layer=3, track=8, num=8, pitch=2), 915, 1071, 0.001)}
WireArray(TrackID(layer=3, track=8, num=8, pitch=2), 915, 1071, 0.001)
6.5
creating layout
layout done
computing AMP_CS schematics
creating AMP_CS schematics
running lvs
Running tasks, Press Ctrl-C to cancel.
lvs passed
lvs log is /home/mgal/Cadence/BAG2_cds_ff_mpt/pvs_run/lvs_run_dir/DEMO_AMP_CS/AMP_CS/lvsLog_20181130_235100uue_tc3j
computing AMP_CS_tb_ac_tran schematics
creating AMP_CS_tb_ac_tran schematics
schematic done
setting up AMP_CS_tb_ac_tran
running simulation
Running tasks, Press Ctrl-C to cancel.
simulation done, load results
Traceback (most recent call last):
File "", line 22, in
demo_core.run_flow(bprj, top_specs, 'amp_cs', layout_core.AmpCS, run_lvs=True)
File "/home/mgal/Cadence/BAG2_cds_ff_mpt/BAG_XBase_demo/xbase_demo/core.py", line 386, in run_flow
simulate(prj, specs, dsn_name)
File "/home/mgal/Cadence/BAG2_cds_ff_mpt/BAG_XBase_demo/xbase_demo/core.py", line 175, in simulate
results = load_sim_results(tb.save_dir)
File "/home/mgal/Cadence/BAG2_cds_ff_mpt/BAG_framework/bag/io/sim_data.py", line 131, in load_sim_results
top_swp_list, values_list = _get_sweep_params(os.path.join(save_dir, 'sweep.info'))
File "/home/mgal/Cadence/BAG2_cds_ff_mpt/BAG_framework/bag/io/sim_data.py", line 70, in get_sweep_params
mat = np.genfromtxt(fname, dtype=np.unicode)
File "/home/mgal/anaconda3/lib/python3.7/site-packages/numpy/lib/npyio.py", line 1700, in genfromtxt
fhd = iter(np.lib._datasource.open(fname, 'rt', encoding=encoding))
File "/home/mgal/anaconda3/lib/python3.7/site-packages/numpy/lib/_datasource.py", line 262, in open
return ds.open(path, mode, encoding=encoding, newline=newline)
File "/home/mgal/anaconda3/lib/python3.7/site-packages/numpy/lib/_datasource.py", line 618, in open
raise IOError("%s not found." % path)
OSError: /home/mgal/Cadence/BAG2_cds_ff_mpt/BAGTMP/simTmp_20181130_2340232vgmmrmy/BagSim_data_20181130_235109pq3dymmi/sweep.info not found.
Best,
Matan

In the temporary folder (/home/mgal/Cadence/BAG2_cds_ff_mpt/BAGTMP/simTmp_20181130_2340232vgmmrmy):

did the ocean script get created?
is there a log file in that folder?  What does it say?
Can you run the ocean script yourself on commandline manually?  If so, does it work?

Hi,

Yes, the ocean script is created.
The ocean script runs if loaded from the command line. The strange thing is that once the script is done running, the CIW closes (and virtuoso terminates). Is that intentional?
There is definitely a problem with either the way ocean scripts are running in EL7 vs EL6, with permissions, or with my installation (?). Log file of the non-running simulation:
command: ocean -nograph -replay /home/mgal/Cadence/BAG2_cds_ff_mpt/BAGTMP/simTmp_20181130_2340232vgmmrmy/BagSim_data_20181130_23
5109pq3dymmi/run.ocn -log /home/mgal/Cadence/BAG2_cds_ff_mpt/BAGTMP/simTmp_20181130_2340232vgmmrmy/BagSim_data_20181130_235109pq
3dymmi/ocn_output.log
2018/11/30 23:51:09 WARNING This OS does not appear to be a Cadence supported Linux configuration.
2018/11/30 23:51:09 For more info, please run CheckSysConf in <cdsRoot/tools.lnx86/bin/checkSysConf
WARNING Unable to open -nograph X Window Display "hostname:80"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :80 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:80.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:81"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :81 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:81.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:82"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :82 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:82.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:83"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :83 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:83.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:84"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :84 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:84.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:85"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :85 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:85.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:86"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :86 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:86.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:87"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :87 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:87.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:88"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :88 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:88.log
Trying another display...
WARNING Unable to open -nograph X Window Display "hostname:89"
WARNING (using "exec /opt/ICADV123/tools.lnx86/dfII/../bin/cdsVncserver :89 -co /usr/share/X11/rgb&").
WARNING cdsXvnc output may be found in file $HOME/.vnc-cds/hostname:89.log
WARNING Giving up after trying 10 displays.
WARNING Unable to connect to a non-graphical X Window Display server.
WARNING Try using the -vncTenbase option or the CDS_XVNC_TENBASE environment variable to specify a different set of 10 display
s.

Any thoughts?
Thanks.
Matan

So you are running ocean in a terminal using -nograph, -replay, and -log options?  Why would it close Virtuoso then?  does this ocean command pop up virtuoso GUI?  How would this separate process know anything about the other Virtuoso GUI process?

I have no idea about those X errors, some googling may help, or if you can contact cadence support I'll do so.  However, you say that the ocean script still runs?  Does it generate the output data file?

No, I'm typing load("<run.ocn path>") in the CIW. Sorry, I wasn't clear.

Yes, the ocean script runs and results look fine as far as I understand..

ok, to debug you have to run ocean from terminal, as that is the way BAG runs simulation.  Use the nograph, replay, and log options.

Hmm. Interesting. Ocean indeed doesn't run from command-line, and it's the "-nograph" option that makes it fail. That's about as far as my knowledge goes. It can still be a permissions or a missing package issue (installation), or some difference with how the C7 installation handles ocean scripts (unlikely IMO). Any ideas will be welcome..

OK. problem solved. Short answer - xorg-x11-fonts packages were missing:
https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/40782/ocean-script-running-on-centos6-but-not-on-centos7


Edit SVS auxiliary images

Hi, I am working with SVS images, and the label contains some confidential information that we would like to de-identify without losing all the label information since it is used for Quality Checks. The image has only one scene, and the label is only found as an auxiliary image. I can see you have transformation options at the scene level, and I was wondering if there is a way to edit and save the slide's auxiliary images as well. Thanks.

Hello, SlideIO transformations do not support removing of auxiliary images. You can use SlideIO converter, which converts other formats to SVS.  But the converter recompresses the image. It takes some time.
I hope it helps.
Best regards,
Stanislav


User friendly parameter defintion

I think it is not very comfortable to source all enumerations everytime.
I think we can build up wrapper with a bit fuzzy logic to determine the Parameter, periodType and TimeResolution.
This is quite similar to issue #8
define_request(parameter='precipitation', time_resolution='10min', start_date?, end_date?,)

Enumerations are helpful to make the code clean but they are not very user friendly I think.

My original thought with parsing parameters from the file was that you could start anywhere between checking metadata and parsing data into a dataframe. But probably you are right, that nobody would use only one function but it's more like a tube that would mean that only a combination of all those functions make it work. This way instead of a function I would suggest a class. Either this class will call our functions one after each other, or our functions will "complete" our class by time, and if certain steps are not done, for example a link to the file is not given, it will throw an error when trying to download the file.
What do you think?

This is a good point. Maybe we provide once a script that is managing the whole pipeline. There we need a defined interface. and if anyone would like to use one of the functions in the pipeline they have to check by themself.


Fix incorrect directory name in code example

Code example creates a directory named myapp but then tries to cd into my-app. Originally changed in 0cbac1aa4885d21d29b50ce607353e8f07103651.

The solution is to fix the cd my-app, not to revert #364, which will bring back the unwanted horizontal scrollbar.


How do I get a token and does it cost anything?

I really don't know how I got LiveStreamer to work.  It was over a year ago, and I just did some quick searches online and used trial and error.  I was even able to find a free token.  And somehow I set it all correctly.  And then I just type something like the following in Command Prompt:
livestreamer --http-header Client-ID=(some long number) twitch.tv/(twitch streamer name) audio_only
But now it doesn't work all of the time.  For instance, I'm getting this now:
[cli][info] Found matching plugin twitch for URL twitch.tv/(twitch streamer name)
error: Unable to open URL: https://api.twitch.tv/api/channels/ (twitch streamer name)/access_token.json ([Errno 1] _ssl.c:504: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version)
It will probably work again later, but I have no idea what is causing this error message.  I'm thinking that maybe someone found the same token I did and maybe they are using it now which is keeping me from using it because maybe two people can't use it at the same time?  If that is the case, how do I get my own token and does it cost anything?

To answer your question: The client-id tokens are obtained by registering a application with Twitch.  As far as I know these don't cost anything. The tokens are used to identify a application with the Twitch-API and thus are supposed to be shared by everyone who is using the same application (meaning the issue is not related to others using an identical token).
The actual issue is not related to the client-id at all. The problem is that this project has not been updated for several year and the old TLS version used by Livestreamer is no longer supported by Twitch. While it is probably possible to update livestreamer I would recommend using streamlink which is a continuation of this project. (you wouldn't even have to use the --http-header-client-ID workaround anymore)

Thank you for referencing me to streamlink.  I'll have a look at it.  Does it let me play audio_only or some quality of video in my VLC player?

Like I said: streamlink is a continuation of livestreamer after it became obvious that livestreamer was abandoned. It can more or less do everything livestreamer can do.

Thanks skulb.  I made the switch today, and it is working.


Typescript 4.8.2 and loadFromPivotTable

Describe the bug
Reported a few times before its official release, but now it has been released and dependabot opend a PR on our repo

https://github.com/mikro-orm/mikro-orm/issues/3367
https://github.com/mikro-orm/mikro-orm/issues/3367

Stack trace
error TS2344: Type 'MongoDriver' does not satisfy the constraint 'IDatabaseDriver<Connection>'.
             Types of property 'loadFromPivotTable' are incompatible.
               Type '<T, O>(prop: EntityProperty<any>, owners: Primary<O>[][], where?: FilterQuery<T> | undefined, orderBy?: QueryOrderMap<T>[] | undefined, ctx?: any, options?: FindOptions<...> | undefined) => Promise<...>' is not assignable to type '<T extends AnyEntity<T>, O extends AnyEntity<O>>(prop: EntityProperty<any>, owners: Primary<O>[][], where?: FilterQuery<T> | undefined, orderBy?: QueryOrderMap<...>[] | undefined, ctx?: any, options?: FindOptions<...> | undefined) => Promise<...>'.
                 Types of parameters 'options' and 'options' are incompatible.
                   Type 'FindOptions<T, never> | undefined' is not assignable to type 'FindOptions<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never> | undefined'.
                     Type 'FindOptions<T, never>' is not assignable to type 'FindOptions<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>'.
                       Types of property 'fields' are incompatible.
                         Type 'readonly EntityField<T, never>[] | undefined' is not assignable to type 'readonly EntityField<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>[] | undefined'.
                           Type 'readonly EntityField<T, never>[]' is not assignable to type 'readonly EntityField<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>[]'.
                             Type 'EntityField<T, never>' is not assignable to type 'EntityField<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>'.
                               Type 'keyof T' is not assignable to type 'EntityField<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>'.
                                 Type 'string | number | symbol' is not assignable to type 'EntityField<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>'.
                                   Type 'string' is not assignable to type 'EntityField<T | ((Primary<T> extends string ? string | RegExp : Primary<T> extends Date ? string | Date : Primary<T>) & {}), never>'.

To Reproduce
Steps to reproduce the behavior:

Upgrade typescript

Yes, its out just few hours :] The release is very breaking for our codebase, you can see how many changes were required to support it partially in #3389. This might take some time to finish.

auch!

One of the issues TS reports is also coming from knex, cc @kibertoad
$ tsc --noEmit --project tests/tsconfig.json
node_modules/knex/types/index.d.ts:453:33 - error TS2344: Type 'TRecord | TResult' does not satisfy the constraint '{}'.
  Type 'TResult' is not assignable to type '{}'.

453             | Knex.QueryBuilder<TRecord | TResult>
                                    ~~~~~~~~~~~~~~~~~

It was fixed in https://github.com/knex/knex/pull/5279, I believe, but not yet released. I'll publish a new version soon

So once knex is released, #3389 should be good to go. I am sure this will break some projects on type level, but what can we do :]

@kibertoad could we have the fix published please?

yes, will do it tonight

@B4nan released in 2.3.0, please let me know if it works as expected

Yes, perfect, thanks!


Update setdex_xy.js

removed pokemon in higher tiers, updated ev spreads

Nice updates, but is there any reason one of Cobalion's RU sets was left in?

Done in #27


Add remove-statements action to ecr

This is related to Issue https://github.com/capitalone/cloud-custodian/issues/1528

rewritten and tests added


Not able to set on_failure_callback in default args

I am trying to set the default args as
default_args={'on_failure_callback': 'foo_function_str`}
the yaml config I am trying
dag_1:
   default_args:
       start_date: '1999-01-01'
       on_failure_callback: 'dags.utils.failures.send_alert' -- str representation of function

The other config I tried using on_failure_callback_file but this does not set the property in the default dict.
dag factory version - 0.8.0

Hi @madhavdube,
I tried creating the DAG based on your config file using the latest version of dag-factory v0.19.0, and it worked fine. Please try running it with the latest version.
As for specifying callbacks, another method is to use the parameters: on_failure_callback_file and on_failure_callback_name. You can find more details in the documentation.
One limitation is that currently it's not possible to provide callbacks within default_args. You can only define them at the DAG level, like this
dag_test:
  default_args:
    start_date: '2024-09-14'
  on_success_callback_file: "/usr/local/airflow/dags/utils/utils/failures.py"
  on_success_callback_name: "send_alert"

However, I've created a PR that will allow specifying callbacks inside default_args, enabling callback configurations for individual DAG tasks as well: https://github.com/astronomer/dag-factory/pull/218.


chore: resume manifest logic and Scenario_ubuntu2204privatekubepkg to support unhappy path

What type of PR is this?
/kind bug
What this PR does / why we need it:
chore: resume manifest logic. This is to support some components which are still using floating cse bootstrap scripts.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.005%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
2564

Relevant Lines:
3611

💛  - Coveralls


Fix typo of the comment in xoro_mod.c

This commit fixes a typo in the first line of xoro_mod.c, changing /* Acharacter ... */ to /* A character ...*/.

Thank @randyuncle for contributing!


is size tag supported?

For example, if the model size is set as a tag,
Tag selections are as follows:
tag1 (less than 5G)
tag2 (0.5-20G)
tag3 (above 10G)
There are three models:
Model a, with a size of 0.4G
Model b, with a size of 6G
Model c, with a size of 99G
If tag1 is selected, it will filter out model a.
If tag2 is selected, it will filter out model b.
If tag3 is selected, it will filter out model c.
Could you please confirm if these types of tags are supported? If yes, how can they be set? If not, will they be considered in the future?

you can define size tag like this in readme.md
size_categories:
- 100B<n<1T

and create system built-in tag category:  size

请问怎么使用啊？
1.界面上可以增加 tag  category嘛
2.size_categories:

100B<n<1T。  这个是不是和tag一样的格式。
如下这么写嘛？

用户自定义标签
tags:

34B
size_categories:
100B<n<1T


upgrade lucene.net component to 4.8.0

Description of problem
lucene.net component is out-to-date.
Description of solution
upgrade lucene.net component to 4.8.0

AFAIK still an open task.

A PR was create for this and there was a discussion about that change. 4.8.0 is still a beta, which means they could still introduce any breaking changes before release. In the current state the approvers did not want to put a dependency on beta packages as more breaking changes can still occur.
Also, this upgrade includes breaking changes that would require proper adjustments/testing after the package is out of Beta.
So to be able to make this an actionable issue we need:

Lucene.Net package to be out of Beta
Planning this upgrade at the very least for a minor release if we have proper wrappers so it's not a breaking change for 3rd party Dnn developers
Planning this upgrade for a major release if we also need to introduce a breaking change.

4.8.0 has been in beta for like 2 years. I will close this issue in the spirit of cleaning the backlog so it does not hang here for too long. If anyone want's to proceed with more analysis/discussions just ping me up and I'll be glad to move it to a discussion instead until this is actionable.


pygmentize does not correctly report file names with UTF-8 characters

(Original issue 1067 created by a3nm on 2014-12-01T21:28:18.484526+00:00)
On revision 3562, with Python 2.7.8, running the following:
#!bash

echo foo > é
./pygmentize é

results in the following broken error message:
#!

Error: no lexer for filename '\xc3\xa9' found

Unless I'm doing something wrong, it would probably be neater to fix this?

(Original issue was assigned to birkenfeld)
(Original issue 1067 last updated on 2015-10-17T06:41:18.678104+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by tshatch on 2015-10-17T02:40:53.938093+00:00)
To be clear, you didn't expect it to find a lexer for that name, you're just talking about the error message?

(Original comment by birkenfeld on 2015-10-17T06:41:18.693659+00:00)
I hesistate to change this, since UnicodeErrors during printing of the exception lurk.
Unless you're using Python 3, you'll have to live with small nits like this.


JSON Auto-Format doesn't display null values...

System information:

Operating system: Mac OS 10.14.4 beta 2
DBeaver version: 5.3.3 EE
Java version: 1.8.0_25
Additional extensions: none

Connection specification:

Database name and version: Postgres 9.6.9
Driver name: PostgreSQL JDBC Driver
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
The auto-formatter version of a JSON field doesn't display any entities that are set to NULL

Steps to reproduce, if exist:
Create a table that has a JSONB column.
INSERT a row, including the following text for the JSON: {"id": 123, "title": "Test", "bogus": null}
SAVE the row
Refresh the table by pressing F5
Look at the data in the table and in the Value Panel (with the setting to JSON and Auto-Format set to true)
Include any warning/errors/backtraces from the logs

Thanks for the bug report.
See fix in the next version (you also can test the fix in Early Access version at https://dbeaver.com/files/ea)


CORS issue

It is not possible to deploy a smart contract using the web IDE due to CORS issue.
Tested on Chrome, Brave and Safari. The same problem on all.

@ultrafellen

Let me check this issue. Thanks for the report.

The issue has been resolved.

It worked! Thank you


Leader Board : Shows Top Play Contributor of the month and Top Play Contributors of all time

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
Shows Top Play Contributor of the month and Top Play Contributors of all time
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

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

Screenshots or example output

@NagarjunShroff The build consists a bunch of the linting errors. please fix them.

Hello @NagarjunShroff got a chance to check the comments? Also please resolve conflicts.

@NagarjunShroff this build fails due to this error:

Hi @NagarjunShroff Here are some tiny responsiveness issues I am observing.

The images in table gets cut

This is on a higher resolution screen. The left and right side is a far apart. It creates an impression lot of real estate waste. Can we provide fix such a way that they auto adjust with the gap between the columns?

@NagarjunShroff
I also wanted to ask:

Do you have details to link the numbers to the list of plays for all the creators on this page? Or do you suggest that to take as a separate issue?

@NagarjunShroff
I also wanted to ask:

Do you have details to link the numbers to the list of plays for all the creators on this page? Or do you suggest that to take as a separate issue?

Lets take that up as separate issue.

@NagarjunShroff
I also wanted to ask:

Do you have details to link the numbers to the list of plays for all the creators on this page? Or do you suggest that to take as a separate issue?

Lets take that up as separate issue.

Please create an issue once we merge this one.

Hi @NagarjunShroff Here are some tiny responsiveness issues I am observing.

The images in table gets cut

This is on a higher resolution screen. The left and right side is a far apart. It creates an impression lot of real estate waste. Can we provide fix such a way that they auto adjust with the gap between the columns?

@atapas Fixed - please test it.

LGTM


Way to get more than 100 changes at once

The API endpoints to get movies and shows that have recently updated has recently been capped to 100 results at once, the docs have always stated this however the endpoint historically let you request a lot more. It makes sense to limit the amount of results at once but 100 seems very low, if you were to only request updates once a day (or even every few days), there could be thousands of changes and with 100 at a time you could be making upwards of 50 requests.
Do you think there is any chance we could up the limit to make it a bit less painful for getting changes? If the issue is performance related as the endpoint does return the title, year and ids, do you think it would be possible to look into an endpoint that just returns the trakt id? All we need (and I assume what most people need who are monitoring changes) is just to know what trakt shows have updated so all we need is the id.
If it isn't possible then the only real solution I have is to manually load a show details with ?extended=full to see when it last updated which somehow seems worse and less performant than being able to use a changes endpoint.
Another issue I see is there is no way to get changes since a specific time? The API only accepts a yyyy-mm-dd style of date, even if I were to request changes every hour (which I can't anyway), it would still return changes for the whole day? Unless I am missing something, I couldn't get it to return changes since a specific date time.
Also there is another issue that I saw was also reported in #198, the endpoint does not add the X-Pagination-Page-Count and X-Pagination-Item-Count headers, I noticed that it sometimes returns it on the first request but in testing the same endpoint multiple times the header is not there anymore.

Thank you.

We were running into issues with some apps requesting a huge amount of data, with extended info. That's when I noticed the bug where the limit wasn't being enforced correctly as mentioned in the API docs.
I'll look into your other suggestions about a lightweight ID only method and accepting more specific date ranges.
Also, please use api.trakt.tv as the hostname, that old one is unsupported.

Thanks for the reply, an improvement to changes would definitely be ideal. At the moment for the project I use, in order to get updated shows it means we need to go through every show and check its last updated at which means if I have like 200 shows tracked, it requires 200 requests at minimum just to check what shows have changed, not even counting  how many more it takes if it a show has updated just to get the latest information. A more lightweight changes endpoint with a slightly higher limit and more specific date filters would go a long way to reducing the amount of requests required.

Also not related to this per se, currently it is quite hard to keep updated data, especially for shows, when requesting a shows full info it gives you the time a show was last updated which is useful to know if a show or its episodes have updated but it also means you then need to request the whole show, all its seasons and all its episodes to make sure you get the latest data and there isn't any way to know what specifically has changed.
If a show like The Expanse updates, it takes 7 requests at minimum to get the show, seasons and episodes. I think there is a way you could optimize this by making the seasons endpoint for a show return the time that a season last updated. This would mean if only Season 4 got a new episode, it would only require 3 requests to get the latest data instead of 7.
If something like this is possible then it would make getting up to date data much easier and reduce the amount of requests required.

I pushed a few updates. API docs have also been updated as needed.

/shows/updates and /movies/updates allow date and time. The time will be accurate to the hour (for caching purposes) but that should still give a much better degree of accuracy.
new methods /shows/updates/id and /movies/updates/id to return only Trakt IDs that have been updated.
/shows/:id/seasons?extended=full includes the updated_at field.

This is great news, thank you for this.

@rectifyer that's nice !
Any luck that you update the number of element returned by these endpoints ?
There is a lot of updated shows and getting them 100 by 100 will make my apps send more requests than fetching each show information individually.
Thanks a lot for your recent work on the API !

No plans to increase the limit currently. I'll see how these latest updates go and then see if that's something we can do once I have more metrics on the API methods.


Demo.py

Hi, thank you for great code! I notice there is a demo.py in your README demonstration, but don't find it in your code base. I would appreciate if you could provide it.

This demonstration shows the training and prediction process of our framework, the code is very simple, you can try it by yourself~

Thanks for your interest in NeuralKG. For the convenience of learning NeuralKG, we'll add demo.py later.


--meta-level 1 show sources triggers compilation

In an existing project with a meta-build, running mill --meta-level 1 show sources triggers compilation in the same meta-level. This comes to a surprise, as compilation depends on the sources and I was in the process to analyze a compile error, for which I wanted to inspect the sources.
Reproducer:
// build.sc
import $meta._

this is a build error

// mill-build/build.sc
object `package` extends MillBuildRootModule

> mill --meta-level 1 show "{sources,allSourceFiles}"
No mill version specified.
You should provide a version via '.mill-version' file or --mill-version option.
Using mill version 0.12.0
[mill-build/build.mill-57/61] compile
[mill-build/build.mill-57] [info] compiling 1 Scala source to /tmp/mill2/out/mill-build/mill-build/compile.dest/classes ...
[mill-build/build.mill-57] [info] done compiling
[build.mill-57/61] compile
[build.mill-57] [info] compiling 1 Scala source to /tmp/mill2/out/mill-build/compile.dest/classes ...
[build.mill-57] [error] /tmp/mill2/build.mill:6:6: value is is not a member of build_.package_
[build.mill-57] [error] this is a build error
[build.mill-57] [error]      ^
[build.mill-57] [error] /tmp/mill2/build.mill:6:9: not found: value a
[build.mill-57] [error] this is a build error
[build.mill-57] [error]         ^
[build.mill-57] [error] /tmp/mill2/build.mill:6:17: not found: value error
[build.mill-57] [error] this is a build error
[build.mill-57] [error]                 ^
[build.mill-57] [error] three errors found
[61/61] ====================================================================================================== show {sources,allSourceFiles} ==========================================================================================================
1 tasks failed
compile Compilation failed

I would expect to see just the sources files, so I can examine them to probably spot any issues resulting in the compile error.

This is no new issue. I can reproduce this with Mill 0.11.0 too.
> MILL_VERSION="0.11.0" mill --meta-level 1 show sources
[mill-build/build.sc] [41/49] compile
[info] compiling 1 Scala source to /tmp/mill2/out/mill-build/mill-build/compile.dest/classes ...
[info] done compiling
[build.sc] [41/49] compile
[info] compiling 1 Scala source to /tmp/mill2/out/mill-build/compile.dest/classes ...
[error] /tmp/mill2/build.sc:3:6: value is is not a member of millbuild.build
[error] this is a build error
[error]      ^
[error] /tmp/mill2/build.sc:3:9: not found: value a
[error] this is a build error
[error]         ^
[error] /tmp/mill2/build.sc:3:17: not found: value error
[error] this is a build error
[error]                 ^
[error] three errors found
1 targets failed
compile Compilation failed


[feat] seek video

Seeking enables the user to control the preview time cursor.
In Worldview:

dispatch a seekTime action

In core:

call seek function on DeckAdapter

Pull Request Test Coverage Report for Build 916463009

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 849161526:
0.0%

Covered Lines:
2

Relevant Lines:
2

💛  - Coveralls


Flow Types

Goal
With a flow type, an abstract flow can be defined and instantiated multiple times. Similar flows can be instantiated using parametrization. Flow types can be nested, which allows reusage of mechanics.
Use Cases
Everything which can run multiple times at the same time:

A game mode
A mechanic of a game mode which is a building block for concrete game modes (for example: flag mechanics is used by multiple game modes)
A weapon mechanics
A mechanic of a weapon which is a building block for concrete weapons
A player
A team
A hardware device which exists multiple times
An identical or similar room which exists multiple times on a map
An IoT device which exists multiple times
...

Specification

Flow types can be represented as JSON and can be imported from a JSON file and exported to a JSON file
Flow types contains:

Virtual entity instances
Virtual relation instances
Specific entity instances (with a specific UUID or path which is known at design time - usually well known singletons)
Named entity instances (the entity instance is not known at design time but provided at instantiation)
Another flow types (which allows building complex scenarios with abstract sub flows)

Flows can be instantiated from a flow type multiple times, because the actual UUIDs of the resulting entity instances are generated at instantiation time
Immediate UUIDs

Virtual entity instances have an immediate UUID
Virtual relation instances connects virtual entity instances (and uses the immediate UUIDs of the outbound + inbound virtual entity instances)

Dynamic Instantiation

Flow type parameters

Flow types can define named parameters
The value of the properties of the virtual entity instances and virtual relation instances can use named parameters
At instantiation of a flow from a flow type, the value of the named parameters are replaced by the provided values

Flow type instances

Flow types can define named entity instances
The UUIDs of virtual entity instances can use an entity instance name
At instantiation of a flow from a flow type, the UUIDs of the named entity instances are replaced by the provided entity instances

Tasks

[x] Import a flow type from JSON
[x] Export a flow type to JSON
[x] Create a new flow type
[x] Delete a flow type
[ ] Update a flow type

[ ] Add a virtual entity instance to a flow type
[ ] Remove a virtual entity instance to a flow type
[ ] Add a virtual relation instance to a flow type
[ ] Remove a virtual relation instance to a flow type

[x] Create a flow (instance) from a flow type

[x] Replace the immediate UUIDs in virtual entity instances and virtual relation instances
[ ] Replace the named parameters
[ ] Replace the named entity instance by the provided concrete entity instance
[ ] Create the flows for the nested flow types

[x] Extend Plugin API

[x] FlowTypeProvider

[x] ChangeLog
[ ] Documentation
[x] Tests

Mostly done in #58. The remaining task will follow in separate pull requests.


Add Dockerfile for IPM

I have created a Dockerifle for IPM. I use it to setup a bundle IRI, IPM and other tools.
See https://github.com/ixidion/iota-docker
There is also an automated docker build: https://hub.docker.com/r/ixidion/ipm/

Was just about to create a Dockerfile for this only to be pleasantly surprised that someone had already created a PR for it just hours beforehand.
One slight improvement you might like to consider is changing the installation method to src rather than direct from NPM.  This way people can easily build a container with the latest code from master rather than waiting for a release to be pushed to NPM.  Also, it allows the maintainer to have images automatically built and tagged in Dockerhub as soon as code is tagged in Github.
Something like the following:
COPY . /usr/src/ipm
WORKDIR /usr/src/ipm
RUN npm install -g .

This results in an image similar in size to your original too so there is not real downside here.


CLI PoC using Click and OpenAPI Tools

PR for issue #1819
What is being addressed
This is a minimal POC of a CLI client for TRE. It is written in Python and uses autogenerated API client which has been created from the published OpenAPI spec (aka Swagger).
The generator used was:
OpenAPI tools generator
How is this addressed

It was found we could not use the Azure CLI extension as a way to provide the functionality required, so a standalone Python app was created
Click provides the framework for the command structure, arguments

includes client sdk generation for multiple languages. focuses on Python. Addresses #1820


[CT-1753] [Bug] Allow using agate 1.7.1 due to serious vulnerability in future

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
It has been recently found that the future package has a serious vulnerability and can lead to a denial of service (see details here https://nvd.nist.gov/vuln/detail/CVE-2022-40899). The current version of dbt-core is indirectly depended on it. The current version of dbt-core specifies the dependency on the agate package to be constrained: "agate>=1.6,<1.7.1" but agate <1.7.1 depended on the version parsedatetime that in its turn depended on future. The future repository has been dead since 2019 (latest release) and parsedatetime dropped the dependency on it: https://github.com/bear/parsedatetime/releases/tag/v2.5. agate reacted to that and also updated its version to 1.7.1 to use the latest version of parsedatetime without the future dependency: https://github.com/wireservice/agate/commit/52198daae198389649a44deb0ec2d1d41f6720c1.
Please, update your dependency on agate to allow version 1.7.1 and by doing so get rid of the dependency on future.
Expected Behavior
The dependency on agate is updated to allow version 1.7.1.
Steps To Reproduce
.
Relevant log output
No response
Environment
- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?
No response
Additional Context
No response

@piankris Thanks for flagging this. It looks like we have an automated PR already open to bump the upper bound: https://github.com/dbt-labs/dbt-core/pull/6522
By merging to main, we would be set up to include that in the next minor version release v1.4. We should take a look at the vulnerability to understand if we should also backport this version bump to older releases (v1.0-1.3), and put out new patch releases accordingly.
(We have the upper bound in place because, historically, new patch releases of agate have resulted in unexpected breaking changes for dbt-core users.)

@colin-rogers-dbt makes a fair point: we should just change this to a fixed version pin (==) for clarity. agate doesn't update often, and the two recent patches were just for Python version compatibility + this security vulnerability.
Potentially worth revisiting ripping out agate entirely (https://github.com/dbt-labs/dbt-core/issues/3413).

We've updated to supporting newer patch releases of agate:
https://github.com/dbt-labs/dbt-core/blob/9836f7bdef00b7cb912ad88ab1bbbfbd4dc4b312/core/setup.py#L52
That will be included in v1.6

@jtcohen6 You can safely bump the upper bound of agate  to <1.7.2 because version 1.7.1 has a minimum of changes https://github.com/wireservice/agate/compare/1.7.0...1.7.1 but it fixes parsedatetimes pinning


Create Scripture Reference Selector

Create a Scripture Reference Selector component (I think there is an Open Components Ecosystem one going around... Or you can start from the one from the POC. Also see Scripture Utils. Or make your own from scratch!)
In the past, Ian made this design.

Depends on #39

If it helps SF has a partial port from C# to TS of the BCV utils.

This document holds the research done so far about what the current Libpalaso Book Chapter Verse control does.


bug: Ionicon not appearing with button-clear

Type: bug
Ionic Version: 1.x
Platform: all
I have the following HTML markup:
<button class="icon ion-social-twitter button button-clear"></button>
With that markup, the ionicon does not appear. After debugging I noticed that in ionic.css:8906 there is the following rule:
.button-clear.button-clear {     border-color: transparent;     background: none;     box-shadow: none;     color: transparent; }
It is repeating the class name twice; and particularly the color property is hiding the ionicon.
In _mixins.scss:25 is where this CSS is sourced, combining the .button-clear class twice and making the color property transparent.

Mine css file in line ionic.css:8880 is
.button-clear.button-clear {
    border-color: transparent;
    background: none;
    box-shadow: none;
    color: #b2b2b2;
}

I don't have idea why the color in your css file is transparent

@amrography Which version of Ionic are you using? You can see here https://github.com/driftyco/ionic/blob/master/release/css/ionic.css that line 8880 is not .button-clear.button-clear. Rather line 8906 is referencing the rule I discussed above with color: transparent.

Hello, thanks for opening an issue with us! @smrubin and @amrography would you all mind telling me what version of Ionic you are using? Thanks for using Ionic!

Ionic Framework Version: 1.3.1
Ionic CLI Version: 1.7.15
Ionic App Lib Version: 0.7.2
OS: Windows 8.1
Node Version: v4.3.2

Ionic Framework Version: 1.3.0
Ionic CLI Version: 2.0.0-beta.25
Ionic App Lib Version: 2.0.0-beta.15
But my project still written in v1.x

+1

having same issue.
ionic version 1.7.17, but having this problem for 2 or 3 minor versions.

Same here. I wonder if this is dependent on the version of sass being used to compile the assets.

This issue was moved to driftyco/ionic-v1#126


Consider reuse of routeUrlTemplates in UrlExtensions

Per discussion with @scottbommarito in #5138, there's some refactoring that we could do in UrlExtensions for code reuse and possibly performance.
Options:

Shared helper between Url.Package and Url.PackageRegistrationTemplate (and similar APIs)
Static cache of RouteUrlTemplate, and use of it by Url.Package (and simliar APIs)

Closing due to priority of refactoring


GH-39769: [C++][Device] Fix Importing nested and string types for DeviceArray

Rationale for this change
In my testing with libcudf and other GPU data, I discovered a deficiency in ImportDeviceArray and thus ImportDeviceRecordBatch where the device type and memory manager aren't propagated to child importers and it fails to import offset-based types such as strings.

What changes are included in this PR?
These are relatively easily handled by first ensuring that ImportChild propagates the device_type and memory manager from the parent. Then for importing offset based values we merely need to use the memory manager to copy the final offset value to the CPU to use for the buffer size computation.
This will work for any device which has implemented CopyBufferTo/From

Are these changes tested?
A new test is added to test these situations.

Closes: #39769

@pitrou I'll add explicit CUDA based tests for the device array interface as a separate PR for https://github.com/apache/arrow/issues/39786#issuecomment-1908321452


expend the multi-band prediction to LPCNet

Hi, thanks for sharing your pretty good projects.
Do you have any plan to extend the multi-band prediction to LPCNet? Which may be some different fromthis projects, like multi band linear prediction etc.
https://arxiv.org/pdf/2005.05551.pdf

Hi. Thank you for your feature request.
This repository focuses on the GAN-based models so LPCnet is out of scope.
If I have the motivation, I may create a new repository.


Support (or document non-support) for Fragments

https://github.com/reactjs/reactjs.org/pull/345
React is adding a top-level React.Fragment export that transpiles to JSX as:
<>

Stuff

Things

</>

React.createElement(React.Fragment, {}, ...)

Would Preact be able to support fragments or provide some type of fallback?

https://github.com/developit/preact/issues/939

#929. I might be working on something.

They introduces  component also. In some cases (e.g. old eslint rules) its more preferrable...

If you want to use Fragment faked out for now, just do this:
React.Fragment = 'x-fragment';

Is lack of support for Fragment why we see <undefined> elements in output?

Would reassigning React.Fragment to 'x-fragment' be needed in the component that makes use of Fragment, and still result in extraneous custom elements in the DOM? I.e.
import React, { Fragment } from 'react'
React.Fragment = 'x-fragment'

@developit any estimate on this feature?

What is the status of this @developit  ?

Right now we just have the hack I posted. Fragment support requires a complete re-architecture of Preact, which I've been working on.  I will be making that work public soon.

@developit Any to help out with that? I'd love to get involved 🎉

@marvinhagemeister I just added you as a contributor here. Ping me on slack!

Just got contributor access and went through a few minor PRs to get started. Implementing Fragments shouldn't be that hard. I did a preview implementation for my preact-server renderer here https://github.com/marvinhagemeister/preact-server-renderer/pull/14/files . Basically a Fragment is a plain component which is treated differently at the render phase.
Before we can tackle it there are a few tasks, which will make adding them much easier:

get dependencies up to date
update to babel 7 because of <>foo</> jsx tags. (Fragments aren't much fun without them)
actually implement support for fragments.

I'm currently working on the first to and hopefully we can tackle point 3 soon 🎉

@marvinhagemeister nice work! but I personally feel that we could skip 2. for this fix if possible. I really hope that this fix could be in place before babel@7 enters the playing field, since it's still in beta

I concur with @phun-ky. In my projects we're not using React.Fragment often, but only sporadically where it aids in getting a simpler (flex) layout (ie. preventing extra wrapping). In those few instances, using <React.Fragment> is preferred as it makes more explicit what's going on.

Nice one @marvinhagemeister.  +1 on bypassing point 2. It's not a showstopper after a bit of destructuring.
import React, { Fragment } from 'react'

<Fragment>
  ...
</Fragment>

@marvinhagemeister what’s the progress on this? Is there any way I can help out?

@georgiemathews We do have Fragments working in a private branch, but we haven't had the time to make it work with hydration yet.

@marvinhagemeister  pretty excited for this - when do you think that this will merge?

@prakashsanker Progress can be tracked here: #1080 🎉

I'm able to achieve the desired effect by returning an array of elements.
Here's a simple example of an HTML definition list:
export default class Glossary extends Component {
  state = {
    glossary: [
      {term: 'HTML', description: 'Hypertext Markup Language'},
      {term: 'JS', description: 'JavaScript'},
      {term: 'CSS', description: 'Cascading Style Sheet'}
    ]
  };
  render({ }, { glossary }) {
    return (

        { glossary.map( g => (
          [
{g.term}
,
{g.description}
 ] // Here is the magic
        )) }

    );
  }
}

HTML output:

HTML

Hypertext Markup Language

JS

JavaScript

CSS

Cascading Style Sheet

Working demo here

@andrewkesper that works if you are inside a JSX.Element. What fragments explicitly allow is something else: returning "an array" directly from render(), so that you don't need to have a single root element on components (at least non that ends up in the DOM).

Could we make a bootleg Fragment component like this:
import React from 'react'

const Fragment = ({ children }) => React.Children.toArray(children)

export default Fragment

The possible downside is that it will auto-assign the key prop to each element. But you essentially get what Fragment does - no containing element. Any thoughts?

No, current preact expects a DOM node per vnode. This is not true for Fragments where the whole point of them is to not render anything into the DOM. So this is not easily doable (if at all) with the current architecture.
That said we have merged the PR for Fragments into our development repo last week. Fragments will be part of the next major release🎉
It is not available to the public yet and we don't have a release estimate for now. It's progressing nicely and we are currently working through an ever shrinking number of failing test cases and ensuring that all known bugs in the next version are fixed.

@marvinhagemeister do you know when the new version of Preact with Fragments will be released?

https://twitter.com/marvinhagemeist/status/1056229900158451712

This workaround is closer to React.Fragment and will keep your project compatible with React:
import React from 'react';
import pure from 'recompose/pure';
const Fragment = React.Fragment || pure(({children}) => children);

There's a bug in preact witch will prevent the rendering of the remaining parts of an children-arrays, if they contain a null value.

@andidevi Do you have a simple test-case or snippet that we can use to reproduce the issue you are experiencing?

So... What's the current status on this? I am currently looking at which library to choose - and I'd rather choose Preact, due to it's size.

We're getting close to a release, but as with everything the last few percents are the hardest. We basically have 1 bug left and need to get compat ready.

Very excited about this :)

I've created a small babel plugin to add support for React.Fragment. What it does is simply to remove the React.Fragment element. I've got it working with material-ui/icons. I'll upload it to npm if it's wanted, but now you can use by reference to GH. I've written a readme at https://github.com/kontrollanten/babel-plugin-preact-fragment

Fragments are implemented in #1302 (will be available in an alpha release pretty soon)

Any idea when this will be out of alpha?

@andyfurniss4 At this point we can't give a specific timeframe on when we'll be out of alpha. We'll likely move to beta when Fragments are rock solid 👍

We have a project written in Preact that is referencing a component from another library that does not render at all on first render (it will appear if I force a rerender)
const TheComponent = React.forwardRef((props, ref) => {
  const { ...rest } = props;

  return (

});

export default TheComponent;

Is this a known issue with Preact X (which we are now on! 🎉 )
What is the most reliable work-around for this right now? I've tried adding React.Fragment = 'x-fragment' at the top of the referencing file, but it didn't change anything.

@jessicabyrne The issue you are describing may not be related at all to Fragments. Can you open a new one issue where we can get to the bottom of it together? Maybe we can even reproduce the issue in a codesandbox.

@marvinhagemeister I'm convinced it's to do with Fragments after doing some more investigating. If I change the referenced code to use a div instead, the component renders fine. I did open a new issue though, we can move the conversation there :)


Uncaught TypeError: Cannot read property 'body' of null

This error happened directly after installing the package from the packages install in Atom
Atom Version: 1.1.0
System: Mac OS X 10.11
Thrown From: cdnjs-atom-extension package, v1.5.2
Stack Trace
Uncaught TypeError: Cannot read property 'body' of null
At ~/.atom/packages/cdnjs/lib/cdnjs-view.coffee:49

TypeError: Cannot read property 'body' of null
  at ~/.atom/packages/cdnjs/lib/cdnjs-view.coffee:47:8
  at Request.callback (~/.atom/packages/cdnjs/node_modules/superagent/lib/node/index.js:785:12)
  at Stream.<anonymous> (~/.atom/packages/cdnjs/node_modules/superagent/lib/node/index.js:990:12)
  at emitNone (events.js:72:20)
  at Stream.emit (events.js:166:7)
  at Unzip.<anonymous> (~/.atom/packages/cdnjs/node_modules/superagent/lib/node/utils.js:108:12)
  at emitNone (events.js:72:20)
  at Unzip.emit (events.js:166:7)
  at endReadableNT (_stream_readable.js:889:12)
  at doNTCallback2 (node.js:438:9)
  at process._tickCallback (node.js:352:17)

Commands
     -3:56 core:backspace (atom-text-editor.editor.mini.is-focused)
     -3:55.8.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -3:55.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -3:55.3.0 command-palette:toggle (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -3:51.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -3:51.9.0 settings-view:view-installed-packages (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -2:44 core:backspace (atom-text-editor.editor.is-focused)
     -2:42.5.0 core:save (atom-text-editor.editor.is-focused)
     -2:28.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -2:01.9.0 core:close (atom-text-editor.editor.is-focused)
     -0:55.7.0 symbols-view:toggle-file-symbols (atom-text-editor.editor.mini.is-focused)
     -0:52.5.0 command-palette:toggle (atom-text-editor.editor.is-focused)
     -0:49.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:49.5.0 settings-view:view-installed-packages (atom-text-editor.editor)
     -0:23.4.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -0:23 core:copy (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "one-dark-syntax"
    ]
  }
}

Installed Packages
# User
cdnjs, v1.5.0
emmet, v2.3.13
linter, v1.10.0
linter-jscs, v3.2.0
linter-jshint, v1.2.1
svn, v0.0.8

# Dev
No dev packages

Thanks for the excellent pull request and sorry for never getting back to you.
This most likely happened due to the API server being down at the time.
I will have to wrap the network requests such that they fail more gracefully.


Parser should return an error instead of panicking on unsupported language versions

Currently panicking kills the LSP process calling it.
Reported by @antico5

Will look into this next, since it is impacting integrations.


Update github action versions

(DIS-2963)

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

Project coverage is 86.40%. Comparing base (aeb04b9) to head (9e8d065).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   86.40%   86.40%
=======================================
  Files          19       19
  Lines        1265     1265
=======================================
  Hits         1093     1093
  Misses        172      172

Flag
Coverage Δ

unittests
86.40% <ø> (ø)

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

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


Add conda-forge distribution to docs

As of yesterday, the PyAV binaries are available on conda-forge on all platforms. Do you want to include this in the docs @mikeboers ?
Installation is done as follows:
conda install av -c conda-forge

I've had Conda floating around in the GitHub issues for a long time. I want to be convinced. I honestly don't have the time/interest in spending forever learning about it on my own (I mean... I do have the interest, but not for the foreseeable future).
Do you happen to have a recommendation for something that summarizes the awesome of it in this case?

I think I finally get it, and while I don't 100% believe it is the best solution, it seems like a pretty great one. Enough to at least include in the docs. ;)

Tell me what you think of https://github.com/mikeboers/PyAV/tree/docs-conda#pyav and https://github.com/mikeboers/PyAV/blob/docs-conda/docs/installation.rst#conda

I pushed it to master, and updated the docs on RTD.
Cheers, everyone!


Collapsible categories (packages) in docs

Currently, the sidebar is quite long, I think a tad too long. KitDocs does not provide the means to have a collapsible sidebar, so there's some effort involved.

I propose an alternative solution where packages are given tabs on the top-bar:

Here, overview corresponds to the current learn tab of the left sidebar.
Motivation:

Makes it easy to see the overall structure of the docs (and threlte) and to jump between packages
Declutters the sidebar without the need for accordion-style collapsible entries
Makes it feasible to put the page navigation inside the left side-bar under the corresponding page, creating space for additional features, like an eventual AI chatbot


Problem with Custom Transformers Installation - No module named 'setuptools_rust'

Following through the instructions in the repo, there seems to be some problem with the installation of the custom transformers package with the issue :
No module named 'setuptools_rust'
System configs :
OS : Ubuntu 22.04 LTS
The log produced :
`...
Installed /home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/transformers-4.3.2-py3.6.egg
Processing dependencies for transformers==4.3.2
Searching for tokenizers<0.11,>=0.10.1
Reading https://pypi.org/simple/tokenizers/
/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/pkg_resources/init.py:119: PkgResourcesDeprecationWarning:  is an invalid version and will not be supported in a future release
PkgResourcesDeprecationWarning,
Downloading https://files.pythonhosted.org/packages/48/2b/b99184cacb1a743edc18290e9127d1b0e658c0c46f2ab5290b27fe865ff4/tokenizers-0.10.3.tar.gz#sha256=1a5d3b596c6d3a237e1ad7f46c472d467b0246be7fd1a364f12576eb8db8f7e6
Best match: tokenizers 0.10.3
Processing tokenizers-0.10.3.tar.gz
Writing /tmp/easy_install-yusrqbr4/tokenizers-0.10.3/setup.cfg
Running tokenizers-0.10.3/setup.py -q bdist_egg --dist-dir /tmp/easy_install-yusrqbr4/tokenizers-0.10.3/egg-dist-tmp-3955d72l
Traceback (most recent call last):
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 156, in save_modules
yield saved
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
yield
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 259, in run_setup
_execfile(setup_script, ns)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 46, in _execfile
exec(code, globals, locals)
File "/tmp/easy_install-yusrqbr4/tokenizers-0.10.3/setup.py", line 2, in
#
ModuleNotFoundError: No module named 'setuptools_rust'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "setup.py", line 312, in
cmdclass={"deps_table_update": DepsTableUpdateCommand},
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/usr/local/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/local/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/usr/local/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/install.py", line 74, in run
self.do_egg_install()
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/install.py", line 124, in do_egg_install
cmd.run(show_deprecation=False)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 414, in run
self.easy_install(spec, not self.no_deps)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 656, in easy_install
return self.install_item(None, spec, tmpdir, deps, True)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 703, in install_item
self.process_distribution(spec, dist, deps)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 751, in process_distribution
[requirement], self.local_index, self.easy_install
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/pkg_resources/init.py", line 773, in resolve
replace_conflicting=replace_conflicting
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/pkg_resources/init.py", line 1056, in best_match
return self.obtain(req, installer)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/pkg_resources/init.py", line 1068, in obtain
return installer(requirement)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 675, in easy_install
return self.install_item(spec, dist.location, tmpdir, deps)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 701, in install_item
dists = self.install_eggs(spec, download, tmpdir)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 896, in install_eggs
return self.build_and_install(setup_script, setup_base)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1168, in build_and_install
self.run_setup(setup_script, setup_base, args)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1152, in run_setup
run_setup(setup_script, args)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 262, in run_setup
raise
File "/usr/local/lib/python3.6/contextlib.py", line 99, in exit
self.gen.throw(type, value, traceback)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
yield
File "/usr/local/lib/python3.6/contextlib.py", line 99, in exit
self.gen.throw(type, value, traceback)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 169, in save_modules
saved_exc.resume()
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 143, in resume
raise exc.with_traceback(self._tb)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 156, in save_modules
yield saved
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
yield
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 259, in run_setup
_execfile(setup_script, ns)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 46, in _execfile
exec(code, globals, locals)
File "/tmp/easy_install-yusrqbr4/tokenizers-0.10.3/setup.py", line 2, in
#
ModuleNotFoundError: No module named 'setuptools_rust'`
Any help with this would be highly appreciated !!!

I tried installing setuptools_rust and the rust compiler - and, after running the command python setup.py install, there seems to be some dependency issue with the numpy, as the best match for the numpy version is 1.24.3 , which is incompatible with Python 3.6.8(and the following message is shown) :
Extracting transformers-4.3.2-py3.6.egg to /home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages
transformers 4.3.2 is already the active version in easy-install.pth
Installing transformers-cli script to /home/ysriv/PycharmProjects/Intern-YANMTT/venv/bin
Installed /home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/transformers-4.3.2-py3.6.egg
Processing dependencies for transformers==4.3.2
Searching for numpy>=1.17
Reading https://pypi.org/simple/numpy/
/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/pkg_resources/init.py:119: PkgResourcesDeprecationWarning:  is an invalid version and will not be supported in a future release
PkgResourcesDeprecationWarning,
Downloading https://files.pythonhosted.org/packages/2c/d4/590ae7df5044465cc9fa2db152ae12468694d62d952b1528ecff328ef7fc/numpy-1.24.3.tar.gz#sha256=ab344f1bf21f140adab8e47fdbc7c35a477dc01408791f8ba00d018dd0bc5155
Best match: numpy 1.24.3
Processing numpy-1.24.3.tar.gz
Writing /tmp/easy_install-lf_xqdl_/numpy-1.24.3/setup.cfg
Running numpy-1.24.3/setup.py -q bdist_egg --dist-dir /tmp/easy_install-lf_xqdl_/numpy-1.24.3/egg-dist-tmp-e4mrbht4
Traceback (most recent call last):
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 156, in save_modules
yield saved
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
yield
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 259, in run_setup
_execfile(setup_script, ns)
File "/home/ysriv/PycharmProjects/Intern-YANMTT/venv/lib/python3.6/site-packages/setuptools/sandbox.py", line 46, in execfile
exec(code, globals, locals)
File "/tmp/easy_install-lf_xqdl/numpy-1.24.3/setup.py", line 20, in
1. Change the version in init.py, setup.py as well as docs/source/conf.py. Remove the master from the links in
RuntimeError: Python version >= 3.8 required.
During handling of the above exception, another exception occurred ....(Runtime Error Python version >= 3.8 required)
Is the Numpy version be same as that in the requirements file(1.18.5) and how do I make sure that the correct version gets installed, not the incompatible one?


Added pivot documentation

This documentation has been missing for a long time. I wouldn't have known this function existed if not for other people having used it.


Update public documentation with juju 3.4

Context
Based on the discussion in https://github.com/canonical/bundle-kubeflow/issues/940, we want to make sure the public documentation for Charmed Kubeflow shows the right version of juju to use.
What needs to get done

Go into charmed-kubeflow.io and check for places where juju 3 is mentioned
Make sure each entry mentions the support for juju 3.4 for CKF 1.8
Remove any traces of juju 3.1 and/or 3.5

Definition of Done
Public documentation in charmed-kubeflow.io does not make any reference to an unsupported version of juju.

The most important guides that should be updated are:

Upgrade 1.7 -> 1.8
Get started

Updated the above plus:

Deploy Charmed Kubeflow to EKS | Documentation | Charmed Kubeflow
Deploy Charmed Kubeflow to AKS | Documentation | Charmed Kubeflow


fix bridge teardown logic

I think the upgrade to rtnetlink broke the connected interfaces detection.
I added a test to ensure it works now correctly.
Signed-off-by: Paul Holzinger<EMAIL_ADDRESS>

lgtm

/lgtm


Skip macro-expanded code in the playground transform.

Playgrounds cannot display any macro expansions anyway and the @Observable macro can generate instrumentations that don't typecheck and/or reference missing functions.
rdar://112122752

@swift-ci test


Ubuntu 21.10 wget URL not found!

$ wget https://packages.microsoft.com/config/ubuntu/21.10/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
--2021-11-10 16:31:10--  https://packages.microsoft.com/config/ubuntu/21.10/packages-microsoft-prod.deb
Resolving packages.microsoft.com (packages.microsoft.com)... <IP_ADDRESS>
Connecting to packages.microsoft.com (packages.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-11-10 16:31:10 ERROR 404: Not Found.

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

ID: 80707602-f283-e796-d3b8-3287fbc011dc
Version Independent ID: 1d732b15-9e64-633a-000c-ad96d9d3818a
Content: Install .NET on Ubuntu - .NET
Content Source: docs/core/install/linux-ubuntu.md
Product: dotnet
Technology: dotnet-install
GitHub Login: @adegeo
Microsoft Alias: adegeo

Tried a while ago and found out that its not even listed in Microsoft Packages Directory

Thank you for reporting this issue. The documentation is being updated. .NET packages haven't been released for Ubuntu 21.10 but are in progress. Using the 21.04 repository works just fine.

Duplicate of #26879

Thank you for reporting this issue. The documentation is being updated. .NET packages haven't been released for Ubuntu 21.10 but are in progress. Using the 21.04 repository works just fine.

Any ETA for 21.10?


Overflow assertion

Assert for overflow anywhere it's possible to actually overflow. Try to avoid overflowing if possible.

Before implementing anything, let's see how the Rust policy for integer overflowing evolves.

Some overflow can be avoided, see #11 but for overflows due to the user, we won't do more than what Rust is already doing (for now).


[Simplification] Remove sorting by container id

I have no idea why someone may want to sort containers by their id. Instead we can sort by name. The id column is not even shown. Will you accept a PR with removing sorting by id?

That would be great indeed, my containers ID have no meaning, they are generated randomly, it's the less useful information bit of the whole thing in my view, I wish I could display their real names or even the domains each container is tied to..

While IDs are randomly generated for Docker containers, I believe runc/machinectl unique container ID is still a value provided by the user. In which case viewing and sorting by ID still has value. The column may, of course, still be hidden in configuration if the user wishes. Closing for now


removeAll and deleteAll are missing from Map

What happened
Was trying to use deleteAll(['key1', 'key2', 'key3']) on a Map object but it noted that the method is undefined. On inspection it doesn't seem this method is on defined.
Version
Currently, the project is using Immutable 4.0.0-rc.9.
How to reproduce
Inspect the Map object and look for deleteAll or removeAll. Alternatively, try to create a Map and use the method on it.

@aktof just checked current (4.0.0-rc.9.) version in the browser, seems to work

@bohdanbirdie Thanks for getting back, will check and confirm.


User flow

It would be very useful to have a user flow in the platform, so as to navigate through all guides solved by a specific user.

It should be a way to filter by topic (instead of the "all VS followed" filter).


User login Issue

I am unable to open the site and yesterday I was not able to login with username:- admin and password:- demo

same problem occurs to me,i am also unable to login with username:admin and password:demo

The demo has been taken offline until further notice. Closing this as it does not pertain to the NetBox code base.

Hi Jeremy,
When will be the demo online. Please let us know.
Best Regards,
Pankaj | Sr. Software Engineer
Daffodil Software Ltd.
On Fri, Sep 30, 2016 at 6:47 PM, Jeremy Stretch<EMAIL_ADDRESS>wrote:

The demo has been taken offline until further notice. Closing this as it
does not pertain to the NetBox code base.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/585#issuecomment-250741765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIpyS4mxMYlrJwDLqencLY2JPvSi1YF6ks5qvQvdgaJpZM4KK94r
.


Optimization doesn't work

Hello, can you help me? I installed your library using composer, installed all libraries (optipng, etc.), wrote
$factory = new \ImageOptimizer\OptimizerFactory(array('ignore_errors' => false));
But file is not optimized.
I tried:
$filepath = 'Upload/'.$data['name'];
try {
$optimizer->optimize($filepath);
} catch (CommandNotFound $e) {
echo "string";
}
But 'echo "string";' doesn't appear on my screen.

How do you know the file is not optimized?

I tried to optimize with optipng using command line with, then i tried to optimize it using script. Size of the first file is less than second.

Same issue here and no error is shown or returned


Add token burn feature to FT contract

When creating token, the creator should have an option (a checkbox on UI) to check if he want to make the token burnable.

Resolved by this PR: https://github.com/lightsea90/near-ft/pull/2


Missing one more metrics category for storage account.

There is one metric category missing in the storage account diagnostic setting ARM template.
"category": "Capacity",

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

ID: b8f43189-3418-fd30-0528-550157d8366d
Version Independent ID: 049e3b0e-6f10-6985-c719-05fe43fc00b8
Content: Resource Manager template samples for diagnostic settings - Azure Monitor
Content Source: articles/azure-monitor/samples/resource-manager-diagnostic-settings.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@jude-chen Thanks a lot for bringing this to our notice, we will review the feedback and update the document accordingly.

@jude-chen Thanks a lot for bringing this to our notice, we will review the feedback and update the document accordingly.

@jude-chen Apologies for delay in getting back to the thread. Thanks again for bringing this to our notice, will create a work item and associated PR to update this document or any other relevant document , to incorporate the feedback you shared.
We will go ahead and close this issue for now, but will make sure to tag the PR to this thread. If you have any further feedback on the documentation, please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you

@jude-chen Apologies for delay in getting back to the thread. Thanks again for bringing this to our notice, will create a work item and associated PR to update this document or any other relevant document , to incorporate the feedback you shared.
We will go ahead and close this issue for now, but will make sure to tag the PR to this thread. If you have any further feedback on the documentation, please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


fix: only one child is reported for a process

Fixes #15

@remy, please take a look.

Waiting on changes as per comments on the code.

Waiting on changes as per comments on the code.

@remy, what comments on the code?
Could you, please, point out where are those comments?

For heaven's sake. Githubs UI for code reviews really isn't obvious. I posted the comment over a week ago, and returning now I see a tiny "pending" label. I've submitted the comments so you should be able to see them now (sorry about that)

@remy, I've made the requested changes, please take a look.

Sorry it's taken so long to answer this. But the pstree.remy module is designed to only get the sub-tree and not the main process. This is how it's used in nodemon too. This current PR thus adds an additional pid that isn't wanted in the list.
Sorry for wasting your time.

Sorry it's taken so long to answer this. But the pstree.remy module is designed to only get the sub-tree and not the main process. This is how it's used in nodemon too. This current PR thus adds an additional pid that isn't wanted in the list.

@remy, I don't get it. This change doesn't get the pid of the main process. It only gets the sub-tree.

@remy, I don't get it. This change doesn't get the pid of the main process. It only gets the sub-tree.

Actually, cross it. I see it.
But the fix is trivial.
And the purpose of the change is to get all children, in contrast to what current implementation does.
Do you mind if I make a fix you to not return the main process?

Apparently, there is some misunderstanding.
The purpose of this PR is to implement getting all children in cases, when some process in the chain has more than one child. Current implementation in the master doesn't do it, because it only remembers last parent. The proposed fix remembers all potential parents.
Returning the pid of the main process is unintentional side effect and it can be easily fixed.

Just trying to get it straight in my head (and I'm very careful about these low level changes because it has 100% affect on Mac and *nix users of nodemon).
The original test case you raised in #15 - this creates 2 sub-processes (off of bash). I'd expect pstree to return 2 pids.
I think you're talking about another test case where you have a sub-sub-process? Is that right?

Actually, it is the same test case: it doesn't matter what process is parent of two children: the main process or some intermediate process in the chain.
In fact, originally I reproduced it with npm-run-all, not bash. As far as I remember, if  some npm task containt npm-run-all, the tree is like this:
nodemon
 +- npm
      +- npm-run-all
           +- npm
           |    +- node
           +- npm
                +- node

The issue with the current implementation is that once it went along one branch, it cannot return up to switch to another branch. This is because it only remembers one parent.

I can't release this at the moment, local tests are failing (as I was worried they would - it's reporting half the number of processes found).
I'm investigating atm.

Live.


write a wrapper for go-tuf

While the end goal is to move the wrappers to the TUF implementations ( #9), including go-tuf in our early wrappers in this repo might make sense:

go-tuf is widely used
the two wrappers we have now are based on the same design so not likely to show new issues with test suite design
having coverage of both go-tuf and go-tuf-metadata would show how compatible they are (which is beneficial for go-tuf-metadata if it wants to replace current go-tuf at some point)

go-tuf in this issue refers to the old go-tuf version btw.

current go-tuf main will be easy -- just port the existing go-tuf-metadata
but it would be great to have a client for the go-tuf <= 0.7 implementation as well -- this would prove that the two have the same functionality

closing as there is too much obsolete stuff here: I'll file another one for maybe supporting go-tuf v1


'{controller}' placeholder does not work with open api spec

I am trying to generate multiple clients for each controller using the {controller}Service class name option:
nswag swagger2tsclient /Input:api-swagger/api-swagger.json /Output:src/app/api/api.ts /ClassName:{controller}Service /WrapDtoExceptions:true /TypeScriptVersion:2.0 /Template:Angular /HttpClass:HttpClient /DateTimeType:Date /GenerateClientClasses:true /GenerateClientInterfaces:true /ImportRequiredTypes:true /BaseUrlTokenName:API_BASE_URL /InjectionTokenType:InjectionToken /RxJsVersion:6.0 /UseSingletonProvider:true /ExcludedParameterNames:Authorisation

While I expect a client for each controller, it only generates one client called Service, which contains all operations across all endpoints.
The spec file looks like the following:

What is the structure of the OperationId? With the default operation name generator the operation id needs to be in the form "controller_method" in order that this actually works.

Thank you for pointing this out, the structure of operations did not include controller names - they only had method names.


Lewis vr helper issues

#3280

Fix if you disconnect & reconnect the controllers while in VR, the teleportation no longer works.
If a camera is already created no device orientation camera will be created
Ability to disable the vr fallback camera

I ll put in the few details tonight THX


release v2.2.x: bump to SDK v0.45.10, prepare changelog for v2.2.3 patch release

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

note: there's a minor unreleased changelog entry in this release line


DTS - update ec transition section

Signed-off-by: Tomasz Żyjewski<EMAIL_ADDRESS>

There are still TBD for links as we waiting on NovaCustom release v1.3.0 on NV4x testing report. After that we will be sure that hashes and links used in DTS to download firmware are correct.

There is no need to update video, last show how to verify DTS v1.0.x and that is enough. Merging.


Add napoleon

Coverage decreased (-9.8%) to 89.235% when pulling 940adc723ad45004ebdd85063c10d8e6747d6b09 on task/add_document into 2b7af9a7379487b635c5c924dc99034df564071b on master.


feat: support Bitgesell Core v0.1.12

Summary
Add support for release: https://github.com/BitgesellOfficial/bitgesell/releases/tag/0.1.12

closed via #4


[FLINK-11630] Triggers the termination of all running Tasks when shutting down TaskExecutor

What is the purpose of the change
Currently, the TaskExecutor does not properly wait for the termination of Tasks when terminating. This patch triggers the termination of all running Tasks when shutting down TaskExecutor.
Brief change log

Make Task#stopExecution returns a CompletableFuture
Make Task#cancelExecution returns a CompletableFuture
Call Task#cancelExecution when invoking TaskExecutor#onStop

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

Thanks for the quick response @tillrohrmann . My bad, will correct it soon :)

Have updated the PR, plz have a look if you have time :) @tillrohrmann

@kisimple
what is the status here?
do you plan/have time to work on this PR?
what do you think about suggested comments?

Hi @azagrebin many thanks for your review and very sorry for the late reply, I will address the comments in the next few days :)

Hi @kisimple, thanks for looking into it, any update here?

Hi @azagrebin Sorry for the delay, I have addressed your comments, and I haven't reproduced the original issue.

Highly appreciate your review :) @azagrebin I have addressed the comments.

@azagrebin I have triggered another build, it passed in my Travis account, but here failed again, the key output messages as below,
Cached flink dir /home/travis/flink_cache/36048/flink does not exist. Exiting build.
The command "./tools/travis_controller.sh misc" exited with 1.

Looks like Travis did not work properly?

@kisimple true, looks like Travis problem. Could you squash the empty commit to trigger it again?

@kisimple could you rebase on latest master and squash empty commits? it seems there has been a fix merged.

@kisimple
I agree with @tillrohrmann , it looks fragile to rely on taskSlotTable for querying incomplete tasks. Depending on when the Task.notifyFinalState is called, it can happen that some resources are still in use in Task and we release network concurrently. Although, it is not the case now but we can miss it in future if Task.notifyFinalState is moved somewhere else.
Instead of relying on taskSlotTable we can introduce another container (e.g. incompleteTasks) to keep undone tasks in TaskExecutor. The tasks can be added to incompleteTasks in TaskExecutor.submitTask when the task is created. We can also immediately add a callback to its close future with the task removing itself from incompleteTasks when is done. Finally we can use incompleteTasks instead of taskSlotTable in TaskExecutor.failTasks to query complete futures and wait for them.
Apart from other @tillrohrmann's comments, it seems we can simplify more and do all stopTaskExecutorServices after all tasks are completed.

@kisimple do you have time to address the comments?

@azagrebin Sorry for the late reaction, I got my hands full lately. I have addressed some comments :)


refactor: upgrade golang ci lint to 1.46.2

Signed-off-by: ankitm123<EMAIL_ADDRESS>

/approve


feat: Configurable operators for free text filtering in property filter

Description
This CR adds the ability to customize free text filtering operators for the Property Filter, just like every other property operator. The corresponding update has already been merged into collection-hooks: https://github.com/cloudscape-design/collection-hooks/commit/59dcd9cd5e46c492e13939e59505f229782c202d.
See: k6RfAb8hHR1t
How has this been tested?

Updated 2 pages in the dev app (general property filter hooks page, and token editor page) and confirmed both worked with the new feature as expected.
Ran unit, integ and motion tests.
Fully ran visual regression testing because I expected the token-editor page to be part of it, but since it's only the permutations page every one of the 144 tests passed.

Video of various interactions with free text filtering in the dev app:
https://github.com/cloudscape-design/components/assets/4647197/fadd9b3c-f8a9-45d3-bb71-07db40001d09

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates. ✅
Changes are backward-compatible if not indicated, see CONTRIBUTING.md. ✅
Changes do not include unsupported browser features, see CONTRIBUTING.md. ✅
Changes were manually tested for accessibility, see accessibility guidelines. ✅

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function. N/A

Testing

Changes are covered with new/existing unit tests? ✅
Changes are covered with new/existing integration tests? N/A

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Sorry it took me a couple days just for a text update, you know how AWS can get. 😅
New revision has rebase on latest main + documentation text updates on the new parameters.

Thank you for the contribution!


Add edit and document to the commands panel

Edit and document aren't available in the Commands panel yet

Closed by https://github.com/sourcegraph/jetbrains/pull/1302


Update views.py

Error - 'WSGIRequest' object has no attribute 'REQUEST' due to the usage of
self.request.REQUEST.get(name, '') in password_policies\views.py (line 110). Fix for the same.

Coverage decreased (-0.3%) to 78.07% when pulling 73a3a8135985e4d6b6ef8019ae846b8fa7521002 on cks333:patch-1 into 1aa31f7e353a33f909b9c6cf8a252a98ccab26c6 on tarak:master.

It is already fixed in #52


Adding a video link

Adding a video link

@marwaIDCxP : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @marwaIDCxP - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Justinha, I assume this is okay to merge, with your requested changes made? Thanks.

@Justinha, I assume this is okay to merge, with your requested changes made? Thanks.

Hi, all. @marwaIDCxP notified me in Teams that a new pull request in the private repo - https://github.com/MicrosoftDocs/azure-docs-pr/pull/142011 - replaces this PR. So, we'll close this pull request. I'll apply feedback from @justinha in the new PR. Then, @marwaIDCxP should sign off in the new PR for it to be auto-merged.

Hi, all. @marwaIDCxP notified me in Teams that a new pull request in the private repo - https://github.com/MicrosoftDocs/azure-docs-pr/pull/142011 - replaces this PR. So, we'll close this pull request. I'll apply feedback from @justinha in the new PR. Then, @marwaIDCxP should sign off in the new PR for it to be auto-merged.

Closed new PR in private repo per author @MicrosoftGuyJFlo

Closed new PR in private repo per author @MicrosoftGuyJFlo


Docs tweak for includes

To allow for include in the unified sites -

Commit 1 adds a snippet to install just the solid-client lib
Commit 2 adds comments in the index.rst so that we can include parts of the file in other files.

as in, include  the content from table-issues-help.rst file directly into the index.rst and then include sections of the index.rst  in other files?
In this case, we could - but in general, in the long run, I've found that having the smaller include files turn out way better.

OK, let's keep it this way then :)


feat: Add accessor for current session id

What does this PR do?
There are use cases (usually support use cases) where clients what to know the current session id without depending on the sessionStarted event. This provides that accessor.
refs: RUM-1962
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1810 (d2ccf9d) into develop (a21c278) will increase coverage by 0.05%.
The diff coverage is 20.00%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1810      +/-   ##
===========================================
+ Coverage    83.44%   83.49%   +0.05%
===========================================
  Files          466      466
  Lines        16375    16358      -17
  Branches      2455     2459       +4
===========================================
- Hits         13663    13657       -6
+ Misses        2047     2029      -18
- Partials       665      672       +7

Files
Coverage Δ

.../main/kotlin/com/datadog/android/rum/RumMonitor.kt
28.57% <ø> (ø)

.../android/rum/internal/monitor/DatadogRumMonitor.kt
84.73% <20.00%> (-1.20%)
:arrow_down:

... and 21 files with indirect coverage changes

@xgouchet  / @0xnm Replaced the accessor with an async callback.  Let me know what you think


Issue on V0.8.1 Impossible to uncheck boxes

Created based on user report from B.H. :+1:
USER_COMMENT= uncheck of the check ☑ boxes are not possible. Resetting a trip would be great. Thx
REPORT_ID=c512aa88-dbc1-434a-9c64-c1e64949c6ff
APP_VERSION_CODE=12
APP_VERSION_NAME=0.8.1
PACKAGE_NAME=com.nbossard.packlist
FILE_PATH=/data/user/0/com.nbossard.packlist/files
PHONE_MODEL=LG-D802
ANDROID_VERSION=6.0.1

Is it a trip that was created in a previous release of packlist ?
if possible which or if you don't remember provide creation date.

See issue #34 similar


Infinite loop when catchError used in conjunction with materialize

Current Behavior
Piping a stream to catchError then materialize starts an infinite loop
Reproduction
const letters = of('a', 'b', 13, 'd');
const upperCase = letters.pipe(map(x => x.toUpperCase()));
const materialized = upperCase.pipe(
  catchError((error, caught) => caught),
  materialize(),
);
materialized.subscribe(x => console.log(x));
// Logs indefinitely

https://stackblitz.com/edit/typescript-e9e2yb (I added a take(100) to avoid the browse to freeze)

Expected behavior
The log should be called 5 times with respective Notification (next, next, error, next, complete).
Environment

Runtime: Chrome / Firefox
RxJS: tested on 6.5.2 and 5.5.12

I don't believe this is a bug. When you return caught, you are asking the implementation of catchError to re-subscribe to the source observable and it will, of course, error again.

Thanks @cartant for your answer. You are right and I missed it in the doc https://rxjs.dev/api/operators/catchError.
I must admit that this behavior of catchError is not intuitive to me.
I would have guessed that catchError((error, caught) => caught) does a kind of bypass while it actually does a retry.


Segun portfolio

What does this pull request do?
merging my portfolio branch

What does this pull request do?
merging my portfolio branch

Looking awesome @segunajibola You could change the primary yellow color to match with your profile. 😎🤩

Alright bro, big thanks to you. i'll try fix that

changed the primary color


Release v2.5.9 potential Electron 26.1.0 bug

Appears Electron update from 25.3.2 to 26.1.0 has broken the app with release 2.5.9
https://github.com/LapsTimeOFF/DigiFlag_F1MV/blob/75d04d9f2f9bec684429d8d7d87116c12ba9f082/package.json

Issue exists on Ubuntu 22.04. Screenshot below.

This issue has been resolved with the updated v2.5.9

Confirmed is solved.  Thank you as always @TheBaconCat