text:
Atom Beta isn't Side by Side on Windows

Expected
According to the beta info page Atom Beta should "run side-by-side with Atom stable". To me that reads like I should be able to have both the beta and stable installed (and even running) simultaneously on the same system (like with Chrome's stable & beta releases) and there should be separate links to run each build.
Actual
On Windows (7 x64), when I install the beta (1.1.0-beta1), it replaces the context menu "Open with Atom" shortcut and the start menu shortcuts with the beta so there is no apparent way to run stable without reinstalling.
Reinstalling stable works but it replaces all the shortcuts with links to the stable version so there is no way to run the beta without re-installing.

/cc @maxbrunsfeld @nathansobo

cc @raelyard

Ok, I had to stop work on this for the time being because of some PathLength issues on windows. We need to upgrade our build infrastructure to use npm 3, which does a better job of reducing path nesting. Until that time, I'm reopening this.

With the file associations and shell integration having the beta executable named something different - atombeta.exe for example - would also make this work better. Thoughts?

having the beta executable named something different - atombeta.exe for example - would also make this work better.

:+1: Ah, I didn't realize that. We already rename a bunch of stuff based on the channel (stable vs beta) in the build scripts, so this would just be one more.

Now the shell integration is coming out of the installer and into Atom settings we should make sure we use productName instead of atom.exe everywhere when we do that work in #5901

Included in the forthcoming shell integration options.

@damieng what's the process/timeline for getting both installed side by side on windows?

It's checked into master now on both atom/atom and atom/settings-view and should ship in Atom 1.10.

Reopening because I am not able to install Atom beta side by side with Atom stable on Windows 7. Installing beta removes the stable install. See below for a full list of what I did to try and install Atom 1.12.0-beta4 side by side with Atom 1.11.2.
I can test it out on Windows 10 later if required to see if stable and beta side by side works there.
Originally reported in: https://github.com/atom/atom/issues/13016 so not alone seeing this.
Windows 7 - Trying to install stable and beta side by side.

Uninstalled Atom 1.12-beta4 using Programs and Features found in the Control panel.
Removed the .atom folder from %USERPROFILE%.
Removed the atom folder from %localappdata%. It contained update.exe and .dead.
Expected: Atom to be uninstalled. Actual: Atom pin is still on the taskbar, clicking it gives an error that it might have been moved, renamed or deleted asking me to remove the pin.
Unpinned Atom from the taskbar by clicking Yes on the dialog.
Installed Atom 1.11.2 using AtomSetup.exe downloaded from atom.io.
Expected and Actual: Atom 1.11.2 starts after install, all settings lost.
Answered yes on the telemetry consent and unchecked the Show On Start option for the welcome guide.
Opened the settings-view using Ctrl+,
Navigated to the System tab and checked all three options.
Pinned Atom to the taskbar.
Closed Atom 1.11.2.
Checked %localappdata\atom it contains the app-1.11.2 folder.
Installed Atom 1.12.0-beta4 using AtomSetup.exe downloaded from atom.io.
Atom 1.12.0-beta4 starts.
Atom does not ask for telemetry consent or show the welcome guide.
Atom 1.11.2 is not in %localappdata%\atom. Only app-1.12.0-beta4.
Atom is still pinned to the taskbar and can open from there but it has the icon from stable.
Open with Atom context menu works, icon from beta and opens Atom 1.12.0-beta4.
Checked the Systems tab all three options are checked.

Atom Beta is expected to use the same config and settings as regular Atom right now so I wouldn't expect it to show the welcome guide or telemetry consent.
The real problem right now is that beta and non-beta on Windows share the same setup-id in Squirrel so one is considered an upgrade to the other.
One option for now would be to use the beta zip and unpack that somewhere.  That should allow you to run side-by-side.  If you want the beta to also use a separate config then you should be able to create an empty .atom folder in the folder about where you unpacked the beta, e.g.
c:\apps\.atom```

I see exactly the same happening as @Ben3eeE is describing. While installing any version of Atom (release, beta or dev) the previous Atom installation is being removed from %LOCALAPPDATA%\atom\.
Windows 7 EN 64-bits

Just installed Atom 1.18 beta (Windows 10, x64) and it has deleted the stable Atom version (1.17). If the issue is not going to be fixed, it would be good to remove the wrong message on the Atom beta page that the beta can be used side-by-side.

Heya Vlad, no it works in other platforms as far as the side-by-side install. It's just in Windows where this is currently an issue. side-by-side installs work fine in UNIX and UNIX-like environments. They're still working on it. In the meantime, refer to @damieng 's suggestion:

Atom Beta is expected to use the same config and settings as regular Atom right now so I wouldn't expect it to show the welcome guide or telemetry consent.
The real problem right now is that beta and non-beta on Windows share the same setup-id in Squirrel so one is considered an upgrade to the other.
One option for now would be to use the beta zip and unpack that somewhere. That should allow you to run side-by-side. If you want the beta to also use a separate config then you should be able to create an empty .atom folder in the folder about where you unpacked the beta, e.g.
c:\apps\atombeta
c:\apps\.atom

Hi all, I've written the first version of a tool designed to solve this problem: https://github.com/atom/avm
Here's how to get started:
npm install -g atom-version-manager

## Install the stable version:
avm switch stable

## Switch to the beta
avm switch beta

The initial run of these commands will take awhile as it downloads Atom and installs it, but from then on switching between the two will be very fast (i.e. 2-3 sec or so). Let me know if this helps!

At a minimum, it would be nice to mention something about this on the atom beta website.  It's really annoying to discover after the fact that it blew away my stable atom install.

Guys, tons of people are wasting a lot of time on this. Like everyone is suggesting please remove the side by side sales pitch from the site, at least on windows side. From the looks of this thread it hasn't worked in years. Its causing a lot of confusion and cursing.

authors: Ben3eeE MartyGentillon MethodGrab MorganMarshall benogle calebmeyer damieng jerone maxbrunsfeld mnquintana paulcbetts sonokamome vvs


text:
Indexing Project..0

Whenever I start the Fuzzy Finder, it gives a screen stating:  Indexing project..0.
How do I get it to work properly?

https://github.com/atom/fuzzy-finder/issues/205?

+1

Closing as a duplicate of #205 - feel free to subscribe there for updates.

source: gharchive/issue

repo: atom/fuzzy-finder

license: mit

license_type: permissive

license_source: bigquery


text:
ESP32: add support to CMake buildsystem used on esp-idf >= 4.x

These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

tested:

[x] network driver
[x] socket driver

source: gharchive/pull-request

repo: atomvm/AtomVM

license_source: github-api


text:
functional tests occasionally failing

Describe the bug
Seeing messages like this in logs

SEVERE|2023-07-05 19:04:35.767602|LocalSecondary (@alice🛠)|exception in llookup:Could not read value from box. Maybe your box is corrupted.

For example in this PR, test run 1 failed but test run 2 succeeded (but can still see the warnings about hive box maybe being corrupted even though the test run succeeded).
Suspect there is a race condition with how and when the hive boxes are being cleaned up / recreated in the functional test pack
Steps to reproduce
run the functional tests
Expected behavior
functional tests should pass or fail consistently

Setting to P0 because (a) worrying messages are worrying (b) happens frequently, which means it is a big thief of time


text:
Update TLS connection to optionally output TLS keys to file

Is your feature request related to a problem? Please describe.
Update TLS connection to optionally output TLS keys to file. This allows you to "see" inside the TLS packets using WireShark and diagnose issues.
Describe the solution you'd like
Open to suggestions on implementation but it would be nice just to include a dev low level library that includes this feature. So testing can be done by including a dev library in pubspec.yaml. This would dump the TLS keys in the directory where the binary is being run.
The additional lines of code required to do this are :-
In at_lookup_impl.dart
      var secConConnect = SecurityContext();
       var keyfile = File('keysfile');
       secConConnect.setTrustedCertificates('caroot/rootcacert.pem');
      var secureSocket = await SecureSocket.connect(host, int.parse(port), context: secConConnect, keyLog: (line) => keyfile.writeAsStringSync(line, mode: FileMode.append));

And in monitor_client.dart
var secConConnect = SecurityContext();
       var keyfile = File('keysfile');
       secConConnect.setTrustedCertificates('caroot/rootcacert.pem');
      var secureSocket = await SecureSocket.connect(host, int.parse(port), context: secConConnect, keyLog: (line) => keyfile.writeAsStringSync(line, mode: FileMode.append));

replacing the secureSocket connection with no SecurityContent()
It would be nice to abstract the SecureSocket.connect so only one change would effect both lines of code and then that abstraction could be used in the secondary server code as well perhaps.
Describe alternatives you've considered
I did consider pushing all the way through via command line options or by adding a method options but that I think holds the danger of leaving it in place before going to a prod build.. But open to them or other ideas..
Additional context
Screen shot of the resulting Wireshark diagnostics

Flowchart for proposed changes
flowchart TD
    A[Start] --> B[CreateSecureSocket]
    B --> C [Read preference]
    C --> D {decryptPackets?}
    D -->|No| E[Create secure socket without security context]
    D -->|Yes| F[Create secure socket with security context]
    E --> G [End]
    F --> G

https://api.flutter.dev/flutter/dart-io/SecureSocket/connect.html

files to modify on client side
at_client/lib/src/manager/monitor.dart
at_lookup/lib/src/at_lookup_impl.dart

wireshark TLS decryption
https://wiki.wireshark.org/TLS#tls-decryption

The above-listed PRs contain implementation for creating sockets with security context and changes necessary to support this new implementation.
What needs to be worked on further: Unit tests in at_client_sdk need minor changes to the way they mock MonitorOutboundConnectionFactory class as this class uses a new implementation to create secure sockets.

When testing this I only see one TLS connection dumping the keys .. The monitor connection.. We need to sump keys for all files. The test for the rootcacerts file also does not error if the file is not there. Plus if the files is not there for the keys it does not get opend (it is being opened in append mode)

Ok I have spotted the problem in at_libraraies and posted a branch with a 'fix'
@srieteja  see what you think
I am not too sure how the monitor connection gets picked up ?? As I see nowhere in monitor_client.dart where the code uses the TLS dumping socket connection , does that happen somewhere else now ??
the branch is 'tlsdump` I tested sshnp's using
dependency_overrides:
  at_lookup:
      git:
         url: https://github.com/atsign-foundation/at_libraries.git
         path: at_lookup
         ref: tlsdump

The monitor uses the SecureSocketUtil in 'at_client/lib/src/manager/monitor.dart'. This was a more feasible place to do this as we needed access to the AtClientPreferences. @cconstab

Is my fix ok? @srieteja if so I will raise a PR

@cconstab I was able to understand the problem but I was unable the understand the fix. Perhaps you could send me your tls keys file with the fix(so that I could understand the diff) or we could jump on a quick call ? Hope I'm not interrupting your weekend :)

Yup it's just a single line change to remove the bool.  The rest is just editor noise

Yes. The thing that is bugging me is that even though the false statement was removed, the default value for decryptPackets is false in SecureSocketConfig class. I'm just trying to understand how removing the false statement is affecting the functioning.

@cconstab I just debugged it and understood your fix and was able to observe the bug. Also if it's okay with you I would like to push a commit into your branch resolving the case with rootcerts availability check.

That's great thanks

When testing this I only see one TLS connection dumping the keys .. The monitor connection.. We need to dump keys for all files. The test for the rootcacerts file also does not error if the file is not there. Plus if the files is not there for the keys it does not get opend (it is being opened in append mode)..

@cconstab sorry for the delay, I forgot to push the change into the branch. I put a fix to throw an error when the certs don't exist. Reg the other thing I used append mode instead of write as append does not overwrite data from previous sessions, and append does create a new file when a file does not already exist.

I think this has been completed but waiting for @cconstab to approve the PR

Ok I have tested this an approved the PR ... Thanks folks!

Once PR is merged and published, we can close this ticket

authors: VJag cconstab gkc murali-shris srieteja


text:
SimplifyType is too expensive

Now that the dust is starting to settle after changing values to be backed by bytes, SimplifyType is rising the top of alot of profiles.
The algorithm is unavoidably costly. I think a good kind of approach here is to try to avoid recomputing a simplified type that we've already computed a bunch (e.g. when creating large collections)

Thinking about this more, I think I can imagine three approaches to mitigating the cost of simplify type:

Find some way to implement which is lost costly in terms of number of memory allocations
Memoize the work so that we don't keep recomputing the same simplified type for the same (or very similar) input types
Avoid doing it at all if the type doesn't need to be simplified

I think maybe a good first place to start is (3) above. I think there's probably a 60-80% base case here which is that SimplifyType gets called everytime the sequence chunker produces a new node in a prolly tree. What gets simplified is all of the elements of the sequence. It's probably more often than not that
a) Each element is exactly the same type
b) Any given element is already Simplified
I think simply detecting this case and avoiding the call to SimplifyType is a good place to start and will help with the major of cases.

repo: attic-labs/noms


text:
Bot logins before joining any team ?

If a bot tries to login before it joins any team, there will be error in MattermostAPIv4.load_initial_data
Should mattermost_bot allows this bot to login ?
A possible way to do that :
def load_initial_data(self):
!   self.teams = self.get('/users/me/teams')
+   self.teams_channels_ids = {}
+   if len(self.teams) == 0:
+       return
    self.default_team_id = self.teams[0]['id']
-   self.teams_channels_ids = {}
    for team in self.teams:
        self.teams_channels_ids[team['id']] = []
        # get all channels belonging to each team
        for channel in self.get_channels(team['id']):
            self.teams_channels_ids[team['id']].append(channel['id'])

Or should mattermost_bot throws defined exception ?

Need to check if not having a default_team_id in this scenario would be a problem. Have you had a chance to test this proposal @seLain?

The default_team_id is necessary for MattermostAPI (APIv3) when calling webhooks. In MattermostAPIv4, there is not much usage of it since the APIv4 webhook is not supported in mattermost_bot yet ....
Maybe we should postpone this issue and think about it more globally. Along with the deprecation of APIv3, the MattermostAPIv4 does not have to extend MattermostAPI (APIv3) anymore. Further, there should be more enhancements needed for mattermost_bot in supporting APIv4. At that time, I believe this issue will be resolved consequently.
After all, a bot must be added to at least one team. Otherwise it can do almost nothing. This issue can be easily skipped this way in normal cases. :stuck_out_tongue:

Totally agree. We should update the documentation to specify that the bot user must be added to at least one team prior to actually running the bot.

authors: attzonko seLain

license: MIT


text:
Remove auto-generated comment :)

I guess the generated docs files are quite modified compared to what sphinx autogenerates, so we can remove this :)

Apparently I end all sentences with smileys right now :)

Right, makes sense!

authors: benjaoming eliasdorneles

repo: audreyr/cookiecutter-pypackage


text:
Merge develop to serenity (#9)

Update ci.yml

fix deployment ts (#8)

Update ci.yml

Co-authored-by: kienvc vuchikien269@gmail.com

@doquockhanhan : Tuần sau merge

repo: aura-nw/verify-contract


text:
fix(tests): Fixed ReferenceError in two tests

Fixed missing done parameters

thanks :+1:

repo: aurelia/animator-css


text:
[Bug] When using 2 config files, bundle fail

I using skeleton-esnext 1.0.0
JSPM Version: 0.16.45
bundle.js
var gulp = require('gulp');
var bundler = require('aurelia-bundler');
var bundles = require('../bundles.js');

var config = {
    force: true,
    baseURL: '.',
    configPath: [
        './jspm.config.js',
        './jspm.config-extend.js'
    ],
    injectionConfigPath: './jspm.config.js',
    bundles: bundles.bundles
};

gulp.task('bundle', ['build'], function () {
    return bundler.bundle(config);
});

gulp.task('unbundle', function () {
    return bundler.unbundle(config);
});

when run gulp export or gulp bundle, get the error:
[17:51:03] 'bundle' errored after 864 ms [17:51:03] Error on fetch for npm:jquery@3.1.0.js at file:///Users/xujin/My_Projects/NodeJS/antme-web-client/npm:jquery@3.1.0.js         Error: ENOENT: no such file or directory, open '/Users/xujin/My_Projects/NodeJS/antme-web-client/npm:jquery@3.1.0.js'     at Error (native)
jspm.config.js
System.config({
  defaultJSExtensions: true,
  transpiler: false,
  paths: {
    "*": "dist/*",
    "github:*": "jspm_packages/github/*",
    "npm:*": "jspm_packages/npm/*"
  },
  map: {
    "aurelia-animator-css": "npm:aurelia-animator-css@1.0.1",
    "aurelia-bootstrapper": "npm:aurelia-bootstrapper@1.0.0",
    "aurelia-framework": "npm:aurelia-framework@1.0.3",
    "aurelia-history-browser": "npm:aurelia-history-browser@1.0.0",
    "aurelia-http-client": "npm:aurelia-http-client@1.0.0",
    "aurelia-i18n": "npm:aurelia-i18n@1.1.2",
    "aurelia-loader-default": "npm:aurelia-loader-default@1.0.0",
    "aurelia-logging-console": "npm:aurelia-logging-console@1.0.0",
    "aurelia-pal-browser": "npm:aurelia-pal-browser@1.0.0",
    "aurelia-polyfills": "npm:aurelia-polyfills@1.1.1",
    "aurelia-router": "npm:aurelia-router@1.0.3",
    "aurelia-templating-binding": "npm:aurelia-templating-binding@1.0.0",
    "aurelia-templating-resources": "npm:aurelia-templating-resources@1.0.0",
    "aurelia-templating-router": "npm:aurelia-templating-router@1.0.0",
    "bluebird": "npm:bluebird@3.4.6",
    "i18next": "npm:i18next@3.4.3",
    "i18next-xhr-backend": "npm:i18next-xhr-backend@1.2.0",
    "intl": "npm:intl@1.2.5",
    "jquery": "npm:jquery@3.1.0",
    "lodash": "npm:lodash@4.16.1",
    "moment": "npm:moment@2.15.0",
    "text": "github:systemjs/plugin-text@0.0.8",
    "github:jspm/nodelibs-assert@0.1.0": {
      "assert": "npm:assert@1.4.1"
    },
    "github:jspm/nodelibs-buffer@0.1.0": {
      "buffer": "npm:buffer@3.6.0"
    },
    "github:jspm/nodelibs-process@0.1.2": {
      "process": "npm:process@0.11.9"
    },
    "github:jspm/nodelibs-util@0.1.0": {
      "util": "npm:util@0.10.3"
    },
    "github:jspm/nodelibs-vm@0.1.0": {
      "vm-browserify": "npm:vm-browserify@0.0.4"
    },
    "npm:assert@1.4.1": {
      "assert": "github:jspm/nodelibs-assert@0.1.0",
      "buffer": "github:jspm/nodelibs-buffer@0.1.0",
      "process": "github:jspm/nodelibs-process@0.1.2",
      "util": "npm:util@0.10.3"
    },
    "npm:aurelia-animator-css@1.0.1": {
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-templating": "npm:aurelia-templating@1.1.0"
    },
    "npm:aurelia-binding@1.0.4": {
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-task-queue": "npm:aurelia-task-queue@1.0.0"
    },
    "npm:aurelia-bootstrapper@1.0.0": {
      "aurelia-event-aggregator": "npm:aurelia-event-aggregator@1.0.0",
      "aurelia-framework": "npm:aurelia-framework@1.0.3",
      "aurelia-history": "npm:aurelia-history@1.0.0",
      "aurelia-history-browser": "npm:aurelia-history-browser@1.0.0",
      "aurelia-loader-default": "npm:aurelia-loader-default@1.0.0",
      "aurelia-logging-console": "npm:aurelia-logging-console@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-pal-browser": "npm:aurelia-pal-browser@1.0.0",
      "aurelia-polyfills": "npm:aurelia-polyfills@1.1.1",
      "aurelia-router": "npm:aurelia-router@1.0.3",
      "aurelia-templating": "npm:aurelia-templating@1.1.0",
      "aurelia-templating-binding": "npm:aurelia-templating-binding@1.0.0",
      "aurelia-templating-resources": "npm:aurelia-templating-resources@1.0.0",
      "aurelia-templating-router": "npm:aurelia-templating-router@1.0.0"
    },
    "npm:aurelia-dependency-injection@1.0.0": {
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-event-aggregator@1.0.0": {
      "aurelia-logging": "npm:aurelia-logging@1.0.0"
    },
    "npm:aurelia-framework@1.0.3": {
      "aurelia-binding": "npm:aurelia-binding@1.0.4",
      "aurelia-dependency-injection": "npm:aurelia-dependency-injection@1.0.0",
      "aurelia-loader": "npm:aurelia-loader@1.0.0",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0",
      "aurelia-task-queue": "npm:aurelia-task-queue@1.0.0",
      "aurelia-templating": "npm:aurelia-templating@1.1.0"
    },
    "npm:aurelia-history-browser@1.0.0": {
      "aurelia-history": "npm:aurelia-history@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-http-client@1.0.0": {
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0"
    },
    "npm:aurelia-i18n@1.1.2": {
      "aurelia-binding": "npm:aurelia-binding@1.0.4",
      "aurelia-dependency-injection": "npm:aurelia-dependency-injection@1.0.0",
      "aurelia-event-aggregator": "npm:aurelia-event-aggregator@1.0.0",
      "aurelia-loader": "npm:aurelia-loader@1.0.0",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-templating": "npm:aurelia-templating@1.1.0",
      "aurelia-templating-resources": "npm:aurelia-templating-resources@1.0.0",
      "i18next": "npm:i18next@3.4.3",
      "intl": "npm:intl@1.2.5"
    },
    "npm:aurelia-loader-default@1.0.0": {
      "aurelia-loader": "npm:aurelia-loader@1.0.0",
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-loader@1.0.0": {
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0"
    },
    "npm:aurelia-logging-console@1.0.0": {
      "aurelia-logging": "npm:aurelia-logging@1.0.0"
    },
    "npm:aurelia-metadata@1.0.0": {
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-pal-browser@1.0.0": {
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-polyfills@1.1.1": {
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-route-recognizer@1.0.0": {
      "aurelia-path": "npm:aurelia-path@1.0.0"
    },
    "npm:aurelia-router@1.0.3": {
      "aurelia-dependency-injection": "npm:aurelia-dependency-injection@1.0.0",
      "aurelia-event-aggregator": "npm:aurelia-event-aggregator@1.0.0",
      "aurelia-history": "npm:aurelia-history@1.0.0",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0",
      "aurelia-route-recognizer": "npm:aurelia-route-recognizer@1.0.0"
    },
    "npm:aurelia-task-queue@1.0.0": {
      "aurelia-pal": "npm:aurelia-pal@1.0.0"
    },
    "npm:aurelia-templating-binding@1.0.0": {
      "aurelia-binding": "npm:aurelia-binding@1.0.4",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-templating": "npm:aurelia-templating@1.1.0"
    },
    "npm:aurelia-templating-resources@1.0.0": {
      "aurelia-binding": "npm:aurelia-binding@1.0.4",
      "aurelia-dependency-injection": "npm:aurelia-dependency-injection@1.0.0",
      "aurelia-loader": "npm:aurelia-loader@1.0.0",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0",
      "aurelia-task-queue": "npm:aurelia-task-queue@1.0.0",
      "aurelia-templating": "npm:aurelia-templating@1.1.0"
    },
    "npm:aurelia-templating-router@1.0.0": {
      "aurelia-dependency-injection": "npm:aurelia-dependency-injection@1.0.0",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0",
      "aurelia-router": "npm:aurelia-router@1.0.3",
      "aurelia-templating": "npm:aurelia-templating@1.1.0"
    },
    "npm:aurelia-templating@1.1.0": {
      "aurelia-binding": "npm:aurelia-binding@1.0.4",
      "aurelia-dependency-injection": "npm:aurelia-dependency-injection@1.0.0",
      "aurelia-loader": "npm:aurelia-loader@1.0.0",
      "aurelia-logging": "npm:aurelia-logging@1.0.0",
      "aurelia-metadata": "npm:aurelia-metadata@1.0.0",
      "aurelia-pal": "npm:aurelia-pal@1.0.0",
      "aurelia-path": "npm:aurelia-path@1.0.0",
      "aurelia-task-queue": "npm:aurelia-task-queue@1.0.0"
    },
    "npm:bluebird@3.4.6": {
      "process": "github:jspm/nodelibs-process@0.1.2"
    },
    "npm:buffer@3.6.0": {
      "base64-js": "npm:base64-js@0.0.8",
      "child_process": "github:jspm/nodelibs-child_process@0.1.0",
      "fs": "github:jspm/nodelibs-fs@0.1.2",
      "ieee754": "npm:ieee754@1.1.6",
      "isarray": "npm:isarray@1.0.0",
      "process": "github:jspm/nodelibs-process@0.1.2"
    },
    "npm:i18next@3.4.3": {
      "process": "github:jspm/nodelibs-process@0.1.2"
    },
    "npm:inherits@2.0.1": {
      "util": "github:jspm/nodelibs-util@0.1.0"
    },
    "npm:intl@1.2.5": {
      "process": "github:jspm/nodelibs-process@0.1.2"
    },
    "npm:process@0.11.9": {
      "assert": "github:jspm/nodelibs-assert@0.1.0",
      "fs": "github:jspm/nodelibs-fs@0.1.2",
      "vm": "github:jspm/nodelibs-vm@0.1.0"
    },
    "npm:util@0.10.3": {
      "inherits": "npm:inherits@2.0.1",
      "process": "github:jspm/nodelibs-process@0.1.2"
    },
    "npm:vm-browserify@0.0.4": {
      "indexof": "npm:indexof@0.0.1"
    }
  }
});

jspm.config-extend.js
System.config({
    paths: {
        "libs/*": "libs/*"
    }
});

The problem seems to be caused by jspm.config.js overrided by jspm.config-extend.js.

@XuJinNet  If possible point me to a Github repo that I can use that reproduces this issue. It will be easier for me to debug. Thanks for reporting.

@ahmedshuhel please visit https://github.com/XuJinNet/aurelia-skeleton-esnext
Thank you !!!!

Looking at it.

@XuJinNet Does your app run with gulp serve? I am unable to run it locally. You have config.js in index.html but you don't have any file in the project root. Before bundling we need to have a working application.

@ahmedshuhel  fixed, please pull, thanks

Looking at it.

@XuJinNet I can bundle your app without any problem. I just had to remove and invalid entry from your bundle config. So, now it looks like this:
var gulp = require('gulp');
var bundler = require('aurelia-bundler');
var bundles = require('../bundles.js');

var config = {
  force: true,
  baseURL: '.',
  configPath: './jspm.config.js',
  injectionConfigPath: './jspm.config.js',
  bundles: bundles.bundles
};

gulp.task('bundle', ['build'], function() {
  return bundler.bundle(config);
});

gulp.task('unbundle', function() {
  return bundler.unbundle(config);
});

Simply, configPath: './jspm.config.js' should be your configPath as you are only using that in your index.html here. You are not using jspm.config-extended.js in index.html or anywhere in the app, thus you should not use it in the bundler config. Thank you.

@ahmedshuhel Sorry, i need the file jspm.config-extended.js, i using it in my project,  i fixed the repo, please pull, thanks.

Could you please point me to where you have used jquery that you configured in https://github.com/XuJinNet/aurelia-skeleton-esnext/blob/master/jspm.config-extend.js ? Then again, I suppose having two config file is not the issue here. It's about the correctness of SystemJS config.  Try importing jquery and use it in your code somewhere and see if your application runs/works and then if the bundling fails please report back.

@ahmedshuhel OK, please pull, thanks.
https://github.com/XuJinNet/aurelia-skeleton-esnext/blob/master/src/welcome.js

Looking at it.

authors: XuJinNet ahmedshuhel

repo: aurelia/bundler


text:
Call internationalization

Add internationalization configuration as parameter of both: check for updates and update methods.

Implemented by e3daf30e81aac6c506dfb080e207c6509613d663.

repo: aureliano/caravela


text:
Use erc721-balance to quickly query badges

This PR integrates erc721-balance by @vrde.
Here's a page that explains what it does: https://vrde.github.io/erc721-benchmark/
TL;DR: It queries ERC721 tokens super quickly by taking advantage of batch calls against the JSON-RPC API. This shows especially when you have lots of badges.
Note: Code is very alpha and may contain bugs. Surely @vrde would be interested to iterate with you on this :)

erc721-balance@0.0.1 contains a bug where accounts with a balance of 0 cannot be retrieved. Fixed it here: https://github.com/vrde/erc721-balance/pull/2/files Let's wait for this to be published on npm before merging this PR.

repo: austintgriffith/burner-wallet


text:
Incompatible types in typeclass instances are not caught by the checker

While looking into why the standard library wasn't building correctly for me, I found that that readByte for StandardInput
was trying to call an incompatible mono in the generated c code.
In the source I found that the implementations of the readByte and writeByte functions in the instances for StandardInput and StandardError respectively did not have the correct types in the function definition.
The typeclass definition demands that the instance type parameter matches the stream type
-- standard/src/IO/IO.aui
typeclass ByteInputStream(T: Type) is
    generic [R: Region]
    method readByte(stream: &![T, R]): Option[Nat8];
end;

But the implementation does not follow this
-- standard/src/IO/Terminal.aum
instance ByteInputStream(StandardInput) is
    generic [R: Region]
    method readByte(stream: &![StandardOutput, R]): Option[Nat8] is
        let stdin: Address[Nat8] := getStdin();
        let res: Int32 := fgetc(stdin);
        if res = EOF then
            return None();
        else
            return toNat8(res);
        end if;
    end;
end;

I have created a PR to fix the discrepancy in this code, but surely this should be getting caught by the type checker?

Yes this is absolutely a bug in the type checker. Thanks for reporting and fixing the code!

repo: austral/austral


text:
🛑 repl.co is down

In b05e2cb, repl.co (https://hello-repl.auteen.repl.co) was down:

HTTP code: 404
Response time: 599 ms

Resolved: repl.co is back up in af7eddb after 45 minutes.

repo: auteen/autoreplit


text:
ESD-32354: Add disable_self_service_change_password to AD connection options

🔧 Changes
Adds support for disable_self_service_change_password on AD Connection Options.
📚 References

https://github.com/auth0/terraform-provider-auth0/issues/870

🔬 Testing

📝 Checklist

[x] All new/changed/fixed functionality is covered by tests (or N/A)
[x] I have added documentation for all new/changed functionality (or N/A)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ba83c16) 94.80% compared to head (09ffb2c) 94.81%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #308   +/-   ##
=======================================
  Coverage   94.80%   94.81%
=======================================
  Files          46       46
  Lines        8916     8921    +5
=======================================
+ Hits         8453     8458    +5
  Misses        361      361
  Partials      102      102

Files
Coverage Δ

management/connection.go
72.50% <ø> (ø)

management/management.gen.go
100.00% <100.00%> (ø)

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

authors: codecov-commenter sergiught


text:
Extra +s are being appended to formData's strings

When sending in formData with some structure as { key: "this is a test" }, all of the spaces in the string are replaced with + after being processed.

Hi! Sorry this took a while! You can now pass convertPluses: true as a config option to form and softForm to enable this behaviour. Otherwise if it's default, it would interfer with actual plus signs. If you want to avoid this altogether you can use enctype="multipart/form-data" in your form which will encode strings properly.

Thanks!

No prob :) I also added file upload support in 1.5.0


text:
fix: resolve namespace cfg snapshot timestamps uniquly per namespace

The changes herein ensure that namespace config snapshots are resolved and propagated uniquely per namespace. namespace config changes can happen at different times between any two different namespaces, and therefore we must propagate the snapshot timestamps independently in the request context.
Fixes #36 .

Codecov Report

Merging #37 (9579d47) into master (e914a98) will increase coverage by 1.87%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #37      +/-   ##
==========================================
+ Coverage   76.07%   77.94%   +1.87%
==========================================
  Files           8        8
  Lines        1028     1147     +119
==========================================
+ Hits          782      894     +112
- Misses        182      189       +7
  Partials       64       64

Impacted Files
Coverage Δ

internal/access-controller.go
75.87% <100.00%> (+1.51%)
:arrow_up:

internal/namespace.go
100.00% <100.00%> (ø)

internal/tree.go
100.00% <0.00%> (ø)

internal/hashring.go
100.00% <0.00%> (ø)

internal/client-router.go
100.00% <0.00%> (ø)

internal/healthchecker.go
100.00% <0.00%> (ø)

internal/relation-tuple.go
100.00% <0.00%> (ø)

internal/namespace-manager/postgres/manager.go
57.21% <0.00%> (+1.47%)
:arrow_up:

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 e914a98...9579d47. Read the comment docs.

Sweet. I'll merge tonight and cut a patch release for it. Thanks!

authors: codecov-commenter jon-whit

repo: authorizer-tech/access-controller


text:
extraPodAnnotations doesn't apply to the migration pod

I deployed the following in a namespace that has istio injection enabled
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: dev
spec:
  config:
    datastoreEngine: postgres
    extraPodAnnotations:
      sidecar.istio.io/inject: "false"
  secretName: dev-spicedb-config

I was trying to add the annotation with extraPodAnnotations to the generated pods so that the sidecar doesn't get injected
Istio adds a sidecar to every pod created in that namespace. Because the sidecar keeps running, the pod never reaches the Completed stage, preventing the operator from progressing further (and creating the spicedb pods)
Since this migration pod is also generated by the operator, shouldn't the additional annotations apply to the migration pod as well?
I know I can either deploy the spicedb cluster to a namespace that doesn't inject sidecars, or configure the Istio operator to never inject anything in the pods that match the labels for spicedb, But it may be simpler, and perhaps more consistent, to apply the same annotations to the migration pod as well.
Another possible solution could be for the operator to only check the status of the migration container within the pod, instead of checking the pod status before moving on

Right now, extraPodLabels only applies to the deployment pods, not the jobs.
There's a PR in progress (https://github.com/authzed/spicedb-operator/pull/135) that attempts to address this generically - that would look something like:
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: dev
spec:
  config:
    datastoreEngine: postgres
  secretName: dev-spicedb-config
  patches:
    - kind: Job
      patch:
        spec:
          template:
            metadata:
              annotations:
                sidecar.istio.io/inject: "false"

Thanks for the very quick response (once again, since you did the same earlier this morning). Looking forward to it.

While the PR #135 looks exciting, until the work there has completed, consider merging PR #147.

@ecordell any plans to cut a new release with the #147 merged in?

authors: Bhashit ecordell thomasklein94

repo: authzed/spicedb-operator


text:
SpiceDb crashing unexpectedly

I came across a weird behaviour for SpiceDB - it crashed with an exit code 2.
Here is the tail of the log:
{"level":"error","module":"pgx","args":[],"err":"ERROR: relation \"relation_tuple_transaction\" does not exist (SQLSTATE 42P01)","pid":7266,"sql":"\n\tSELECT COALESCE(\n\t\t(SELECT MIN(id) FROM relation_tuple_transaction WHERE timestamp >= TO_TIMESTAMP(FLOOR(EXTRACT(EPOCH FROM NOW() AT TIME ZONE 'utc') * 1000000000 / 5000000000) * 5000000000 / 1000000000) AT TIME ZONE 'utc'),\n\t\t(SELECT MAX(id) FROM relation_tuple_transaction)\n\t),\n\t5000000000 - CAST(EXTRACT(EPOCH FROM NOW() AT TIME ZONE 'utc') * 1000000000 as bigint) % 5000000000;","time":"2022-09-28T11:52:42Z","message":"Query"}
panic: interface conversion: interface {} is nil, not decimal.Decimal

goroutine 786 [running]:
github.com/authzed/spicedb/internal/datastore/common/revisions.(*CachedOptimizedRevisions).OptimizedRevision(0xc000b087c0, {0x2117760?, 0xc000e74280?})
	/home/runner/work/spicedb/spicedb/internal/datastore/common/revisions/optimized.go:72 +0x4d3
github.com/authzed/spicedb/internal/datastore/proxy.hedgingProxy.OptimizedRevision.func1({0x2117760?, 0xc000e74280?}, 0x0?)
	/home/runner/work/spicedb/spicedb/internal/datastore/proxy/hedging.go:179 +0x65
created by github.com/authzed/spicedb/internal/datastore/proxy.newHedger.func1
	/home/runner/work/spicedb/spicedb/internal/datastore/proxy/hedging.go:78 +0x27b
paw-marketplace-spicedb-1 exited with code 2

It is being run inside a docker-compose like so:
pg-spicedb:
    image: postgres:14-alpine
    healthcheck:
      test: [ 'CMD-SHELL', 'pg_isready -U postgres -d spicedb' ]
      interval: 10s
      timeout: 5s
      retries: 5
    labels:
      - 'traefik.enable=false'
    expose:
      - '5432'
    environment:
      POSTGRES_PASSWORD: postgres
      POSTGRES_USER: postgres
      POSTGRES_DB: spicedb
    volumes:
      - pg-spicedb-data:/var/lib/postgresql/data

spicedb:
    image: quay.io/authzed/spicedb:v1.9.0
    depends_on:
      - pg-spicedb
    labels:
      - 'traefik.enable=false'
    ports:
      - 50051:50051
    volumes:
      - ./libs/authz/schema.local.yml:/schema.yml
    environment:
      - SPICEDB_GRPC_PRESHARED_KEY=localadmin
      - SPICEDB_GRPC_ENABLED=1
      - SPICEDB_GRPC_ADDR=:50051
      - SPICEDB_GRPC_NO_TLS=1
      - SPICEDB_METRICS_ENABLED=0
      - SPICEDB_DASHBOARD_ENABLED=0
      - SPICEDB_DATASTORE_ENGINE=postgres
      - SPICEDB_DATASTORE_CONN_URI=postgresql://postgres:postgres@pg-spicedb:5432/spicedb?sslmode=disable
      - SPICEDB_DATASTORE_BOOTSTRAP_FILES=/schema.yml
      - SPICEDB_DATASTORE_BOOTSTRAP_OVERWRITE=1
      - SPICEDB_TELEMETRY_ENDPOINT=
    command: serve

👋🏻 It seems like you are running v1.9.0. In that version, if an error happened while checking for optimized revisions, it was not checked and would panic:
https://github.com/authzed/spicedb/blob/ae4552ed89f0561f71893da2feeb7feb1e767e71/internal/datastore/common/revisions/optimized.go#L71-L72
You can see that this was fixed in https://github.com/authzed/spicedb/pull/740, which is part of release v1.12.0.
Feel free to reopen if that does not fix your problem! 🙇🏻

authors: jakub-lesniak-mck vroldanbet

repo: authzed/spicedb


text:
Surround URL replacements option with quotes

Internal ticket: https://app.clickup.com/t/864ea29wc
https://github.com/autifyhq/autify-cli/pull/389
To support --url-replacements option with space delimiter we need to surround the arg with quotes.
I confirmed it works well on autify-cli with this commit https://github.com/autifyhq/autify-cli/pull/389/commits/84b25fd9d2fe19e536e948b4abe2948cbfea8629

The escaping looks good. Then, it reminds us that the URLs containing , will be broken (also CircleCI integrations as well).

Then, it reminds us that the URLs containing , will be broken (also CircleCI integrations as well).

True, we need to have another delimiter to pass multiple replacements option via CI integrations.
I will raise an internal ticket but will not deal with it here since it'll be also breaking change.

authors: mtsmfm riywo

repo: autifyhq/actions-web-test-run


text:
Adsk Contrib - Add cmake option OCIO_HAS_BUILTIN_YAML_CONFIGS

Adding cmake option to remove built-in yaml based configs (CGConfig and StudioConfig). When this option is turned off, the tests that rely on the built-in configs will also be removed.

Yes, when the YAML switch is added this will be controlled by it too. These PR's are for rolling in all the previous work in separable pieces.

repo: autodesk-forks/OpenColorIO


text:
The file extension loaded into the viewer is not supported

I have a 2022 revit model (.rvt).
I want to know whether the problem comes from the version of the software or from the formats that are supported by the app.
I used the same revit file as in the README.
The file extension loaded into the viewer is not supported

@petrbroz
Thank you.

Solved.
https://gist.github.com/salahelfarissi/784796c339ea39ec917f919db6f203fc


text:
prune vendor using pruning rules

Before prune:
$ du -sh vendor/
121M     vendor/

After prune:
$ du -sh vendor/
41M     vendor/

Thanks @jmrodri You're going to have to show me how to do this :)

authors: dymurray jmrodri

repo: automationbroker/sbcli


text:
Doitpay Go SDK

Implementation:

docs/ masih WIP

Gokil 16K 🤣

Pada github action tambahkan job untuk running Unit test

authors: kervinch reza-putra

repo: automotechnologies/doitpay-go


text:
How could I disable verbose output

chatty(false) is no-op now. Do I have an opportunity to disable console output?

Thanks for asking. I have made an effort with recent releases to reduce console output by default. Do you find this is still too verbose?

Yes, we have a lot of modules around 300 and a lot of plugins and they all want to print something
Now your plugin makes a lot of noise in the logs
It makes hard to read logs and I prefer to look for your plugin advice only in files

Thanks for the response. Would you like the ability to suppress all output from this plugin?

It would be enough for me.

I'm not sure I want to make this an extension method (like chatty), but I'm also not totally opposed to it. What about using a system property to disable it? You could do it via the command line or in gradle.properties.

For me, it would be enough. Feel free to make any design decision you think fits for your vision

Note to self, I think I only need to disable logging in the AdviceSubprojectAggregationTask class. This is one of only two places where logger.quiet is used. The other is FailOrWarnTask, which runs just once per invocation of buildHealth, compared to once per subproject for the Advice... task.

I have resolved this by adding a system property the plugin will respond to. If you add
systemProp.dependency.analysis.silent=true

to gradle.properties, then logging will be greatly reduced. You may also use -Ddependency.analysis.silent=true on the command line.
This has not yet been published, but is available as a snapshot if you want to test.

authors: autonomousapps sboishtyan


text:
ignoreKtx(true) is not working

Plugin version
2.1.4
Gradle version
8.10.2
JDK version
23
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
2.0.20
(Optional) Android Gradle Plugin (AGP) version
8.6.2
(Optional) reason output for bugs relating to incorrect advice
./gradlew sha:vide:reason --id androidx.lifecycle:lifecycle-runtime:2.8.6
:shared:video-player
\--- io.coil-kt:coil-base:2.7.0
      \--- androidx.lifecycle:lifecycle-runtime:2.8.6

Source: developDebug, main
--------------------------
(no usages)

./gradlew sha:vide:reason --id libs.androidx.lifecycle.runtime
Shortest path from :shared:video-player to androidx.lifecycle:lifecycle-runtime-ktx:2.8.6 (libs.androidx.lifecycle.runtime) for nowsecureReleaseUnitTestRuntimeClasspath:
:shared:video-player
\--- androidx.lifecycle:lifecycle-runtime-ktx:2.8.6

Source: developDebug, main
--------------------------
(no usages)

Describe the bug
The ktx dependency is proposed to be removed and the normal dependency is proposed to be added even we have
dependencyAnalysis {
    structure {
        ignoreKtx(true) // default is false
    }
}

In the root folder.
Expected behavior
ignoreKtx is respected
Additional context
Plugin is applied in root folder and then applied in every module. The ignoreKts is applied in the root file.

Thanks for the issue. Do you have a reproducer?

Sorry for the delay, let me try in small project.

authors: autonomousapps emartynov


text:
Add definition of "Script Plugin"

https://kotlinlang.slack.com/archives/C19FD9681/p1652110468534199?thread_ts=1652107016.526049&cid=C19FD9681

Oops, @martinbonnin was wrong, it is there.  My fault for not double-checking though 😂
https://github.com/autonomousapps/gradle-glossary#script-plugin
CLOSING

repo: autonomousapps/gradle-glossary


text:
Compiling for Windows?

Hello,
I made a trimmed down version and building for Linux is easy. I'm having issues with building on Windows. Can you post directions online?
Thank you!

I figured it out

I figured it out

repo: autopilot-rs/autopy


text:
chore: sync issue and PR templates

Sync files that will be added in https://github.com/autowarefoundation/autoware/pull/56.

pre-commit.ci run

@xmfcx cc @mitsudome-r I'll explain about this CI here.
If we change the settings like this,

and run the workflow sync-files,

this kind of PR is created. It enables us to sync files between repositories easily.
https://github.com/autowarefoundation/autoware.core/pull/12

This time I've run it manually, the workflow usually runs automatically every day.

This time I've run it manually, the workflow usually runs automatically every day.

Why not run it with every commit?

Every commit in which repository? :thinking:
Anyway, we don't have to run this workflow so frequently. I believe daily execution is enough.
If necessary, you can run it anytime you like using workflow_dispatch. (What I've used this time.)

Every commit in which repository? 🤔 Anyway, we don't have to run this workflow so frequently. I believe daily execution is enough. If necessary, you can run it anytime you like using workflow_dispatch. (What I've used this time.)

Ah this repository doesn't have ability to get event notifications from the https://github.com/autowarefoundation/autoware-github-actions/tree/main/sync-files so we cannot trigger this when changes to that repo occurs right?

@xmfcx Actually, it's technically possible, for example by https://github.com/peter-evans/repository-dispatch.
But I think it's a bit complex for this use case.

authors: kenji-miyake xmfcx


text:
feat(obstacle_cruise_planner): implement slow down planner

Description
Implemented slow down planner, inserting slow down point in the trajectory where the point is close to the dynamic/static obstacles.

Related links
launcher PR: https://github.com/autowarefoundation/autoware_launch/pull/288
Tests performed
Planning simulator works well.

TODO

[x] scenario sim: https://evaluation.tier4.jp/evaluation/reports/50ce7861-d8b3-5ef9-87b1-f68421f860a8?project_id=prd_jt

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

slow down virtual wall


text:
fix(goal_planner): fix goal search for narrow shoulder lane

Description

Fix goal search for narrow shoulder lane considering patterns when the bound of the vehicle at pull over lane's center line is outside the bound of the lanelet.
before (skip checking is in lane)

after

Related links

Tests performed

psim
!
Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kosuke55
could you give me time to check this PR?
If it's urgent I will take a look briefly

@kyoichi-sugahara
OK, thanks!!b


text:
fix(docker): install CUDA development drivers in development containers

Description
Resolved https://github.com/autowarefoundation/autoware/issues/5219
The cause of #5219 is that due to the changes in #5159, only the CUDA runtime drivers are now being installed in both the development containers and the runtime containers. Though the development containers are required to install the CUDA development drivers.
https://github.com/autowarefoundation/autoware/blob/main/ansible/roles/cuda/tasks/main.yaml#L28-L50
This PR installs CUDA development drivers on development containers.
cc @marioney
Tests performed
https://github.com/youtalk/autoware/actions/runs/11288251647
https://github.com/youtalk/autoware/actions/runs/11288252539
Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

I hope it was self hosted runner problem. Please let me merge to run by GitHub runner.

repo: autowarefoundation/autoware


text:
feat(autoware_adapi_v1_msgs): add vehicle status msgs

Signed-off-by: tkhmy tkh.my.p@gmail.com
Description

Create msgs for vehicle status

Related links
https://github.com/autowarefoundation/autoware/issues/3232
https://github.com/autowarefoundation/autoware-documentation/pull/312
Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@isamu-takagi I think we will need to add the maximum velocity. Do you think is better to put it in this place?

@tkhmy If it means the limit value of hardware, I think that it can be provided as vehicle information. If it is a config value, it seems better to consider making it as a planning API Including setting service.

@tkhmy If it means the limit value of hardware, I think that it can be provided as vehicle information. If it is a config value, it seems better to consider making it as a planning API including setting service.

@isamu-takagi it should be velocity limit. Ya I think we should put it in planning api instead of vehicle api

@mitsudome-r @isamu-takagi @yukkysaito @kenji-miyake
Hi, I created the message for visualization the vehicle status.
Can you help to review it?
Thank you!

@kenji-miyake @yukkysaito
I think it's okay except for the typo (int8). Do you have any other comments?

@isamu-takagi I think @mitsudome-r needs to get agreements with other AWF members (at least @xmfcx ).

@mitsudome-r @xmfcx Could you check this PR?

authors: isamu-takagi kenji-miyake tkhmy


text:
Unifying the Reporting API: without RaceBuffer for now

Closes #179
Based on #185 , but replaces the RaceBuffer with a basic ring buffer to get us by until the RaceBuffer work settles.

:+1:

authors: ZackPierce jonlamb-gh

repo: auxoncorp/modality-probe


text:
Add ReSwitched Silver™

one real addition to one meme addition is a good ratio right

Can you make it an embed?

thanks I hate it

authors: ThatNerdyPikachu aveao leo60228

repo: aveao/robocop-ng


text:
Improve clarity of 1. Your budget and expectations screen

[ ] It is unclear to the players what values are constant every round: The facilitator can explain that aspect by adding an * to the applicable values and a note below.

I do not think it is wise to hard-code this. Future versions of the game could have changes in these values as a result of news measures (e.g., increased living costs). Therefore, I would not like to change this. Also, the (*) gives extra clutter on the screen.

authors: averbraeck vjcortesa

repo: averbraeck/housinggame-player


text:
Auto save of new asset not working

When auto-save tries to save an asset it "appears" to save because the save button is disabled but the asset is not really saved anywhere. Furthermore, Save As is not enabled to save it somewhere else.

This ended up being a problem with the data model which has now been resolved. Save As will be fixed in a different issue.

repo: avereon/xenon


text:
Load/Save Employee PINs to file

Done When: the pins for every employee can be loaded and saved to file

30 min: planning and discussion with group about what is needed for this and how to approach it. I started coding it but realized I need to merge unfinished work to really get going

1.5 hr: did work on saving to file

1.5 hrs: Fixing issues and getting I/O to work


text:
Adding Wikipedia Scrapper

Aim

What is the objective of the Script
It is basically a technique or a process in which large amounts of data from a huge number of websites is passed through a web scraping software coded in a programming language and as a result, structured data is extracted

Details

What the features will your script have??
Web scraping is an automatic process of extracting information from the web.
It allows scrapping based on Javascript and Python Framework.
Almost compatible with all the websites and retrieve necessary informations

@avinashkranjan  and @1e9abhi1e10 plz assign this issue to me

Go ahead @Shreya111111

@1e9abhi1e10 @Yashbhadiyadra Plz review the PR https://github.com/avinashkranjan/Amazing-Python-Scripts/pull/1867 fixes https://github.com/avinashkranjan/Amazing-Python-Scripts/issues/1849 ..

repo: avinashkranjan/Amazing-Python-Scripts


text:
Vulnerability Assessment and Scanning Script

Aim
The objective of Vulnerability Assessment and Scanning is to identify and assess vulnerabilities within a system, network, or application. This process involves using various tools and techniques to systematically identify weaknesses that could be exploited by attackers.
The main objective is to discover potential vulnerabilities within a system, network, or application. This includes identifying security weaknesses in configurations, software, services, or infrastructure components that could be exploited by malicious individuals.
Once vulnerabilities are identified, they need to be evaluated and prioritized based on their severity and potential impact on the system's security. This allows security teams to focus their efforts on addressing the most critical vulnerabilities first.
By conducting vulnerability assessments and scanning, organizations can gain insights into their security weaknesses and take appropriate measures to strengthen their overall security posture, reduce the risk of exploitation, and protect their systems and data from potential attacks.
Details
Vulnerability scanning script using the popular open-source tool Nmap.
Do I want to work on this:

[x]  Yes
[ ] No

Please assign me this issue under gssoc 23 @avinashkranjan

Go Ahead @Abhinavcode13


text:
JSON-API: No Authorization with valid token sent

Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)

Steps to reproduce
API Authentication: on
Internet API Access: off
Local Admin API Authentication: on
Local API Authentication: off
curl http://localhost:8090/json-rpc -H 'Content-Type: application/json' -H 'Authorization : token [valid token]' -d '{"command":"config","subcommand":"getconfig"}'
What is expected?
output of current config
What is actually happening?
result of curl request:
{
"command": "config",
"error": "No Authorization",
"success": false,
"tan": 0
}
When Local Admin API Authentication is disabled, request will succeed.
Maybe my curl request or my understanding of the security system is wrong, but please have a look at this:
JsonAPI::handleConfigCommand() checks for _adminAuthorized
void JsonAPI::handleConfigCommand(const QJsonObject& message, const QString& command, int tan)
{
...
else if (subcommand == "getconfig")
	{
		if (_adminAuthorized)
			sendSuccessDataReply(QJsonDocument(_hyperhdr->getQJsonConfig()), full_command, tan);
		else
			sendErrorReply("No Authorization", command, tan);
	}

API::isTokenAuthorized() is not setting _adminAuthorized but _authorized:
bool API::isTokenAuthorized(const QString& token)
{
	(_authManager->thread() != this->thread())
		? QMetaObject::invokeMethod(_authManager, "isTokenAuthorized", Qt::BlockingQueuedConnection, Q_RETURN_ARG(bool, _authorized), Q_ARG(QString, token))
		: _authorized = _authManager->isTokenAuthorized(token);

	return _authorized;
}

System

HyperHDR Server:

Build:           master (GitHub-bc24df7/a9a00f9-1678986833)
Build time:      Mar 23 2023 09:35:26
Git Remote:      https://github.com/awawa-dev/HyperHDR.git
Version:         20.0.0.0beta0
UI Lang:         en (BrowserLang: de)
UI Access:       default
Avail Capt:      Linux (V4L2)
Database:        read/write

HyperHDR Server OS:

Distribution:   Raspbian GNU/Linux 11 (bullseye)
Architecture:   arm
CPU Model:      ARMv6-compatible processor rev 7 (v6l)
CPU Type:       Raspberry Pi Zero W Rev 1.1
CPU Revision:   9000c1
CPU Hardware:   BCM2835
Kernel:         linux (6.1.19+ (WS: 32))
Qt Version:     5.15.2
Browser:        Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0

When Local Admin API Authentication is disabled, request will succeed.

When enabled, you first need to ask the user (a dialog will appear on the HyperHDR page if it is open) to authorize the token before using it (authorize>requestToken). I still can't remember if it can be done with http://ip:8090/json-rpc or json port (default 19444).

Hi,
token was created directly in Web UI and i can see it in Token Management. There is a requestToken subcommand and according to the docs a popup should appear in the Web UI to accept/reject the token request. But there seems to be no difference in token creation.
Hyperion.ng has the same problem, there is an old (05/2021) issue about this topic, but i don't expect to get that fixed. This is one of the reasons i try to switch to HyperHDR, because i hope you are more motivated and/or skilled and have a better coding style.
A request to
http://ip:8090/json-rpc?request={%22command%22:%22authorize%22,%22subcommand%22:%22requestToken%22,%22comment%22:%22testtokentest%22}
results in:
{
    "command": "authorize",
    "error": "Command not implemented",
    "success": false,
    "tan": 0
}

BTW: All references to _authorized are in API.cpp and i couldn't find any code checking _authorized, it's always set only. This may be caused by the coding style of hyperion.ng developers, maybe they have removed it, i don't know.
Simple fix of the issue would be to set _adminAuthorized = _authorized; at the end of API::isTokenAuthorized(), but i don't know if this will break something else in security system.
wbr

_adminAuthorized is different from _authorized and requires user interaction: just creating a token is not enough. If you don't want the user to interfere, the local admin option should be disabled (but it's enabled on default and the user has to disable it manually). Even if I redesign it to make it work over https POST (http & GET requests are too risky), user interaction will still be required.

A request to
....
results in:

yes I checked it: it's disabled for http/https requests so only json api RPC port can be used.

Some more test:
http://192.168.32.107:8090/json-rpc?request={"command":"config","subcommand":"getconfig"}
{
"command": "config",
"error": "No Authorization",
"success": false,
"tan": 0
}
http://192.168.32.107:8090/json-rpc?request={"command":"authorize","subcommand":"login","token":"911faca7-0d11-4e06-9424-e46c6c6784b0"}
{
"command": "authorize",
"error": "Command not implemented",
"success": false,
"tan": 0
}
curl --request POST http://localhost:8090/json-rpc -H 'Content-Type: application/json' --data-raw '{"command":"config","subcommand":"getconfig"}'
{
"command": "config",
"error": "No Authorization",
"success": false,
"tan": 0
}
curl --request POST http://localhost:8090/json-rpc -H 'Content-Type: application/json' --data-raw '{"command":"authorize","subcommand":"login","token":"911faca7-0d11-4e06-9424-e46c6c6784b0"}'
{
"command": "authorize",
"error": "Command not implemented",
"success": false,
"tan": 0
}
curl --request POST http://localhost:8090/json-rpc -H 'Content-Type: application/json' -H 'Authorization : token 911faca7-0d11-4e06-9424-e46c6c6784b0' --data-raw '{"command":"config","subcommand":"getconfig"}'
{
"command": "config",
"error": "No Authorization",
"success": false,
"tan": 0
}
echo '{"command":"config","subcommand":"getconfig"}' | nc localhost 19444
{"command":"config","error":"No Authorization","success":false,"tan":0}
waiting for input... need to CTRL-C
echo '{"command":"authorize","subcommand":"login","token":"911faca7-0d11-4e06-9424-e46c6c6784b0"}' | nc localhost 19444
{"command":"authorize-login","success":true,"tan":0}
waiting for input... need to CTRL-C
Looks like JSON-API can be used by raw access to port 19444 only, but there is no way to use it in shell scripts (would like to switch V4L device input by shell script triggered by lirc irexec, executing getconfig, using jq to change, and executing setconfig to save config)
wbr

Just change the token if it exists in your config for this example to work: a message in HyperHDR page will popup when you execute the command.

OK, there is a login subcommand, let's try this:
echo '{"command":"authorize","subcommand":"login","token":"d9f2c817-9b8e-4358-9133-995e611b09ab"}' | websocat -n1 ws://localhost:8090
{"command":"authorize-login","success":true,"tan":0}

Token must be longer than 36 chars https://github.com/awawa-dev/HyperHDR/blob/6a6b29dfa970ff1c0b1b4d46192d27deaedab70c/sources/api/JsonAPI.cpp#L1531
otherwise for 36 chars it triggers method that won't unlock admin access only ordinary authorization
https://github.com/awawa-dev/HyperHDR/blob/6a6b29dfa970ff1c0b1b4d46192d27deaedab70c/sources/api/JsonAPI.cpp#L1541

OK, silly question, how do i get a valid token longer than 36 bytes to unlock admin access?
wbr

Did you check 'auth' table for a token for the user? also login with a password returns it https://github.com/awawa-dev/HyperHDR/blob/6a6b29dfa970ff1c0b1b4d46192d27deaedab70c/sources/api/JsonAPI.cpp#L1562

Hi,
yes there is another entry in auth table
        user = Hyperhdr
    password = 4e0d2fa2cf3741d8999b884f5b77dcbe70c1978abbc9ee656fe1046eb08b788fac4db5903453735f77302358fce50ef51bbe5ea43a132c8d6fc713cf1f8d5860
       token = df7d84dabef464722b5253b4187489e82260def11b16e05cafae27958265946d169ad062767754d17f13a4e424b0c35e8cc08849b25b02199d4597581752a90f
        salt = 510c2bc6125aab9a53aa2dd91f655a1903093ff02d335bb565fd32186bad47eb7c73cd597196a78ef6731ad5003ef29271eae5c847de914e96db0c0e283084df
     comment =
portal_token =
          id =
  created_at = 2023-03-23T15:25:33Z
    last_use = 2023-03-29T22:11:56Z

looks like token is hashed too, let's try to login with password
echo '{"command":"authorize","subcommand":"login","password":"hyperhdr"}' | websocat -n1 ws://localhost:8090

{"command":"authorize-login","info":{"token":"df7d84dabef464722b5253b4187489e82260def11b16e05cafae27958265946d169ad062767754d17f13a4e424b0c35e8cc08849b25b02199d4597581752a90f"},"success":true,"tan":0}

hashed token is longer than 36 bytes, maybe we are logged in now?
echo '{"command":"config","subcommand":"getconfig"}' | websocat -n1 ws://localhost:8090

{"command":"config","error":"No Authorization","success":false,"tan":0}

Maybe the token has to be used either in further requests
echo '{"command":"config","subcommand":"getconfig","token":"df7d84dabef464722b5253b4187489e82260def11b16e05cafae27958265946d169ad062767754d17f13a4e424b0c35e8cc08849b25b02199d4597581752a90f"}' | websocat -n1 ws://localhost:8090

{"command":"config","error":"Errors during specific message validation, please consult the HyperHDR Log","success":false,"tan":0}

WEBSOCKET              : <ERROR> While validating schema against json data of 'JsonRpc@::1':[root].token: no schema definition

OK key "token" is not defined in schema-config.json, let's try to login with token
echo '{"command":"authorize","subcommand":"login","token":"df7d84dabef464722b5253b4187489e82260def11b16e05cafae27958265946d169ad062767754d17f13a4e424b0c35e8cc08849b25b02199d4597581752a90f"}' | websocat -n1 ws://localhost:8090

{"command":"authorize-login","success":true,"tan":0}

echo '{"command":"config","subcommand":"getconfig"}' | websocat -n1 ws://localhost:8090

{"command":"config","error":"No Authorization","success":false,"tan":0}

Any more ideas? Code flow looks like this, there are no errors in log (--debug option)
void JsonAPI::handleAuthorizeCommand(const QJsonObject& message, const QString& command, int tan)
...
if (subc == "login")
...
			if (token.length() > 36)
			{
				if (API::isUserTokenAuthorized(token))
...

bool API::isUserTokenAuthorized(const QString& userToken)
{
	bool res;
	QMetaObject::invokeMethod(_authManager, "isUserTokenAuthorized", Qt::BlockingQueuedConnection, Q_RETURN_ARG(bool, res), Q_ARG(QString, DEFAULT_CONFIG_USER), Q_ARG(QString, userToken));
	if (res)
	{
		_authorized = true;
		_adminAuthorized = true;
		// Listen for ADMIN ACCESS protected signals
		connect(_authManager, &AuthManager::newPendingTokenRequest, this, &API::onPendingTokenRequest, Qt::UniqueConnection);
	}
	return res;
}

bool AuthManager::isUserAuthorized(const QString& user, const QString& pw)
{
	if (isUserAuthBlocked())
		return false;

	if (!_authTable->isUserAuthorized(user, pw))
	{
		setAuthBlock(true);
		return false;
	}
	return true;
}

bool AuthTable::isUserAuthorized(const QString& user, const QString& pw)
{
	if (userExist(user) && (calcPasswordHashOfUser(user, pw) == getPasswordHashOfUser(user)))
	{
		updateUserUsed(user);
		return true;
	}
	return false;
}

wbr

repo: awawa-dev/HyperHDR


text:
Add a "good-thomas double butterfly" algorithm impl

When I added the good-thomas implementation a while back, I tried it with very large sizes, and saw that it didn't really stand up to mixed-radix.
Something I didn't try is very small sizes. It turns out that if both child FFTs are small enough to be butterflies, Dgood-Thomas pretty greatly outperforms mixed-radix. So the planner now does Good-Thomas double butterfly instead of Mixed-Radix Double Butterfly whenever possible.
I also tried using the main Good-Thomas Algorithm instead of Mixed Radix when sizes are less than a few thousand, but I got mixed results. Some benchmarks were improved, while others were worse. If we did something like FFTW where we measured performance as a part of the planning process, it would be worth it to test mixed radix vs good-thomas performance for given sizes, but it seems to be too unreliable to do it all the time.
I also tried another stab at computing the reordering indexes on the fly, and I got a version that's faster than the original, but it's still slower than precomputing them, both at small and large sizes.

Comparing benchmarks of before and after:
PLANNED -- BEFORE
test complex_composite_20736       ... bench:     470,106 ns/iter (+/- 24,886)
test complex_composite_24028       ... bench:   2,118,454 ns/iter (+/- 96,817)
test complex_composite_24576       ... bench:     361,290 ns/iter (+/- 30,788)
test complex_composite_30270       ... bench:   1,164,039 ns/iter (+/- 151,710)
test complex_composite_32192       ... bench:   2,957,133 ns/iter (+/- 287,858)
test complex_prime_0019            ... bench:         262 ns/iter (+/- 58)
test complex_prime_0151            ... bench:       4,154 ns/iter (+/- 302)
test complex_prime_1009            ... bench:      29,750 ns/iter (+/- 2,597)
test complex_prime_2017            ... bench:      75,501 ns/iter (+/- 6,779)
test complex_primepower_160801     ... bench:  10,726,836 ns/iter (+/- 821,831)
test complex_primepower_44521      ... bench:   2,604,360 ns/iter (+/- 89,333)

PLANNED -- AFTER
test complex_composite_20736       ... bench:     454,925 ns/iter (+/- 131,175)
test complex_composite_24028       ... bench:   1,946,914 ns/iter (+/- 115,707)
test complex_composite_24576       ... bench:     353,485 ns/iter (+/- 16,025)
test complex_composite_30270       ... bench:   1,079,107 ns/iter (+/- 52,330)
test complex_composite_32192       ... bench:   2,719,065 ns/iter (+/- 114,287)
test complex_prime_0019            ... bench:         254 ns/iter (+/- 11)
test complex_prime_0151            ... bench:       3,924 ns/iter (+/- 186)
test complex_prime_1009            ... bench:      27,943 ns/iter (+/- 1,231)
test complex_prime_2017            ... bench:      74,977 ns/iter (+/- 3,572)
test complex_primepower_160801     ... bench:   9,487,384 ns/iter (+/- 238,325)
test complex_primepower_44521      ... bench:   2,468,669 ns/iter (+/- 106,513)

And comparing good thomas vs mixed radix at various sizes, showign that good-thomas is much better than mixed radix at small sizes
test good_thomas_0002_3            ... bench:          51 ns/iter (+/- 14)
test good_thomas_0003_4            ... bench:          72 ns/iter (+/- 6)
test good_thomas_0004_5            ... bench:         148 ns/iter (+/- 7)
test good_thomas_0007_32           ... bench:       1,666 ns/iter (+/- 708)
test good_thomas_0032_27           ... bench:      13,751 ns/iter (+/- 743)
test good_thomas_0256_243          ... bench:   1,915,772 ns/iter (+/- 121,952)
test good_thomas_2048_2187         ... bench: 264,304,653 ns/iter (+/- 2,765,125)
test good_thomas_2048_3            ... bench:      71,788 ns/iter (+/- 5,187)
test good_thomas_butterfly_0002_3  ... bench:          32 ns/iter (+/- 7)
test good_thomas_butterfly_0003_4  ... bench:          50 ns/iter (+/- 3)
test good_thomas_butterfly_0004_5  ... bench:         109 ns/iter (+/- 45)
test good_thomas_butterfly_0007_32 ... bench:       1,544 ns/iter (+/- 431)

MIXED RADIX:
test mixed_radix_0002_3            ... bench:          81 ns/iter (+/- 25)
test mixed_radix_0003_4            ... bench:         103 ns/iter (+/- 7)
test mixed_radix_0004_5            ... bench:         180 ns/iter (+/- 51)
test mixed_radix_0007_32           ... bench:       1,861 ns/iter (+/- 115)
test mixed_radix_0032_27           ... bench:      14,030 ns/iter (+/- 768)
test mixed_radix_0256_243          ... bench:   1,735,521 ns/iter (+/- 106,055)
test mixed_radix_2048_2187         ... bench: 193,542,181 ns/iter (+/- 3,073,271)
test mixed_radix_2048_3            ... bench:      75,990 ns/iter (+/- 5,625)
test mixed_radix_butterfly_0002_3  ... bench:          43 ns/iter (+/- 13)
test mixed_radix_butterfly_0003_4  ... bench:          64 ns/iter (+/- 16)
test mixed_radix_butterfly_0004_5  ... bench:         119 ns/iter (+/- 8)
test mixed_radix_butterfly_0007_32 ... bench:       1,684 ns/iter (+/- 126)

Nice work. Thanks!
As an aside, you may have noticed I haven't been putting much time into this project lately. At this point, I think you have a more complete understanding of the code and you seem to have a good vision for pushing this project forward. Would you be willing to assume ownership of this project? You're already a collaborator, so what this means is I would just defer to you for PR decisions and you would manage the version hosted on crates.io.

Could you add me ad an owner on the crate? Username is ejmahler

@awelkie Have you had a chance to look at this?

At the PR or adding you as an owner? I sent the crates.io invitation 5 days ago when you asked, let me know if you didn't get it. I skimmed the PR and it looks fine, but as I said I'll defer to you. You should have permissions to merge pull requests, right?

The crates.io account. I didn't notice that you had sent an invite. I just accepted it! thanks

authors: awelkie ejmahler

repo: awelkie/RustFFT


text:
Added GitHub Student Developer Pack

Link muito útil pro pessoal que usa o gitHub, eles oferecem repositórios privados grátis por 2 anos, UnrealEngine full grátis e desconto e várias outras ferramentas.

A página está em inglês

Eu vi! Mas o link é muito bom, senti que deveria compartilhar. Poderia escrever um artigo sobre ele e explicar em passo a passo com faz pra utilizar. Vocês conhecem algum lugar que eu possa fazer isso? Blog ou algo do tipo.

Você pode escrever no Medium

theSkilled, vc precisa de um email .edu.br para poder ter o direito. basta assinar o programa e se cadastrar com o email.

authors: danielschmitz jonatasleon theSkilled


text:
Add zoxide

zoxide is a blazing fast autojump alternative written in Rust. It's orders of magnitude faster than other autojumpers, cross-shell, and extremely feature-rich.

First you didn't disclose that it was your project. Please do it next time. With 4.3k stars I think it is fine for the popular enough part. Last thing though, this tool is neither written in bash (which could be fine) nor it is bash related. Well it is not more related to bash than zsh or fish. I think zoxide would be perfect for an awesome-cli or something like this. We may have include tool like this in the past. I dont know (who wants to check?). Fianlly, I dont have a close answer to give. Who have an opinion to share?

This tool is neither written in bash (which could be fine) nor it is bash related

IMHO, this is one of the strengths of the project. Because it's not linked to a shell, it can work across other applications like ranger/nnn/vim/emacs without a problem, which adds so much more value to the tool as a shell plugin.
I wouldn't say it isn't bash related, though. It has first-class support for bash, and the fact that it is able to support other shells at the same time shouldn't diminish its value as a bash plugin.

We may have include tool like this in the past. I dont know (who wants to check?).

I just checked the Command Line Productivity section. Almost all of the tools are written in other languages:

aliases is written in Rust, supports only bash right now but mentions zsh under future plans
bashhub is written in Python, supports bash+zsh
commacd is written in POSIX shell, supports bash+zsh
hstr is written in C, supports bash+zsh
qfc is written in Python, supports bash+zsh

The only tools that actually are written in Bash were:

bashmarks
has
sshrc (although the link is broken)

Would it be more relevant on awesome-cli-apps or awesome-cli? Does awesome-zsh or awesome-fish included it?

Would it be more relevant on awesome-cli-apps or awesome-cli?

zoxide is, at the end of the day, a shell plugin. It needs to be set up on your shell. It comes with a CLI, but that CLI is basically used to set up the shell plugin.

Did awesome-zsh or awesome-fish include it?

It's included in awesome-zsh. awesome-fish didn't include it because they require every tool to be written in Fish rather than for Fish.

I am fine with merging stuff not written in bash if it is relevant to bash in some way.

If you're trying to curate a list of high-quality Bash plugins, I don't see why you would want to exclude a plugin simply because it supports other shells.
Consider the starship project. I use it on Bash, because it's the best prompt I could find for Bash. Does it matter to me, as a user, that it's not written in Bash, or that it works on zsh as well? Absolutely not.
I haven't understood why you say zoxide isn't relevant to Bash. It's a Bash plugin. The fact that it's also a zsh plugin doesn't change the fact that it's a Bash plugin.
Finally, 5/8 projects I checked in the list were not written in Bash. Would you want to remove those from the README, for no fault other than the fact that they support other shells?

The list was not maintained much and thus did not have real contribution guidelines. I am in favor of adopting the philosophy of the awesome-fish list. However, I also could envision some middle ground where we have an category of enhancements that are not "pure" bash.

authors: Knusper ajeetdsouza aloisdg

repo: awesome-lists/awesome-bash


text:
Not support MV3 native ES background worker

Blocked by https://github.com/w3c/ServiceWorker/issues/1356, otherwise, we need to emit import statements which is not easy in a webpack bundle.

I think that maybe it already works with this, regardless if manifest version:

Yep: https://github.com/pixiebrix/pixiebrix-extension/pull/7472

I'm unsure if your comment relates to this issue, but I'll write down what I recently found as a memo.
Firstly, Chrome supports service workers with native ES modules now, you need to write your manifest like this:
  "background": {
    "service_worker": "background.worker.js",
    "type": "module"
  },

Then the service worker can use import or export statements, not importScripts.
Currently, we use JSONP-style (the default of webpack) to load chunks, this way works well, so even if this issue is not resolved, this plugin is ok to use.
// JSONP-style chunk format
"use strict";
(globalThis["webpackChunk"] = globalThis["webpackChunk"] || []).push(...)

As an ES Module enthusiast, I hope we can support ES Module as the chunk format, and also as the chunk loading format.
// ES Module chunk format
export const id = 232;
export const ids = [232];
export const modules = {

/***/ 232:
/***/ (() => {
/***/ })

};

If the chunk format becomes ESM, the only way to load it is static import or dynamic import.
Dynamic import already works to load JSONP-style chunks in the content script (https://github.com/awesome-webextension/webpack-target-webextension#content-script), the problem is dynamic import is not allowed in an ES Module service worker even if the dynamic import is called before first event loop ends. This requires me to emit not dynamic import, but static imports. Webpack now only supports dynamic import (see __webpack_require__.f.j if you're interested) those chunks.
This becomes harder, but not impossible. I think it needs a lot of time to figure out how to make this work. I can emit import statements at the top level, but I need to know their file name, but unluck, file names are generated from a runtime function (__webpack_require__.u) and it's very hard to do it in the compile time.
Since everything works well today, this is not very urgent to fix.

Then the service worker can use import or export statements, not importScripts.

That's very good to know. Parcel forced me to use that syntax but never investigated it. I'll start using it in webpack too because importScript breaks "Pause on uncaught errors" in the dev tools, because the debugger pauses on importScript, regardless of the actual position and source maps.

dynamic import

That didn't seem to work for me 🤷♂ I got the same error as before

Changing it to import statement fixed it.

So technically now I'm using a native ES background worker in webpack-target-webextension. This issue is fixed? Maybe it just needs some documentation?

Native ES service worker works, dynamic import does not.
While using this plugin, compiled ES modules (including dynamic import) work after bundling, loading by importScritps. Native ES service worker does not work with this plugin currently (the screenshot you gave).

I just took another look of this. This is not possible until there is ES Module support in content script.

e is ES Module support in content script

I think you meant "in background workers" right?

e is ES Module support in content script

I think you meant "in background workers" right?

No, to share chunks between the background and content script, they must use the format that both environments support. Now ES Module is only supported in the background worker and not supported in the content script, so there is no meaning in investigating this.

What do you mean? I definitely am using both static and dynamic ESM in content scripts:
https://robwu.nl/crxviewer/?crx=https%3A%2F%2Fchromewebstore.google.com%2Fdetail%2Frefined-github%2Fhlepfoohegkhhmjieoechaddaejaokhf%3Fhl%3Den
See content-script.js.
There are some tricks though:

you need to use import(chrome.runtime.getURL('actual-content-script.js')) in your entry point in order to later be able to use import statements
all JS files need to be in web_accessible_resources

hmm wait you're right, an extra file will be enough to load ESM in content script.

authors: Jack-Works fregante


text:
Improve GInputBox's behaviour with a long title

Before:

After:

A solid improvement :+1:

authors: awesomekling rburchell

repo: awesomekling/serenity


text:
Where do I add permissions when using amplify-cli?

** Which Category is your question related to? **
API/Function
** What AWS Services are you utilizing? **
Lambda/DynamoDB
** Provide additional details e.g. code snippets **
I have a lambda that gathers data from DynamoDB that i created using the cli.
When I execute it, I get a permission error:
User: blah is not authorized to perform: dynamodb:DescribeTable
This is easy enough to fix, I added the DynamoDB permissions required through the console but this feels bad.  I could edit the cloudformation template, adding the permissions there before pushing the changes up.  But the template is generated, that also feels bad.
Any idea where I should be doing this?  I can't find any documentation around it.

@bwobbones You could probably modify the Cloudformation file in amplify/backend/function<funcition-name>/cloudformation-file.json file to add the perminssions.

Thanks @kaustavghosh06, do you know if that file will be overwritten if I push changes?

@gregevari What do you mean by if push changes? I don't beleive this file is changed dynamically by the CLI after it's created.

@kaustavghosh06 pushing with amplify push.  I think you cover my question though, thanks!

authors: bwobbones gregevari kaustavghosh06

repo: aws-amplify/amplify-cli


text:
add-graphql-datasource is not showing list of secrets

Describe the bug
No keys available to select
To Reproduce
Steps to reproduce the behavior:

Create new project, amplify init, amplify add api
Create RDS instance (Aurora PostgreSQL compatible with PostgreSQL 10.7, serverless)
Execute amplify api add-graphql-datasource, try to complete quiz.
See error

Expected behavior
Being able to use RDS as datasource.
Screenshots
If I just press enter, this happens

Additional context

OS: Windows 10
amplify -v: 3.10.0

@TrueLecter
Did you select the "serverless" mode when you create the RDS database?
It is required to select the "serverless" mode as stated in our document.

Yes. All clusters were created with serverless template. Role shown as serverless in console as well.

@TrueLecter
Did you create the password for the "master" user? and then use the query editor to create a database in the newly created cluster?
I will send a PR to guard against those scenarios, and print out error messages.

Ok, so I was able to finally connect to database in Query Editor. However, not I'm getting next issue:

I was also getting an error, stating that there was no database named . After that I created database with name same as username and started receiving issue regarding unrecognized configuration parameter.

This seems to still be the case (CLI ver. 4.12.0). Is there any info on when amplify will support Postgres?
(in fact, I did not find any documentation that it was not supported beyond this issue...)

Is there any update, please?

authors: Genkilabs TrueLecter UnleashedMind stefanotauriello


text:
chore: use correct commit when publishing git tag

Description of changes
This changes the prerelease scripts to make sure we are publishing tags and releases linked to the correct commit SHA.

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@5ea0b9a). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev   #10677   +/-   ##
======================================
  Coverage       ?   47.37%
======================================
  Files          ?      669
  Lines          ?    33066
  Branches       ?     6673
======================================
  Hits           ?    15665
  Misses         ?    15723
  Partials       ?     1678

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

authors: codecov-commenter danielleadams


text:
Cloning repository fails trying to read the cache

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d31qkmp0h12ar6
AWS Region
us-west-2
Amplify Hosting feature
Build settings, Monorepo
Describe the bug
I'm using a Monorepo configuration for this application and try to make the deploy using a custom amplify.yml file.
Currently the main issue is that the checkout job fails with the following 2 relevant warnings:
2023-01-06T12:25:44.542Z [INFO]: # Retrieving environment cache...
2023-01-06T12:25:44.612Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}

2023-01-06T12:26:00.536Z [INFO]: # Retrieving cache...
2023-01-06T12:26:00.536Z [INFO]: # Retrieved cache
2023-01-06T12:26:40.089Z [ERROR]: !!! TypeError: m.indexOf is not a function
2023-01-06T12:26:40.168Z [INFO]: # Starting environment caching...
2023-01-06T12:26:40.168Z [INFO]: # Environment caching completed

After that the build step fails.
I've tested the following configuration changes:

Node 14 & 16
Overwrite the amplify CLI version (multiple versions and the same as we are using locally)
Removed the caches from the amplify.yml file declaration
Removed the test step
Reconnect the repository multiple times (as is the indication that appears on the interface)

Expected behavior
We expect to see the checkout to work as expected as the indications are warnings and not errors.
Reproduction steps
This happens when triggering a build or pushing a new change from gitlab integration.
Build Settings
No response
Log output

2023-01-06T12:25:44.414Z [INFO]: # Switching to commit: 4a5a6f7d9966f36b966e056f491b0948b4bea32a
2023-01-06T12:25:44.458Z [INFO]: Agent pid 159
2023-01-06T12:25:44.458Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
                                 Note: switching to '4a5a6f7d9966f36b966e056f491b0948b4bea32a'.
                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at 4a5a6f7d9 Testing configuration
2023-01-06T12:25:44.530Z [INFO]: Successfully cleaned up Git credentials
2023-01-06T12:25:44.531Z [INFO]: # Checking for Git submodules at: /codebuild/output/src955501831/src/creator-web/.gitmodules
2023-01-06T12:25:44.542Z [INFO]: # Retrieving environment cache...
2023-01-06T12:25:44.612Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2023-01-06T12:25:44.612Z [INFO]: ---- Setting Up SSM Secrets ----
2023-01-06T12:25:44.612Z [INFO]: SSM params {"Path":"/amplify/d35m6bal8x8kl9/citesting/","WithDecryption":true}
2023-01-06T12:25:44.666Z [INFO]: # Defaulting to Node version 16
2023-01-06T12:25:54.411Z [INFO]: # Node version 16 is available for installation
2023-01-06T12:25:54.502Z [INFO]: # Installing Node version 16
2023-01-06T12:26:00.450Z [INFO]: # Now using Node version 16
2023-01-06T12:26:00.531Z [INFO]: No live updates for this build run
2023-01-06T12:26:00.536Z [INFO]: # Retrieving cache...
2023-01-06T12:26:00.536Z [INFO]: # Retrieved cache
2023-01-06T12:26:40.089Z [ERROR]: !!! TypeError: m.indexOf is not a function
2023-01-06T12:26:40.168Z [INFO]: # Starting environment caching...
2023-01-06T12:26:40.168Z [INFO]: # Environment caching completed
Terminating logging...

Additional information
This application is configured on the amplify console to use other application backend.

Hi @esteban-serfe 👋🏽 thanks for raising this issue. It's possible that there could be an issue with your amplify.yml file and we are misrepresenting the error. Could you please share the file so we can make sure it is configured correctly?

Hi @hloriana
This is the amplify.yml file from the last build.
The issue appears within the students application, not the creators.
version: 1
applications:
  - appRoot: creators
    backend:
      phases:
        preBuild:
          commands:
            # Run the lint over the lambdas functions > check #97113"
            #- npm i
            #- npm run lint:lambdas
            - if [[ ! -v ENV ]]; then export ENV=${USER_BRANCH}; fi;
            - if [[ ! -v ENV && -z "$ENV" ]]; then export ENV=${AWS_BRANCH}; fi
            - echo "Using $ENV as the Backend environment"
            #- whereis jq
            #- yum update && yum install -y jq
            #- aws cloudformation wait stack-update-complete --stack-name $(amplify env get --name $ENV --json | jq '.awscloudformation.StackId')
        build:
          commands:
            - amplifyPush --simple
    frontend:
      phases:
        preBuild:
          commands:
            - nvm use $VERSION_NODE_14
            - export NODE_OPTIONS=\"--max-old-space-size=8192\"
            #- npm ci --no-audit
            #- echo "=== Running Lint to validate it works as expected ==="
            #- "npm run lint"
            - npm i --no-audit --production
        build:
          commands:
            - npm run build
      artifacts:
        baseDirectory: build
        files:
          - "**/*"
      cache:
        paths:
          - node_modules/**/*
    test:
      artifacts:
        baseDirectory: cypress
        configFilePath: "**/mochawesome.json"
        files:
          - "**/*.png"
          - "**/*.mp4"
          - "report/mochawesome-report/**/*"
      phases:
        preTest:
          commands:
            - echo "=== Install cypress reporters and friends ==="
            - npm install --no-audit wait-on pm2 mocha mochawesome mochawesome-merge mochawesome-report-generator
            - echo '=== Configure the environment data sample ==='
            - 'echo "{ \"CYPRESS_TEST_USER_CREATOR\": \"${CYPRESS_TEST_USER_CREATOR}\", \"CYPRESS_TEST_PASS_CREATOR\": \"${CYPRESS_TEST_PASS_CREATOR}\" }" > cypress.env.json'
            - npx pm2 start npm -- start
            - npx wait-on http://localhost:3000/
        test:
          commands:
            - 'npx cypress run --reporter mochawesome --reporter-options "reportDir=cypress/report/mochawesome-report,overwrite=false,html=false,json=true,timestamp=mmddyyyy_HHMMss" --config video=false'
        postTest:
          commands:
            - echo "=== Generate tests output by merging ==="
            - "npx mochawesome-merge cypress/report/mochawesome-report/mochawesome*.json > cypress/report/mochawesome.json"
            - "npx pm2 kill"
  - appRoot: students/everprep-students
    backend:
      phases:
        build:
          commands:
            # - set
            - true
    frontend:
      phases:
        preBuild:
          commands:
            - nvm use $VERSION_NODE_14
            - export NODE_OPTIONS=\"--max-old-space-size=4096\"
            - echo "=== Install dependencies ==="
            - npm ci --no-audit --production
            # - if [[ ! -v ENV ]]; then export ENV=${USER_BRANCH}; fi;
            # - if [[ ! -v ENV && -z "$ENV" ]]; then export ENV=${AWS_BRANCH}; fi
            # - echo "Using $ENV as the Backend environment"
            # - export AWSCLOUDFORMATIONCONFIG='{"configLevel":"project","accessKeyId":"$AWS_ACCESS_KEY_ID","secretAccessKey":"$AWS_SECRET_ACCESS_KEY","region":"$AWS_REGION"}'
            # - export AMPLIFY='{"envName":"$ENV","appId":"$AWS_APP_ID","defaultEditor":"code"}'
            # - export PROVIDERS='{"awscloudformation":$AWSCLOUDFORMATIONCONFIG}'
            # - export CODEGEN='{"generateCode":false,"generateDocs":false}'
            # - export REACTCONFIG='{"SourceDir":"src","DistributionDir":"build","BuildCommand":"npm run-script build","StartCommand":"npm run-script start"}'
            # - export FRONTEND='{"frontend":"javascript","framework":"react","config":$REACTCONFIG}'
            # - export PORT=3001
            # - amplify pull $ENV --yes --amplify ${AMPLIFY} --providers ${PROVIDERS} --frontend ${FRONTEND}
            # - test -f src/aws-exports.js
        build:
          commands:
            - npm run build
      artifacts:
        baseDirectory: build
        files:
          - "**/*"
      # cache:
      #   paths:
      #     - node_modules/**/*
    # test:
    #   artifacts:
    #     baseDirectory: cypress
    #     configFilePath: "**/mochawesome.json"
    #     files:
    #       - "**/*.png"
    #       - "**/*.mp4"
    #       - "report/mochawesome-report/**/*"
    #   phases:
    #     preTest:
    #       commands:
    #         - "npm install --no-audit wait-on pm2 mocha@5.2.0 mochawesome mochawesome-merge mochawesome-report-generator"
    #         - "npx pm2 start npm -- start"
    #         - "npx wait-on http://localhost:3001"
    #     test:
    #       commands:
    #         - 'npx cypress run --reporter mochawesome --reporter-options \"reportDir=cypress/report/mochawesome-report,overwrite=false,html=false,json=true,timestamp=mmddyyyy_HHMMss\" --config video=false'
    #     postTest:
    #       commands:
    #         - "npx pm2 kill"
    #         - "npx mochawesome-merge cypress/report/mochawesome-report/mochawesome*.json > cypress/report/mochawesome.json"

authors: esteban-serfe hloriana

repo: aws-amplify/amplify-hosting