Please mention any limitation in "Set the memory limit"

Many users have complained that "Set the memory limit" is not working in Linux containers.
https://github.com/microsoft/mssql-docker/issues/293
https://github.com/microsoft/mssql-docker/issues/517 , Please mention those limitation if any

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

ID: 9c0b1027-3982-e114-0230-c6bd9bd81346
Version Independent ID: 244740de-8817-1671-387d-970f8ee8dfcb
Content: Configure SQL Server settings on Linux - SQL Server
Content Source: docs/linux/sql-server-linux-configure-mssql-conf.md
Product: sql
Technology: linux
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@vibeeshan025 -- Vibeeshan, thank you for your feedback.  Please consider these resources:

DBA Stack Exchange
Stack Overflow

@VanMSFT -- Van, please look into this issue.

Hi @vibeeshan025! Thanks for submitting this issue. The limitation you referenced is in regards to Linux Containers on Windows. The reqs for SQL Server are listed here: https://docs.microsoft.com/sql/linux/sql-server-linux-setup?view=sql-server-ver15#system
We won't be adding this information to the mssql-conf page as it's not restricted to SQL Server. However, I'll check with the Product Team on whether there's an update regarding a fix for the LCOW issue. Thanks!
@vin-yu @tejasaks

Pinging the Product Team.

Hi @vibeeshan025 - Thank you for your patience. I confirmed that there's currently no update on the Linux Container on Windows memory bug. I'll go ahead and close this for now, but please let us know if you have any concerns.


Investigate (and possibly integrate) tox into the project.

During work on PR #59 , it was discovered that the make test that is ran locally on a developer's machine will never report full coverage due to a recent import change required in Django 2.0.
It looks like it is time to start using / integrate tox into the project to handle all the different Django and python versions that Travis CI is targeting.

I started by installing tox of course:
$ pip install tox
Collecting tox
  Downloading tox-2.9.1-py2.py3-none-any.whl (73kB)
    100% |████████████████████████████████| 81kB 1.4MB/s
Collecting pluggy<1.0,>=0.3.0 (from tox)
  Downloading pluggy-0.6.0.tar.gz
Collecting virtualenv>=1.11.2; python_version != "3.2" (from tox)
  Downloading virtualenv-15.1.0-py2.py3-none-any.whl (1.8MB)
    100% |████████████████████████████████| 1.8MB 692kB/s
Collecting py>=1.4.17 (from tox)
  Downloading py-1.5.2-py2.py3-none-any.whl (88kB)
    100% |████████████████████████████████| 92kB 5.1MB/s
Requirement already satisfied: six in /Users/purda/.virtualenvs/django-le/lib/python3.6/site-packages (from tox)
Building wheels for collected packages: pluggy
  Running setup.py bdist_wheel for pluggy ... done
  Stored in directory: /Users/purda/Library/Caches/pip/wheels/df/44/8e/e136760ae525eac46b3e3db643ef58ff1753177b5a722b0c96
Successfully built pluggy
Installing collected packages: pluggy, virtualenv, py, tox
Successfully installed pluggy-0.6.0 py-1.5.2 tox-2.9.1 virtualenv-15.1.0

Merged into develop.


Ramone/tools 1964

Added the Remix IDE section for compile and deploy a smart contract including accompanying screenshots.

Too far from main with many conflicts


Product timeline detailed visualization

[ ] Add link as 'View detail' in existing Product Timeline visualization to show detail
[ ] Show detailed visualization in popup as in Total Spending. In the place of countries show Product Categories

I assume that this feature will not be implemented, at this point, so closing.


[SLUS-20701] Scooby-Doo! Mystery Mayhem (USA)

When starting a new game, the cutscene freezes in Scooby doo Mystery Mayhem in the US version, in the European version this problem does not occur. Is there a way to fix a huge fps drop in one part of the game?

Interesting!
The opposite of what happens with shadow of the colossus. The pal version was kinda problematic while USA version worked like a charm
I doubt it's related to this issue, but mentioning it felt worth it

I forgot to mention, this is also a problem in opl

I just tested this game on the latest neutrino. Everything seems fine to me.
Can someone confirm this game works as expected?
Tested on a real ps2 with udpbd.


Make regression test for setSeed and the new r.plot syntax

See https://github.com/sys-bio/roadrunner/issues/300

I will write some unittests and improve documentation on this.

Regression tests in unittests and updated documentation.


Parsing errors

while checking multiline support i ran through all dbc files form https://github.com/commaai/opendbc
theres some Bu_ Parsing errors but a issue for thats already created. I removed duplicate errors that occur for the same reason. And also stuff like missing signals that actually dont exist in there or actual duplicates.
I also have to mention that on many of these i have no idea if the error is valid:
acura_ilx_2016_can_generated.dbc: line 153 und 154. Code is:

CM_ SG_ 304 "Seems to be platform-agnostic";
CM_ SG_ 316 "Should exist on Nidec";

Missing the Signal name. probably invalid;
acura_ilx_2016_nidec.dbc: line 180 and 181;

BO_TX_BU_ 768 : NEO,ADAS;
BO_TX_BU_ 769 : NEO,ADAS;

We dont support seperate define trasceivers yet. I dont know any case where thats relevant
bmw_e9x_e8x.dbc'

CM_ SG_ 408 ParkButtonSecond "Redundant buton. 0x1 = pressed;";
CM_ SG_ 408 SideButton "0x1 = pressed;";
CM_ SG_ 408 SportButtonPressed "0x1 = pressed;";

Something i feared with multiline support. Seemingly ";" can appear in a message. actually adding comment to the signal and then failing at a ";" only line.
chrysler_pacifica_2017_hybrid_generated.dbc

VAL_ 320 ACC_OFF_REQ 2 "PERMANENT" 1 "TEMPORARY" 0 "NONE"

Val table without ; error?
\chrysler_ram_dt_generated.dbc

CM_ "Generated from _stellantis_common.dbc"

Comment without ";" error?
FORD_CADS.dbc

BA_DEF_ SG_ "GenSigMissingSourceValue" INT 0 1e+09;

the 1e+09 style is unsupported
ford_lincoln_base_pt.dbc

VAL_TABLE_ DcacRdy_D_Stat 7 "NotUsed_2" 6 "NotUsed_1" 5 "Faulted" 4 "ProtectionTempearture" 3 "ProtectionOverload" 2 "ProtectionGfci" 1 "Active" 0 "Idle";

Literally every single val table fails parsing in this file. I suspect the same error that @Whitehouse112 fixed for the Val_Parsing. Maybe want to look into this too?
gm_global_a_powertrain_generated.dbc

VAL_ 501 ManualMode 1 "Active" 0 "Inactive"

";" missing at or near end of file; Error? (near in mazda_2017.dbc)
mazda_2017.dbc

BO_ 1277 NEW_MSG_10: 8 XXX
SG_ NEW_SIGNAL_3 : 31|8@0+ (1,0) [0|255] "" XXX
SG_ NEW_SIGNAL_2 : 15|8@0+ (1,0) [0|255] "" XXX
SG_ counter : 7|8@0+ (1,0) [0|255] "" XXX

BO_ 1275 2017_5: 8 XXX
SG_ counter : 4|5@0+ (1,0) [0|255] "" XXX

I suspect the fact that the message only contains numbers failing the regex?
tesla_radar_bosch_generated.dbc

CM_ BO_ 345 "Message sent every 20ms. Checksum : Sum of all first bytes + 0xc; place checksum in 4th octet";

Another ";" in a comment but worse as its not even directly followed by "
vw_mqb_2010.dbc

CM_ SG_ 1720 KBI_Reifenumfang_Sekundaer "Fahrzeuge mit unterschiedlichen Reifenumfängen Vorderachse / Hinterachse:

Primärachse: KBI_Reifenumfang
Sekundärachse: KBI_Reifenumfang_Sekundaer
";

Empty line in comment allowed?

things that should probably be fixed:
the comment fails are mostly due to trying generic multiline support which doesnt realy work for comments. Are all comments ended by "; or atleast by "   ;   then this could still be done seperatly in the comment parsing;
If not im not to sure about multiline support because currently the comment stuff works now it doesnt but other stuff has multiline support; On the other hand failing to parse comments is better than failing to parse other entries.

BO_TX_BU_ 769 : NEO,ADAS;

Can do at some point before the 2.0 release i guess would be best. Should probably just be added to the messages Transmitters? Duplication handling?

BA_DEF_ SG_ "GenSigMissingSourceValue" INT 0 1e+09;

Would need a fancy regex change that i cant do. neither can the AI Overlord ;)

VAL_TABLE_ DcacRdy_D_Stat 7 "NotUsed_2" 6 "NotUsed_1" 5 "Faulted" 4 "ProtectionTempearture" 3 "ProtectionOverload" 2 "ProtectionGfci" 1 "Active" 0 "Idle";
@Whitehouse112 could probably adjust the regex for this; Just like in the VAL_ parsing?

BO_ 1277 NEW_MSG_10: 8 XXX
SG_ NEW_SIGNAL_3 : 31|8@0+ (1,0) [0|255] "" XXX
SG_ NEW_SIGNAL_2 : 15|8@0+ (1,0) [0|255] "" XXX
SG_ counter : 7|8@0+ (1,0) [0|255] "" XXX

BO_ 1275 2017_5: 8 XXX
SG_ counter : 4|5@0+ (1,0) [0|255] "" XXX

Also a fancy regex change? This group ([a-zA-Z_][\w]*) probably expects atleast on letter. Not to sure though as i dont know why you cant just use [\w] alone. I do think that the name here is allowed. isnt it?

Hi,
It's Saturday so I'll quickly scratch the surface here.

On the other hand failing to parse comments is better than failing to parse other entries.

We may discuss about this but for us that would be a regression.
Generally speaking, finding complete and trustable DBC specification has been a mess so we followed the specifications you can find in project's home page. For some tags that spec states that final ; I'd compulsory. There are also clear limitations on message names and other identifiers. We, nevertheless, often double checked opening DBC with Vector CANdb++. Sometimes it was strict, sometimes it was loose and accepted minor syntax errors.
it may be worth checking all these errors with both documentation and CANdb++ and see what happens. I won't assume that those DBC are all strictly formatted.
Since our observed is named Strict we could also think about making behavior configurable, something like parsing mode: strict, loose, mute (where mute is current Silent observer).
A

@Adhara3
there are test for sientificNotation but only for FLOAT and it only works for float. Im not sure if it is allowed for int. In this case it might since its only e+. Im not sure. Spec is unclear.
for the comment stuff thats why i said multiline support is a poc. I can let the nextline provider handle general multiline/multidefiniton per line support and handle comments specially still as before. im just not sure if i should.
i could drop multidefinition per line support but thats also uncool. or if i see a ; in line i check for keyword after that but ill have to experiment some more.
The basic dilema is that the NextLine provider can not really have the info if a ; should be the splitter between two definitions in one line or just a ; like in a comment. The most probable solution atm would be not to split a line if the part behind ; is not a new keyword. but that would still leaf the empty line problem.
How would i do it if i had no code base: let each parser itself decide when its wants to stop reading and drop the newLineProvider
I know that many dbcs are flawed thats why i picked the points that in my opinions atleast seem to be reasonable and within spec in my second comment. I think these should all be within spec. im unable to verify with CANdb++ though.

I suspect the fact that the message only contains numbers failing the regex?

C_identifier: a valid C_identifier. C_identifiers have to start with
an alpha character or an underscore and may further consist of
alpha-numeric characters and underscores.
C_identifier = (alpha_char | '') {alpha_num_char | ''}
DBC_identifier: a C_identifier which doesn’t represent a DBC-Keyword.

From the spec an indenter should at least start with letter or _.
A

Was just thinking regarding to this:

Since our observed is named Strict we could also think about making behavior configurable, something like parsing mode: strict, loose, mute (where mute is current Silent observer).

I was first thingik you wanna swap the parser but i dont like that. however would it be possible to classify the pasing errors like a comment parsing error being => Info; a single for a val table not found like a warning and a signal or message error being critical. Kind of the same direction as your idea but might be a bit easier

@Adhara3 we checked the current code against some production dbc (so ones that are used in production systems and are parsed without error by the softwares we use.
From the parsing errors we observed i can say that only 2 things are currently an actual problem.

stuff like this appears sometimes:

BO_TX_BU_ 769 : NEO,ADAS;

Let me know if i should create a PR for this for 1.7 or later or not at all?

Stuff like this is really common:
VAL_TABLE_ DcacRdy_D_Stat 7 "NotUsed_2" 6 "NotUsed_1" 5 "Faulted" 4 "ProtectionTempearture" 3 "ProtectionOverload" 2 "ProtectionGfci" 1 "Active" 0 "Idle";

As i have no idea how to adjust the regex as whitehouse did in i would appreciate it if someone couuld fix this.
The testcase for it would be an adjustment of "ValueTableDefinitionIsParsedAndCallsBuilder" where you just remove the trailing space before the ';'
I actually found one single comment in our files with a line ending in ';'. No big deal though even tough it fails parsing.
As for the message with message name only with numbers and '_'. two of three parsers do parse it but it never appears in the production files so doesnt matter.
BA_DEF_ SG_ "GenSigMissingSourceValue" INT 0 1e+09;   Seems to be fully valid. parsed by all parsers. "Matlab, Goepel, python cantools, " But i dont need it as it doesnt appear in any of our files

If we go down this path the we should ignore de doc/spec at all and switch parsing target to parse what other parsers parse or provide mechanism to not be strict but keeping a strict mode.
If a parser is parsing a wrong syntax it is not doing a good job for me, it is allowing bad habits. I'm fine to allow loose parsing but it should be a user choice, we should be strict when possible. My 2 cents.

As far as i understand the spec literally and char can appear in a comment as long as it is in between "". This includes ; and also at line ends. the actual comment end is something like this (regex style): "\s*;
so " markes the end of the comment text then it can have zero or more spaces before a final; Just because ; is at a line end doesnt neccesarily mean the comment ends. But anyway this is such an edge case...

If we go down this path the we should ignore de doc/spec at all and switch parsing target to parse what other parsers parse or provide mechanism to not be strict but keeping a strict mode.
If a parser is parsing a wrong syntax it is not doing a good job for me, it is allowing bad habits. I'm fine to allow loose parsing but it should be a user choice, we should be strict when possible. My 2 cents.

As far as i understand the spec literally and char can appear in a comment as long as it is in between "". This includes ; and also at line ends. the actual comment end is something like this (regex style): "\s*; so " markes the end of the comment text then it can have zero or more spaces before a final; Just because ; is at a line end doesnt neccesarily mean the comment ends. But anyway this is such an edge case...

Sorry I misunderstood the issue.
in CANdb++ both VAL_TABLE_ and CM_ must end with a ;. In case of CM_ the ; must follow the body closing " but this is important for supporting multiline *the fact that we can assume that the final ; is there otherwise we fail).
The comment body text having a ; or event having a line ending with ; must be supported. Maybe it's rare, but must be supported anyway.
Anyway, I'm starting to have some ideas, I need to write code and see.
Cheers

Anyway, I'm starting to have some ideas, I need to write code and see.

You can still check out my multiline code but it doesnt go for line ends but instead line starts. but it works. If we keep the current parser we could change comment to look for "; for line end instead of only ;. that would fix that.

Anyway, I'm starting to have some ideas, I need to write code and see.

You can still check out my multiline code but it doesnt go for line ends but instead line starts. but it works. If we keep the current parser we could change comment to look for "; for line end instead of only ;. that would fix that.

I truly believe we should abandon the concept of INextLineProvider. The parser should not be involved in anthing related to line
Anyway, I need to write down my design and see if I really like the design, we'll see. Let me think about it, then I'll list here 2 or 3 otpions I have in mind.
Cheers

Dear all,
I close this issue to avoid noise as the two main problems highlighted here are being addressed in the scope other issues (some completed, some ongoing).
Thanks for your effort
A


collections_remove_stale: Failed deleting collection

Just installed 2.9.2.  Still getting these:  Message: collections_remove_stale: Failed deleting collection (name "ip", key "x.x.x.x_c4cec15ef22e6f8b45b90bbea4b5e887cb5c72a3"): Internal error
Apache-Error: [file "apache2_util.c"] [line 271] [level 3] [client x.x.x.x]
Centos 7, compiled locally on machine.

Please check #576


MSG Buffalo Feed Missing Gotham Integration

Hey, was toying around with this and noticed that it does not seem to have the MSG Buffalo feed integrated. Was looking at your code and noticed the section below with the channel mappings in the Gotham Handler.ts file.
const CHANNEL_MAP = {
MSG: '057E6429-044F-49E6-9E97-64D617B4D3CD',
MSG2: 'F1DA3786-A8A2-4C3D-B18E-F400F9C6EE0B',
MSGSN: '6D250945-BB55-44D4-A5A9-3DF45DBE134E',
MSGSN2: '0135EBDF-184F-41FA-B36C-46CDA4FC9B33',
YES: 'BD50D13C-CC01-4518-AD42-B3EFACF1DBF5',
} as const;
The MSG Buffalo feed from what I can tell is available at the following.
3CB7314C-A3F4-48AD-85D7-F536D225FE81

Actually looking at your code further and matching up what you have for YES I believe the following is the channel GUID for MSG Buffalo.
FCA11159-7246-4EAA-9298-74D131367BFB
There is also a different MSGSN for this region at the below.
7B347484-D367-44EE-8BE8-49849D85CD58


Php::warning, Php::error are broke in nginx + phpfpm + Centos 7

I am working on nginx + phpfpm + Centos 7.
Php::warning, Php::error are broke when call in onRequest().
this is example:
in main.cpp
void init_request(){
	Php::error << "Testing" << std::flush;
}
.......
.......
extension.onRequest([]() {
	init_request();
});

What exactly do you mean with broken? Does it not compile, does it not do what it is supposed to do (generate output) or does the entire application crash?


10/21 Manual Review: Introduction Changes

2.1 Maybe the mentioning of “Shut up and write” could be removed or changed, as we haven’t had one since I arrived (but have had other types of writing workshops)
2.4 The ??? link just redirects me to the top of the introduction page
Add Recommended Reading List

Revised "Shut Up and Write" section, repaired link to section 13.


Installation problem

I have been using pysplit for the past two months. Recently I had to reset my Windows 10 Laptop after which I started facing installation issues. The specific issue says "Package conflicts" for dependents. I tried uninstalling and reinstalling Anaconda, still the problem persists. Request you to help me solve this. Thanks in advance.

Somehow the installation is successful, however receiving a user warning while stating " UserWarning: The Shapely GEOS version (3.8.0-CAPI-1.13.1 ) is incompatible with the GEOS version PyGEOS was compiled with (3.10.1-CAPI-1.16.0). Conversions between both will be slow.
shapely_geos_version, geos_capi_version_string".
In addition to the above warning, "RuntimeWarning: invalid value encountered in arccos np.cos(lon[0] - lon)) * 6371) * 1000" is appearing while the generating bulk trajectories. Kindly help me in resolving this issue.


Update packages

Added in https://github.com/ifvictr/ghost-storage-github/commit/fffdedf5b03191b95c01877d1dfad38bdc8616f8.


Clean builds of some projects fail if whole solution isn't built (FunctionalTests.vcxproj as an example)

Develop builds of FunctionalTests.vcxproj try to link against all frameworks (default imports from sbclang stuff) but the build dependencies aren't actually there. This suggests that this system of just dumping everything in is not sufficient and error prone. Either FunctionalTests should depend on a fully built sdk and be moved to samples / somewhere else or it should correctly describe its build deps and not be built as an "sdk consumer" since it is in the build that builds the sdk so everything may not be built by the time its needed ...

@bbowman why can't we add the explicit dependencies on the "dll" projects which the functional tests use?

@rajsesh-msft that is exactly what we are already doing but its the ones it doesn't use that can be problematic. The linker still looks for all of the import libs added and only discards them if they don't provide any needed unresolved external symbols. This means all libraries in the sdk consumer build props (all our frameworks) must exist so that lib can be found and found to be useless.

packaging fixed this I believe. FunctionalTests no longer inherit a huge linker line with all the libraries on it. This only happens when consuming packages which by definition all the binaries would be in the package.


add pulsar exporter/receiver to otel-contrib distributions

add pulsar exporter/receiver to otel-contrib distributions

@dmitryax PTAL


Automate Generating db

srvy.py should check to see if srvy.db exists. If not, it should call a seprate script that creates the database.

Use CREATE TABLE IF NOT EXISTS


terragrunt not showing output from terraform -version

during any terragunt action it will show this line
> terragrunt plan
2020/06/08 12:12:26 Running command: terraform --version

and doesn't show the terraform version. this makes it hard to debug some language issues because I'm not sure what terragrunt is actually running. should this be printing a version string?

We deliberately don't print out the terraform version as it is not necessary in the logs, but I can see how that might be useful. I think we can use util.Debugf in cli.PopulateTerraformVersion to only log the terraform version when in debug logging mode. Would you be up for a PR to add this in?

@yorinasub17 why are you running terraform --version then?

To enforce terraform version constraints (tg 0.19+ only works with terraform 0.12+ by default, but is customizable with terraform_version_constraint).


'npm install' fails for simple example

I cannot run the simple example - I get an error from npm install.
To repro:

download fresh repo from github
cd to examples/simple
run npm install
not the error below (I've tried this on a few Macs)

➜  simple git:(master) npm install
npm WARN prepublish-on-install As of npm@5, `prepublish` scripts will run only for `npm publish`.
npm WARN prepublish-on-install (In npm@4 and previous versions, it also runs for `npm install`.)
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.

><EMAIL_ADDRESS>prepublish /Users/lowellk/workspace/redux-form
> npm run test && npm run clean && npm run build

><EMAIL_ADDRESS>test /Users/lowellk/workspace/redux-form
> mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js

sh: mocha: command not found

npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "run" "test"
npm ERR! node v7.4.0
npm ERR! npm  v4.0.5
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>test: `mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script 'mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the redux-form package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs redux-form
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls redux-form
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/lowellk/workspace/redux-form/npm-debug.log

npm ERR! addLocal Could not install /Users/lowellk/workspace/redux-form
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.4.0
npm ERR! npm  v4.0.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run test && npm run clean && npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run test && npm run clean && npm run build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the redux-form package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run test && npm run clean && npm run build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs redux-form
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls redux-form
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/lowellk/workspace/redux-form/examples/simple/npm-debug.log

Also, the following command fails: npm run test && npm run clean && npm run build
> @ test /Users/lowellk/workspace/redux-form/examples/simple
> echo 'Error: no test specified'

Error: no test specified

> @ clean /Users/lowellk/workspace/redux-form/examples/simple
> rimraf dist

sh: rimraf: command not found

npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "run" "clean"
npm ERR! node v7.4.0
npm ERR! npm  v4.0.5
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! @ clean: `rimraf dist`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @ clean script 'rimraf dist'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rimraf dist
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/lowellk/workspace/redux-form/examples/simple/npm-debug.log

Because the examples contain relative paths to redux-form module, it seems like you hit this issue:
npm/npm#15097 npm/npm#15114
Could you please try upgrading to npm v4.1.0, and see if it fixes the problem?

Still getting the same error with npm 4 with both node 6 and 7

By 'the same error', I'm referring to the first one I mentioned: sh: mocha: command not found

I have the same error !
I tried to install mocha it does not work.
Node version : v6.9.1
Npm version : 4.1.2
C:\Downloads\redux-form-master\examples\simple>npm install
npm WARN prepublish-on-install As of npm@5, `prepublish` scripts will run only for `npm publish`.
npm WARN prepublish-on-install (In npm@4 and previous versions, it also runs for `npm install`.)
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.

><EMAIL_ADDRESS>prepublish C:\Downloads\redux-form-master
> npm run test && npm run clean && npm run build

><EMAIL_ADDRESS>test C:\Downloads\redux-form-master
> mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js

'mocha' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "test"
npm ERR! node v6.9.1
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test: `mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script 'mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the redux-form package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mocha --compilers js:babel-register --recursive --recursive "src/**/__tests__/*" --require src/__tests__/setup.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs redux-form
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls redux-form
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Downloads\redux-form-master\npm-debug.log

npm ERR! addLocal Could not install C:\Downloads\redux-form-master
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.9.1
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run test && npm run clean && npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run test && npm run clean && npm run build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the redux-form package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run test && npm run clean && npm run build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs redux-form
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls redux-form
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Downloads\redux-form-master\examples\simple\npm-debug.log

@lowellk did you find the problem ?

Hi people,
I had the same problem. After a while, I restarted from scratch and I noticed the documentation says:
"To run this example locally on your machine:
1 - Clone the redux-form repository, then
2 - cd redux-form to change to the repo directory, and
3 - run: npm install.
Then run npm run example:simple or manually run the following commands:
cd ./examples/simple
npm install
npm start"
I was missing the steps 1,2,3. Best!

Ah, really. This makes more sense. Thanks @matiaslee!


Value not displayed for std::string*

std::string* name = new std::string ("Albert"), the value of *name is not displayed in the variables view.

Fixed in 0.5.1.


Is it still being maintained and updated?

Is it still being maintained and updated?

I'll keep the long-term support for bug fixes, security improvements and performance optimizations. I use it for some private projects including a password manager (not open-sourced) without any issues. If there's any bugs or issues I'm ready to take a look at them. As I depend on this library for my private projects.
It's a hobby project so development will be slow from my side when I have time. I see it as a stable and well-tested project as it is now. I don't plan to build any new features at all, but would accept well-tested community PRs. But bugs and performance issues will be fixed.
My future roadmap is to publish better documentation online. Otherwise, I watch homomorphic encryption development closely and projects like SEAL and it would be nice to change encryption behind the scenes to that technology.


feat: Added support for multiple accounts

This adds multiple account support.  Only the first car per account though.  This is modeled after dalhb's work.   Config is auto updated from the current build.  I have only tested this once though.  I plan to keep testing but wanted to get a PR in for review.

This will need squash and merge to ensure it doesn't show so many commits.

I will do a round and tweaks.  After running this for a few days I am seeing the occasional error around non unique keys on sensors.   I will have to dig into that. Restarting seems to resolve it.

For some reason it won't let me reply to the threads anymore.  In response to vehicle id being the same as device id.  Sort of.   Home assistants "device ID" is the car.  Which is our vehicle id.  I think device ID in the token is different and more of a "client id" representing the endpoint from an API standpoint.


Fix reset and measurement gates being wrongly applied when moving

The initial comments on #100 raised a few very valid points that are not fixed yet. This issue document one of them.
Relevant part of the original comment:

The glue between different layers remains a cumbersome aspect. Maybe we can use some strategy pattern to specify how to merge /rewrite operations at the temporal boundaries when integrating different layers. For example, we can define a strategy to eliminate the reset operations for the already-in-use qubits when stacking an initialization layer onto a memory layer.

Originally posted by @inmzhang in https://github.com/QCHackers/tqec/pull/100#pullrequestreview-1887608426

Is your feature request related to a problem? Please describe.
Moving a logical qubit requires a few manipulation on Plaquette instances. Let's take the example below

Going from 1 to 2 has no issue. Plaquette instances that are used in 2 automatically reset their syndrome qubit by default
https://github.com/QCHackers/tqec/blob/47cb5e9712ab02959df9e2ce552cf8c663a2b110/src/tqec/plaquette/library/utils/pauli.py#L10-L56
but this reset gate can be tagged to be merged automatically afterwards like
https://github.com/QCHackers/tqec/blob/47cb5e9712ab02959df9e2ce552cf8c663a2b110/src/tqec/plaquette/library/measurement.py#L29

[!NOTE]
Turns out the reset is not tagged, a follow-up issue will be opened to address that.

Changing 2 into 3 is a little bit more challenging, because we need to apply initialisation plaquettes to the qubits to the right (in the example above), but we also need to avoid resetting the data qubits highlighted in blue.
Finally, changing 3 into 4 has the same issue, but with measurements: we need to apply the measurement plaquettes but also need to make sure that the data qubits highlighted in blue are not measured, as they are still used.
Describe the solution you'd like
I have no preference, as long as we are able to make that work, if possible elegantly, I am fine with the solution.
Describe alternatives you've considered
None of the following alternatives have been tested yet:

As noted in the comment cited at the beginning of this issue, maybe find a clever way to remove reset and measurement gates in some conditions. My main concern here is that I think this will be tricky to get predictable, easy to explain to a potential user, and right in all cases.
We may also try to make the initialisation and measurement plaquettes aware of that kind of situations (e.g., adding a PlaquetteSide argument somewhere that would be either the side of the plaquette that should be kept or the one that should be reset/measured).

Note that potential solution number 2 above is not enough: we do not want to have to re-define specific Template instances to be able to apply different plaquettes as this is the main pain point found by implementing the qubit movement in #81 and #100.
This additional restriction leaves us with very little freedom to implement something, and I can only see option 1 (automatically removing the operations in some way) if we want to avoid creating a (or several) new Template and Plaquette instances.

I'd like to help out with the backend some more, so I can look into this.

One more piece that might be important for this one: we can consider logical qubits to have assigned positions on the physical qubit grid.

In the grid above, Template instances are drawn in blue, and it is reasonable to limit ourselves to logical qubits that can only be within a red square. In other words, logical qubits are arranged on a grid.
Feel free to discuss what you plan to do here, both @inmzhang and myself have implemented the qubit movement and so we might be able to see if there is any shortcoming early.

@smburdick any update on that issue?

Sam is out this week, can anyone else help?
On Tue, May 7, 2024 at 12:31 AM Adrien Suau @.***>
wrote:

@smburdick https://github.com/smburdick any update on that issue?
—
Reply to this email directly, view it on GitHub
https://github.com/QCHackers/tqec/issues/202#issuecomment-2097636153,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAXTDMJ3I5AOMOYW7FMTLZBB7MRAVCNFSM6AAAAABFMJ5SFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXGYZTMMJVGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sam is out this week, can anyone else help?

Let's wait for Sam on that. I can start hacking, but I do not want to re-do things that Sam already did on his side without pushing online, and as he assigned to this issue he should have the priority.

@smburdick have you started to look at that issue on your side?
If not, I am thinking about coming back to it and try to find a reasonable solution to this long-standing issue that is currently blocking most of the interesting developments.
If you did think about it / write code to solve it, could you share your work?

@nelimee I haven't had time recently due to my personal life, and being more focused on the frontend. I don't know if I'll have time to in the next couple of weeks.

If this is fine for you, I will assign myself to that issue then. Thanks for answering :)

Closing this issue as we are changing the way we think about movement. Rather than a movement, it is a merge of 2 logical patches.


refactor: add #[doc(hidden)] for some constants

#50

Well, couldn't find a similar issue, so I created one: https://github.com/rust-lang/rust/issues/112085

I'm also pleasantly surprised, but I haven't taken into account that this is an issue with rustc.


Create ROM using pre-defined seed

I have a couple seeds saved, but I can not find any way to create a ROM using the seeds.
It seems the only way to create a new randomized ROM is to create a new seed.

There is, see the example image.


false identification of bid as invalid

Today I see bottracker showing bids invalid that are actually valid and accepted by bot, this misleads bidders.

Seems bids are now showing valid after bot config update.

Again I see valid bids showing up as invalid in botrracker.
This is a problem.
Example

Any plans to look into this issue?
Customers are complaining about being mislead.

I will look into it.

It keeps happening!

I just commented out the check for if the bot already voted on the post as I think this is what is causing the issue. Please keep an eye on it and let me know if you are still seeing the issue or if it has been resolved.

Ok. Will watch for it and let you know. Thanks.

I saw it again.
Valid bid showed as invalid
https://steemit.com/photography/@badol1994/boat-photography

Likely because it was 18 hours before payout.

Is not false alarm. This bot is upvoted the post already

bot voted for this post after I took this pic.

That was marked as invalid because the post was more than 6 days old. Some bots use 6 days, some use 6 days 12 hours, some even use 5 days. I've realized that I can't get the settings right for every bot so I've gone ahead and turned off checking for invalid posts entirely.
I'm working on a solution where bots can report their valid bids directly to the bot tracker which should be much better, but for now it will show all bids as valid so people will only ever get more than what the bot tracker showed if there were any invalid bids.


Vulnerability roundup 84: fuse-2.9.9: 1 advisory

search, files

[ ] CVE-2019-14860 CVSSv3=6.5 (nixos-19.09, nixos-20.03, nixos-unstable)

Scanned versions: nixos-19.09: 31dcaa5eb67; nixos-20.03: 82b5f87fcc7; nixos-unstable: 0f5ce2fac0c. May contain false positives.

This is a false positive. CVE-2019-14860 is for Red Hat Fuse while fuse-2.9.9 is from libfuse.


python37Packages.tensorflow-bin: 1.14.0 -> 2.1.0

Motivation for this change
This bumps python37Packages.tensorflow-bin to version 2.1.0.
It also bumps some of the dependencies of tensorflow-bin to the required versions:

tensorflow-tensorboard: 1.15.0 -> 2.1.0
tensorflow-estimator: 1.15.1 -> 2.1.0

With this PR, tensorflow-bin builds correctly, and appears to be able to be used correctly with python37Packages.
I've tested it with the following simple python script (from https://www.tensorflow.org/tutorials/quickstart/beginner):
from __future__ import absolute_import, division, print_function, unicode_literals
import tensorflow as tf

mnist = tf.keras.datasets.mnist
(x_train, y_train), (x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0

model = tf.keras.models.Sequential([
  tf.keras.layers.Flatten(input_shape=(28, 28)),
  tf.keras.layers.Dense(128, activation='relu'),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10)
])
loss_fn = tf.keras.losses.SparseCategoricalCrossentropy(from_logits=True)
model.compile(optimizer='adam', loss=loss_fn, metrics=['accuracy'])
model.fit(x_train, y_train, epochs=5)
model.evaluate(x_test,  y_test, verbose=2)

I've only tested this on Linux without CUDA.  I would appreciate if someone could try this out on Mac or with CUDA enabled.
I'm a beginner with both Tensorflow and Python, so please let me know if I am doing anything weird here.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build python37Packages.tensorflow-bin

Here are two related PRs:

https://github.com/NixOS/nixpkgs/pull/71890: bumps tensorflow-tensorboard to 2.0.0, but it should be superceded by this current PR.

https://github.com/NixOS/nixpkgs/pull/70910: bumps tensorflow to 2.0.0.  This isn't directly related to this PR, but people who are following that will probably be interested in this PR as well.  cc @tbenst @danieldk @mjlbach @Zhen-hao @Ericson2314

I'm currently in the process of testing the following:

Linux, non-cuda:

python36Packages.tensorflow-bin
python35Packages.tensorflow-bin
python27Packages.tensorflow-bin

(Although I'm not sure if any of them would be considered expected failures.)

@GrahamcOfBorg build python37Packages.tensorflow-bin python36Packages.tensorflow-bin python35Packages.tensorflow-bin python27Packages.tensorflow-bin

I forgot to update the hash for tensorflow-tensorboard for python27, so I just updated it and force-pushed.

Shouldn't update to pythonPackages.tensorflow-tensorboard and pythonPackages.tensorflow-estimator break the pythonPackages.tensorflow unless we don't bump it as well?

@veprbl I was under the impression that pythonPackages.tensorflow was already broken.
When I try to build it on master, I get the following message:
$ nix-build -A python37Packages.tensorflow
error: Package ‘openssl-1.0.2u’ in /home/illabout/git/nixpkgs/pkgs/development/libraries/openssl/default.nix:130 is marked as insecure, refusing to evaluate.

Known issues:
 - Support for OpenSSL 1.0.2 ended with 2019.

You can install it anyway by whitelisting this package, using the
following methods:
...

I don't think this should hold back updating tensorflow-bin.

@veprbl I was under the impression that pythonPackages.tensorflow was already broken.

This is my understanding as well, I'm fine with surpassing a broken build.

tensorflow is fixed pending merge of two PRs: https://github.com/NixOS/nixpkgs/issues/80379#issuecomment-593129212.
tensorflow 2 is sadly not fully backward-compatible with tensorflow 1, and there are a number of libraries / applications that are not moving. I’d love to see both versions in nixpkgs.

This now broke the non-bin package of tensorflow. Some of us were using it but others (like me) were trying to unbreak the edge-cases I am hitting.
TF 1.15 might have been broken in a few ways. With this PR merged we now need to unbreak even more.. I guess I'll just go about adding a second version of TF estimator for the older TF 1.15.

Those that need tensorflow and related packages need to cooperate a bit more, because with all these different PR's touching it, it is hard to follow.

Since there seem to be many people who are very interested in keeping it working, it would be nice if some of them could add themselves as additional maintainers. Due to time constraints maintaining it isn't a very high priority for me personally right now.

@andir Sorry for breaking the other tensorflow with this.
Could we merge in #70910 (after possibly updating it to 2.1.0)?

hi, what is the new tensorflowWithCuda for 2.1? Is it built in tensorflow-bin_2?

Look at the old ones definition? All I know of is a cudaSupport flag on 1.x and 2.x.

you are right.
  tensorflowWithCuda = self.tensorflow.override {
    cudaSupport = true;
  };


Ability to change "Images" breadcrumb element to something else.

With the ability to display videos as well as photos, having "Images" as the base folder (and breadcrumb root) feels a little dated.  If this could be set to something else within the config/settings that would make for a great option.
Even if it was set to "Home" by default it would look better.

I agree

SG. Its more complex to make it configurable, as it needs to be localized, but I changed to Home

Nice.  Thank you.


XCM. PAH to Mythos - can't bypass Recipient check with EVM address

Description

Address example:
0x4c2ab98b646ce36df6a4a4407ab9fcee1c90549a
Environment
https://github.com/novasamatech/nova-spektr/commit/aec2ef298e5061fd22d29d7a05c6a2029fc6adab

Status verification: ✅


starfive visionfive2: update kernel to 6.6.0

Description of changes
Things done

[ ] Tested the changes in your own NixOS Configuration
[ ] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

@mergify queue


function doi_crossref

This function takes a doi (10.1109/ACCESS.2022.3232939) to perform a web scraping in crossref https://www.crossref.org/ and creates a data frame with all the data.

Assigned @darien231995
Deadline: Monday, September 30


Fix optimizer miscalculation and add optimization for Animation::ValueTrack

Fixed wrong calculation for ratio (I had overlooked that the positive/negative inversion reverses the if judgment)
Use double internally to improve accuracy
Allowed some types of value tracks to be optimized

FLOAT
VECTOR2
VECTOR3
QUATERNION

There are some concerns:

In AnimationEditor, the Edit button can access to optimization from previously, but it is not possible to filter by track type. Also, there is no undo function. This is because the optimization is implemented directly in the Animation class. It might be better to implement an AnimationOptimizer class and use static methods to perform optimizations.

A little change to the UI around the AnimationTrackEditor optimizer (added a warning).

Also, after optimize, clear not only Animation but also AnimationTrackEditor's history.

Thanks!


Fixed the link to Cadence comparison example

Please specify parts this PR updates:

[ ] Specification
[ ] Schema
[ ] Examples
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[x] Other

What this PR does / why we need it:
This PR fixes the link to Cadence comparison. Previously the link pointed to Temporal comparison.
Special notes for reviewers:
None
Additional information (if needed):
None

Approved in our team meet today - https://docs.google.com/document/d/1xwcsWQmMiRN24a7o7oy9MstzMroAup31oOkM5Dru1jQ/edit#


[BUG] failed to run a gpt2_xl test case

I wrote a GPT2 test case and tried gpt_small and gpt_large. they are fine. However, it failed on gpt2_xl.
For more details see my MR #115 .
BTW: What is the unit of throughput? Can you provide a Tflops metrics? It is a task-irrelevant indicator that reflects the utilization of hardware computing power.
Tflops = (model_numel * batch_size * sequence_length * 2 * 4) / elapse per iter
On a 8 GPU node.
cd examples/gpt
bash run.sh

Traceback (most recent call last):
  File "run_gpt2_with_engine.py", line 110, in <module>
Traceback (most recent call last):
  File "run_gpt2_with_engine.py", line 110, in <module>
    train_gpt()
  File "run_gpt2_with_engine.py", line 106, in train_gpt
    trainer.fit(train_dataloader=train_dataloader, epochs=gpc.config.NUM_EPOCHS, hooks=hook_list, display_progress=True)
  File "/workspace/ColossalAI/colossalai/trainer/_trainer.py", line 312, in fit
    train_gpt()
  File "run_gpt2_with_engine.py", line 106, in train_gpt
    self._train_epoch(
  File "/workspace/ColossalAI/colossalai/trainer/_trainer.py", line 178, in _train_epoch
    trainer.fit(train_dataloader=train_dataloader, epochs=gpc.config.NUM_EPOCHS, hooks=hook_list, display_progress=True)
  File "/workspace/ColossalAI/colossalai/trainer/_trainer.py", line 312, in fit
    logits, label, loss = self.schedule.forward_backward_step(
  File "/workspace/ColossalAI/colossalai/engine/schedule/_non_pipeline_schedule.py", line 52, in forward_backward_step
    output = self._call_engine(engine, data)
  File "/workspace/ColossalAI/colossalai/engine/schedule/_base_schedule.py", line 98, in _call_engine
    self._train_epoch(
  File "/workspace/ColossalAI/colossalai/trainer/_trainer.py", line 178, in _train_epoch
    return engine(inputs)
  File "/workspace/ColossalAI/colossalai/engine/_base_engine.py", line 112, in __call__
    logits, label, loss = self.schedule.forward_backward_step(
      File "/workspace/ColossalAI/colossalai/engine/schedule/_non_pipeline_schedule.py", line 52, in forward_backward_step
return self.model(*args, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    output = self._call_engine(engine, data)
  File "/workspace/ColossalAI/colossalai/engine/schedule/_base_schedule.py", line 98, in _call_engine
    return engine(inputs)
  File "/workspace/ColossalAI/colossalai/engine/_base_engine.py", line 112, in __call__
    return self.model(*args, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 871, in forward
    return forward_call(*input, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 871, in forward
    output = self.module(*inputs, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    output = self.module(*inputs, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/cuda/amp/autocast_mode.py", line 18, in decorate_autocast
    return func(*args, **kwargs)
  File "/workspace/ColossalAI/colossalai/amp/torch_amp/torch_amp.py", line 63, in forward
    return self.model(*args, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/cuda/amp/autocast_mode.py", line 18, in decorate_autocast
    return func(*args, **kwargs)
  File "/workspace/ColossalAI/colossalai/amp/torch_amp/torch_amp.py", line 63, in forward
    return self.model(*args, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/workspace/ColossalAI/model_zoo/gpt/gpt.py", line 245, in forward
    x, attention_mask = block(x, attention_mask)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/workspace/ColossalAI/model_zoo/gpt/gpt.py", line 245, in forward
    x, attention_mask = block(x, attention_mask)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/workspace/ColossalAI/colossalai/nn/layer/utils/common.py", line 26, in forward
    return checkpoint(self._forward, *args, **kwargs)
  File "/workspace/ColossalAI/colossalai/utils/activation_checkpoint.py", line 117, in checkpoint
    return CheckpointFunction.apply(function, *args)
  File "/workspace/ColossalAI/colossalai/utils/activation_checkpoint.py", line 44, in forward
    outputs = run_function(*args)
  File "/workspace/ColossalAI/model_zoo/gpt/gpt.py", line 148, in _forward
    return forward_call(*input, **kwargs)
  File "/workspace/ColossalAI/colossalai/nn/layer/utils/common.py", line 26, in forward
    return checkpoint(self._forward, *args, **kwargs)
x = x + self.attn(self.norm1(x), attention_mask)  File "/workspace/ColossalAI/colossalai/utils/activation_checkpoint.py", line 117, in checkpoint

  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return CheckpointFunction.apply(function, *args)
  File "/workspace/ColossalAI/colossalai/utils/activation_checkpoint.py", line 44, in forward
    outputs = run_function(*args)
  File "/workspace/ColossalAI/model_zoo/gpt/gpt.py", line 148, in _forward
    x = x + self.attn(self.norm1(x), attention_mask)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1056, in _call_impl
    return forward_call(*input, **kwargs)
  File "/workspace/ColossalAI/model_zoo/gpt/gpt.py", line 72, in forward
    qkv = qkv.view(new_qkv_shape)
RuntimeError: shape '[8, 1024, 6, 192]' is invalid for input of size 9830400
    return forward_call(*input, **kwargs)
  File "/workspace/ColossalAI/model_zoo/gpt/gpt.py", line 72, in forward
    qkv = qkv.view(new_qkv_shape)
RuntimeError: shape '[8, 1024, 6, 192]' is invalid for input of size 9830400

Hi. The problem is supposed to be that the number of attention heads of GPT-XL is 25, which cannot be divided by the tensor parallel size 4. We will improve the related error messages very soon.


Variance or weighted variance to measure the fairness?

I see you have the fairness definition according to the variance of accuracies across m devices.
However, the variance you compared
https://github.com/litian96/fair_flearn/blob/5f174cba7521df606fc946f40a0b5fef09b546e3/plot_fairness.py#L51
has the assumption that the accuracies are equally like the same.
My question is,
instead of using the standard the variance, why not calculate the variance in a weighted fashion?
A revised variance, either in the weights of the sample distributions or the q-federated weights makes much more sense to me.
Is that true?

The standard variance is also consistent with the accuracy distribution figures. We would like to treat each device equally, such that each user's experiences are the same (even if they have different numbers of training samples, etc).

My concern is for a larger loss in a device with a smaller sample size won't reflect its fairness in the variance.  And vice versa.
As in the eq (2), the objective has the weights involved, then the variance (fairness) could also have the weights involved.

A larger loss potentially means small accuracy. Why won't it affect the fairness/variance?

Sorry, revised as accuracy.
Consider a toy example: three devices (acc, # sample)
(0.5, 10), (0.5, 10), (0.5, 10000) -- low variance
(0.1, 10), (0.1, 10), (0.9, 10000) -- high variance
Which one is better in terms of "fairness"?

Sorry I missed your previous question...
By our definition (Def 1 in https://arxiv.org/pdf/1905.10497.pdf), the first one is more fair and in your second example, the model seems to overfit to the 'dominant' devices with 10,000 samples, which is what we are trying to mitigate.

Yes, thanks for your reply.
I see the published work on ICLR. Congrats. I will follow up later.

Hi Hongwei,
do you have any additional questions/comments regarding this issue?

Not at this moment, thanks.
Issue can be closed.


Fix memory leak when using passthrough

This should solve #53

Look good. But there should be a check for null on avPacket.

First I wanted to add a null check as well. But then I read the docs of the av_packet_free call, and saw that it will internally already do a null check.
I just pushed a new commit to remove the redundant check (also in one other place).

Thanks for the merge :)


DCS World does not push VR "view" to Quest

When starting DCS World, the game loads up on the desktop fine but SteamVR just hangs on the loading screen in the Quest.
This seems to be an issue with Alpha5, specifically, as apparently it worked fine in A4 (https://github.com/polygraphene/ALVR/issues/395)

I can confirm that its not working but I don't know who to blame for it:
Tue Sep 10 2019 12:27:06.412 - [System] System is running for 10 seconds. Tue Sep 10 2019 12:27:47.446 - CSharedResourceNamespaceServer sent namespace data: 19996 Tue Sep 10 2019 12:27:47.457 - New Connect message from C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe (VRApplication_Scene) (Args: ) 26564  Tue Sep 10 2019 12:27:47.457 - StartSceneApplicationTransitionFromProcess( 26564, C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe, ) Tue Sep 10 2019 12:27:47.457 - Creating builtin app for C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe (VRApplication_Scene) Tue Sep 10 2019 12:27:47.457 - Sending Quit event to process steamtours (22776) Tue Sep 10 2019 12:27:47.457 - Refusing connect from DCS (26564) because app start error VRInitError_Init_Retry Tue Sep 10 2019 12:27:47.470 - Console message (Info) from http://localhost:8998/dashboard/vrwebui_shared.js?v=ede2cce03cd72bef05b4:5: | Loaded action manifest for  Tue Sep 10 2019 12:27:47.561 - Closing pipe steamtours (22776) because it was broken from the other end Tue Sep 10 2019 12:27:47.561 - Process steamtours (22776) disconnected (Thread(0x000002EDD2CE3760/0x000) Tue Sep 10 2019 12:27:47.561 - Clearing application openvr.tool.steamvr_environments PID because 22776 has exited Tue Sep 10 2019 12:27:47.561 - Closing pipe steamtours (22776) because it was broken from the other end Tue Sep 10 2019 12:27:47.561 - Process steamtours (22776) disconnected (Thread(0x0000022A0F63F4B0/0x000) Tue Sep 10 2019 12:27:47.561 - Lost pipe connection from steamtours (22776) Tue Sep 10 2019 12:27:47.561 - ###################################################################### Tue Sep 10 2019 12:27:47.561 - Cumulative stats for pid: 22776 Tue Sep 10 2019 12:27:47.561 - Total..................  3635 presents.    6 dropped.    0 reprojected Tue Sep 10 2019 12:27:47.561 - Startup................   486 presents.    6 dropped.    0 reprojected Tue Sep 10 2019 12:27:47.561 - Loading...  1 total....     0 presents.    0 dropped.    0 reprojected Tue Sep 10 2019 12:27:47.561 - Timed out.  0 total....     0 presents.    0 dropped.    0 reprojected Tue Sep 10 2019 12:27:47.561 - ###################################################################### Tue Sep 10 2019 12:27:47.561 - Total dropped frames: 6 Tue Sep 10 2019 12:27:47.610 - Found Windows 10 or newer, so enable advanced image processing of scene textures. Tue Sep 10 2019 12:27:47.958 - New Connect message from C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe (VRApplication_Scene) (Args: ) 26564  Tue Sep 10 2019 12:27:47.958 - Unable to create property container PC_7000067c4 because it already existed Tue Sep 10 2019 12:27:47.958 - Unable to create property container for DCS (26564). Maybe it's a reconnect? Tue Sep 10 2019 12:27:47.958 - StartSceneApplicationTransitionFromProcess( 26564, C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe, ) Tue Sep 10 2019 12:27:47.969 - Setting app system.generated.dcs.exe PID to 26564 Tue Sep 10 2019 12:27:47.969 - Enabling legacy input for system.generated.dcs.exe Tue Sep 10 2019 12:27:47.971 - system.generated.dcs.exe (oculus_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Flegacy_bindings_generic_hmd.json Tue Sep 10 2019 12:27:47.971 - system.generated.dcs.exe (oculus_touch) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fdrivers%2Foculus%2Fresources%2Finput%2Flegacy_bindings_touch.json Tue Sep 10 2019 12:27:47.971 - Using existing HMD alvr_server.WMHD000X000XXX Tue Sep 10 2019 12:27:47.971 - Processing message VRMsg_Connect from DCS (26564) took 0.0138 seconds Tue Sep 10 2019 12:27:47.989 - External connection from C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe 26564 Tue Sep 10 2019 12:27:47.997 - Invalid input type click for controller (/user/head/proximity) Tue Sep 10 2019 12:27:48.010 - Closing pipe DCS (26564) because it was broken from the other end Tue Sep 10 2019 12:27:48.010 - Process DCS (26564) disconnected (Thread(0x000002EDC2B6DB40/0x000) Tue Sep 10 2019 12:27:48.010 - Clearing application system.generated.dcs.exe PID because 26564 has exited Tue Sep 10 2019 12:27:48.010 - Closing pipe DCS (26564) because it was broken from the other end Tue Sep 10 2019 12:27:48.010 - Process DCS (26564) disconnected (Thread(0x0000022A0F4BF240/0x000) Tue Sep 10 2019 12:27:48.010 - Lost pipe connection from DCS (26564)

Thanks for the reply. Unfortunately none of that makes sense to me. The only thing I could suggest is doing the same thing with the old ALVR alpha 4 and comparing the log to (maybe) see where the issue is. I'm sorry I don't know enough about anything that's going on to help out myself.

The formatting is horrible. Here is the entry I'm referring to:
Closing pipe DCS (26564) because it was broken from the other end Tue Sep 10 2019 12:27:48.010 - Process DCS (26564) disconnected (Thread(0x000002EDC2B6DB40/0x000)
DCS seems to close the connection to SteamVR

I've just downloaded v2.4.0-alpha4 and DCS loads on that. The controllers are all messed up obviously, but the "VR view" works perfectly.
I tried turning on the debug log but there's nothing in the generated log that contains "DCS" so I'm assuming it's not the same log you're using.

This commit breaks DCS. If I change the tracking system name back to "Oculus Tracker" from "oculus", DCS opens a terribly distorted and miss aligned VR view.
If the name of the tracking system throws DCS off, I strongly suspect a problem on their end.
Has someone tried this game with a Oculus Rift S? It should report the same as ALVR. I have installed the oculus runtime wich is always started when I launch DCS, maybe they try to launch the game using the oculus runtime and fail.

It's great that you've tracked it down!
When I used alpha 4 earlier, I did not think it looked distorted or misaligned.
I actually have a family member with a Rift S who plays DCS regularly. I did a quick search on YouTube to find something more concrete than that and found several videos uploaded within the last month (such as this: https://youtu.be/0vaHsjxY1vU)

Hello, sorry to bump this, but I've just looked at the https://github.com/polygraphene/ALVR/releases/tag/v2.4.0-alpha4 source code and it doesn't have the "driverConfig.trackingSystemName" at all. It only has serialNumber and modelNumber. It seems that whatever is messing up DCS (including the weird skewed we now get when changing the trackingSystemName) happened when these additional settings (and their associated changes) got added.

@JackD83
My comment above is incorrect.
I've started at the alpha5 release and undone as many of the post-alpha4 commits as I could (I don't currently have Android Studio so I can't build the .apk and therefore can't alter anything that requires a corresponding change in the .apk).
Even with the vast majority of the code rolled back to alpha4 (including the trackingSystemName setting etc), the view in DCS is still distorted. It's fine if I look straight ahead, but any time I turn it skews the view (like turning a rectangle into a parallelogram) and zooms in/out.
The only places left for the issue to be are in the client->server communication changes or in a change in the .apk.
It's a very odd issue given that the same distortion doesn't occur in any other games using ALVR, the view in alpha4 is not distorted, and that DCS works fine on the Rift/Rift S.

Rise of the tomb raider has the same issue as DCS

The distortion is caused by the required <uses-feature android:name="android.hardware.vr.headtracking" android:required="true" android:version="1"/>
in the client manifest to enable controller tracking on later firmware versions. I don't know how to fix this

I just found this:

 is required for v2 signing, which is required for store review for Oculus Quest apps. For apps that target Oculus Quest and Oculus Go / GearVR with the same APK, v1 signing must instead be used for GearVR compatibility. If you are using the same binary for your Oculus Quest and Oculus Go / GearVR application, and have added headtracking in platform-specific code, you can use the above in your manifest but with android:required="false" to mark it as a hybrid application, however it must be signed with schema v1. Applications with headtracking and android:required="true" are the only ones that will support and require v2 signing for upload to dashboard.

Perhaps changing android:required to false could work?

No, not working either

After the change from oculus, the reported fov changed from:
GetProjectionRaw Eye=0 (l,r,t,b)=(45.000000,45.000000,45.000000,45.000000)
to
GetProjectionRaw Eye=0 (l,r,t,b)=(52.000000,42.000000,53.000000,47.000004)
I tried to change it back manually, but this parameters change the rendering on the quest and forcing it to the old values did not help

Closed and integrated in #88


Curing meat not working

I know to place rack , place hooks, put meat and wait but it turned into -6 days to cure and meat was still raw

I imagine you were away from the area for an extended period of time, with the chunk unloaded, and returned to see this? If not, please let me know some more details.
Seems there was some strangeness in one of the logic checks that caused this. It should be fixed for the next release, just got to test it a little more. Thanks for the report!
If you see this again, just wait an in-game hour. When the curing rack does another tick it should cure the things.

This should now be fixed in Ancient Tools V1.4.4. If you have the chance to confirm, please do let me know what you find ^.^


Adding brick map

Added a BrickMap implementation, and made VoxelStorage a trait, that is implemented by BrickMap and Octree, so the rendering system, etc. doesn't need to know which storage method is being used


Google Analytics 4 migration followup

This is a followup item to

#354

Tasks

[ ] Drop UA ID once it is no longer receiving events (in 2H2023) or are no longer needed. Given that this site uses the Docsy page-feedback feature, you'll need to add a bogus ID to the config file (at least, that is the required behavior as of the time of writing this).
[ ] #356

/remove-lifecycle stale


AttributeError: WindowSpecification class has no 'CPUUsage' method

Hi Master,
I tried the following code and an err raised, would you have a look?
Thanks & Regards,
Simon
app = application.Application(backend="uia")
app = app.start("C:\Program Files (x86)\___.exe")
app.wait_cpu_usage_lower(5,10,0.5)
Traceback (most recent call last):
File "NT8Auto_v0.2.py", line 99, in
main()
File "NT8Auto_v0.2.py", line 63, in main
app.wait_cpu_usage_lower(5,10,0.5)
File "C:\Program Files\Python35\lib\site-packages\pywinauto\application.py", line 1030, in wait_cpu_usage_lower
while self.CPUUsage(usage_interval) > threshold:
File "C:\Program Files\Python35\lib\site-packages\pywinauto\application.py", line 165, in call
format(self.criteria[-1]['best_match']) )
AttributeError: WindowSpecification class has no 'CPUUsage' method

You didn't specify a window / dialog. The general form should be: app.WindowTitle.wait_cpu_usage_title(),  but you have to change it according to a title of a dialog in your app

CPU usage is app specific only (window specification is not needed), so it looks like a bug produced by replacing deprecated CPUUsage method with cpu_usage. I think I know how to reproduce and fix this. Will do when get back from the trip (after January, 9).


Ambient + Cilium: Cilium NetPol enforcement no longer silently ignores host probes

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
As part of the inpod ambient work, in order to prevent host-originating status probes from the kubelet from being proxied thru the ztunnel, Istio modifies the source IPs for host probes to bypass their capture via iptables SNAT.
This causes an issue when using Istio+Cilium, as Cilium uses the host source IP to silently bypass NetPol enforcement for host traffic.
This means that when using Istio+Cilium, healthprobes are no longer silently ignored by Cilium for NetPol enforcement, and have to be explicitly considered in NetPol.
For instance, with plain Cilium and no Istio ambient, given a pod with a healthcheck endpoint on 8080, applying the following ingress NetPol:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: only-hbone
spec:
  policyTypes:
  - Ingress
  ingress:
  - ports:
    - protocol: TCP
      port: 15008

would result in host probes to 8080 silently being allowed thru, even though 8080 is not allowlisted in the NetPol.
However, with Istio ambient added to the mix, NetPol starts to apply to host probes, and the above causes (as you might expect) probe traffic on 8080 to start to be rejected.
This means the following ingress NetPol is required:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: only-hbone
spec:
  policyTypes:
  - Ingress
  ingress:
  - ports:
    - protocol: TCP
      port: 15008
      # Istio modifies the source IPs for host probes to bypass their capture.
      # Cilium uses the host source IP to bypass host traffic enforcement for NetPol.
      # This means that when using Istio+Cilium, healthprobes are no longer silently ignored by
      # Cilium for NetPol enforcement, and have to be explicitly considered in NetPol.
    - protocol: TCP
      port: 8080

The use (and pitfalls, and alternatives) of host-probe SNATs was discussed here: https://github.com/istio/istio/pull/48253/files#r1424242669
While this is certainly better than previous large-scale incompatibilities with Cilium, this is still not ideal. Calico does not seem to have this issue AFAICT, so it probably allowlists host probes thru NetPol enforcement via a different mechanism than Cilium.
Version
N/A

Additional Information
No response

Hmm, it looks like cilium identity health probe by host source ip, but we utilize SNATed well-know ip to do that, both are intended to bypass the further process.
I may lost some background or discussion on why we choose SNAT here. I'm wondering if we could also just use host source ip to identity the health probe as well.  IIRC, in previous redirection mode, we bypass the health probe just by host ip  and we have an API to emulate how kubelet to get the host source ip(since istio-cni daemonset and kubelet are in the same host network namespace).

Hmm, it looks like cilium identity health probe by host source ip, but we utilize SNATed well-know ip to do that, both are intended to bypass the further process. I may lost some background or discussion on why we choose SNAT here. I'm wondering if we could also just use host source ip to identity the health probe as well.

2 reasons why we didn't do this:

"getting the canonical host IP" from the perspective of packets entering a given pod network namespace in a way that works for all CNIs and all networking setups is actually quite tricky and varies widely by CNI, and there is no one reliable way to do it. All ways we had done it in the past did not work in all cases, for all CNIs.

Filtering on "the host IP" is not actually sufficient in some cases - as we see in https://github.com/istio/ztunnel/issues/642 it is entirely possible for packets from LoadBalanced services that did not originate on the host to arrive at the pod with the host IP - bypassing those wholesale is not desirable.

The way Cilium ignores host probes from network policies is as follows:

There is a controller in the agent that periodically syncs the host's IP addresses to the bpf lxcmap and ipcache. As a part of this, it maps the host IP addresses to a reserved host identity in Cilium. This notifies the network-policy cache on changes.
In Kubernetes mode (other modes reserved for VMs, etc.), localhost traffic is always allowed to reach local endpoints. This is realized by adding an ALLOW entry  to the bpf policy map that is lower in priority than explicit DENY entries, with the identity key for this entry being the reserved host identity noted in the step above.

Summary: Cilium assigns a reserved host identity to host local endpoints and adds an explicit ALLOW entry to the bpf policy map for ingress traffic from endpoints that have the reserved host identity (applicable localhost endpoints in this case).

That's annoying - despite all the machinery it's still just allow-listing host IPs and treating them as identities, which means it has the same conceptual gaps but is harder to change.
Calico clearly does something different here, as well.
Haven't looked much, but I wonder if https://docs.cilium.io/en/stable/security/policy/language/#host-policies could be an option.

Tested - this can be solved by applying the following CiliumClusterwideNetworkPolicy
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: "allow-ambient-hostprobes"
spec:
  description: "Allows SNAT-ed kubelet health check probes into ambient pods"
  endpointSelector: {}
  ingress:
  - fromCIDR:
      - "<IP_ADDRESS>/32"

where fromCIDR is the SNAT-ed host probe IP ambient uses

I think this is a relatively acceptable solution so I am going to close this issue and put this in our docs somewhere.


Add an option to let us customize shadows

I want to increase shadow distance just a little bit more

Currently you can pass two object to customize the light shadow and  dark shadow.
But it is still in experimental,
try passing the prop customLightShadow and customDarkShadow
the property you can use are:

blur

spread

color

offsetX

-offsetY
but for color, offsetX and Y, I suggest putting a ternary of handling inset view.
I am refactoring that part of code for easier implementation.

This feature will come in version 1.2, stay tuned

Please update react-native-neu-element to the latest version, this feature has been added, thank you.
npm install --save<EMAIL_ADDRESS>or
npm install --save react-native-neu-element


Add mypy to pre-commit

Feel free to close if not desired, but we find it handy internally to use mypy as it's better at catching type errors.

basic question, wouldn't we also need to add mypy to requirements-dev.in? (and isort)

The pre-commit library will keep everything installed and correct version itself (except pylint which I listed as local, because it works better with packages that way), so no need to add them explicitly to requirements-dev.

(Just noting that mypy / isort aren't being run in CI without merging #268 first.

Yes, I just merged that other PR. Thank you for adding it, and for adding isort! My only remainining question here is around the version; it seems like the most recent mypy version is 1.0.0. Is there a reason you prefer v0.961?

pre-commit failures fixed in https://github.com/broadinstitute/regional_missense_constraint/pull/275

closing; duplicated in https://github.com/broadinstitute/regional_missense_constraint/pull/278


Added new mode to compute slices incrementally for depth texture

I added a progressive mode to compute 3D textures
It works quite well (slice are losely couples, and look indeed like blue noise)
I think that the difficulty with 3D textures in general is that the kernel is too big, causing overcoupling, and can't converge easily to blue noise as a result. A future improvement could be to remove samples on the kernel that do not contribute enough (when dz < 0, only keeping samples with x == 0 and y == 0 for example).

thanks ! For double, no particular reason, I wanted to see if precision was an issue.
today, I tried to use a sparse kernel for 3D texture with the base algo. It is much faster. But the result looks similar than that of highpass, however it is of better quality and more orderly. I just changed the kernel generation code for this case. I will submit it later

Sparse kernel just keep the major axis.
Inside the kernel generation, I Just added this :
if (_GenParams.N_dimensions >= 3)
{
// use sparse kernel
uint32_t sum = (ks.Distances[0] != 0 ? 1 : 0) + (ks.Distances[1] != 0 ? 1 : 0) + (ks.Distances[2] != 0 ? 1 : 0);
if (sum == 3u) continue; // not on major axis, do not keep for the kernel
}

Hey, @nicovize I noticed that all files require "debug_opt.h" that is not in the repository - could you submit it please? Thanks!

Hi Bart, this is debug code that I forgot to remove :( You can remove all the include "debug_opt.h".
I will do it later, but I have some modifications to finish before I can do it.
Sorry for the inconvenience.
Cheers,
Nico

Yeah, that's what I did - had to remove asserts as well, but then it worked :)
Cheers,
Bart

Happy new year ! And happy coding :)

Happy New Year and lots of fun and satisfaction from coding, sharing and contributing! :)

Hi Bart, how are you ?
Do you know if it is possible to change the tabs from 8 spaces to 4 spaces in github when viewing a file ?  I noticed that some of my commits are not displayed correctly, because I used 4 spaces tabs in visual studio.
An example of file with this problem is blue_noise_generator_parameters.cpp, as an example.
Cheers,
Nico

Hey Nico!
Beginning of the year has been pretty crazy for me, but I'm managing and hopefully will be back to blogging and open source work soon. :)
I'll be honest, I have no idea how to change settings on github... Only think I found is this: http://stackoverflow.com/questions/8833953/how-to-change-tab-size-on-github/23522945#23522945 so it can be changed when viewing, but not per whole repository.
Cheers,
Bart


[CERT-TEST-FAILURE] Ble-Thread Fails For Python

Feature Area
Other
Test Case
TC-RR-1.1
Reproduction steps
Command to run this Python Testcases: python3 TC_RR_1_1.py  --commissioning-method ble-thread --discriminator 3840 --passcode 20202021 --thread-dataset-hex 0e08000000000001000035060004001fffe00708fd99434432b35eab0c0402a0f7f8051000112233485566778899aabbccddeeff030f4f70656e54687265616444656d6f7404105fb16125077f91d910f8801ef67f283200030000100208111181112222222201021237 --ble-interface-id 0 -storage-path admin_storage.json --paa-trust-store-path ../../credentials/development/paa-root-certs/
Bug prevalence
Whenver I Do this
GitHub hash of the SDK that was being used
548e4f3de32053abe44854c35882bbc354f0538a
Platform
nrf, python
Anything else?
Ble-Thread pairing is fails in the python testcases for example the TC-RR-1.1 testcase has been run with the ble-thread pairing but it is failed in the commissioning with the error:

Traceback (most recent call last):
File "/home/ubuntu/connectedhomeip/no/lib/python3.10/site-packages/mobly/base_test.py", line 783, in exec_one_test
test_method()
File "/home/ubuntu/connectedhomeip/src/python_testing/matter_testing_support.py", line 1336, in test_run_commissioning
if not self._commission_device(commission_idx):
File "/home/ubuntu/connectedhomeip/src/python_testing/matter_testing_support.py", line 1369, in _commission_device
return dev_ctrl.CommissionThread(
File "/home/ubuntu/connectedhomeip/no/lib/python3.10/site-packages/chip/ChipDeviceCtrl.py", line 1785, in CommissionThread
return self.ConnectBLE(discriminator, setupPinCode, nodeId)
File "/home/ubuntu/connectedhomeip/no/lib/python3.10/site-packages/chip/ChipDeviceCtrl.py", line 441, in ConnectBLE
).raise_on_error()
File "/home/ubuntu/connectedhomeip/no/lib/python3.10/site-packages/chip/native/init.py", line 67, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
[MatterTest] 01-12 09:44:34.591 INFO [Test] test_run_commissioning ERROR
[MatterTest] 01-12 09:44:34.604 INFO Summary for test class CommissionDeviceTest: Error 1, Executed 1, Failed 0, Passed 0, Requested 1, Skipped 0

Reference log:
tc-rr-1-1.txt
Note: Due to this issue it is also failing in TH as well.

This issue has been resolved in lasest commit: f59323b0303e90dc4158acd44f115beabfcba89b


Fix swagger-schema-official JSON import

I ran into an issue with swagger-parser using node v7.5.0 and Typescript 2.1.6 where swagger-schema-official/schema couldn't be required. Adding .json to the require statement fixes the problem.

Thanks for the fix!


MikhaelTovel

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[core-auth] [Identity] Added an optional property correlationId to the GetTokenOptions

The new Identity gives users the ability to configure getTokenOptions, however that wasn't exposed since the credentials rely on this type from core-auth.
Though we could add this on Identity as a separate type, I believe we should add this property to core-auth.

The new Identity gives users the ability to configure getTokenOptions

Where do we allow this? From what I can see, users can configure TokenCredentialOptions which is different from GetTokenOptions

Closing as per https://github.com/Azure/azure-sdk-for-js/pull/14869#pullrequestreview-636192625

I didn’t mean to close this.
This is on master: https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/identity/identity/src/msal/nodeFlows/nodeCommon.ts#L233
we need correlationId on getTokenOptions to allow users to configure it

Hey @sadasant
Apologies, I closed this PR as my assumption was that we had opened this based on the requirements in #14869 which was closed.

we need correlationId on getTokenOptions to allow users to configure it

From what I know, getToken() is called by @azure/core-http and users never call it directly. So, can you elaborate on how we expect users to configure it? Perhaps I am missing something...
Or by users, are you referring to @azure/core-http itself? For example, take the case of an end user using our Key Vault Keys package. Each request gets assigned a unique id in core-http unless the user overrides it by setting the header x-ms-client-request-id themselves. Are we saying that to ensure that this value flows through to MSAL, we need GetTokenOptions to include correlationId? If yes, then why should this be called correlationId in GetTokenOptions while every where else in our core packages, we call it requestId?
If we do re-open this PR to indeed add a new property for this purpose, it should also be coupled with the below changes as they are all related. Otherwise, changes just to the GetTokenOptions interface does not change anything on its own

removing the same from CredentialFlowGetTokenOptions in @azure/identity because it extends GetTokenOptions anyway.
changes to @azure/core-http to actually pass the requestId to the getToken() call

Also, I tried to look for the same feature (requestId of a request should get passed to getToken()) in other languages, and it looks like there is a gap

In .NET, getToken() takes TokenRequestContext which in turns has a ParentRequestId
In Java, there is a similar TokenRequestContext but without the requestId
In Python, getToken() takes scopes and kwargs. Not sure if the kwargs contains the requestId

This is worth discussing with the rest of the feature crew to see what the expectation is

@ramya-rao-a
Thanks, there is indeed a gap.
This correlation ID is currently not being properly sent through in our pipelines, but it has meaningful consequences for our users. They will see this random value on requests, and without this they won't be able to use it.
Some users  come to the Identity package similar to how they would come to the MSAL packages, looking for a way to authenticate against Azure clouds without having to worry about SDK clients. For these users, this property is clearly missing in Identity and not missing in MSAL.
From my perspective, trying to provide comprehensive support for Identity, this feature has minimal costs to us while it allows us to provide a less variable behavior, so I see this is a feature as worth having, even if the rest of the environment isn't ready for it.

Thanks for the additional insights on scenarios where users may indeed use the @azure/identity directly.
This is still an addition to the public API surface and should go through the usual process of API proposal in the feature crew, decision on a name to align with all languages and review with the API board rather than a direct PR to update the code. Please log a tracking issue for the next milestone.


Adding the SqlJson type

Fixes https://github.com/dotnet/SqlClient/issues/2665
Brings in the SqlJson implementation along with the tests.
The ref will be updated https://github.com/dotnet/SqlClient/issues/2670 closer to the release.

This PR cannot be merged, since the tests which work with package reference would fail to compile.
We will merge this in, when we start to modify the ref assemblies on the main branch, which will make sense after the TDS protocol is documented.

Do we still need this PR?
@saurabh500 @apoorvdeshmukh @deepaksa1

Do we still need this PR? @saurabh500 @apoorvdeshmukh @deepaksa1

We have already merged the SqlJson class in a separate PR. I think this one can be dropped

[like]  Apoorv Deshmukh reacted to your message:

From: Deepak Saini @.>
Sent: Sunday, October 6, 2024 7:22:39 PM
To: dotnet/SqlClient @.>
Cc: Apoorv Deshmukh @.>; Mention @.>
Subject: Re: [dotnet/SqlClient] Adding the SqlJson type (PR #2734)
Do we still need this PR? @saurabh500https://github.com/saurabh500 @apoorvdeshmukhhttps://github.com/apoorvdeshmukh @deepaksa1https://github.com/deepaksa1
We have already merged the SqlJson class in a separate PR. I think this one can be dropped
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/SqlClient/pull/2734#issuecomment-2395552601, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABMWK35HRWASWTELA3J6Z3LZ2GEX7AVCNFSM6AAAAABLXBY5TKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGU2TENRQGE.
You are receiving this because you were mentioned.Message ID: @.***>


background job fails when trying to update

Description
At some point one or two of my docker containers running portus was down while I was doing work, so new images got pushed in, but did not show up in the portus web interface. Once I got everything up and running, NEW images with new tags will show up, but the old ones do not. I tried to configure the background container to use the "update" strategy, but now when it looks and tries to do the update it errors out, crashes and restarts.
Here is the error message it gives:
/srv/Portus/lib/portus/registry_client.rb:92:in `calculate_tag_size': undefined method `[]' for nil:NilClass (NoMethodError)
	from /srv/Portus/lib/portus/registry_client.rb:75:in `manifest'
	from /srv/Portus/app/models/repository.rb:263:in `block in create_tags'
	from /srv/Portus/app/models/repository.rb:260:in `each'
	from /srv/Portus/app/models/repository.rb:260:in `create_tags'
	from /srv/Portus/app/models/repository.rb:224:in `create_or_update!'
	from /srv/Portus/lib/portus/background/sync.rb:113:in `block in update_registry!'
	from /srv/Portus/lib/portus/background/sync.rb:108:in `each'
	from /srv/Portus/lib/portus/background/sync.rb:108:in `update_registry!'
	from /srv/Portus/lib/portus/background/sync.rb:68:in `block (2 levels) in execute!'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:267:in `block in transaction'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/transaction.rb:239:in `block in within_new_transaction'
	from /usr/lib64/ruby/2.6.0/monitor.rb:230:in `mon_synchronize'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/transaction.rb:236:in `within_new_transaction'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:267:in `transaction'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/transactions.rb:212:in `transaction'
	from /srv/Portus/lib/portus/background/sync.rb:68:in `block in execute!'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:70:in `block (2 levels) in find_each'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:70:in `each'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:70:in `block in find_each'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:136:in `block in find_in_batches'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:238:in `block in in_batches'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:222:in `loop'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:222:in `in_batches'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:135:in `find_in_batches'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/relation/batches.rb:69:in `find_each'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/activerecord-5.2.3/lib/active_record/querying.rb:11:in `find_each'
	from /srv/Portus/lib/portus/background/sync.rb:62:in `execute!'
	from /srv/Portus/bin/background.rb:61:in `block (2 levels) in <top (required)>'
	from /srv/Portus/bin/background.rb:58:in `each'
	from /srv/Portus/bin/background.rb:58:in `each_with_index'
	from /srv/Portus/bin/background.rb:58:in `block in <top (required)>'
	from /srv/Portus/bin/background.rb:57:in `loop'
	from /srv/Portus/bin/background.rb:57:in `<top (required)>'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/commands/runner/runner_command.rb:38:in `load'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/commands/runner/runner_command.rb:38:in `perform'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/command/base.rb:65:in `perform'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/command.rb:46:in `invoke'
	from /srv/Portus/vendor/bundle/ruby/2.6.0/gems/railties-5.2.3/lib/rails/commands.rb:18:in `<top (required)>'
	from bin/rails:12:in `require'
	from bin/rails:12:in `<main>'

This is based on the docker-compose file for ssl with clair and the opensuse/portus:head image.

I'm having exactly the same problem with the latest image. Are you also using Docker Registry 2.7?

Same here

Ok, I think I have an idea here, based on the env variable PORTUS_BACKGROUND_SERVICE_FQDN this remark I made :
https://github.com/SUSE/Portus/issues/2243#issuecomment-565889410
The idea is that if your background container is down and not receiving (and sending back confirmation), and we make sure the portus container never gets any HTTP REQUEST notifications from the registry (a webhook), then the registry will keep sending the webhooks notifying about those entries you guys want to "update" after bringing back background service.
And the docker registry WILL keep retrying sending those notifications, all of them, until background is up n running.
Alright, I see here that the number one priority about Portus Monitoring, is to monitor the background process, and the notification flow in full details, using elastic stack, grafana and prometheus.


Is this repo abandoned?

Looks like there's been no commits or releases for at least a year?

@kylebebak Are there plans to continue work on this package?

It appears like this repo is abandoned. Here are the instructions how to maintain a copy of this package for your own project. It ended up taking just a bit of extra effort.

Prerequisites

Install and set up patch-package in your project
Fork this repo; we'll use example as its new destination

Set Up
In a new terminal window:

git clone git@github.com:example/react-dropzone-uploader.git
cd react-dropzone-uploader
npm install

Develop

Make the necessary changes to the files in src
npm run build

Patch

Switch to the terminal window at the root of your project
Copy the freshly-built dist/ folder to your project's node_modules/react-dropzone-uploader:rm -rf node_modules/react-dropzone-uploader/dist
cp -r path/to/react-dropzone-uploader/dist node_modules/react-dropzone-uploader

npm run postinstall -- react-dropzone-uploader

Share

Commit your changes to the forked react-dropzone-uploader
Push your changes

I also recommend turning off the minifier on the newly forked repo. This way your patches are more obvious:
 webpack.build.config.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/webpack.build.config.js b/webpack.build.config.js
index 6636b27..7bff398 100644
--- a/webpack.build.config.js
+++ b/webpack.build.config.js
@@ -12,7 +12,7 @@ function createConfig(entry, output) {
     entry,
     output,
     optimization: {
-      minimizer: [new UglifyJSPlugin()],
+      minimize: false,
     },
     module: {
       rules: [

It appears like this repo is abandoned. Here are the instructions how to maintain a copy of this package for your own project. It ended up taking just a bit of extra effort.

Prerequisites

Install and set up patch-package in your project
Fork this repo; we'll use example as its new destination

Set Up
In a new terminal window:

git clone git@github.com:example/react-dropzone-uploader.git
cd react-dropzone-uploader
npm install

Develop

Make the necessary changes to the files in src
npm run build

Patch

Switch to the terminal window at the root of your project
Copy the freshly-built dist/ folder to your project's node_modules/react-dropzone-uploader:rm -rf node_modules/react-dropzone-uploader/dist
cp -r path/to/react-dropzone-uploader/dist node_modules/react-dropzone-uploader

npm run postinstall -- react-dropzone-uploader

Share

Commit your changes to the forked react-dropzone-uploader
Push your changes

I also recommend turning off the minifier on the newly forked repo. This way your patches are more obvious:
 webpack.build.config.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/webpack.build.config.js b/webpack.build.config.js
index 6636b27..7bff398 100644
--- a/webpack.build.config.js
+++ b/webpack.build.config.js
@@ -12,7 +12,7 @@ function createConfig(entry, output) {
     entry,
     output,
     optimization: {
-      minimizer: [new UglifyJSPlugin()],
+      minimize: false,
     },
     module: {
       rules: [

welp looks like im gonna be switching to a diff project