Security risks reported by scan for debian

We have performed blackduck scan on mcr.microsoft.com/azure-functions/python:4-python3.10, it reported below 3 high security risks with debian. Please check and help to resolve these risks -

Common Unix Printing System (CUPS) 1.2.7
Linux Kernel 5.10.140
Linux Kernel 5.10.149

We are investigatingon this  But you can try below options.
The security risks you mentioned are related to the Debian packages used in the mcr.microsoft.com/azure-functions/python:4-python3.10 image. To address these risks, you have a few options:
Keep the base image up to date: Check if there are newer versions of the mcr.microsoft.com/azure-functions/python image available that address these security vulnerabilities. Microsoft regularly updates their base images to include the latest security patches and fixes. You can pull the latest version of the image and rebuild your application using that.
Apply security patches: If updating the base image is not feasible, you can manually patch the specific packages mentioned in the security report. For example, you can use the apt package manager to update the CUPS package and the Linux kernel packages to their latest versions. You can run the following commands in your Dockerfile:
Dockerfile
Copy code
RUN apt-get update && apt-get install -y cups
RUN apt-get update && apt-get upgrade -y linux-image-5.10.140 linux-image-5.10.149
This will install the latest version of CUPS and upgrade the Linux kernel packages to the specified versions.
Use alternative base images: If you're concerned about the security risks associated with the base image, you can consider using alternative base images that are regularly updated and maintained by the community. For example, you can use the official Python Docker images provided by the Python Software Foundation (python:), which are frequently updated and include security patches.
It's important to regularly monitor and update your Docker images to address any security vulnerabilities. Additionally, consider implementing other security best practices, such as using minimal and purpose-specific images, following the principle of least privilege, and regularly scanning and monitoring your containerized applications for security risks

@pragnagopa  pls comment  and validate


Kong 2.1.2 CE, ERROR: bin/busted:58: module 'busted.runner' not found

I receive the following error:
Kong version: 2.1.2
ERROR: bin/busted:58: module 'busted.runner' not found:No LuaRocks module found for busted.runner
	no field package.preload['busted.runner']
	no file '/usr/local/openresty/site/lualib/busted/runner.ljbc'
	no file '/usr/local/openresty/site/lualib/busted/runner/init.ljbc'
	no file '/usr/local/openresty/lualib/busted/runner.ljbc'
	no file '/usr/local/openresty/lualib/busted/runner/init.ljbc'
	no file '/usr/local/openresty/site/lualib/busted/runner.lua'
	no file '/usr/local/openresty/site/lualib/busted/runner/init.lua'
	no file '/usr/local/openresty/lualib/busted/runner.lua'
	no file '/usr/local/openresty/lualib/busted/runner/init.lua'
	no file '/kong-plugin/busted/runner.lua'
	no file '/kong-plugin/busted/runner/init.lua'
	no file './busted/runner.lua'
	no file '/usr/local/openresty/luajit/share/luajit-2.1.0-beta3/busted/runner.lua'
	no file '/usr/local/share/lua/5.1/busted/runner.lua'
	no file '/usr/local/share/lua/5.1/busted/runner/init.lua'
	no file '/usr/local/openresty/luajit/share/lua/5.1/busted/runner.lua'
	no file '/usr/local/openresty/luajit/share/lua/5.1/busted/runner/init.lua'
	no file '/root/.luarocks/share/lua/5.1/busted/runner.lua'
	no file '/root/.luarocks/share/lua/5.1/busted/runner/init.lua'
	no file '/usr/local/openresty/site/lualib/busted/runner.so'
	no file '/usr/local/openresty/lualib/busted/runner.so'
	no file './busted/runner.so'
	no file '/usr/local/lib/lua/5.1/busted/runner.so'
	no file '/usr/local/openresty/luajit/lib/lua/5.1/busted/runner.so'
	no file '/usr/local/lib/lua/5.1/loadall.so'
	no file '/root/.luarocks/lib/lua/5.1/busted/runner.so'
	no file '/usr/local/openresty/site/lualib/busted.so'
	no file '/usr/local/openresty/lualib/busted.so'
	no file './busted.so'
	no file '/usr/local/lib/lua/5.1/busted.so'
	no file '/usr/local/openresty/luajit/lib/lua/5.1/busted.so'
	no file '/usr/local/lib/lua/5.1/loadall.so'
	no file '/root/.luarocks/lib/lua/5.1/busted.so'
stack traceback:
	bin/busted:58: in function 'file_gen'
	init_worker_by_lua:49: in function <init_worker_by_lua:47>
	[C]: in function 'xpcall'
	init_worker_by_lua:56: in function <init_worker_by_lua:54>

2.1.2 release is imminent / currently running through CI. Could you try with 2.1.1 in the meantime KONG_VERSION=2.1.1

I receive pongo test failures for my unit tests with 2.1.1 and 2.1.0 but not 2.0.5. I'm hoping 2.1.2 is business as usual. I'll RCA concurrently while I wait for the release.
Can you ping this thread once 2.1.2 is available? TIA

I have resolved my issue. Thanks for the quick responses!

I removed the 2.1.1 commits and force pushed the update to master.
@GordonMcKinney how did you resolve the issue? was the problem with the 2.1.1, or was it something on your end?

typically this is an image build failure, see #241


Bisect should fail fast if ordering is not stable

I encountered an oddly failing test suite this morning, so I fired up rspec bisect and went to get breakfast once it started running. When I came back, this was the output I encountered:
$ rspec --bisect
Bisect started using options: ""
Running suite to find failures... (4 minutes 32.5 seconds)
Starting bisect with 8 failing examples and 1585 non-failing examples.
Checking that failure(s) are order-dependent... failure appears to be order-dependent

Round 1: bisecting over non-failing examples 1-1585 .

Bisect failed!

The example ordering is inconsistent. `--bisect` relies upon consistent ordering (e.g. by passing `--seed` if you're using random ordering) to work properly.

Is there a way to determine that I forgot to stabilize the order before running the initial test suite pass and fail the operation quickly and before the first 5 minute test suite run?

In the general case no, since the ordering strategy is customizable and is opaque to bisect short of actually trying the tests.
That said, we could possibly inspect the configuration to look for some combination of seed and default random ordering and issue a warning. However I think this would be too complicated/prone to error to be worthwhile adding, given the number of ways an ordering can be specified (CLI, configuration, metadata).
Maybe though a heuristic of "warn if --seed argument is not present in CLI args" is good enough? Are there any cases where you specifically wouldn't want to set one (even if just to get rid of the warning)? I wouldn't want to expand the scope of the configuration API to cover it. The coordinator has access to the original CLI args already...
Possible next steps:

Proof-of-concept PR.
Additional opinions about whether effectively requiring seed for warning-less bisect is acceptable.

Maybe though a heuristic of "warn if --seed argument is not present in CLI args" is good enough?

I think it would be frustrating for the folks who don't use random ordering.  --bisect can be used with the default defined ordering, in which case a seed should not be provided.  IMO, we shouldn't issue a warning from the lack of a --seed under the (potentially mistaken) assumption that the user must be using random ordering (and therefore the lack of a seed is problematic).  It's confusing for a user to get a warning when they are doing something completely OK.

follow on: we probably should detect if the entire example tree is going to be consistently ordered before proceeding with a bisect. That is:

if all example groups use default ordering, we are done
if any example groups or the entire suite use random ordering, check if a seed is provided.

@samphippen while that is a complete solution, I think it's more complex than we need.  For the general case, we already detect inconsistent ordering, we just don't pre-detect it as @derekprior is requesting. IMO, it's sufficient to only detect the problem for the common case of someone using random ordering (set on RSpec.configure; ultimately, CLI options or options in .rspec get copied there) and not setting a seed.  It's pretty easy to detect RSpec.configuration.order == :random && RSpec.configuration.seed.nil? and warn in that case, with no need to look at any example groups.  There are some complex, non-standard cases where the user is applying random ordering to only some example groups that this won't detect, but we'll still catch the issue there later on, and I don't think such a complex case is sufficiently common to warrant anything more than that.


Add constant-encoded vectors

Picking up on @save-buffer work done here: https://github.com/facebookincubator/velox/pull/4113
Rebased on top of latest main
Add support for complex types (ROW, MAP, ARRAY)

Hi @richtia , I have merged constant and dictionary changes from these PRs (https://github.com/facebookincubator/velox/pull/3859). Can you rebase against main and I will take a look .

Hi @richtia , I have merged constant and dictionary changes from these PRs (#3859). Can you rebase against main and I will take a look .

Thanks!  Just rebased and resolved the conflicts.


Feat/native federation retry logic

Description
Retry logic for native federation typescript
Related Issue
From this thread: https://github.com/module-federation/universe/pull/1539#issuecomment-1925353074
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist

[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] I have updated the documentation.

Can we implement the federation/runtime into native federation? or move native fed into the SDK layer
we already have tons of functionality here and i think its like 4-6 functions that need to be connected and its done

@ScriptedAlchemy Can you argue a bit? To be honest I would avoid mixing things.
These plugins actually do a single thing and do it well, I would keep them segregate from the rest to be also evolved easily.


Camera aspect ratio

the camera_stream tile doesn't appear to respect the aspect ratio of the camera stream - it shrinks horizontally to fit resulting in the aspect ratio being wrong - could this be padded to preserve the aspect ratio?
types.camera:

types.camera_stream:

You simply need to change objFit:
https://developer.mozilla.org/en-US/docs/Web/CSS/object-fit

@resoai where do I need to specify this?

You'll find it referenced on https://github.com/resoai/TileBoard/blob/master/TILE_EXAMPLES.md


How to change the JFoenix date picker's arrow button's background by using CSS?

I want to change the background of this date swapping button by using CSS. Do you have any suggestion?

That arrow is a jfx-button so you can do this:
.jfx-date-picker .jfx-button{     -fx-background-color: red; }

Thank you very much Mr. JFoenix.💚
Can I email you when I have a problem?

From: Acapetahua<EMAIL_ADDRESS>Sent: Tuesday, June 26, 2018 10:35 PM
To: jfoenixadmin/JFoenix
Cc: Panduka Nandara; Author
Subject: Re: [jfoenixadmin/JFoenix] How to change the JFoenix date picker's arrow button's background by using CSS? (#763)
That arrow is a jfx-button so you can do this:
.jfx-date-picker .jfx-button{ -fx-background-color: red; }
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/jfoenixadmin/JFoenix/issues/763#issuecomment-400390858, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AjiMszt-Fh8UwlNkzXdyFqcqg-ZTTT6Fks5uAmnOgaJpZM4Uye2p.

Well i am actually not Mr. JFoenix and i know simple things i help the community as much as i can.


Compatibility with flutter

I'm new to dart & flutter, but from what I understand your lib can't be used in flutter because it uses mirrors? Would a flutter-friendly branch be complicated? I'm sure there would be a large audience.  I tried removing references to mirror in your code but couldn't even get past the class declaration with the following error
Inconsistent declarations of 'cast' are inherited from <RV,RV>() [] Map <RV,RV>, <R>() [] Iterable<R>

@b354c502 This package is not compatible with Strong Mode, which is default in Dart 2.0 and thus also in the new version of Flutter. As such, I would advise against using this package in the future. You can use the regular JSON.decode() from the dart:convert package.

@stevenroose that's a shame, but thanks for the quick clarification


Create About section in Home Page

-Create a flexible Home Page section.
-It should include animations.
-There should be color transitions in the header section.

Please a good description

This issue has been postponed to a later date because it has not been completed


fix having clause do not works correct with same alias name

Proposed changes
Issue Number: close #15142
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.36 seconds
load time: 645 seconds
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221216152051_clickbench_pr_64549.html

please add regression test

please add regression test

done


Fix formatting, whitespace, markdownlint (#9)

To fix the problem, we should avoid constructing the shell command by concatenating strings. Instead, we should use the execFileSync method from the child_process module, which allows us to pass the command and its arguments separately. This approach ensures that the arguments are not interpreted by the shell, thus preventing any unintended behavior due to special characters in the file path.
We need to modify the code in index.test.js to use execFileSync instead of execSync. Specifically, we will change the construction of the command to pass the file path as an argument.


Automatic PR from RestAPI-PR981

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/981

Codecov Report

Merging #1017 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master    #1017   +/-   ##
=======================================
  Coverage   57.84%   57.84%
=======================================
  Files        1933     1933
  Lines       53454    53454
=======================================
  Hits        30919    30919
  Misses      22535    22535

Impacted Files
Coverage Δ

...onitor/azure/mgmt/monitor/models/metric_trigger.py
38.46% <ø> (ø)
:white_check_mark:

...-monitor/azure/mgmt/monitor/models/scale_action.py
55.55% <ø> (ø)
:white_check_mark:

.../mgmt/monitor/operations/alert_rules_operations.py
17.24% <ø> (ø)
:white_check_mark:

...onitor/azure/mgmt/monitor/models/scale_capacity.py
62.5% <ø> (ø)
:white_check_mark:

...onitor/models/rule_management_event_data_source.py
29.41% <ø> (ø)
:white_check_mark:

...nitor/azure/mgmt/monitor/models/metric_settings.py
62.5% <ø> (ø)
:white_check_mark:

...tor/azure/mgmt/monitor/models/autoscale_profile.py
50% <ø> (ø)
:white_check_mark:

...onitor/operations/autoscale_settings_operations.py
17.24% <ø> (ø)
:white_check_mark:

...or/azure/mgmt/monitor/models/recurrent_schedule.py
55.55% <ø> (ø)
:white_check_mark:

...onitor/azure/mgmt/monitor/models/incident_paged.py
80% <ø> (ø)
:white_check_mark:

... and 37 more

Continue to review full report at Codecov.

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

Already fixed


Add support for creating reproducers on OpenBSD

First stab at adding support for reproducers on OpenBSD, as discussed in #790.

So, this supersedes #790, right? @blackgnezdo

Yeah, this one is largely overlapping. Neither one is fully addressing the problem on broken tests/builds on CI. I took it past the point of broken tests and straight into inability to produce executor for OpenBSD target
mkdir -p ./bin/openbsd_amd64
c++ -o ./bin/openbsd_amd64/syz-executor executor/executor.cc \
		-pthread -Wall -Wframe-larger-than=8192 -Wparentheses -Werror -O2 -m64 -static -lutil  \
		-DGOOS_openbsd=1 -DGOARCH_amd64=1  -DGIT_REVISION=\"c4122a2f86bf16d31791f09d28310e1b30a720c8\"
In file included from executor/common.h:383:0
                 from executor/executor.cc:137:
executor/common_bsd.h:24:18: fatal error: util.h: No such file or directory
 #include <util.h>
                  ^
compilation terminated.


[Pulumi] Recreate tutorial

Summary
Replaces #16173

@desteves, mind taking a look at the preview to confirm I've moved it over successfully?


"Stupid" users can crash Chrome when uploading

Hi.
Looking at the official example: http://jsfiddle.net/danialfarid/s8kc7wg0/400/ (Drop and upload with $watch). (verified in Chorme across several machines and Windows versions, not reproducible in Edge)
If you press the dropfile area, to open the "open" dialog, then proceed to drag images over in the dropfile area and while they are processing, close the dialog with the "open" button, then the page crashes the browser.

Any suggestions on how to work around?

Works fine on my box (Win10, Chrome51) - the file is processed twice, but no crash happens.

Just checked again. Problem still there Win10 / Chrome52.
Not that is does not crash pr say, the browser hangs (like stuck in a loop)
Reproduction:
Press the drop area to open the dialog
Select multiple files (images?) from the "open" dialog and drag them over to the drop area.
While the dragged files are processing immediately hit "open"-button in the "open"-dialog
Browser hangs immediately after this

OK I can confirm it hangs the browser when using the latest reproduction steps (Win10, Chrome52).

Not much to be done on the module level. It is more like a browser bug.


git-cliff-core: allow adding arbitrary values to commits

Is there an existing issue or pull request for this?

[X] I have searched the existing issues and pull requests

Feature description
First of all thank you for the amazing crate and the hard work you put into it 🙏
I would like to attach a remote context to the commit, so that people can write commit.remote.username in release-plz changelog (which is similar to commit.github.username git-cliff equivalent.
Even though I can't have commit.remote I tried enabling the "github" feature and my Cargo.lock exploded because of many dependencies to retrieve remote info I'm not using (because I'm retrieving remote info by myself). So I would like to have a "lighter" way to add arbitrary fields to the commit object.
So a very similar mechanism to https://github.com/orhun/git-cliff/pull/613 but limited to the commit object.
Desired solution
The Commit struct could have a Map of <String, Json> (this is psudo-code). In my example, "String" is remote and Json is { author }.
Library users should be able to add any fields they like to it.
Alternatives considered
The alternative is rely entirely on git-cliff for commits remote info retrieval.
My issue is that I generate multiple changelogs that share some commits, so we would hit GitHub API multiple times for the same commits for no reason.
We could solve this by implementing https://github.com/orhun/git-cliff/issues/468 but I'm not sure if it's easier than this issue.
Also, with this approach, the following problems remain:

I would like to have commit.remote instead of commit.github, commit.gitea, etc. (unless you change my mind that commit.github is a better idea 👀)
I prefer to avoid adding all those dependencies because release-plz already takes a while to compile 😵

Additional context
PR where I experimented: https://github.com/MarcoIeni/release-plz/pull/1630
Also, I'm curious, why you have commit.github, commit.gitea, etc instead of a unified solution (e.g. commit.remote)?

I just thought about the simplest solution to my issue: the Commit struct adds a remote field as Option. This field is not behind a feature flag (so I don't need to pull other dependencies).
Of course it's not a generic solution 👍

Hello Marco 👋🏼

The Commit struct could have a Map of <String, Json> (this is psudo-code). In my example, "String" is remote and Json is { author }.

Would that work? Is serde serializing keys as separate fields?
Btw can you take a look at #784 which does something similar (adds a new field called extra). Maybe we can tweak PR a bit to satisfy this use case too.

Also, I'm curious, why you have commit.github, commit.gitea, etc instead of a unified solution (e.g. commit.remote)?

There is a stale PR #688 which greatly simplifies that module.

Would that work? Is serde serializing keys as separate fields?

I guess we would need to do what the linked PR is doing 👍

(adds a new field called extra). Maybe we can tweak PR a bit to satisfy this use case too.

Yeah, I would need something like that, but without typing extra. So as the remote HashMap 👍

This feels like a bit of a workaround and is specific to release-plz's use case.
Maybe we should deprecate individual remote-related fields and instead support commit.remote, as you've suggested. That way, we wouldn't need to make small tweaks in the library like this.

Sounds good to me as long as the remote field is not behind a feature flag that pulls other dependencies 👍

Yup, please go ahead.


Query using a subquery with sql

What steps will reproduce the problem?
$testQuery = Entity::findBySql("select entity.id from entity where entity.parent_id is null and entity.status = 10");
$test = Entity::find()->andWhere(['id' => $testQuery])->count();

What is the expected result?
SELECT COUNT(*) FROM `entity` WHERE `id` IN (select entity.id from entity where entity.parent_id is null and entity.status = 10)

What do you get instead?
SELECT COUNT(*) FROM `entity` WHERE `id` IN (SELECT * FROM `entity`)

This seems to come from https://github.com/yiisoft/yii2/blob/f388ca71b08b89e940f1ffbe4afa19ae9d5e115f/framework/db/QueryBuilder.php#L227 not taking into account the possibility of Query already having sql in place.
It should do a similar check to this:
https://github.com/yiisoft/yii2/blob/f388ca71b08b89e940f1ffbe4afa19ae9d5e115f/framework/db/ActiveQuery.php#L351
Additional info

Q
A

Yii version
2.0.46

PHP version
7.0.33

Operating system
Docker php:7.0-fpm image

$testQuery = new \yii\db\Expression("select entity.id from entity where entity.parent_id is null and entity.status = 10");
$test = Post::find()->andWhere("id in ({$testQuery})")->count();
// or
$testQuery = Entity::findBySql("select entity.id from entity where entity.parent_id is null and entity.status = 10");
$expression = new \yii\db\Expression($testQuery->sql);
$test = Post::find()->andWhere("id in ({$expression})")->count();

// or $testQuery = Entity::findBySql("select entity.id from entity where entity.parent_id is null and entity.status = 10"); $expression = new \yii\db\Expression($testQuery->sql); $test = Entity::find()->andWhere("id in ({$expression})")->count();

This is ok as long as You know that that specific query is crafted from raw SQL, however is very annoying to keep track of when this sort of query is an ActiveRecord class method for finding some other related models.


fix screenshot in chrome

https://stackoverflow.com/questions/2572333/google-chrome-window-open-workaround

The old threejs backend along with the screenshot button is intended to be deprecated soon. Closing this


[type:fix]fix logging plugin

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (97cb883) 61.93% compared to head (730e0cc) 61.79%.

Files
Patch %
Lines

...g/common/handler/AbstractLogPluginDataHandler.java
0.00%
6 Missing :warning:

...etmq/handler/LoggingRocketMQPluginDataHandler.java
92.30%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5348      +/-   ##
============================================
- Coverage     61.93%   61.79%   -0.15%
+ Complexity     8820     8810      -10
============================================
  Files          1260     1260
  Lines         38691    38707      +16
  Branches       3697     3696       -1
============================================
- Hits          23963    23918      -45
- Misses        12606    12658      +52
- Partials       2122     2131       +9

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


Node names inside pages get corrupted on copy-pase

Try to copy-paste stage1 page in the attached work.
Some of the nodes inside the page get "a" suffix as if there was a name conflict.

danilovesky at 2015-05-14T10:17:17Z:


AWS is sensitive to permissions inside .zip files

Firstly, thanks for Zappa, it's making my first steps into working with lambdas much easier. While I haven't quite got my application working fully yet, I did make an interesting discovery today.
It appears that not only can zip files contain unix permissions, but also that AWS is sensitive to these permissions when running code.
The result was that I was getting mysterious Unable to import module 'handler': No module named handler errors when trying to run my code, but after running chmod -R a+rX over my venv directory and re-redeploying, these went away and got replaced with a new yak for me to shave. :)
While this was a terribly obscure error to find, I'm hoping the solution is as straightforward as having zappa manually adjusting the permissions on the zipped files as they're added to the archive.
Many thanks again for a great tool!
~ Paul

Update: My new yak was also a permissions problem, since my application was still set to 0640. On the upside I've now verified that AWS care a lot about permissions. :)

Now this is a bug report.
In fact, we already address this for some files, but apparently not enough! Related: https://github.com/Miserlou/Zappa/blob/master/zappa/cli.py#L1455
Want to submit a PR to properly chmod the inside the lambda package creation code? :)

I would love to submit a PR, especially since this is a such a newbie-friendly change to make. Alas, I'm still bootstrapping myself into Python, and have an eye-wateringly full calendar over the next two weeks (four countries, three talks, two conferences, and one change of career), so I can't reasonably promise a PR in anything approaching a timely fashion.
If the bug is still open in 2017, then I'd love to submit a PR, since this would also be a great excuse for me to learn more about Python testing frameworks as well. :)

fwiw we had to deal with this same issue in another lambda provisioning project, fix for python zip usage https://github.com/capitalone/cloud-custodian/commit/6394043f90ee80495cefd5a6dbf5389ebdb42784

Just a +1 for this issue.
I hit this (using zappa==0.35.2) because I run with with umask=0077 as a habit (safety/paranoia holdover from the old days of true multi-user Unix environments with many users' home directories on the same NFS filesystem).

I believe this should be fixed now, the fix will be published in the next version update, which should happen quite soon.
@rjpcal - I'm curious about what you're using the project for - feel free to email me at<EMAIL_ADDRESS>if you'd like to chat more!


Ensure Delwaq receives correct network typology

see attachment. current status is not representing the Ribasim network correct

Fixed in #1519:

Oude tijden herleven. dit doet erg aan een DM model schematisatie denken

The original Edge geometries of this model nicely follow the waterways, but in model.to_xugrid we currently drop this information and preserve only the topology. We could probably add it to the datamodel under UGrid or Deltares conventions like done for reaches.


i18n Spanish translation updates

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

Changelog Entry
Description

The Spanish translation is not yet complete. This helps by translating more strings from English into Spanish

Added

New English strings translated into Spanish now

Fixed

Variable '{{ models }}' was translated to Spanish as '{{ modelos }}' which could cause issues if left as is

Additional Information

PR #2744 originally introduced the renaming of the '{{ models }}' variable into the Spanish '{{ modelos }}' which is fixed on this PR

Ready for review. Translated the latest strings into Spanish 😉

Closing due to conflict, feel free to reopen!

I've got to get my head down and learn/resolve this conflict 😉 No problem @tjbck. Thanks for the note.


Import path quick suggestions - jsconfig aliases not recognised

VSCode Version: 1.17.0
OS Version: macOS High Sierra 10.13

Reproduces without extensions: Yes
Doesn't work properly with aliases added in jsconfig.json https://code.visualstudio.com/docs/languages/jsconfig
Sample jsconfig.json
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "ClientApp/*": ["./ClientApp/*"]
    }
  }
}

Expected behaviour
import Something from 'ClientApp/...'

will pull path intellisense for folder ClientApp
Existing extension path-intellisense for example can also be configured with aliases in settings.json
"path-intellisense.mappings": {
    "ClientApp": "${workspaceRoot}/MvcProject/ClientApp",
  }

This issue was moved to Microsoft/TypeScript#19113


developed backend further, inc views and forms

Develops two main back-end files: forms.py and views.py
Also set dummy/blank templates to get it to run without errors. These templates will be fully developed in the next PR, so can ignore these for now. Just focus on the 2 Python files.

Mike happy to approve this as it all looked sensible to me. The main point of interest were the methods in exercises/views.py; I have gone through these but not tested them. In future do you require me to checkout the project to test the working prototype, or is it enough to read through the code?

thanks @garciaay for reviewing so promptly. no need to check it out, no, just reading the code is enough. I've ensured it runs without errors on my machine (hence the default templates to prevent missing template errors) and in the future I'll be adding Continuous Integration (CI) for various automated tests in the PR.

Thanks Mike, I am just starting on the Django test unit road - would appreciate a chat sometime as it sounds like you are further down that route


Base58Check; add mransan base58 for OPAM pinning

Implement the Base58Check algorithm, to replace base64 coding, eventually.
OPAM has a base58 package, but the two incompatible versions come from different authors. Put the mransan-authored version (0.1.0 in OPAM) in the repo for OPAM-pinning. That's the same version as used in coda_net2 (so it could be removed there after this PR is merged).

I think opam.export needs to be updated? But I'm not confident in my understanding of our build system.

I think opam.export needs to be updated?

I added that, though I think it's not really needed. I think if you follow the instructions in README-dev, you'll install the base58 0.1.0 from OPAM, and the subsequent pin will override that.
But we do that for digestif and sodium, so I made that change.


Default Repo Rules (RFC / discussion)

There's already a short list of rules in the readme: https://github.com/webosbrew/apps-repo/blob/main/README.md
The purpose of this issue is to discuss the rules and/or propose new ones.
I have some proposed additions:

Your app must be licensed under a recognized Open Source license.

Your app must not contain any obfuscated code.

Some sources of inspiration:
https://extensionworkshop.com/documentation/publish/add-on-policies/

I was tend to have permissive rules, such as allowing closed source application. But if we enforce open source rule in central repo, we can certainly lower the risk of providing malicious app.

Another idea: avoid porting desktop games/applications directly (not a hard requirement)

Another idea: avoid porting desktop games/applications directly (not a hard requirement)

You mean porting apps without adjusting for different input method / adding "TV-style" UX?

@Informatic Yes, also porting some apps like QEMU isn't a good idea. I think these are some guidelines instead of rules.

I was tend to have permissive rules, such as allowing closed source application. But if we enforce open source rule in central repo, we can certainly lower the risk of providing malicious app.

Yes. While I don't like restrictive rules in general, we have a certain amount of accountability if buggy/malicious code damages someone's TV. Being picky doesn't cost us anything.
I suspect a less-restricted public repo will pop up at some point, if there is sufficient demand, and I think that's a good thing (as long as people using it are aware of whatever risks they're taking). And of course, individual developers can still host their own repos.
It might be worth noting that the official Ubuntu repos are split into four seperate repos: (https://help.ubuntu.com/community/Repositories/Ubuntu)

Main - Canonical-supported free and open-source software.

Universe - Community-maintained free and open-source software.

Restricted - Proprietary drivers for devices.

Multiverse - Software restricted by copyright or legal issues.

I think we should aim to be like Ubuntu's "universe" repo, and allow the wider community to provide the rest.


type class inference for minor premises

Is it possible to automatically try to solve minor premises which are in square brackets by type class resolution?
Example: Pt in trunc.rec
  protected constant rec {n : trunc_index} {A : Type} {P : trunc n A → Type}
    [Pt : Πaa, is_trunc n (P aa)] (H : Πa, P (tr a)) : Πaa, P aa

Example usage currently:
-- HoTT
open is_trunc
attribute trunc.rec [recursor]

definition my_elim {n : trunc_index} {A : Type} {P : Type}
  [Pt : is_trunc n P] (H : A → P) : trunc n A → P :=
begin
  intro x, induction x,
  exact _,
  apply H, assumption
end

It is possible :-)

BTW, I'm assuming that if users do not want to solve a minor premise using type class resolution, then they should create another recursor where the minor premise does not have [ ].

That sounds fine. Thanks!


Remove LESS

To complete our transition from LESS to Sass, we need to remove all LESS files and remove the LESS option from the build system.

Removing this as a duplicate, we already have #56.


Mechanism for hiding anatomograms that misbehave in certain experiments

On certain experiments we have cases where the heatmap with cell type is empty even though we have data. If we don't manage to fix cases like this, we need a simple mechanism to hide anatomograms from certain experiments.

I'm going to close this since is redundant to #127

I'm going to close this since is redundant to #127


simple_hash_from_byte_slices should take a Vec instead of slice

Currently we have fn simple_hash_from_byte_slices(byte_slices: &[&[u8]]) -> Hash
But this leads to some complexities in the few places it's so far used:

https://github.com/interchainio/tendermint-rs/blob/10a3026cfbd4ab333752d344645a4f07ecdc29f7/tendermint/src/validator.rs#L23-L35
https://github.com/interchainio/tendermint-rs/pull/36/files#diff-a1644bb72a1c83c54d82738ef71ce095R126 (ie. the need for a separate variable followed by as_slice would go away)

Although it looks like a good idea, we should also consider that in Rust it is "more common to pass slices as arguments rather than vectors when you just want to provide a read access"
(ref: https://doc.rust-lang.org/std/vec/struct.Vec.html#slicing)
There is even a clippy warning about fn(&Vec) which we'd need to disable then: https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg
ref #59

Oh hmm. I was thinking we'd want Vec<Vec<u8>>. It seems justified since if I'm not mistaken these arguments are not used again and so can be moved and consumed by this function.
That said for the recursion we may want an inner function that deals in slices so we don't need to_vec everywhere!

@ebuchman you can always add a From impl that consumes (or creates) a Vec


Standardization of rep

Hi @FernandoCelmer, we need to adjust a few things first to move forward, ok? ✨
We need a separate .md with installation instructions to show the theme on the site.
I ask for these changes to standardize with the other repositories see an example; this is also important because it helps other potential users who would like to contribute too! 😁
Let me know if something isn't possible or if you have any questions! 🙂

Hello @luxonauta ,
I opened a pull request with the project's standardization changes.  You can validate if necessary by this link: https://github.com/dracula/mkdocs/pull/2

Awesome! 💜✨


yaml: disable resizing of the android's images

With the moulin 0.27 the handling of the option size for the raw_image was made compliant with the same for other types of the images.
This means that if the size is specified for the raw_image and the real image size is less, then we are trying to resize the real file size to the size. This approach works for ext4 images. But we found that raw_image with size is used for the android images. And mentioned change breaks the assembling of the android.img.
This commit explicitly disables resizing for the android images.
And min_ver is set to 0.27 due to usage of the resize option.

LGTM

Ack is added.
Ready to be merged.


Add component for arrays

The "Add to arrays" component allows the user to generate arrays of integers or floats with custom specifications. The user can choose the length of the arrays, the minimum and maximum value of each element, and the number of arrays to generate. Additionally, the user can specify whether to allow duplicates in the arrays or not.

Implemented the solution and tested it successfully. Closing the issue.


[Bug]: Segmentation fault on MacOS when using HuggingFaceEmbedding with FAISS

Bug Description
Seeing segmentation fault when running a minimal script with HuggingFaceEmbedding and FAISS. A simple import faiss is enough to trigger the failure in a new environment with nothing but llama-index-embeddings-huggingface and faiss-cpu installed.
$ poetry run python3 example.py
[1]    63240 segmentation fault  poetry run python3 example.py

Contents of example.py:
import faiss
from llama_index.embeddings.huggingface import HuggingFaceEmbedding
embed = HuggingFaceEmbedding(model_name="BAAI/bge-small-en-v1.5")
print("success")

As far as I can tell, the specific model passed to HuggingFaceEmbedding does not have an impact.
Potentially related to #9949, though that issue does not appear to relate to FAISS.
Version
0.10.51
Steps to Reproduce
From a fresh directory:

poetry init with Python 3.12 and click through init menu
poetry add llama-index-embeddings-huggingface faiss-cpu
poetry run python3 example.py (see contents of this file above)

Output:
$ poetry run python3 example.py
[1]    63995 segmentation fault  poetry run python3 example.py

If you remove the import faiss line from example.py, the output is as expected:
$ poetry run python3 example.py
success

Relevant Logs/Tracebacks
With DEBUG logging enabled:
poetry run python3 example.py
DEBUG:faiss.loader:Environment variable FAISS_OPT_LEVEL is not set, so let's pick the instruction set according to the current CPU
Environment variable FAISS_OPT_LEVEL is not set, so let's pick the instruction set according to the current CPU
INFO:faiss.loader:Loading faiss.
Loading faiss.
INFO:faiss.loader:Successfully loaded faiss.
Successfully loaded faiss.
INFO:sentence_transformers.SentenceTransformer:Load pretrained SentenceTransformer: BAAI/bge-small-en-v1.5
Load pretrained SentenceTransformer: BAAI/bge-small-en-v1.5
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): huggingface.co:443
Starting new HTTPS connection (1): huggingface.co:443
DEBUG:urllib3.connectionpool:https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/modules.json HTTP/11" 200 0
https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/modules.json HTTP/11" 200 0
DEBUG:urllib3.connectionpool:https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/config_sentence_transformers.json HTTP/11" 200 0
https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/config_sentence_transformers.json HTTP/11" 200 0
DEBUG:urllib3.connectionpool:https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/README.md HTTP/11" 200 0
https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/README.md HTTP/11" 200 0
DEBUG:urllib3.connectionpool:https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/modules.json HTTP/11" 200 0
https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/modules.json HTTP/11" 200 0
DEBUG:urllib3.connectionpool:https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/sentence_bert_config.json HTTP/11" 200 0
https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/sentence_bert_config.json HTTP/11" 200 0
DEBUG:urllib3.connectionpool:https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/config.json HTTP/11" 200 0
https://huggingface.co:443 "HEAD /BAAI/bge-small-en-v1.5/resolve/main/config.json HTTP/11" 200 0
[1]    64618 segmentation fault  poetry run python3 example.py

@dosu adding device="cpu" to the HuggingFaceEmbedding initialization did not fix the issue.


⚠ Bofrost.at has degraded performance

In 23d8931, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1380 ms

Resolved: Bofrost.at performance has improved in ab7ff15.


webpack live reload is not working.

I have installed the webpack but the live reload is not working , it is building the modules and caching it.
Linux 4.4.0-31-generic
node v6.2.2
npm  v3.10.5
angular-cli: 1.0.0-beta.11-webpack
node: 6.2.2
os: linux x64

Are you using the ng serve command or ng build --watch.
Both should work but I ask because we really need more information to accurately tackle this.

I am using ng serve

10% building modules 1/1 modules 0 active
*
*
NG Live Development Server is running on http://localhost:4200.
*
4318ms building modules
38ms sealing
0ms optimizing
0ms basic module optimization
16ms module optimization
1ms advanced module optimization
15ms basic chunk optimization
1ms chunk optimization
0ms advanced chunk optimization
0ms module and chunk tree optimization
58ms module reviving
5ms module order optimization
4ms module id optimization
3ms chunk reviving
0ms chunk order optimization
14ms chunk id optimization
26ms hashing
1ms module assets processing
71ms chunk assets processing
2ms additional chunk assets processing
1ms recording
0ms additional asset processing
127ms chunk asset optimization
864ms asset optimization
25ms emitting
Hash: 3eaa2255197a9b5cb5fd
Version: webpack 2.1.0-beta.18
Time: 5607ms
Asset       Size  Chunks             Chunk Names
main.bundle.js    2.18 MB    0, 2  [emitted]  main
polyfills.bundle.js     227 kB    1, 2  [emitted]  polyfills
inline.js    4.96 kB       2  [emitted]  inline
main.map    2.59 MB    0, 2  [emitted]  main
polyfills.map     294 kB    1, 2  [emitted]  polyfills
inline.map    5.13 kB       2  [emitted]  inline
index.html  476 bytes          [emitted]
.npmignore    0 bytes          [emitted]
Child html-webpack-plugin for "index.html":
Asset    Size  Chunks       Chunk Names
index.html  2.4 kB       0
webpack: bundle is now VALID.

I have the same problem with windows and webpack 2.1.0-beta.18
last entry is webpack: bundle is now VALID. for a fresh application.

I'm seeing the live reload working myself. Can you give very exact repro steps so we can see if there's something missing?

I am having the same issue after I cloned a project from my repo.
On my regular machine, I see a lot of something like "69% building modules 1054/1062 modules 8 active ..", etc.
But on my other machine, I only see this -
 ng serve
 10% building modules 1/1 modules 0 active
*
*
 NG Live Development Server is running on http://localhost:4200.
*
5134ms building modules
13ms sealing
0ms optimizing
0ms basic module optimization
43ms module optimization
1ms advanced module optimization
9ms basic chunk optimization
0ms chunk optimization
1ms advanced chunk optimization
0ms module and chunk tree optimization
89ms module reviving
2ms module order optimization
3ms module id optimization
4ms chunk reviving
0ms chunk order optimization
19ms chunk id optimization
19ms hashing
0ms module assets processing
56ms chunk assets processing
3ms additional chunk assets processing
0ms recording
0ms additional asset processing
131ms chunk asset optimization
1059ms asset optimization
22ms emitting
Hash: 101774096aac67c140a7
Version: webpack 2.1.0-beta.18
Time: 6621ms
              Asset       Size  Chunks             Chunk Names
     main.bundle.js    3.75 MB    0, 2  [emitted]  main
polyfills.bundle.js     232 kB    1, 2  [emitted]  polyfills
          inline.js    4.96 kB       2  [emitted]  inline
           main.map    4.42 MB    0, 2  [emitted]  main
      polyfills.map     295 kB    1, 2  [emitted]  polyfills
         inline.map    5.13 kB       2  [emitted]  inline
         index.html  877 bytes          [emitted]

Child html-webpack-plugin for "index.html":
         Asset     Size  Chunks       Chunk Names
    index.html  2.83 kB       0
webpack: bundle is now VALID.

Now, when I make any changes to my code, it doesn't reload.

If you can provide us with a repo where this behaviour happens, we can investigate. Otherwise I'm not really able to reproduce this behaviour.

I'm having same issue. My ng version is: angular-cli: 1.0.0-beta.11-webpack.2
ng serve works without live reload and ng build --watch only build the app and then quit without even serving the app on localhost

I'm having the issue for directories starting with '+'. ng serve and ng build -w works normally: they build the application and wait for changes. If I modify a file in a 'normal' directory (i.e. app.component.ts), the change is detected and ng rebuilds. If I modify a file in a directory whose name starts with '+', nothing happens.
I have an exception when I use gedit: when gedit saves a file, it creates a backup that triggers the reload. Reloads also works if I manually create a new file.

I renamed my directories to remove the '+' and in fact the problem happens with any subdirectory of app. If I modify anything directly inside src (i.e. index.html, main.ts, ...) reload works. If I modify something in a subdirectory of src (i.e. src/app/app.component.*, src/app/app.module.ts, src/assets, src/environments/environment.ts, ...) reload works as well. But if I modify something in a subdirectory of app (i.e. src/app/foo/foo.component.ts), there is no reload.
I can reproduce this with any repository. For example:
ng new project
cd project
ng g c foo
ng serve

Then open a browser on the application. Edit app.component.html as follow:

  {{title}}

<app-foo></app-foo>

Save: ng reloads the app.
Edit foo/foo.component.html as follow:

  foo works! ng reloads?

Save: ng does not reload.
@filipesilva Do you confirm you cannot reproduce following these steps?

I had the same issue, but managed to fix it. The problem might have to do with folder naming. At first, my main project folder (where I would navigate to before doing "ng serve") was named something like "XX (Front)". I renamed it to "XX_Front" (and flattened the folder structure) and live reload started working.

@osechet I followed your instructions and had a life reload be triggered when changing foo/foo.component.html.
I'm using beta.14 and VSCode as an editor, if that helps. Do you also get this in beta.14?

I'm using vscode as well but I tested several editors to see if there was a difference. I'm not yet using beta.14. I will try during the week.

I confirm the @FoodBuster naming problem. My project was in directory named like :
c:\SomeDir\Some with space and (parenthesis)\myapp
Moving to :
c:\AnotherDirectory
And reload works.

I'm on linux, the naming doesn't fix mine. My files are located at ~/git/my_codebase/ui/..., so no spaces or parentheses. Live reload not working.

I fixed this by removing running rm -rf node_modules , and reinstalling angular-cli both globally and locally.

I just updated my project from 1.0.0-beta.11-webpack.8 to 1.0.0-beta.15. Everything has been cleaned (node_modules, node cache...). Problem is still here.
I'm on Ubuntu 14.04.

Same here. Modifying anything, even scss files reloads whole app.

So as far as I can tell, there's two situations that can cause this issue:

a problem with folder paths having spaces, as described by @FoodBuster on https://github.com/angular/angular-cli/issues/1610#issuecomment-246259005
inotify reaching watcher max on linux, as described by and solved by @paillave on https://github.com/angular/angular-cli/issues/2389#issuecomment-250964095

We'll try to find a more permanent solution to these problems.

@filipesilva I found the 3rd scenario where it doesn't live-reload - if you generate a component with the -component suffix; e.g.:
ng generate component title-component

I can confirm doing ng serve doesn't watches for changes.
here is my ng --version log:
angular-cli: 1.0.0-beta.19-3
node: 6.9.1
os: linux x64

I am currently running Ubuntu 16.04
Whereas if I use the same files on my windows running system, changes appear fine.
If you wanna try out a repo just make a new app using ng new app-name
Try changing app.component.html file.

I have greatly increased inotify limit and it resolved issue on Ubuntu 16.10
08.11.2016 22:11 "thesunnypro"<EMAIL_ADDRESS>napisał(a):

I can confirm doing ng serve doesn't watches for changes.
here is my ng --version log:
angular-cli: 1.0.0-beta.19-3
node: 6.9.1
os: linux x64
I am currently running Ubuntu 16.04
Whereas if I use the same files on my windows running system, changes
appear fine.
If you wanna try out a repo just make a new app using ng new app-name
Try changing app.component.html file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1610#issuecomment-259260810,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB5UkzA73bY28URzFqs8RNrteKNADBBks5q8OV3gaJpZM4JgIZF
.

Found the solution for Ubuntu webpack rebuild issue.
Seems it was indeed an problem with inotify max_user_watches as told by @Namek
sudo echo "fs.inotify.max_user_watches=524288" >> /etc/sysctl.conf
sudo sysctl -p /etc/sysctl.conf

Changing fs.inotify.max_user_watches to 16384 worked for me. The strange thing is that it used to work with 8k watches, anyone knows the reason for the increased number of watches in webpack ?

I use Vagrant with shared folder to run angular-cli and changing fs.notify.max_user_watches didn't work for me. As I found here: https://github.com/webpack/webpack-dev-server/issues/155#issuecomment-159140735 one solution is to specify --watch-poll option for webpack-dev-server.
So when I change this line: https://github.com/angular/angular-cli/blob/master/packages/angular-cli/tasks/serve-webpack.ts#L83 to poll: true, the reloading starts to work. It's pretty slow though...

@dmikhaylov thanks dear, worked for me and for slow issue try increasing vb.memory to double the current value.

I have the same issue on MacOS X. It seems to be a problem with just ng server - whereas ng build --watch seems to function as expected.
ng --version
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.19-3
node: 6.5.0
os: darwin x64
I did notice something that may be a hint. It seems the outDir is being deleted and recreated. If I stay in the outDir and monitor the contents of main.bundle.js after a rebuild the directory is empty. If I cd up and back into the outDir the files have been recreated, but the contents are not correct - main.bundle.js does not contain the change that I made.
With ng build --watch I do not experience the same behavior. After a rebuild the outDir contents have been recreated, but not the directory itself. The directory continues to be valid and the contents reflect the change made.
It seems that there are 2 different things going on there ... but thought the additional info may help.

I had the same problem. I fixed it by simply moving the folder. it was in my "Dropbox (Personal)" folder before. I suspect the reload is tripping over the parentheses.

Thanks to @dmikhaylov , for Vagrant users, adding "poll":true in angular.cli.json file fixed the issue for me.

I had the same problem with sub-modules.
I guess it has to do with special symbols in path name.
Changing dir name from mf-tracker to mfTracker worked for me.

I confirm that setting a higher max_user_watches for inotify worked for me. It was 8k by default.

Same issue,
Angular CLI : 1.0.0-beta.28.3
Node: 7.5.0
OS : Win32 x64
No spaces to app  .. here's the path : c:\dev\myapp
I reinstalled node and angular a couple of time but nothing worked.

Same issue after installing latest to CLI.
Angular CLI : 1.0.0-beta.28.3
Node: 7.5.0
No spaces in path.

Same issue here.
Angular-cli: 1.0.0-beta.28.3
node: 7.0.0
Os: Win10 x64
I reinstalled angular-cli in local and global also npm cache clean but didn't work. path is ok as well.

Same here,
Angular-cli 1.0.0-beta.28.3,
node: 6.5.0
Os: Win7 x64

Same issue after install beta.28.3
Os: Windows 10 x64

the problem is the new version the @ngtools/webpack
i solved it go back to beta26 and<EMAIL_ADDRESS>this command
npm install --save<EMAIL_ADDRESS>maybe work in beta 28

thanks miguelcaravantes, that worked for me.

Thanks @miguelcaravantes  that worked for me too.

Thanks @miguelcaravantes that worked for me too.

Thanks @miguelcaravantes that worked for me too.

@miguelcaravantes answer didn't work for me, Maybe I'm doing something wrong? I'm completly new to this.
I simply did npm install<EMAIL_ADDRESS>followed by npm install --save<EMAIL_ADDRESS>When I save the .ts-file and look at the Chrome DevTools console, I see:
[WDS] App updated. Recompiling...
[WDS] Nothing changed.
ng --version --verbose shows:
angular-cli: 1.0.0-beta.26
http_parser: 2.7.0
node: 7.5.0
v8: 5.4.500.48
uv: 1.10.2
zlib: 1.2.8
ares: 1.10.1-DEV
modules: 51
openssl: 1.0.2k
icu: 58.2
unicode: 9.0
cldr: 30.0.3
tz: 2016j
os: win32 x64

Same problem here guys:
ng --version
angular-cli: 1.0.0-beta.28.3
node: 7.4.0
os: darwin x64

npm install --save<EMAIL_ADDRESS>this works @rafaell-lycan  give it a try

@challe  try uninstall beta 26
install beta 30
npm install --save -g<EMAIL_ADDRESS>install ngtools 1.2.7
npm install --save<EMAIL_ADDRESS>this to works for me

@miguelcaravantes I just tried this but I still have the same issue.

thanks man @miguelcaravantes, u saved my dy.

Some problem here in Archlinux with a fresh installation via angular-cli, I solved it changing the fs.inotify.max_user_watches, also I remember to have this problem previously angular-cli with gulp-watch but at this time I had an error message, so it was easy to figure what was going on.
To change it in archlinux follow these steps:
# Add this line to /usr/lib/sysctl.d/50-default.conf
/usr/lib/sysctl.d/50-default.conf

# Reload all system configurations
sudo sysctl --system

max_user_watches setting doesn't fix my problem. At first change it reloads well but after first it doesn't reload. Totally it's an file system cache issue. After I drop the page cache it works well.
sync;echo 1 > /proc/sys/vm/drop_caches;sync

Same problem for me on Ubuntu 14.04 LTS, node: 6.9.2, I tried angular-cli 1.0.0-beta.28.3 / 1.0.0-beta.30 / 1.0.0-beta.31, and I tried the suggestions of this thread...
Nothing worked to solve the problem...

@sancaruso<EMAIL_ADDRESS>angular/cli and 1.0.0-beta.31 and chrome browser fixed my issue.

With<EMAIL_ADDRESS>angular/cli 1.0.0-beta.31 and chrome browser it doesn't work for me.

Oh! I found the problem... In fact I had a folder with parenthesis in the path of my project, but it was hidden by a symbolic link...

Awesome @dmikhaylov . Adding poll : true solved the problem.

max_user_watches fix doesn't work for me, and I tried using npm install<EMAIL_ADDRESS>as suggested in linked issues and then my project wouldn't even compile - I assume because I have @angular/cli rc.0 and it is too new for the older version of ngtools/webpack.
I don't have any spaces or parenthesis or + in path names, what can I try now?

ng serve --poll=2000

I've created new project using latest version of cli: ng new test
tried to start web site with:
ng serve,
ng serve --watch,
ng serve --poll=2000
but live reload doesn't work
ng -v:

@angular/cli: 1.0.0-rc.1
node: 6.9.5
os: win32 x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.1
@angular/compiler-cli: 2.4.9

@alexsaraiva That did the trick for me, thanks a lot!

@filipesilva  The inotify fix will not work in all cases. I recently ran into this issue and no matter how high I set the max, it did not fix it. I finally solved it when I figured out that Sublime Text 3 (popular text editor) was using up all available inotifies as soon as I created them. If I killed Sublime, suddenly  ng serve was correctly watching files again. The Sublime bug is still open:
https://github.com/SublimeTextIssues/Core/issues/1195
I recommend adding a warning or error-level output to ng serve that lets you know that all inotifies are used up and file watching is unavailable. I can research and submit a PR for this if you think it would be worthwhile.

Hello,
I have updated a project to angular 4, and i found this issue, in fact watcher is working, then compile is ok, but on the browser app remains on "loading..." with no console errors.
this my ng info:
@angular/cli: 1.0.0
node: 6.9.5
os: darwin x64
@angular/animations: 4.0.1
@angular/common: 4.0.1
@angular/compiler: 4.0.1
@angular/compiler-cli: 4.0.1
@angular/core: 4.0.1
@angular/forms: 4.0.1
@angular/http: 4.0.1
@angular/material: 2.0.0-beta.3
@angular/platform-browser: 4.0.1
@angular/platform-browser-dynamic: 4.0.1
@angular/platform-server: 4.0.1
@angular/router: 4.0.1
@angular/cli: 1.0.0

any suggestion?, Thanks.

Hello!
I got the same problem. But it works fine with Sublime Text when you press CTRL+S , but in PHPStorm it stops to work after few clicks CTRL+S.

I am seeing spurious errors more along the lines of what @klmcwhirter describes:
A change is being triggered, and the live reload refreshes in the browser, but the source changes are not reflected in the new page. This may be something as trivial as changing a string, and still seeing the old string shown after a refresh.
This could either be compiling a wrong (cached) version of the file, or – more likely – serving a stale version.
I get the feeling we're seeing three different errors:

Changes are not detected. This seems to be what the majority of this thread focuses on.
Changes are detected, but a stale version still ends up in the browser after a refresh.
Changes to footprint/interfaces are not correctly reloaded. (This seems to be quite consistent, and has some dedicated issue reports, but doesn't seem to be fully resolved).

@wulfsberg - what I observed could be explained by this (I have done this to myself years ago on UNIX):

cd outDir
rm -fr outDir/* outDir
mkdir outDir

At this point outDir exists on the filesystem again but so does the old one in the kernel. I suspect the main server process remains in the old outDir. This directory is empty. [ note in my example above I do not cd to a different dir after doing the deletes ]
What I cannot explain, however, is why the new outDir directory contains the contents of the old .js bundles.
I, too, suspect what @wulfsberg describes - old cached copy is placed into the new outDir instead of the newly compiled bundle(s). Although I cannot conceive of an implementation of ng server that would read the old bundles into memory, compile and build new bundles but then write out the old cached versions. That does not make sense to me. But it seems that indeed that is what is happening.
I tested for and eliminated browser caching as a possibility (used chrome dev tools and turned cache off).
For now, I am just using ng build --watch. The issue may be fixed at this point. I simply haven't taken the time to find out.

@wulfsberg I'm currently facing the same issue with the recompile working but the browser still serving the previous version.
E.g. when changing a HTML file ("a" => "abc") the devtools show the reload, the page even reloads but still displays "a".
When doing another change to the same file ("abc" => "def") it again reloads but now shows the first change (displaying "abc").
Will investigate tomorrow, must be something with my setup which is an ng4-ejected, adapted config that worked well before ejecting and adapting it.

To follow up on @filipesilva's comment in https://github.com/angular/angular-cli/issues/5831#issue-299191668, it does seem likely that the spurious stale results are related to IntelliJ's "Safe write".
It looks as if the Angular-CLI triggers on the first change in the folder (the write of the new, yet-to-be-renamed file), and then throttles further changes, likely in anticipation of a couple more changes to timestamps etc., rather than debouncing the changes and picking up the final result of the barrage.
-This is based on some experiences I have with file change detection in other contexts, not the Angular-CLI code and dependencies, so this is just me guessing wildly.

@wulfsberg explanation makes a lot of sense considering https://github.com/angular/angular-cli/issues/6238 (any file change in src/ triggers a rebuild).

I'm consolidating https://github.com/angular/angular-cli/issues/5117 with this thread. If you're having this issue, make sure to check out #5117 for some more discussion (e.g. solution for vim users is listed there).

Same thing here with Windows 7 and the most recent CLI.
Steps when starting from a directory with node_modules from a previous CLI install:
ng new hello-world --skip-install=true
mklink /j "hello-world/node_modules" "./node_modules"
cd hello-world
ng build -aot -w
I then proceed to edit some html in src/app/app.component.html. The change is detected by doesn't appear in the browser.
Hash: aa73a2645a976a8ce9f8
Time: 3144ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 158 kB {3} [initial]
chunk    {1} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {3} [initial]
chunk    {2} main.bundle.js, main.bundle.js.map (main) 1.13 MB [initial]
chunk    {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry]
Without changing anything else in app.component.html I save again causing it to recompile and the changes are reflected:
Hash: ba4753ae6244f2bad1a8
Time: 3258ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 158 kB {3} [initial]
chunk    {1} styles.bundle.js, styles.bundle.js.map (styles) 10.5 kB {3} [initial]
chunk    {2} main.bundle.js, main.bundle.js.map (main) 1.13 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry]
I see the same behavior whether I use Visual Studio or Visual Studio Code.

Same issue here, it works with vim due to the tmp backup files but it fails with visual studio and atom.
I am using Arch Linux, node and angular version are posted below.
@angular/cli: 1.0.6
node: 7.10.0
os: linux x64
@angular/animations: 4.1.3
@angular/common: 4.1.3
@angular/compiler: 4.1.3
@angular/core: 4.1.3
@angular/forms: 4.1.3
@angular/http: 4.1.3
@angular/platform-browser: 4.1.3
@angular/platform-browser-dynamic: 4.1.3
@angular/router: 4.1.3
@angular/cli: 1.0.6
@angular/compiler-cli: 4.1.3

i had same issue..i changed my directory name with no spaces and only letters..now it reload works fine

Also tried with @angular/cli: 1.1.0, same issue.

Same with @angular/cli: 1.1.0

Had this issue, my directory name had square brackets and spaces. Changed my directory name with no spaces then concatenated it with '-' and now it works.

@alexsaraiva, ng server --poll=2000 worked. Thanks

ng serve --poll=1000 works for me

Using ng server --aot has 1- change save lag:
Save foo -> nothing
Save bar -> foo
Save foobar -> bar
...
--poll is not working, changing folder name to simple is not working
Using ng-server without --aot is working without problem
Browser reload is not working- the sources are not correct served.
@angular/cli: 1.1.0
node: 6.11.0
os: win32 x64
@angular/animations: 4.2.5
@angular/common: 4.2.5
@angular/compiler: 4.2.5
@angular/core: 4.2.5
@angular/forms: 4.2.5
@angular/http: 4.2.5
@angular/platform-browser: 4.2.5
@angular/platform-browser-dynamic: 4.2.5
@angular/router: 4.2.5
@angular/cli: 1.1.0
@angular/compiler-cli: 4.2.5
@angular/language-service: 4.2.5

@filipesilva Is there a chance to some fix in the near future?
Maybe newer webpack version could fix that issues?

@KrystianRos - Use ng serve --poll=1000 it works like a charm for below config:
"dependencies": {
    "@angular/animations": "^4.3.1",
    "@angular/cdk": "^2.0.0-beta.8",
    "@angular/common": "^4.0.0",
    "@angular/compiler": "^4.0.0",
    "@angular/core": "^4.0.0",
    "@angular/forms": "^4.0.0",
    "@angular/http": "^4.0.0",
    "@angular/material": "^2.0.0-beta.8",
    "@angular/platform-browser": "^4.0.0",
    "@angular/platform-browser-dynamic": "^4.0.0",
    "@angular/router": "^4.0.0",
    "core-js": "^2.4.1",
    "hammerjs": "^2.0.8",
    "rxjs": "^5.4.1",
    "zone.js": "^0.8.14"
  }

Some issue, second change will be picked up:
ng serve --poll=1000 or 5000 doesn't work for me.
When I remove the -aot flag it does work properly.

I had problems on Ubuntu 16.04 with ng build --watch running once and quitting. Adding the --poll=1000 flag solved the issue, thanks @alexsaraiva

Poll doesn't stop Webstorm from writing to settings or Sourcetree from writing to the index.  How do I stop ng serve from "recompiling" when these two things happen?

When running ng build -w or ng serve, the reload only worked within the top directory "src" despite applying various fixes reported in this thread.
I was running

Linux 4.12.5-gentoo #2 SMP PREEMPT Sun Sep 17 10:24:52 EDT 2017 x86_64
node 8.4.0
npm 5.4.2
@angular/cli 1.4.5
fs.inotify.max_user_watches=524288
using dashes into filenames and directories (but no other fancy characters)
.angular-cli.json contained:{
  "apps": [
    {
      "root": "src",
      "outDir": "dist"
    }
  ]
}

Upgrading @angular/cli resolved my issue:
npm i<EMAIL_ADDRESS>--save-dev

See if any one is having this type of file name. I was having the same and I fixed it using this solution.
My folder was named as 'question' but when I imported it in app module, I did like this
import { QuestionModule } from './Question/Question.module';
Notice in the path there is 'Q'. My code was running perfectly on browser but webpack stopped tracking my files. I changed it to
import { QuestionModule } from './question/question.module';
And now webpack is also working

I used tip @thesunnypro  and I had a solution
Tip:
sudo echo "fs.inotify.max_user_watches=524288" >> /etc/sysctl.conf
sudo sysctl -p /etc/sysctl.conf
My version CLI:
@angular/cli: 1.4.9
My OS
Fedora 23

After trying multiple options, I solved the issue by reinstalling nodes_modules. Hope it helps.
Steps

rm -rf nodes_modules/
npm update
npm install

ng serve --poll=1000 works for me fine
Thanks

--poll=1000 saved me thanks !!

This still happens, I've just installed angular cli and it doesn't work properly.
I'm just following the angular guide.
The error is the same.
When you run ng serve -o and make some basic editing it won't reload automatically.
Solution by @thesunnypro and @alexsaraiva work for me, but I'm still wondering why this happens.
ng -v
Angular CLI: 1.6.7
Node: 6.10.1
OS: linux x64
Angular: 5.2.3

@angular/cli: 1.6.7
@angular-devkit/build-optimizer: 0.0.42
@angular-devkit/core: 0.0.29
@angular-devkit/schematics: 0.0.52
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.7
@schematics/angular: 0.1.17
typescript: 2.5.3
webpack: 3.10.0

uname -rms
Linux 4.14.16-200.fc26.x86_64 x86_64

Had the same problem when running the ng serve command (updating files had no effect what so ever)
I solved the issue by reinstalling nodes_modules, It also works with the --poll option without needing to re-install the nodes_modules (@alexsaraiva solution), So either one worked for me.
Steps for solution:
rm -rf nodes_modules/
npm update
npm install

This is my setup:
Angular CLI: 1.7.0
Node: 8.9.4
OS: linux x64
Angular: 5.2.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.0
@angular-devkit/build-optimizer: 0.3.1
@angular-devkit/core: 0.3.1
@angular-devkit/schematics: 0.3.1
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.0
@schematics/angular: 0.3.1
@schematics/package-update: 0.3.1
typescript: 2.5.3
webpack: 3.11.0

I am using Centos, and increasing the amount of inotify watchers worked for me.
It is also applicable to Ubuntu users.

--poll=1000 causes my cpu to spike insanely high when running docker / archlinux

I dont understand why this ticket was closed
https://github.com/angular/angular-cli/issues/2748#issuecomment-349821610

This is not an issue with low inotify watchers, the alpine node base image has the following:
/app # sysctl -a | grep inotify
fs.inotify.max_queued_events = 16384
fs.inotify.max_user_instances = 128
fs.inotify.max_user_watches = 524288

Even if this issue is related to low inotify watchers, it is not an OS issue but an Angular issue.
We should not to hack our systems to run an Angular project!

It would be great if the angular team and @filipesilva put together an official docker hub container with the angular client working in it. It would allow us to narrow the possibility space for whats failing across these numerous build approaches.

This is still a problem, same behaviour on a Fedora / Windows 10 machine

i used sudo ng serve and it was working.

ng serve --poll=1000 works for me fine
Thanks

It's work with me. Thanks.

Solution offered by @cabaleirog worked for me.

After trying multiple options, I solved the issue by reinstalling nodes_modules. Hope it helps.
Steps

rm -rf nodes_modules/
npm update
npm install

My app.component changes were triggering the update. But all the other components I made to place within the app would not trigger any updates to the view of my app. This solution made any changes I made update the view, and it works accordingly now.

ng serve --poll=1000

This solved the issue on my Angular 7 project. Thank you @sergiyvoytovych

Looks like there's already a solution for the issue. It's strange that I cannot reproduce it at all though. Please try updating to the latest CLI version. In case you hit this problem again, please share a repository with a minimal demo so we can reproduce the bug and open a new issue.

@mgechev I am currently experiencing this issue for a project I started a few days ago. Please find the url to the repo: [https://github.com/oyes/tailor-notes-ui.git]
I am currently trying the various suggestions mentioned on this thread.

You just run following command it will work when you're did any changes. app will auto-deploy.
ng serve -o

@narain96 - thanks, your solution works for me

I have been having the same issue. Only solution that works is the --poll=1000 option.
The issue itself definitely appears to be Angular version dependent. I have a project folder with a local Angular version of 5.2.0 and the recompile and reload on saved changes works no problem. My global Angular 7 version does not allow for this. The --poll=1000, however, just spike my CPU (as @rightisleft mentions). This is also true for a brand new ng new foobarappthat I created. Nothing else in it, but the recompile & reload doesn't happen on saved changes without the --poll=1000
My Angular version info:
Angular CLI: 7.3.9
Node: 10.15.2
OS: darwin x64
Angular: 7.2.15
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.13.9
@angular-devkit/build-optimizer   0.13.9
@angular-devkit/build-webpack     0.13.9
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cli                      7.3.9
@ngtools/webpack                  7.3.9
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.2
typescript                        3.2.4
webpack                           4.29.0

Same issue here. Even if I use the base Notepad from Windows (so there is no concept of safe write to be disabled with this editor), TypeScript changes are never reflected (compilation not triggered), only HTML and CSS changes.
Removing/reinstalling the node_modules folder did not change anything, nor the usage of the --poll parameter.
I finally tried with a new bare application (i.e. ng new) : ng serve works as expected. I suspect that it is related to the content of the tsconfig.json file(s) or the angular.json file.
Angular CLI: 7.3.9
Node: 12.3.0
OS: win32 x64
Angular: 7.2.15
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.13.9
@angular-devkit/build-optimizer   0.13.9
@angular-devkit/build-webpack     0.13.9
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cli                      7.3.9
@ngtools/webpack                  7.3.9
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.2
typescript                        3.2.4
webpack                           4.29.0

More or less the same issue here: all HTML and CSS files are properly watched, but not the TypeScript files. Whatever the solution applied (removing/reinstalling the node_modules folder, using the --poll parameter, changing the inotify watchers on Linux), nothing has worked. It's probably related to the layout of my project, or the contents of the tsconfig.json files, because ng serve works as expected on a minimal app generated with ng new.
Tested with Node.js 12.2.0 and 12.3.0 on Windows 10 and Ubuntu 19.04: in my case, the issue is clearly not OS-dependant.
Angular CLI: 7.3.9
Node: 12.3.0
OS: win32 x64
Angular: 7.2.15
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.13.9
@angular-devkit/build-optimizer   0.13.9
@angular-devkit/build-webpack     0.13.9
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cli                      7.3.9
@ngtools/webpack                  7.3.9
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.2
typescript                        3.2.4
webpack                           4.29.0


Added T3/T5 branches for GNN T5 classification

Added GNN NTuple branches for T5 classification plus some minor fixes to Event.cu

Let me know if I should address #249 in this PR as well. I think the fix is easy.

general comment.
Is there a reason why not to put idxs to the relevant LS in the t3 branches?
The flattening of the t3 hit positions are OK in principle.
But it puts a danger in creating a lot of branches and lots of duplicate information.
(e.g. if two T3's share a LS, it's going to copy paste same information twice.)
I would rather do something like
T3_LS_idx0
keeping the same branch philosophy as the LS.

Is there a reason why not to put idxs to the relevant LS in the t3 branches?

We use the three hits stored in the t3 branches for computing Balaji's Chi^2. Storing them directly makes it very easy to use them as inputs to the GNN, rather than requiring nested lookups (first to the LS, then to the MD). I also figure that there is not much "danger" here for now, as this is just for training the GNN.

I would rather do something like
T3_LS_idx0
keeping the same branch philosophy as the LS.

This is doable if necessary, but would be more of a headache as explained above.


For Discussion - Table identification in queries

only works in very basic cases
needs deeper look-back (n token lookback)
it is very confused by CTEs
tests are a mess

@MasterOdin what do you think to something like this? I think this feature would be an awesome addition to the library.
Something I think this needs:

Some way to look-up CTES in the parser
Some way to do an n token lookback in the parser

I guess that my biggest thing would be that this is starting to increasingly pushing the library from just a simple query identifier to more of a query AST builder, and is that the direction want to take this library? A logical next step would be that we then also include the list of columns, and then after that maybe the where clause, etc.
Just want to make sure we're on the same page that that's what this library is looking like it might become, though maybe also is that the right direction for this library...

I think we're increasingly needing something like that, and we'll want that to build a bunch of other shared features in the future - like quality autocomplete.
Not sure if it's better keeping this library focused and making something new that has a codebase custom built for purpose, or whether this library can be easily expanded.

Yeah, makes sense. At some point will probably want to better rework the parsing algorithm since it kind of expects you to skip everything after identifying, and we're kind of bolting on new functionality, and I think there might be a cleaner way to accomplish what it does while have it extend better as we add in additional AST type features, but that's not pressing.
All in all, I'm fine with you continuing this thread of work, and I'm not against it, and that I don't think picking out the tables would make the library work any slower or anything for downstream users who don't need that feature.

Closing in favor of #76


What if I use windows in bootcamp in my MBP '15 mid 2010?

Hello I used the GPUFix in my macbook pro and the problem with my GPU was solved, after one year... thanks Julian!!
Well, the problem reappears when I run my MBP with the Windows in bootcamp, it seems the patch doesn´t work when you start the computer with windows... is there any solution for that?
Thanks again!

Hi @antorero, I really don't know how KEXT are managed when using Bootcamp.
You can maybe try to run Windows from a virtual machine if you need a lot of ressources...


Fix link context in step-by-step templates

Link context (price) wasn't showing correctly previously

thanks @hannalaakso I pushed up the fix to that page as well


Setting primary key when building model doesn't set associated primary key

Description

We have two tables where the primary key is generated using the same sequence. I need to set the primary key value when building/creating a model from FactoryBot, because we have an id hard-coded in the code we are testing.
If I set the primary key when calling create(:factory_name, primary_key: 5), the association is still created, but it isn't tied to the parent object, because the child object was created with the default values, not the parent's primary key.
Reproduction Steps

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"
  git_source(:github) { |repo| "https://github.com/#{repo}.git" }
  gem "factory_bot", "~> 6.0"
  gem "activerecord"
  gem "sqlite3"
end

require "active_record"
require "factory_bot"
require "minitest/autorun"
require "logger"

ActiveRecord::Base.establish_connection(adapter: "sqlite3", database: ":memory:")
ActiveRecord::Base.logger = Logger.new(STDOUT)

ActiveRecord::Schema.define do
  create_table :vendors, primary_key: :vendor_no
  create_table :vendor_items, primary_key: :vendor_no
end

class Vendor < ActiveRecord::Base
  self.primary_key = :vendor_no
  belongs_to :vendor_item, foreign_key: :vendor_no, primary_key: :vendor_no
end

class VendorItem < ActiveRecord::Base
  self.primary_key = :vendor_no
end

FactoryBot.define do
  factory :vendor do
    vendor_item

    # Possible work-around
    # after(:build) do |vendor|
    #   vendor.vendor_item = build(:vendor_item, vendor_no: vendor.vendor_no)
    # end
  end

  factory :vendor_item do
  end
end

class FactoryBotTest < Minitest::Test
  def test_factory_bot_stuff
    vendor = FactoryBot.create(:vendor, vendor_no: 5)

    assert_instance_of(VendorItem, vendor.vendor_item)
  end
end

# Run the tests with `ruby <filename>`

Expected behavior

I thought that the association would automatically be created with the correct foreign key
Actual behavior

As shown by the sql statements in the debug log, it was created using default values.
I thought setting a sequence, but a sequence generally won't be necessary for this factory,
and I wouldn't want the sequence to collide when I need a factory to create a model with
a specific id.
It is possible to work-around this by adding an after(:build) callback, in which case, the
association doesn't need to be defined inside the factory.
System configuration
factory_bot version:  6.2.1
rails version:  <IP_ADDRESS>
ruby version: 3.1.1p18

With the factory you presented:
vendor = FactoryBot.create(:vendor, vendor_no: 5)

factory_bot ultimately runs something like:
vendor = Vendor.new
vendor.vendor_no = 5
vendor_item = VendorItem.new
vendor.vendor_item = vendor_item
vendor.save!

The assignment of a new VendorItem with no primary key will wipe out the foreign key on the vendor.
Solving with an after(:build) callback seems reasonable. You might also be able to use the association method inside the block:
  factory :vendor do
    vendor_item { association :vendor_item, vendor_no: vendor_no }
  end

Which would make it behave more like:
vendor = Vendor.new
vendor.vendor_no = 5
vendor_item = VendorItem.new
vendor_item.vendor_no = vendor.vendor_no
vendor.vendor_item = vendor_item
vendor.save!

Thank you for your response! The FactoryBot.create explanation and the association method example were very helpful. I looked at the docs for belongs_to to understand why the assignment of a new VendorItem with no primary key would wipe out the foreign key on the vendor.
belongs_to
association=(associate)
Assigns the associate object, extracts the primary key, and sets it as the foreign key...
Post#author=(author) (similar to post.author_id = author.id)
has_one
association=(associate)
Assigns the associate object, extracts the primary key, sets it as the foreign key, and saves the associate object...
Account#beneficiary=(beneficiary) (similar to beneficiary.account_id = account.id; beneficiary.save)
I realized that changing the vendor_item association from belongs_to to has_one would fix the test. I changed my Vendor class from
class Vendor < ActiveRecord::Base
  self.primary_key = :vendor_no
  belongs_to :vendor_item, foreign_key: :vendor_no, primary_key: :vendor_no
end

to
class Vendor < ActiveRecord::Base
  self.primary_key = :vendor_no
  has_one :vendor_item, foreign_key: :vendor_no, primary_key: :vendor_no, required: true
end


[REQUEST] Unit testing

What is the feature you're proposing?
unstable is a land of both creativity and instability, which is commonly seen from the consistency in bugs appearing on this branch. This branch helps us with standardising a rapid development workflow, however, we often find ourselves having issues with detecting when regular core features of the library begin to break. It's hard to always be able to check every area of this library ourselves, so, I would like to suggest unit testing. This would be a sound and dependable way for us to keep a consistent method in testing parts of the library and halting our ability from committing new code if something fails as a check.
The introduction of unit testing would work in a similar fashion to pre-commit. Additionally, we've now enabled readthedocs builds to occur per Pull Request made in this repository, which will be useful for documentation-based changes as well.
Additional Information

[ ] My feature request is related to an existing Issue.

Issue (if referenceable):

Resolved in 5.x


Add tzdata package for installing

gcloud ubuntu minimal has not tzdata

@overskylab I think you should use https://github.com/geerlingguy/ansible-role-ntp instead with Ansible 2.2+. They are already updated to use timezone module with ensure that tzdata is installed


构建出错

npm install 或者yarn之后报错

@wk13eagle the author does not know Chinese......

Closing due to inactivity. Sorry for the language gap, feel free to comment back with more details.


Coffeescript doc

Referring to this: https://github.com/rstoenescu/quasar-framework/issues/97

Fixed it. Will update website in a few hours.


[SPARK-39496][SQL][3.1] Handle null struct in Inline.eval

What changes were proposed in this pull request?
Backport of #36903
Change Inline.eval to return a row of null values rather than a null row in the case of a null input struct.
Why are the changes needed?
Consider the following query:
set spark.sql.codegen.wholeStage=false;
select inline(array(named_struct('a', 1, 'b', 2), null));

This query fails with a NullPointerException:
22/06/16 15:10:06 ERROR Executor: Exception in task 0.0 in stage 0.0 (TID 0)
java.lang.NullPointerException
	at org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificUnsafeProjection.apply(Unknown Source)
	at org.apache.spark.sql.execution.GenerateExec.$anonfun$doExecute$11(GenerateExec.scala:122)

(In Spark 3.1.x, you don't need to set spark.sql.codegen.wholeStage to false to reproduce the error, since Spark 3.1.x has no codegen path for Inline).
This query fails regardless of the setting of spark.sql.codegen.wholeStage:
val dfWide = (Seq((1))
  .toDF("col0")
  .selectExpr(Seq.tabulate(99)(x => s"$x as col${x + 1}"): _*))

val df = (dfWide
  .selectExpr("*", "array(named_struct('a', 1, 'b', 2), null) as struct_array"))

df.selectExpr("*", "inline(struct_array)").collect

It fails with
22/06/16 15:18:55 ERROR Executor: Exception in task 0.0 in stage 0.0 (TID 0)/ 1]
java.lang.NullPointerException
	at org.apache.spark.sql.catalyst.expressions.JoinedRow.isNullAt(JoinedRow.scala:80)
	at org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificUnsafeProjection.writeFields_0_8$(Unknown Source)

When Inline.eval returns a null row in the collection, GenerateExec gets a NullPointerException either when joining the null row with required child output, or projecting the null row.
This PR avoids producing the null row and produces a row of null values instead:
spark-sql> set spark.sql.codegen.wholeStage=false;
spark.sql.codegen.wholeStage	false
Time taken: 3.095 seconds, Fetched 1 row(s)
spark-sql> select inline(array(named_struct('a', 1, 'b', 2), null));
1	2
NULL	NULL
Time taken: 1.214 seconds, Fetched 2 row(s)
spark-sql>

Does this PR introduce any user-facing change?
No.
How was this patch tested?
New unit test.

Merged to branch-3.1.


Used named imports for react-router in react-router-config

I was recently doing some bundle size analysis using source-map-explorer
and noticed that we had a little bit of duplication of react-router
code. It seems as though our import of react-router-config was bringing
in modules from react-router/Foo, while our named imports from
react-router was bringing in modules from react-router/es/Foo.
As a workaround, I've set up a webpack alias to avoid the duplication,
but I think this should be solved in this package so that everyone can
benefit.
I believe this is similar to:

https://github.com/ReactTraining/react-router/pull/5589

Thanks!


Add relation field name to list view

Changed ID into the relation column to a readable view

Thank you, but once again, I had something slightly different in mind.
I'm planning to handle it together with the more generic relations picker refactoring in v0.12/v0.13 as part of https://github.com/pocketbase/pocketbase/issues/976.
Please file an issue/discussion with the planned implementation details before starting work on a PR for a new feature to avoid wasting your time. Also please refer to https://github.com/pocketbase/pocketbase#contributing.


Secure Tenancy chart

Helm chart to install Secure Tenancy.  Requires user to build and supply an image on private repository for Secure Tenancy binary.

Easy to get going, by default it will setup and install a MySQL database to use
Can also use an existing MySQL database instead
Migrate script will run with helm install commands, as either a post-install (when install MySQL) or pre-install (when using an existing MySQL) hook.
Includes support for Ingress
Includes support for horizontal pod autoscaling

Beautiful! LGTM


Handle GitHub file as not found

Fixes #345

I signed it!

What's wrong with looking at the raw bytes?
The goal is to return not found when the response is not the expected type, a JSON array.
The proposed UnmarshalTypeError error check does something different. It will not return a NotFoundError error when the JSON is a number or a string. It can return a NotFoundError on type mismatch on one of the fields (this should probably be internal server error).

What's wrong with looking at the raw bytes?

Nothing, it can just lead to more poorly readable code.

The goal is to return NotFoundError when the response is not the expected type, a JSON array.

Can't you do that with just if _, ok := err.(*json.UnmarshalTypeError) { then?
From its docs:
// An UnmarshalTypeError describes a JSON value that was not appropriate for a value of a specific Go type.

Can't you do that with just _, ok := err.(*json.UnmarshalTypeError) then?

This sets ok to true for a type mismatch anywhere in the structure, not just the root.  I think it's best to check for the specific condition (the root is not an array).

Nothing, it can just lead to more poorly readable code.

Is this code poorly readable?  There's a comment explaining what's going on.

The server handles not found errors differently from other errors (grep for NotFound). Because I don't understand that code, I wanted to make the most conservative change that fixes the issue.
Is it OK to return NotFoundError for a type mismatch anywhere in the structure?

Please look again.

The new higher-level implementation looks great to me, I think it's more readable and maintainable.
I've reviewed it, LGTM. I've tested and it worked as expected. Thanks!

To answer my own question above, it’s not OK to return NotFoundError for type mismatches below the root. The server deletes packages form the database when NotFoundError is returned (see crawl.go). Type mismatches below the root are a program error and should not result in the deletion of data.
I think the original version of the code is more readable. A developer with a superficial knowledge of JSON should be able figure out that the original version of the code tested for a JSON array.  The final version requires a detailed understanding of the errors returned by the encoding/json package.
JSON syntax ain't gonna change. Writing a bit of code that depends on the syntax is not going to cause a maintenance issue. On the other hand, the errors returned by the encoding/json package have changed. Maybe they will change again and break this code.

@lucidlime are you saying that the code as merged is not correct? I'm not sure I follow exactly what you mean by "type mismatches below the root".

errors returned by the encoding/json package have changed. Maybe they will change again and break this code.

I think that's unlikely. But, I think you are ultimately correct. It is in some ways simpler to just check the start of the response before invoking the json package. If it were possible for me to see your original commit I'd have more to say. :-/

To answer my own question above, it’s not OK to return NotFoundError for type mismatches below the root. The server deletes packages form the database when NotFoundError is returned (see crawl.go). Type mismatches below the root are a program error and should not result in the deletion of data.

Yes, I agree, it's not ok to return NotFoundError for type mismatches below the root.
I think the merged code is correct. It only returns NotFoundError if the parsing error is at at first byte (e.Offset == 1) rather somewhere deeper inside the JSON input, which should only happen if it's a file and not a directory.

It is in some ways simpler to just check the start of the response before invoking the json package. If it were possible for me to see your original commit I'd have more to say. :-/

I agree it's simpler, but the reason I asked if there were higher level alternatives is because looking at JSON bytes in order to parse JSON feels dirty and it's a slippery slope, one that's heading towards someone else then parsing some binary protocol or HTML with regexp, etc., just because it's slightly easier in the short term.
@adg, you can see a portion of the original commit in my first inline comment here.

I think the original version of the code is more readable. A developer with a superficial knowledge of JSON should be able figure out that the original version of the code tested for a JSON array. The final version requires a detailed understanding of the errors returned by the encoding/json package.
JSON syntax ain't gonna change. Writing a bit of code that depends on the syntax is not going to cause a maintenance issue. On the other hand, the errors returned by the encoding/json package have changed. Maybe they will change again and break this code.

If you asked me for the ideal solution, I think it's best to be using the go-github Go library as the GitHub client, and let it worry about internal GitHub API details (and keeping up to date with GitHub API changes), exporting a nice idiomatic Go API. However, I didn't make this decision to use raw GH API, and it was made many years ago, probably before go-github even existed.
If you look at how go-github does it, it doesn't try to look at JSON bytes either, it uses a json.RawMessage and then decodes it into two types (one for a file, and one for a directory) and lets you use the one that worked without an error. That's probably even better than checking for JSON error that's merged here.
In any case, I'm happy to go with a different approach if it's deemed better. I just asked if there was a way not to use raw bytes and asked "what do you think?", I didn't mean that it must be done in any specific way.

@lucidlime are you saying that the code as merged is not correct?

The server will return internal errors instead of not found errors if GitHub adds whitespace to the beginning of the response. This seems unlikely. Otherwise, the code is correct.

I'm not sure I follow exactly what you mean by "type mismatches below the root".

The response is decoded to:
var contents []*struct {
	Type    string
	Name    string
	GitURL  string `json:"git_url"`
	HTMLURL string `json:"html_url"`
}

I am using the term root to refer to the slice.  A type mismatch on the slice is what we want to check for.  A type mismatch on one of the any of the fields is a program error of some sort and should not be handled as a not found error.

If it were possible for me to see your original commit I'd have more to say. :-/

p, err := c.getBytes(expand("https://api.github.com/repos/{owner}/{repo}/contents{dir}?ref={tag}", match))
if err != nil {
	return nil, err
}
p = bytes.TrimSpace(p)

// GitHb returns JSON array for directories
if len(p) == 0 || p[0] != '[' {
	return nil, NotFoundError{Message: "Not a directory in GitHub"}
}

I saw that part of the commit from the discussion above, but where do the bytes get actually decoded? Or does this mean you make two requests to the API?

I updated my previous comment with the code to decode the response.  I lost my original code when I squashed the commits.

I don't see the update (maybe a stale cache entry somewhere on GitHub's end). But I take it you didn't make the request twice, but instead did the decode of the bytes fetched with getBytes. That seems ok.
Moving forward from here, it might be worth fixing this:

The server will return internal errors instead of not found errors if GitHub adds whitespace to the beginning of the response.

One way of doing this would be to strip whitespace inside the getJSON method before decoding. Another would be to revert this change and go with your original approach. I'm ambivalent about which road to take. If we go with the latter, then I'd suggest replacing this code
p = bytes.TrimSpace(p)
if len(p) == 0 || p[0] != '[' {

with if bytes.HasPrefix(bytes.TrimSpace(p), []byte{'['})) {.

@adg, has this change been deployed yet? It was merged 9 days ago.

Looks like it's been deployed now, and https://godoc.org/github.com/golang/go/src/cmd/vet/doc.go is correctly showing a Not Found page.