prepare example store backend app

Right now there is an example app: https://admin-bro-example-app.herokuapp.com/admin which shows default admin features. Since we use AdminBro in a couple of web stores it will be good to have an example backend showing all the possibilities of AdminBro for E-Commerce use-case.
working name: Bromence (AdminBro for E-Commerce)
Acceptance criteria:
in general: build admin panel for e-commerce page

database should have:
** products
** variants
** nested categories (n to n)
** orders with order items
** photos
** users
in the AdminBro UI there should be a
** dedicated page for adding product and variants (ideally on one page)
** dedicated page for managing orders
it will have to be deployed somewhere (heroku, firebase etc)

Next

in a separate task we could add an example frontend to it.

Can you explain it in more details. Could you give any example?

@pawlakzn I update the description - long story short it is about Bromance example

can you share the source code of the heroku deployed website

https://github.com/SoftwareBrothers/admin-bro-example-app

WIP of the app is inside the repo (/app) - we will be constantly working on it so closing this task


Spreading props overrides children while SSR

Describe the bug
Using spread props (it was working before 1.6 update) overrides children if they're defined in JSX and have spread props as well. It works correctly, if they're defined as normal prop. The error occurs only with SSR.
Your Example Website or App
https://stackblitz.com/edit/vitejs-vite-kwtgcw?file=src/root.tsx
Steps to Reproduce the Bug or Issue

Use newest Solid.JS version with SSR setup, f.e. solid-start
Create element which has spread props and children with spread props too
Render them

Expected behavior
Both parent and children are rendered correctly, and props are assigned properly
Screenshots or Videos
No response
Platform
N/A
Additional context
No response

Oh, it looks like a duplicate of #1345, sorry for inconvenience


Add BitChoiceGroup component Documentation Comments (#541)

This closes #541

I'm closing this PR because of the unrelated commits in it


System.InvalidCastException

Condition:
Entity "A" has a "UploadedAs" attribute of type int.
Entity "B" has a "uploadedAs" attribute of type "SomeEnum".
Problem:
When mapping from A->B, it just ignores my custom mapping and throws exception.
Solution:
I renamed the attribute "uploadedAs" as "uploadedAs1" in entity B. The issue resolved.
Exception Details:
Invalid cast from 'System.Int32' to '...SomeEnum..'.
StackTrace:
[InvalidCastException: Invalid cast from 'System.Int32' to '...SomeEnum..'.]
System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider) +13709456
lambda_method(Closure , IEnumerable`1 ) +1015
TargetInvocationException: Exception has been thrown by the target of an invocation.]
System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) +0
System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) +128
System.Delegate.DynamicInvokeImpl(Object[] args) +153
...
...
...

Dear @canaliden ,
Thanks a lot for your valuable input!
As you can see int to enum there is no default IConvertible implementation. But I'd love to implement it. Will try to implement it in the next release.
Thanks!


Error: Runtime crashed

when running the instructions from step 4., the following error occured
Running dfx start for version 0.19.0
Using shared network 'local' defined in /Users/moritz/.config/dfx/networks.json
2024-04-23T06:17:32.043046Z ERROR icx_proxy_dev: Runtime crashed
Error: Runtime crashed

Caused by:
    0: fail to fetch root key for http://localhost:8000/
    1: An error happened during communication with the replica: error trying to connect: tcp connect error: Connection refused (os error 61)
2024-04-23T06:17:34.231380Z ERROR icx_proxy_dev: Runtime crashed
Error: Runtime crashed

Caused by:
    0: fail to fetch root key for http://localhost:8000/
    1: An error happened during communication with the replica: error trying to connect: tcp connect error: Connection refused (os error 61)
Initialized replica.
Dashboard: http://localhost:8000/_/dashboard

this error continues to appear, even after running cleanup.sh

This error can be safely ignored as long as
Dashboard: http://localhost:8000/_/dashboard

appears

But you might be able to silence the error by running killall replica icx-proxy dfx if it bothers you


[convert:utf8] decode(encode(org)) is different than original input

hi,
i was testing dart's utf8 functionality,
comparing the utf8 "encoded, then decoded, output", with the original input,
with the following (working, even on dartpad.dev) code:
import "dart:convert";

void main() {
  final //
      original = List<int>.generate(
        0x10ffff,
        (final int charCode) => //
            (1 /* to eliminate the value 0(null/delimiter) */ + charCode),
        growable: false,
      ),
      bytes = Utf8Encoder().convert(String.fromCharCodes(original)),
      utf8 = Utf8Decoder().convert(bytes).runes.toList();

  for (int i = 0, limit = original.length; i < limit; i += 1) {
    print("$i: " +
        ((original[i] == utf8[i]) //
            ? "OK        "
            : "***WARN***") +
        "  ${original[i]}  vs  ${utf8[i]}");
  }
}

Above code produces 0x10ffff lines,
But the relevant part is copied below,
Where,
/**
  1st column is iteration,
  2nd is:
    OK(utf8 output matches with original input), or
    WARN(mis-match),
  3rd is original input
  4th is utf8 output

  i    match?      org        utf8   */
55273: OK          55274  vs  55274
55274: OK          55275  vs  55275
55275: OK          55276  vs  55276
55276: OK          55277  vs  55277
55277: OK          55278  vs  55278
55278: OK          55279  vs  55279
55279: OK          55280  vs  55280
55280: OK          55281  vs  55281
55281: OK          55282  vs  55282
55282: OK          55283  vs  55283
55283: OK          55284  vs  55284
55284: OK          55285  vs  55285
55285: OK          55286  vs  55286
55286: OK          55287  vs  55287
55287: OK          55288  vs  55288
55288: OK          55289  vs  55289
55289: OK          55290  vs  55290
55290: OK          55291  vs  55291
55291: OK          55292  vs  55292
55292: OK          55293  vs  55293
55293: OK          55294  vs  55294
55294: OK          55295  vs  55295
55295: ***WARN***  55296  vs  65533
55296: ***WARN***  55297  vs  65533
55297: ***WARN***  55298  vs  65533
55298: ***WARN***  55299  vs  65533
55299: ***WARN***  55300  vs  65533
55300: ***WARN***  55301  vs  65533
55301: ***WARN***  55302  vs  65533
55302: ***WARN***  55303  vs  65533
55303: ***WARN***  55304  vs  65533
55304: ***WARN***  55305  vs  65533
55305: ***WARN***  55306  vs  65533
55306: ***WARN***  55307  vs  65533
55307: ***WARN***  55308  vs  65533
55308: ***WARN***  55309  vs  65533
55309: ***WARN***  55310  vs  65533
55310: ***WARN***  55311  vs  65533
55311: ***WARN***  55312  vs  65533
55312: ***WARN***  55313  vs  65533
55313: ***WARN***  55314  vs  65533
55314: ***WARN***  55315  vs  65533
55315: ***WARN***  55316  vs  65533
55316: ***WARN***  55317  vs  65533

This is working as intended.
That code points being warned about here are unpaired surrogates, in the range U+D800 through U+DFFF, which are not allowed as part of valid UTF-8 encodings.
The code point you get instead, is U+FFFD, the "replacement character" used to replace invalid characters. That's not avoidable, you simply cannot encode an unpaired surrogate as UTF-8. (The extension to UTF-8 which allows that is often called WTF-8. That's not what Dart's Utf8Encoder allows.)
You should only test with scalar values, not code points ("scalar values" are all code points except surrogates), because only scalar values can be encoded as UTF-8:
var original = [for (var i = 0; i <= 0x10FFFF; i++) if (i < 0xD800 || i >= 0xE000) i];
// ...

The String.fromCharCodes accept both code units and code points, and Dart strings allow unpaired surrogates, so it only becomes a problem when you try to convert.
And String.fromCharCodes is not unique, you can have two different arguments that create the same string, like [0xD800, 0xDC00] and [0x10000]. So it's not entirely surprising that what you get out of .runes.toList() isn't necessarily the same list you put into String.fromCharCodes, even if there were no unpaired surrogaes.
There is one other issue with the test, also related to the unpaired surrogates.
If you insert:
  print(original.length.toRadixString(16)); // 10ffff
  print(utf8.length.toRadixString(16)); // 10fffe

you can see that the two lists are not even the same length.
That's because the input contains the char code sequence ... 0xDBFE, 0xDBFF, 0xDC00, 0xDC01, ..., and the middle two "character codes" is actually a surrogate pair, which are encoded and decoded correctly as a single code point ("rune") in the result. Which is why everything is off-by-one after that.
Consider this test instead:
import "dart:convert";

void main() async {
  var codec = Utf8Codec(allowMalformed: true);

  var charCodes = [
    for (var i = 0; i <= 0x10FFFF; i++)
      if (i < 0xD800 || i >= 0xE000) i
  ];
  var original = String.fromCharCodes(charCodes);

  var roundtrip = codec.decoder.convert(codec.encoder.convert(original));

  print(original.length == roundtrip.length); // True
  print(original == roundtrip); // True
  for (var i = 0, ito = original.runes.iterator, itr = roundtrip.runes.iterator;
      ito.moveNext() && itr.moveNext();
      i++) {
    var or = ito.current;
    var rr = itr.current;
    if (or != rr) {
      print("$i: ${or.toRadixString(16)} vs ${rr.toRadixString(16)}");
    }
  }
}

If you remove the if (i < 0xD800 || i >= 0xE000), you will see that it reports only the unpaired surrogates as differing.


Update configure-zowe-zosmf-workflow.md

(1) Fixed typos.
(2) For the SMP/E installable version, the workflows are in /workflows vs. /files/workflows, I assume the same is true for the downloadable version.
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ] If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.

[ ] If this PR relates to GitHub issues in docs-site or other repositories, please list in Description, prefixed with close, fix or resolve keywords.

Description (including links to related git issues)
Please describe your pull request.
:heart:Thank you!

@sn666239

Hello,
    Is there something else I need to do?

            Neil

From:   nannanli<EMAIL_ADDRESS>To:     zowe/docs-site<EMAIL_ADDRESS>Cc:     neils-ibm<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Date:   11/26/2020 09:32 PM
Subject:        [EXTERNAL] Re: [zowe/docs-site] Update
configure-zowe-zosmf-workflow.md (#1498)
@sn666239
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @neils-ibm, thank you for making these changes! Your contribution is appreciated. Nothing else is needed on your side now. We are finding the developer and doc owner to review these so they are aware of the issues. Will get this PR merged soon.


Disable vue/max-len

The new rule vue/max-len has been added since<EMAIL_ADDRESS>
https://eslint.vuejs.org/rules/max-len.html
https://github.com/vuejs/eslint-plugin-vue/releases/tag/v6.1.0
https://github.com/vuejs/eslint-plugin-vue/pull/959

This rule is an extension of the ESLint core rule max-len,
and eslint-config-prettier has disabled the rule already by setting value to 0.

https://github.com/prettier/eslint-config-prettier/blob/d6bf4c063dfaf1de0b5c22ba0156184955b39b44/index.js#L14

Thanks! Released in v6.9.0.


Fix wrong params in test

Function definition is:
https://github.com/stretchr/testify/blob/bb548d0473d4e1c9b7bbfd6602c7bf12f7a84dd2/require/require.go#L155
func Equal(t TestingT, expected interface{}, actual interface{}, msgAndArgs ...interface)

content from file should be expected result, not actual result

@luantranminh  its because your forked repo is lacking some secret, I will create identical PR from this repo

Oh, weird. Does it mean I followed the wrong steps to make a PR?

Oh, weird. Does it mean I followed the wrong steps to make a PR?

no, you did everything ok.
Just when forking repo, you dont fork the secrets.
and the 1 of the secret is used to run the integration tests, thus the GH action fail.

duplicated #42


GALAXY

dockstore/dockstore#3186
Dockstore has updated the subclass to be GALAXY so this change is needed to register these workflows on Dockstore using GitHub Apps. Once merged, who can I talk to about getting these workflows registered on Dockstore?

Thanks @NatalieEO! If you like to join us on gitter for any other question or create an issue here.


Change colour scheme

Codecov Report
Base: 76.23% // Head: 76.09% // Decreases project coverage by -0.14% :warning:

Coverage data is based on head (035e2a8) compared to base (8779bdb).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #129      +/-   ##
============================================
- Coverage     76.23%   76.09%   -0.15%
  Complexity      730      730
============================================
  Files           115      115
  Lines          2142     2146       +4
  Branches        260      260
============================================
  Hits           1633     1633
- Misses          439      443       +4
  Partials         70       70

Impacted Files
Coverage Δ

...n/java/seedu/address/commons/core/GuiSettings.java
69.23% <ø> (ø)

...c/main/java/seedu/address/ui/ProjectListPanel.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/StaffListPanel.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/TaskCard.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/TaskListPanel.java
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[5.x] Unexpected token "import" with electron-mocha

Hi,
I am new to Electron and web-based tools such as electron-forge, WebPack and Babel, and I am having a hard time trying to add unit tests with electron-mocha to my Electron application.

In package.json, I added the test script:

electron-mocha --renderer --require babel-core/register --recursive tests/**/*.spec.js

Content of tests/search.spec.js, where search is a single-file Vue component:

import Search from "../src/components/search";

describe("Search", () => {
	it("Test", () => {
		console.log("ok");
	});
});

Content of .compilerc:

{
  "env": {
    "development": {
      "application/javascript": {
        "presets": [
          [
            "env",
            {
              "targets": {
                "electron": "2.0"
              }
            }
          ],
          "react"
        ],
        "plugins": [
          "transform-async-to-generator",
          "transform-object-rest-spread"
        ],
        "sourceMaps": "inline"
      }
    },
    "production": {
      "application/javascript": {
        "presets": [
          [
            "env",
            {
              "targets": {
                "electron": "2.0"
              }
            }
          ],
          "react"
        ],
        "plugins": [
          "transform-async-to-generator",
          "transform-object-rest-spread"
        ],
        "sourceMaps": "none"
      }
    }
  }
}

When I run yarn test, I have the following error:
yarn run v1.6.0
$ electron-mocha --renderer --require babel-core/register --recursive tests/**/*.spec.js
Unexpected token import
/Users/jroy/Workspace/app/tests/search.spec.js:1
(function (exports, require, module, __filename, __dirname, process, global, Buffer) { return function (exports, require, module, __filename, __dirname) { import Search from "../src/components/search";
                                                                                ^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:606:28)
    at loader (/Users/jroy/Workspace/app/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/jroy/Workspace/app/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:504:12)
    at Function.Module._load (module.js:496:3)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at /Users/jroy/Workspace/app/node_modules/mocha/lib/mocha.js:250:27
    at Array.forEach (<anonymous>)
    at Mocha.loadFiles (/Users/jroy/Workspace/app/node_modules/mocha/lib/mocha.js:247:14)
    at Mocha.run (/Users/jroy/Workspace/app/node_modules/mocha/lib/mocha.js:576:10)
    at Object.run (/Users/jroy/Workspace/app/node_modules/electron-mocha/mocha.js:54:30)
    at EventEmitter.ipc.on (/Users/jroy/Workspace/app/node_modules/electron-mocha/renderer/run.js:29:11)
    at emitOne (events.js:116:13)
    at EventEmitter.emit (events.js:211:7)
error Command failed with exit code 1.

Can someone point me to the right direction please?
Thanks beforehand!

In anticipation of The V6 Stable Release we are closing out all the v5 issues.  Once V6 stable is released it will be the only supported version of Electron Forge.


Let Kotlin tasks implicitly use the configured java toolchain

From https://kotlinlang.org/docs/gradle.html#gradle-java-toolchains-support:

You can set a toolchain via the java extension, and Kotlin compilation tasks
will use it

A followup to #18393

@bot-gradle test and merge

OK, I've already triggered a build for you.


Misc. Package Updates

Similar to https://github.com/SymfonyTest/SymfonyConfigTest/pull/69, this PR:

Drops support for Symfony versions prior to 4.4 and 5.0 through 5.2
Changes the CI to use GitHub Actions instead of Travis (https://github.com/mbabker/SymfonyDependencyInjectionTest/actions/runs/1231711382 from my fork is the build for this PR's branch)
Allows install with Symfony 6.0

Merged, thanks @mbabker !


[WIP] Refactoring, bugfixes add slide policy

As the maintainers seem quite inactive for a few month now, I decided to create a PR which addresses a lot of issues and implements a few new features, I'd like to have.
@PaoloRotolo and @Andrew-Quebe: If you don't want to merge the whole PR but only parts, let me know, for most points I mention in the following list, it would be possible to create a own PR, if requested.
Note: All changes are backward compatible and don't break any implementation.

[x] Go back to stable version of the gradle plugin to prevent warnings when using an outdated preview version (45e7a1a) Edit: Plugin version changed to v2.0.0 stable (768680e)
[x] Add missing import (576392e). Same as #199 and #207
[x] The classes AppIntro and AppIntro2 share a lot of common code. This is ugly, a common parent class would solve it (7c4008b and c0b2d53)
[x] The function onNextPressed is useless. (Marked as deprecated in 55c7034)
[x] #134, #175 : Add new functions with changed signature of onSlideChanged, onDonePressed and onSkipPressed returning the instance of the current fragment, mark the old ones as deprecated. (55c7034)
[x] #129: Add the possibility to have some fragment-based policy on whether going to the next slide, pressing done, pressing skip (#100) leaving the intro by pressing the back button is enabled. E.g.: One has a fragment with a license text which should be acknowledged by ticking a checkbox. The fragment should be able to lock the intro until the user checked the checkbox. (Method setGoBackLock implemented d014eed)
[x] #119: Let users override onCreate(), mark init() as deprecated (2941c7f)
[x] remove custom method restoreLockingState and override onRestoreInstanceState instead (2941c7f).
[x] Consolidate layout files layout_intro.xml and layout_intro2.xml. Both have a almost completly indentical file for the layout-v21 stuff. This could be easier done via a small style. Also as mentioned in #142, both contain unnecessary color declarations (2153055 and b9b36c9)
[x] Implement support for immersive mode. Add two methods setImmersiveMode(isEnabled) and setImmersiveMode(isEnabled, isSticky). The former is a shorthand method for the latter with the second parameter set to false. (c8e7825)
[x] Implement correct fragment instance saving and restoring (for example on orientation changes).

94c480e: Implemented basic support for saving and restoring supported fragments. Custom fragments need to override onSaveInstanceState and restore data manually. AppIntroFragment supports this behavior natively now.

[x] Implement callbacks to slides if they were selected or deselected. Custom fragements may implement ISlideSelectionListener which contains the two methods onSlideSelected and onSlideDeselected. These methods will be called automatically. Extend AppIntroFragment to implement ISlideSelectionListener. (0f529ee)
[x] Split AppIntroFragment into AppIntroFragment and AppIntro2Fragment with a common super class in order to be able to set the different bottom paddings of the two layouts accordingly (Layout: 64dp, Layout2: 80dp). Add fragment_intro.xml and fragment_intro2.xml with common layout xml fragment_intro_content.xml. (cf81e46).
[x] Add some default styles and dimensions for easier cusomisation (i.e. custom slides) (ef87b30
):

Style AppIntroDefaultPadding adds some basic padding to the slide, respecting the status bar's height. This style does not respect the bottom bars height, if the content is too high, it will underlay the bottom bar.
Style AppIntroDefaultPadding.Intro1: Same as i) but with additional padding at the bottom to respect the bottom bar's height (normal layout)
Style AppIntroDefaultPadding.Intro2: Same as i) but with additional padding at the bottom to respect the bottom bar's height (Layout2)
Style AppIntroDefaultHeading: Default style for a slide's heading
Style AppIntroDefaultText: Default style for a slide's text

[x] #186: Add support for color transitions. Color transitions are only available if all slides implement ISlideBackgroundColorHolder and can be enabled and disabled via setColorTransitionsEnabled(boolean). AppIntroFragment and AppIntroFragment2 implement this interface by default. (c963ce4 and 11d5e23)

Regarding the last item with enabling/disabling fragments, this functionality is already included, please see #100, although it hasn't been added to the readme/instructions and probably should be.

@danluong: Aaah, thanks didn't get that one, but there is stilling a missing lock that prevents leaving the intro by pressing the back button.

Wow, it seems good to me. @Andrew-Quebe what do you think?

I added a slide with some input elements to the example app's DefaultIntro in order to demonstrate fragment retaining.
However, I didn't overhaul the example app and readme yet.
Another feature I'll implement is some callback functionality slide -> activity to be able to lock the intro directly without ((AppIntro)getActivity).....

So, wow. Thanks for your work. I'll release a new version on Maven soon.

Thanks for merging, however I might add some further changes regarding slide-based locking in the next days. Also the readme isn't up to date anymore.
I will create a new PR for further changes.

@maxee some awesome work man! Very detailed PR...one of the best I've ever seen in my open source experience!

@Andrew-Quebe, thanks and you're welcome, I hope, everything works as expected, for me all tests worked. Maybe you could test it a bit before releasing a new version in order to be sure, but most of the changes are refactoring-related :)
I hope I'll find time to update the readme file within the next days.
Also the example app does not demonstrate the new color transition, lock and immersive mode capabilities at this time.

@maxee I'll look into updating the Readme as well as the sample once we release on Maven.


glava: 1.5.1 -> 1.5.4

Motivation for this change
Things done

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

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

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

@GrahamcOfBorg build glava

Unexpected error: command failed with exit code 1 on x86_64-linux (full log)
Attempted: glava
Partial log (click to expand)
remote: Counting objects: 100% (76/76), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 76 (delta 10), reused 34 (delta 3), pack-reused 0
From https://github.com/Dav1dde/glad
 * tag               v0.1.24    -> FETCH_HEAD
Switched to a new branch 'fetchgit'
removing `.git'...
fixed-output derivation produced path '/nix/store/5msba2vm2jqbw28vnl4zxbcnd6wp23wk-glava' with sha256 hash '10b977dap71af7jx73z15qws9ybxvrrl2s143r3hf5xpgf2s8c14' instead of the expected hash '0y5nz51r5brxs0xc100ingfrm96kl49gwnslhscvfxwwqrb6g1p1'
cannot build derivation '/nix/store/hhyb3jkbf0x4d61n8a44mz8ill69kicr-glava-1.5.4.drv': 1 dependencies couldn't be built
error: build of '/nix/store/hhyb3jkbf0x4d61n8a44mz8ill69kicr-glava-1.5.4.drv' failed

Unexpected error: command failed with exit code 1 on aarch64-linux (full log)
Attempted: glava
Partial log (click to expand)
remote: Counting objects: 100% (76/76), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 76 (delta 10), reused 34 (delta 3), pack-reused 0
From https://github.com/Dav1dde/glad
 * tag               v0.1.24    -> FETCH_HEAD
Switched to a new branch 'fetchgit'
removing `.git'...
fixed-output derivation produced path '/nix/store/5msba2vm2jqbw28vnl4zxbcnd6wp23wk-glava' with sha256 hash '10b977dap71af7jx73z15qws9ybxvrrl2s143r3hf5xpgf2s8c14' instead of the expected hash '0y5nz51r5brxs0xc100ingfrm96kl49gwnslhscvfxwwqrb6g1p1'
cannot build derivation '/nix/store/xa3dmx7ry1zjp4paqlz8ybh6v4s4ahk5-glava-1.5.4.drv': 1 dependencies couldn't be built
error: build of '/nix/store/xa3dmx7ry1zjp4paqlz8ybh6v4s4ahk5-glava-1.5.4.drv' failed

hash mismatch (in a git submodule?)

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: glava
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

With versions 1.5.4+, the glad submodule isn't needed anymore, though I'll just use the hash generated from --fetch-submodules then.

@GrahamcOfBorg build glava

Success on x86_64-linux (full log)
Attempted: glava
Partial log (click to expand)
'shaders/util' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/util'
'shaders/util/premultiply.frag' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/util/premultiply.frag'
'shaders/util/smooth.glsl' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/util/smooth.glsl'
'shaders/util/smooth_pass.frag' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/util/smooth_pass.frag'
'shaders/wave' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/wave'
'shaders/wave/1.frag' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/wave/1.frag'
'shaders/wave/2.frag' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/wave/2.frag'
'shaders/wave.glsl' -> '/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5/etc/xdg/glava/wave.glsl'
post-installation fixup
/nix/store/ibf0qsaq7c4iv9dl154bgs04hybi1kjp-glava-1.5.5

Success on aarch64-linux (full log)
Attempted: glava
Partial log (click to expand)
'shaders/util' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/util'
'shaders/util/premultiply.frag' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/util/premultiply.frag'
'shaders/util/smooth.glsl' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/util/smooth.glsl'
'shaders/util/smooth_pass.frag' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/util/smooth_pass.frag'
'shaders/wave' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/wave'
'shaders/wave/1.frag' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/wave/1.frag'
'shaders/wave/2.frag' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/wave/2.frag'
'shaders/wave.glsl' -> '/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5/etc/xdg/glava/wave.glsl'
post-installation fixup
/nix/store/mkc5dlwdi2bkbdlc90883f7pgsjrfhbf-glava-1.5.5

With versions 1.5.4+, the glad submodule isn't needed anymore, though I'll just use the hash generated from --fetch-submodules then.

That's fine for now. We generally prefer fetchFromGitHub (which does not fetch submodules by default) for fetching from Github repos. I suggest you change that with the next update.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: glava
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


Minor doc fixes for AMQP, fixed a typo and added CDI configuration.

Minor typo in hostname.  Also added a CDI based example.

Thanks for the PR it has been merged. Do you mind closing this?


Multiminer and Slushpool - what am I doing wrong?

hello,
I just started my mining journey 7 days ago so I believe that makes me an infant to this.
Despite all the reading and research I'm doing (trial and error with most of this), I cannot seem to get a good grasp of what slushpool is telling me.  I know I have much more to learn but I think I am doing some things extremely wrong.
I am only running 1 gpu for now until i get a better understanding of this. my 'Worker States' seems to be in "off" all the time and my apparent 'estimated payout period' is constantly telling me something ridiculous like 88 years... I just feel like everything on my dashboard is reading very low and it might be because I have things set up wrong or that what I'm running is horrible.
I have attached a screenshot for an illustration of what I am typing about.
Just trying to reach out for a little (or a lot) help.
thank you

If you are mining with a single GPU, even if it's a top of the line 1080ti, that's probably about right. BTC is dominated by ASIC mining now (i.e. BitMain's AntMiners). My older S7's are going about 4.7TH/s and it was almost a month for a payout. GPU mining is probably better for some of the other coins at this point.

already sluchpool mention in they help section here you can read here https://slushpool.com/help/get-started/mining_beginners
First of all you need specialized hardware (ASIC miner)
Do not even try mining without an ASIC miner. Neither your CPU/GPU nor your Smart phone is sufficient for mining anymore. It is considered dead and unprofitable due to low efficiency (hash rate vs. power consumption).


Large file notification doesn't show when opening fresh Code

Testing https://github.com/Microsoft/vscode/issues/46602

Close all instances of vscode
Run code-insiders myLargeFile.txt
Empty code window opens, no file or notification

After investigation, this looks to be caused because the partService is not ready in doHandleSetInputError in editorPart.ts … I think we may be needing to check the notificationService instead. Assigning to @bpasero


[fix] (nereids) fix Match Expreesion in filter estimation (#39050)

Proposed changes
pick from master #39050

run buildall


fix(eslint): Enable rule react/no-array-index-key

Fixes #1503

@gihrig the component ListItem don'ts accept a object example:
const items = [
  { id: 1, name: 'Hello' },
  { id: 2, name: 'World' },
];

Which would be the best option to pass another component that accepts the property established by the fake state ?

@carloscuatin Off hand, I don't have an answer for that...
Anyone else?

const items = [
  { id: 1, name: 'Hello' },
  { id: 2, name: 'World' },
];
const Item = ({ name }) =>
{name}
;
const renderedComponent = render(
  <List items={items} component={Item} />
);

possible solution @gihrig

@carloscuatin That looks good, and it works ✨
A few issues though:

const Item Item is not an object or Component, it should be lowercase.
Eslint has an issue with

const item = ({ name }) =>
{name}
;

Suggest adding  // eslint-disable-line react/prop-types

@carloscuatin I tried the exact same thing, but it didn't work 😕 Maybe I missed something. Let's go with this if it works 👍

@KarandikarMihir

I tried the exact same thing, but it didn't work

What happened?
Current iteration works for me...
@carloscuatin Another win for code quality ✨
Thanks for hanging in there through all the back and forth!


fix for blank check on a stringvalue that wraps null

closes #37

Current coverage is 90.39%

Merging #38 into master will decrease coverage by -0.02% as of 9bc4979

@@            master     #38   diff @@
======================================
  Files          134     134
  Stmts         4288    4288
  Branches       444     445     +1
  Methods          0       0
======================================
- Hit           3877    3876     -1
- Partial        156     157     +1
  Missed         255     255

Review entire Coverage Diff as of 9bc4979

Powered by Codecov. Updated on successful CI builds.


merge Juniper changes into my fork.

hopefully i didn't mess this up.

This should include vnitinv's changes to fix the root shell issue (i431)


Update libthrift to 0.14.0

Update libthrift to 0.14.0
This addresses https://github.com/advisories/GHSA-g2fg-mr77-6vrm

@kokosing  - the fix is merged in master and ranger-2.5 branches, via RANGER-4870. Thank you!

Thank you!


[BUG]:  Azure File Copy Task (Version 6) is breaking on pipeline using Self hosted agent with error 'The term 'azcopy' is not recognized.

New issue checklist

[ ] I searched for existing GitHub issues
[ ] I read pipeline troubleshooting guide
[ ] I checked how to collect logs

Task name
Azure file copy
Task version
6.241.0
Issue Description
We recently upgraded the Azure DevOps (ADO) service connection from using an Azure Resource Manager service principal (automatic) to Azure Resource Manager using Workload Identity federation with OpenID Connect (automatic). But, we got an issue with Azure file copy task (Task version 6) when running it on pipeline with self-hosted agent. The error message received was: 'The term 'azcopy' is not recognized as the name of a cmdlet, function, script file, or operable program. Please check the spelling of the name, or verify that the path is correct and try again.' Also, the task works correctly when using an Azure agent, but fails on the self-hosted agent.
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows
Relevant log output
[debug]Script stack trace:
[debug]at ThrowError, C:\Agent\vsts-agent-win-x64-2.182.1\_work\_tasks\AzureFileCopy_eb72cb01-a7e5-427b-a8a1-1b31ccac8a43\6.241.0\Utility.ps1: line 121
[debug]at Upload-FilesToAzureContainer, C:\Agent\vsts-agent-win-x64-2.182.1\_work\_tasks\AzureFileCopy_eb72cb01-a7e5-427b-a8a1-1b31ccac8a43\6.241.0\Utility.ps1: line 272
[debug]at <ScriptBlock>, C:\Agent\vsts-agent-win-x64-2.182.1\_work\_tasks\AzureFileCopy_eb72cb01-a7e5-427b-a8a1-1b31ccac8a43\6.241.0\AzureFileCopy.ps1: line 181
[debug]at <ScriptBlock>, <No file>: line 1
[debug]at <ScriptBlock>, <No file>: line 22
[debug]at <ScriptBlock>, <No file>: line 18
[debug]at <ScriptBlock>, <No file>: line 1
[debug]Exception:
System.Management.Automation.RuntimeException: Upload to container: 'sitemap-generator' in storage account: 'sitemapextractor' with blob prefix: '' failed with error: 'AzCopy.exe exited with non-zero exit code while uploading files to blob storage.' For more info please refer to https://aka.ms/azurefilecopyreadme
2024-06-13T07:48:44.0282744Z ##[error]Upload to container: 'sitemap-generator' in storage account: 'sitemapextractor' with blob prefix: '' failed with error: 'AzCopy.exe exited with non-zero exit code while uploading files to blob storage.' For more info please refer to https://aka.ms/azurefilecopyreadme
[debug]Processed: ##vso[task.logissue type=error;source=TaskInternal]Upload to container: 'sitemap-generator' in storage account: 'sitemapextractor' with blob prefix: '' failed with error: 'AzCopy.exe exited with non-zero exit code while uploading files to blob storage.' For more info please refer to https://aka.ms/azurefilecopyreadme
[debug]Processed: ##vso[task.complete result=Failed]
[section]Finishing: AzureBlob File Copy

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION]

Repro steps
No response

Hi @Varaprasad91
Could you please share us the complete logs of the pipeline by adding variable system.debug to "true".

error logs1.txt

Hi @Varaprasad91
Thanks for sharing the logs. I hope @v-snalawade already connected with you reg this issue and she has started investigation.

Hi, @v-schhabra
I'm having trouble with the same issue. Are there any updates?
Auto-login appears to fail because azcopy.exe isn't available for the oauth token task has retrieved, even though task has running Connect-AzAccount.
Same issue as #19910 ?

Hi, @v-snalawade I'm having trouble with the same issue. Are there any updates? Auto-login appears to fail because azcopy.exe isn't available for the oauth token task has retrieved, even though task has running Connect-AzAccount. Same issue as #19910 ?

We are already investigating on this issue. Will share the latest updates here.

@tomaeda - Can you check if this suggestion  resolves the issue

Thank you for your response.
@v-schhabra
I'm sorry, the logs I'm seeing are provided by the end user. I can't share it here.
I haven't been able to reproduce this issue, so I don't have my own logs.
However, the information from line 5599 onwards in the error.logs1.txt shared by Varaprasad91 is consistent with the logs I am seeing, except for specific information such as the storage account name.
@v-snalawade
End user can work around the issue with a different pool.
The issue only occurs with the Self-hosted agent pool, not with MS-hosted pool.
But end user wants to use Self-hosted, so I'd like to know how to resolve the inconsistency between powershell and pwsh. (If this is same issue)

Thank you for your response.
@v-schhabra I'm sorry, the logs I'm seeing are provided by the end user. I can't share it here. I haven't been able to reproduce this issue, so I don't have my own logs. However, the information from line 5599 onwards in the error.logs1.txt shared by Varaprasad91 is consistent with the logs I am seeing, except for specific information such as the storage account name.
@v-snalawade End user can work around the issue with a different pool. The issue only occurs with the Self-hosted agent pool, not with MS-hosted pool. But end user wants to use Self-hosted, so I'd like to know how to resolve the inconsistency between powershell and pwsh. (If this is same issue)

If it is fine for you please share the logs at<EMAIL_ADDRESS>

#20117
Did fixes for the above issue. Will update here once it is deployed to all the cx.


Full indexing the whole project

Is there a way to index the entire project?
When a single C++ file is too large, I will wait for clangd to process it for a while.

you should generate a compile_commands.json for your project, listing all the files and compile commands associated with each one. then clangd can pick that file and start indexing every file in there. See Project Setup section in our docs.

Also, when your project is too large, once compile_commands.json is generated you can use clangd-indexer to generate the static index (will not be updated incrementally) and pass it to Clangd via --index-file.

@kadircet  Thank you for your reply, my configuration is good and compile_commands.json is generated. I mean, when I open a C++ file (more than 1w lines and containing many header files) in compile_commands.json, it takes a few seconds for cland to index it(from parsing includes state to idle). Therefore, I am considering whether there is a way to pre-index all files, so when I open the file, I will no longer wait for clangd to index the file.

ah i see. you meant parsing not indexing. unfortunately we currently have no a way to pre-parse or cache parsing results. but it is something we plan to improve eventually.
also it is a clangd feature rather than a coc-clangd, so transfering the issue.


Wrong MLIL lifting on MIPS

I hope this is a real bug and not just some misunderstanding on my part :).
I have the following MIPS code:

0x80065046 looks like this:

(not sure why there is no reference to this memory address, some other bug?)
Then MLIL looks like this:

As you can see, it simplified the $v0 == $v1 comparison into false, which is completely wrong at runtime, because that memory address can (and will) change, obviously. Not sure if the lack of reference to that memory address (there is no data_XXXX field) has something to do with it.

I manually created a field on that address and it didn't solve the problem, so I'm guessing this is really a bug, but happy to be proven wrong :).

What are the segment/section permissions for 0x80065046?

Right, I knew I was missing something. The segment 0x80010000-0x80069800 is being set as r-x, which is not completely correct. Is there a way for me to manually change that?

You can right click in the UI from linear view at the top of the file. You can also use the API in the python console. There may be a bug here actually.

I'll check the API then, I don't see any entry in the popup menu when right clicking on the top of the linear view (I guess you mean where it specifies the segments and sections)

Yeah, the UI can modify section semantics, not the segment semantics. I imagine there are not sections defined. You could probably try bv.add_user_section("<section_name>", <section_start_address>, <section_size>, SectionSemantics.ReadWriteDataSectionSemantics)

Ok, that was a bit confusing, but I managed to change that section (yes, there were sections defined, matching 1:1 with the segments). When I changed that section to be writable, BN marked it as such and reanalyzed my whole target, but sadly the same behavior continues.

So after re-creating the code segment manually and assigning write permissions to it, this worked as expected, so I think this can be closed, unless you still think there is a bug somewhere @bpotchik ?

Missed that this issue has been resolved.


Copr builds fail for epel-7 and epel-6

Since yesterday 2022-08-02, approximately 14:30 packages for epel-6 and epel-7 fail to be build for Convert2RHEL PR's.
Building packages for epel-8 works fine.
See https://copr.fedorainfracloud.org/coprs/g/oamg/convert2rhel/build/4698072/
There were no issues with packages being built for main at that time
See https://copr.fedorainfracloud.org/coprs/g/oamg/convert2rhel/build/4698179/
Start: buildsrpm
Start: rpmbuild -bs
error: bad date in %changelog: Tue Aug 02 02:31:02 UTC 2022 Packit<EMAIL_ADDRESS>- 0.26-1.20220802143102718182.pr451.28.g33894f1
Building target platforms: x86_64
Building for target x86_64
Finish: rpmbuild -bs
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/epel-6-x86_64-1659450720.702706/root/var/log/dnf.rpm.log
/var/lib/mock/epel-6-x86_64-1659450720.702706/root/var/log/dnf.librepo.log
/var/lib/mock/epel-6-x86_64-1659450720.702706/root/var/log/dnf.log
Finish: buildsrpm
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-6hm9s8u6/convert2rhel/convert2rhel.spec) Config(epel-6-x86_64) 0 minutes 57 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
ERROR: Command failed:
 # bash --login -c /usr/bin/rpmbuild -bs  --target x86_64 --nodeps /builddir/build/SPECS/convert2rhel.spec

Copr build error: Mock build failed

do I get it correctly that the date is the problem?
error: bad date in %changelog: Tue Aug 02 02:31:02 UTC 2022 Packit<EMAIL_ADDRESS>- 0.26-1.20220802143102718182.pr451.28.g33894f1

do I get it correctly that the date is the problem?

It seems so, it's in the extended format and the version of RPM in EPEL 6 and 7 is most likely not able to parse it.

The support was added in https://github.com/rpm-software-management/rpm/commit/57f94a582602f0353cdb17a02dc12c4461d4f32d (so it's in 4.14.0 and up) and RPM version in EPEL 7 is 4.11.3.

It does seem so.
Weird thing is it does not have any problem with parsing for builds after merging to main
Start: buildsrpm
Start: rpmbuild -bs
warning: Could not canonicalize hostname: aws-x86-64-normal-prod-01942800-20220802-151250
Building target platforms: x86_64
Building for target x86_64
Wrote: /builddir/build/SRPMS/convert2rhel-0.26-2.20220802152613756774.main.28.g03da14c.el6.src.rpm
Finish: rpmbuild -bs
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/epel-6-x86_64-1659454027.796971/root/var/log/dnf.rpm.log
/var/lib/mock/epel-6-x86_64-1659454027.796971/root/var/log/dnf.librepo.log
/var/lib/mock/epel-6-x86_64-1659454027.796971/root/var/log/dnf.log
Finish: buildsrpm
INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-mq97lzgj/convert2rhel/convert2rhel.spec) Config(child) 0 minutes 54 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot

I'm assuming this is something we have changed in Packit that caused the breakage, is that correct? Well actually, is the date coming from the specfile library?

Well actually, is the date coming from the specfile library?

I don't think so, it defaults to the old format: https://github.com/packit/specfile/blob/1ba57311637d41f9fdbe5f85ee2f8bd96abc8618/specfile/specfile.py#L273-L279

Well actually, is the date coming from the specfile library?

Actually, you are right, I just tested it locally with convert2rhel spec and it does generate a new entry with extended timestamp format :frowning_face:

I've opened https://github.com/packit/specfile/issues/76.

Wow, that was a fast fix :D now to get it to production

Unfortunately, the fix didn't solve the problem https://github.com/TomasTomecek/convert2rhel/pull/3
@nforro confirmed it works as expected locally, but once we get inside Packit, the problem persists. We don't know right now where the problem is exactly.
My plan right now is to workaround the issue by changing c2r's packit.yaml

Update: we have proposed a workaround that is merged (see above). Hence dropping high-prio
Work on our side to do:

[ ] Build ogr and specfile in packit-stable Copr project
[ ] Install worker image using that Copr packit-stable repo
[ ] Install our stack using the packit-stable Copr repo inside the Copr env for SRPM builds ( https://github.com/packit/packit-service/issues/1562 )
[ ] Release specfile

Related: packit/specfile#80

I'd like to note that the workaround https://github.com/oamg/convert2rhel/pull/556 solved the issue partially as now the copr builds don't have a distinct NEVRA which is something we're expeting when testing manually. For example instead of convert2rhel-0.26-1.20220805122400334947.pr554.44.g66a5b9a describing what PR the build relates to we now have convert2rhel-0.26-1.
It's nothing critical yet not ideal. Instead of some automation we have around the package NEVRA, we can go to the GitHub PR, get a link to the specific copr build from the Packit dashboard, copy the copr build rpm URL and paste it to a yum install call.

adding high-prio back as this now affects more teams
we now fully understand scope of this problem, and will refine tasks and prioritize them accordingly
please let us know if you are blocked by this

please provide karma for the fc35 update of python-specfile https://bodhi.fedoraproject.org/updates/?search=python-specfile
once it lands in stable, the update should land in Copr SRPM build chroot thus resolving this problem

I just verified that for the SRPM builds that happen in Copr (you set srpm_build_deps in your packit.yaml), the issue is resolved: https://github.com/redhat-performance/tuned/pull/455
For legacy SRPM builds that happen inside Packit infra, the fix will be available Tue morning per our usual production update.
Please reopen if you are still affected by this or found a new case where the changelog is parsed incorrectly. Thank you all for your patience!

We have srpm_build_deps in our packit.yaml so reverting https://github.com/oamg/convert2rhel/pull/556 should solve this issue for us, right?

Whoopsie, this one is totally resolved.


[Bug]: Failing to convert AutoScalingGroup.launchTemplate from list to array

Is there an existing issue for this?

[X] I have searched the existing issues

Affected Resource(s)

autoscaling.aws.upbound.io/v1beta3 - AutoscalingGroup

Resource MRs required to reproduce the bug
apiVersion: autoscaling.aws.upbound.io/v1beta3
kind: AutoscalingGroup
metadata:
  name: "dev-us-east-1-private-consul"
  namespace: "dev"
  labels:
    name: "dev-us-east-1-private-consul"
    environment: "dev"
    region: "us-east-1"
spec:
  forProvider:
    # prettier-ignore
    desiredCapacity: 3
    # prettier-ignore
    maxSize: 3
    # prettier-ignore
    minSize: 3
    launchTemplate:
      - version: "$Latest"
        idSelector:
          matchLabels:
            name: "dev-us-east-1-private-consul"
            environment: "dev"
            region: "us-east-1"
    region: "us-east-1"
    tag:
      - key: Name
        value: "dev-us-east-1-private-consul"
      - key: environment
        value: "dev"
      - key: managed-by
        value: crossplane
    vpcZoneIdentifierSelector:
      matchLabels:
        subnet-type: "private"
        environment: "dev"
        vpc-name: "dev-us-east-1"

Steps to Reproduce
Apply the above manifest (with a matching template/subnet)
What happened?
Missing launchTemplate property on the converted v1beta3 resource.
Relevant Error Output Snippet
Message:               create failed: async create failed: failed to create the resource: [{0 creating Auto Scaling Group (dev-us-east-1-private-consul): operation error Auto Scaling: CreateAutoScalingGroup, https response error StatusCode: 400, RequestID: 7ebe95af-e405-4fcb-9a7a-dc53a888d835, api error ValidationError: Valid requests must contain either LaunchTemplate, LaunchConfigurationName, InstanceId or MixedInstancesPolicy parameter.  []}]

Spec
Spec:
Deletion Policy:  Delete
For Provider:
Desired Capacity:  3
Max Size:          3
Min Size:          3
Region:            us-east-1
Tag:
Key:    Name
Value:  dev-us-east-1-private-consul
Key:    environment
Value:  dev
Key:    managed-by
Value:  crossplane
Vpc Zone Identifier:
subnet-12345
subnet-67890
subnet-45678
Vpc Zone Identifier Refs:
Name:  dev-us-east-1c-private
Name:  dev-us-east-1b-private
Name:  dev-us-east-1a-private
Vpc Zone Identifier Selector:
Match Labels:
environment:  dev
subnet-type:  private
vpc-name:     dev-us-east-1
Init Provider:
Management Policies:
*
Provider Config Ref:
Name:  default

### Crossplane Version

1.16.0

### Provider Version

1.8.0

### Kubernetes Version

Client Version: v1.30.1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.4-eks-036c24b

### Kubernetes Distribution

EKS

### Additional Info

Works fine if I manually change it and switch to the v1beta3 resource myself with the requisite resource changes.

See https://crossplane.slack.com/archives/C05E0UE46S2/p1720556633009269 for more discussion.

Maybe related: https://github.com/crossplane-contrib/provider-upjet-aws/pull/1332

Yeah I'm aware, but I was using the v1beta1 object. That should either:

be allowed to work as is
be migrated to the correct format

Currently it is silently ignored.

In the example you gave, you used apiVersion: autoscaling.aws.upbound.io/v1beta3, I could not fully understand your issue.
You can continue to use the v1beta1 version as is, and if you have existing resources it should not be affected.


plots: copy edit walkthrough and dashboard tooltips

Should I feel free to merge approved PRs in this repo? Thanks

@jorgeorpinel I'll review it, haven't had time yet


Adds support for multiple debug servers

N.B. I removed the httpProtocol and domain pair in favor of a combined domain that includes the protocol.  This was easier than having these separate, esp. since they were never used separately.
Your .env file should now look like this:
NINJA_CLIENT_KEY=[ninja key]
NINJA_CLIENT_SECRET=[ninja secret]
NINJA_DOMAIN=https://ninja

STAGE1_CLIENT_KEY=[stage1 key]
STAGE1_CLIENT_SECRET=[stage1 secret]
STAGE1_DOMAIN=https://stage1

STAGE2_CLIENT_KEY=[stage2 key]
STAGE2_CLIENT_SECRET=[stage2 secret]
STAGE2_DOMAIN=https://stage2

# all stage servers
STAGING_SEGMENT_KEY=[staging segment key]

PROD_CLIENT_KEY=[prod key]
PROD_CLIENT_SECRET=[prod secret]
PROD_DOMAIN=https://ello.co
PROD_SEGMENT_KEY=[prod segment key]

Instead of toggling a debug server on/off, the user is presented with an alert that lets you choose which server you want to use.  Then the app is force-crashed, and next time the app is launched the selected server will be used.
Finishes #141335381

Test Suite 'All tests' passed at 2017-03-15 16:53:25.749.
	 Executed 2577 tests, with 0 failures (0 unexpected) in 239.655 (240.852) seconds


Add ko.json to support Korean localization

Hello maintainers!
Thanks for this nice project.
I am one of the maintainers of the CNCF Cloud Native Glossary Project
We are trying to apply the PageFind to our website.
It seems Korean UI strings are not supported yet. Hope to add Korean ko.json.
Please note that I am a native Korean and contributing to several Korean localization projects. :)

Fantastic! Thank you 🙏
Merging, and will be included in Pagefind's next release (hopefully soon!)

Thanks @bglw
looking forward the next release!
Have a nice day!

Released in released in v1.1.0, thanks again!


Added code for custom CSS injection through the options variable

CSS can now be injected into the html template. If options.css is defined as a string of css, it'll be passed in. By being an optional attribute of options, it's not intrusive on the expected behavior of the functions.

Hi, thank you for a pull request, it is a very interesting feature.
Could you please tell me why do you need this :)?
You have a couple options now, actually, you can:

require css you want to override in the same way as smalltalk does and then build a bundle with webpack.

here is css with all styles and you can add your own css after smalltalk load with help of load.js if you do not use webpack.

Closed due to a long time of inactivity 🏝


AssertionError when using declared symbols in terminal

I built a custom lexer which generates a custom token stream. I wanted to use the tokens which come from the token stream just like regular terminals in combination with other terminals, but then I encountered this error:
File "venv\lib\site-packages\lark\load_grammar.py", line 739, in resolve_term_references
    assert term_value is not None
AssertionError

As a minimal broken example I can modify two lines in the custom_lexer.py example:
from lark import Lark, Transformer, v_args
from lark.lexer import Lexer, Token

class TypeLexer(Lexer):
    def __init__(self, lexer_conf):
        pass

    def lex(self, data):
        for obj in data:
            if isinstance(obj, int):
                yield Token('INT', obj)
            elif isinstance(obj, (type(''), type(u''))):
                yield Token('STR', obj)
            else:
                raise TypeError(obj)

# HERE I CHANGED data_item: STR INT* to data_item: COMP and defined it below
parser = Lark("""
        start: data_item+
        data_item: COMP

        COMP: STR INT*

        %declare STR INT
        """, parser='lalr', lexer=TypeLexer)

class ParseToDict(Transformer):
    @v_args(inline=True)
    def data_item(self, name, *numbers):
        return name.value, [n.value for n in numbers]

    start = dict

def test():
    data = ['alice', 1, 27, 3, 'bob', 4, 'carrie', 'dan', 8, 6]

    print(data)

    tree = parser.parse(data)
    res = ParseToDict().transform(tree)

    print('-->')
    print(res) # prints {'alice': [1, 27, 3], 'bob': [4], 'carrie': [], 'dan': [8, 6]}

if __name__ == '__main__':
    test()

I don't see any reason why this should not be possible, but I am also absolutely no expert in this field. In any case, it would make my life so much easier.

I consider it a bug that you got such a cryptic error message.
But Lark is works fine with the correct input. If you rename COMP to _comp it should work.
You're getting an error because the parser is trying to construct a terminal from the terminals you declared. But it can't because they are not defined yet. Change COMP to a rule bypasses this issue.

I kind of understand, but this seems to be a limitation of Lark. Declared terminals should just work like normal terminals even if it can't already construct them during the loading phase. During the parsing it just has to wait for the correct token instead of searching a particular string. Am I mistaken by that? Terminals as collection of atomic tokens and rules as aggregation of other rules and terminals. This _comp workaround feels wrong.

Terminals in lark are atomic. This means they are represented by a single regex. This now means that compound Terminals like the own you showed are joined together into a single regex. Of course if lark can't see the definition of the Terminals because they are %declared lark can't do that.
It sounds like you are writing your own lexer. In that case you can do whatever you want. %ignore is not handled by the parse, but by the lexer.

@SkryptX You might be a little confused about how parsers and lexers work.
The lexer's job is to transform text into a bunch of tokens (as defined by terminals). Those tokens are the API it provides the parser. So if you define COMP, the parser expects to see COMP, and not INT or STR which don't appear in any rule, so the parser doesn't know about them.
The job of a custom lexer is to provide the parser with terminal that it knows.
What you're looking for, perhaps, is another layer between you and the parser, that will be able to parse token fragments into whole tokens, before passing them to the parser.
It might be possible to write, but, what's the point? Just pass the fragments to the parser, it will be simpler and more efficient.

@SkryptX I really have no idea why you would need more than Lark already provides. Can you explain it more clearly?
Why is it so important to lazy-compose terminals when you can use rules?

P.S. %ignore simply throws away the tokens. i.e. not yield.


Adding A Nobody's Way Up to an Exploration Hero (MAL 57646)

Updated tvdbid for A Nobody's Way Up to an Exploration Hero (MAL 57646)

There's a problem with your commit, so I just went ahead and added it for you:
https://github.com/varoOP/shinkro-mapping/pull/48

Thanks! @happytaz


Script for Currency Converter

I request you to add a Script for Currency Converter , as another automated helping mini-project.
Hence i will like to send a pr for the following

added a PR in #87

should have added the labels before merging.

added a PR in #99


Faster printing

The lpr command is able to print many files much faster using wildcards. the barcode portlet already creates a timestamped folder of each batch of barcodes that are created. the command should be changed to something like lpr [...] timestamp+"/*"

Once portal-testing is up again, we should deploy it there

Ok, merged into development #7

Since this was merged, can this issue be closed?

indeed it can


Behaviour of media_controller.block_until_active

@armills
In relation to https://github.com/balloob/pychromecast/pull/145, I'm having a bit of a problem with block_until_active's behaviour. For this project, I need to be able to block until media_controller is ready but not necessarily playing. Before 0.8.0, I could have used update_status(blocking=True), but that does not seem to be available anymore. Any ideas?
For reference, see https://github.com/skorokithakis/catt/issues/12#issuecomment-276869698.

@dominikkarall Might be able to answer better, since this was removed with #131. Can you link to your usage so I can understand it better? Can you make use of the update_status callback to achieve what you're trying to do?


Multiple iPhone Apps

Is it possible rapns to work with multiple iPhone Apps

Not currently, thought it is on my todo list.


Navigation: Make certain pages more accessible

Certain pages may not easily accessible. Most notably, these pages

About Us - https://beta.advisory.sg/about-us/
Team Page - tbd
Press Releases - https://beta.advisory.sg/press-releases/
Reports - https://beta.advisory.sg/reports/

We could try to add some in the nav bar (especially more important ones such as About Us)

For some of the less important links (eg. Press Releases & Reports), we could try putting them at the footer

The Footer/ Nav Bar may be tweaked/ redesigned as needed

One note on the dropdown - there's no multi-level navigation available (which makes websites harder and more confusing to navigate), but there's an option to display extra navigation links under a submenu. Personally I think the navigation links should either be displayed in full or under a drawer (on smaller screens), as a mix of both would cause some pages to be more concealed than others. In any case, the navigation should contain only a small number of links most relevant to users (rest can be placed under footer if they're not really important, e.g. privacy policy)

weien

To be discussed further

About should be in navigation bar
Add to footer
Press releases and Reports should be found somewhere (currently doesn't exist)
Press releases & Reports would be under "Get Involved"

https://docs.google.com/spreadsheets/d/1_oezcWKessjw0FR03szSDZJWn3RUq5atp31vkorsctQ/edit#gid=0

This is not a very concrete issue, so I'll close it for now
Can be reopened when we have more feedback


add Planetscale

this pull request is for issue number #57
I added tsup because currently @planetscale/database and kysely-planetscale only support esmodule. and I don't know how to use tsc.
Sorry I didn't test it because I was in a hurry and also I got this error Cannot use import statement outside a module when I tried to test it. But I got it working.
This is not perfect but I hope it helps
-edit
adding test for planetscale is not going to work because of this ts-node-dev's issue which is related to esm.

it turns out Cannot use import statement outside a module is because I changed the tsconfig settings to esnext, so I revert it back

Code looks nice, but I guess one question is whether this should be part of kysely-codegen, or if we should make it easy to add custom plugins. Considering that kysely-planetscale is a custom dialect and that it's probably not a scalable solution to include every possible dialect in the core, I am leaning towards the latter option.
That means we'll need to focus on making a (minimal) plugin system viable though.

Yes you are right.. maybe we could also make the official dialects (mysql & postgres) as a "plugin" as well instead of specifying --dialect

Not unreasonable, but I think mysql/postgres/sqlite might continue to be part of the core as long as they are in the kysely core (and for the sake of making it easy for most users to start). But who knows in the future.
But at the very least, custom plugins should become a breeze to use.


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

doc/README.hbs

docs(README): update from template

Coverage remained the same at 69.388% when pulling 92fe882080479c167a51fd56dba79e3ea2d6f93f on template-sync-1 into ee201358a90def37d1f1d154812f70c4ae3f9972 on master.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #138   +/-   ##
=======================================
  Coverage   69.79%   69.79%
=======================================
  Files           2        2
  Lines          96       96
=======================================
  Hits           67       67
  Misses         29       29

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee20135...92fe882. Read the comment docs.


Cannot read property 'layout' of undefined

I'm trying to debug VS Code's source code, and I'm running into some issues. To try to fix the below problem, I tried re-cloning the repo, running yarn cache clean, deleting node_modules, and delete .vscode-oss-dev. Nothing seemed to help. Please help. Thank you.

VSCode Version: Latest (f2a654c782)
OS Version: macOS 10.15.5

Steps to Reproduce:

Forked the source at Latest (f2a654c782)
Ran yarn to install dependencies
Ran yarn watch to build and watch
Ran VS Code launch configuration to launch an instance of VS Code
See errors:

Does this issue occur when all extensions are disabled?: Yes/No

/duplicate 100783


How can I check if a user is seeking the seekbar?

How can I check if a user is seeking the seekbar?
Is it possible using the YouTubePlayerSeekBarListener ?
I am just using the default webui player

Hi, I don't think it's possible without adding custom methods the the Javascript code.

Well the only option I have now is to add the custom seekbar In YouTubePlayerSeekBar I need access to  seekBarTouchStarted but its private so I forked the repo and made some changes and added jitpack to my project but I am getting build errors
https://jitpack.io/com/github/Acidrai0/android-youtube-player/d3155be9f3/build.log
How can I resolve this?

It's not recommended to use the native UI. You should stick to web ui (the default) to avoid risk breaking YouTube terms of service.


Heatmap itself is not representative

It woould be cool if the color grading could be set up differently because for now my scheme makes no sense with overused Spacebar and almost white "Q" with 4000+ presses

I suppose the color grading options could also be exposed in configuration file, so that they can at least be overridden by the user. For example, the current default heatmap settings are: blue from 25%, green from 55%, yellow from 85% and red from 100% (percentage being the ratio of a key count compared to the most frequent key count).
However, that would not really solve the problem, as one would need to start tailoring the settings to fit the data, but the data changes..
Maybe a solution would be to constrain the topmost one or two keys if they are way more frequent than the rest, then they would not skew the results so much..
Out of curiosity, what are the top 10 keys from your view? From some bigger data in my own logs, spacebar is 7th and the topmost is Left Ctrl:

My top ten certainly differs from yours since I'm russian and do not
program anything, the most frequently used keys are Space, J and T
[image: image.png]
пт, 12 апр. 2024 г. в 17:07, Erki Suurjaak @.***>:

I suppose the color grading options could also be exposed in configuration
file, so that they can at least be overridden by the user. For example, the
current default heatmap settings are: blue from 25%, green from 55%, yellow
from 85% and red from 100% (percentage being the ratio of a key count
compared to the most frequent key count).
However, that would not really solve the problem, as one would need to
start tailoring the settings to fit the data, but the data changes..
Maybe a solution would be to constrain the topmost one or two keys if they
are way more frequent than the rest, then they would not skew the results
so much..
Out of curiosity, what are the top 10 keys from your view? From some
bigger data in my own logs, spacebar is 7th and the topmost is Left Ctrl:
image.png (view on web)
https://github.com/suurjaak/InputScope/assets/719382/82cce247-e9b4-4d12-a7b3-f99bb6fd4c79
—
Reply to this email directly, view it on GitHub
https://github.com/suurjaak/InputScope/issues/32#issuecomment-2051831763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44HBPTZYJSK2KEKEENA2ODY47TA3AVCNFSM6AAAAABGCX47NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRHAZTCNZWGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

FYI, I'm currently experimenting with using a log scale for the keyboard heatmap, so that superfrequent keys do not fade out lesser keys so strongly.
The result is looking much better for me. And, rather different as well, e.g. before:

vs after:

I will tinker with this a bit and make a new release, in the not too far future.

Very cool!
See näeb välja täpselt nii, nagu peaks, minu arvates
сб, 13 апр. 2024 г. в 19:41, Erki Suurjaak @.***>:

FYI, I'm currently experimenting with using a log scale for the keyboard
heatmap, so that superfrequent keys do not fade out lesser keys so strongly.
The result is looking much better for me. And, rather different as well,
e.g. before:
image.png (view on web)
https://github.com/suurjaak/InputScope/assets/719382/f5369d27-f652-45fa-8d13-4bc510b8e01c
vs after:
image.png (view on web)
https://github.com/suurjaak/InputScope/assets/719382/d414ae9c-09aa-49a1-b0ee-18c4bf8d5ccf
I will tinker with this a bit and make a new release, in the not too far
future.
—
Reply to this email directly, view it on GitHub
https://github.com/suurjaak/InputScope/issues/32#issuecomment-2053697234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44HBPXYRSPGGDSHENYODL3Y5FN2LAVCNFSM6AAAAABGCX47NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJTGY4TOMRTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

The new v1.11 release should show the keyboard heatmap in better highlighting.
Also, if you like, you can now override the heatmap colours. By specifying a custom gradient for heatmap display options in configuration file:
HeatmapDisplayOptions = {"keyboard": {"gradient": {0.25: "blue", 0.55: "green", 0.85: "yellow", 1.0: "red"}}}

The numbers in gradient stand for percentage of total events; so in the default colouring above it starts from blue and ranges through green and yellow towards red. The colour can be any standard web colour, including colour codes like "#FF0000" or "rgb(255, 0, 0)".
The heatmap display options can be applied to specific inputs like "keyboard" or "mouse", more specific event types like "combos" or "clicks", or to all heatmaps if given without nesting.

Amazing, thank you :)
ср, 17 апр. 2024 г. в 20:35, Erki Suurjaak @.***>:

The new v1.11 release should show the keyboard heatmap in better
highlighting.
Also, if you like, you can now override the heatmap colours. By specifying
a custom gradient for heatmap display options in configuration file:
HeatmapDisplayOptions = {"keyboard": {"gradient": {0.25: "blue", 0.55: "green", 0.85: "yellow", 1.0: "red"}}}
The numbers in gradient stand for percentage of total events; so in the
default colouring above it starts from blue and ranges through green and
yellow towards red. The colour can be any standard web colour, including
colour codes like "#FF0000" or "rgb(255, 0, 0)".
The heatmap display options can be applied to specific inputs like
"keyboard" or "mouse", more specific event types like "combos" or "clicks",
or to all heatmaps if given without nesting.
—
Reply to this email directly, view it on GitHub
https://github.com/suurjaak/InputScope/issues/32#issuecomment-2061846787,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44HBPUEZCXOPZMDVX24RODY52XGBAVCNFSM6AAAAABGCX47NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRRHA2DMNZYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


New option: skip to next image via GPIO

Hi Richard,
I have added a new feature to rBoot, because the existing GPIO feature didn't suit my needs. It might be useful to others as well.
Background: I am using rBoot with 2 slots. Firmware updates (downloading and flashing) are performed by the user program, where the active program in slot 0 will flash into slot 1 or vice versa.
In the situation where flashing was succesful (ROM checksum is ok), but the program itself contains a bug, rBoot will keep booting into that new ROM image. If the networking or firmware upgrade code is broken, I'm stuck.
The 'normal' GPIO functionality is no solution here, because it can only boot into a predefined slot. If this slot happens to contain the 'broken' firmware, it doesn't help.
The new option uses GPIO to simply mark the current slot as 'invalid', and lets the existing code search for an other ROM to boot from. In my case, it will find the previous firmware in the other slot, which can be used to re-flash a new (hopefully fixed) image.
Commit f04392b contains the new option mentioned above.
In commit 3c68cc9 I have separated the reading of the GPIO pin from configuring it as an input. In my opinion, the pin should be set as input as early in the boot process as possible, to prevent large currents when the pin is also driven externally. Furthermore, once the pin is configured as an input, there is a lot more time for the voltage at the pin to stabilize at the required level before the pin state is read back.
I couldn't convince Github to exclude bb7421d from the pull request, please ignore it.
Cheers,
Matthijs

Could you please take a look at the 'test' branch. I've implemented your request (slightly differently), please check it meets your needs before I merge with master.

On 03-09-16 14:05, Richard Antony Burton wrote:

Could you please take a look at the 'test' branch. I've implemented
your request (slightly differently), please check it meets your needs
before I merge with master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/raburton/rboot/pull/19#issuecomment-244542704, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ARRvJZ01AnYfsIi-DEUZKsB_GAjuVOfhks5qmWJsgaJpZM4JjCQP.

Thanks Richard, I'm glad that you liked the 'skip to next image' idea.
I have looked through the diff on Github, your implementation looks fine
to me. Of course, mine was a bit minimalistic (to keep the maintenance
effort of a separate branch/patch low), yours is better integrated with
the rest of the code.
I'm afraid that I will not have the opportunity to do a real test in my
esp8266 project for at least the next few weeks. However, looking at
just the code I'm pretty confident that it will fit my application. I'll
leave it up to you whether you prefer to wait for a real test first, or
to merge the test branch into the trunk asap.
One thing which comes to mind right now is: would other users be helped
with an extra compile-time option, so they can choose between skipping
to the 'next' (/romToBoot = romconf->current_rom + //1/) or the
'previous' (/romToBoot = romconf->current_rom - //1/) ROM?
In my situation (with only 2 slots) it doesn't matter, but I can image
that in case of multiple ROM slots, someone would like to skip back to
the previous one instead of skipping forward to the next one.
Of course, one could also solve the same problem by inverting the
direction in which he flashes new ROMs: if the newest ROM is flashed
into /'current-1'/ instead of/'current+1/', then skipping to the 'next'
ROM is actually the previous (most recent) working ROM.
Kind regards,
Matthijs


cqlsh could adjust client request timeout for USING TIMEOUT queries

This is a small suggestion for a user experience improvement. In Scylla 4.4.0, USING TIMEOUT syntax was introduced. However, if you want to execute query with per-query timeout in cqlsh, you must remember to change --request-timeout option:
$ cqlsh <IP_ADDRESS>
cqlsh> SELECT COUNT(*) FROM ks.zrodlo USING TIMEOUT 20m;
OperationTimedOut: errors={'<IP_ADDRESS>': 'Client request timeout. See Session.execute[_async](timeout)'}, last_host=<IP_ADDRESS>

$ cqlsh <IP_ADDRESS> --request-timeout 1200
cqlsh> SELECT COUNT(*) FROM ks.zrodlo USING TIMEOUT 20m;

 count
---------
 9995165

(1 rows)

For better user experience, cqlsh could:

Give a better error message. Currently it prints:

OperationTimedOut: errors={'<IP_ADDRESS>': 'Client request timeout. See Session.execute[_async](timeout)'}, last_host=<IP_ADDRESS>

and there is no suggestion to use --request-timeout flag.

Automatically change client request timeout (or maybe ask the user if they want to change it). I am aware that to do this it could require parsing the query on the cqlsh side (so possibly not worth it).

/cc @psarna (only a suggestion, not that this is important)

@avelanarius cqlsh already parses statements: https://github.com/apache/cassandra/blob/56ea39ec704a94b5d23cbe530548745ab2420cee/bin/cqlsh.py#L970 , and even though USING TIMEOUT is ScyllaDB-specific, USING isn't on its own (https://github.com/apache/cassandra/blob/f28dd90feb215db85ac2e510c5657a49edd46e12/pylib/cqlshlib/cqlhandling.py#L32), so there's a fair chance such validation can be done rather easily.


package manager file?

Hi,
Thank you for this letter template.
Have you seen that typst now has a package manager?  Details are at:
https://typst.app/blog/2023/package-manager/
and as far as I can understand would be as simple as adding some metadata in typst.toml looking like
[package]
name = "typst-letter"
version = "0.1.0"
entrypoint = "template.typ"

and then making a PR to https://github.com/typst/packages

p.s. the guidelines suggest using a specific name for the package, e.g. 'letter-din5008' rather than 'typst-letter'.

as I didn't want to move this into the package structure without your permission, for now I've added it as a local package on my computer.  To this, I still needed a typst.toml file, so here it is if you, or others, need it.
[package]
name = "din5008"
version = "0.1.0"
entrypoint = "din5008.typ"
authors = ["David Voigt"]
license = "MIT"
description = "Letter template conforming to DIN5008."

and you can see I've gone with din5008 as a more specific package name.
This can then be included from a typst file using:
#import "@local/din5008:0.1.0": *

Hi @sje30
I am happy to hear that you apparently found use for this template. Thanks for already supplying the needed .toml file. I will happily add it to this repository and try to submit it to the official package “registry”.

Yes, I've used it for several letters already, and I find it very convenient (and was looking for an alternative to cumbersome latex letters.)

Yes, I've used it for several letters already, and I find it very convenient (and was looking for an alternative to cumbersome latex letters.)

Glad to hear that! Is there anything you encountered, you would like to see changed before I submit it as a package? Some annoyances or further configuration options?

some options that might be interesting, like a logo.  perhaps the only issue I hit so far is that
the "Name Surname" of the writer is the same at the top of the page and when signing off.  I had one letter where I wished I could write something other than my name at the bottom of the page (I wanted to write "Me, on behalf of x,y,z").

Hey! Can I ask about the status of getting this to be a package?
I have looked and it have not been submitted yet.

Oh right! It is recommended not to use packages for templates, for now! That's the reason.
Sorry 🙏 but at least the issue is not somewhat updated.


bindings: nordic,nrf-rtc.yaml: Do not require 'ppi-wrap' property

Looking at the code, this flag was probably made 'required: true' by
mistake. Combining 'type: boolean' with 'required: true' for 'ppi-wrap'
means that all nodes that use this binding are required to have a
'ppi-wrap;' property.
The mistake was hidden by a bug in edtlib (failing to flag missing
'required: true' booleans).

Fix for edtlib bug: https://github.com/zephyrproject-rtos/zephyr/pull/19482
That one currently fails CI because of this.


Output issue

I 've tried to run stan_BA18_f1.00hz_NGAWest2CA_compute_coeffs and i don't have the ../output/NergEASGMM_f1.00hz file
this is the cmd error ''FileNotFoundError: [Errno 2] No such file or directory: '../../data/output/NergEASGMM_f1.00hz/NergEASGMM_f1.00hz_NGAWestCA_laten_var_unbound_hyp_stan_posterior.csv''

Did you first run stan_BA18_f1.00hz_NGAWest2CA_unbounded_hyp.py to estimate the coefficients at the known locations? stan_BA18_f1.00hz_NGAWest2CA_compute_coeffs.py computes the non-ergodic coefficients at the new locations based on the coefficients at the existing locations. I will write an instructions document to explain what each function does.

The file ’stan_BA18_f1.00hz_NGAWest2CA_unbounded_hyp.py‘ didn't find it

I apologize for this, I uploaded stan_BA18_f1.00hz_NGAWest2CA_unbounded_hyp.py
Please let me know if any issue persists

Added instructions.Rmd which contain brief instructions on running the two scripts.

Added instructions.Rmd which contain brief instructions on running the two scripts.


Correct some status update oversights

This addresses multiple issues:

It brings the life-cycle of the Available condition in line with that of Completed. Both are now created false when the domain is recognized by the operator. (OWLS-93193, OWLS-94048)
It defines all servers shut down (such as start policy = NEVER) as Completed/true (OWLS-93493)
It corrects a bug in the detection of ReplicasTooHigh (OWLS-93692)

I verified the OWLS-93493 with this branch. When the serverStartPolicy is set to NEVER in DOMAIN level, the conditions have the expected result. However when the serverStartPolicy is set to NEVER in CLUSTER level, the condition type Completed is still false.

I verified the OWLS-93493 with this branch. When the serverStartPolicy is set to NEVER in DOMAIN level, the conditions have the expected result. However when the serverStartPolicy is set to NEVER in CLUSTER level, the condition type Completed is still false.

Thanks; I will try that case.

@xiancao can you try your case again?

@xiancao can you try your case again?

It's working now.

Converting to draft, as I have found a couple of cases that I missed.

Fixing the ReplicasTooHigh case is going to require a fair bit of work, as we now need to do some processing in the scheduled status thread that was previously not needed. For that reason, and since Dongbo needs some of these changes, I would like to merge this now and defer the rest of the work to a different PR.

Russ: Fixing the ReplicasTooHigh case is going to require a fair bit of work, as we now need to do some processing in the scheduled status thread that was previously not needed. For that reason, and since Dongbo needs some of these changes, I would like to merge this now and defer the rest of the work to a different PR.

Tom: Sounds good to me, assuming the outage is tracked via JIRA & "Known Issue". I'm passing my sign-off off to Dongbo & Anil, as they're more familiar with Operator internals.

Yes, OWLS-93692 tracks the issue and is not closed by this PR.


Add page type to body class

Why ?

Because we will need to provide different styling based on page type, while the DOM structure roughly remains the same.


Introduce a logger

I see that the project uses System.out to print out messages, for example:
https://github.com/stevespringett/nist-data-mirror/blob/8f1faec3985fd17fd8d2b97aa66b4690cd542ada/src/main/java/us/springett/nistdatamirror/NistDataMirror.java#L116
As a result, an application that uses the library doesn't have much control over this messages. It would be better to use a logger. If this improvement sounds good, I can open a pull request that introduces log4j. Please let me know what you think.

Yes, that sounds like a good improvement.


Introduce non-libstd socket builder methods

Motivation
#1029 removed the net resources APIs to match those of libstd. This change also allowed Mio to remove it's dependency on net2 which was used to provide these methods.
As part of the Mio update in Tokio--and mentioned briefly in the other issues--these methods would be helpful to provide again. For example, they are currently removed as part of the Mio update PR in Tokio.
socket2-rs/net2 provide a lot of additional methods that Mio does not really need and reintroduces a dependency when the syscalls would be fairly straightforward to implement directly. That being said, it's a dependency that can be relied on for the things we would need it for.
Alternatively, a new API could be introduced that provides builder methods for sockets (such as set_keepalive/keepalive/set_ttl/etc.) This approach would not introduce a new dependency. Something along the lines of providing a TcpSocket that has these methods and is consumed with a connect -> TcpStream.
Speaking with @carllerche offline about this I think the second approach of introducing something along the lines of TcpSocket builder is what Mio should move forward with, but there is more design conversation that should go into it.

I've outed thing opinion before, but I'll repeat it here. I don't think it wise to duplicate the effort of a net2/socket crate. We already have the FromRawFd/FromRawSocket and from_std implementations that allow for advanced usage of all our net type (not just TcpStream, as the other types also have useful options that the std lib versions don't provide).
In the past I've also tried adding a way to set options on TcpListener, see https://github.com/tokio-rs/mio/pull/1068. I think it would be best if we would add the required methods to std lib instead, then everybody can benefit.

We now have TcpSocket and #1381 track switching to socket2.


Update header.js with comments

Motivation
Which issue does this fix? Fixes #issue number
If no issue exists, what is the fix or new feature? Were there any reasons to fix/implement things that are not obvious?
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[x] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
If manual testing is required, what are the steps?

Hi @. There's no added value in this pull request.
If you want to contribute to Hacktoberfest, please feel free to pick any of the hacktoberfest labeled issues with no assignee.


Fix backup worker crashing master on interruption

When a backup is interrupted, there is a chance that the resume callback cannot be canceled and thus happens after the server is already resumed by the journal reload process. While it makes sense for backup to crash the master if resume fails to complete and master cannot accept new journal entries, it is completely fine for master to continue if backup tries to resume an already resumed journal. This change updates the journal to not throw if someone attempts to resume after the journal is already resumed.

@gpang @LuQQiu PTAL.

alluxio-bot, test this please

No need to rerun tests since the integration tests passed for twice and only failed for the third run

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.4 please.


See if functions in Sim.js can be made less static

Describe the function you'd like to see added to CookieMonster
Following #592 we should check if other functions (notably CM.Sim.CalculateGains()) can also us CM.Sim.ReplaceFunction().
However, this does not have priority over implementing the last things left for version 2.031.4 and I have therefore scheduled it for the version after it.

With the new rewrite to modules this is no longer really feasible.


JsonHttpResponseHandler failure Exception handling issue

Hi Team,
I am facing this error. Every time when response not come.. Please handle this on api if response is null then print message instead of exception.
onFailure(int, Header[], String, Throwable) was not overriden, but callback was received
org.json.JSONException: Response cannot be parsed as JSON data
at com.loopj.android.http.JsonHttpResponseHandler$1$1.run(JsonHttpResponseHandler.java:158)
at android.os.Handler.handleCallback(Handler.java:746)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5443)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)

if you trying to print response in onFailure it might have issue. Check for null 1st and if null..just print throwable.toString()

Hi Team, I have the same problem
onFailure(int, Header[], String, Throwable) was not overriden, but callback was received
org.json.JSONException: Response cannot be parsed as JSON data
at com.loopj.android.http.JsonHttpResponseHandler$1$1.run(JsonHttpResponseHandler.java:158)


offsets not being applied

Using this markup in Inky
<columns small="12" large="8" class="large-offset-4">
The class is applied but style is overwritten by column padding.

Fixed via fb5e796f23455aac1e03ad9c281f5dc8a0148c8a


Performance issue for NYUv2

Thank you for your excellent contribution!
I have a question about the performance of MTAN with PCGrad.
In my experiment, the result of NYUv2 is very different from the PCGrad official performance (although I not used UW in this experiment)

(sorry for this image to very small)
Also, when I experimented to the resnet50-HPS without weighting method, the result is beyond the MTAN official performance.

I tried your official training command line in all cases and used the dataset in your Dropbox.
Is that result the right phenomenon?
Thank you in advance!

The SegNet is used as the backbone network in the original PCGrad paper. While we use the DeepLabV3+ (ResNet50 with dilated convolution + ASPP) as the backbone here, which achieves better performance than SegNet.

Thank you for your answer!
Is there SegNet architecture in this library?
The SegNet is not in the LibMTL model directory.
Is not supported in the current version?
Or, is the same architecture when I tried the supported command-line below for the original MTAN with SegNet?
python train_nyu.py --weighting DWA --arch MTAN --gpu_id 5 --scheduler step --train_bs 4

LibMTL does not support the SegNet backbone network. MTAN is orthogonal to the backbone network, which means MTAN can combine with both SegNet and ResNet50.

Thank you!!


Adds Daru::Vector#match and Daru::Vector#apply_where (issue #175)

Rspec test added, has been written in the older format to main consistency. This will be easier to change while re-writing all tests to modern specifications file-wise. RDoc documentation has also been added. Daru::Vector#match uses Regexp match via the =~ operator.
Tackles issue #175

@v0dro @zverok - Following the discussions on the issues #175 and #174 , #match support has been provided only to Daru::Vector. Do review the PR. :smile:

@v0dro @zverok @lokeshh - Following the discussions on the issues #175 and #174 , #match support has been provided only to Daru::Vector. Do review the PR. :smile:

@zverok @v0dro : Just wanted to remind you about this PR - kindly review whenever you're free. :slightly_smiling_face:

Reviewing it now.

Whats the update with the PR?

Please finish it off ASAP.

@zverok - Please review when you're free. 😄

I think @zverok is busy with refactoring :P


Can't download server.met

Any idea why?
2022-05-10 00:24:51: Logging to stdout enabled
2022-05-10 00:24:51: Initialising aMuleD 2.3.3 compiled with wxBase(GTK2) v3.0.4 and Boost 1.77
2022-05-10 00:24:51: Checking if there is an instance already running...
2022-05-10 00:24:51: No other instances are running.
2022-05-10 00:24:51: *** TCP socket (ECServer) listening on <IP_ADDRESS>:4712
2022-05-10 00:24:51: Created Server UDP-Socket at port 4665
2022-05-10 00:24:51: ListenSocket: Ok.
2022-05-10 00:24:51: Created Client UDP-Socket at port 4672
2022-05-10 00:24:51: Loading server.met file: /home/amule/.aMule/server.met
2022-05-10 00:24:51: Server.met file not found!
2022-05-10 00:24:51: Loading temp files from /temp.
2022-05-10 00:24:51: All PartFiles Loaded.
2022-05-10 00:24:51: No part files found
2022-05-10 00:24:51: No shareable files found in directory: /incoming
2022-05-10 00:24:51: Found 0 known shared files
!2022-05-10 00:24:51: web server running on pid 45
2022-05-10 00:24:51: amuled: OnInit - starting timer
2022-05-10 00:24:51: Asio thread 1 started
2022-05-10 00:24:51: Asio thread 3 started
2022-05-10 00:24:51: Asio thread 2 started
2022-05-10 00:24:51: Asio thread 4 started
2022-05-10 00:24:51: Loading IP filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2022-05-10 00:24:51: Loaded 0 IP-ranges from '/home/amule/.aMule/ipfilter.dat'.
2022-05-10 00:24:51: Loaded 0 IP-ranges from '/home/amule/.aMule/ipfilter_static.dat'.
2022-05-10 00:24:51: IP filter is ready
!2022-05-10 00:24:51: Connecting
!2022-05-10 00:24:51: No valid servers to which to connect found in server list
!2022-05-10 00:24:51: No contacts found, please bootstrap, or download a nodes.dat file.
!2022-05-10 00:24:51: Kad started.
!2022-05-10 00:24:51: HTTP: WARNING: Void response on stream creation
!2022-05-10 00:24:51: HTTP: WARNING: Void response on stream creation
2022-05-10 00:24:51: New external connection accepted
2022-05-10 00:24:51: Connecting client: aMuleweb 2.3.3
!2022-05-10 00:24:51: Invalid response from HTTP download server
!2022-05-10 00:24:51: Failed to download server.met from http://upd.emule-security.org/server.met
!2022-05-10 00:24:51: Failed to download ipfilter.dat from http://upd.emule-security.org/ipfilter.zip
!2022-05-10 00:24:51: Invalid response from HTTP download server

I do not understand why. The URL http://upd.emule-security.org/server.met works fine in my browser and mlDonkey. Could it be a temporary problem? How long has it been going on?

Both URLs are working fine for me. You can try 2 things:

Inside the container you can execute this command to test it => wget http://upd.emule-security.org/server.met
Replace http with https to see if it works.

I tested it in a clean install and it's working as expected.


ARROW-4341: [C++] primitive builders use bufferbuilder

Hmmm, this is a performance regression.

BooleanBuilder seems to be more than 4 times slower with this patch
after
BM_BuildBooleanArrayNoNulls/repeats:2                        789455 us     789468 us          1   648.538MB/s

before
BM_BuildBooleanArrayNoNulls/repeats:2                        172299 us     172302 us          4   2.90189GB/s

Based on this evidence the iterator based unrolled bit generator vectorizes poorly. I just pushed changes https://github.com/apache/arrow/pull/3575/commits/be8442f8574cdc7d6df6f55d8f71136e217be894 reverting some of these changes (but still using TypedBufferBuilder<bool>, so better than before), as well as an option to disable tracking the false count, which we don't care about. For the record, disabling the false count only improved the benchmark from 650 MB/s to 1 GB/s, far less than the original 3GB/s. The compiler just isn't generating very good code for the CPU
If these changes are acceptable I suggest that we merge this patch (once the build is passing) and leave this be for now.

With my changes the perf seems slightly improved from the baseline
BM_BuildBooleanArrayNoNulls/repeats:2                        163077 us     162609 us          4   3.07486GB/s

It seems that there are symbol visibility problems on Windows caused by the PrimitiveBuilder / NumericBuilder collapse, and valgrind problems additionally. I would say to limit how much additional time (say 2 hours or less) you spend on this patch as there's a lot of feature work and bug fixes in the 0.13 backlog.

I moved the entire NumericBuilder<T> implementation to the header file. I think this should make the linker problems go away. I don't expect an application to have a ton of instantiations of these templates so I don't know that it's worth stressing about code size for these until it can be demonstrated to be a problem. The size of arrow-array-test in a release build increased by about 3%.

I reverted some changes and think I fixed the valgrind / Windows / Python failures

Seems there are some correctness issues https://travis-ci.org/apache/arrow/jobs/493616072. @bkietz can you look at the Ruby failure? We should try to reproduce the failure as a C++ unit test

@wesm I'll try to write a unit test which produces the same error

I can't reproduce https://travis-ci.org/apache/arrow/jobs/493915377#L2632 locally

OK, I can take it from here then

Fixed the Ruby test failures and added a C++ unit test that failed.
@xhochy I removed the valid_bytes argument from AppendNulls
https://github.com/apache/arrow/blob/master/cpp/src/arrow/array/builder_primitive.h#L55
If anyone was using this argument, it was not doing anything useful, unless the goal is to append zeroes. I'm not sure if this needs to go through a deprecation cycle. In our codebase it was only being used for internal purposes

+1