IFrame extension port

This is a port of the 'IFrame' extension from https://penguinmod.site/ . Credits to JeremyGamer13 for the original extension and TheShovel for porting it.

@GarboMuffin Mind fixing the Linting? I don't understand what it wants...

This barely works on some browsers, and the implementation on PenguinMod is messy. I wanted to tackle this with my own method of implementation and workflow layout later on

What browsers does this not work on?

For me Opera GX, admittedly I haven't tried it on any other browsers.

this is one of the extensions that i kinda dont care about anymore so im fine with it being added to TW if you are still gonna do that

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

I am not sure of how to do that.

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

I am not sure of how to do that.

Ogadaki, the creator of adacraft added this on adacraft, I don't know exactly how, but you can search in the source code on gitlab.
I think he made a program to delete all

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

you can do this with data urls but just being able to type html would be better

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

you can do this with data urls but just being able to type html would be better

Mind telling me how you can do that with data URLs? It would really help to make a simple implementation.

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

you can do this with data urls but just being able to type html would be better

Mind telling me how you can do that with data URLs? It would really help to make a simple implementation.

You can encode to base 64 the original code and convert it to dataURI, then create an Iframe for this dataURI

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

you can do this with data urls but just being able to type html would be better

Mind telling me how you can do that with data URLs? It would really help to make a simple implementation.

You can encode to base 64 the original code and convert it to dataURI, then create an Iframe for this dataURI

I remember trying this before... mind showing me a working example?

In the Iframe, can you add the bloc set HTML ? To add custom HTML, without using an external website!

you can do this with data urls but just being able to type html would be better

Mind telling me how you can do that with data URLs? It would really help to make a simple implementation.

You can encode to base 64 the original code and convert it to dataURI, then create an Iframe for this dataURI

I remember trying this before... mind showing me a working example?

the original code: <p> example </p>
The base64 code: PHA+IGV4YW1wbGUgPC9wPg==
The data URL code: data:html/plain;base64,PHA+IGV4YW1wbGUgPC9wPg==
Iframe + data URL: `

another way would be to change the url to about:blank, then edit the iframes document directly
im not sure what the browser support is for contentDocument on iframe elements but it would probably work for most use cases

there is also https://developer.mozilla.org/en-US/docs/Web/API/HTMLIFrameElement/srcdoc
to comply with our policies to protect user security, this will also not be merged without applying a sandbox (it's on https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe) to the iframe that does not contain allow-scripts (ideally just an empty string)

I have no idea how to do this stuff. I just made sure the extension doesn't need dependencies from PenguinMod, formated it correctly for TurboWarp, and removed some litmits.
I would be happy if someone could take it from here and make it ready for merging.

Once I get home I'm going to quickly throw together an iframe extension from the ground up to work in TurboWarp


WIP: implement packagesFrom

fixes #5

This new packagesFrom attribute would be useful. I hope this PR can be merged sometime in the future.

Same question as @srid here: I'm using haskellPackages.shellFor at work and would like to use devshell in some way, but I'm not sure how to get the best of both worlds.


No such file or directory : default.yml

When I trigger travis-ci build, I find these logs for error.
{ Error: ENOENT: no such file or directory, open '/home/travis/build/willhunger/Blog/themes/donob/i18n/default.yml'
    at Error (native)
    at Object.fs.openSync (fs.js:634:18)
    at Object.fs.readFileSync (fs.js:502:33)
    at Helper.resetLocales (/home/travis/.nvm/versions/node/v6.0.0/lib/node_modules/acyort/lib/generator/helper/index.js:36:41)
    at Generator.genHtmls (/home/travis/.nvm/versions/node/v6.0.0/lib/node_modules/acyort/lib/generator/index.js:47:18)
    at Generator.generate (/home/travis/.nvm/versions/node/v6.0.0/lib/node_modules/acyort/lib/generator/index.js:107:19)
    at _fetcher.fetch.then.then.data (/home/travis/.nvm/versions/node/v6.0.0/lib/node_modules/acyort/lib/acyort.js:17:35)
    at process._tickCallback (internal/process/next_tick.js:103:7)
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/travis/build/willhunger/Blog/themes/donob/i18n/default.yml' }

But build exited with 0.
How to deal with it?

@willhunger now fixed, you can trigger travis ci rebuild

Now it worked well.Thanks.


don't trigger 'ind' event

hi all,
when i start permitJoin device, i can see my device have been add PAN network.
but it don't trigger 'ind' event and  shepherd.list() return only Coordinator.
could you give me some suggestion with this?
I'm a beginner at full-stack iot development.
how to use the utilizes debug module on windows(win 7 64bit)
hw. cc2531 usb dongle.
fw. cc-znp

We have seen similar issues, usually restarting the software, reseting the device or ZNP dongle does the job.
Often this happens when the software is restarted. Our current operating theory is that the ZNP dongle thinks the device is joined in the firmware. I have not been able to find a place where Zigbee Shepherd asks  for a list of joined devices.
Perhaps executing a ZNP reset before start / init would solve the problem?

Internal discussion reveals:

Issue could be due to application close when allowing join, this can allow device to join when ZS not running. Never sending off any event.
Regardless, no events logged during period that ZS not online, therefore not aware of state.

Our proposed solution we are toying with at the moment is on-init to use assocFindDevice and assocCount to iterate the ZNP's status and mark devices as online/offline in devbox (the db).
Would love some feedback from the Zigbee Shepherd guys.

That would be limited to associations on the coordinator, it wouldn't pick up on associations on routers in the network.
Perhaps the approach described here: http://electronics.stackexchange.com/questions/199078/how-do-i-maintain-an-active-list-of-zigbee-devices-in-a-han

Initial implementation in our fork, cursory evaluation in our lab looks positive.

One outstanding issue with our patch is that IAS status changes are not being handled received by node.
We can communicate with the device just fine (e.g enrol to events), and the events are sent (packet sniffer confirmed), just nothing in ZS (DEBUG=*).

Hi @amigomcu.  you can try the node-env out to have the environment variable been set correctly in windows.

Under your project folder, npm install cross-env --save-dev
Run the server with cross-env: cross-env DEBUG=zigbee-shepherd* node server.js

Could you paste your code to us? Let's see if anything went wrong with the 'ind' issue.  Thanks!

Hi @splitice, I think your speculation on these two points is sensible:

Issue could be due to application close when allowing join, this can allow device to join when ZS not running. Never sending off any event.
Regardless, no events logged during period that ZS not online, therefore not aware of state.

My proposal is to have a handler to always disallow device joining when the server shutting down:
process.on('exit', function () {
     shepherd.permitJoin(0);
})`

But I wonder that this would not fully solve the problem, there is still a very little chance that a device comes into the network when ZS is not in the ready state and the ZNP dongle still opens for joining.

That still doesnt help as existing devices will stay joined during reboot, they will never re-join as they are in fact still joined. You could do a hardware reset instead. Still, it's not all that reliable and for some devices rejoining takes hours.
Our current method of doing an network scan is holding up well. Further work is required as per the TODO though in case we loose the database, or a new device joins while the software isnt running.


Update CLI References

The current CLI references are outdated and should be updated.
This is related to https://github.com/blockstack/docs/issues/733

I ran into this today; it caused me some headaches. I opened a pr to hopefully resolve this.


Atomic Linked List

Formatter and Tests

@a20012251 Done the changes
Also new PR for new.sh -> https://github.com/a20012251/lldb_folly_formatter/pull/10


Data Science with Python : Data Discretization during Pre Model Processing

Description
Welcome to the 'DSWP' Team, good to see you here.
With this issue, readers will get introduced to the core information about 'Data Discretization during Pre Model Processing' along with sample code completely in an effective way.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and the choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly, if you had used datasets, include them in "DS Datasets".
Domain: Machine Learning
Mentors Assigned: Kareem Negm | Shivang Dubey
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include the issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of the 'DSWP' domain.
All the best. Enjoy your journey ahead. 😎
Domain
Datascience with Python
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[ ] I will follow Contributing Guidelines & Code of conduct of this project.

Thankyou @prathimacode-hub
I will be working on documentation part of this issue
[x] I will follow Contributing Guidelines & Code of conduct of this project.


Problem while running setup_rouge.py

cloud-miracl@Cloud-Miracl:~/Bureau/Nouha/Projects/files2rouge$ python setup_rouge.py
files2rouge uses scripts and tools that will not be stored with the python package
where do you want to save it? [default: /home/cloud-miracl/.files2rouge/]/home/cloud-miracl/usr/local/anaconda/lib/python3.6/site-packages/files2rouge-2.0.0-py3.6.egg/files2rouge
Copying './files2rouge/RELEASE-1.5.5/' to '/home/cloud-miracl/usr/local/anaconda/lib/python3.6/site-packages/files2rouge-2.0.0-py3.6.egg/files2rouge'
Traceback (most recent call last):
File "setup_rouge.py", line 40, in
data = copy_rouge()
File "setup_rouge.py", line 33, in copy_rouge
shutil.copytree(src_rouge_root, path)
File "/home/cloud-miracl/usr/local/anaconda/lib/python3.6/shutil.py", line 315, in copytree
os.makedirs(dst)
File "/home/cloud-miracl/usr/local/anaconda/lib/python3.6/os.py", line 220, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/home/cloud-miracl/usr/local/anaconda/lib/python3.6/site-packages/files2rouge-2.0.0-py3.6.egg/files2rouge'

shutil.copytree actually tries to create a new directory, the path you're passing already exists, which raises an error.


Documentation: pics bug

I was trying to upload a new documentation but I encountered multiple bugs when uploading images. Couldn't seem to work out a pattern there. Images previously uploaded would suddenly disappear (multiple at a time). Had to go back and forth to check all ics were still there. Super weird.

child of #3

It's hard to understand what append here, can you explain how to reproduce the bug you encounter ?

Probably just have to try upload a documentation with multiple steps each including multiple pics.. As I said I can't understand the pattern to help reproduce it

Hopefully this will be fixed with the update I've made to docs file upload and delete. Merge requested (pending @BenGamma  review), will let you know when it's live for testing


.fsx file not colourized with latest bits.

Observe:

Are you sure it is not a duplicate of #1590?

@KevinRansom  The fix is not inserted into VS yet. To test it, you've to F5 the vsix locally.

Sweet ... Thanks


Beta V9

Hey, I wanted to switch to Beta-V9 everything has gone downhill literally everything breaks.
I create PR #52  for the patch but it is even with the patch, db. create not generation Unique id and creating user:⟨⟩.
I don't know if this is SurrealDB or Golang Driver cause this is Critical for Database Usage.
@phughk Could look into this.
I can even use db right now.

merged.


smart_reply

Summary
Explain the high-level impact of these commits in plain language.
Use bullet points for brevity.
Reasons
Provide the rationale for these changes.
Explain why these commits were necessary to address the issue.
Use bullet points for clarity.
References
Include links to relevant GitHub issues or helpful documentation to provide context.
If this PR resolves a GitHub issue, use "closes #123" format.

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

Comparison is base (fb4334e) 13.42% compared to head (e60bb7a) 12.66%.

Files
Patch %
Lines

...com/softteco/template/utils/NotificationHandler.kt
0.00%
78 Missing :warning:

.../com/softteco/template/utils/NotificationHelper.kt
0.00%
55 Missing :warning:

.../main/kotlin/com/softteco/template/MainActivity.kt
0.00%
22 Missing :warning:

...ature/notifications/AppFirebaseMessagingService.kt
0.00%
12 Missing :warning:

.../ui/feature/notifications/NotificationViewModel.kt
0.00%
11 Missing :warning:

...ature/notifications/SmartReplyBroadcastReceiver.kt
0.00%
7 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main       #3      +/-   ##
============================================
- Coverage     13.42%   12.66%   -0.76%
  Complexity       28       28
============================================
  Files            73       77       +4
  Lines          2615     2771     +156
  Branches        444      456      +12
============================================
  Hits            351      351
- Misses         2250     2406     +156
  Partials         14       14

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


AttributeError: 'NoneType' object has no attribute 'decode'

File "DDPG.py", line 22, in
from car_env import CarEnv
File "/home1/ /Self-driving-car-RL/Reinforcement-learning-with-tensorflow/experiments/2D_car/car_env.py", line 148, in
class Viewer(pyglet.window.Window):
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/init.py", line 357, in getattr
import(import_name)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/window/init.py", line 1816, in
gl._create_shadow_window()
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/gl/init.py", line 205, in _create_shadow_window
_shadow_window = Window(width=1, height=1, visible=False)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/window/xlib/init.py", line 163, in init
super(XlibWindow, self).init(*args, **kwargs)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/window/init.py", line 504, in init
config = screen.get_best_config(template_config)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/canvas/base.py", line 161, in get_best_config
configs = self.get_matching_configs(template)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/canvas/xlib.py", line 179, in get_matching_configs
configs = template.match(canvas)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/gl/xlib.py", line 29, in match
have_13 = info.have_version(1, 3)
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/gl/glx_info.py", line 86, in have_version
client_version = self.get_client_version().split()[0]
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/gl/glx_info.py", line 118, in get_client_version
return asstr(glXGetClientString(self.display, GLX_VERSION))
File "/home//workspace/tensorflow1.0-py3/lib/python3.5/site-packages/pyglet/compat.py", line 88, in asstr
return s.decode("utf-8")
AttributeError: 'NoneType' object has no attribute 'decode'
Same error with other experiments of this repository.
Did you ever meet this error?  I have tried many different versions of pyglet.
My env :  tf1.0 + py3.5 + Virtualenv

This error may be caused by using Windows I think. What is your operation system?

Ubuntu 14.04

hello,  Mr Zhou, I have solved it already. THX!

hello， How did you solve it


Format license

Hello, I'd like to fork your software for a project, but I'm not sure that's it's properly licensed unless the template is implemented. (I'd guess just the template being in LICENSE.txt is probably enough in court, but I'm no lawyer..)

The applied license is in the readme. This is a copy of the full license.

Got it thx


Can we get sliding animation for notifications and other layers?

It wold be hypr if the notifications could slide in and out instead of just fade. Thanks for the amazing work, btw.

dupe of #981


Enable typedefs jballerina-unit-tests

Purpose
$subject
Fixes #23605
Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #23606 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #23606   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 6e06a7c...eab152c. Read the comment docs.


⚠ Bofrost.fr has degraded performance

In a11246b, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1482 ms

Resolved: Bofrost.fr performance has improved in 18b0a5d after 8 minutes.


friendly printed arrays for json responses

before:

after:

LGTM after travis, solid if game. 👍


error on cart when rental booking update from backend

Bug report
Title
error on the cart when rental booking update from backend
Issue Description
error on the cart when rental booking update from backend
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- add to cart, rental booking per hourly basis
2. step2- Now, update rental booking on a daily basis from the backend
3. step3- reload a cart again.

Expected result
Actual result
item exists in cart(hourly basis) update to daily basis

item exists in cart(daily basis) update to hourly basis

fixed


Include/require format changed with @PhpCsFixer in v2.17.1?

Support question (& possible bug)
Prior with version 2.17.0 & @PhpCsFixer ruleset, code like the following one remains unformated
require_once '1.php';
require_once '2.php';

But since 2.17.1, the exact same code becomes: (line break are added)
require_once '1.php';

require_once '2.php';

I can't find any changelog about this modification.

could be related to #4831 , @SpacePossum ?
(btw, i see 2.16 not adding the line, but 2.17.0 already adding it (not only 2.17.1)

AFAIK this wasn't changed on 2.17.1. This change is done by blank_line_before_statement, which you probably run because of the PHP-CS-Fixer set, which has been updated in 2.16


Fixed compilation error.

Fixed a compilation error mentioning a potentially uninitialized local pointer variable named 'fileName'.

Try running \build\build_clean.cmd and clear the cache because the SAL annotations for out parameters don't have uninitialized warnings.

Try running \build\build_clean.cmd and clear the cache because the SAL annotations for out parameters don't have uninitialized warnings.

PS C:\Users\trpar\source\repos\systeminformer\build> .\build_release.cmd
Windows: 10.0.22621.3733 (WinBuild.160101.0800)
WindowsSDK: 10.0.22621.0 (17.10.34803.213)
VisualStudio: VisualStudio/17.10.3+35013.160
Building... 3.1.12319.7792 (0fa94ef) [master]
[00:00] Building SystemInformer (Win32)...
[ERROR] (1) SystemInformer\thrdprv.c(340): error C4703: potentially uninitialized local pointer variable 'fileName' used [C:\Users\trpar\source\repos\systeminformer\SystemInformer\SystemInformer.vcxproj]SystemInformer\sysscmem.c(1056): error C4703: potentially uninitialized local pointer variable 'kernelFileName' used [C:\Users\trpar\source\repos\systeminformer\SystemInformer\SystemInformer.vcxproj]LINK : fatal error LNK1257: code generation failed [C:\Users\trpar\source\repos\systeminformer\SystemInformer\SystemInformer.vcxproj]
Press any key to continue . . .

Something must have changed in another commit because the code compiles as is without these changes that I made a pull request for. I'm closing this pull request since it appears that it's not needed anymore.


NET SDK msbuild conflict in 20221127.1

Description
I tried building a project with dotnet 7.x.x and got an error that said msbuild was too old.
##[error]The nuget command failed with exit code(1) and error(/home/vsts/work/1/s/api/myproject/myproject.csproj : error : Version 7.0.100 of the .NET SDK requires at least version 17.3.0 of MSBuild. The current available version of MSBuild is <IP_ADDRESS>701. Change the .NET SDK specified in global.json to an older version that requires the MSBuild version currently available.

I then specified 6.0.403 in global.json and it also required a newer version of MSbuild than what was installed.
##[error]The nuget command failed with exit code(1) and error(/home/vsts/work/1/s/api/myproject/myproject.csproj : error : Version 6.0.403 of the .NET SDK requires at least version 17.0.0 of MSBuild. The current available version of MSBuild is <IP_ADDRESS>701. Change the .NET SDK specified in global.json to an older version that requires the MSBuild version currently available.

I'm not that familiar with the dotnet toolchain so I don't know if this is something that can be fixed with more options in our pipeline or other config files, or if it's an actual bug in the runner image.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
20221127.1
Is it regression?
20221002.2
Expected behavior
It should build with the installed version of msbuild.
Actual behavior
I get an error saying dotnet SDK requires msbuild 17.x.x.
Repro steps
Here is a copy of part of our azure-pipeline.yml with some details removed.   We have not yet tried to run this on an older ubuntu image, but that is going to be our next step to work around the problem.
trigger:
  - development
  - stage
  - production

pool:
  vmImage: 'ubuntu-latest'

variables:
  buildConfiguration: 'Release'

steps:
  - task: NuGetCommand@2
    inputs:
      command: 'restore'
      restoreSolution: '**/*.sln'
      feedsToUse: 'select'
      vstsFeed: '<a uuid>'

  - task: DotNetCoreCLI@2
    inputs:
      command: 'build'
      projects: 'api/projectdirectory'
      arguments: '--configuration Release --output $(Build.ArtifactStagingDirectory)/api'

hello @rfdrake, could you please provide minimal steps so we can try to reproduce the issue?

I'm going to try to make a public repo with a baseline config that reproduces the issue.  I'll post here with links to the repo if I can get it to fail the same way.

@rfdrake as ubuntu images have both .NET and mono installed it also has 2 flavours of msbuild installed as the msbuild and dotnet msbuild accordingly. From your yaml snippet and the output it looks like you are using the dot net core task but call msbuild from mono. You can compare its versions by calling msbuild --version and dotnet msbuild --version

It appears to not be caused by ubuntu-runner, but somewhere in our dependencies or some other aspect of our project.  Here is what I've been able to figure out so far:

It works when we switch from ubuntu-latest to ubuntu-20.04
I've thrown together the same dependencies in a test repository and can't get it to fail:

https://dev.azure.com/gigaMonster/example of msbuild issue/_git/example of msbuild issue
Here is a longer example of the error message.  I'm not sure if the msbuild message is the cause, or the 'Microsoft.NET.Sdk.Worker' message is the cause.  I'm guessing the NuGet task must be calling the msbuild from mono based on @mikhailkoliada 's reply, since this all happens in the NuGetCommand phase.
2022-12-02T20:09:40.5749231Z /home/vsts/work/1/s/api/Franklin.WorkerService/Franklin.WorkerService.csproj : error : Version 7.0.100 of the .NET SDK requires at least version 17.3.0 of MSBuild. The current available version of MSBuild is <IP_ADDRESS>701. Change the .NET SDK specified in global.json to an older version that requires the MSBuild version currently available.
2022-12-02T20:09:40.5751220Z /home/vsts/work/1/s/api/Franklin.WorkerService/Franklin.WorkerService.csproj : error MSB4236: The SDK 'Microsoft.NET.Sdk.Worker' specified could not be found.
2022-12-02T20:09:40.5752286Z /home/vsts/work/1/s/api/Franklin.MoveOutWorker/Franklin.MoveOutWorker.csproj : error MSB4236: The SDK 'Microsoft.NET.Sdk.Worker' specified could not be found.
2022-12-02T20:09:40.5753776Z /home/vsts/work/1/s/api/Franklin.SalesForce.ResidentWorker/Franklin.SalesForce.ResidentWorker.csproj : error MSB4236: The SDK 'Microsoft.NET.Sdk.Worker' specified could not be found.
2022-12-02T20:09:40.5754758Z /tmp/NuGetScratch/iv02szy6.ij8.nugetrestore.targets(298,5): warning MSB4181: The "MSBuild" task returned false but did not log an error. [/tmp/NuGetScratch/a9gckcw4.1i4.nugetinputs.targets]
2022-12-02T20:09:40.5756187Z /tmp/NuGetScratch/iv02szy6.ij8.nugetrestore.targets(310,5): warning : Skipping restore for project '/home/vsts/work/1/s/api/Franklin.WorkerService/Franklin.WorkerService.csproj'.  The project file may be invalid or missing targets required for restore. [/tmp/NuGetScratch/a9gckcw4.1i4.nugetinputs.targets]
2022-12-02T20:09:40.5757939Z /tmp/NuGetScratch/iv02szy6.ij8.nugetrestore.targets(310,5): warning : Skipping restore for project '/home/vsts/work/1/s/api/Franklin.MoveOutWorker/Franklin.MoveOutWorker.csproj'.  The project file may be invalid or missing targets required for restore. [/tmp/NuGetScratch/a9gckcw4.1i4.nugetinputs.targets]

I'm closing this since I don't believe it's an ubuntu-runner issue.  If anyone has any hints about what might fix it please let me know.  Our current plan is to stay on ubuntu-20.04.


Memory Leaks With Large Request

Hi,
I'm running large request with queue manager (bull) more than 8k URL, and after few minute my memory gets busted, from node inspector I know that network request take the big portion

So do you have any idea to prevent this? I mean, I want that after request completed, then it's disappeared from memory
btw I'm using request promise and this is my piece of my code
var adsListingQueue = Queue('adsListingQueue', config.redis.port, config.redis.host)

adsListingQueue.process(config.concurrency.getAdsListing, function (job, done) {
    var url = urijs(program.url)

    var page = job.data.page

    if (page > 1) {
        url.addQuery({
            page: page
        })
    }

    rp({
        uri: url.toString(),
        headers : {
            'User-Agent': randomUserAgent()
        },
        transform: function (body) {
            return cheerio.load(body)
        }
    })
        .then(function ($) {
            // just simple parsing with cheerio

            done()
        })
        .catch(function (err) {
            done(err)
        })
})

_.each(_.range(1, 500), function (item) {
    adsListingQueue.add({page: item})
})

Thanks

Perhaps related to https://github.com/request/request/pull/2051 ?


Can get error trying to save diagnostics\settings.json

This came up here, as well as in another case (internal report).
Here ie the stack:
[IOException: The process cannot access the file 'D:\home\site\diagnostics\settings.json' because it is being used by another process.]
    Does this code imply that we'll save it on every request? Note that we seems to have no code path that sets _enableTrace to false.

Hi
Kudu will continue to run in Azure App Service. However, this repo will no longer be maintained.
If the problem persists and is related to running on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Implement Dispatcher.UnhandledException and Dispatcher.UnhandledExceptionFilter

How was the solution implemented (if it's not obvious)?
Implements both Dispatcher.UnhandledException and Dispatcher.UnhandledExceptionFilter, by copypasting error handling logic from WPF. And adjusting DispatcherOperation logic in Avalonia.
The same as in WPF, this feature is not recommended for general use. Major nuances:

Many Avalonia events needs to be wrapped into DispatcherOperation.Send call, so exception in these handlers can be passed to the Dispatcher.UnhandledException. This PR ONLY implements it for TopLevel.Input events - basically the most common place for exceptions. I plan to adjust more places in following PR, but for the most part we are going to leave it for contributors, as the fundamental part is done in this PR.
Any exception has a potential to break Avalonia internal state. And yes, after many years the same can happen in WPF - try to throw exception in render size changed handles of Window.
Dispatcher.Invoke/InvokeAsync events bypass Dispatcher.UnhandledException completely. General rule of thumb - if method can return exception (by throwing it or as part of DispatcherOperation object), then UnhandledException is not executed (as these exceptions can be in fact handled by the used). The same behavior work in WPF (except old method based on LegacyInvokeImpl, but that's where WPF is even more broken).

Checklist

[x] Added unit tests (if possible)?
[x] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation - I would rather not.

Breaking changes
None
Fixed issues
Closes #13476
Fixes https://github.com/AvaloniaUI/Avalonia/issues/13393
Fixes https://github.com/AvaloniaUI/Avalonia/issues/8418

This is a great re-implementation of the WPF handling, thanks!
Please, make sure to check https://github.com/AvaloniaUI/Avalonia/pull/14229 as well. It happens that the loop that handles Dispatcher queue is broken (the native implementation stops and is not restarted ever after).
@maxkatz6 @kekekeks


140-move-plugins

Closes #140.

UPDATED AAC PACKAGE AND MOVED PLUGIN HOOKS TO THE AAC.PLUGINS PACKAGE TO AVOID CIRCULAR DEPENDENCIES
Updated hookimpl names to remove the aac package name as the new FQN would have been aac.plugins.hookimpl
Moved plugins into the python source directory
UPDATED AAC-SPEC to SPECIFICATIONS to avoid confusion with the AaC Core Spec
Updated plugin names for better consistency and removed redundant aac descriptors from names
Removed 1st party plugin versions since they'll always be versioned by the AaC package
Updated package setup to include all plugin model yaml files
Updated all plugins to load their model definition from their AaC DSL file.
Updated template engine loading to ignore non-jinja2 files in the templates directory.
Updated pipeline smoke test with new plugin model file locations
Added basic plugin models for plugins missing them
Added some additional tests to raise the code coverage to 80% -- will need to update several plugins for testability to improve coverage amounts.

Can you fix the merge conflict with the pipeline?


Authz: Decide if (I)Authorization and (I)ModuleAuthorization should be merged

(I)Authorization and (I)ModuleAuthorization are merged


LinkError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-1

Issue: LinkError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-1
The installation failed with a LinkError in a Python 2.7 environment where only the cudatoolkit is installed beforehand. This is strange because there is no error in another Python 3.6 env. Any ideas?

Environment (conda list):

$ conda list
# packages in environment at /home/ml/farleylai/Backups/miniconda3/envs/sinet27:
#
# Name                    Version                   Build  Channel
ca-certificates           2019.5.15                     0
certifi                   2019.3.9                 py27_0
chardet                   3.0.4                    pypi_0    pypi
cudatoolkit               10.0.130                      0
cython                    0.29.10                  pypi_0    pypi
easydict                  1.9                      pypi_0    pypi
idna                      2.8                      pypi_0    pypi
libedit                   3.1.20181209         hc058e9b_0
libffi                    3.2.1                hd88cf55_4
libgcc-ng                 9.1.0                hdf63c60_0
libstdcxx-ng              9.1.0                hdf63c60_0
mxnet-cu100mkl            1.4.1                    pypi_0    pypi
ncurses                   6.1                  he6710b0_1
numpy                     1.14.6                   pypi_0    pypi
opencv-python             <IP_ADDRESS>                 pypi_0    pypi
openssl                   1.1.1c               h7b6447c_1
pip                       19.1.1                   py27_0
python                    2.7.16               h9bab390_0
python-graphviz           0.8.4                    pypi_0    pypi
readline                  7.0                  h7b6447c_5
setuptools                41.0.1                   py27_0
sqlite                    3.28.0               h7b6447c_0
tk                        8.6.8                hbc83047_0
urllib3                   1.25.3                   pypi_0    pypi
wheel                     0.33.4                   py27_0
zlib                      1.2.11               h7b6447c_3

Details about  conda and system ( conda info ):

$ conda info
     active environment : sinet27
    active env location : /home/ml/farleylai/Backups/miniconda3/envs/sinet27
            shell level : 2
       user config file : /home/ml/farleylai/.condarc
 populated config files : /home/ml/farleylai/.condarc
          conda version : 4.6.14
    conda-build version : not installed
         python version : 3.7.1.final.0
       base environment : /home/ml/farleylai/Backups/miniconda3  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://conda.anaconda.org/pytorch/linux-64
                          https://conda.anaconda.org/pytorch/noarch
                          https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /home/ml/farleylai/Backups/miniconda3/pkgs
                          /home/ml/farleylai/.conda/pkgs
       envs directories : /home/ml/farleylai/Backups/miniconda3/envs
                          /home/ml/farleylai/.conda/envs
               platform : linux-64
             user-agent : conda/4.6.14 requests/2.21.0 CPython/3.7.1 Linux/4.15.0-51-generic ubuntu/16.04.3 glibc/2.23
                UID:GID : 8531:3000
             netrc file : None
           offline mode : False

Details about  conda install:

$ conda install cudatoolkit-dev
Collecting package metadata: done
Solving environment: done

## Package Plan ##

  environment location: /home/ml/farleylai/Backups/miniconda3/envs/sinet27

  added / updated specs:
    - cudatoolkit-dev

The following NEW packages will be INSTALLED:

  asn1crypto         pkgs/main/linux-64::asn1crypto-0.24.0-py27_0
  cffi               pkgs/main/linux-64::cffi-1.12.3-py27h2e261b9_0
  chardet            pkgs/main/linux-64::chardet-3.0.4-py27_1
  conda              pkgs/main/linux-64::conda-4.6.14-py27_0
  cryptography       pkgs/main/linux-64::cryptography-2.7-py27h1ba5d50_0
  cudatoolkit-dev    conda-forge/linux-64::cudatoolkit-dev-10.0-1
  enum34             pkgs/main/linux-64::enum34-1.1.6-py27_1
  futures            pkgs/main/linux-64::futures-3.2.0-py27_0
  idna               pkgs/main/linux-64::idna-2.8-py27_0
  ipaddress          pkgs/main/linux-64::ipaddress-1.0.22-py27_0
  pycosat            pkgs/main/linux-64::pycosat-0.6.3-py27h14c3975_0
  pycparser          pkgs/main/linux-64::pycparser-2.19-py27_0
  pyopenssl          pkgs/main/linux-64::pyopenssl-19.0.0-py27_0
  pysocks            pkgs/main/linux-64::pysocks-1.7.0-py27_0
  requests           pkgs/main/linux-64::requests-2.22.0-py27_0
  ruamel_yaml        pkgs/main/linux-64::ruamel_yaml-0.15.46-py27h14c3975_0
  six                pkgs/main/linux-64::six-1.12.0-py27_0
  urllib3            pkgs/main/linux-64::urllib3-1.24.2-py27_0
  yaml               pkgs/main/linux-64::yaml-0.1.7-had09818_2

Proceed ([y]/n)? y

Preparing transaction: done
Verifying transaction: done
Executing transaction: - ERROR conda.core.link:_execute_post_link_actions(658): An error occurred while installing package 'conda-forge::cudatoolkit-dev-10.0-1'.
LinkError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-1
running your command again with `-v` will provide additional information
location of failed script: /home/ml/farleylai/Backups/miniconda3/envs/sinet27/bin/.cudatoolkit-dev-post-link.sh
==> script messages <==
<None>

Attempting to roll back.

failed
ERROR conda.core.link:_execute(568): An error occurred while installing package 'conda-forge::cudatoolkit-dev-10.0-1'.
LinkError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-1
running your command again with `-v` will provide additional information
location of failed script: /home/ml/farleylai/Backups/miniconda3/envs/sinet27/bin/.cudatoolkit-dev-post-link.sh
==> script messages <==
<None>

Attempting to roll back.

Rolling back transaction: done

LinkError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-1
running your command again with `-v` will provide additional information
location of failed script: /home/ml/farleylai/Backups/miniconda3/envs/sinet27/bin/.cudatoolkit-dev-post-link.sh
==> script messages <==
<None>

I have no experience debugging conda-forge build errors, but I noticed another package with similar problems tracing this error back to SSL problems. It looks like you may be able to either (a) pin wget, (b) bump the conda executable version, or (c) mess with the environmental variable SSL_CERT_FILE. I hope that helps point you in the right direction.
https://github.com/bioconda/bioconda-recipes/issues/13846

@slochower, thank you for chiming in!
@farleylai,

The installation failed with a LinkError in a Python 2.7 environment where only the cudatoolkit is installed beforehand. This is strange because there is no error in another Python 3.6 env. Any ideas?

The Python script used during the post-installation step requires Python >=3.5. However, prior #11, the Python version wasn't specified in the requirements section of the recipe. This might be an explanation for the mysterious failure of the installation when using Python 2.7
Today, Python version is specified in the recipe:
https://github.com/conda-forge/cudatoolkit-dev-feedstock/blob/e4f70263ded3c38feb769d4dbfd908192cc37a48/recipe/meta.yaml#L18-L20

This issue may be more complex. I'm working on a recipe that attempts to use cudatoolkit-dev as a dependency, but it reliably fails to install cudatoolkit-dev at the post-link stage when I try to test the recipe locally with ./.circleci/run_docker_build.sh:

Post-link error:
```
Executing transaction: ...working... done
ERROR conda.core.link:_execute(656): An error occurred while installing package 'conda-forge::cudatoolkit-dev-10.0-2'.
Rolling back transaction: ...working... done
Traceback (most recent call last):
  File "/home/conda/.ci_support/build_all.py", line 131, in
    build_all(args.recipes_dir, args.arch)
  File "/home/conda/.ci_support/build_all.py", line 68, in build_all
    build_folders(recipes_dir, new_comp_folders, arch, channel_urls)
  File "/home/conda/.ci_support/build_all.py", line 121, in build_folders
    conda_build.api.build([recipe], config=get_config(arch, channel_urls))
  File "/opt/conda/lib/python3.7/site-packages/conda_build/api.py", line 209, in build
    notest=notest, need_source_download=need_source_download, variants=variants)
  File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 2343, in build_tree
    notest=notest,
  File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 1407, in build
    create_build_envs(top_level_pkg, notest)
  File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 1247, in create_build_envs
    is_conda=m.name() == 'conda')
  File "/opt/conda/lib/python3.7/site-packages/conda_build/environ.py", line 867, in create_env
    execute_actions(actions, index)
  File "/opt/conda/lib/python3.7/site-packages/conda/common/io.py", line 88, in decorated
    return f(*args, **kwds)
  File "/opt/conda/lib/python3.7/site-packages/conda/plan.py", line 321, in execute_actions
    execute_instructions(plan, index, verbose)
  File "/opt/conda/lib/python3.7/site-packages/conda/plan.py", line 533, in execute_instructions
    cmd(state, arg)
  File "/opt/conda/lib/python3.7/site-packages/conda/instructions.py", line 73, in UNLINKLINKTRANSACTION_CMD
    unlink_link_transaction.execute()
  File "/opt/conda/lib/python3.7/site-packages/conda/core/link.py", line 245, in execute
    self._execute(tuple(concat(interleave(itervalues(self.prefix_action_groups)))))
  File "/opt/conda/lib/python3.7/site-packages/conda/core/link.py", line 672, in _execute
    rollback_excs,
conda.CondaMultiError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-2
location of failed script: /home/conda/feedstock_root/build_artifacts/simplejson_1564338724346/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/bin/.cudatoolkit-dev-post-link.sh
==> script messages <==

==> script output <==
stdout:
stderr: Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/simplejson_1564338724346/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/bin/cudatoolkit-dev-post-install.py", line 44, in
    from conda.exports import download, hashsum_file
ModuleNotFoundError: No module named 'conda'
```

To reproduce:

Clone https://github.com/conda-forge/staged-recipes
Copy recipes/example/ to a new recipe recipes/test/
./.circleci/run_docker_build.sh will succeed in building the test recipe
Now add cudatoolkit-dev under the host: dependencies to recipes/example/meta.yaml
./.circleci/run_docker_build.sh will fail to install cudatoolkit-dev in the post-link stage

Complete output below:

Complete output:
```
(base) lski2414:staged-recipes.jchodera choderaj$ ./.circleci/run_docker_build.sh
Containers: 6
 Running: 0
 Paused: 0
 Stopped: 6
Images: 1
Server Version: 18.09.2
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.125-linuxkit
Operating System: Docker for Mac
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.952GiB
Name: linuxkit-025000000001
ID: NHMZ:YBTQ:PE3V:C6NK:2YMW:REFH:3T7T:FWOZ:JLCX:DTBI:7QUB:K3V6
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine
No active host found
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.

export PYTHONUNBUFFERED=1

PYTHONUNBUFFERED=1

cat

cp -r /home/conda/staged-recipes/recipes /home/conda/conda-recipes

cp -r /home/conda/staged-recipes/.ci_support /home/conda/.ci_support

echo 'Finding recipes merged in master and removing them from the build.'
Finding recipes merged in master and removing them from the build.

pushd /home/conda/staged-recipes/recipes

'[' False == True ']'

xargs -I '{}' sh -c 'rm -rf ~/conda-recipes/{} && echo Removing recipe: {}'

git ls-tree --name-only master -- .
 This is only useful when pretending to be on another arch, such as for rendering necessary dependencies on a non-native arch. I trust that you know what you're doing.
WARNING conda_build.config:arch(288): Setting build arch. This is only useful when pretending to be on another arch, such as for rendering necessary dependencies on a non-native arch. I trust that you know what you're doing.
rendering /home/conda/conda-recipes/test for linux-64
Setting build platform. This is only useful when pretending to be on another platform, such as for rendering necessary dependencies on a non-native platform. I trust that you know what you're doing.
WARNING conda_build.config:platform(302): Setting build platform. This is only useful when pretending to be on another platform, such as for rendering necessary dependencies on a non-native platform. I trust that you know what you're doing.
Computed that there are 3 distributions to build from 1 recipes
Resolved dependencies, will be built in the following order:
simplejson-3.8.2-python_3.6-on-linux-64
simplejson-3.8.2-python_2.7-on-linux-64
simplejson-3.8.2-python_3.7-on-linux-64
Adding in variants from internal_defaults
INFO conda_build.variants:_combine_spec_dictionaries(189): Adding in variants from internal_defaults
Adding in variants from /opt/conda/conda_build_config.yaml
INFO conda_build.variants:_combine_spec_dictionaries(189): Adding in variants from /opt/conda/conda_build_config.yaml
Adding in variants from config.variant
INFO conda_build.variants:_combine_spec_dictionaries(189): Adding in variants from config.variant
Attempting to finalize metadata for simplejson
INFO conda_build.metadata:finalize_outputs_pass(699): Attempting to finalize metadata for simplejson
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
BUILD START: ['simplejson-3.8.2-py36h516909a_0.tar.bz2']
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done

Package Plan
environment location: /home/conda/feedstock_root/build_artifacts/simplejson_1564338724346/h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
The following NEW packages will be INSTALLED:
_libgcc_mutex:   0.1-main             defaults
ca-certificates: 2019.6.16-hecc5488_0 conda-forge
certifi:         2019.6.16-py36_1     conda-forge
cudatoolkit-dev: 10.0-2               conda-forge
libffi:          3.2.1-he1b5a44_1006  conda-forge
libgcc-ng:       9.1.0-hdf63c60_0     defaults
libstdcxx-ng:    9.1.0-hdf63c60_0     defaults
ncurses:         6.1-hf484d3e_1002    conda-forge
openssl:         1.1.1c-h516909a_0    conda-forge
pip:             19.2.1-py36_0        conda-forge
python:          3.6.7-h357f687_1005  conda-forge
readline:        8.0-hf8c457e_0       conda-forge
setuptools:      41.0.1-py36_0        conda-forge
sqlite:          3.29.0-hcee41ef_0    conda-forge
tk:              8.6.9-hed695b0_1002  conda-forge
wheel:           0.33.4-py36_0        conda-forge
xz:              5.2.4-h14c3975_1001  conda-forge
zlib:            1.2.11-h516909a_1005 conda-forge

Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
ERROR conda.core.link:_execute(656): An error occurred while installing package 'conda-forge::cudatoolkit-dev-10.0-2'.
Rolling back transaction: ...working... done
Traceback (most recent call last):
File "/home/conda/.ci_support/build_all.py", line 131, in
build_all(args.recipes_dir, args.arch)
File "/home/conda/.ci_support/build_all.py", line 68, in build_all
build_folders(recipes_dir, new_comp_folders, arch, channel_urls)
File "/home/conda/.ci_support/build_all.py", line 121, in build_folders
conda_build.api.build([recipe], config=get_config(arch, channel_urls))
File "/opt/conda/lib/python3.7/site-packages/conda_build/api.py", line 209, in build
notest=notest, need_source_download=need_source_download, variants=variants)
File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 2343, in build_tree
notest=notest,
File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 1407, in build
create_build_envs(top_level_pkg, notest)
File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 1247, in create_build_envs
is_conda=m.name() == 'conda')
File "/opt/conda/lib/python3.7/site-packages/conda_build/environ.py", line 867, in create_env
execute_actions(actions, index)
File "/opt/conda/lib/python3.7/site-packages/conda/common/io.py", line 88, in decorated
return f(*args, **kwds)
File "/opt/conda/lib/python3.7/site-packages/conda/plan.py", line 321, in execute_actions
execute_instructions(plan, index, verbose)
File "/opt/conda/lib/python3.7/site-packages/conda/plan.py", line 533, in execute_instructions
cmd(state, arg)
File "/opt/conda/lib/python3.7/site-packages/conda/instructions.py", line 73, in UNLINKLINKTRANSACTION_CMD
unlink_link_transaction.execute()
File "/opt/conda/lib/python3.7/site-packages/conda/core/link.py", line 245, in execute
self._execute(tuple(concat(interleave(itervalues(self.prefix_action_groups)))))
File "/opt/conda/lib/python3.7/site-packages/conda/core/link.py", line 672, in _execute
rollback_excs,
conda.CondaMultiError: post-link script failed for package conda-forge::cudatoolkit-dev-10.0-2
location of failed script: /home/conda/feedstock_root/build_artifacts/simplejson_1564338724346/h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/bin/.cudatoolkit-dev-post-link.sh
==> script messages <==

==> script output <==
stdout:
stderr: Traceback (most recent call last):
File "/home/conda/feedstock_root/build_artifacts/simplejson_1564338724346/h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/bin/cudatoolkit-dev-post-install.py", line 44, in
from conda.exports import download, hashsum_file
ModuleNotFoundError: No module named 'conda'
return code: 1
()
</details>

Now add cudatoolkit-dev under the host: dependencies to recipes/example/meta.yaml

Have you tried adding conda under the host as well?

How embarrassing! That indeed does the trick in allowing the installation of cudatoolkit-dev to complete within conda build---thanks so much, and my apologies for not realizing this was now required.
The build doesn't complete locally, but that is likely for totally unrelated reasons. Full output below just in case.

(base) lski2414:staged-recipes.jchodera choderaj$ ./.circleci/run_docker_build.sh
Containers: 7
 Running: 0
 Paused: 0
 Stopped: 7
Images: 1
Server Version: 18.09.2
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.125-linuxkit
Operating System: Docker for Mac
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.952GiB
Name: linuxkit-025000000001
ID: NHMZ:YBTQ:PE3V:C6NK:2YMW:REFH:3T7T:FWOZ:JLCX:DTBI:7QUB:K3V6
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine
No active host found
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.

export PYTHONUNBUFFERED=1

PYTHONUNBUFFERED=1

cat

cp -r /home/conda/staged-recipes/recipes /home/conda/conda-recipes

cp -r /home/conda/staged-recipes/.ci_support /home/conda/.ci_support

echo 'Finding recipes merged in master and removing them from the build.'
 This is only useful when pretending to be on another arch, such as for rendering necessary dependencies on a non-native arch. I trust that you know what you're doing.
WARNING conda_build.config:arch(288): Setting build arch. This is only useful when pretending to be on another arch, such as for rendering necessary dependencies on a non-native arch. I trust that you know what you're doing.
rendering /home/conda/conda-recipes/test for linux-64
Setting build platform. This is only useful when pretending to be on another platform, such as for rendering necessary dependencies on a non-native platform. I trust that you know what you're doing.
WARNING conda_build.config:platform(302): Setting build platform. This is only useful when pretending to be on another platform, such as for rendering necessary dependencies on a non-native platform. I trust that you know what you're doing.
Computed that there are 3 distributions to build from 1 recipes
Resolved dependencies, will be built in the following order:
simplejson-3.8.2-python_3.7-on-linux-64
simplejson-3.8.2-python_3.6-on-linux-64
simplejson-3.8.2-python_2.7-on-linux-64
Adding in variants from internal_defaults
INFO conda_build.variants:_combine_spec_dictionaries(189): Adding in variants from internal_defaults
Adding in variants from /opt/conda/conda_build_config.yaml
INFO conda_build.variants:_combine_spec_dictionaries(189): Adding in variants from /opt/conda/conda_build_config.yaml
Adding in variants from config.variant
INFO conda_build.variants:_combine_spec_dictionaries(189): Adding in variants from config.variant
Attempting to finalize metadata for simplejson
INFO conda_build.metadata:finalize_outputs_pass(699): Attempting to finalize metadata for simplejson
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
BUILD START: ['simplejson-3.8.2-py37h516909a_0.tar.bz2']
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done

Package Plan
environment location: /home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
The following NEW packages will be INSTALLED:
_libgcc_mutex:          0.1-main                  defaults
asn1crypto:             0.24.0-py37_1003          conda-forge
bzip2:                  1.0.8-h516909a_0          conda-forge
ca-certificates:        2019.6.16-hecc5488_0      conda-forge
certifi:                2019.6.16-py37_1          conda-forge
cffi:                   1.12.3-py37h8022711_0     conda-forge
chardet:                3.0.4-py37_1003           conda-forge
conda:                  4.7.10-py37_0             conda-forge
conda-package-handling: 1.3.11-py37_0             conda-forge
cryptography:           2.7-py37h72c5cf5_0        conda-forge
cudatoolkit-dev:        10.0-2                    conda-forge
icu:                    64.2-he1b5a44_0           conda-forge
idna:                   2.8-py37_1000             conda-forge
libarchive:             3.3.3-hb44662c_1005       conda-forge
libffi:                 3.2.1-he1b5a44_1006       conda-forge
libgcc-ng:              9.1.0-hdf63c60_0          defaults
libiconv:               1.15-h516909a_1005        conda-forge
libstdcxx-ng:           9.1.0-hdf63c60_0          defaults
libxml2:                2.9.9-hee79883_2          conda-forge
lz4-c:                  1.8.3-he1b5a44_1001       conda-forge
lzo:                    2.10-h14c3975_1000        conda-forge
ncurses:                6.1-hf484d3e_1002         conda-forge
openssl:                1.1.1c-h516909a_0         conda-forge
pip:                    19.2.1-py37_0             conda-forge
pycosat:                0.6.3-py37h14c3975_1001   conda-forge
pycparser:              2.19-py37_1               conda-forge
pyopenssl:              19.0.0-py37_0             conda-forge
pysocks:                1.7.0-py37_0              conda-forge
python:                 3.7.3-h33d41f4_1          conda-forge
python-libarchive-c:    2.8-py37_1004             conda-forge
readline:               8.0-hf8c457e_0            conda-forge
requests:               2.22.0-py37_1             conda-forge
ruamel_yaml:            0.15.71-py37h14c3975_1000 conda-forge
setuptools:             41.0.1-py37_0             conda-forge
six:                    1.12.0-py37_1000          conda-forge
sqlite:                 3.29.0-hcee41ef_0         conda-forge
tk:                     8.6.9-hed695b0_1002       conda-forge
tqdm:                   4.32.2-py_0               conda-forge
urllib3:                1.25.3-py37_0             conda-forge
wheel:                  0.33.4-py37_0             conda-forge
xz:                     5.2.4-h14c3975_1001       conda-forge
yaml:                   0.1.7-h14c3975_1001       conda-forge
zlib:                   1.2.11-h516909a_1005      conda-forge
zstd:                   1.4.0-h3b9ef0a_0          conda-forge

Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Package Plan
environment location: /home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/_build_env
The following NEW packages will be INSTALLED:
_libgcc_mutex:          0.1-main          defaults
binutils_impl_linux-64: 2.31.1-h6176602_1 defaults
binutils_linux-64:      2.31.1-h6176602_7 defaults
gcc_impl_linux-64:      7.3.0-habb00fd_1  conda-forge
gcc_linux-64:           7.3.0-h553295d_7  conda-forge
libgcc-ng:              9.1.0-hdf63c60_0  defaults
libstdcxx-ng:           9.1.0-hdf63c60_0  defaults

Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
Source cache directory is: /home/conda/feedstock_root/build_artifacts/src_cache
INFO conda_build.source:download_to_cache(43): Source cache directory is: /home/conda/feedstock_root/build_artifacts/src_cache
Downloading source to cache: simplejson-3.8.2_d58439c548.tar.gz
INFO conda_build.source:download_to_cache(66): Downloading source to cache: simplejson-3.8.2_d58439c548.tar.gz
Downloading https://pypi.io/packages/source/s/simplejson/simplejson-3.8.2.tar.gz
INFO conda_build.source:download_to_cache(80): Downloading https://pypi.io/packages/source/s/simplejson/simplejson-3.8.2.tar.gz
Success
INFO conda_build.source:download_to_cache(91): Success
Extracting download
source tree in: /home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/work
export PREFIX=/home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
export BUILD_PREFIX=/home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/_build_env
export SRC_DIR=/home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/work
ln: target `/home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/bin/zstdmt' is not a directory
Traceback (most recent call last):
File "/home/conda/.ci_support/build_all.py", line 131, in
build_all(args.recipes_dir, args.arch)
File "/home/conda/.ci_support/build_all.py", line 68, in build_all
build_folders(recipes_dir, new_comp_folders, arch, channel_urls)
File "/home/conda/.ci_support/build_all.py", line 121, in build_folders
conda_build.api.build([recipe], config=get_config(arch, channel_urls))
File "/opt/conda/lib/python3.7/site-packages/conda_build/api.py", line 209, in build
notest=notest, need_source_download=need_source_download, variants=variants)
File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 2343, in build_tree
notest=notest,
File "/opt/conda/lib/python3.7/site-packages/conda_build/build.py", line 1491, in build
cwd=src_dir, stats=build_stats)
File "/opt/conda/lib/python3.7/site-packages/conda_build/utils.py", line 397, in check_call_env
return _func_defaulting_env_to_os_environ('call', *popenargs, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/conda_build/utils.py", line 377, in _func_defaulting_env_to_os_environ
raise subprocess.CalledProcessError(proc.returncode, _args)
subprocess.CalledProcessError: Command '['/bin/bash', '-e', '/home/conda/feedstock_root/build_artifacts/simplejson_1564345777932/work/conda_build.sh']' returned non-zero exit status 1.

This issue should be fixed in #16. Feel free to reopen

I am having the same issue using this package in bioconda's builds (see https://circleci.com/gh/bioconda/bioconda-recipes/100387):
LinkError: post-link script failed for package conda-forge::cudatoolkit-dev-10.1.243-h516909a_3
location of failed script: /opt/conda/conda-bld/pp-sketchlib_1585141860567/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/bin/.cudatoolkit-dev-post-link.sh

Unfortunately I don't get the full output as to what's failing. Any thoughts on what might be causing this? It looks like it works on a local conda install. Could it be a permissions or existing files issue with the symlinks?

broken again for cudatoolkit-dev=11.2

I am having a similar problem. Conda install works for older version of cudatoolkit (11.3) and cudnn(8.2.1). Whe you try installing the newer versions, I get the same error. When I look at the file it is poi nting to -> c:\users\om\anaconda3\envs\deeplearning\Scripts.cudatoolkit-post-link.bat, I do not see suvh a thing with file explorer. I get a stderr: 'chcp' is not recognized as internal or external command, operable program or batch file. What am I missing? I am running windows 11, have GeForce RTX 3070 Ti and latest driver installed.. Shoudl I be trying tyo add something to my user path variable? Any comments or suggestions would be greatly appreciated. Thank you.


Extension not working on remote SSH?

@pmichel31415 commented on Thu Sep 12 2019

Environment data

VS Code version: 1.38.1
Extension version (available under the Extensions sidebar): 2019.9.34911
OS and version: Windows 10 (CentOS 7 on remote)
Python version (& distribution if applicable, e.g. Anaconda): 3.6.4 64 bit anaconda
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: N/A
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): True

Expected behaviour
When connected to the remote host using the "Remote - SSH" extension, the Python extension recognizes .py files and syntax highlighting is available.
Actual behaviour
(Same as #6509, copied here)
When connected to the remote host, .py files are not recognized (VSCode recognizes them as Plain Text) and syntax highlighting does not work. The following error pops up in the bottom right-hand corner when opening a .py file:
[ms-python.python]: Unknown language in `contributes.python.language`. Provided value: python

When "Show disabled extensions" is selected in the Extensions tab, the "Python Language Basics" extension is among the list of disabled extensions. There is no option to enable or install it. Despite the fact that the Python extension is already installed on the remote host (dev-server), the following text appears where an "Enable" or "Install" button would normally appear:

Install the extension on 'SSH: dev-server' to enable.

Steps to reproduce:

Install VSCode on local machine
Install Python3 on remote host
Install "Remote - SSH" extension in VSCode
Use "Remote - SSH" to connect to the remote host
Install "Python" extension in VSCode on the remote host
Attempt to open any .py file
Issue persists even after multiple reinstalls / folder cleanups.

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
User belongs to experiment group 'AlwaysDisplayTestExplorer - control'
> conda --version
> pyenv root
> python3.7 -c "import sys;print(sys.executable)"
> python3.6 -c "import sys;print(sys.executable)"
> python3 -c "import sys;print(sys.executable)"
> python2 -c "import sys;print(sys.executable)"
> python -c "import sys;print(sys.executable)"
> ~/anaconda3/bin/python -c "import sys;print(sys.executable)"
Starting Jedi Python language engine.
> conda info --json
> conda env list
> conda info --json
> conda env list
> ~/anaconda3/bin/python ~/.vscode-server/extensions/ms-python.python-2019.9.34911/pythonFiles/interpreterInfo.py
> ~/anaconda3/bin/python ~/.vscode-server/extensions/ms-python.python-2019.9.34911/pythonFiles/interpreterInfo.py
> ~/anaconda3/bin/python -m pip --version

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
notificationsAlerts.ts:40 [ms-python.python]: Unknown language in `contributes.python.language`. Provided value: python
onDidNotificationChange @ notificationsAlerts.ts:40

@pmichel31415 commented on Sat Sep 14 2019
OK so I managed to fix this in a very ugly way so not sure whether this issue should be closed or not but in case someone faces the same issue here's what I tried

Remove the vscode-server from my VSCode client with Ctrl+Maj+P -> "Remote SSH: Kill Vscode Server on Host" and reconnect: didn't work
Manually run rm -rf ~/.vscode-server on my remote machine: didn't work somehow rm didn't want to remove some folders
Move ~/.vscode-server to a trash folder on my remote and reconnect from the client: didn't work
I connected to another remote I had access to. No problems there. zipped and sent the ~/.vscode-server from the new remote (where ms-python.python was working) to the old remote: somehow worked!!!

What I've noticed is that for instance  ~/.vscode-server/bin/b37e54c98e1a74ba89e03073e5a3761284e3ffb0/node_modules was empty on my old remote and would remain so even after removing ~/.vscode-server and reconnecting.

@DonJayamanne commented on Sun Sep 15 2019
Thanks for reporting this issue, unfortunately, this is issue with VS Code.
I'm glad you have managed to get this resolved, hence I'm closing this issue and moving it to VS Code.

Please note this isn't an extension issue as the user managed to resolve this issue by deleting the ~/.vscode-server folder.


add 	R example on list

only add readme base functions sample list in R
Description

Motivation and Context

[ ] I have raised an issue to propose this change (required)

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I've read the CONTRIBUTION guide
[ ] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I don't understand why also ca9b1f4.

Merging. Thanks again @mrchypark


Fix E2E tests for IR.

These are some relatively minor fixes for bugs which accrued while I was away.  The E2E tests were failing sometimes when using IR, these changes fix that.
The ec_recover_test still fails with IR but will be resolved when the new B512 code in sway-lib-std is released.

A new version of sway-lib-std was released so that should help with failing tests here.


[VL] shuffle writer failed - Invalid: Failed to insert rows

Backend
VL (Velox)
Bug description
24/08/13 13:28:42 ERROR [Executor task launch worker for task 6582.0 in stage 9.0 (TID 15705)] util.TaskResources: Task 15705 failed by error:
org.apache.gluten.exception.GlutenException: Native write: shuffle writer failed - Invalid: Failed to insert rows. Remaining rows: 854
	at org.apache.gluten.vectorized.ShuffleWriterJniWrapper.write(Native Method)
	at org.apache.spark.shuffle.ColumnarShuffleWriter.internalWrite(ColumnarShuffleWriter.scala:180)
	at org.apache.spark.shuffle.ColumnarShuffleWriter.write(ColumnarShuffleWriter.scala:239)
	at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:59)
	at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
	at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
	at org.apache.spark.scheduler.Task.run(Task.scala:131)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1471)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:509)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)
E20240813 13:28:44.709362 161310 Exceptions.h:67] Line: /home/binweiyang/gluten/ep/build-velox/build/velox_ep/velox/exec/Task.cpp:1864, Function:terminate, Expression:  Cancelled, Source: RUNTIME, ErrorCode: INVALID_STATE
24/08/13 13:28:44 ERROR [Executor task launch worker for task 6582.0 in stage 9.0 (TID 15705)] executor.Executor: Exception in task 6582.0 in stage 9.0 (TID 15705)
org.apache.gluten.exception.GlutenException: Native write: shuffle writer failed - Invalid: Failed to insert rows. Remaining rows: 854
	at org.apache.gluten.vectorized.ShuffleWriterJniWrapper.write(Native Method)
	at org.apache.spark.shuffle.ColumnarShuffleWriter.internalWrite(ColumnarShuffleWriter.scala:180)
	at org.apache.spark.shuffle.ColumnarShuffleWriter.write(ColumnarShuffleWriter.scala:239)
	at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:59)
	at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
	at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
	at org.apache.spark.scheduler.Task.run(Task.scala:131)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1471)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:509)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)
24/08/13 13:37:36 ERROR [SIGTERM handler] executor.CoarseGrainedExecutorBackend: RECEIVED SIGNAL TERM

Spark version
Spark-3.2.x
Spark configurations
No response
System information
No response
Relevant logs
No response

fixed by 6832


ci: update e2e apimodel to 2004

Reason for Change:

Remove ubuntu 16.04 from cluster creation's since it's out of support
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

/azp run

/azp run


Improvements on CPU Usage core widget

Summary of the pull request
This pull request adds some changes to the CPU Usage widget to address some of its accessibility problems. Here, the update time interval for all the core widgets are increased and the CPU widget was changed to open the Task Manager instead of killing the process from a button click.

References and relevant issues
#1284
Detailed description of the pull request / Additional comments
The interval time for the update of all core widgets are increased from 1 second to 3 seconds. The CPU widget lost its buttons to kill the processes and have a new button to open the task manager from it.
Validation steps performed
Tested locally.
PR checklist

[ ] Closes #1284
[ ] Tests added/passed
[ ] Documentation updated

LOVE this.

@guimafelipe and @krschau noticed this was still in draft mode for about a month. Is it still valid/being worked on?

There were already some changes in CPU widget, so I will close this PR for now.


Finish Support for Virtual Entities

The architecture currently supports virtual entities in concept. The metadata supports it and you can manually construct a virtual entity by specifying a pseudo-base-table and creating a custom base view. The base table is ignored in this situation and the CodeGen tool uses the custom base view provided to do metadata work.
This works, but is a bit of a hack. The intent is to better support virtual entities directly as follows:

An admin can create a virtual entity manually in the UI by simply defining the entity name and providing the base view for it. Base Table won't be required in this case. Also, the Admin would populate one or more Entity Field records to specify the primary key for the virtual entity.
From there, we need to update the CodeGenLib to implement support for virtual entities properly. The vast majority of the existing code will work fine but we have to test it out
Write some documentation explaining the use of virtual entities so people can take advantage of this concept.

Rolled it in MemberJunction 2.5x


Error Retrieving Partial Objects with byte range in ballerinax/aws.s3 Library

Description:
Attempting to download objects partially, by using byte range in the objectRetrievalHeaders and passing it as an argument to the getObject function results in an error. The error occurs when the server responds with a status code of 206 - Partial Content, indicating a successful partial retrieval. However, the getObject function only considers a status code of 200 as successful, leading to the following error:

error GenericClientError ("Error occurred while retrieving the xml payload from the response",error ParserError ("Error occurred while extracting xml data from entity: error("failed to parse xml: Unexpected character 'T' (code 84) in prolog; expected '<'
 at [row,col {unknown-source}]: [1,1]")"))

Debugging the library code reveals that the getObject function considers only a 200 status code as a success.
Steps to reproduce:

Create an S3 bucket with sample objects or use an existing one.
Set up the objectRetrievalHeaders with byte range specifications for partial object retrieval.
Call the getObject function with the specified byte range headers.

Affected Versions:
Ballerina version: 2201.4.1
ballerinax/aws.s3 version: 3.2.0
OS, DB, other environment details and versions:
OS: Ubuntu 22.04.3 LTS
openjdk 11.0.2 2019-01-15

In the getObject implementation all other 2xx codes except 200 is considered unsuccessful an returns the payload as an error.


#95 Fix merge issue and reformat code after merge of #80 and #85

Coverage decreased (-0.006%) to 91.824% when pulling 56c53535541dbbb06a85ac4257440e3c4993fd06 on issue-95 into 6aa464810cbef9e954b7be9d5fbc166e9073e663 on master.


[Mobile] "Create proposal" button is absent on physical device

This issue is observed on physical android device Nokia 8 with Android 9.
In the web browser everything is OK with any resolution. Issue is reproducible on physical device only.
AR: "Create proposal" button is absent
ER: "Create proposal" button should be present

Not an issue


Vulcanize strips dynamic

I had the following in a template:
<template is="dom-repeat" items="[[_somePaths]]" as="path">
  <script src$="[[path]]" defer></script>
</template>

In order to dynamically load some JS within a template.
After the vulcanization step it stripped the <script> tag. Perhaps checking to see if the src attribute is set dynamically would help this?

Vulcanize should understand templates. Can you file a bug?
On May 8, 2016 10:40 AM, "Andrew Bonventre"<EMAIL_ADDRESS>wrote:

I had the following in a template:

In order to dynamically load some JS within a template.
After the vulcanization step it stripped the

Oh, this is a bug! Shouldn't be checking email right now :)
On May 8, 2016 11:52 AM, "Justin Fagnani"<EMAIL_ADDRESS>wrote:

Vulcanize should understand templates. Can you file a bug?
On May 8, 2016 10:40 AM, "Andrew Bonventre"<EMAIL_ADDRESS>wrote:

I had the following in a template:

In order to dynamically load some JS within a template.
After the vulcanization step it stripped the


feat(driverProvider/sauce) Add build Id as configurable option

Add build Id as a configurable option for sauce users
Update sanity tests to run on the built dir
Update sanity tests to call getNewDriver() function

closes #2240
Tested by running sanity tests locally. Attached are screen shots of the execution, and the build shown at sauce labs.

Note: I've regenerated my sauce key so no worries about it showing in the screenshot

Looks like the test failed because of flash.

closed with 582411b7ad6c0f9176b231dc51dc328b98affbdf


Sveltekit crashes on startup

Describe the bug
Unable to bootstrap a new Sveltekit app. Looks like it's blowing up here: https://github.com/sveltejs/kit/pull/2726/files#diff-3d3392afaae8a848f5862f73d4cfa9e50f984b68ecd1d91f6c414ece0de4f23bR114
 ❯❯❯ npm init svelte@next sample-app
npx: installed 5 in 1.42s

create-svelte version 2.0.0-next.89

Welcome to SvelteKit!

This is beta software; expect bugs and missing features.

Problems? Open an issue on https://github.com/sveltejs/kit/issues if none exists already.

✔ Which Svelte app template? › Skeleton project
✔ Use TypeScript? … No / Yes
✔ Add ESLint for code linting? … No / Yes
✔ Add Prettier for code formatting? … No / Yes

Your project is ready!
✔ Typescript
  Inside Svelte components, use <script lang="ts">
✔ ESLint
  https://github.com/sveltejs/eslint-plugin-svelte3
✔ Prettier
  https://prettier.io/docs/en/options.html
  https://github.com/sveltejs/prettier-plugin-svelte#options

Install community-maintained integrations:
  https://github.com/svelte-add/svelte-adders

Next steps:
  1: cd sample-app
  2: npm install (or pnpm install, etc)
  3: git init && git add -A && git commit -m "Initial commit" (optional)
  4: npm run dev -- --open

To close the dev server, hit Ctrl-C

Stuck? Visit us at https://svelte.dev/chat

~/Desktop ❯❯❯ cd sample-app
~/D/sample-app ❯❯❯ npm install

><EMAIL_ADDRESS>postinstall /Users/jakthom/Desktop/sample-app/node_modules/esbuild
> node install.js

><EMAIL_ADDRESS>postinstall /Users/jakthom/Desktop/sample-app/node_modules/svelte-preprocess
> echo "[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: node-sass/sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc..."

[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: node-sass/sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc...
npm notice created a lockfile as package-lock.json.  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/jakthom/.npm/_logs/2021-11-28T18_31_20_941Z-debug.log

Reproduction
Go through the Getting Started steps here:
https://kit.svelte.dev/docs#introduction-getting-started
Logs
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/Users/jakthom/.nodenv/versions/12.22.1/bin/node',
1 verbose cli   '/Users/jakthom/.nodenv/versions/12.22.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'dev'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /Users/jakthom/.nodenv/versions/12.22.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/jakthom/Desktop/sample-app/node_modules/.bin:/Users/jakthom/.nodenv/versions/12.22.1/bin:/usr/local/Cellar/nodenv/1.4.0/libexec:/Users/jakthom/.poetry/bin:/Users/jakthom/Library/pnpm:/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin:/Users/jakthom/.local/bin:/Users/jakthom/.nodenv/shims:/Users/jakthom/.pyenv/shims:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/jakthom/Desktop/sample-app
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'svelte-kit dev' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
13 verbose stack Error<EMAIL_ADDRESS>dev: `svelte-kit dev`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/Users/jakthom/.nodenv/versions/12.22.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:314:20)
13 verbose stack     at ChildProcess.<anonymous> (/Users/jakthom/.nodenv/versions/12.22.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:314:20)
13 verbose stack     at maybeClose (internal/child_process.js:1022:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /Users/jakthom/Desktop/sample-app
16 verbose Darwin 21.1.0
17 verbose argv "/Users/jakthom/.nodenv/versions/12.22.1/bin/node" "/Users/jakthom/.nodenv/versions/12.22.1/bin/npm" "run" "dev"
18 verbose node v12.22.1
19 verbose npm  v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>dev: `svelte-kit dev`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

System Info
npx envinfo --system --binaries --browsers --npmPackages "{svelte,@sveltejs/*,vite}"
npx: installed 1 in 0.992s

  System:
    OS: macOS 12.0.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 21.59 GB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.22.1 - ~/.nodenv/versions/12.22.1/bin/node
    npm: 6.14.12 - ~/.nodenv/versions/12.22.1/bin/npm
  Browsers:
    Chrome: 96.0.4664.55
    Firefox: 94.0
    Safari: 15.1
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.3
    @sveltejs/kit: next => 1.0.0-next.201
    svelte: ^3.44.0 => 3.44.2

Severity
annoyance
Additional Information
No response

sveltekit requires node 14 at least. You are on 12 as indicated by the error message


Feature/automated soft credits  affiliations

Implemented functionality that allows a data entry user to define which specific Affiliation records should receive OCRs when an Opportunity is created. Work Item #: W-009097.
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

So here are some issues I've run into:

if I have a Relationship between two household members, and the relationships specify a contact role, then when an Opp is saved with one of the contacts being the primary contact, there is the correct OCR from the relationship created.  But the 'Household Member' OCR, that is normally created, is missing.

If I have two household members, with Relationships between them specifying OCR role 'Soft Credit', and both contacts also have an Affiliation to an organizational account (such as their foundation), specifying an OCR role 'Foundation Donor'.  Then when I create an organizational donation from their foundation account, and specify one of the contacts as the primary donor, I do get OCR's for both with 'Foundation Donor' and the correct contact's OCR is marked Primary.  But I do not get OCR's for Soft Credit.  I assume this is because your code is only applying Relationship OCR's for Individual donations, not Org donations.  We need to get agreement with @mpusto on whether this is the correct behavior or not.

I have two household members with an Organization account and Affiliations to that account.  The affliations have OCR role 'Soft Credit'.  The NPSP Settings for Default Organizational Contact Role is set to 'Matched Donor'.  Now create an organizational Opportunity with one of the contacts as primary contact.  You end up with 3 OCR's (Soft Credit, Soft Credit, Matched Donor) which is correct, but both of the OCR's for the primary contact is marked Primary, which is incorrect.  only one should be marked primary, and I believe it should be the Matched Donor one.

Rather than continuing more adhoc testing that I think might find more issues, let's look at this thoroughly.  There are 4 ways that OCR's get auto created in NPSP:

the OCR for the Primary Contact on the Opportunity (controlled by the Default Opportunity Contact Role and Default Organizational Contact Role NPSP Settings)
the household member OCR's (controlled by the Household Member Contact Role and Household Contact Roles On NPSP Settings)
the Relationships OCR's
the Affiliation OCR's

I think we need to test the interplay of all these settings with both individual Opps and org Opps, to ensure the correct OCR's result.  I bet we could come up with a single helper test routine that took flags to specify which of the OCR Settings to consider, and what the expected results to be.  Then you could easily test the full set of permutations.  Creating the matrix of expected results would also help us ensure we have the full spec thought out.

@davidhabib -- Thanks for the scenarios. The ad hoc/edge case testing is helpful in presenting the possible usage of the feature. Currently, we have in place test charters for three of the four scenarios listed:

the OCR for the Primary Contact on the Opportunity (controlled by the Default Opportunity Contact Role and Default Organizational Contact Role NPSP Settings)  -- The focus has been on the new Organizational setting.
the Relationships OCRs
the Affiliation OCRs

I'll follow up with @mpusto and the team about the Household member scenarios as well as mapping out the feature's usage, which is basically creating a matrix. I really like the mapping/matrix to test the interplay of Individual and Organizational Opportunities and their OCRs.

Keeping everyone in the loop regarding the issues Dave raised on Monday, April 23rd.
Scenario #1 -- I'm currently working on the fix for this issue. Extra time is required to review the code, implement the change, and test the fix in order to ensure that other parts of the code aren't impacted because the issue is inside of a single method that performs multiple tasks.
Scenario #2 -- During a discussion with the team on April 25th, it was decided by @mpusto that Opportunity Contact Role records will not be created for the Primary Contact's Relationships on an Organizational Gift at this time.
Scenario #3 -- The issue described reflects salesforce standard behavior. The IsPrimary field is "Defaulted on create" and per the documentation (https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_opportunitycontactrole.htm):
Indicates whether the associated Contact plays the primary role on the Opportunity (true) or not (false). Each Opportunity has only one primary contact. Label is Primary.
Please reach out with questions.
@alex-peralta, @force2b

Thanks so much for jumping in and testing the code, Mike!
I'll schedule some time for us to chat about the items called out.


Error handling

Label under harebrained ideas.
MPI operations are generally fallible, but rsmpi generally ignores any such errors and proceeds as though the operation was successful. The natural way to handle fallibility would be to return Result<T, E>, but the question is what is E and how does this interact with drop. Suppose we write the following:
fn f(comm) -> Result<(), NoncollectiveError> {
  comm.barrier()?;
  comm.all_reduce_into(...)?;
  Ok(());
}

If the first line errors on one rank, it'll return from f while the other ranks deadlock in the all_reduce_into. I think we need to avoid this and ensure that collectives are only called in functions that return CollectiveError<'c> where 'c is a lifetime associated with the communicator. MPI primitives would return Result<T, NoncollectiveError> and the caller would need to be responsible for making them collective in order to safely proceed to the next line. Now I'm just spitballing, but I think there are two ways to do this:

Create a result.consensus(comm)?; that promotes Result<T, NoncollectiveError> to Result<T, CollectiveError>. This sort of thing requires polling on a nonblocking collective, possibly with a timeout to panic if a rank has vanished (in which case it's hard to even determine which ranks are alive, much less return with a consistent state). If any ranks are Err(NoncollectiveError(e)) on input, then all ranks will Err(CollectiveError(e)).

Variant of 1 in which NoncollectiveError "knows" which communicator it's associated with so one can use result.consensus()?;. You'd impl From<NoncollectiveError<'c1>> for NoncollectiveError<'c2>, with constraints on the relationship between 'c1 and 'c2 (these might need to be runtime checks rather than static lifetime checks).

Note that in both cases, one will probably want an execution mode to be unsafe or panic to avoid the run-time cost of the nonblocking collectives necessary for consensus.

Give up on safely propagating errors and instead get panics to use MPI_Abort and set MPI_ERRORS_ARE_FATAL.

@hppritcha @jtronge I think this is a summary of my half-baked ideas for handling errors. I think with objects like an MPI_Win that must be dropped collectively, you'd want any scope that can have ownership of the Win to return a result E that cannot be converted to non-collective using from or other functions. That way you could only call in a function returning suitable collective errors. I haven't thought deliberately about whether lifetimes can be made to enforce all the constraints statically.

I think we're drifting into ULFM land here a bit with these concerns.  The way to make this code "work" in the presence of faults or other error returns from collective operations.   Item 1 above  has been the source for numerous papers and phd dissertation theses, and code (in c).  Putting on my ULFM hat I'd write the code like this:
fn f(comm) -> Result<(), CollectiveError> {
let rc = comm.barrier();
let flag = 0;
if (MPI_SUCCESS == rc) {
flag = 1
}
comm.mpix_comm_agree(&flag);
if (!flag) {
/* uh oh, something happened to one or more of my partners /
comm.MPIX_Comm_revoke;  / this will cause other processes who maybe got success on the barrier and charging ahead to the allreduce to get a an error there, so no deadlock /
return MPIX_ERR_PROC_FAILED;
}
rc = comm.all_reduce_into(...);
/ same check above if rc == MPI_SUCCESS) using the mpix_comm_agree consensus  /
else
if (MPIX_ERR_REVOKED == rc) {
/ we failed out because some processes died between the barrier call and this collective, so return error */
return MPI_ERR_REVOKED;
}
Ok(());
}
I think the most common error that wouldn't involve process failure would be invalid parameters, which means a buggy program, in which case we could have a default rustmpi error handler just do the rusty thing of aborting the program by doing a MPI_Abort on MPI_COMM_WORLD.
Note that by default,  with Open MPI 5.0.0 and later,  ULFM MPI extensions are available.

(Commenting to follow)

I see those MPIX_ functions are available in MPICH-4.1a1 as well. Is there a good place to look for complete examples that can handle vanishing processes? I don't have a sense for whether that's a realistic mode for rsmpi, though if we can make it safer using the type system, maybe it'll be a place people will seek out for writing this sort of fault-tolerant MPI.
There's a really nice post by Andrew Gallant (author of ripgrep) on Rust error handling, and when unwrap (panic) is okay.
https://blog.burntsushi.net/unwrap/
It would be useful to outline what kind of errors could be raised by MPI and that a user would possibly expect to recover from (at least enough to clean up, say closing local file handles). If the answer is none, then we can stick with the current strategy, though I think we should still work with MPI_ERRORS_RETURN (raising our own panic/MPI_Abort). If there are good use cases, we'll want to work out how much we can get the type system to do.

this is probably a place to start:
https://github.com/ICLDisco/ulfm-testing/
note for Open MPI this stuff is only in the 5.0.0 pre-release and main.
Yes to your point above, we would need to do a taxonomy of possible errors returned from collective calls (including non-blocking), decide which ones the application might be able to handle (MPI_ERR_ARG maybe), and for now flame out for MPI_ERR_PROC_FAILED, etc.
I mainly brought up ULFM here because of the consensus function it introduced, not so much for all the shrinking/recovery  functionality.

After talking with Howard about this, we think there's a couple different ways that this could be solved.  I agree, like you said, there's probably some way that we can utilize the type system here to avoid deadlock.
First of all when a process fails for some reason or another, most current MPI runners are simply going to kill everything. Howard mentioned that you might be able to add some parameters to the runner to avoid this, but this is not the default. So in the case where everything is killed, the errors that will be returned are either going to be argument-related errors or some kind of internal error that you probably wouldn't be able to recover from.
If we were only looking at catching these types of errors, then we might be able to use some MPI-only calls to avoid a deadlock. For instance, after a collective operation, we could do an allreduce on either the errorcode or a flag indicating failure. If a failure did occur, then we would need some way of determining what error occurred and on what rank. Of course there could have been multiple errors that occurred on different ranks, and at that point it becomes difficult to determine which error should actually be returned to the user.
On the other hand, if we wanted to also support recovery from process-failure, then we would probably need to use the ULFM extensions. Being an extension, RSMPI would probably need a new user-specified feature or have to do something in a build.rs that checks for ULFM support. Otherwise this would break compatiblity with older MPI implementations and those that don't support ULFM yet.
I'm going to experiment with some of these methods and see what might work. Whether or not we attempt to implement this type of error handling, I think it's a good idea to have most calls return Result.