Start push distance is wrong for all buttons

Overview
All hololens 2 buttons should begin to compress immediately as the finger tip touches the button surface. Currently, the finger needs to go at least half way through the button before the button begins to compress.
Steps to reproduce
In the editor, press a button and observe where the finger is when the button starts moving.

You can also observe this by looking at the press planes of the button (select button component then inspect in scene view. Ensure "Show Button Event Planes" is checked. Noticethat the start push distance is half way into the button:

Expected Behavior
The start push plane should be at the beginning of the button cage, the button should start moving as soon as the finger touches the cage.

@julenka Sorry, when I updated the buttons I just tested functionality and didn't look at finese also not realizing this was desired behavior.
For defaults for PressableButton, can we also review so they make more sense as starting point?
And is there any way to create an auto-place feature that sets the plane distance based on our "golden" ratios?

@Troy-Ferrell @julenka It seems like with the code updates, PressableButtonHoloLens2's Start Push distance cannot be 0. I tried adjusting the planes and ended up with the following values. Updated both HoloLens 2 buttons and Round buttons.

@cre8ivepark and @thalbern  is this done? If so, please close it.

@julenka, this is reported as fixed in #5577

Hi, I have a similar problem where if the button is pressed in far interaction mode and call an event that SetActive(false) the button (or a parent), the button will be stuck at the "half postition" mentionned above when re-enabled. Should I open a new bug report for this ?

Hi, I have a similar problem where if the button is pressed in far interaction mode and call an event that SetActive(false) the button (or a parent), the FrontPlate cover GameObject will be stuck at the "half postition" mentionned above when re-enabled. Should I open a new bug report for this ?

Hi @umaknow-manu thank you for reporting your issue. Yes this sounds like a different bug, please open a new issue. Ping @CDiaz-MS and @thalbern  for awareness.


Fix/re export third party deps in macro

this PR is to fix issue #79,
we re-export once_cell, arrow and parquet in tonbo's lib.rs
and replace all direct usage of deps with ::tonbo prefix.
but, there is still one direct usage of third party dep tokio

which is fine for now, in my mind, cuz tonbo currently depends on tokio runtime. it means that user cannot use tonbo without tokio dep

Close #79

You should probably re-export tonbo_macro as well?

You should probably re-export tonbo_macro as well?

no needed, cuz we export the proc macro directly in lib tonbo, users can use tonbo::tonbo_record and does not need to install tonbo_macro as dep
https://github.com/tonbo-io/tonbo/blob/80a4a5e4a124f261c4c26caba52d78dda2e38130/src/lib.rs#L149

The generated code of tonbo_record includes tonbo_macro::KeyAttributes.

The generated code of tonbo_record contains tonbo_macro::KeyAttributes.

you're right
https://github.com/tonbo-io/tonbo/blob/80a4a5e4a124f261c4c26caba52d78dda2e38130/tonbo_macro/src/lib.rs#L769C1-L773C2
but the KeyAttributes is now a placehoder, not sure what's it for? probably @ethe can explains it for us.
I will raise an issue to export macro KeyAtrributes directily.

BTW, I personally don't like generating #[derive(Debug, PartialEq, Eq, Clone)] for users. It's implicit and might produce confusion to users.

I have no idea why those Trait are required.


[firebase_messaging] Error while calling method messaging#getToken & Messaging#subscribeToTopic

Hello World,
I am new to flutter and writing the function for receiving notification on both iOS and Android platform. I achieved this function and it was working well but these days I got an issue:
FLTFirebaseMessaging: An error occurred while calling method Messaging#getToken, errorOrNil => {
}
FLTFirebaseMessaging: An error occurred while calling method Messaging#subscribeToTopic, errorOrNil => {
}
[VERBOSE-2:ui_dart_state.cc(209)] Unhandled Exception: [firebase_messaging/unknown] An unknown error has occurred.
#0      MethodChannelFirebaseMessaging.getToken (package:firebase_messaging_platform_interface/src/method_channel/method_channel_messaging.dart:229:7)
<asynchronous suspension>
[VERBOSE-2:ui_dart_state.cc(209)] Unhandled Exception: [firebase_messaging/unknown] An unknown error has occurred.
#0      MethodChannelFirebaseMessaging.subscribeToTopic (package:firebase_messaging_platform_interface/src/method_channel/method_channel_messaging.dart:371:7)
<asynchronous suspension>

This only happened on iOS platform (Android is working well), I have tried to find the reason so I rollback to previous commit and I can see this happened after I added Push Notification and Background Modes capabilities to Runner Target, but these two are the main cores for receiving notification on iOS platforms. :3. I also tried to remove these two capabilities, the error still exit, so it is very confusing.
Any suggestions would be appreciated!
Here is Flutter Doctor -v
[✓] Flutter (Channel stable, 2.8.1, on macOS 11.5.1 20G80 darwin-arm, locale en-AU)
    • Flutter version 2.8.1 at /Applications/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (5 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/bpc/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.63.2)
    • VS Code at /Users/bpc/Downloads/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

Here is the code
    //ios part permission
    FirebaseMessaging.instance.requestPermission().then((value) {
      print(value);});
    FirebaseMessaging.instance.getToken().then((token){
      print(token);});
    FirebaseMessaging.instance.getAPNSToken().then((APNStoken){
      print(APNStoken);});
  }

And I am using
firebase_messaging: ^11.2.5

@FortySL
Did you use dart-only initialization for firebase or was it manual installation ?
If the latter, can you check if you are using wrong api key of firebase in the GoogleServices-info.plist ?

Thx for your reply.
I am not so clear about what is dart-only initialization and will do some searches tmr.
I tried to delete the current Googleservice-info and re download it, this issue was still there. But apart from this, other functions are working well like displaying products from firebase so I think the connection between my app and firebase is fine.
Again, thx for ur reply and suggestion

Thx for your reply.
I am not so clear about what is dart-only initialization and will do some searches tmr.
I tried to delete the current Googleservice-info and re download it, this issue was still there. But apart from this, other functions are working well like displaying products from firebase so I think the connection between my app and firebase is fine.
Again, thx for ur reply and suggestion

@darshankawar
Thx for your reply.
I am not so clear about what is dart-only initialization and will do some searches tmr.
I tried to delete the current Googleservice-info and re download it, this issue was still there. But apart from this, other functions are working well like displaying products from firebase so I think the connection between my app and firebase is fine.
Again, thx for ur reply and suggestion

@FortySL

I am not so clear about what is dart-only initialization

This is a new CLI tool introduced by flutterfire plugin owner with which you can initialize firebase through this tool. You can read more about it here: https://firebase.flutter.dev/docs/cli/
If you have done it with traditional way, then make sure you have properly setup and configured for iOS, as it may be a bit tricky to set up messaging properly. See this documentation and confirm if you have correct setup : https://firebase.flutter.dev/docs/messaging/overview#4-apple-integration

@darshankawar
Thx for this, I think the configuration should be correct cuz it was working. This error happened after I merged several branches with different flutter version. I tried to use flutter clean and cache clean, but they do not work.
I am thinking is there any way that can help me to clean firebase related setting or configuration inside my iOS folder, so I can redo this part.
I tried to delete the iOS folder inside my project and then use flutter create . to generate a new one, and this error has been removed, but in this case, App store regard my app as a new app rather than the continues of the previous one.
FLTFirebaseMessaging: An error occurred while calling method Messaging#getToken, errorOrNil => {
}
FLTFirebaseMessaging: An error occurred while calling method Messaging#subscribeToTopic, errorOrNil => {
}
flutter: null
[VERBOSE-2:ui_dart_state.cc(209)] Unhandled Exception: [firebase_messaging/unknown] An unknown error has occurred.
#0      MethodChannelFirebaseMessaging.getToken (package:firebase_messaging_platform_interface/src/method_channel/method_channel_messaging.dart:229:7)

[VERBOSE-2:ui_dart_state.cc(209)] Unhandled Exception: [firebase_messaging/unknown] An unknown error has occurred.
#0      MethodChannelFirebaseMessaging.subscribeToTopic (package:firebase_messaging_platform_interface/src/method_channel/method_channel_messaging.dart:371:7)

This error happened after I merged several branches with different flutter version. I tried to use flutter clean and cache clean, but they do not work.

It seems your entire setup / config is messed up. Can you try with a fresh project from scratch with new firebase project and config according to the document and see if you still get same error ?


Travis CI build is failing: The platform of the target ios (iOS 5.0) is not compatible with Expecta (0.3.2) which has a minimum requirement of iOS 5.1.1 - OS X 10.7

$ pod update
Update all pods
Analyzing dependencies
CocoaPods 0.36.0.beta.2 is available.
To update use: sudo gem install cocoapods --pre
[!] This is a test version we'd love you to try.
For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.
Fetching podspec for SDWebImage from ../
[!] The platform of the target ios (iOS 5.0) is not compatible with Expecta (0.3.2) which has a minimum requirement of iOS 5.1.1 - OS X 10.7

Travis CI builds were fixed


E21: Cannot make changes, 'modifiable' is off

When I try to go to the error(inconsistency with pep-8) in my code after running vim-flake8, by pressing enter.
E21: Cannot make changes, 'modifiable' is off
How do I resolve this?

It has something to do with quickfix stealing focus.
I'm trying to solve the same problem :\


[Request] File extension txt and caption

its not a bug
but since kohya standart extension is caption may it would be nice to load txt or caption

Implemented in 2.1.0


Kopernicus not updating to 1.4.5-4 from 1.4.5-3

See title. Kopernicus isn't being updated for some reason....
Also it says on the top of your page after I logged in:
The password you provided has been reported as compromised due to re-use of that password on another service by you or someone else. GitHub has not been compromised directly. To increase your security, please change your password as soon as possible.
Read our documentation on safer password practices. See our blog for more details.
Has my password really been compromised and being used by hackers and I need to change my passwords everywhere? Or is this just your site's dumb way of saying I need a stronger password that has a symbol in it...?
CKAN Version:
KSP Version:
Operating System:
Have you made any manual changes to your GameData folder (i.e., not via CKAN)?
Affected mods and mod versions:
Problem
What steps did you take in CKAN?
What did you expect to happen?
What happened instead?
Screenshots:

CKAN error codes (if applicable):

It is being updated. The previous version was indexed 5 hours ago. Please be patient.
As for the password stuff, the CKAN team has nothing to do with that. Try GitHub:
https://github.com/contact


playwright-test: init at 1.31.1

Adds "playwright test" command.
Description of changes
Raw dump of a package working in an out of tree project, still needs some polish
Fixes  https://github.com/NixOS/nixpkgs/issues/217693
I've tried buildNpmPackage but doesn't seem ready yet to handle this kind of package.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/running-playwright-tests/25655/9

I built the PR and run the resulting binary in a (unfortunately private) repository with Playwright tests written in Javascript:
/nix/store/8ck7islaxlgffm584kf91rq05ygigima-_at_playwright_slash_test-1.31.1/bin/playwright test

gave me errors like
Error: Playwright Test did not expect test() to be called here.
Most common reasons include:
- You are calling test() in a configuration file.
- You are calling test() in a file that is imported by the configuration file.
- You have two different versions of @playwright/test. This usually happens
  when one of the dependencies in your package.json depends on @playwright/test.

   at mono/mono.spec.js:7

   5 |     await page.goto('https://url.domain');
   6 |     await expect(page).toHaveURL(/auth\/realms/);
>  7 |     await page.locator('#username').fill(process.env.STUDENT_USERNAME ?? '');
     | ^
   8 |     await page.locator('#password').fill(process.env.STUDENT_PASSWORD ?? '');
   9 |     await page.locator('button[type="submit"]').click()
  10 |     await expect(page).toHaveURL(/mono/);

    at TestTypeImpl._currentSuite (/home/user/dev/e2e-tests-ng/node_modules/@playwright/test/lib/common/testType.js:70:13)
    at TestTypeImpl._createTest (/home/user/dev/e2e-tests-ng/node_modules/@playwright/test/lib/common/testType.js:76:24)
    at /home/user/dev/e2e-tests-ng/node_modules/@playwright/test/lib/common/transform.js:226:12
    at Object.<anonymous> (/home/user/dev/e2e-tests-ng/tests/mono/mono.spec.js:7:1)

You have two different versions of @playwright/test.

Ha I have seen that error at some point. I was told that javascript has a peculiar singleton system based on path that even symlinks could throw off. This package is a port of a package we use internally with success and that shouldn't suffer from the problem.
Why is it that the path is a local one ? /home/user/dev/e2e-tests-ng/node_modules/@playwright/test/lib/common/testType.js:76:24
it should come from the nix store
So maybe it's a plawyright error. Have you tried clearning up NODE_PATH in case it does load an alternative playwright ?

My NODE_PATH is NODE_PATH=/nix/store/njh6p007ymbmcgas5l7sqqxfmm394zx1-nodejs-18.15.0/lib/node_modules.
Setting it to an empty string didn't help. 🤔
Only when I was manually removing node_modules/@playwright/ (note that it will installed again by npm install) I managed to use the test successfully in Chromium!
But not in Firefox, there I got:
browserType.launch: Executable doesn't exist at /nix/store/dkpc25ivrhx19d5v9px74qnsafn65hlr-playwright-browsers-chromium/firefox-1378/firefox/firefox

I don't know where it gets the path from, /nix/store/dkpc25ivrhx19d5v9px74qnsafn65hlr-playwright-browsers-chromium is the path for the chromium browser. Any chance to make it work in firefox too?
My shell.nix is:
{ pkgs ? import <nixpkgs> {} }:
  pkgs.mkShell {
    buildInputs = [
      pkgs.nodejs-18_x
      pkgs.playwright
    ];

    PLAYWRIGHT_BROWSERS_PATH="${pkgs.playwright-driver.browsers}";
  }

And is there a chance to make it work inside VS-Code with the Playwright extension (where you are supposed to do the actual development of the tests)?

And is there a chance to make it work inside VS-Code with the Playwright extension (where you are supposed to do the actual development of the tests)?

Add this to your vscode settings
"playwright.env": {
    "PLAYWRIGHT_BROWSERS_PATH": "/nix/store/mlyamflq8icq0lwfircr03aiba0dbzg3-chromium-playwright",
    "PLAYWRIGHT_SKIP_VALIDATE_HOST_REQUIREMENTS": 1
  },

Unfortunately u have to hard code the nix store path, maybe there's a way to read it from env var in vscode

Hm, I tried to do that, but vs-code doesn't even seem to detect my JS tests any more. It wants to show python tests. 😅

awesome, maybe we can integrate your repository as part of the testsuite ?
Seems like it works for the only supported browser aka chrome:
Running 3 tests using 3 workers
  1) [webkit] › example.spec.js:4:1 › has title ────────────────────────────────────────────────────

    browserType.launch: Executable doesn't exist at /nix/store/fpibn255xp5iazcdnghbf06qgbacrqv3-playwright-browsers-chromium/webkit-1792/pw_run.sh
    ╔═════════════════════════════════════════════════════════════════════════╗
    ║ Looks like Playwright Test or Playwright was just installed or updated. ║
    ║ Please run the following command to download new browsers:              ║
    ║                                                                         ║
    ║     npx playwright install                                              ║
    ║                                                                         ║
    ║ <3 Playwright Team                                                      ║
    ╚═════════════════════════════════════════════════════════════════════════╝

  2) [firefox] › example.spec.js:4:1 › has title ───────────────────────────────────────────────────

    browserType.launch: Executable doesn't exist at /nix/store/fpibn255xp5iazcdnghbf06qgbacrqv3-playwright-browsers-chromium/firefox-1378/firefox/firefox
    ╔═════════════════════════════════════════════════════════════════════════╗
    ║ Looks like Playwright Test or Playwright was just installed or updated. ║
    ║ Please run the following command to download new browsers:              ║
    ║                                                                         ║
    ║     npx playwright install                                              ║
    ║                                                                         ║
    ║ <3 Playwright Team                                                      ║
    ╚═════════════════════════════════════════════════════════════════════════╝

  2 failed
    [firefox] › example.spec.js:4:1 › has title ────────────────────────────────────────────────────
    [webkit] › example.spec.js:4:1 › has title ─────────────────────────────────────────────────────
  1 passed (6.0s)

  Serving HTML report at http://localhost:9323. Press Ctrl+C to quit.

I am tempted to merge as is and discuss the test afterwards. There might even be a native testsuite that could be run

awesome, maybe we can integrate your repository as part of the testsuite ?

fine with me! 🚀

Let's go !

@teto, do you maybe know why there is no --ui parameter, as in playwright test --ui? (see https://playwright.dev/docs/test-cli)

nope sry no idea, documentation is not clear to me either.

@pbek That was added in 1.32.0.

Ah, I see, thank you :)
So we'll need to wait for @toto. 😅

@teto We're also keen on a newer version at work. What would be the process of updating? Do we need to think about the driver/browsers as well?

I think you mean @teto not @toto ;)

I am sure you could sell @toto for a shitton of money, if only to https://en.wikipedia.org/wiki/Toto_Ltd.
@samhh Absolutely, the playwright-driver version must match the package version ! we could add a warning to check that
the playwright python package has this script to update the driver that I might have broken ?!
https://github.com/teto/nixpkgs/blob/3beded5aa4b3e20e510b2eea292c3f49fbe44341/pkgs/development/python-modules/playwright/update.sh#L24
I dont know if nix-update can replace that script (probably not) but I guess the last lines should be moved to pkgs/development/web/playwright/
I have spent my plawyright FOSS credits but I am happy to review PRs if you wanna update the package.
pkgs/development/web/playwright-test/wrapped.nix was written manually but depends on the driver version. Updating the driver and running pkgs/development/web/playwright-test $ node2nix -i package.json (from memory)  should work

I think you mean @teto not @toto ;)

I'm so sorry! 😆

@samhh pr with latest playwright version https://github.com/NixOS/nixpkgs/pull/235914


Lazy chunk Webpack config adjustments

This prevents initial chunks (most importantly polyfills) from being split.  It also allows the creation of an overall application async common chunk for small common modules if the total is greater than 30Kb.

This fixes https://github.com/angular/angular-cli/issues/10353.


[AUTO-CHERRYPICK] [CHERRYPICK] Backport azurelinux-sysinfo to 2.0 - branch main

This is an auto-generated pull request to cherry-pick commit 5c2eed7955e4b9a7a5931299031dc1dfcfefd13a to main. Original PR: #8812

Original fast-track commit reverted, needs update before applying to main.

Moved to #9117.


swift inout parameter

It seems, that if I pass a variable managed by Realm to a function as an inout parameter I get this error:
*** Terminating app due to uncaught exception 'RLMException', reason: 'Attempting to modify object outside of a write transaction - call beginWriteTransaction on an RLMRealm instance first.'
What is going on here? Is passing something as an inout parameter implicitly modify it? I have commented out the whole body of the function and I still get the same error. It goes away only when I replace the Realm-managed variable with a regular one when calling the function.

Yes, inout modifies the thing passed in that spot. It doesn't pass a reference to that value; instead at the end of the function it assigns the new value of the local variable back to the thing passed in, even if it has not changed. This means that the setter of a property which is passed as an inout argument will always get called.

Is there a good way to wrap it in a realm.write {} ?

I'd suggest you do something like this:
realm.beginWrite()
let didModify = maybeModifyRealmObjectPassedAsInout(myRealmObject)
if didModify {
  try realm.commitWrite()
} else {
  realm.cancelWrite()
}

Where maybeModifyRealmObjectPassedAsInout returns whether or not the object was modified.


Remove JBoss logging from dependencies

I don't think we need it and it might be the cause of #3901
Fixes #3901

Proposed Changes

Remove JBoss logging from dependencies

Release Note

Docs

/test upgrade-tests

/cc @matzew @Cali0707


[build][trunk] Add triple lib to config, turn off shared build

- Upstream has introduced a triple lib subdir for target libraries
  (requires another search path in the cfg)
- Building with -DBUILD_SHARED_LIBS=ON is causing compiler so's
  to appears as dependencies in libomptarget.so

Turning BUILD_SHARED_LIBS=OFF will unfortunately increase the size of the installation significantly:
-DBUILD_SHARED_LIBS=OFF
[r5 /work1/omp-nightly/build/rocm/trunk_19.0-0]$ du -sh .
6.4G    .
-DBUILD_SHARED_LIBS=ON
[r5 ~]$ du -sh /COD/LATEST/trunk/
854M    /COD/LATEST/trunk/

Seems to be a recent change in the libomptarget build causing the LLVM so's to get listed as dependencies:
[r5 ~]$ ldd /COD/LATEST/trunk/lib/x86_64-unknown-linux-gnu/libomptarget.so
linux-vdso.so.1 (0x00007ffdd52ca000)
libomp.so => /COD/LATEST/trunk/lib/x86_64-unknown-linux-gnu/libomp.so (0x00007f60d1d84000)
libLLVMObject.so.19.0git => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f60d1d49000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f60d1d3f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f60d1bf0000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f60d1bea000)
libLLVMSupport.so.19.0git => not found
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f60d1a06000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f60d19eb000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f60d17f9000)
/lib64/ld-linux-x86-64.so.2 (0x00007f60d1e9b000)

Applied Michael's suggestion to add symlinks from x86_64-unknown-linux-gnu to lib which allows us to build shared again.  All dependent LLVM libs in libomptarget.so currently need to be found in the same directory as the lib.

Michael tracked problem down to this patch:
https://github.com/llvm/llvm-project/pull/83624
and heard from Joseph "The intended solution is to require users to set up LD_LIBRARY_PATH according and have ASO make -frlib-add-rpath true by default."

With this patch to trunk/build_project.sh all smoke-fort tests are once again passing with trunk-atd and build size is back down to ~850MB (vs. 6.4GB):
[r5 /COD/2024-03-13a]$ du -sh trunk-atd_19.0-0
853M    trunk-atd_19.0-0


Fixed 2D playground Notebook

Resolves #100 to work with the prompt processor pipeline! Sample image generated:

Sure, I've removed those lines and some other dead code in the notebook.


transcription initiation-coupled chromatin remodeling (GO:0045815) parentage query

CC @colinlog @pgaudet
transcription initiation-coupled chromatin remodeling (GO:0045815)
Should this have a parent to transcription initiation, or was it an explicit decision not to add this?
Note that
transcription elongation-coupled chromatin remodeling (GO:0140673)
Does have a parent to
transcription elongation by RNA polymerase II (GO:0006368)
But maybe there is a reason for the difference.
Apologies if I asked about this before.

I feel like this was brought up before. As far as I recall, this occurs before initiation, so we cannot add a relation 'part of initiation of transcription'
to be confirmed with @colinlog

OK, I think my problem is that I annotated SAGA by IC to "transcription elongation-coupled chromatin remodeling" but SAGA isn't chromatin remodelling and it should only be annotated to
"positive regulation of transcription initiation by RNA polymerase II (GO:0060261)"
like mediator.
@colinlog is that correct?

Chromatin remodelling comes in two forms: nucleosomal histone post
translational modification GO:0140993 and ATP-dependent nucleosome
remodelling. SAGA belongs to the former as it has the GCN5 histone
acetylase. So, I would include it in remodelling ( GO:0140993). This is in
addition to the GO:0060261 annotation.
On Tue, Oct 3, 2023 at 9:13 AM Val Wood @.***> wrote:

OK, I think my problem is that I annotated SAGA by IC to "transcription
elongation-coupled chromatin remodeling" but SAGA isn't chromatin
remodelling and it should only be annotated to
"positive regulation of transcription initiation by RNA polymerase II
(GO:0060261)"
like mediator.
@colinlog https://github.com/colinlog is that correct?
—
Reply to this email directly, view it on GitHub
https://github.com/geneontology/go-ontology/issues/26161#issuecomment-1744340049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALZVLKF4V7UBLAMGBMDMDNTX5O3KNAVCNFSM6AAAAAA46UQGSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBUGM2DAMBUHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Created a new ticket requesting the same parentage
https://github.com/geneontology/go-ontology/issues/26319
So this ticket here is now a duplicate.

I  also wanted to record that some of my community who work on chromatin-related processes   have objected to  SAGA being classed as a chromatin remodeller. They say that most of the community would refer to SAGA as  "chromatin re-organization" but not "chromatin remodelling"  which is restricted to the ATP-dependent remodelers.
I tried  explain that as a process we define chromatin remodelling more broadly as"A dynamic process of chromatin reorganization resulting in changes to chromatin structure." and it is not in GO restricted to processes involving ATP-dependent chromatin remodeler activity (GO:0140658)
but I wonder if this use might be quite confusing for many in the field?

What do you suggest?
A BP is 'coordinated biological module'; that can not be limited to any activity using ATP. We can add comments and clarify the definitions, but I dont think we can make ATP-dependent activities a BP.

I agree! In the proposed view "chromatin remodelling" is analogous to "chromatin modification"  (this was how they described it   "modifiers and remodelers".  This would mean we would not have "remodelling" in the process ontology, it would be a related synonym of the remodelling activities, and the chromatin remodelling BP terms would be renamed "reorganization" and could have e remodelling as a narrow synonym.
I don't know how prevalent this stricter view of "chrome atin remodelling"  is,  so we. can keep as is for now. I wanted to report so that if it is raised again we know what the issue is and that there is a solution.
For what it's worth, Wikipedia used the broader view of remodelling
https://en.wikipedia.org/wiki/Chromatin_remodeling so I think we can ignore for now and reconsider if we get more negative feedback on this issue.

Yes Val, as described in the wiki page you refer to and in the literature, it is consensual to consider both nucleosomal histone (de)modification and ATP-dependent remodelling (slide, dismantle, replace a histone with another histone variant) as 'chromatin remodelling' activities, which is part of the chromatin organisation BP. Hence SAGA should have both a coTF (MF) and a remodelling activity (MF) annotations as well as the transcription intiation BP and the chromatin remdelling/chromatin organisation BPs.
Remodeling is the activity term that the field uses, rather than organisation. There are often many such activities that work in cascades to perform the process remodelling. Perhaps it is better to call the process 'chromatin organisation' than chromatin remodelling? To me these are broad synonyms when talking about the process.
The view that only dbTFs and their coTFs are part of the regulation branch is also consensual I believe.

OK,
and this  was one of my main remaining questions to answer:

The view that only dbTFs and their coTFs are part of the regulation branch is also consensual I believe.

So I will open PAINT tickets for the violations.
CC @marcfeuermann


Update documentation with API endpoints

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/246
Originally created by @tayloramurphy on 2022-04-25 19:37:36

At a minimum the readme, but something on the Hub would be good too.

View 1 previous comment from the original issue on GitLab


Investigate occasional high CPU usage of vault clients

It seems like sometimes, the vault clients' CPU usage increases up to 100% without any apparent reason. This leads to the vault client becoming unresponsive and not handling bridge requests anymore.
What we know:

This issue happens across all Amplitude and Pendulum vaults at around the same time.
In the monitoring, we can see that the CPU usage increases from 50% to 100% within 45 minutes.
Memory and disk usage are not increasing during this time window.
After the periodic restart, the CPU usage goes back to ~50%
There are no messages appearing in the logs (at least on 'INFO' log level).
The Spacewalk-related metrics are unavailable for this timeframe which indicates that the whole client becomes unresponsive

@zoveress to facilitate the investigation of this ticket, can we change the log level of one of the Spacewalk clients to 'DEBUG'? Doesn't matter which one on Amplitude or Pendulum as they all seem to have the same issue at the same time (at least when it occurs for which we don't know the reason yet).

@pendulum-chain/product this is a bug that can lead to the vault client being unresponsive and only able to bridge after the next periodic restart. It does not occur frequently and we first have to monitor the instances when this is happening.

From the #DevOps Incidents, it started as far back as Sept 17, 2023.
extra: Memory Usage High alerts happened on Sept 21, 2023

@annatekl anything blocking this from being moved to Ready?

moved @vadaynujra

@b-yap please don't forget to assign yourself to tickets once you start working on them so that others don't. 😬

@ebma noted.
Question; as this has something to do with the vaults, should we move this ticket over there?

Over where? It's already in the spacewalk repository or would you prefer to have it elsewhere? 😅

ah nevermind, I got confused with the zenhub "Pendulum" icon  :weary:


Update instructions for stty error in windows

Closes #68

The stackage server is being too much unreliable :angry:

/azp run


Reachability: Avoid dispatching the same method on the same interface.

When we find a regular call to some (virtual) method C.m, we have to reach the implementations of m in all the instantiated subclasses of C. We do it immediately for the already known subclasses, and maintain a log for subclasses that will be found to be instantiated later.
Previously, we did this dispatch for every call site of C.m. If M methods call C.m and C has N instantiated subclasses, this would result in M*N resolutions. This was not strictly unnecessary work, since the from argument is different in each case. However, this makes the analysis non-linear, which is bad.
One might argue that M*N never gets arbitrarily big for any given C.m, so this is not so bad. But there is at least one case where M and N typically each grow linearly with the size of the codebase: the apply method of FunctionN traits.
Therefore, this commit changes the approach to make it linear, without losing from information. We introduce one indirection in the from-chain: a FromDispatch(C, m) represents a dispatch from a virtual call of C.m. The first time we call C.m, we actually do the resolutions and use FromDispatch(C, m) as from. We also store the previous from in the dispatchCalledFrom of C.m. For subsequent calls, we enrich dispatchCalledFrom but we do not redo the resolutions.
The indirection with FromDispatch allows to recover all the callers of an actual method, without requiring O(M*N) amount of information.
The generated .js files are unchanged.

On the test suite, this reduces the time spent in
"Compute reachability" by approximately 17% (from around 5.2s to around 4.3s on my machine).

For an unlinkable call to Await.result, a typical log output is now:
Referring to non-existent class java.util.concurrent.locks.AbstractQueuedSynchronizer
  called from scala.concurrent.impl.Promise$CompletionLatch
  called from scala.concurrent.impl.Promise$DefaultPromise.tryAwait(scala.concurrent.duration.Duration)boolean
  called from scala.concurrent.impl.Promise$DefaultPromise.ready(scala.concurrent.duration.Duration,scala.concurrent.CanAwait)scala.concurrent.impl.Promise$DefaultPromise
  called from scala.concurrent.impl.Promise$DefaultPromise.result(scala.concurrent.duration.Duration,scala.concurrent.CanAwait)java.lang.Object
  dispatched from scala.concurrent.Awaitable.result(scala.concurrent.duration.Duration,scala.concurrent.CanAwait)java.lang.Object
  called from private scala.concurrent.Await$.$anonfun$result$1(scala.concurrent.Awaitable,scala.concurrent.duration.Duration)java.lang.Object
  called from scala.concurrent.Await$.result(scala.concurrent.Awaitable,scala.concurrent.duration.Duration)java.lang.Object
  called from helloworld.HelloWorld$.main([java.lang.String)void
  called from static helloworld.HelloWorld.main([java.lang.String)void
  called from core module module initializers

Updated.


ui: Link from statement diagnostics to details page

PR: https://github.com/cockroachdb/cockroach/pull/46923
From release notes:

Added links to statement details from the Statement Diagnostics history page. [#46923][#46923] {% comment %}doc{% endcomment %}

Advanced debug pages aren't documented.


Make JWTSecuredRequest pass opts to Request

This makes it possible to pass { logRequest: false } to a JWTSecuredRequest to disable the request logging added in f715d282a6edb649e5479b54870fe1a728de6443

Coverage remained the same at 100.0% when pulling ae569d42b3476c7e18ef43c2367ce16ff33b67a4 on fix_options_jwt_request into 047163332cbeb3d812a7bea3adc7a34f8c81fa73 on master.


feat: definitive profile creation on healthcrm service

Review Checklist

Summary*

[ ] fix: Bug fix for Add the items tackled here as checklists
[x] feat: Completed task
[ ] chore: Incomplete task

[ ] test: Sub-task 1

Structure*

[ ] The Pull Request has a proper title that conforms to our MR title standards
[ ] The Pull Request has one commit, and if there are more than one, they should be squashed
[ ] The commit should have a proper title and a short description
[ ] The commit must be signed off
[ ] Unused imports are not present
[ ] Dead code is not present
[ ] Ensure dry running library to confirm changes

Tests

[ ] Proper and high quality unit, integration and acceptance(if applicable) tests have been written
[ ] The coverage threshold should not be lowered

Sign off*

[ ] All comments have been resolved by the reviewers
[ ] Approved by Czar {replace_with_czar_name}
[ ] Signed off by second reviewer {replace_with_name}
[ ] Ensure all checks are done before merging :warning:
[ ] All PRs needs to be signed before merging :warning:

N/B:

Add a checklist if more than one item is done.
Add screenshots and/or images where necessary
Indicate any breakages caused in the UI :exclamation:
Where necessary, indicate which issue the Pull Request solves (Closes #)
Any new files are updated in the folder structure in the README

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 20 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-5.1%) to 76.25%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

healthcrm.go
0
20
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-5.1%

Covered Lines:
244

Relevant Lines:
320

💛  - Coveralls


Tracking nvbench benchmark results

Is there any interest in tracking the results from nvbench?
I'm considering adding an adapter for nvbench to my continuous benchmarking tool, Bencher: https://github.com/bencherdev/bencher
And I figured I should check in on whether there is already a preferred way to do this.

Hey @epompeii, thanks for reaching out!
I hadn't heard of bencher before, but it looks great! A continuous benchmarking tool is something we've often talked about wanting to build, but have never got around to it.
I'd say we're definitely interested! What all is required?

Awesome!
I'm happy to help where I can to get things set up. My email is<EMAIL_ADDRESS>or you are welcome to hop on our discord: https://discord.gg/yGEsdUh7R4
Please, feel free to ask me any questions or give candid feedback!

Hey @jrhemstad,
I just wanted to follow up, how are the self-hosted Action runners are coming along?


Continuous function pulses

What is the expected enhancement?
A ContinuousFunctionalPulse will wrap a function that outputs a continuous complex scalar value as a function of duration. When wrapped with a Sampler (#1935) strategy it will output a DiscreteFunctionalPulse.

Closed by #2043.

Closed in favor of samplers (#1935).


Updated go version to 1.19 in jx-changelog

Signed-off-by: PratikforCoding<EMAIL_ADDRESS>

related to jenkins-x/jx#8433

/assign @ankitm123

/ok-to-test

/ok-to-test


Escape search text for use in Regex

Implementation notes
After seeing an alert in Sentry, this will fix the issue.
Add new package to do the escape and use in the highlight filter
Checklist

[ ] Has the branch been rebased to develop?
[ ] Automated tests (Any of the following when applicable: Unit, Functional or Acceptance)
[ ] Manual compatibility testing (Browsers: Chrome, Firefox, IE11, Safari)

discontinued closing


Last web-ifc implementation is not compatible with the last web-ifc-three implementation

Hi there,
If I try to build current implementation of web-ifc-three (i.e 0.0.122) with the lastest implementation of web-ifc it throws the following errors,

So web-ifc-three it has to be adapted with the latest changes of web-ifc, because some signatures were changed since web-ifc 0.0.36

@agviegas , I thing I've achieved make compatible last implementation web-ifc with last implementation of web-ifc-three. I'll make PR in a while.

@agviegas , I think it has no sense do a PR that makes compatibles to the last web-ifc, because people will still use web-ifc from npm and to build web-ifc, copy files is not easy task. But anyway, tell me if you are interested or not still in do the PR

So there have been a few API changes to support multi-schema in the new web-ifc. My suggestion is wait for us to get the new version of web-ifc done then adapt web-ifc-three

So there have been a few API changes to support multi-schema in the new web-ifc. My suggestion is wait for us to get the new version of web-ifc done then adapt web-ifc-three

I agree with that @beachtom

Agreed! Both web-ifc-three and web-ifc-viewer need a big update / clean up, so this might be a good opportunity.

I opened IFCjs/web-ifc-viewer#188 a few minutes ago and discovered this one afterwards. I guess both are intermingled. This comment to cross-reference both.


Acer

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 6314cab8-5f54-827b-d906-46f67dd0d0cf
Document Details.txt

Version Independent ID: fe69a922-b5b5-001b-5ef9-c0f44a693beb

Content: Sources tool overview - Microsoft Edge Development

Content Source: microsoft-edge/devtools-guide-chromium/sources/index.md

Product: microsoft-edge

Technology: devtools

GitHub Login: @MSEdgeTeam

Microsoft Alias: msedgedevrel

Closing as incomplete.


Add Word Count to Frontmatter Metadata

Problem

I am interested in word and character counts for specific files, but not all files. The file explorer becomes quite busy when word counts are listed next to file and folder titles. I also want the word counts etc. to be portable and stay with the file if I open the file in another program.
Idea

I'd like to disable the word counts in the file explorer and instead view the word counts inside the frontmatter of each file.

Ok. Thank you for clarifying!


fix: definition of gcnv conda enviroment for mamba>=1.3 (#452)

fix: definition of gcnv conda enviroment for mamba>=1.3 (#452)
Leaving out the 'default::' seems to work, see my comment on the issue

coverage: 85.904%. remained the same when pulling af3fce4e9b7f63cf5aa7233cc9e91e2b6313cb19 on 452-gcnv-yaml-mamba-12-disallows-mixing-of-conda-forge-and-defaults-channel into e394e8cd4bd76eef4725bbaa9ff7711ab5aa9dcc on main.


Add the ability to watch fields of a replication controller

With this change clients can watch on a specific controller's status.replicas without polling pods/rcs. This is needed for https://github.com/GoogleCloudPlatform/kubernetes/issues/5745 and https://github.com/GoogleCloudPlatform/kubernetes/issues/5884.

Adhoc and unittest testing done, e2e still running.
@lavalamp

PTAL

LGTM - shippable looks like a flake

e2e done

Looking at travis failure, which seems to be for a different apiversion

This should be good to go, the failures were flakes and didn't repro locally or on the rerun

All checks are green so merging.


Ensure that an error at agent startup time is properly logged

Description
Ensure that an error at agent startup time is properly logged.
closes #2777
Self Check:

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in 2dabfb506cbf3717faf718c0f606f1a94e74a86c

Processing #2831.

Processing #2832.


example workflow not loading at all

MooreAnimateAnyone_DDIM.json
press "Refresh".
Your current root directory is: E:\COMFYUI\ComfyUI
Error. No naistyles.csv found. Put your naistyles.csv in the custom_nodes/ComfyUI_NAI-mod/CSV directory of ComfyUI. Then press "Refresh".
Your current root directory is: E:\COMFYUI\ComfyUI
Error. No naistyles.csv found. Put your naistyles.csv in the custom_nodes/ComfyUI_NAI-mod/CSV directory of ComfyUI. Then press "Refresh".
Your current root directory is: E:\COMFYUI\ComfyUI
Error. No naistyles.csv found. Put your naistyles.csv in the custom_nodes/ComfyUI_NAI-mod/CSV directory of ComfyUI. Then press "Refresh".
Your current root directory is: E:\COMFYUI\ComfyUI
Error. No naistyles.csv found. Put your naistyles.csv in the custom_nodes/ComfyUI_NAI-mod/CSV directory of ComfyUI. Then press "Refresh".
Your current root directory is: E:\COMFYUI\ComfyUI
Error. No naistyles.csv found. Put your naistyles.csv in the custom_nodes/ComfyUI_NAI-mod/CSV directory of ComfyUI. Then press "Refresh".
Your current root directory is: E:\COMFYUI\ComfyUI

me too.HELP!HELP!HELP!HELP!

I restart it can fix the error


Wrapper Element Required

Given the following where <foo-bar /> is a custom component from Glimmer, the SSR'd content will be removed when Glimmer replaces <foo-bar/>.

SSR'd content

    <foo-bar />

When you wrap the WC everything works

SSR'd content

       <foo-bar />

Try changing <foo-bar /> to <foo-bar></foo-bar>. Custom elements cannot be self-closing[1][2]. They do funny things if you try.

Man the platform is rough.


fix scrolling on media feed

seems to only show a part of the scrollable area
may have to do with the image/bounding box of the internal element

is working fine now, I think it was just an issue of me not holding the scroll button properly


Fix mingw (cross) build issues in vcpkg_configure_make

What does your PR fix?
Fixes resource compilation on mingw. (Similar to #17246, but a) also sets RC, and b) without the unrelated changes to OpenSSL.)
Fixes the incorrect passing of ${prefix} to the shell where it would be expanded to an empty string before reaching configure (i.e. actual: --bindir=/tools/gettext/bin, expected: --bindir=${prefix}/tools/gettext/bin etc., logged in config.log).

Which triplets are supported/not supported? Have you updated the CI baseline?
all (but made for mingw), no
(Tested with libiconv:x64-mingw-static on Ubuntu 18.04.)

Does your PR follow the maintainer guide?
yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
not needed

Waiting for https://github.com/microsoft/vcpkg/pull/18579 merge to resolve the regression.

/azp run

Thanks!


Vertical timeline component

Looking at wanting to introduce a vertical timeline component that has mobile responsiveness baked in, looking at using React Vertical Timeline for this.
I want to export wrappers that stylise these components in a consistent way

The interface can be quite messy, and is very firm on wanting to use CSSProperties. This is breaking my convention of using CVA and Tailwind. But the solution is workable, breaking that convention is acceptable in this case as there's no real alternative library that preforms how I want and the effort required to custom implement isn't worth it


Update sphere-node-utils dependency

Updated the dependency, mainly to have the SFTP fix. Please bump the version after the pull request is merged.

Coverage remained the same at 93.434% when pulling fa2b1aa6f582bed6a8715eefd9b16ce6552a73bd on use-fixed-sftp-client into d72aa78f14d852fba7cbe014546c0814daab2a74 on master.


Crashing 1.5.6 and 1.5.7

Since 1.5.6 went main and 1.5.7 released TpacTool crashes when trying to open the files.

Fixed in 0.3.0

Fixed in 0.3.0


Database restore error

Hello,
I installed it with apt-get on Ubuntu 16.04
development restore-from staging gives me the following error:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 27247  100 27247    0     0   3109      0  0:00:08  0:00:08 --:--:--  7992
sh: 1: Syntax error: "&&" unexpected
sh: 1: cannot open %=: No such file

Is there any way I can debug it or check out logs to know what is the error exactly for?
I use rbenv. I tried it with Ruby 2.1.1p76, 2.2.2p95

@tannakartikey do you have your database defined with an ERB file and a dynamic value?

@geoffharcourt sorry did not get you about ERB file.
I have used Figaro for ENV variables. Variables are used in the config/database.yml. Please find it below:
default: &default
  adapter: postgresql
  pool: 5
  timeout: 5000

production:
  <<: *default
  database: db/production.sqlite3

development:
  adapter: postgresql
  host: <IP_ADDRESS>
  database: <%= ENV["CURRENTS_DB_NAME"] %>
  username: <%= ENV["CURRENTS_PSQL_USERNAME"] %>
  password: <%= ENV["CURRENTS_PSQL_PASSWORD"] %>

test:
  adapter: postgresql
  host: <IP_ADDRESS>
  database: <%= ENV["CURRENTS_DB_NAME"] %>
  username: <%= ENV["CURRENTS_PSQL_USERNAME"] %>
  password: <%= ENV["CURRENTS_PSQL_PASSWORD"] %>

Hi @tannakartikey we don't currently support dynamic database names via environment variables (your database config is using ERB-style variables).

Ok. Thank you.
Can I contribute that feature? What are the ups/downs for having the feature?

You are very welcome to make a PR?
The requirements for this to work in acceptance is that whatever solution for bundling the ERB-parsing (you'll need that to parse the database.yml file since that's not valid YAML until the ERB is processed) and the environment variable-loading needs to work when the gem gets repackaged for distribution with Homebrew and APT. We experimented with ERB support previously but had to remove it when we ran into issues with packaging.

Closing this out, but open to PRs that are distributable via package managers.

@geoffharcourt we're interested in this as well. Do you happen to remember any details about what went wrong with the package managers so we have an idea of where to start if we come around to offering a PR for this?

@bbugh Traveling Ruby is no longer supported and has a version of Bundler that causes permissions issues when installed through Homebrew. If you want to try tackling a PR that includes ERB, I would enthusiastically support this.
Any solution we implement would have to work through a Homebrew install (and likely apt), so keep those in mind if you decide to take this on.

Got it, thanks for the fast reply. We made a local patch that has resolved the issue for now, but I imagine it's not portable. We'll see if this works or if we can submit a PR for this project.
--- backup.rb	2018-02-08 09:23:48.000000000 -0600
+++ backup.rb	2018-02-08 09:23:55.000000000 -0600
@@ -1,4 +1,6 @@
 require "etc"
+require 'erb'
+require 'rails'

 module Parity
   class Backup
@@ -104,7 +106,7 @@
     end

     def database_yaml_file
-      IO.read(DATABASE_YML_RELATIVE_PATH)
+      ERB.new(IO.read(DATABASE_YML_RELATIVE_PATH)).result(binding)
     end
   end
 end

@bbugh possibly relevant: https://github.com/thoughtbot/homebrew-formulae/blob/master/Formula/parity.rb
I went through a couple iterations of this before giving up. I'd be pretty excited to see this make it back into the utility.


MAISTRA-1457: Pull in changes from upstream 1.4.8

This big number of commits and no actual change is a result of merging upstream 1.4 branch into ours (there are many commits and reverts). Thus our fork keeps in sync with upstream.

No, I didn’t but if you look at the changes tab the only actual changes are
a bump in Envoy. All others were reverted or I fixed the merge conflict -
mostly our changes in those tests.
On Fri, May 29, 2020 at 7:24 PM Dmitri Dolguikh<EMAIL_ADDRESS>wrote:

@dmitri-d commented on this pull request.
Did you run tests after the merge? There are changes in
SniVerifierFilterTest, which could potentially break it under gcc.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Maistra/proxy/pull/22#pullrequestreview-421346372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA6WP6GOLSZYCSRC4K7Z5LRUA73HANCNFSM4NOFSHLA
.

--
Jonh Wendell
https://bani.com.br


Added @error support for sass

Added support for @error linting for sasss.
Related to Microsft/vscode#22735

The build error that travis is returning seems to be the same error I receive on my local machine when I attempt to build master. Perhaps some one can help me discover a way to add these changes without breaking the build.

Thanks, great PR. It will go in the April release.


Addon not starting.  FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Version: 2023.02.0
Hardware : RPi 3 B+
Description:
Concagudo addon fails to start and returns the following error in the log
<--- Last few GCs --->
[94:0x7316c440]    28507 ms: Scavenge 34.1 (37.5) -> 34.0 (37.5) MB, 4.3 / 0.0 ms  (average mu = 0.886, current mu = 0.272) allocation failure;
[94:0x7316c440]    28526 ms: Scavenge 34.1 (37.5) -> 34.0 (38.0) MB, 6.3 / 0.0 ms  (average mu = 0.886, current mu = 0.272) allocation failure;
[94:0x7316c440]    28863 ms: Mark-sweep 34.4 (38.0) -> 34.0 (38.2) MB, 297.1 / 0.0 ms  (average mu = 0.793, current mu = 0.388) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
./valetudo.sh: line 54:    94 Aborted                 (core dumped) valetudo
After that, the service stopped

Solved with the low-mem images. Maybe a new addon version for low mem devices? @txitxo0

Solved with the low-mem images. Maybe a new addon version for low mem devices? @txitxo0

Finally we just added more memory to this lowmem devices in all release, I guess we don't need an extra release for that


[identity] Rework expires_on logic for managed identity credentials

Packages impacted by this PR
@azure/identity
Issues associated with this PR
#22722
#23202
Describe the problem that is addressed by this PR
The 2019 api-version of managed identity switched from using a string-encoded datetime to instead using a string-encoded number of seconds from the epoch for expires_on. The logic for how we parse expires_on was spread across every managed credential type, making this hard to reason about and incorporating a lot of assumptions about what these responses look like per credential.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
I basically copied the .NET solution which is to dynamically detect what kind of expires_on we are being given instead of assuming anything. This seems far simpler than our previous approach.
Are there test cases added in this PR? (If not, why?)
Updated existing tests.

API change check
API changes are not detected in this pull request.

/azp run js - identity - tests

There were some live test failures, but I couldn't tell if it's related at first glance. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1854033&view=logs&j=77fbbdd4-440d-501f-3a7b-78ae114f7a46&t=37372121-aa18-588d-f377-a54dbf764ccf (MS INTERNAL link)

@jeremymeng I'm seeing a lot of "Failed to replace the request. This might be expected if you're running multiple sendCredentialRequests() calls." which also show up locally... but everything passes locally

/azp run js - identity - tests


navbar is not sticky

Ain this page, the navbar is not sticky  means while we scrolling down the page .
the navbar gonna hiden. so, i want to make the navar while scrolling down the navar attched on the top.
https://github.com/user-attachments/assets/7eead800-a2f3-4186-83ae-b906506e8fe1
@Rizwan102003 :  PLEASE ASSIGN ME .I WANT WORK ON THAT

@dipeshkumar799 I have assigned this issue to you.I suggest using separate files for your work as we have a lot of contributions here. @SaurabhS55 @pulkitpathak99 please put the labels here.


<IP_ADDRESS>:53: server misbehaving

For a specific domain (roboflow.com) I get the above error. I tried with different resolver endpoints: Cloudflare DoT, Cloudflare DoH, quad9 DoT - But the error always stays the same: lookup roboflow.com on <IP_ADDRESS>:53: server misbehaving.
When I try another domain (e.g. google.com or even media.roboflow.com), it works fine.
Is this an bug in this library? Or an unsupported feature the DNS server uses?
Maybe it is because of the "Comment" attribute, or the missing "Authority" attribute? (The domain has no AAAA records)
$ curl -s -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=roboflow.com&type=AAAA" | jq
..
  "Comment": [
    "EDE(6): DNSSEC Bogus (proof of non-existence of roboflow.com. AAAA)"
  ]
}

Can you please have a look? Thank you!
package main

import (
	"fmt"
	"net"

	dns "github.com/ncruces/go-dns"
)

func main() {
	resolver, err := dns.NewDoTResolver("cloudflare-dns.com", dns.DoTAddresses("<IP_ADDRESS>", "<IP_ADDRESS>"))
	// resolver, err := dns.NewDoTResolver("dns.quad9.net")
	// resolver, err := dns.NewDoHResolver("https://cloudflare-dns.com/dns-query")
	if err != nil {
		panic(err)
	}
	net.DefaultResolver = resolver

	host := "roboflow.com"
	// host := "google.com"  // works
	l, err := net.LookupHost(host)
	if err != nil {
		panic(err)
	}
	fmt.Printf("IPs: %v\n", l)
}

Yes, it's because of DNSSEC.
I'm setting resolver.StrictErrors to true which in retrospect may be a bad default.
You can change it yourself, just add resolver.StrictErrors = false before setting the net.DefaultResolver.


make test complains about missing MCU header

Hi
'make test' fails while complaining about unknown MCU. For compilation -mmcu=msp430x1611 is given, but this (generic) cpu type is not listed in msp430.h and leads to the warning.

make test
(cd tests && make)
make[1]: Entering directory `.../src/mspsim/tests'
msp430-gcc -I. -DWITH_ASCII -Wall -mmcu=msp430x1611 -g -Os -DAUTOSTART_ENABLE -c cputest.c -o cputest.co
In file included from cputest.c:44:0:
/usr/lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430.h:813:2: warning: #warning Unable to identify and include MCU header, use -mmcu=MCU [-Wcpp]

using this software:
mspsim last version from git
gcc version 4.6.3 20120301 (mspgcc LTS 20120406 unpatched) (GCC)
Ubuntu 14.04 LTS

changing MCU to msp430f1611 in tests/Makefile helped in my case.

Can you make a pull-request?


switched to use transient and fix bug in mintMoney

[x] switched to use transient when reading or writing private data
https://github.com/LayerXcom/hyperledger-fabric-security-dvp/issues/1

[x] when minting money, get the current balance and increment the amount to mint
https://github.com/LayerXcom/hyperledger-fabric-security-dvp/issues/3

👀

LGTM


Fix FFI bindings for libffi >= 3.4

Resolves #11802
https://github.com/libffi/libffi/pull/540 changed the memory layout of ffi_closure (LibFFI::Closure) between libffi 3.3 and 3.4 (which equates to libffi7 and libffi8 packages).
When linking against libffi 3.4 the constant FFI_TRAMPOLINE_SIZE is 32 instead of 24 (16 instead of 12 on 32-bit).

SemanticVersion doesn't handle version strings without the patch part :(
Error: Not a semantic version: "3.3"

Confirmed, this patch fixed the segfault issue on Ubuntu 22.04 for me.
It would be nice to have this in the 1.5 release.

SemanticVersion doesn't handle version strings without the patch part :(

It's true, I get "3.4-rc1" on my end, and it fails to compile. I think we'll need to do some preprocessing before passing that to compare_versions.

SemanticVersion doesn't handle version strings without the patch part :(

It's true, I get "3.4-rc1" on my end, and it fails to compile. I think we'll need to do some preprocessing before passing that to compare_versions.

@asterite I'd rather refactor SemanticVersion to handle such cases, since they're not uncommon.

But then it's not a semantic version 🤔

Oh, that's a good note. So LibFFI::Closure is actually just used within this method and even there it's really just a handle.
https://github.com/crystal-lang/crystal/blob/8eb1413aa8d750d41b3ccfb9ee48cd2a757be169/src/compiler/crystal/ffi/closure.cr#L5-L15
I don't think there should be any harm from over-allocating a couple of bytes. Since we really only need the memory size and not the internal layout, we could just use the biggest size (from 3.4) always.

Right. In that case I would also make Closure an opaque type.

We still need to hard-code the value of sizeof(LibFFI::Closure) somewhere. The official documentation suggests the size argument to ffi_closure_alloc only needs to be "sufficient to hold a ffi_closure object", so over-allocation is probably fine.

Fixed on my arch linux
 ╰─ $ cr i
icr:1:0> Time.local
=> 2022-07-06 02:54:45.607922055 +08:00 Asia/Shanghai
icr:2:0>
 ╰─ $ cr version
Crystal 1.5.0-dev [e9d223a67] (2022-07-05)

LLVM: 14.0.6
Default target: x86_64-pc-linux-gnu
``


Debug build error: no_std + FnvIndexMap (linker err: rust_eh_personality)

TL,DR, A debug build using FNVIndexMap fails linking with missing rust_eh_personality, but release build works.
Apologies if this is user error, I am new to no_std.
Environment

See details
$ rustc --version --verbose
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7

$ cargo --version --verbose
cargo 1.81.0 (2dbb1af80 2024-08-20)
release: 1.81.0
commit-hash: 2dbb1af80a2914475ba76827a312e29cedfa6b2f
commit-date: 2024-08-20
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.8.0-DEV (sys:0.4.73+curl-8.8.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Linux Mint 22.0.0 (wilma) [64-bit]

$ rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /home/caleb/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu (default)
nightly-2024-06-08-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu
1.73.0-x86_64-unknown-linux-gnu
1.80.1-x86_64-unknown-linux-gnu
1.80-x86_64-unknown-linux-gnu

installed targets for active toolchain
--------------------------------------

x86_64-unknown-linux-gnu
x86_64-unknown-linux-musl

active toolchain
----------------

stable-x86_64-unknown-linux-gnu (default)
rustc 1.81.0 (eeb90cda1 2024-09-04)

$ uname -a
Linux caleb-ThinkPad-X13-Gen-1 6.8.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 13 13:35:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Reproducer
Here is a tiny project:
Cargo.toml:
[package]
name = "heapless_debug_err"
version = "0.1.0"
edition = "2021"

[dependencies]
heapless = "0.8.0"
libc = { version = "0.2.148", default-features = false }

[profile.dev]
panic = "abort"
debug-assertions = false

[profile.release]
panic = "abort"

[!NOTE]
default-features = false is required to disable linking to std

main.rs:
#![no_std]
#![no_main]

use core::panic::PanicInfo;
use libc;

#[panic_handler]
fn panic(_info: &PanicInfo) -> ! {
    loop {}
}

#[no_mangle]
pub extern "C" fn main(_argc: isize, _argv: *const *const u8) -> isize {
    let mut v = heapless::Vec::<i32, 16>::new();
    v.push(1).unwrap();

    let mut h = heapless::FnvIndexMap::<i32, i32, 16>::new();
    h.insert(1, 2).unwrap();
    0
}

Build in release mode is fine:
$ cargo build --release
warning: unused import: `libc`
 --> src/main.rs:5:5
  |
5 | use libc;
  |     ^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: `heapless_debug_err` (bin "heapless_debug_err") generated 1 warning (run `cargo fix --bin "heapless_debug_err"` to apply 1 suggestion)
    Finished `release` profile [optimized] target(s) in 0.00s

[!NOTE]
Removing the libc import from main.rs breaks it - it will complain about the entrypoint not being found.

Build in debug mode fails.  This is the linker error:
  = note: /bin/ld: /home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-500f37ee5bcf0ffe.rlib(core-500f37ee5bcf0ffe.core.3cad2706d8bdcdc4-cgu.0.rcgu.o):(.data.DW.ref.rust_eh_personality[DW.ref.rust_eh_personality]+0x0): undefined reference to `rust_eh_personality'
          collect2: error: ld returned 1 exit status

See the full details from cargo build
$ cargo build
   Compiling heapless_debug_err v0.1.0 (/home/caleb/tmp/no_std_heapless/libc_print_how)
warning: unused import: `libc`
 --> src/main.rs:5:5
  |
5 | use libc;
  |     ^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error: linking with `cc` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/home/caleb/.modular/pkg/packages.modular.com_mojo/bin:/run/user/1000/fnm_multishells/45691_1726058239106/bin:/usr/local/sbin:/usr/local/bin:/home/caleb/.local/share/JetBrains/Toolbox/scripts/:/snap/bin:/home/caleb/go/bin:/usr/sbin:/home/caleb/Dropbox/Technical/codelibs/bin:/home/caleb/bin:/home/caleb/.cargo/bin:/home/caleb/.local/bin:/home/caleb/Downloads/zig-linux-x86_64-0.12.0:/bin:/usr/bin" VSLANG="1033" "cc" "-m64" "/tmp/rustcgoHT0r/symbols.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.103qnko1lohuvkimci0fd7g72.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.1mfnq4h650ety896dtrpo3e0p.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.1nqtj657kao438xyq70kqirmo.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.375t1g7ov8ily1i3ywelm0xvt.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.43o13xbntrfzp2zyp2epr9eod.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.4nv1v0pbeucefmivuvf4mhrsx.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.65apesuvfc1piaqeuivcqrn15.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.6c0f4mdpjijwbixka0s9l2s4i.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.6lebqev3orvw3j4ipox6ftibv.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.6p7l92m0wk5t6bmfmtzdkb7d4.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.6z7dzm2mrt6hhspnadyyri1xf.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.7a2991n0u41g4rg6btp4ti0va.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.7hbfh1d1s047grr47rgukotho.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.8oqrttr9rssx7gr6cwg12wkmb.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.8so8mqosyn0tvy5hnj9g1ku9l.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.9gfl301xa7po0lxeqey8da6j3.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.9rkp0grqz0ks6z6ovu4n2nyfy.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.ar8mdmmannklqyz3rmf2bw2ub.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.auhbm9uwrtb32xam9donklqn5.rcgu.o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef.b862efaqf6ajkags50mtv2haw.rcgu.o" "-Wl,--as-needed" "-L" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps" "-L" "/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/libheapless-c0cbae0f547a8105.rlib" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/libhash32-a0bd382e6ff2493a.rlib" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/libbyteorder-2df7e366e369b3b1.rlib" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/liblibc-99893e597621ca51.rlib" "/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_core-2a862c0b1c86f483.rlib" "/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-500f37ee5bcf0ffe.rlib" "/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-06dfbf1de02fde3b.rlib" "-Wl,-Bdynamic" "-lc" "-lm" "-lrt" "-lpthread" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/home/caleb/tmp/no_std_heapless/libc_print_how/target/debug/deps/heapless_debug_err-aef797243ee916ef" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs"
  = note: /bin/ld: /home/caleb/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-500f37ee5bcf0ffe.rlib(core-500f37ee5bcf0ffe.core.3cad2706d8bdcdc4-cgu.0.rcgu.o):(.data.DW.ref.rust_eh_personality[DW.ref.rust_eh_personality]+0x0): undefined reference to `rust_eh_personality'
          collect2: error: ld returned 1 exit status

  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#rustc-link-lib)

warning: `heapless_debug_err` (bin "heapless_debug_err") generated 1 warning
error: could not compile `heapless_debug_err` (bin "heapless_debug_err") due to 1 previous error; 1 warning emitted

Discussion
The issue happens with the FnvIndexMap, not with the Vec.  Commenting out the hashmap resolves it:
#![no_std]
#![no_main]

use core::panic::PanicInfo;
use libc;

#[panic_handler]
fn panic(_info: &PanicInfo) -> ! {
    loop {}
}

#[no_mangle]
pub extern "C" fn main(_argc: isize, _argv: *const *const u8) -> isize {
    let mut v = heapless::Vec::<i32, 16>::new();
    v.push(1).unwrap();

    // let mut h = heapless::FnvIndexMap::<i32, i32, 16>::new();
    // h.insert(1, 2).unwrap();
    0
}

$ cargo build
   Compiling heapless_debug_err v0.1.0 (/home/caleb/tmp/no_std_heapless/libc_print_how)
warning: unused import: `libc`
 --> src/main.rs:5:5
  |
5 | use libc;
  |     ^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: `heapless_debug_err` (bin "heapless_debug_err") generated 1 warning (run `cargo fix --bin "heapless_debug_err"` to apply 1 suggestion)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.17s

The complaint about rust_eh_personality is something I've seen before, in a different library that supports no_std. In that case, it turned out that a macro using format_args! was somehow causing a debug_assert to get compiled in.  Even though my crate specifes panic = "abort", nevertheless somehow the debug_assert was bringing in panic unwinding code. For that library, I could resolve the problem with debug-assertions = false, which is why I have that set here. However, with the heapless hashmap shown here it seems to be a different issue.
So my guess is that there is something in heapless::FnvIndexMap that is somehow including panic code but only in debug mode.

The issue here is that the stock libcore is built with panic=unwind.
If you want to stay on stable you could try bumping the opt level:
[profile.dev]
opt-level = 1
panic = "abort"
debug-assertions = false

[profile.release]
panic = "abort"

If you can use a nightly toolchain compile libcore yourself with panic=abort:
cargo +nightly -Zbuild-std build --target x86_64-unknown-linux-gnu

Related: https://github.com/rust-lang/rust/issues/56152

closing, not a bug in heapless as per the above comment.


Signin

Closes #6
Comments
Add an icon link to the signin page of Devise
Update routes with custom path
Modify css for header

👍


Example with import from google/protobuf types

E.g. if you want to use timestamps, it makes sense to
import "google/protobuf/timestamp.proto";

When as-proto processes this definition it produces AssemblyScript like this:
import { google } from "./google/protobuf/timestamp";

but there is no such source file to import from, at least that I have been able to find. The fact that the import is processed to something that looks sensible makes me think it is intentional, so I need an example to see how it is supposed to be used.

UPDATE: you have to include the Google proto sources on the command line when you run protoc, e.g:
protoc --plugin=protoc-gen-as=./node_modules/.bin/as-proto-gen --as_out=./protoc simple.proto google/protobuf/timestamp.proto

then you get a "google" directory generated with AssemblyScript in it. An example would still be useful.

To be honest, I didn't know about that. Thanks for all reported issues - this is really helpful! This library is still pretty new and it doesn't cover all cases.
Would you like to create a PR to add this to the README.md?


matrix tests to run on linux and windows

Closes #35

closing in favor of an incremental approach in #333


Expanded function return type for certain mapped types in compiled output causes index access error

Bug Report

🔎 Search Terms

index access function return compiled .d.ts expansion
🕗 Version & Regression Information

This is the behavior in every version I tried

⏯ Playground Link

Playground link with relevant code
💻 Code

type evaluate<t> = { [k in keyof t]: t[k] } & unknown

export type entryOf<o> = evaluate<
    { [k in keyof o]-?: [k, o[k] & ({} | null)] }[o extends readonly unknown[]
        ? keyof o & number
        : keyof o]
>

export type entriesOf<o extends object> = evaluate<entryOf<o>[]>

export const entriesOf = <o extends object>(o: o) =>
    Object.entries(o) as entriesOf<o>

🙁 Actual behavior

TS source has no errors, compiled .d.ts has errors
🙂 Expected behavior

Either TS source should have errors, or .d.ts should not have errors
Addendum
This resulted in a blocking issue for an ArkType user who wasn't able to enable skipLibCheck in their CI environment.
Though the repro conditions are somewhat specific, issues like this can cause big problems for library authors, as I don't think it is commonplace to check build output for errors after TSC is successful.
Although in this specific case a faulty return type expansion seems to be at fault, in general I'd love if the default on skipLibCheck could be revisited. As I understand based on a conversation with @Andarist, individual TSConfig settings like exactOptionalPropertyTypes can affect whether some dependency blocks your build if skipLibChecks is not manually enabled.
Perf considerations aside, while I understand how it could be useful to know if the types of one of your dependencies is doing something unexpected, there's no feasible way for libraries to avoid these types of problems without checking their types under multiple combinations of TSConfig settings. Even if in a case like this the root of the problem isn't config-specific, very often it's something like an index access in a generic that doesn't affect the computed type at all and could have been safely ignored by the end-user. The resulting issue caused for both the user and maintainer can be difficult to track down and address, whereas I'd question how often the average TS user with skipLibCheck defaulted is being alerted to useful problems (which I guess they're supposed to pass on to maintainers?).
The only path I can see to this being a reliable source of errors is if TS could load multiple TSConfigs simultaneously and apply per-directory settings so that dependencies had control over the rules that applied to their own types, but I assume that would be a massive undertaking. Barring that or a default change, maybe some gold standard for "check your types against this config, if they work here then they should work with any config" could be adopted by libraries hoping to avoid this (not sure whether this possible or some settings have mutually exclusive results).
EDIT: Just found https://github.com/microsoft/TypeScript/pull/49886, so maybe these is hope for the required subset to be included as part of the compilation if the performance issues can be mitigated. Though I'd still question whether skipLibChecks would be a net positive, I'd feel much better about it if I could include our config options in our .d.ts output👍

It seems that one of my open PRs already fixes this: https://github.com/microsoft/TypeScript/pull/54759 . I just pushed out this as an extra test case there


Sample console app won't build

The type or namespace name 'Salesforce' could not be found (are you missing a using directive or an assembly reference?)
This is after downloading from git, opening in VS2012, and restore/update the packages thru NuGet. References are there, packages appear to be downloaded...
Any thoughts as to why it would fail?

I have the same problem. VS displays below warning. I am using this package on project with .NET Framework 4.
Warning	27	The primary reference "Salesforce.Force" could not be resolved because it has an indirect dependency on the framework assembly "System.Text.Encoding, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0". To resolve this problem, either remove the reference "Salesforce.Force" or retarget your application to a framework version which contains "System.Text.Encoding, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".	Imprima.Connect.SalesForceREST

You are probably running issues with .Net 4.0 - since the API is using Async/Await , .Net 4.0 is not supported.
Switch to .net 4.5 and you should be able to build

@v50minasyan : the project is already set to 4.5. As seen in melih154's post, the issue is that the salesforce.Force and Salesforce.Common included in the repository still apparently are built off the 4.0 framework, at least indirectly: the newtonsoft & threading stuff all seems to be pointed at 4.0. if I go back to the master src, still get issues with different bits or packages pointed at the wrong framework. I've tried half a dozen times now to get everything lined out with no success.

Hi, I think the folder structure is a bit odd. I have an issue with build any sample ;)
There is no solution file(s) for the sample projects.  It could work just like that, but please note, that in the .csproj of the sample project the reference to the packages is like:
..\..\src\packages\
Because of this structure, the missing solution for sample project should be in the "\src" folder (you really want to re-use 'packages' folder?)
Moreover, the samples will not build, if first, you will not try to build the ForceToolkitForNET.sln because it will downolad packages to the \src\packages\ that are required
Once again - moreover - the sample projects contains a reference to  "\src\ForceToolkitForNET\bin\Debug\Salesforce.Force.dll" ?
Maybe that's another reason why it can't be find?
I really think that the sample projects should rebuild all possible and required dependencies.
The samples builds should work on clean git clone.

Agreed. And if they don't it's a regression. I'll mark this as a bug.

I've fixed the samples here. https://github.com/developerforce/Force.com-Toolkit-for-NET/tree/master/samples
I also included a build-samples.cmd script here to make it easier to ensure they're building.


Add bitcoin.rocks merchant link

Added a link to https://bitcoin.rocks/business so merchants can read more about the benefits of accepting sats.

@dergigi any chance to get this merged soon? It is a very simple change.


Updated use cases document with expanded and new use cases

cc: @csantanapr

@romankhar thanks for the doc updates your PR is now merged 7cfc638d03ba7c7aa0e5f0fc99deb00fe5c210ed


Fight against COVID

Your checklist for this pull request
Author name
Author: Swaraj

About your game
Kill the Covid virus that is trying to infect you!
How do you play your game?

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[ ] The image is in the /games/img directory.
[ ] The name of the image matches the name of your file.

Thanks for your PR!

Hi - I added a berserk mechanic and limited the default bullets available to the player.

Congratulations!  If you're a teenager, and you haven't already received a Sprig device, fill in this form to receive one!  Also, feel free to join the Hack Club's Slack #sprig channel and share your creation!


feat: exposed indexes to scope as dsIndexes

there are times when we need to know the entire array of filtered results of a table through the scope.
Currently we can get:

all non-filtered rows
all filtered rows for the current page

So I added the indexes so we can get:

all filtered rows for all pages

Thanks for contributing @mesqueeb, I've added some docs and also exposed dsIndexes through provides


Remove encryption toggle and allow always encryption

There is a temporary toggle to disable encryption for interop work. This will need to go away once we have made progress on the interop

@suhasHere , why is this needed for interop? Decimus is not meant for interop right now.


some changes 👉👈

I thinks these changes are good 👉👈

I thinks these changes are good

Hey! I already thought in adding this but I still think its not necessary, because the goal of this RPC its only to show off your stats like in Brawl Stars, in your profile page, and to have the same structure like the other RPCs that I made.


Order of mouseover options doesn't match Inbox.

The order of the hover-over links which appear over messages does not match what is expected in Inbox. I still have an Inbox tab open (who knows for how much longer), so I can show the comparison:
Inbox:

Inbox-in-Gmail:

I keep almost clicking the wrong thing and it's a bit jarring :).

I keep almost clicking the wrong thing and it's a bit jarring

That's a good point. Muscle memory is very powerful!

What are your thoughts on this. I found that I was primarily messing up when I wanted to click the Done button, this change should address that. i can't change the pin location though, since it's where the yellow pin icon appears, when an email is pinned.

@abasiri Makes sense to me. I think leaving the pin where it is is fine.
Unless you've already fixed this since your screenshot, it looks like there should be more spacing between the Done icon and the Pin.
What do you think, @digitalneoplasm ?

I agree, I think this is great! The Done button was also my primary concern! Thanks!


Generate a swarm joining secret if none is specified

The current behavior of docker swarm init is to set up a swarm that
has no secret for joining, and does not require manual acceptance for
workers. Since workers may sometimes receive sensitive data such as pull
credentials, it makes sense to harden the defaults.
This change makes docker swarm init generate a random secret if none
is provided, and print it to the terminal. This secret will be needed to
join workers or managers to the swarm. In addition to improving access
control to the cluster, this setup removes an avenue for
denial-of-service attacks, since the secret is necessary to even create
an entry in the node list.
docker swarm init --secret "" will set up a swarm without a secret,
matching the old behavior. docker swarm update --secret "" removes the
automatically generated secret after docker swarm init.
Closes #23785
cc @diogomonica @aluzzardi @tonistiigi @dnephin

Note that this PR does not change the defaults for auto-acceptance. So while a secret will be required in all cases, under default settings, a node can't join as a manager without approval, even though it presents the secret. It will still show up as a pending node, which needs to be accepted with docker node accept on a manager.

cc @sfsmithcha

Updated to made docker swarm init show a docker swarm join command that can be used to join the new swarm.

@dnephin: Updated to address the comments, PTAL.

Design LGTM

Thanks LGTM

@aaronlehmann this LGTM, but are you going to do the changes we talked about yesterday in another PR?

@diogomonica: Yes, I'm planning to do those as a followup.
I'm waiting for design review on the mockup, and also on the swarmkit PR https://github.com/docker/swarmkit/pull/1128.

Didn't quite understand. So, the old behavior still exists right? Nodes can join swarm cluster without any secret and the default --auto-accept is set to worker?
Or are you saying that passing --secret is now mandatory and if we don't explicitly set it up, docker swarm will automatically pick one and thereafter both worker and manager nodes need to know that auto-generated secret to join the cluster.
So, are we dropping none as a parameter value for --auto-accept? or are we thinking to drop --auto-accept parameter itself since it will no more be needed since we are mandating --secret?
Can we also update the respective documentation?

@praving5 see https://github.com/docker/docker/issues/24430 for more context

@praving5: The new behavior is that swarm init by default will generate a secret that you need to pass to add nodes. swarm init will print a complete command line you can use to do this, including the secret. You can always opt out of this behavior by passing --secret "" on the swarm init command line (though note that the form of this flag may change soon - see #24430).
Node acceptance is a separate concept from the joining secret. The defaults there haven't changed, so it's still necessary to accept managers with docker node accept.
The documentation you mentioned was updated as part of this PR.


WIP: Process API addressable ports

Improves test coverage for dealing with addressable ports with Process API. Needed for #526

@trustmaster would be good to give this an initial review round

Follow-up would be to add convenience methods for checking / fetching input data by connection idx


Automation lanes/events (like in Ableton)

I'm currently stumped trying to create Automation events in a way that is atomic (can be scheduled / rendered offline).  The simplest example to recreate would be similar to an automation / modulation lane like in Ableton Live:

Experimenting with different ways to compose these events, we've started with a simple data model:
const AutomationLane = {
  startValue: 0,
  paths: [
    { time: 0.5, value: 1, exponent: 0.3 },
    { time: 1, value: 0, exponent: 3 }
  ],
  endValue: 0
};

The key here is that the lines connecting the startValue, Path values, and endValue both have unique, specific exponents for their curves.  We have it working with realtime Midi CC and with raw Midi files via setValueCurveAtTime, but a proper offline/transport-synced solution is alluding me.
A few things we've tried:
Using multiple Signals and Pows gets things going:
const pow1 = new Tone.Pow(3).connect(target);
const pow2 = new Tone.Pow(0.3).connect(target);
const signal1 = new Tone.Signal(0).connect(pow1);
const signal2 = new Tone.Signal(1).connect(pow2);

signal1.rampTo(1, 0.5, 0);
signal2.rampTo(0, 0.5, 0.5);

But their values compound (they go from 1-2 instead of 0-1). To compensate for the compounding, we tried setting each one to 0 when it's done, and setting the next one to the previous one's value like so:
const pow1 = new Pow(3).connect(target)
const pow2 = new Pow(0.3).connect(target)
const signal1 = new Signal().connect(pow1)
const signal2 = new Signal().connect(pow2)

signal1.linearRampToValueAtTime(1, 0.5)
signal1.setValueAtTime(0, 0.5)

signal2.setValueAtTime(1, 0.5)
signal2.linearRampToValueAtTime(0, 1)

But it gives confusing results, including an offset that causes it to over or undershoot 0 and 1:

We tried sticking to 1 Signal and 1 Pow, but scheduling a callback that updates the exponent via transport.scheduleOnce:
let pow = new Tone.Pow(3).connect(target)
const signal = new Tone.Signal().connect(pow)

signal.linearRampToValueAtTime(1, 0.5)
signal.setRampPoint(0.5)
signal.linearRampToValueAtTime(0, 1)

context.transport.scheduleOnce(() => {
	pow.value = 0.1
}, 0.5)

context.transport.start()

It seems to ignore the initial exponent value.  If we remove the part where the exponent changes at 0.5:
let pow = new Tone.Pow(3).connect(target)
const signal = new Tone.Signal().connect(pow)

signal.linearRampToValueAtTime(1, 0.5)
signal.setRampPoint(0.5)
signal.linearRampToValueAtTime(0, 1)

// context.transport.scheduleOnce(() => {
// 	pow.value = 0.1
// }, 0.5)

context.transport.start()

It looks like this:

I'm fumbling around in the dark here it seems 😅
So far, the system I've come up with for modularizing / generating these works pretty nicely -- I just can't seem to get the actual signal automation right!
For the curious, this is what it looks like as of now:
fn: (target, context) => {
  const lane: AutomationLane = {
    target: {
      pointer: () => {},
      min: 0,
      max: 1,
    },
    startValue: 0,
    paths: [
      { time: 0.5, value: 1, exponent: 3 },
      { time: 1, value: 0, exponent: 0.3 },
    ],
    endValue: 0,
  }

  const AutomationEvent = (lane: AutomationLane, automationTarget: Signal | number) => {
    const signals = lane.paths.map((path, i) => {
      const pow = new ScaleExp({
        context,
        exponent: path.exponent,
        min: lane.target.min,
        max: lane.target.max,
      })

      const signal = new Tone.Signal<'normalRange'>({
        context,
        value: 0,
        units: 'normalRange',
      })
      signal.debug = true

      // Make sure there is a setValue event at the start of the automation.
      signal.setValueAtTime(0, 0)

      // Hook them up.
      signal.chain(pow, target)

      return signal
    })

    const event = new Tone.ToneEvent(
      (now) => {
        for (let i = 0; i < lane.paths.length; i++) {
          if (i === 1) {
            signals[i].setValueAtTime(lane.startValue, now)
          }

          const startTime = i === 0 ? now : lane.paths[i - 1].time
          const startValue = i === 0 ? lane.startValue : lane.paths[i - 1].value
          console.log({ startValue, startTime })

          const path = lane.paths[i]

          // Do the automation.
          signals[i].linearRampToValueAtTime(path.value, path.time)

          // Set the current paths value to 0 when it's complete.
          signals[i].setValueAtTime(0, path.time)

          // And set the next paths value to the current path's value.
          if (signals[i + 1]) {
            signals[i + 1].setValueAtTime(path.value, path.time)
          }
        }
      },
      { context },
    )

    return { event }
  }
  context.transport.start()

  const automation = AutomationEvent(lane, target)
  automation.event.start()
}

Anyways, I suppose my question is:
Is there a recommended approach to solving this problem?  Perhaps someone could offer any insight or advice to point me in the right direction?  Any feedback would be greatly appreciated!!
Thanks!  And thank you to all of the brilliant minds behind this amazing project 🙏

My advice: don't do it like that.
Create an algorythmic but discrete array of values, and ride the sliders with that.

@dirkk0 hmm ok that makes sense, thanks!  When you say "ride the sliders", what do you mean?  I was imagining that setValueCurveAtTime would be ideal if I understand you correctly.

I didn't try setValueCurveAtTime out, but yes this seems an option.
My use case was 'writing automation lanes in real time' while hearing the stems and then 're-playing them while doing the offline rendering' as fast as possible.
What worked for me was to write the values into a vanilla JS array from sliders like a mixing desk (hence 'ride the sliders') with appropriate resolution and writing/reading these values respectively.
Simple approach that worked very well for my clients use case.

I'll give that a shot - thanks for the advice!


Feature/cplp 1544/app subscription page

@oyo I made all the changes you mentioned, can you please review again


Indicator Plan update: Incorporate RF levels into web view and export

Affects: Indicator plan and Excel export
Affected by: Legacy indicator levels and our migration plan for those. See the "Indicator Plan" section in #1286.
Stories

My indicator plan groups indicators by Results Framework (RF) levels, just like the IPTT does.
I can group indicators by results chain or by level, just as I can in the IPTT.
My indicator plan export includes RF level rows and reflects my grouping selection.

Acceptance criteria

There are two options for grouping indicators, identical to what we are doing for the IPTT (see #1298): by [2ndRFtier] chain or by Level, where "level" in this case refers to what we're internally calling tier. Length-wise, make sure to take into account long RF tier names translated into French, like so:

[ ] 1. The Indicator plan now includes RF level rows, in exactly the same way we're displaying them in the IPTT.

[ ] 1.1. RF level rows are displayed regardless of whether or not there are indicators linked to them.

[ ] 1.2. Any indicators unassigned to an RF level is grouped at the bottom under a row called "Indicators unassigned to a results framework level" -- same as the IPTT.

[ ] 2. I can toggle between two indicator grouping options using a single-select menu with only the two options and no selectable "null" option like "------". The menu is in the upper right corner, right-aligned under the Excel export button. The search function should be OFF, since there are only two options.

[ ] 2.1. The form field label to the left of the menu is "Group indicators:"

[ ] 2.2. The default selection is "by [2ndRFtier] chain" -- so in the case of the MC template where the 2nd tier is Outcome, it'd be "by Outcome chain" and in the case of EC it'd be "by Specific Objective chain". Please note the capitalization -- "by" is lower case, and the RF tier is title case.

[ ] 2.3. The other option is "by Level".

[ ] 3. When I toggle between the options, the Indicator Plan table reloads, grouped according to my selection.

[ ] 4. My Excel Export:

[ ] 4.1. Includes the RF level rows
[ ] 4.2. Reflects my grouping preference

Housekeeping (where applicable)

[ ] Unit test/s written
[ ] i18n strings included
[ ] Is accessible to people using screen readers

@jennyhavah what behavior do you want for the indicator plan in the case of programs that haven't migrated to the new RF levels?  Should we be displaying the old levels and not adding grey level rows, until they switch over their "grouping" in the program admin?

@camgnostic I was imagining we'd handle it exactly like we're handing the IPTT -- no gray rows, ordered according to the original sorting criteria -- OldLevel, then number. Which I think is what we're doing right now.

PASSED. RF tier rows are displaying as expected, and export as expected, whether I group by Chain or by Level.