Failed to load the build package

[Enter steps to reproduce below:]

Setting> Install > Search build
Install

Atom Version: 1.0.0
System: Microsoft Windows 8.1 Single Language
Thrown From: build package, v0.38.0
Stack Trace
Failed to load the build package
At Cannot find module 'bluebird'

Error: Cannot find module 'bluebird'
  at Module._resolveFilename (module.js:328:15)
  at Function.Module._resolveFilename (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\module-cache.js:383:52)
  at Function.Module._load (module.js:270:25)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (C:\Users\user\.atom\packages\build\lib\build.js:4:15)
  at Module._compile (module.js:452:26)
  at Object.loadFile [as .js] (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\babel.js:162:21)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Package.module.exports.Package.requireMainModule (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:709:34)
  at C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:188:28
  at Package.module.exports.Package.measure (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:165:15)
  at Package.module.exports.Package.load (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:179:12)
  at PackageManager.module.exports.PackageManager.loadPackage (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package-manager.js:372:14)
  at PackageManager.module.exports.PackageManager.activatePackage (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package-manager.js:451:30)
  at C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\node_modules\settings-view\lib\package-manager.js:362:29
  at exit (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\node_modules\settings-view\lib\package-manager.js:53:16)
  at triggerExitCallback (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\buffered-process.js:213:47)
  at ChildProcess.<anonymous> (C:\Users\user\AppData\Local\atom\app-1.0.0\resources\app.asar\src\buffered-process.js:235:18)
  at emitTwo (events.js:87:13)
  at ChildProcess.emit (events.js:169:7)
  at Process.ChildProcess._handle.onexit (child_process.js:1057:12)

Commands
 22x -6:49.5.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -6:39.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-light-ui",
      "base16-tomorrow-light-theme"
    ]
  }
}

Installed Packages
# User
build, v0.38.0
terminal-panel, v1.14.1

# Dev
No dev packages

Weird. Bluebird is specified as a dependency and should be installed by apm when the package is installed. Could you try to
apm uninstall build
apm install build

Closing this out. Please come back if the issue persists.

Don't know it this is the right place to post this but the atom error tool points here. I already re-installed the build package, error still persists.
[Enter steps to reproduce below:]

Open a folder in Atom from the context menu
...

Atom Version: 1.0.7
System: Microsoft Windows 10 Pro
Thrown From: build package, v0.44.0
Stack Trace
Failed to load the build package
At Cannot find module 'lodash'

Error: Cannot find module 'lodash'
    at Module._resolveFilename (module.js:328:15)
    at Function.Module._resolveFilename (C:\Users\user\AppData\Local\atom\app-1.0.7\resources\app.asar\src\module-cache.js:383:52)
    at Function.Module._load (module.js:270:25)
    at Module.require (module.js:357:17)
    at require (module.js:376:17)
    at Object.<anonymous> (C:\Users\user\.atom\packages\atom-build\lib\build.js:7:9)
    at Module._compile (module.js:452:26)
    at Object.loadFile [as .js] (C:\Users\user\AppData\Local\atom\app-1.0.7\resources\app.asar\src\babel.js:167:19)
    at Module.load (module.js:347:32)
    at Function.Module._load (module.js:302:12)

Commands

Config
{
  "core": {
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ],
    "disabledPackages": [
      "omnisharp-atom"
    ]
  },
  "build": {}
}

Installed Packages
# User
atom-material-syntax, v0.2.3
atom-material-ui, v0.6.0
build, v0.44.0
language-lua, v0.9.4
language-pascal, v0.7.0
language-textile, v0.2.0
line-ending-converter, v1.3.2
linter, v1.4.3
linter-lua, v1.0.0
wordcount, v2.3.0

# Dev
No dev packages

Can you update to the latest version and try again?

Same with the latest version. I downloaded the zip from github, extracted into the .atom/packages folder and changed the name to atom-build. If I shall re-install in another way please tell me.

Hmm. You should definitely use the built-in package manager. The latest version doesn't use bluebird at all. Also, it will automatically install all the dependencies- which is probably what you missed

The latest version I get though the build-in package manager is 0.44.0, that is also the version that caused the error I posted. Also, it complains about lodash not about bluebird.

Yea.. When you unzip the package it doesn't install the dependencies. You would have to run 'apm install' or re-install via the package manager. I'd recommend the latter.

I did re-install via the package manager prior to posting the report. The
error came from a fresh install of 0.44.0.
On Thu, Aug 27, 2015, 15:18 Alexander Olsson<EMAIL_ADDRESS>wrote:

Yea.. When you unzip the package it doesn't install the dependencies. You
would have to run 'apm install' or re-install via the package manager. I'd
recommend the latter.
—
Reply to this email directly or view it on GitHub
https://github.com/noseglid/atom-build/issues/110#issuecomment-135424476
.

Then you should probably report the error over at atom/apm. The logic for installing dependencies is not part of a package.

Starting Atom
Error message on the top right corner

Atom Version: 1.2.2
System: Ubuntu 14.04.3
Thrown From: build package, v0.49.1
Stack Trace
Failed to load the build package
At Cannot find module 'XRegExp'

Error: Cannot find module 'XRegExp'
    at Module._resolveFilename (module.js:336:15)
    at Function.Module._resolveFilename (/opt/atom/resources/app.asar/src/module-cache.js:383:52)
    at Function.Module._load (module.js:286:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/dobosgy/.atom/packages/build/lib/error-matcher.js:4:24)
    at Module._compile (module.js:434:26)
    at Object.defineProperty.value [as .js] (/opt/atom/resources/app.asar/src/compile-cache.js:190:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)

Commands

Config
{
  "core": {
    "followSymlinks": true,
    "disabledPackages": [
      "exception-reporting",
      "feedback",
      "git-diff",
      "language-c",
      "language-gfm",
      "language-git",
      "language-go",
      "language-java",
      "language-make",
      "language-objective-c",
      "language-perl",
      "language-ruby",
      "language-ruby-on-rails",
      "language-toml",
      "language-yaml",
      "open-on-github",
      "run-command",
      "remote-edit"
    ],
    "themes": [
      "one-light-ui",
      "own-fizzy"
    ],
    "fileEncoding": "iso88592"
  },
  "build": {}
}

Installed Packages
# User
build, v0.49.1
color-picker, v2.0.13
file-types, v0.5.1
highlight-selected, v0.11.1
less-autocompile, v1.0.0
minimap, v4.16.1
minimap-highlight-selected, v4.3.1
minimap-selection, v4.3.1
own-fizzy, v0.15.0
project-manager, v2.6.5
remote-sync, v3.5.0
tablr, v0.7.0
tool-bar, v0.1.9
tool-bar-main, v0.0.8

# Dev
No dev packages

For me the same error as @dobosgy above. Running Ubuntu 15.10. I did try
$ sudo npm install xregexp
<EMAIL_ADDRESS>node_modules/xregexp
$ sudo apm install xregexp
Installing xregexp to /home/charlie/.atom/packages ✗
Request for package information failed: Not Found

But the error didn't disappear. I did restart Atom.

This was a new regression. Fixed in v0.49.2.

This seems to happen again with atom 1.6.0 and 0.57.0.
Cannot find module 'tree-kill'
Hide Stack Trace
Error: Cannot find module 'tree-kill'
at Module._resolveFilename (module.js:336:15)
at Function.Module._resolveFilename (/Applications/Atom.app/Contents/Resources/app.asar/src/module-cache.js:383:52)
at Function.Module._load (module.js:286:25)
at Module.require (module.js:365:17)
at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
at Object. (/Users/aaronisotton/.atom/packages/build/lib/build.js:4:55)
at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
at Package.module.exports.Package.requireMainModule (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:720:27)
at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:116:28
at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
at Package.module.exports.Package.load (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:106:12)
at PackageManager.module.exports.PackageManager.loadPackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:445:14)
at PackageManager.module.exports.PackageManager.loadPackages (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:395:14)
at AtomEnvironment.module.exports.AtomEnvironment.startEditorWindow (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:684:21)
at module.exports (/Applications/Atom.app/Contents/Resources/app.asar/src/initialize-application-window.js:28:10)
at setupWindow (file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.js:86:5)
at window.onload (file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.js:41:9)

Restarting Atom should work

Or re-installing atom.

I'm being redirected to this issue, I just installed Atom on OS X 10.11.5, I'm being referenced to this issue. The editor seems to be working properly but I keep getting a warning. Here's the full trace
Cannot read property 'prototype' of undefined
Hide Stack Trace
TypeError: Cannot read property 'prototype' of undefined
    at __extends (<anonymous>:1:1)
    at <anonymous>:6:3
    at Object.<anonymous> (<anonymous>:6:3)
    at Object.<anonymous> (<anonymous>:1:1)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (<anonymous>:9:13)
    at Object.<anonymous> (<anonymous>:1:1)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Package.module.exports.Package.requireMainModule (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:715:27)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:117:28
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
    at Package.module.exports.Package.load (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:106:12)
    at PackageManager.module.exports.PackageManager.loadPackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:457:14)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:402:19
    at Config.module.exports.Config.transact (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:312:16)
    at PackageManager.module.exports.PackageManager.loadPackages (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:397:19)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:743:28


The DockerHub publish action bump demo race condition

If additional commits are pushed while the publish action is running and already done a checkout, but hasn't reached the push step then the bump demo version will fail because a pull must be done first.  This can happen if you update the README while a CD workflow is running.
https://github.com/JeffersonLab/container-workflows/blob/2000de75007f901053c4aedf822986378f047d56/.github/workflows/docker-publish.yml
Example log:
Run git config --local user.name "github-actions[bot]"
From https://github.com/JeffersonLab/cnm
 * branch            main       -> FETCH_HEAD
   41de3a5..40f2a7d  main       -> origin/main
Already on 'main'
Your branch is behind 'origin/main' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
[main b567a3f] Bump demo compose version to 2.8.2
 1 file changed, 1 insertion(+), 1 deletion(-)
To https://github.com/JeffersonLab/cnm
 ! [rejected]        main -> main (non-fast-forward)
error: failed to push some refs to 'https://github.com/JeffersonLab/cnm'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. If you want to integrate the remote changes,
hint: use 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Will be a race condition even if we add a pull.    Might need to just avoid doing commits during a release/deployment, which seems reasonable.    Also consider using "latest" tag in DockerHub instead of having to update the version reference each release.  The latest tag isn't without it's own issues , but may make sense in this case.

Fixed in v2.0.0


Cfg loops did not have an alternate node

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls


Autoscroll Doesn't Seem to work

Great library.  I found it very quick and generally easy to use.
One thing that doesn't seem to work, though is the AutoScroll property of the control.  If you make the control anchored inside a form, and then you change the size of the form, its easy to lose your nodes by shrinking the control.  It seems like there's no good way to navigate the control "canvas".  Normally, this would be handled by the autoscroll property.  Unless, I'm maybe using it wrong.

If I'm understand correctly the situation, you probably should put the node editor control inside a panel, and then set that panel property AutoScroll to true. The Panel could be anchored or docked to the form.

My problem is with the nodes inside the nodecontrol itself.  Just create a node inside the nodecontrol, then slide it so it goes outside of the main nodecontrol.  I would expect scrollbars to show up with Autoscroll on the nodecontrol set to true.  As it is, I can slide a node outside of the nodecontrol and there is no way to get it back.

@komorra  thx for this project, same problem with scroll feature

Hello everyone,
i'm a newby on GitHub and only a hobbiest programmer.
@komorra  Awesome Project!!
May i'm allowed to generate a new Branch?
I would like to create a Universal Node Editor IDE for text-based languages (like PHP & HTML).
Where you can import any Project & it generates there nodes itself.
Currently i managed to add some Features:

Zoom in & out - Limited to 0.2f and 3.0f (can be changed in Source Code)
Move Projekt-Plane with Nodes (can be moved outside Viewport) - Limited to int size

ToDo:

Debugging - weird moving Plane behavior while pageScale/Zoom != 1.0f
Improvment: Draw Only Nodes & Connections those are in Viewport
Adding Scrolling with MouseWheel (+horizontal Scroll with ShiftKey pressed)
Adding AutoScroll as Thread named
To learn how creating my own Nodes does work o.O
Removing default grid Image at top left corner xD

Best regards
DevelopingJohnny ;D

Hi @DevelopingJohnny , thanks, I would prefer for you to fork this project instead of creating branch. Some of features, that you've mentioned I'm working currently on (but not so fast, because of having very little time for it).
Currently there are two branches master and v1.1, so upcoming features will be some time on v1.1.
If I undersand you correctly, are you planing to make some node based programming approach for writing in PHP/HTML without coding? It sounds interesting!

Hey @komorra, thanks your quick response.
Sure i'll do fork this project, have to reseach it. xD

If I undersand you correctly, are you planing to make some node based programming approach for writing in PHP/HTML without coding? It sounds interesting!
Yeah you understood it correctly. It should be a combination with nodes & Coding ^^, to keep an overview of you Website/Project.

Hello everyone,
i'm a newby on GitHub and only a hobbiest programmer.
@komorra Awesome Project!! May i'm allowed to generate a new Branch?
I would like to create a Universal Node Editor IDE for text-based languages (like PHP & HTML). Where you can import any Project & it generates there nodes itself.
Currently i managed to add some Features:

Zoom in & out - Limited to 0.2f and 3.0f (can be changed in Source Code)
Move Projekt-Plane with Nodes (can be moved outside Viewport) - Limited to int size
Adding Scrolling with MouseWheel (+horizontal Scroll with ShiftKey pressed)

ToDo:

Debugging - weird moving Plane behavior while pageScale/Zoom != 1.0f Solved
Improvment: Draw Only Nodes & Connections those are in Viewport
Adding AutoScroll as Thread named
To learn how creating my own Nodes does work o.O
Removing default grid Image at top left corner xD

Best regards DevelopingJohnny ;D

hi, is it possible to see how you did the zooming feature


Invalid byte sequence in US-ASCII

--crop detect and detect-crop tool failing with error Invalid byte sequence in US-ASCII

@dorgan OK, I'm back from dinner. :)
Thanks for filing this! Can you add more information about the problem media file? Like results from --scan or output from MediaInfo? Also, does this happen with every media file or only one?
Also, which version of ffmpeg are you using?

output from detect-crop --scan is:
`+ title 1:

stream: shrek.mkv
duration: 01:30:08
size: 1920x1080, pixel aspect: 1/1, display aspect: 1.78, 23.976 fps
chapters:

1: cells 0->0, 0 blocks, duration 00:04:59
2: cells 0->0, 0 blocks, duration 00:06:46
3: cells 0->0, 0 blocks, duration 00:04:16
4: cells 0->0, 0 blocks, duration 00:04:13
5: cells 0->0, 0 blocks, duration 00:06:08
6: cells 0->0, 0 blocks, duration 00:05:21
7: cells 0->0, 0 blocks, duration 00:03:32
8: cells 0->0, 0 blocks, duration 00:05:11
9: cells 0->0, 0 blocks, duration 00:04:37
10: cells 0->0, 0 blocks, duration 00:04:15
11: cells 0->0, 0 blocks, duration 00:06:11
12: cells 0->0, 0 blocks, duration 00:05:27
13: cells 0->0, 0 blocks, duration 00:04:39
14: cells 0->0, 0 blocks, duration 00:03:42
15: cells 0->0, 0 blocks, duration 00:02:18
16: cells 0->0, 0 blocks, duration 00:03:19
17: cells 0->0, 0 blocks, duration 00:02:42
18: cells 0->0, 0 blocks, duration 00:03:19
19: cells 0->0, 0 blocks, duration 00:02:09
20: cells 0->0, 0 blocks, duration 00:07:04

audio tracks:

1,  (AC3) (5.1 ch) (iso639-2: rus), 48000Hz, 640000bps
2,  (DTS) (5.1 ch) (iso639-2: rus), 48000Hz, 768000bps
3,  (DTS-HD MA) (5.1 ch) (iso639-2: rus)
4,  (DTS-HD MA) (5.1 ch) (iso639-2: rus)
5,  (DTS-HD MA) (5.1 ch) (iso639-2: rus)
6,  (DTS-HD MA) (5.1 ch) (iso639-2: rus)
7,  (DTS-HD MA) (5.1 ch) (iso639-2: rus)
8,  (DTS-HD MA) (5.1 ch) (iso639-2: rus)
9, English (DTS-HD MA) (5.1 ch) (iso639-2: eng)

subtitle tracks:

1, Russian (iso639-2: rus) (Text)(SSA)
2, Russian (iso639-2: rus) (Text)(SSA)
3, Russian (iso639-2: rus) (Text)(SSA)
4, Russian (iso639-2: rus) (Text)(SSA)
5, Russian (iso639-2: rus) (Text)(SSA)
6, Russian (iso639-2: rus) (Text)(SSA)
7, English (iso639-2: eng) (Text)(SSA)
8, Russian (iso639-2: rus) (Text)(SSA)`

well know i know the issue.  Apparently it doesnt like the russian subtitles...

@dorgan Maybe it's not the language but the SSA/ASS format?

@dorgan So, did you resolve this yourself?

I resolved it by deleting it...

@dorgan That works! :) OK, I'll close this issue then.


GTT-1018 Enabled access logs in api gateway

Description
Enabled access logs in API Gateway and bumped up all CDK packages from v1.74.0 to v1.87.1. I tried bumping up the cdk packages to the latest version but our CloudFront distribution broke due to a bucket policy change in version 1.90.1. I have reported the bug on the CDK GitHub repo.
Testing
Deployed to my personal environment and verified that the Access Logs are showing up correctly in CloudWatch Logs.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do we need the package-lock.json file to be included?

Yes, absolutely package-lock.json is what makes our builds predictable and stable by freezing specific versions on our dependency tree.


[Docs][Next.js]Fix step for deploying Next.js items to Sitecore [479849]

Description / Motivation

Testing Details

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)
[x] Documentation update (non-breaking change; modified files are limited to the /docs directory)

@ambrauer I've detailed the steps as you described and added hash links for each step. I think this gives us what we need.
I've had to make some changes to the route handler and the link component that renders markdown links so that the hash (id of the heading I link to) gets pushed to history and used to scroll down to the heading. Let me know if I need to fix anything else. Otherwise, if approved, I will cherry-pick this over the weekend to the release.


allow string.c to be disabled when it conflicts with other libs

There are other crates that are based on C libs and define various functions like strchr.  This PR adds a feature that when enabled does not compile string.c and expects some external source to provide the functions within.
I ran into this issue with the current (unreleased) esp-wifi that when combined with littlefs2 fails to link because strchr is multiply defined.
When combining crates that do this one can disable string.c and if needed add this to fill in any functions that are still missing:
tinyrlibc = { version = "0.4.0", features = ["strspn", "strcspn", "strlen"] }

Having features that disable code is somewhat counter-intuitive for me.  But I’m not sure if a positive feature that enables strings.c would really be better here.  Do you have a preference?

I have no preference - as long as there is control as to where these functions come from.

From the Cargo book

A consequence of this is that features should be additive. That is, enabling a feature should not disable functionality, and it should usually be safe to enable any combination of features. A feature should not introduce a SemVer-incompatible change.

Another solution would be to expect the user to always bring their own implementation. This is only matters for embedded so it's not shocking.

Another solution would be to expect the user to always bring their own implementation. This is only matters for embedded so it's not shocking.

Thats fine too.  One can always use
tinyrlibc = { version = "0.4.0", features = ["strspn", "strcspn", "strlen"] }

to bridge the gap.

I don’t see strspn and strcspn in tinyrlibc v0.4.0.  Am I missing something?

Your correct :-(

That works for me.

I'll open an issue on tinyrlibc, honestly being able to get rid of theses implementation seems good (and using a rust implementation instead too).

I would still keep a feature flag that brings in tinyrlibc as a dependency to still have the two functions.


Document string encoding

Following on from #47, and based on our eventual Python 2 vs. 3 vs. C++ design decisions, we should add a section to the documentation detailing how string encoding is handled in OAIO.

Closing due to low importance, as well as also being docced in a DR : https://github.com/OpenAssetIO/OpenAssetIO/blob/main/doc/decisions/DR005-String-encoding.md


update repeatabilityFirstSent to be DateTimeOffset

update repeatabilityFirstSent to be DateTimeOffset in request parameter
convert it to string when sending to api

Can you update readme.md file here while you are fixing the conflicts?

repeatabilityFirstSent: The value should be the date and time at which the request was first created, expressed using the IMF-fixdate form of HTTP-date. Example: Sun, 06 Nov 1994 08:49:37 GMT.
RepeatabilityFirstSent = DateTimeOffset.Now.ToString("R"),

Can you update readme.md file here while you are fixing the conflicts?

repeatabilityFirstSent: The value should be the date and time at which the request was first created, expressed using the IMF-fixdate form of HTTP-date. Example: Sun, 06 Nov 1994 08:49:37 GMT.
RepeatabilityFirstSent = DateTimeOffset.Now.ToString("R"),

update! ty!


[csolution/cbuild] all contexts present in cbuild-idx.yml even if a particular context was selected

Describe the bug
This is closely related to https://github.com/Open-CMSIS-Pack/devtools/issues/1210
cbuild/csolution were run for a particular context (here FRDM-K32L3A6.Debug+FRDM-K32L3A6):
the following is the content of the cbuild-idx.yml and all contexts are referenced; not just the one selected.
build-idx:
  generated-by: csolution version 2.2.1
  csolution: ../workspace/workspace/Blinky_FRDM-K32L3A6/Blinky.csolution.yml
  cprojects:
    - cproject: ../workspace/workspace/Blinky_FRDM-K32L3A6/FRDM-K32L3A6.cproject.yml
  cbuilds:
    - cbuild: FRDM-K32L3A6.Debug+FRDM-K32L3A6.cbuild.yml
      project: FRDM-K32L3A6
      configuration: .Debug+FRDM-K32L3A6
    - cbuild: FRDM-K32L3A6.Release+FRDM-K32L3A6.cbuild.yml
      project: FRDM-K32L3A6
      configuration: .Release+FRDM-K32L3A6

from previous unrelated builds, other context's artefacts are also present in the output folder and so, it is impossible to distinguish from the listing in the index file what artefacts are the output of the job we just ran and which ones are the result of previous jobs
Expected behavior
Only list the data related to the context selected and job performed
Environment (please complete the following information):
cbuild 2.2

For the sake of IDE integrations the concept of a "context set" was introduced.
When you invoke cbuild with -S / --context-set as well as selecting the contexts to be built using c / --context in addition to the *.cbuild-idx.yml the file *.cbuild-set.yml is generated. It can be (re-)used in subsequent tool invocations for the same selection of contexts.
As the *.cbuild-idx.yml file is always listing all contexts of a *.csolution.yml the *.cbuild-set.yml lists the contexts being updated during the last cbuild ... -S / csolution ... -S runs.
Does that solve the above problem or is it required to inspect timestamp of files?

Just to clarify. *.cbuild-idx.yml contains a list of paths to <context>.cbuild.yml for all the contexts defined in the csolution projects no matter what --context option was used and so, if this option is used, only corresponding <context>.cbuild.yml is created and therefore, the index file may reference files which do not exist. Moreover, if I run cbuild multiple times with different --context options, I can only know which context was build by looking at the timestamp of the <context>.cbuild.yml files and consider the ones which were created or modifield after I ran the cbuild command. *.cbuild-set.yml has indeed only just been introduced and so, is not an option for older versions on cbuild 2.x which I need to support.

This is not a bug, it is intended behaviour: https://github.com/Open-CMSIS-Pack/devtools/issues/1125

Thank you @brondani for pointing me to this decision record. I had missed that completely. Could you confirm that my understanding of how context specific build artefacts should be retrieved is correct https://github.com/Open-CMSIS-Pack/devtools/issues/1426#issuecomment-2051395452 ?
Furthermore, I believe we should change the wording in the documentation https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/YML-CBuild-Format.md#file-structure-of-cbuild-idxyml to reflect that behaviour

cbuilds:  List of *.cbuild.yml output files that are generated for this application.

should probably become something along the lines of

cbuilds:  List of *.cbuild.yml files corresponding to the different contexts defined in the csolution project (Note: file may not be generated if the corresponding context is not selected)

Could you confirm that my understanding of how context specific build artefacts should be retrieved is correct #1426 (comment) ?

In the same way build artifacts are referenced in cbuild.yml but don't exist until a successful build is performed, it cannot be assumed a referenced cbuild.yml file exist until a successful convert call is performed. In addition it may exist but be incomplete since it is also used for error status reporting https://github.com/Open-CMSIS-Pack/devtools/issues/1385 and note that cbuild-idx.yml is also used for compatible layers reporting https://github.com/Open-CMSIS-Pack/devtools/issues/1379. I would say the information you can get from these files depends on the workflow you are performing.

The generation of *.cbuild-idx.yml with all contexts is currently needed for ensuring the correct generation of build files (CMakeLists).
If one or more selected contexts depend on other contexts that are not selected at the same time, a partial *.cbuild-idx.yml would miss such dependencies leading to a fail.
I agree with Reinhard here:

I would recommend that *.cbuild-idx.yml only contains the files that are in the context-set.

But we should also improve or clarify the build approach without context-set which could be also relevant for the generation of cbuild-set.yml.

I believe all you need is an error message, i.e.
error: context <project>.<build-type>+<target-type> not included in current build, output is required for context <project>.<build-type>+<target-type>
This would tell the user that there is a dependency between the projects and it is required to build the first context also.

this is done


(click) is not called on the IOS devices

It seems that the ngAfterViewInit is called before the rect is rendered.
Similar issue:
https://stackoverflow.com/questions/61913054/ngafterviewinit-called-too-early

Note:
It was happening because of the event.path property which is not available on the Safari.


Add DCPower metadata and generated files and register DCPower service

Justification
Adds the DCPower metadata and the generated proto file and service handlers.
Link to task : https://ni.visualstudio.com/DevCentral/_workitems/edit/1367880
Register DCPower service.
Link to task : https://ni.visualstudio.com/DevCentral/_workitems/edit/1367885
Implementation

Added nidcpower.h , nidcpowerObsolete.h , nidcpower.lib
Made some changes to config.py
Cleaned up function.py
Registered DCPower service in core_server.cpp
Added DCPower in CMakeLists.txt
Added service.custom file for DCPower

Testing
Manually inspected the generated files

This Pull Request is a replica of PR 161.
Since I need to merge PR 161 in this repo, I have created a replicated PR here.
PR 161 was approved by all owners.


Move to use batch operations to delete files from S3

### Tasks
- [ ] https://github.com/neondatabase/neon/pull/4461
- [ ] Batch DeleteOp's from UploadQueue

Working on this - wip branch that aggregates deletions into a pageserver-wide queue that can generate nice efficient DeleteObjects is here
https://github.com/jcsp/neon/tree/jcsp/deletion-queue

Complete with merge of deletion queue


Disable two way audio from Home Assistant camera stream

Is there a way to disable audio completely from a camera stream? I'm having an issue with my Amcrest AD110 door bell where the chime gets disabled (and also the talk back function on the amcrest app) when go2rtc is streaming its video. It basically locks the mic channel so the doorbell itself doesn't even ring. This used to work flawlessly using WebRTC, but I'm not sure how to change this in go2rtc for it to not lock out the mic audio.

Just add #backchannel=0 to the stream in go2rtc config

Need to make this setting optional somehow

Not sure where to put this in the config since there are no streams there. I'm having it automatically pick up the generic camera streams I've put into Home Assistant.

That worked! Thank you

Just a thought but should the default be backchannel=1 rather than always enabled?

@mattbrad2 were you actually able to get 2-way audio working with your AD110 doorbell through go2rtc? I see that people have been getting it to work with their AD410's, but I haven't seen anyone else get it working on an AD110.
If you got it working, I'd love some pointers!

Sorry, no. Everything else works flawlessly though.
Matthew Bradley
President, Bradley Electronics
t:<PHONE_NUMBER> x2001 | a: 26 E Midland Ave, Winder, GA 30680
e: @.*** | w: www.bradleyelectronics.com

From: Anil Ozyalcin @.>
Sent: Monday, December 26, 2022 7:45:38 PM
To: AlexxIT/go2rtc @.>
Cc: Matthew Bradley @.>; Mention @.>
Subject: Re: [AlexxIT/go2rtc] Disable two way audio from Home Assistant camera stream (Issue #95)
@mattbrad2https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmattbrad2&data=05|01|matthewb%40bradleyelectronics.com|dbe47746333b4f96701f08dae7a3ac5b|0d0b558ae6ce4a688e4b4c196374b0c4|1|0|638076987427929748|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=RfDY%2B3rYduphz83T03Xskly3OKRbLmYxYK71zPGSiu0%3D&reserved=0 were you actually able to get 2-way audio working with your AD110 doorbell through go2rtc? I see that people have been getting it to work with their AD410's, but I haven't seen anyone else get it working on an AD110.
If you got it working, I'd love some pointers!
—
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAlexxIT%2Fgo2rtc%2Fissues%2F95%23issuecomment-1365524750&data=05|01|matthewb%40bradleyelectronics.com|dbe47746333b4f96701f08dae7a3ac5b|0d0b558ae6ce4a688e4b4c196374b0c4|1|0|638076987427929748|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=5R29g4C7ii%2BI4BM7UhR33yRUhH03B0xXQ0usrZwmf8E%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASHJAOLLS5JBNVQWYW3CGGLWPI33FANCNFSM6AAAAAARXOMMRE&data=05|01|matthewb%40bradleyelectronics.com|dbe47746333b4f96701f08dae7a3ac5b|0d0b558ae6ce4a688e4b4c196374b0c4|1|0|638076987427929748|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=3EIJ7CkpCD2jO9nI0UNJ%2By3EflmC5QbhOeCcUddy9uI%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>


Mathematical operations for DataFrames

Common math operations that work along dimensions of Arrays would be useful for DataFrames (and DataArrays as discussed in issue #325).  The use case I envision is there are many numerical columns and some categorical columns, and say we want to compute the average of the numerical columns.  It would be great to be able to say df["mean_col"] = mean(df[:,numeric_colinds], 2, skipna=true) without having to convert to a DataMatrix first.  If someone tries to take the mean of something that doesn't make sense an error can be thrown.
If people think this is useful I'm willing to take a stab at it.  I prefer the mean(df, dim, skipna) interface to rowmeans and colmeans to stay consistent with the rest of Julia but if others prefer the R names I can go along with that.
Thanks.

Closing as ensuing discussions have also landed on 'no' to treating DataFrames this way.


Support batching for output HDFS

Hi!
Are there any plans for supporting writing to HDFS with batching? We want to writing compressed files with size witch equal size of hdfs block.

Hey @deavil, yeah this should be quick to add. In the meantime you can currently define batches using a broker (with a single output):
output:
  broker:
    outputs:
      - hdfs:
          hosts:
            - localhost:9000
          directory: foo
          path: ${!count("files")}-${!timestamp_unix_nano()}.tar.gz
    batching:
      count: 1000
      processors:
        - archive:
            format: tar
        - compress:
            algorithm: gzip

Done https://github.com/Jeffail/benthos/commit/1b53ff957084f6fb457062c5f2963eac65dc6cc6


test: don't invoke docker-machine directly

Use machine helper for that.
Signed-off-by: Vincent Bernat<EMAIL_ADDRESS>

LGTM cheers

cc @ehazlett

LGTM


Bump grafana-plugin-sdk-go to v0.220.0

This is necessary as v0.217.0 includes a PDC bug.

@wbrowne you're correct, will merge this as is 😊


What about Symfony 4.0?

While playing with Symfony 4.0 and flex, I can't use this bundle cause of the Your requirements could not be resolved to an installable set of packages.. Are there already any future plans, idk if there are any compatibility issues?

Yes, it would be nice to know if you are planning to resolve the compatibility issues.
Thank you.

yes, this is on my plan, but I cannot promise a date (my hope is to have it done before the stable release). I don't have a lot of free time for open-source these days (personal life being busy)

+1

Is there any way others might be able to help with?

Any updates with this? Symfony 4 was just released.

@stof Maybe you can point us in the direction of what needs to be changed. Perhaps we can help with some of the work.

@martijnhartlief  there is PR #358. We have to wait for @stof to do his magic.

Another PR is the https://github.com/stof/StofDoctrineExtensionsBundle/pull/355 which do the same. @stof could you merge and release one of those?

The funny thing is, this bundle is on the documentation of Symfony 4. But its not working for Symfony 4.
https://symfony.com/doc/current/doctrine/common_extensions.html
@stof is it really one line composer.json change?


x/website:

What version of Go are you using (go version)?

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

What did you expect to see?
A windows X32 or A windows X64 Installer
What did you see instead?
Saw a windows amd installer
I don't own a windows Phone I Own a Windows Laptop

What did you expect to see?
A windows X32 or A windows X64 Installer

Both are there, you selected them in the screenshots:
amd64 is also known as x64 or x86_64 (see https://en.wikipedia.org/wiki/X86-64), and 386 is also known as x32 or x86 (see https://en.wikipedia.org/wiki/IA-32).

What did you see instead?
Saw a windows amd installer
I don't own a windows Phone I Own a Windows Laptop

You're probably thinking of arm64, which is not the same as amd64.

Closing per above.


Error when trying to use arrow keys for navigation

Expected behavior
I expect to be able to use the arrow keys (specifically left & right) to highlight a new "selected" date when the datepicker is open (like in the examples).
Actual behavior
I get an error when trying to use the arrow keys when the input field is in focus.
Steps to reproduce
Here is the code I am using which produces the error, along with a little gif of the error happening:
import React from 'react';
import DatePicker from 'react-datepicker';
import moment from 'moment';

const MyComponent = (props) => (
    <DatePicker
        className="calendar-input__datepicker js-test-calendar-input"
        dateFormat="MMM D, YYYY"
        onChange={props.onDateChange}
        selected={this.props.date ? moment(props.date) : null}
        placeholderText={props.placeholder}
        minDate={props.minDate}
        maxDate={props.maxDate}
    />
);

MyComponent.defaultProps = {
    date: null,
    minDate: null,
    maxDate: null,
};

export default MyComponent;

This is the line of source code from which the error originates.

Wondering if maybe I am just missing a prop or if it's a real bug? Any insight/ideas would be greatly appreciated by me and my team. For the time being, we have applied the disabledKeyboardNavigation prop, which gets around the issue, however now we lose keyboard navigation, which kinda sucks.

I'm experiencing the same error on keyboard navigation. If I remove minDate and maxDate, the error disappears and keyboard navigation starts working again. I feel like the two are probably related since @himynameisdave is also passing those props.


no name property on response?

am I missing something? no name property in the response

What do you expect exactly? You could get everything from geocoding google maps API

it was in the originalPrediction object for selectSuggest. I guess I expected it in the 1st suggestion argument as well.

If I can't get the info from the Google API, I don't know what to tell to you.


Test Issue

Test Issue. What is this!?

@KellyVance Try smelling it, sight is over-rated.

Testing profile image markup

I see your comment and I raise you a feedback

Test issue closed


[GH-586] Fix zone killfeed

Client PR https://github.com/lambdaclass/curse_of_mirra/pull/1764
Motivation
When the zone kills a player we are not sending any killfeed to the client
Closes #586
Summary of changes

Send killfeed when the zone kills a player

How to test it?
Play a match and get a player to die to the zone damage
Checklist

[ ] Tested the changes locally.
[ ] Reviewed the changes on GitHub, line by line.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

https://github.com/lambdaclass/mirra_backend/assets/20927859/f27c92b1-6883-4361-900a-887986c7a882
@agustinesco it seems we are killing player all the time (with the zone)


Sarah/pulumiup event day

Description
PulumiUP landing page updates for after the event (https://github.com/pulumi/pulumi-hugo/issues/3014)
Checklist:

[x] I have reviewed the style guide.
[x] If blogging, I have reviewed the blogging guide.
[x] I have manually confirmed that all new links work.
[x] I added aliases (i.e., redirects) for all filename changes.
[x] If making css changes, I rebuilt the bundle.

up to yall, but the size increase on this ad, really changes the vibe in the docs

Strange that the image is visibly larger in the file diff but dimensions are smaller.

Interesting, I didn't mean for it to be any larger. I can resize this, if helpful, but since it looks like the dimensions are already smaller not sure that it would work?

@lindsaymarolich let's leave the image as-is, I can enforce the size of the ad programmatically. Update incoming!


Is there a way to run this cmd line utility in a forced fashion for pipeline deployments?

Hi,
Is there a way to make the cmd utility not behave in a Dry Run mode by default? I want to add it as part of the CI/CD automation process but I wanted to know if there was an ability to force delete without a prompt for the Dry Run.

I figured there was a 0.3.0 version with this fix. Closing this out. Thank you!


add schedule peer info

Signed-off-by: allen.wq<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Add schedule peer info.
Ⅱ. Does this pull request fix one issue?

NONE.
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
NONE.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1358   +/-   ##
=======================================
  Coverage   51.59%   51.59%
=======================================
  Files         130      130
  Lines        8605     8605
=======================================
  Hits         4440     4440
  Misses       3797     3797
  Partials      368      368

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 88cb9fa...0dc8afb. Read the comment docs.


importing library fails. pydantic.errors.PydanticUserError: Field 'decimals' defined on a base class was overridden by a non-annotated attribute

tested on Py 3.8, 3.9 in docker containers:
python:3.8-slim
python:3.8-bullseye
python:3.9-alpine3.17
and later py versions.
#0 1.888 Traceback (most recent call last): #0 1.888   File "/main.py", line 1, in <module> #0 1.888     from zksync_sdk import ZkSyncLibrary #0 1.888   File "/usr/local/lib/python3.8/site-packages/zksync_sdk/__init__.py", line 1, in <module> #0 1.888     from .ethereum_provider import EthereumProvider #0 1.888   File "/usr/local/lib/python3.8/site-packages/zksync_sdk/ethereum_provider.py", line 6, in <module> #0 1.888     from zksync_sdk.types import Token #0 1.888   File "/usr/local/lib/python3.8/site-packages/zksync_sdk/types/__init__.py", line 3, in <module> #0 1.888     from .responses import * #0 1.888   File "/usr/local/lib/python3.8/site-packages/zksync_sdk/types/responses.py", line 26, in <module> #0 1.888     class NFT(Token): #0 1.888   File "/usr/local/lib/python3.8/site-packages/pydantic/_internal/_model_construction.py", line 98, in __new__ #0 1.888     private_attributes = inspect_namespace( #0 1.888   File "/usr/local/lib/python3.8/site-packages/pydantic/_internal/_model_construction.py", line 337, in inspect_namespace #0 1.888     raise PydanticUserError( #0 1.888 pydantic.errors.PydanticUserError: Field 'decimals' defined on a base class was overridden by a non-annotated attribute. All field definitions, including overrides, require a type annotation. #0 1.888 #0 1.888 For further information visit https://errors.pydantic.dev/2.1.1/u/model-field-overridden
docker-compose build fails with other error.

zksync_sdk/types/responses.py
class NFT(Token):
    creator_id: int
    content_hash: str
    creator_address: str
    serial_id: int
    decimals: int = 0


Comparision Filter PropertyIsLike

Feature Request
Is your feature request related to a problem? Please describe.
currently wildcard, singleChar and escape values are hard coded.
Describe the solution you'd like
option to pass wildcard, singleChar and escape values, while creating comparison filter PropertyIsLike

Good point. To do so, we would have to add these options to the typing for the propertyIsLike filter in the geostyler-style here and here (the *= is the equivalent of propertyIsLike). Then, the sld-parser could be adjusted to that.
Are you planning on providing a PR for this?

I have made changes to provide "PropertyIsLike" attributes. Please check the pull request https://github.com/geostyler/geostyler-style/pull/616.

I have to make changes to "geostyler-sld-parser" project to remove use the provided like attributes. After the pull request complete and released?

You can also develop based on your unmerged changes by using npm link. Please reference the open PR in the description, then.

Hey @rajsync do you think you will continue working on the PR in the geostyler-style? Otherwise we might could take care of it in the upcoming codesprint.


_get_alloc_size_checked behavior

during initialization, there's a call to "_get_alloc_size_checked(6, &alloc_size)", which is returning "true", but the value stored in alloc_size is 0. This is on Vector::resize() (line 277). The alloc size 0 is causing the function to return with ERR_OUT_OF_MEMORY.
Only happens on a release build (debug works), with a clang compiler.
Could this be the cause of the ios issue?

Could this be the cause of the ios issue?

The mentioned issue being: #4190.
It sounds like a potential culprit indeed, as it seems indeed to happen only when building binaries with a certain build environment. (One user reported having good binaries when building for iOS with OS EL CAPTION 10.11.4, IOS SDK 9.3).

I worked around by disabling the overflow stuff and using
nearest_power_of_2() on my build (I don't know which one is broken tho)
On 8 April 2016 at 02:43, Rémi Verschelde<EMAIL_ADDRESS>wrote:

Could this be the cause of the ios issue?
The mentioned issue being: #4190
https://github.com/godotengine/godot/issues/4190.
It sounds like a potential culprit indeed, as it seems indeed to happen
only when building binaries with a certain build environment. (One user
reported having good binaries when building for iOS with OS EL CAPTION
10.11.4, IOS SDK 9.3).
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/4262#issuecomment-207224855

@punto- hmm can you try to find out with which parameters nearest_power_of_2_templated gets called?
And what is sizeof(size_t) for IOS?

Should some more work be done on this nearest_power_of_2_templated for 2.2, or are we happy with the current situation?

I'm waiting for @punto- to answer the question here.

I guess we're happy with it... :)


Add type Instance to trait Backend

Fixes #2963
Much simpler than #3034, but still had to add the cfgs to the gl backend.
PR checklist:

[X] make succeeds (on *nix)
[ ] make reftests succeeds (panics on macOS, but same for master branch, didn't have enough time on the windows machine to test)
[X] tested examples with the following backends:

macOS: metal ✅ , vulkan (moltenvk) ✅ , gl 🔴 (panics)
windows: vulkan ✅ , dx12 ✅ , dx11 ✅ , gl ✅

[X] rustfmt run on changed code

To my understanding the chain starts with:
#[cfg(any(
    all(not(target_arch = "wasm32"), feature = "glutin"),
    target_arch = "wasm32",
    feature = "wgl"
))]
impl hal::Backend for Backend {
    #[cfg(any(
        all(not(target_arch = "wasm32"), feature = "glutin"),
        feature = "wgl"
    ))]
    type Instance = Instance;

    #[cfg(all(target_arch = "wasm32", not(feature = "wgl")))]
    type Instance = Surface;

    // ... snip ...
}

The hal::Backend trait previously didn't provide an Instance associated type, but now that it does we have to select one in the impl. There are 3 candidates to choose from:

Instance for the glutin feature
Instance for the wgl feature
Surface from window::web if target_arch = "wasm32"

This makes it difficult to produce a valid impl hal::Backend for Backend universally. The consumers using Backend require it to be constrained by hal::Backend, and since there is no cfg-less impl for that, I had to cfg all consumers of it.
I don't like it either 🙁. Perhaps if we could make one of the options for producing the Instance a default one? I am not sure, which one of those 3 it should be though. I am open to ideas.

Today, gfx-backend-gl has a single impl hal::Backend. We should just keep it, there is no need to have any cfg() on top.
We'll just have a few choices for the Instance inside, like what you wrote:
    #[cfg(any(
        all(not(target_arch = "wasm32"), feature = "glutin"),
        feature = "wgl"
    ))]
    type Instance = Instance;

    #[cfg(all(target_arch = "wasm32", not(feature = "wgl")))]
    type Instance = Surface;

There should be no other cfg() added.

Hmmm, I did as you asked, but I'm pretty sure the build will fail unless one of glutin/wgl features is passed, or the wasm32-unknown-unknown.
Do we want the user to explicitly pass the features/targets for the gl backend build? Hmm, that might actually make sense, especially given that wasm is not the usual build target and those features add more dependencies... Unfortunately the CI doesn't know it needs to add those build flags though: https://travis-ci.org/gfx-rs/gfx/jobs/594688627

@yanchith we can always have some struct Instance that we define when neither of the other configurations are enabled (and we impl hal::Instance for Instance).

Damn, I should have figured that out myself 😄 On it!

bors r+


[Virtual DOM] Investigate lambda set generalization when ambient function is not generalized

https://roc.zulipchat.com/#narrow/stream/231635-compiler-development/topic/casual.20conversation/near/317764158
is main broken? I'm hitting this
     Running `target/debug/roc check examples/virtual-dom-wip/example-client.roc`
thread '<unnamed>' panicked at 'assertion failed: `(left != right)`
  left: `12479`,
 right: `12479`: lambda set cloned but its ambient function wasn't?', crates/compiler/solve/src/solve.rs:4178:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Hm, seems to work on main now.
0cf9ba647c9d26c1296ce705ac7609fc775b59ef is the last time this was busted. So I suspect https://github.com/roc-lang/roc/pull/4805 moved something around here.
@brian-carroll if you have a chance could you please try to minimize the virtual DOM program from 0cf9ba647c9d26c1296ce705ac7609fc775b59ef to reproduce this bug? It's only present in debug builds. I think if we can find a minimal example it will also cover the other lambda set bug you saw in the PR.

https://github.com/roc-lang/roc/pull/4805#discussion_r1057275424 also needs a minimal example. It manifests itself as an empty lambda set in mono but I suspect the underlying causes are the same.

@ayazhafiz yep, I should be able to take a look in the next few days.

This is as far as I was able to take it! Anything I change seems to get rid of the assertion.
interface Html.Internal
    exposes [
        Html,
        initServerApp,
        initClientApp,
    ]
    imports []

Action state : [Action state]

Html state : [
    Element (state -> Action state) (Html state),
]

RenderedHtml : [
    RenderedNone,
]

translateStatic : Html state -> Html *

initServerApp : {} -> Html []
initServerApp = \{} ->
    translateStatic (Element [] [])

initClientApp : {} -> { thing : RenderedHtml }
initClientApp = \{} ->
    indexNodes { thing: RenderedNone } (Element [] [])

indexNodes : { thing : RenderedHtml }, Html state -> { thing : RenderedHtml }
indexNodes = \{ thing }, unrendered ->
    List.walk [] { thing } indexNodes

Here's the branch I used, in case it's useful for some reason https://github.com/roc-lang/roc/tree/virtual-dom-bug-repro

Relevant branch: virtual-dom-annotations
Pop ca364a19967210cfcf3f46c203c18fb293e57fdf for the relevant bit


Create CI test (integration test) that loads the extension and confirms it works

What's interesting is the fact that the even if tests pass, extension loading could fail (e.g. missing packages).

"Extensions loosing"?

Fixed with https://github.com/Microsoft/vscode-python/pull/1366


Pen width adjustment not restarting at current value after changing Pen

https://github.com/pubpub-zz/ppInk/issues/75#issuecomment-851178597

The first time I've coded that way and I wonder What is the best solution between the two options : like currently coded, you can recover the width before selecting the new pen. in another hand, It can be a little confiousing to not restart fro the current size. Can you open a new issue about this specific point opening the question to get other opinions.

For me, it's really confusing because I use the arrow and with it I cannot see how wide my pen is or which my last width was before swaping to another pen color (because when I swap from a pen to another one, the pen width restarts from the preset value (that's great). I think if it restarts when using the mouse wheel or hotkeys starting the pen width from its preset value, it will be more intuitive. Even so, I'm willing to open an issue about this topic. It would be interesting to get other opinions.

I seen what you mean : will put in the stack 👍
Originally posted by @pubpub-zz in https://github.com/pubpub-zz/ppInk/issues/75#issuecomment-851266162

@chrisj0192
A beta verVersion for evaluation includes fixes for #107 #106 #102:
ppInk64_01a.zip

Hello @pubpub-zz I'm testing your beta version in different cases, I'll post my observations about the multiple selector, pen width, load/save shortcuts and snapshot in a few hours.

Hello @pubpub-zz I was testing your beta version (ppInk64_01a.zip) in different cases and I can say that everything is perfect!
I only have one observation that you might want to consider. here you are my results:
Pen width test results:

Stroke test with shortcuts (Perfect)

Stroke test with the mouse wheel (Perfect)

Shape test with the mouse wheel (Perfect)
This is the video if you want to see it
https://user-images.githubusercontent.com/20199672/120950796-1f62c100-c70d-11eb-8448-5e7732e4e40f.mp4

Shape test with shape shortcuts and (+/-) shorcuts (it's missing)
In my case, when pressing Alt + W (to draw rectangles) and release W key holding down alt and then pressing S to draw ellipses, in this case those combinations work perfectly, but it's missing with pen width +/-.
Honestly I don't find it necessary for now. But You might want to consider implementing this requeriment, (If possible)
This is the video:
https://user-images.githubusercontent.com/20199672/120950901-546f1380-c70d-11eb-93c5-a79cb1d23f63.mp4

Tha's all about my tests.
Grateful for your work.

This additional observation is not related to the pen width but I've also noticed that when pressing alt + a custom key for the "toggle fading" option and releasing that custom key (it works) but finally when realeasing alt, and you makes strokes, toggle fading option keeps working.

see #111 for alt as temporary for Fading

Done! I think you can close this issue if you want. There's nothing more to report.
Thank you so much!


warn about impossible conditions

Feature Request
warn if conditions can not be satisfied
Out of curiosity I added the following condition to a process (e.g, waiting for postgres to be up) wihout setting up a healthprobe on postgresql.
    depends_on:
      postgresql:
        condition: process_healthy

so it turns out that my process with never start.
Use Case:
avoid mistake/help the user write his configuration
Proposed Change:
It might be useful to add a warning in that case (in F3, the process details) or instead of pending mark as "Impossible". In the logs at least.
Who Benefits From The Change(s)?
users

Hey @teto,
Thanks for all the improvement recommendations.
I will add a better warning to the next release.

Added in v1.0.0.


jotta-cli: 0.6.24251 -> 0.7.33634

Motivation for this change
Version bump.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 102008 run on x86_64-linux 1

1 package built:

jotta-cli