AgentStatusPoller broken in Tier0 2.0.9

What is the error message trying to tell me ?
2017-10-02 21:42:13,354:140023845025536:INFO:AgentStatusPoller:Getting agent info ...
2017-10-02 21:42:13,777:140023845025536:ERROR:AgentStatusPoller:Error occurred, will retry later.
Details: You must include http(s):// in your server's address, ReqMgr2 rest service/data/ doesn't
Traceback (most recent call last):
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMComponent/AgentStatusWatcher/AgentStatusPoller.py", line 112, in algorithm
agentInfo = self.collectAgentInfo()
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMComponent/AgentStatusWatcher/AgentStatusPoller.py", line 188, in collectAgentInfo
agentInfo['disk_warning'] = listDiskUsageOverThreshold(self.config, updateDB=True)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/ReqMgrAux/ReqMgrAux.py", line 141, in listDiskUsageOverThreshold
reqMgrAux = ReqMgrAux(config.TaskArchiver.ReqMgr2ServiceURL)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/ReqMgrAux/ReqMgrAux.py", line 34, in init
Service.init(self, httpDict)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/Service.py", line 133, in init
self["requests"] = requests(cfg_dict['endpoint'], cfg_dict)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 526, in init
Requests.init(self, url, idict)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 109, in init
check_server_url(self['host'])
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 58, in check_server_url
raise ValueError(msg)
ValueError: You must include http(s):// in your server's address, ReqMgr2 rest service/data/ doesn't

I'm not sure which ReqMgr url the T0 agent is supposed to use. But Seangchan will know that.
What I wanted to comment is, please use our WMAgent stable release (1.1.6.patch4). Seangchan is already cooking 3 other patches, so we'll have 1.1.6.patch5 by tomorrow evening.

We are using 1.1.6.patch4. The rpm was built against 1.1.7.pre3 (no way to specify what I want, it takes the latest and @ticoann updated the spec too quickly). We are overriding all the python code during deployment.

Hmm, that isn't the best. Is the spec simply pointing to master/HEAD? You should be able to define one specific release in the spec file. It also helps anyone that needs to debug the T0 code.

I have wmagent as a dependency, which means it picks whatever version is currently defined in wmagent.spec. If someone can give me a way how to override that (without specifying WMCore as a source in the t0.spec and building it myself and including it in the to rpms), I would be using that immediately.

Ok, I am trying some of that in my personal builds, lets see how it goes...

Yeah, it doesn't work. Following up in HN.

Dirk, have a look at the wmarchive spec:
https://github.com/cms-sw/cmsdist/blob/comp_gcc630/wmarchive.spec#L3
it does exactly what you need.

No, it doesn't. It builds a wmarchive package that includes the WMCore code. I want to build a t0 package that depends on the wmagent package and installs the wmagent package.

Hmm the error looks like a bug. Dirk, was it working before when you test with 1.1.6.patch4?
Anyway, I will create a new patch for that.

Not sure if this was ever working. It didn't prevent my replays from completing, so this might very well always have been there with the later WMCore versions. Tier0Ops noticed it in their replay and then I checked mine and it was there as well.

Sorry about that I created the patch, #8217, could you apply this patch and run it again you don't have to change tier0 config now. It will take the default value.

#8217 seems to fix this problem, but then I get the following error (did you change something in the component heartbeat ?):
2017-10-03 02:08:37,302:140548846745344:INFO:AgentStatusPoller:Getting agent info ...
2017-10-03 02:08:37,703:140548846745344:INFO:AgentStatusPoller:CouchDB is running with 2 processes
2017-10-03 02:08:37,704:140548846745344:INFO:AgentStatusPoller:List of agent components down: ['Tier0Feeder']
2017-10-03 02:08:38,615:140548846745344:INFO:AgentStatusPoller:Getting wmbs job info ...
2017-10-03 02:08:38,916:140548846745344:INFO:AgentStatusPoller:WMBS data collected in: 0 secs
2017-10-03 02:08:38,924:140548846745344:ERROR:AgentStatusPoller:Error occurred, will retry later.
Details: CouchNotFoundError - reason: Object Not Found, data: {'docs': [{'status': 'down', 'couch_process_warning': 0, 'disk_warning': [], 'agent_team': 'REPLACE_TEAM_NAME', 'down_components': ['Tier0Feeder'], 'timestamp':<PHONE_NUMBER>, 'acdc': 'http://localhost:5984/acdcserver/_design/ACDC/collections.html', 'agent': 'WMAgentCommissioning', 'WMBS_INFO': {'wmbsCreatedTypeCount': {}, 'sitePendCountByPrio': {'T2_CH_CERN': {0: 0}, 'T0_CH_CERN': {0: 0}}, 'wmbsCountByState': {}, 'thresholds': {'T2_CH_CERN': {'state': 'Normal', 'running_slots': 0, 'pending_slots': 0}, 'T0_CH_CERN': {'state': 'Normal', 'running_slots': 1600, 'pending_slots': 1600}}, 'total_query_time': 0, 'completeRunJobByStatus': {}, 'wmbsExecutingTypeCount': {}, 'activeRunJobByStatus': {}, 'thresholdsGQ2LQ': {'T2_CH_CERN': 0.0, 'T0_CH_CERN': 1600.0}}, 'down_component_detail': ['Tier0Feeder'], 'drain_mode': False, 'agent_url': 'vocms001.cern.ch', '_id': 'vocms001.cern.ch', 'type': 'agent_info', 'agent_version': '1.1.6.patch4'}]} result: None
Traceback (most recent call last):
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMComponent/AgentStatusWatcher/AgentStatusPoller.py", line 128, in algorithm
self.uploadAgentInfoToCentralWMStats(agentInfo, uploadTime)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMComponent/AgentStatusWatcher/AgentStatusPoller.py", line 234, in uploadAgentInfoToCentralWMStats
self.centralWMStatsCouchDB.updateAgentInfo(agentDocs)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/WMStats/WMStatsWriter.py", line 140, in updateAgentInfo
result = self.couchDB.commitOne(agentInfo)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 240, in commitOne
retval = self.post(uri, data)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Services/Requests.py", line 125, in post
encode, decode, contentType)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 123, in makeRequest
getattr(e, "reason", None), data)
File "/data/tier0/srv/wmagent/2.0.9/sw/slc6_amd64_gcc493/cms/wmagent/1.1.7.pre3/lib/python2.7/site-packages/WMCore/Database/CMSCouch.py", line 140, in checkForCouchError
raise CouchNotFoundError(reason, data, result)
CouchNotFoundError: CouchNotFoundError - reason: Object Not Found, data: {'docs': [{'status': 'down', 'couch_process_warning': 0, 'disk_warning': [], 'agent_team': 'REPLACE_TEAM_NAME', 'down_components': ['Tier0Feeder'], 'timestamp':<PHONE_NUMBER>, 'acdc': 'http://localhost:5984/acdcserver/_design/ACDC/collections.html', 'agent': 'WMAgentCommissioning', 'WMBS_INFO': {'wmbsCreatedTypeCount': {}, 'sitePendCountByPrio': {'T2_CH_CERN': {0: 0}, 'T0_CH_CERN': {0: 0}}, 'wmbsCountByState': {}, 'thresholds': {'T2_CH_CERN': {'state': 'Normal', 'running_slots': 0, 'pending_slots': 0}, 'T0_CH_CERN': {'state': 'Normal', 'running_slots': 1600, 'pending_slots': 1600}}, 'total_query_time': 0, 'completeRunJobByStatus': {}, 'wmbsExecutingTypeCount': {}, 'activeRunJobByStatus': {}, 'thresholdsGQ2LQ': {'T2_CH_CERN': 0.0, 'T0_CH_CERN': 1600.0}}, 'down_component_detail': ['Tier0Feeder'], 'drain_mode': False, 'agent_url': 'vocms001.cern.ch', '_id': 'vocms001.cern.ch', 'type': 'agent_info', 'agent_version': '1.1.6.patch4'}]} result: None

Tier0Feeder is definitely NOT down.

Dirk, what is following config value?
config.AnalyticsDataCollector.centralWMStatsURL

I have three of those in the config
config.TaskArchiver.centralWMStatsURL = 'http://admin:couch@localhost:5984/wmstats'
config.AnalyticsDataCollector.centralWMStatsURL = 'http://admin:couch@localhost:5984/wmstats'
config.AgentStatusWatcher.centralWMStatsURL = 'http://admin:couch@localhost:5984/wmstats'

Which is exactly what's in the secrets file
WMSTATS_URL=http://admin:couch@localhost:5984/wmstats
This is a replay, we do not have a central wmstats instance for that, just the local one.

You should still have different central db as local db fpr the test even if it is using the same db.  ie
http://admin:couch@localhost:5984/wmstats_central

But still weird that it cannot find the document. If you restart is do you still get the same error?

Same error when I restart the AgentStatusWatcher. Seems something is screwed up with my configuration. If you want to take a look:
vocms001:/data/tier0/srv/wmagent/current/config/tier0/config.py

Can I restart AgentStatusWatcher there for debugging?

Only Couch and AgentStatusWatcher are running right now, feel free to start/stop/restart whatever. Keep the JobSubmitter down if possible though to avoid jobs being run (not the end of the world if they do, but for debugging this issue we don't need them, so I'd rather not run them).

The problem was central WMStats url is pointing to local database but it doesn't exist.
I created the db manually and restarted AgentStatusWatcher. It seems OK now.
We can maybe change config or deploy script for local testing settings to handle this properly.

Does the deployment assume that the wmstats couch db exists already ? How do you handle this in agent testing ? Are you always using the central wmstats ?

for vm agent testing we set up in separate vm for all other applications reqmgr, workqueue, wmstats.
But I guess that is overkill for Tier0 case. You can also point to cmsweb-testbed wmstats if there is no change in wmstats code in the deployment.

What happens if two replays publish the exact same workflows to the testbed wmstats instance ? Will likely happen if we have two active replays going on.

Not good. :-) The basic assumption is the workflow names are unique. So it will add up all the data,
However, that is only in central wmstats. local data is intact. If you just set up in local db, you are not really using tier0 wmstats anyway, isn't it?

Anyway, it sounds like we need to set up test specific case to put the central wmstats locally.

Would that go into the wmagent deploy scripts ? Check if the wmstats db in the secrets files is local and create it if it is ?

I create the patch. It is a little hacky but I think it is simplest
#8226

With that patch the AgentStatusWatcher works now ! Guess we need both patches in the master branch and also the 1.1.16 branch ?

Yes I will include both.


tests: Re-enable the explicit error checks for non-tarball DWB requests

Change-type: patch

I self-certify!


Multiple values for isDisabled?

I'm trying to disable weekends, while having a minDate set but nothing I seem to do works. Is this not possible, or am I doing something wrong?

$().datepicker({
  isDisabled: function(date) {
    return (date.getDay() === 6 || date.getDay() === 0) ? true : false;
  }
});

Try the startDate and endDate in the v0.2.0 please.


undefined method `react' for #<Rails::Application::Configuration

Hi there.
I've just added the gem to my rails project and bundled. Although, I'm getting this error when trying to run the install generator. (Using ruby 2.20 and Rails 4.2.2)
/home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/railtie/configuration.rb:95:in method_missing': undefined methodreact' for #Rails::Application::Configuration:0x0000000d7eb7f8 (NoMethodError)
from /home/boromir/workspace/gemini/config/application.rb:87:in <class:Application>'     from /home/boromir/workspace/gemini/config/application.rb:21:inmodule:Gemini'
from /home/boromir/workspace/gemini/config/application.rb:20:in <top (required)>'     from /home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/commands/commands_tasks.rb:141:inrequire'
from /home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/commands/commands_tasks.rb:141:in require_application_and_environment!'     from /home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/commands/commands_tasks.rb:128:ingenerate_or_destroy'
from /home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/commands/commands_tasks.rb:50:in generate'     from /home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/commands/commands_tasks.rb:39:inrun_command!'
from /home/boromir/.rvm/gems/ruby-2.2.0@gemini/gems/railties-4.2.2/lib/rails/commands.rb:17:in <top (required)>'     from script/rails:6:inrequire'
from script/rails:6:in `'

@gemini-google-group Did you maybe forget to uninstall the react-rails gem?
We don't have any method called react.

When I received this message, it was because I had removed react-rails from my Gemfile but not the configuration code in config/development.rb

When I received this message, it was because I had removed react-rails from my Gemfile but not the configuration code in config/test.rb


docs: add architecture and roadmap

add a section in the README to sketch the future plans, and start an ARCHITECTURE document to describe in
broad strokes how the operator is designed.

Do we intend to add (main) known issues?

I think the proper place for this is github issues, feel free to file them


%lifetime%

Hey
For some reason it shows over all play time and not from last death.

This is an issue of the bukkit API


Add support for Slack's new modals APIs and events

This PR adds support for Slack's new modal APIS and events described here
Changes include:

Update dependency to latest version of @slack/web-api
Add some new sample code to the testbot
allow events without channels -- because new modal events do not include channel data. (This means bot.reply will not work with these events, amongst other caveats)

In addition, this will fix the behavior that caused all "block_actions" and "interactive_message" events to become "message" events.  These events will retain their native event type, but will still be passed into active dialogs (so a button click can be passed to a convo.ask)

@geoff-watson yes


npm install hangs forever and freezing rancher desktop while dockerizing angular application

Command
new
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
While dockerizing angular application, npm install hangs with below logs
 => [build 4/6] RUN npm install --verbose                                                                                6.9s
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/darwin-x64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/darwin-arm64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/android-x64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/android-arm64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/android-arm
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/aix-ppc64

Minimal Reproduction
ng new my-app
cd my-app
docker build --tag myapp --platform=linux/amd64 --file Dockerfile .
Exception or Error
docker build --tag cbdc --platform=linux/amd64 --file Dockerfile .
[+] Building 9.4s (9/13)                                                                                docker:rancher-desktop
 => [internal] load build definition from Dockerfile                                                                              0.0s
 => => transferring dockerfile: 337B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 95B                                                                                0.0s
 => [internal] load metadata for docker.io/nginxinc/nginx-unprivileged:latest                                                     2.4s
 => [internal] load metadata for docker.io/library/node:20.11.1                                                                   2.4s
 => [build 1/6] FROM docker.io/library/node:20.11.1@sha256:e06aae17c40c7a6b5296ca6f942a02e6737ae61bbbf3e2158624bb0f887991b5       0.0s
 => [stage-1 1/2] FROM docker.io/nginxinc/nginx-unprivileged:latest@sha256:2577b782328a7d6cc311a17ba8634996d9e8221c413361e847a74  0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 1.03kB                                                                                0.0s
 => CACHED [build 2/6] WORKDIR /usr/src/build                                                                                0.0s
 => CACHED [build 3/6] COPY package*.json .                                                                                0.0s
 => [build 4/6] RUN npm install --verbose                                                                                6.9s
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/darwin-x64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/darwin-arm64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/android-x64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/android-arm64
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/android-arm
 => => # npm verb reify failed optional dependency /usr/src/build/node_modules/@esbuild/aix-ppc64

Your Environment
ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 17.3.2
Node: 20.11.0
Package Manager: npm 10.2.4
OS: darwin x64

Angular: 17.3.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.2
@angular-devkit/build-angular   17.3.2
@angular-devkit/core            17.3.2
@angular-devkit/schematics      17.3.2
@angular/cli                    17.3.2
@schematics/angular             17.3.2
rxjs                            7.8.1
typescript                      5.4.3
zone.js                         0.14.4

Anything else relevant?
Dockerfile
FROM node:20.11.1 as build

WORKDIR /usr/src/build

COPY package*.json .

RUN npm install --verbose

COPY . .

RUN npm run build

FROM nginxinc/nginx-unprivileged:latest

COPY --from=build /usr/src/build/dist/my-app/browser /usr/share/nginx/html

EXPOSE 8080

CMD ["nginx", "-g", "daemon off;"]

workaround
Only way to fix this is, remove package-lock.json while doing docker build and it works without any issue.

This is related to https://github.com/npm/cli/issues/4828 and is an NPM bug.
In short the package lock becomes platform specific when having platform specific dependencies.
As an alternative you might want to consider using an alternate package manager.


Proxyless does not work correctly when open second browser window

What is your Scenario?
In my test I open second browser window using experimental-proxyless
What is the Current behavior?
The url is incorrect in the second window
What is the Expected behavior?
The url should be correct
What is your public website URL? (or attach your complete example)
In the example beforeEach method opens an url- url is ok
in test i open another window with another url
Url is incorrect

What is your TestCafe test code?
file: example.js
fixtureOpen navigation
.beforeEach(async t => {
await t.navigateTo("https://reactnavigation.org/docs/hello-react-navigation/");
})

test("Expand navigation", async t => {
await t.openWindow("https://reactnavigation.org");
});
Your complete configuration file
no config file needed
Your complete test report

Screenshots
No response
Steps to Reproduce
1.open url
2.open window with other url
3.
TestCafe version
2.4.0
Node.js version
16.7.0
Command-line arguments
testcafe chrome --experimental-proxyless example.js -t "Expand navigation"
Browser name(s) and version(s)
Chrome 111 Linux
Platform(s) and version(s)
Linux Ubuntu 22
Other
No response

Thank you for sharing this. Currently, the proxyless mode is not supported in multiple window mode. Please use the '--disable-multiple-windows' flag.


Can't create F# function

When I run func new the options only list C# and JavaScript. F# should be on the list
When I run func new --language F# --template HttpTrigger --name MyHttpTrigger the following error is reported:
Can't find template "HttpTrigger" in "F#"

Are you on core version?

I installed it from the mom package as per the  the README. Should I build from source using the core branch?

I'm a bit confused since I don't know what "mom package" is.
I asked because when I install the master branch of the tool (npm i -g azure-functions-core-tools), I get lots of templates including F#.
If I install cross-platform beta version (npm i -g azure-functions-core-tools@core), I only get JS and C# templates.

my apologies (I was on my phone an it autocorrected npm to mom. I have fixed that). I'm on my computer now. AFAIK I used the standard installation ie npm i -g azure-functions-core-tools. I will update my installation now and check. I could have done something wrong.

I did not install via npm
I installed via these docs: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest
I'm on mac so I used brew install azure-cli

Ok, so you are on cross-platform version which is now in beta. I guess they did not bother with adding more templates yet.
I've just created #301 earlier today, so it's almost the same question.

If i try to install with the npm command i get the following error:
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"any"} (current: {"os":"darwin","arch":"x64"})
npm ERR! notsup Valid OS:    win32
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   darwin
npm ERR! notsup Actual Arch: x64

Thanks for raising the new issue.
This is where is found I found the installation steps with hose I installed the tool:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local
You were correct, I did install using with npm i -g azure-functions-core-tools@core
I also noticed that the README for this project still states that this tool is windows only, while the microsoft docs state that cross-platform support is in beta. Should a seperate issue be raised to update README for this repo?

Does this mean I can't get Azure Functions Core Tools (2.0.1-beta.31) working on macos for F#?

@slifin It should work, but it has no templates for F#, so you'd have to setup the project manually

oh right, is there any documentation for that? This is my first foray into F# so I don't know what's involved with setting up a project manually
I have a F# template in the azure function cloud, can I copy all the files from that into my local dir where I did func new?

@slifin Shameless plug to my blog and samples repo:
https://mikhail.io/2017/12/precompiled-azure-functions-in-fsharp/
https://github.com/mikhailshilkov/azure-functions-fsharp-examples

@jeffhollan are there any plans to add F# templates?

@ahmedelnably https://github.com/Azure/azure-functions-templates/pull/738#issuecomment-479959072

cc/ @soninaren, as the PR has already been merged


[Snyk] Upgrade @azure/msal-common from 14.13.0 to 14.15.0

Snyk has created this PR to upgrade @azure/msal-common from 14.13.0 to 14.15.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 5 versions ahead of your current version.

The recommended version was released on a month ago.

Release notes

Package name: @azure/msal-common

14.15.0 - 2024-09-20

14.14.2 - 2024-08-28

14.14.1 - 2024-08-13

14.14.0 - 2024-07-23

14.13.1 - 2024-07-16

14.13.0 - 2024-07-01

    from @azure/msal-common GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Deleting as pull request was generated by old Snyk.
Any new Synk PRs should be come from the new Synk - https://app.snyk.io/org/legal-aid-agency/


prisma migrate reset fails if the db is not already initialized

Bug description
prisma migrate reset fails if the db is not already initialized. This is a problem because this reset command is heavily used in test environments on the test DB. The test DB may or may not exist. And currently if it doesn't, this command fails.
So now we have to run prisma migrate dev && prisma migrate reset in our test scripts which just isn't great 😅
How to reproduce

Run prisma migrate reset in a project without the database set up

Expected behavior
Should not fail on the first step (delete DB), and then continue on with setting up a new clean DB.
Prisma information
Prisma 2.14.0

The current migrate reset command only checks if it can connect to the database but does not create it.
These commands create the database if it does not exist:

db push
migrate deploy
migrate dev

It could make sense to to that here too, thanks for the issue!

The current migrate reset command only checks if it can connect to the database but does not create it.
These commands create the database if it does not exist:

db push
migrate deploy
migrate dev

It could make sense to to that here too, thanks for the issue!

That was fast 🔥🔥🔥🔥🔥

That was fast 🔥🔥🔥🔥🔥


Replication fail with multiple volume servers

Describe the bug
Try to run curl -F<EMAIL_ADDRESS>"http://${filerIp}:8888/target?replication=010" and get {"error":"rpc error: code = Unknown desc = Cannot grow volume group! No matching data node found! \n1:Only has 1 rack with more than 1 free data nodes, not enough for 2."} while actually, we have 2 racks in one datacenter. Also tried to assign these two volume servers to different datacenter names and try to replicate with 100 strategy and got {"error":"rpc error: code = Unknown desc = Cannot grow volume group! No enough data node found!"}
Screenshots

Your rack 2 has max of 7 volumes, and all were taken already.


kuka_external_control_sdk: 1.3.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository kuka_external_control_sdk to 1.3.0-1:

upstream repository: https://github.com/kroshu/kuka-external-control-sdk.git
release repository: https://github.com/ros2-gbp/kuka_external_control_sdk-release.git
distro file: humble/distribution.yaml
bloom version: 0.12.0
previous version for package: null

kuka_external_control_sdk
* Change motion state variables from pointer to reference
* Rework control signal Add methods to accept stl iterators

kuka_external_control_sdk_examples
* Add examples package
* Contributors: Mark Szitanics, Gergely Kovacs, Aron Svastits

Closing due to failed Jenkins build (missing test dependency)
Fixed in 1.3.1 (#41273)


[readability] Consider changing name of idToIndex and idToOwnerIndex

I use to name index mappings like idToIndexInTokens (or tokenIdToIndexInTokens) and idToIndexInOwnerToIds (last part after In is the same as name of array). This makes it clear which array uses given index mapping.

Good suggestion but it's too long and less readable. We made this decision earlier.

That's fine. I just find idToOwner, idToIndex and idToOwnerIndex, which are unrelated, too similar when reading the code.

Hum ... let's stay with that for now. We'll think about it.


Fix PrimitivesJob's status method

Summary
Fixes PrimitiveJob's status to correctly return JobStatus.DONE when there were no errors.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 84.052%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
56316

Relevant Lines:
67001

💛  - Coveralls


Fix metadata encryption migration bug

Changes:

Fixed a use after move issue
The metadata encryption key retrieval function can now repair inconsistent state caused by the above bug

Fixes #569

For sake of expediency, how about we land the fix for the original issue (i.e., removing the std::move), and pull out the recovery into a separate PR where we can spend a little more time getting it right?

When app is launched with 2.10.2 it's rewrites old metadata.realm with new one. Because old couldn't be read. And when you have two keys in keychain it's not always legacy key is the one you should use. Best fix would be to check what key could decrypt metadata.realm and store it as new one. Or always try new key, then catch an exception and if it's encryption - it should try to read metadata with the legacy key.

Thanks for bringing this to our attention.

If the metadata Realm is deleted because of an invalid key error (as you stated), a new Realm will be generated. It will use the newly added keychain item as its encryption key.
Upon all subsequent launches the metadata subsystem will find the new key, use it properly, and ignore the old key.
We don't make any provision for deleting the old key; you may do so yourself if you desire. That being said, once the new key is added there is no code path for removing the old key. The new key is added either as a newly generated random value or as a copy of the old key, and is exclusively used from this point on. The bug in question skipped the copying of the old key and required the Realm to be deleted and recreated with the newly generated key as a result.

As a result this fix is unnecessary and users who have already experienced this bug, while having lost their metadata, should now have properly functioning metadata.


Evaluation architecture

This is my preliminary trial on building evaluation architecture. It follows the diagram below, where the blue is included in the code, the grey is saved for future use. Feel free to leave any comments, thoughts, and ideas!

I would reframe the flow chart above as saying:

There is a Forecast class, which is an extension of a polars dataframe that enforces some schema (say, it has columns forecast_date, observation_date, target, value)
There are two subclasses to Forecast: QuantileForecast and SampleForecast. The quantile forecast will have a column quantile (with values like 0.50) and the sample forecast will have a column sample_id (running from 1 to the number of posterior samples).
PointForecast could be a subclass of QuantileForecast that enforces there being only a single quantile (ie 0.50, the median). Or it could be its own subclass of Forecast that doesn't have quantile or sample_id.

I don't know that you need the time/less distinction?
A model like the one that's been coded up now would produce PointForecast for now, and could be upgraded to do QuantileForecast

The updated evaluation architecture is that ValidateData as the super parent, embracing UptakeData and Forecast. Forecast has QuantileForecast and SampleForecast, and PointForecast is a subclass of QuantileForecast. All the metrics are standalone functions given the data and the pred are in the matching and standard format.


Add windows e2e tests to CI/CD (#1906)

Testing new workflow

/ok-to-test

It would seem there is no way to get github to run a workflow not on the master branch.


Update windows utils

Added struct to maintain lifetime of pointers
Moved logic that operates on pointers into struct

Side note: I worked on this using the x86_64-pc-windows-msvc target and it builds fine.

Hi @pandarrr ,
Thanks for the PR!


Better plotting functions

We should improve the aesthetic of JAXspec when it comes to plotting results etc.

Add better handling of the x axis ticks


In contact:addrType the elements sp, pc  (contact::Address fields province, postal_code) are optional

The elements sp, pc are optional but the struct Address in module contact makes them compulsory.
Here is the schema definition from RFC 5733, page 31
<complexType name="addrType">
  <sequence>
    <element name="street" type="contact:optPostalLineType"
     minOccurs="0" maxOccurs="3"/>
    <element name="city" type="contact:postalLineType"/>
    <element name="sp" type="contact:optPostalLineType"
     minOccurs="0"/>
    <element name="pc" type="contact:pcType"
     minOccurs="0"/>
    <element name="cc" type="contact:ccType"/>
  </sequence>
</complexType>

Should I fix this and submit PR?

(FWIW, the fork is still young so it likely has many of the same data model issues as epp-client, though I think it might be better at dealing with different ways of encoding XML namespaces.)


fixed read file command for legacy python

fixes #133

[Current coverage][cc-pull] is 78.76%

Merging [#134][cc-pull] into [master][cc-base-branch] will increase coverage by 0.39%

@@             master       #134   diff @@
==========================================
  Files            16         16
  Lines          1558       1573    +15
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1221       1239    +18
+ Misses          337        334     -3
  Partials          0          0

Powered by Codecov. Last updated by [0f80a13...99552c1][cc-compare]
[cc-base-branch]: https://codecov.io/gh/crate/crash/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/crate/crash/compare/0f80a137b48ef51dc5e48a4a35c96d94ed20738d...99552c16933f03a2e56626f88bd0480b06acbd4c
[cc-pull]: https://codecov.io/gh/crate/crash/pull/134?src=pr

lgtm


/r/milking- new "reddit-logo" dosent replace old logo after complete set up

i have followed all of the set up steps to the best of my ability, and for some reason the stock reddit logo is appearing on the header to the left instead of the new "reddit-logo" icon. The old logo is covering both the Hot, and the New tabs. how do i solve this?

Hey,
You're supposed to upload it here

https://old.reddit.com/r/milking/about/edit/
Let me know is that worked out for you. @jm27904

gotcha thank you


Fix bound function internal prototype handling to match ES6

In ES6 (and ES7) internal prototype should be copied from the current internal prototype of the target, at the time of the .bind() call:

http://www.ecma-international.org/ecma-262/6.0/#sec-function.prototype.bind
http://www.ecma-international.org/ecma-262/6.0/#sec-boundfunctioncreate
Steps 2 and 8

In ES5 Function.prototype was used for bound functions:

https://www.ecma-international.org/ecma-262/5.1/#sec-<IP_ADDRESS>
Step 11: "Set the [[Prototype]] internal property of F to the standard built-in Function prototype object as specified in <IP_ADDRESS>."

Tasks:

[x] Change behavior
[ ] Fix testcases
[x] Migration note
[x] Releases entry

I wonder why they even went to the trouble of changing this in ES6.  Is it common in real-world code to change the internal prototype of a function to something other than Function.prototype?

I haven't encountered code doing that in practice. Just hypothetically, maybe if you implement some kind of RPC framework, RPC-backed methods might inherit from a different prototype.

Huh, so I was skimming through the specification and I found the section on Function.prototype.toString().  Unless I'm misreading the spec, it seems to require that either .toString() returns the actual function source code for an Ecmascript function, or else to return something that will cause a SyntaxError:
http://www.ecma-international.org/ecma-262/6.0/#sec-function.prototype.tostring
Specifically the last two bullets:

If the object was defined using ECMAScript code and the returned string representation is not in the form of a MethodDefinition or GeneratorMethod then the representation must be such that if the string is evaluated, using eval in a lexical context that is equivalent to the lexical context used to create the original object, it will result in a new functionally equivalent object. In that case the returned source code must not mention freely any variables that were not mentioned freely by the original function’s source code, even if these “extra” names were originally in scope.
If the implementation cannot produce a source code string that meets these criteria then it must return a string for which eval will throw a SyntaxError exception.

Duktape's current behavior matches neither: eval()ing the string will neither produce a "functionality equivalent object" (in fact it will produce a nop function), nor will it cause a syntax error.
Of course ES5.1 is naturally much less specific about this :)
http://www.ecma-international.org/ecma-262/5.1/#sec-<IP_ADDRESS>

An implementation-dependent representation of the function is returned. This representation has the syntax of a FunctionDeclaration. Note in particular that the use and placement of white space, line terminators, and semicolons within the representation String is implementation-dependent.

Yeah that seems changed - ES5.1 specifically requires that the .toString() result doesn't cause a SyntaxError :)

I guess there's so much code out there using .toString() to get function source code that throwing a syntax error on eval is preferable - otherwise the code may break in more subtle ways.

Code that relies on source code being available and working perfectly when parsed is quite weird in my opinion. There's never any guarantee that a particular function has been written in Ecmascript for instance.
But I see what you mean - maybe that's the reason for the change.

I agree - however, it does seem to be a common technique.  See this SO question, the bottom answer claims that at least AngularJS relies on Function.prototype.toString() returning actual source (I've yet to verify this claim but found it interesting):
http://stackoverflow.com/questions/16937940/in-what-javascript-engines-does-function-prototype-tostring-not-return-the-sourc

This is also interesting:
http://www.2ality.com/2016/08/function-prototype-tostring.html

So I think the best minimal change is to return e.g.:
function foo() { [ecmascript code] }

which won't parse, and will be similar to the suggested function foo() { [native code] }.

That has the nice property that it matches the syntax used by V8:
C:\Users\fatce>node
> Object.prototype.toString.toString()
'function toString() { [native code] }'

By the way, if function .toString() behavior is changed, be careful not to reintroduce the bug fixed by #554.

I know, although that's not really a bug in Duktape but rather a non-compatible expectation in Emscripten. There's no alternative though: either follow ES6 and potentially break Emscripten compatibility (not sure if that's the case - hopefully not), or don't follow ES6.


Login error

Hi!
Since yesterday I've been able to login to Fuckr without any kind of problem.
How can I solve this?

See #157

Closes #173


remove required .bash extension for load()

Allow load() to be used for bringing in an external bash script and testing individual functions without forcing a rename.
This is a breaking change for previous uses of load.

I think you should just use source instead.


Make python env show only when not the default.

Fixed open comment from https://github.com/caiogondim/bullet-train.zsh/pull/224/commits/cc57e991d95c5c464a2a8cfc6074e908e961ccd2?utf8=✓&diff=unified&w=1

Thank you @bedge, hope this can be merged in at some point @caiogondim

Thanks for the PR 👍


Is possible to use TIFF file as input?

Hello, my input file is tiff file with type is uint16. Could we use this file as input for training? Thanks

i think so, as long as you can convert it to rgb.

@endernewton: Thanks for your reply. I choose the tiff because RGB only contains grayscale [0~255], while my original image is uint16 bit scale. If I store it as RGB format, I will lose the information. Hence, converting is not good option for my case

@John1231983 who knows, try and see.


Allow specifying fetchOptions from Context

Hello! 👋
I am working on a GraphQL webapp, written in Next.js where Next.js SSR does the query fetching and then client hydrates the state and continues forward. The GraphQL API server requires authorization, through a simple bearer header. The frontend client does not get access to the authorization details, only the SSR part deals with that.
There's no simply way to do SSR and contextually pass down the fetchOptions with GQTY. This leaves us with two choices

Create a new Client then React Client where the fetcher has been generated with the auth token in context and uses it. This complicates things, as you have to use GQTY from the context everywhere, as having two different instances of it breaks query extraction, so one client during SSR, in components and getServerSideProps and the other in client in components
Create a global state on the server-side that looks a little something like this

The second approach is not concurrency safe, as it means two concurrent executions would fight for control over the global state.
I request that GQTY adds a way to specify fetchOptions via context so we can specify it through SSR and leave everything else untouched

Woah @steelbrain and @PabloSzx in the same place 🤯

@steelbrain You may want to try the new cachePolicy option in V3 😄
I am cleaning up old issues, please feel free to continue the conversation or reopen if you think the new option is not what you wanted.


Autocomplete - not working in Android mobile browser

(Sorry if I've missed something or if this is a browser-specific issue not fixable in Codemirror!)
In http://codemirror.net/demo/xmlcomplete.html (for example), '<' triggers autocomplete on iOS Safari and desktop Chrome but does not display anything on mobile Chrome on Android.
Working on iOS (Safari on iOS 11.2):

Not doing anything on mobile Chrome on Android (63.0.3239.111 on Android 7.0.0):

I'd really appreciate any help with this issue.

@MaximKraev Please are you able to fix this issue?


Hotfix for gateway user status check

What's done:

Added /api/$v1/avatar/** to allowedForInactiveEndpoints
Supported unauthorized users in gateway WebSecurityConfig

What about the 403 error for authorized users?

I was unable to reproduce


IRecurringJob Async Task Execute(PerformContext context) IRecurringJob

Could it be posible to add an Async interface for IRecurringJob?

I also encountered the same problem, have you solved it？ @Condor2708

I also encountered the same problem, have you solved it？ @Condor2708

is this project dead?


Add some logics and topics in Sets, Relation and Functions

Is your feature request related to a problem? Please describe.
I want to add the explanation of types of function, which is not available in website.
Here , in your website there is only name of that function and one line description which is not enough to understand, so I want to add this logic and explanation in detail.

Please assign me for this problem .
Thank you!

@sairish2001 please assign me!

Sorry, but no issues related to Documentation will be accepted.
You can move onto the Calculator, if you want to.


Test S3AM (SSEC) with URLs from public S3 Buckets

Local file worked, URL from public S3 bucket did not.  Stack trace below:
2015-08-07 19:46:42,361 upload(20585) Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/s3am/upload.py", line 263, in _stream_part
    self._upload_part( upload_id, part_num, buf )
  File "/usr/local/lib/python2.7/dist-packages/s3am/upload.py", line 316, in _upload_part
    headers=headers )
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/multipart.py", line 260, in upload_part_from_file
    query_args=query_args, size=size)
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/key.py", line 1293, in set_contents_from_file
    chunked_transfer=chunked_transfer, size=size)
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/key.py", line 750, in send_file
    chunked_transfer=chunked_transfer, size=size)
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/key.py", line 951, in _send_file_internal
    query_args=query_args
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/connection.py", line 664, in make_request
    retry_handler=retry_handler
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1071, in make_request
    retry_handler=retry_handler)
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1030, in _mexe
    raise ex
error: [Errno 104] Connection reset by peer

John, if you still have it, could you attach the command line you used to produce this?


Refactor ASTs

I think this is most of #618 and #623
Hopefully it's clean now?

Yeah, nice✨
I hope it helped, I had a few similar ideas, on what's duplicated in the llops, the code feels a lot nicer now.
I'll make a PR to fix the cuda runtime.


matcher: extend filter state matcher to http input

Commit Message: extend filter state matcher to http input
Additional Description: extend matching input of type 'FilterStateInput' to http input, which retrieves a specific filter state object by a given key and uses the serialized value as a matching candidate. It can be used to match route in route table.
Risk Level: low
Testing: unit test and manual testing
Docs Changes: matching_api
Release Notes: N/A
Platform Specific Features: N/A
Fixes #32807

@zhaoyangli311 CI has failed with build errors: https://source.cloud.google.com/results/invocations/a035e0a4-f914-4e0f-90c7-1dfb6a4505e9
/wait

gentle ping @kyessenov

Sorry, this looks good. A senior maintainer needs to merge since it touched core router code.

/retest

gentle ping @wbpcode

/wai-any

/retest

gentle ping @wbpcode , thanks for your help!


CTAM Test Full Device Update [F1] Testcase

Hi @MeritedHobbit ,
Unable to run the "F1" test case.
I have a "BKC_XX.pldm" pldm bundle image to flash and ran the "CTAM Test Full Device Update [F1] Testcase" and also updated the "package_info.json"  with path and package(pldm file).
{
"GPU_FW_IMAGE": {
"Path": "directopry from where we need to take the file.",
"Package": "BKC_XX.pldm",
"Version": "version",
"JSON": "<fwpkg_json_file.json>",
"Vendor": "Vendor Name"
}
}
what should be the contents in the "<fwpkg_json_file.json>"  ?
Regards,
Khader

Hi @khaderbmc ,
We have two options. Either get the header information from the gpu supplier as a json file. Or you could generate the header.json file from this repo. https://github.com/microsoft/pldm-fw-pkgr/tree/main (assuming you are using pldmspec 1.0)

Thanks for the quick help @MeritedHobbit

Hi @MeritedHobbit ,
I have provided the "Package": "BKC_XX.pldm" as pldm bundle in the  "package_info.json"  .
{
"GPU_FW_IMAGE": {
"Path": "directopry from where we need to take the file.",
"Package": "BKC_XX.pldm",
"Version": "version",
"JSON": "<fwpkg_json_file.json>",
"Vendor": "Vendor Name"
}
Will the F1 testcase be able to update the FW using pldm bundle or the package  should be the bin file ?


SSA again

Closes https://github.com/numba/numba/pull/4445

@sklam https://github.com/stuartarchibald/numba/commit/8ce7fbf451b8cbfec9af9a6b9574abbf25a2020c should sort out the problem with int hash.

@sklam https://github.com/stuartarchibald/numba/commit/f1860abfcd95072a5f4a700f0086c35a167c8adb fixes another test or two

@sklam https://github.com/numba/numba/commit/1f4715a30ef76a1a5694e3ada55c57bdcb658a1a sorts out a multiple-definition site problem in the tuple unroller, SSA highlighted it. Bug in SSA is that definition table needs to follow control flow (as noted over IRC).

literal_unroll tests are fixed (checked locally)
the def table problem (https://github.com/numba/numba/pull/5351#issuecomment-598860263) is because of my changes to interpreter.py which is now reverted.
32-bit int_hash still fails
still need to work on parfors errors

failures in `numba.tests.test_parfors`
======================================================================
ERROR: test_copy_global_for_parfor (numba.tests.test_parfors.TestPrange)
issue4903: a global is copied next to a parfor so that
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 2360, in test_copy_global_for_parfor
    self.prange_tester(test_impl, zz, tc, patch_instance=[0])
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3230, in get_parfor_reductions
    reductions, reduce_varnames, param_uses, param_nodes, var_to_param)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable lc.4 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_parfor_array_access2 (numba.tests.test_parfors.TestParfors)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1155, in test_parfor_array_access2
    self.check(test_impl, n)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 491, in check
    cfunc, cpfunc = self.compile_all(pyfunc, *args)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 93, in compile_all
    cpfunc = self.compile_parallel(pyfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable n.1.2 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_parfor_array_access3 (numba.tests.test_parfors.TestParfors)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1170, in test_parfor_array_access3
    self.check(test_impl, n)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 492, in check
    self.check_parfors_vs_others(pyfunc, cfunc, cpfunc, *args, **kwargs)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 148, in check_parfors_vs_others
    np.testing.assert_almost_equal(njit_output, py_expected, **kwargs)
  File "/Users/siu/miniconda3/envs/dev-numba-py37/lib/python3.7/site-packages/numpy/testing/_private/utils.py", line 599, in assert_almost_equal
    if abs(desired - actual) >= 1.5 * 10.0**(-decimal):
TypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'

======================================================================
ERROR: test_prange08 (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1884, in test_prange08
    check_fastmath=True)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable acc.3 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_prange08_1 (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1897, in test_prange08_1
    check_fastmath=True)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable acc.3 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_prange18 (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 2020, in test_prange18
    check_fastmath=True)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable acc.3 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_prange19 (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 2033, in test_prange19
    check_fastmath=True)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable acc.3 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_prange_conflicting_reduction_ops (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 2148, in test_prange_conflicting_reduction_ops
    self.prange_tester(test_impl, 9)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable c.3 other than in a supported reduction function is not permitted.

======================================================================
ERROR: test_prange_two_instances_same_reduction_var (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 2135, in test_prange_two_instances_same_reduction_var
    self.prange_tester(test_impl, 9)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1741, in prange_tester
    cpfunc = self.compile_parallel(pfunc, sig)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 81, in compile_parallel
    return self._compile_this(func, sig, flags=self.pflags)
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 78, in _compile_this
    return compile_isolated(func, sig, flags=flags)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 182, in compile_isolated
    flags, locals)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 555, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 331, in compile_extra
    return self._compile_bytecode()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 393, in _compile_bytecode
    return self._compile_core()
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 373, in _compile_core
    raise e
  File "/Users/siu/dev/numba/numba/core/compiler.py", line 364, in _compile_core
    pm.run(self.state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 341, in run
    raise patched_exception
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 332, in run
    self._runPass(idx, pass_inst, state)
  File "/Users/siu/dev/numba/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 291, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/Users/siu/dev/numba/numba/core/compiler_machinery.py", line 264, in check
    mangled = func(compiler_state)
  File "/Users/siu/dev/numba/numba/core/typed_passes.py", line 282, in run_pass
    parfor_pass.run()
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 2651, in run
    get_parfor_reductions(self.func_ir, p, p.params, self.calltypes)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3239, in get_parfor_reductions
    reduce_nodes = get_reduce_nodes(param, param_nodes[param], func_ir)
  File "/Users/siu/dev/numba/numba/parfors/parfor.py", line 3326, in get_reduce_nodes
    " other than in a supported reduction"
ValueError: Failed in nopython mode pipeline (step: convert to parfors)
Use of reduction variable c.3 other than in a supported reduction function is not permitted.

======================================================================
FAIL: test_prange_fastmath_check_works (numba.tests.test_parfors.TestPrange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 2247, in test_prange_fastmath_check_works
    self.assertTrue(fadd_inst.match(splitted[i + 1]))
AssertionError: None is not true

======================================================================
FAIL: test_use_of_reduction_var1 (numba.tests.test_parfors.TestParfors)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/siu/dev/numba/numba/tests/test_parfors.py", line 1069, in test_use_of_reduction_var1
    self.assertIn(msg, str(e.exception))
AssertionError: 'Use of reduction variable acc in an unsupported reduction function.' not found in 'Failed in nopython mode pipeline (step: convert to parfors)\nUse of reduction variable acc.2 in an unsupported reduction function.'

----------------------------------------------------------------------
Ran 183 tests in 218.441s

FAILED (failures=2, errors=9, skipped=22)

@sklam https://github.com/stuartarchibald/numba/commit/9b9df268ef51a1d4ebb8e5bab4989e33c17eef65 should fix:
test_prange_conflicting_reduction_ops
test_use_of_reduction_var1

and most of the reduction failures, it makes test_prange_18 into a lowering error though, which is going to need more effort.

Remaining parfor errors:

ERROR: test_parfor_array_access3 (numba.tests.test_parfors.TestParfors)
ERROR: test_prange18 (numba.tests.test_parfors.TestPrange)
FAIL: test_prange_two_instances_same_reduction_var (numba.tests.test_parfors.TestPrange)

@sklam https://github.com/stuartarchibald/numba/commit/8efb3b7d7b02e70ca0b84d57cc9c30503e7eb2ed should fix the syntax error on this branch, then I hope https://github.com/stuartarchibald/numba/commit/6a5d1655d74d2631f8a1e8bd4ef80af061897e9e will sort out the 32bit int hashing.

d875759 is failing on:
numba.tests.test_linalg.TestLinalgMatrixPower.test_linalg_matrix_power
numba.tests.test_try_except.TestTryExceptOtherControlFlow.test_yield
numba.tests.test_ir_inlining.TestFunctionInlining.test_inline_involved
numba.tests.test_annotations.TestTypeAnnotation.test_delete
numba.tests.test_dispatcher.TestDispatcher.test_misaligned_array_dispatch
numba.tests.test_dispatcher.TestDispatcher.test_misaligned_high_dimension_array_dispatch

seems like they were not caught before because of the test slicing features issue fixed in the recently merge https://github.com/numba/numba/pull/5369

With this branch, #5400, and #5369 all merged together, the CUDA test suite looks good (Tesla V100s on DGX-1) in the sense that all tests pass, except for this warning:
test_independent_scheduling (numba.cuda.tests.cudapy.test_warp_ops.TestCudaWarpOperations) ... /home/nfs/gmarkall/numbadev/numba/numba/core/ssa.py:310: NumbaWarning: Detected uninitialized variable ballot

File "numba/cuda/tests/cudapy/test_warp_ops.py", line 91:
def use_independent_scheduling(arr):
    <source elided>
        ballot = cuda.ballot_sync(0x88888888, True)
    arr[i] = ballot
    ^

  loc=loc),
ok

It might be that this test is a bit incorrect, so I'm going to look into it a bit now.

I think the test is correct, ballot is never uninitialized:
 81 def use_independent_scheduling(arr):
 82     i = cuda.threadIdx.x
 83     if i % 4 == 0:
 84         ballot = cuda.ballot_sync(0x11111111, True)
 85     elif i % 4 == 1:
 86         ballot = cuda.ballot_sync(0x22222222, True)
 87     elif i % 4 == 2:
 88         ballot = cuda.ballot_sync(0x44444444, True)
 89     elif i % 4 == 3:
 90         ballot = cuda.ballot_sync(0x88888888, True)
 91     arr[i] = ballot

I'm not going to be able to get up to speed on this PR very quickly, but I guess that none of the assignments dominates the assignment on line 91, and I presume there isn't extra analysis to determine that one of the four branches must be executed?

@sklam https://github.com/stuartarchibald/numba/commit/94dd96f10f93e1626b5a82f19ff342f13fd870d6 helps with the init problem which I think is root cause of matrix_power and dispatcher fails.
https://github.com/stuartarchibald/numba/commit/528646950856b9938e87bf78d58912095e98ffd2 fixes the inliner test, I think it was broken.

I think the test is correct, ballot is never uninitialized:
 81 def use_independent_scheduling(arr):
 82     i = cuda.threadIdx.x
 83     if i % 4 == 0:
 84         ballot = cuda.ballot_sync(0x11111111, True)
 85     elif i % 4 == 1:
 86         ballot = cuda.ballot_sync(0x22222222, True)
 87     elif i % 4 == 2:
 88         ballot = cuda.ballot_sync(0x44444444, True)
 89     elif i % 4 == 3:
 90         ballot = cuda.ballot_sync(0x88888888, True)
 91     arr[i] = ballot

I'm not going to be able to get up to speed on this PR very quickly, but I guess that none of the assignments dominates the assignment on line 91, and I presume there isn't extra analysis to determine that one of the four branches must be executed?

Correct. Could you perhaps assign something to ballot outside the if nest so it always has a value? Also https://github.com/stuartarchibald/numba/commit/94dd96f10f93e1626b5a82f19ff342f13fd870d6 might help and make a warning message appear about uninitialized variable use.

Also, thanks for testing the CUDA side @gmarkall

Could you perhaps assign something to ballot outside the if nest so it always has a value?

You could, but I think this flags up that there will be spurious uninitialized variable warnings in user code with this PR.

Also stuartarchibald@94dd96f might help and make a warning message appear about uninitialized variable use.

I think we wouldn't want messages like the above for this pattern though - the warning is a false positive.

Could you perhaps assign something to ballot outside the if nest so it always has a value?

You could, but I think this flags up that there will be spurious uninitialized variable warnings in user code with this PR.

Also stuartarchibald/numba@94dd96f might help and make a warning message appear about uninitialized variable use.

I think we wouldn't want messages like the above for this pattern though - the warning is a false positive.

On second look, I'm not sure it's a false positive, the if-tree has no else?

I think we wouldn't want messages like the above for this pattern though - the warning is a false positive.

On second look, I'm not sure it's a false positive, the if-tree has no else?

There are only 4 possibilities of i % 4 and all of them are covered.  Could just make the last elif just an else.

SSA can't tell that much. All it see is the control-flow paths.

I think the warning message can be a bit pedantic

smoking at numba_smoketest_cpu_27

Buildfarm is failing on (and consistently across all platforms etc):

numba.tests.test_looplifting.TestLoopLiftingInAction.test_recompilation_loop (assertion error, name not in live vars)
numba.tests.test_annotations.TestTypeAnnotation.test_delete (missing del's in output string, https://github.com/numba/numba/pull/5402/commits/1ad0a80f3c01e603e817807daae1e08dd2e51f55 might fix)

There's also:

PPC64LE builds are failing with the Invalid PPC CTR Loop! UNREACHABLE executed bug that intermittently appears, numba.tests.test_parfors_passes.TestConvertSetItemPass.test_setitem_gather_if_{array, scalar} are triggering it.

Seems like the test slicing still has a generated test pushing some slice to be off-by-N as the test_recompilation_loop error wasn't picked up by public CI.

Reminder: Add all the applicable cases from https://github.com/numba/numba/issues?q=is%3Aopen+is%3Aissue+label%3ASSA to the test suite.

SSA can't tell that much. All it see is the control-flow paths.

Whilst this is the case, the issue with the warning message is that it produces false positives - this example is a false positive because there is no possible input to use_independent_scheduling that results in the use of ballot before it is assigned to. Changing the test could well suppress the warning, but I don't think this is the right course of action - users' code will contain similar patterns, for which the warning will be emitted too.
I think having a warning that produces false positives enabled by default is not a good idea, because warning fatigue sets in quickly (and causes problems if code is written to catch warnings).
Perhaps a safer resolution would be to disable this check by default, and add a configuration option to enable it, so that a user who is trying to debug their code can turn it on to see potential uninitialized uses - the documentation for the option would have to mention that the warning can sometimes produce false positives because it uses an SSA-based analysis that only sees control flow, not value ranges and their propagation, perhaps even using the i % 4 type case from use_independent_scheduling as an example.

Thanks @gmarkall, I'm inclined to agree. I don't feel that these are false positives with knowledge of the constraints under which they appear, however, I agree that this may cause confusion/present unnecessary challenges as the constraints are non-trivial in explanation. Also, as noted, it's quite trivial to trigger them whilst doing something relatively common.
Making this configurable seems like a good idea, NUMBA_WARN_UNINITIALIZED as an env var/config option perhaps? When deeper analysis is added and confidence increases over giving unequivocally correct warnings that require no knowledge of the constraints under which they appear, such warnings can be raised irrespective of the option, I think this satisfies the good point made about warning fatigue.

@sklam https://github.com/numba/numba/pull/5402/commits/1ad0a80f3c01e603e817807daae1e08dd2e51f55 fixes the Annotation test failure, and https://github.com/numba/numba/pull/5402/commits/875f188dd18c9a31f14e84b20d049b5efb7d2608 adds in tests which come from the "SSA" label on github issues which are actually fixed by this PR. There are some others, which require e.g. type specialisation in branches, which are not fixed.

I am finding an error in SSA reconstruction that leads to the test_recompilation_loop failure

smoking again at numba_smoketest_cpu_28

Only failures for numba_smoketest_cpu_28 were on PPC64LE due to the LLVM Invalid PPC CTR Loop! UNREACHABLE executed bug. Good job @sklam!

https://github.com/numba/numba/pull/5402/commits/c95ae4601fd5bb1387845ab6221f5da1623b397d suppresses the PPC64LE LLVM bug.

Applied c95ae46

I need to add a config to stop warning about SSA variable all the time.


fix ocv_add_module CMake macro (3.0):

it tries to remove 'opencv_' prefix from 'name' variable, but
it creates new variable with the same name as module

:+1:


weex init always show error  "Invalid project name" !!!

Hi,  I use npm  installed weex-toolkit according to weex document.
node:       v6.11.3
npm:        5.4.2
system:   mac Sierra
error
When I use weex init weex-demo to init a project, always show error Invalid project name.
But use weex create weex-demo  is success.
please help me.
weex info:

error info

I got it.
In this edition, init has removed ！！！

need to change the guide in the official site:
https://weex.incubator.apache.org/guide/tools/toolkit.html


Add "transient" hint for notification

I think that adding this flag make sense. For example when using xfce4-notifyd and enabled logging, every change of volume is stored in history, but if notification is marked as transient, then it's skipped in log.

Is this addressed by #18? If so, I'd rather merge that.

Hi, what prevents this PR from being merged?

Lack of time and interest in the project, sadly.


[UI/UX Improvement]: Enhance Activity Log Section for Better User Experience

Description
The current design of the Activity Log section can be improved to provide a cleaner, more user-friendly experience.

Tasks

Improve Contrast and Readability:

Increase contrast between text and background for better clarity (e.g., light text on darker backgrounds).
Adjust font sizes to improve readability, especially for section headers and log details.

Implement Card-Based Layout:

Reorganize log entries for "HealthCare", "Location", and "Date" horizontally within cards for a compact and easy-to-scan layout.
Ensure consistent spacing between elements.

Simplify Date/Time Format:

Simplify the date and time format to: DD MMM YYYY, HH:MM (e.g., 16 Oct 2024, 19:10).
Use tooltips or small icons for more advanced time details like UTC offset.

Additional Notes

Maintain a modern, slightly lighter theme to make the interface feel fresh and user-friendly.

/assign me

@matinshaikh31 share your idea before you begin working on this issue

Hi!
Can you please assign me for this issue.
Below I have attached a figma screenshot for the idea what I thought of.

The text is more readable, UI is clear and easy-to-read.
The content is organised into cards for an easy-to-scan layout. I have used a consistent standard spacing in each element.
The date and time format will be formatted as required.

ok @Tanish2207 you suggestion look great to me, you can take this, and make sure the latest log appear top in respective section list


Fixed docblocks

$value in wrap and $table in wrapTable can be \Illuminate\Database\Query\Expression or string

You must use FQCNs.


Unable to import logstash!

After installling the Python3-logstash package in python 3.6  , i was unable to import .
Solution :+1:
I found that userparse package called in init.py by logstash was actually changed in python 3.6 to userlib.parse.
After changing the package in init.py of logstash the import was successful!

This is already fixed as far as I can see.


bump reva to latest edge

https://github.com/cs3org/reva/pull/4343 should fix the failing test

@micbar  @fschade I am not really sure if the current failure is it a bug in the code (reva) or in the tests. Is the receiver for a share (with edit role) supposed to be able to see the existing file versions? Then our viewer and editor roles lack the ListFileVersions permission. (Other I somehow think something is borked with the test)


Phpunit 7

Provide a narrative description of what you are trying to accomplish:

[ ] Are you fixing a bug?

[ ] Detail how the bug is invoked currently.
[ ] Detail the original, incorrect behavior.
[ ] Detail the new, expected behavior.
[ ] Base your feature on the master branch, and submit against that branch.
[ ] Add a regression test that demonstrates the bug, and proves the fix.
[ ] Add a CHANGELOG.md entry for the fix.

[ ] Are you creating a new feature?

[ ] Why is the new feature needed? What purpose does it serve?
[ ] How will users use the new feature?
[ ] Base your feature on the develop branch, and submit against that branch.
[ ] Add only one feature per pull request; split multiple features over multiple pull requests
[ ] Add tests for the new feature.
[ ] Add documentation for the new feature.
[ ] Add a CHANGELOG.md entry for the new feature.

[ ] Is this related to quality assurance?

[ ] Is this related to documentation?

Hm... Not sure how it happened, that this PR is opened twice with different target. Closing in favour of #22.


Remove redundant package from dependencies

Summary
The package @types/chart.js was added as a dependency in package.json, when it already exists in the devDependencies. My console shows a warning for this when running tests.
Ticket Link
https://mattermost.atlassian.net/browse/MM-18925
Related Pull Requests
https://github.com/mattermost/mattermost-webapp/pull/3855 introduced the duplication
If I understand correctly, the only reason we would want to have types in the dependencies section is if another repo imports mattermost-webapp and wants to know about those types. With that in mind, should all @types dependencies go into devDependencies?

Do any of these @types libraries need to be part of dependencies in the first place? They're only used at compile time as far as I know


Update to go 1.20

Closes: https://github.com/aws/eks-anywhere/issues/3267

/lgtm
Thanks Terry!

/approve


[Investigate] - "Total obtained does not match specific items collected"

Investigate why this warning keeps popping up for users. As far as I have found out from the community, this happens after uploading.

Closing as I meant to open this in the website repository. https://github.com/evansloan/collectionlog.net/issues/70


CI/CD - Automate the uploading of the example images to dockerhub

This issue is for discussing and implementing the steps required to automate the publishing of the helloworld and bookinfo images to dockerhub.
This is one aspect of the automation needed to satisfy the overall goals laid out in issue https://github.com/amalgam8/amalgam8/issues/406

Right now I perform the following manual steps for each A8 release (most relevant portion in bold):

Update changelog.
Update Dockerhub images to install new release.
Create interim release.
Build bookinfo/helloworld app images.
Verify bookinfo/helloworld demo steps in K8S and Docker environments.
Make release public.
Push bookinfo/helloworld images to Dockerhub.

Right now I run this bash command to upload the images
for i in "amalgam8/a8-examples-helloworld-sidecar:v1" "amalgam8/a8-examples-helloworld-sidecar:v2" "amalgam8/a8-examples-helloworld:v1" "amalgam8/a8-examples-helloworld:v2" "amalgam8/a8-examples-bookinfo-ratings-sidecar:v1" "amalgam8/a8-examples-bookinfo-ratings:v1" "amalgam8/a8-examples-bookinfo-reviews:v3" "amalgam8/a8-examples-bookinfo-reviews-sidecar:v2" "amalgam8/a8-examples-bookinfo-reviews-sidecar:v3" "amalgam8/a8-examples-bookinfo-reviews:v2" "amalgam8/a8-examples-bookinfo-reviews-sidecar:v1" "amalgam8/a8-examples-bookinfo-reviews:v1" "amalgam8/a8-examples-bookinfo-details-sidecar:v1" "amalgam8/a8-examples-bookinfo-details:v1" "amalgam8/a8-examples-bookinfo-productpage-sidecar:v1" "amalgam8/a8-examples-bookinfo-productpage:v1" "amalgam8/a8-controller:latest" "amalgam8/a8-registry:latest" "amalgam8/a8-sidecar:alpine"; do docker push $i; done

Merged