Fix Android build failing due to dependencies being built for wrong ABIs

Details
With the PR enabling the new architecture (https://github.com/Expensify/App/pull/13767), we enabled building React Native from source on Android. When building from the command line, --active-arch-only flag is passed to gradle so not all ABIs are built which speeds things up. This caused problem in two libraries:

react-native-live-markdown - https://github.com/Expensify/react-native-live-markdown/pull/284
react-native-quick-sqlite - https://github.com/margelo/react-native-quick-sqlite/pull/41

In both cases, there was a problem with abiFilters field in gradle which was causing them to fail on the linking step. The libs were being build for all ABIs but the relevant .so files from React Native core were only being built for one (arm64-v8a).
Fixed Issues
I don't think one has been created, here's a thread on Slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1712746783190519

$
PROPOSAL:
Tests

Build the app using npm run android.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Adhoc build should be ready soon - asked for a C+ to run through testing https://expensify.slack.com/archives/C02NK2DQWUX/p1712851640475759

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

LGTM, builds locally and markdown tests well on all platforms

This is blocking a lot of people so I'm just gonna merge this now

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

thanks for pushing this through 🚀

🚀 Deployed to staging by https://github.com/arosiclair in version: 1.4.63-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Arrow keys support

sorry, but i want to know, why not support arrow keys, is there a technical bottleneck?

In addition, how do I know if it is my problem or the software problem?

Oh, I see, the focus is on the search box by default. When I enter content in the search box, I can use the arrow keys to select, but ,

it is not available by default.
It is not possible after hiding the search box.

Is it true that I am the only one?

The focus cannot be kept on the search box because it's kept on the list items, so that you can select them with up/down keys and Enter. What would the arrow keys do in that case?

I guess the OP is asking to focus on the list right after opening the popup (instead of only when you have entered something).

It is not possible after hiding the search box.

Not sure what this line means (and from my understanding it's not true)

I guess the OP is asking to focus on the list right after opening the popup (instead of only when you have entered something).

When the popup is opened, the list is already focused so you can press up/down/Enter. Do you see a different behavior?

When the popup is opened, the list is already focused so you can press up/down/Enter. Do you see a different behavior?

Yes, as I have described above, the list is only focused when you have entered something. (I'm using the latest version of Maccy downloaded via the website, it you are interested.)

Can you record a small video showing how the list is not focused when popup is open?
Thank you,
Alex
On Jun 24, 2021, 09:48 -0700, Kid @.***>, wrote:

When the popup is opened, the list is already focused so you can press up/down/Enter. Do you see a different behavior?
Yes, as I have described above, the list is only focused when you have entered something. (I'm using the latest version of Maccy downloaded via the website, it you are interested.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm experiencing the same issue, but this used to work as described in https://github.com/p0deje/Maccy/issues/287#issuecomment-867095626
I'm using the latest Maccy 0.20.1 on the macOS Monterey beta (build 21A5268h), maybe @wqk317 is also using the beta?
Short screencast (at the start, before searching, I'm pressing the up/down keys but nothing happens 😉):

Hm, this looks like a bug and should work correctly.
@wqk317 What OS version do you use?
@rvdsteege Can you share the output of running defaults read org.p0deje.Maccy?

Sure, here is my config (click).
{
    "KeyboardShortcuts_popup" = "{\\"carbonModifiers\\":2304,\\"carbonKeyCode\\":9}";
    "NSStatusItem Visible Item-0" = 0;
    "NSWindow Frame SUUpdateAlert" = "1194 977 620 398 0 0 3008 1667 ";
    "NSWindow Frame com.sindresorhus.Preferences.FrameAutosaveName" = "1192 698 549 591 0 0 3008 1667 ";
    SUAutomaticallyUpdate = 1;
    SUEnableAutomaticChecks = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2021-07-02 07:49:21 +0000";
    SUUpdateRelaunchingMarker = 1;
    avoidTakingFocus = 0;
    enabledPasteboardTypes =     (
        "public.utf8-plain-text"
    );
    hideFooter = 1;
    hideSearch = 0;
    hideTitle = true;
    history = {length = 42, bytes = 0x62706c69 73743030 a0080000 00000000 ... 00000000 00000009 };
    historySize = 200;
    hotKey = "command+option+v";
    ignoredPasteboardTypes =     (
        "com.agilebits.onepassword",
        "de.petermaurer.TransientPasteboardType",
        "Pasteboard generator type",
        "com.typeit4me.clipping",
        "net.antelle.keeweb"
    );
    imageMaxHeight = 16;
    migrations =     {
        "2020-02-22-history-item-add-copied-at" = 1;
        "2020-02-22-history-item-add-number-of-copies" = 1;
        "2020-02-22-introduce-history-item" = 1;
        "2020-04-18-switch-storage-to-core-data" = 1;
        "2020-04-25-allow-custom-ignored-types" = 1;
        "2020-06-19-use-keyboardshortcuts" = 1;
        "2020-09-01-ignore-keeweb" = 1;
        "2021-02-20-allow-to-customize-supported-types" = 1;
    };
    pasteByDefault = true;
    removeFormattingByDefault = 1;
    showInStatusBar = 0;
    supressClearAlert = 1;
}

Ah, I see now. The issue is that you have an Option in your popup hotkey, so when Maccy opens it shows "alternate" menu items and the code highlights non-alternate versions. I'll fi it.

Tried, but removing the Option key from the hotkey does not resolve the issue. Default Cmd + Shift + C does not resolve the issue.

It will work fine if you disable "Paste automatically".

It will work fine if you disable "Paste automatically".

This answers my question, I have that option enabled. However I don't understand why "Paste automatically" interferes with default selection and IMO it shouldn't.

Yes, it is a bug and I need to fix it.

It will work fine if you disable "Paste automatically".

Nope, it doesn't (sorry 😉).
However, I now discovered that first pressing Tab once, the list is focused and I can use the arrow keys like before (with Option in hotkey and Paste automatically enabled). Something must have changed with macOS 12 Monterey...

@rvdsteege Do you mind trying this build and see if it fixes an issue?
Maccy.app.zip

Wow, thank you for the build! Tried it, but unfortunately it does not resolve the issue.
I'm happy with the Tab 'trick', but if there's anything I can do/test to fix this then just let me know.

It seems like there are 2 issues here:

The issue when an improper item gets highlighted depending on the hotkey. This is the one fixed in the build ☝.
Some issue on Monterey where nothing is highlighted at all. I guess I need to install beta to figure out what is going on.

faa3de2 hasn't really fixed it - my mistake

Already noticed https://github.com/p0deje/Maccy/commit/faa3de23489de2dd91d0508d1d9f7372c322bf65 did not resolve the issue and tried fixing the issue myself, but it didn't work out without any Swift knowledge 😉
I can confirm that https://github.com/p0deje/Maccy/commit/e559d575b1ac6a903ca08ec3bc81b71047ac3870 indeed resolves the issue. Thank you @p0deje!

The fix is still bad as it prevents the field from being clicked and used as a regular text field.


adding authentication

Assign me this under JWOC'24

@Pranav-Rastogi1 Welcome to the repo.
Sorry to close this issue.
Make sure to open the issues after coding period starts


Perf: comet should be using pebble

Background
We wrote it, informal didn't want it, now Osmosis has performance problems stemming from comet.  (obviously there's more to it than that but -- I don't think this is inaccurate)

https://github.com/tendermint/tm-db/pulls?q=is%3Apr+is%3Aclosed+pebble
https://github.com/cometbft/cometbft-db/issues/90

Suggested Design
Welp, either we fork cometbft-db (we might already have one) or they finally accept pebble.
Acceptance Criteria
Osmosis should be able to use pebble and it should be faster in every way.

Hey, I think that this ended up in red herring territory.


Add alg_type check in algorithm response.

Fix: https://github.com/DMTF/libspdm/issues/1607
Signed-off-by: Jiewen Yao<EMAIL_ADDRESS>

Please also include a unit test that hits this check.

Done.
Add both requester and responder.
Without check, both tests fail.
With check, both tests pass.


is_numeric matches non-numeric strings

If you call is_numeric with '123 Foo' it matches and returns true. This seems to deviate from standard PHP which returns false.
Here's an implementation which seems to have the behaviors I expected:
    @Runtime.Immutable
    public static Memory to_floating_point(String s) {
        try {
            return new DoubleMemory(Double.parseDouble(s));
        } catch(NumberFormatException nfe) {
            return null;
        }
    }

    @Runtime.Immutable
    public static Memory to_long(String s) {
        return StringMemory.toLong(s);
    }

    @Runtime.Immutable
    public static boolean is_numeric(Memory memory) {
        if (memory.isNumber()) {
            return true;
        } else {
            String asString = memory.toString();
            return to_long(asString) != null || to_floating_point(asString) != null;
        }
    }

Fixed.


Doesn't work

Doesn't work since I updated my streamdeck to the 6.0

Uh oh, I haven’t upgraded, I’ll take a look. Thanks for the heads up.On Nov 15, 2022, at 7:23 AM, jjvaillancourt00 @.***> wrote:
Doesn't work since I updated my streamdeck to the 6.0
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I can confirm that. Since updating to version 6 it stopped working.

This isn't the only stocks plugin that stopped working. I wouldn't be surprised if this had to do with the fact that apparently with Stream Deck 6 CIRS headers started being enforced. I also needed to make some adjustments in a couple of personal plugins in order to unblock them (in one case I need to add an Nginx proxy in front of the REST service to handle the CORS headers logic).

Thank you all for the info. I started looking into this yesterday. Currently the plugin won’t even log to the console. @pedro, I’ll look into the headers as well. I hope to be back in action shortly.On Nov 16, 2022, at 6:53 AM, Pedro Pombeiro @.***> wrote:
This isn't the only stocks plugin that stopped working. I wouldn't be surprised if this had to do with the fact that apparently with Stream Deck 6 CIRS headers started being enforced. I also needed to make some adjustments in a couple of personal plugins in order to unblock them (in one case I need to add an Nginx proxy in front of the REST service to handle the CORS headers logic).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

@pedropombeiro You are right, it is a CORS problem. I was unable to adjust my query to get it to work. The Streamdeck team said there are other plugins affected and they are working on a solution.

@pedropombeiro You were right, it was a CORS issue. Everything will be fixed in the next release of the Elgato software. Also more features in Stonks v1.1.7

With today's release of Stream Deck <IP_ADDRESS>22 it works again. Good job. Thank you.

Working again.
Thank you!

Thank you all for the support. Fixed with the release of Streamdeck 6.0.1(17722).


Upgrading syntax to ES6 and improving converter

I refactored the whole app by upgrading the syntax to the ES6 syntax. We are using create-react-app, so we might as well make use of the ES6 feature to accomplish a cleaner and concise code.
I also changed some UI aspects on the converter component and added some validations to certain situations:

Do not show the Copy to Clipboard button when an invalid JSON is pasted;
Remove the Copied span when the result is an empty string;

I used Prettier to format the code, hope that's ok.
All the tests are still passing, so I think this PR is ready to be merged, if you will.
If there is any problem, let me know.

Thanks for the contribution! Maceió? I'm glad to see other Brazilians here.
About the code style, I prefer the ident with 4 spaces. About the other changes looks nice! Can you change the spaces before merge?

I just committed changing from 2 to 4 spaces in indentation.
Valeu e abraço! Parabéns pelo projeto. 😆

Vlw @arthurdenner


User Agent Required for Github api v3

:+1:

@chelm Any way I can get this merged in? Really would like to drop my fork


Autofix Missing Module Does Not Work On Vim With Coc

Steps to reproduce:

Create a rust project cargo new  --lib mytest.
Put this in src/lib.rs:

mod child;

Put this in src/child.rs:

mod grandchild;

Put the cursor over mod grandchild; and execute (inside Vim) :execute ":normal \<Plug>(coc-fix-current)".
Confirm.
This is going to happen:

rust-analyzer tells coc to create src/child/grandson.rs this requires creating src/child first, which coc doesn't do I think. The lsp spec doesn't seem to specify if you must first create a directory or that directories are automatically created for you as necessary. https://microsoft.github.io/language-server-protocol/specifications/specification-current/#resourceChanges

Closing as upstream issue!


More self-regulation restrictions

Changes

renamed profile page "karma" -> "self-regulation"
removed "karma calculator" -> "self-regulation formula calculator"
invites are disabled when issuer's "self-regulation score" <= 0
when "self-regulation score" < -10 karma votes by the user are revoked (triggered on certain actions)
display active restrictions in profile
minor change in VoteRepository.ts: add voterId and userId for all vote-returning queries

and remove now unnecessary call to UserManager.getByUsername in UserManager

Example restrictions displayed:

Network error when checking an invite of the user with low "self-regulation score":

Calculator after renaming:

Testing:

tested locally on recent dump
tested in debugger

@pazoozoo42 , I addressed the UX issues (although I tried to minimize the effort spent on that, as this page is mostly for internal usage and debug and will be thrown away in the future).
Changes:


Correction for raw affiliation ENS-CNRS UMR 5239, Ecole Normale Supérieure de Lyon, F-69364 Lyon, France

Correction needed for raw affiliation ENS-CNRS UMR 5239, Ecole Normale Supérieure de Lyon, F-69364 Lyon, France
raw_affiliation_name: ENS-CNRS UMR 5239, Ecole Normale Supérieure de Lyon, F-69364 Lyon, France
new_rors: 029brtt94;04zmssz18;02feahw73;01bj4fd12
previous_rors: 029brtt94;04zmssz18;02feahw73
works_examples: W2022777266
contact: fcff71672050082850716465619a4166:7b693800c765d60d3b86d72a3bd5 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Axis value rounding for overridden axes

In order to ensure that the axes finish on a labelled point, dimple will round the axes to the next ticked value, this probably shouldn't be the case for overridden axes.
From;
http://stackoverflow.com/questions/25451092/dynamic-overiding-of-measure-axes-in-dimple-js-causing-floating-droplines/25451479?iemail=1&noredirect=1#25451479

Just ran into this bug myself, is a fix for this planned, or a recommendation on how to work around it?


Command line documentation is wrong

The command line does not accept the arguments documented in README.md.
This:
-exporter.bind_address
-logstash.endpoint

Should be:
--web.listen-address
--logstash.endpoint

Sample usage:
--web.listen-address=:9198
--logstash.endpoint=http://localhost:9600

^ just submitted a new README for this

Just had the same issue. Any plans to merge https://github.com/BonnierNews/logstash_exporter/pull/19 please? :)


Correction for raw affiliation CIRAD, UMR Eco&Sols, F-34398, Montpellier, France; Eco&Sols, Univ Montpellier, CIRAD, INRA, IRD, Montpellier SupAgro, Montpellier, France; World Agroforesty Centre (ICRAF), Yaoundé, Cameroon

Correction needed for raw affiliation CIRAD, UMR Eco&Sols, F-34398, Montpellier, France; Eco&Sols, Univ Montpellier, CIRAD, INRA, IRD, Montpellier SupAgro, Montpellier, France; World Agroforesty Centre (ICRAF), Yaoundé, Cameroon
raw_affiliation_name: CIRAD, UMR Eco&Sols, F-34398, Montpellier, France; Eco&Sols, Univ Montpellier, CIRAD, INRA, IRD, Montpellier SupAgro, Montpellier, France; World Agroforesty Centre (ICRAF), Yaoundé, Cameroon
new_rors: 00b80ez59;03rnk6m14;051escj72;05q3vnk25;05kpkpg04;01kmz4383
previous_rors: 00b80ez59;03rnk6m14;051escj72;05q3vnk25;03dj0nw15;05kpkpg04
works_examples: W2912919478
contact: 24e751d39ac52e36422dfc78b9c948ac:6c6acae53831b5e091a80997c1c8f78b6b18 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Feature/symfony34

This PR updates the symfony components to version 3.4 and updates all forms and middlewares accordingly.
As test coverage is not 100% this will probably require some manual testing by the reviewer, I've tested all forms, but could use an extra pair of eyes

This looks like a stale PR. I would recommend closing it and revisit the topic at a later time (perhaps convert to an issue).

@zghosts If you can re-roll this after deps are updated in the other outstanding PR, I'll at the very least do a code review on the changes soon, probably Monday evening (your time) of next week).


chore: improve docker_cluster script

This PR improves the test/tools/docker_cluster.sh script added in #2597.
Downloaded mongoDB binaries are now stored in a persistent shared volume,
so they don't need to be re-downloaded each time a container is launched.

No longer needed


feat(linter/jsdoc): Implement implements-on-classes rule

Part of #1170

https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/implements-on-classes.md

contexts option is not supported for now.

Try to fix perf issues...!


fix: android sync warning

Summary
Removes a gradle warning with this module
WARNING: The targetSdk version should not be declared in the android manifest file. You can move the version from the manifest to the defaultConfig in the build.gradle file.
Remove targetSdkVersion and sync project
Affected Modules: @react-native-community_audio-toolkit

Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Thank you for your contribution!


add SIP headers and response codes from RFC 6665

Adds SIP types from RFC 6665, the extension for SUBSCRIBE / NOTIFY methods.

Sorry for taking so lang, looks good 👍


PagerDuty: Influxdata integration instructions on pagerduty site are out of date.

Describe the issue here.
Relevant URLs

https://www.pagerduty.com/docs/guides/influxdata-integration-guide/

Tried to follow the instructions at pager duty, but step 3 suggests using controls that have changed.

The current UI selects Events API v2 like this...

@karel-rehor We don't maintain or have access to the PagerDuty documentation. I've looked for a public repository to report this issue to so their documentation team can make the necessary updates, but I haven't been able to find the repository where this documentation is stored.
As there isn't anything our team can do to make these updates, I'm going to go ahead and close this issue.


complex_layout_scroll_perf__timeline_summary average_frame_build_time_millis regressed

It regressed from ~2.4ms to ~2.6ms around https://github.com/flutter/flutter/commit/22ca3f96cabbadbaa242347abdfc27e397070b98 or https://github.com/flutter/flutter/commit/f3e698fba40ce4cddbf3d13d1cbbd3c84d1e396e

The regression is small (10%) so it's hard to pin-point exactly what commit should we blame. We may need a bisection with a lot of driver tests on each commit.
It may also be a device lab issue.

This seems to be solved by https://github.com/flutter/flutter/commit/7742572106eeb40b2dc4d310382fb97a79aa400d


Add to docs input range of confirm_in_blocks

We already enforce it: https://github.com/getlipa/lipa-business-lib/blob/3157022a85f9741ba5697ccb3a46bcc178ead83d/src/wallet.rs#L99
In testing, I verified that values above 25 make the request to electrum fail. The docs mention the possibility of the server not being able to estimate for every confirm_in_blocks but I can't find information on which values it usually can predict.


Dockerfile parse error line 14: FROM requires either one or three arguments

Running, as instructed by README.md, the following command:

docker build --rm --tag deb-builder:bionic .

Results in the following error:

Error response from daemon: Dockerfile parse error line 14: FROM requires either one or three arguments

This is with Docker version 18.09.7, build 2d0083d

This was closed by recent commit a74e235ee5a1f59cc5e697fd60333d07c7489794


Menu always showing on dev even when removed

I have removed Menu.setApplicationMenu(menu); from the menu.js and when packaging the app it is not displaying which is as expected. However when I run in dev mode (yarn dev) the menu is still visible as a default.
Is there a way to hide the menu in dev and packaged?

you can set a default menu to hide this,such as this(in render progress)
const remote = require('electron').remote;
const Menu = remote.Menu;
let menu = new Menu();
    menu.append(new MenuItem({ label: 'xxxx', click: () => {} }))
    menu.popup(remote.getCurrentWindow());

Thanks.
I've actually changed to a borderless design now so don't see the menu anymore anyway.


Feature request related to Franklin.jl

I thought you'd appreciate being informed that I've filed a feature request at Microsoft/vscode#103132 that is essentially a request for Visual Studio Code's default Markdown support to include support for Franklin-enhanced Markdown.

Thanks!

this seems to have fizzled.  I would love for code blocks in an .md file that start ```julia:blockName ...
to get highlighted.  Has any extension been enhanced to do this in vscode?

the issue mentioned above is probably the right place to ask for such things (or discourse) but I expect the answer is "no".
Also bear in mind that even though Julia code blocks might get properly highlighted, the Franklin style
```julia:name
...
```
or
```!
...
```

likely won't be for quite a while as it's not standard Markdown.

Thx for the quick reply!  Franklin is really great.  The VSCode issue you reference above got closed so it seems that path is a dead end... we just need to find someone with the skillset to modify a VSCode extension.
I think it might be as simple as modifying one line in the "Markdown Julia" extension (see code below).  I put in an issue request there even though it does not seem actively maintained:  https://github.com/colinfang/markdown-julia/issues/2
If you know someone who knows regular expressions well, I really think the feature can be added quite easily to the "Markdown Julia" extension.  My guess is the only change is to one or two lines within these 46 lines of the extension's core JSON logic:
{
    "fileTypes": [],
    "injectionSelector": "L:text.html.markdown",
    "patterns": [
        {
            "include": "#fenced_code_block_julia"
        }
    ],
    "repository": {
        "fenced_code_block_julia": {
            "begin": "(^|\\G)(\\s*)(`{3,}|~{3,})\\s*(?i:(julia)((\\s+|:|\\{)[^`~]*)?$)",
            "name": "markup.fenced_code.block.markdown",
            "end": "(^|\\G)(\\2|\\s{0,3})(\\3)\\s*$",
            "beginCaptures": {
                "3": {
                    "name": "punctuation.definition.markdown"
                },
                "4": {
                    "name": "fenced_code.block.language"
                },
                "5": {
                    "name": "fenced_code.block.language.attributes"
                }
            },
            "endCaptures": {
                "3": {
                    "name": "punctuation.definition.markdown"
                }
            },
            "patterns": [
                {
                    "begin": "(^|\\G)(\\s*)(.*)",
                    "while": "(^|\\G)(?!\\s*([`~]{3,})\\s*$)",
                    "contentName": "meta.embedded.block.julia",
                    "patterns": [
                        {
                            "include": "source.julia"
                        }
                    ]
                }
            ]
        }
    },
    "scopeName": "markdown.julia.codeblock"
}


[enhancement]: eufycam 3

Describe the solution you'd like
Hi there,
will the plugin work with the new eufy S330 and Homebase 3?

Usually the security client needs to be updated prior to this plugin. I would follow https://github.com/bropat/eufy-security-client/issues/228


Add h7 power states

Implement power states for STM32H735 and test them in a sample project on the discovery kit.

@benediktibk Thanks for this work. I've performed a first round of comments.
I hope this will help guiding you in this task. I will likely resume review in January now.


Refactor ExternalUser#available_roles into service object

As discussed this would probably better as methods on the respective model classes.


Content translations - v3

Calling this medium assuming that any fixes from translators validating the language as shown in the app on iOS and Android will be taken care of here.

I conducted my own review since we are still trying to get translators access to app. Found a number of items that need to be addressed. For the items requiring translation, can you please send an updated spreadsheet so I can get it over to the translators ASAP?
Translation Issues_round 3.docx

@kevin-sheldon @fahd-arshad I did the following: looked back at the translations file just after we received and applied v2 and compared it with the current version. All of the differences need to be translated, so I'm attaching the file here.
❗ ❗ Very important: Lots of entries have already translation for the other languages, but those need to be verified. There were a bunch of small changes like uppercasing a letter or adding a single word etc. In the same time there might be a couple of entries that might have already been translated but it's very hard for me to be sure so I just included them.
@kevin-sheldon I'll address the above findings when I applied the v3 of the translations. Also note that Privacy Policy is not part of the app, but it's stored in the database cc @segfault
Transaltions v3: covid-alert-ny-translations-v3-original.xlsx

@floridemai what do we need to do about the in-app privacy policy translation? I know that data comes from the server...

@floridemai Can we add the associated line(s) for the new "Submit Feedback" feature?

@helloantoine can you please open up the attached word doc and look at the last image? Transliterations need to be removed for just that one language to be consistent with others.

@kevin-sheldon Removing English transliterations from Bengali is done in https://github.com/project-vagabond/covid-green-app/pull/436 and should be in the next build.
I'm putting together a new spreadsheet of recent English copy changes for translators.

@kevin-sheldon Here is the new spreadsheet for the translators. As Paul said above, many entries already have translations but they need to be re-checked - some are only capitisation changes, some are very subtle changes in wording, some are significant changes in meaning.
It might also be worth mentioning that there are a few items in these that should not be translated because they are read as code by the app:

Text inside double curly brackets, like {{county}} or {{page}}, should not be changed
The round parenthesis part of link blocks like 01-2345-6789 or Translatable link title where round parenthesis immediately follow square brackets. Text inside the square brackets [ ] can be translated but the parenthesis immediately after the square brackets and their contents should not be changed. For example they have been correctly replacing other parenthesis characters in text with their Chinese equivalents but these specific parenthesis immediately following square brackets, and any tel: text inside, should stay unchanged.
Each \n in the spreadsheet is turned into one line break, so these should be unchanged, and it's okay for there to be no space between it and the start of the next word

It's not a major problem if they mistakenly change some of these, these are things we know to check for and can fix our side, but it'll save some time.
output.xlsx

@AlanSl  Spreadsheet sent over to translators.

@kevin-sheldon Can you please upload the previous spreadsheet in a comment here - the one you sent to Paul two weeks ago mentioned in this comment: https://github.com/project-vagabond/covid-green-app/issues/53#issuecomment-683782153
We need to check the encoding of some of the Korean characters. Thanks!

@kevin-sheldon Here's the updated spreadsheet, adding today's changes:
covid-alert-ny-translations-v3-200918.xlsx
And this contains only today's changes since earlier this week:
covid-alert-ny-translations-v3-200918-changes-from-200915.xlsx

@AlanSl @floridemai Translations from V3 attached. Still awaiting V4 from translator.
covid-alert-ny-translations-v3-200915_6 languages.xlsx

covid-alert-ny-translations-v4-200918-changes-from-200915_6 languages.xlsx
V4 back from translators.

Great, thanks @kevin-sheldon and here's version 5 which as discussed does not include the app store content.
covid-alert-ny-translations-v5-200921.xlsx

@kevin-sheldon I believe you will have already been told yesterday afternoon / evening that unfortunately there were some more text tweaks added requiring translation.
If you don't have these already, they are in this spreadsheet, and I've been told there should not be any more.
It will be worth telling the translators that the only change in the first item is changing "public health research" to "public health researchers":
covid-alert-ny-translations-v6-200922.xlsx

@kevin-sheldon Alex has just told me that the under-18s text is being changed again by Legal

@kevin-sheldon This sheet replaces the first v6 sheet above and includes the revised age approval text. It can be done after v5.
covid-alert-ny-translations-v6-200922_2.xlsx

On behalf of Kevin:
covid-alert-ny-translations-v5-200921_5 languages.xlsx
This has 5 languages, not Korean yet.

@AlanSl added Korean as well. v5 is now fully translated.
Just awaiting v6
covid-alert-ny-translations-v5-200921_Korean.xlsx

v6 has been translated in Russian and Bengali.
Only outstanding translations are the v6 translations for Haitian, Korean, Chinese, and Spanish
covid-alert-ny-translations-v6-200922_2_Russian and Bengali.xlsx
Sorry this is coming in pieces. Figured I would send what we have.
@AlanSl

The attached is v6 with Spanish and Chinese.  Sorry for the multiple files – let me know if they want us to put everything together tomorrow (should be easy to do) or if it’s all the same to them.

covid-alert-ny-translations-v6-200922_2_Chinese and Spanish.xlsx

v6 attached with ALL languages @AlanSl
covid-alert-ny-translations-v6-200922_2_ALL Languages.xlsx

We believe this to now be complete:

Everything is in build 46 except for, in ko and ht only, the age gate text and the change from "research" to "researchers" in the health log welcome screen
Those remaining changes are done and will be in build 47 later today

Confirmed done


Created new mcc user configuration for edge-core when compiled for Pe…

…lion Edge
Use this configuration to define the endpoint_type=EDGE_GW. This will
help classify the feature rich gateway as "Edge Gateways" vs feature free gateway
as "Gateway" in Pelion portal. Also reduced the MBED_CLOUD_CLIENT_LIFETIME to 10 minutes.

What constitutes feature rich?

@40Grit  Feature rich includes more of device management capabilities -- Gateway logs in cloud, remote terminal and protocol supports like Modbus, BACnet, Enocean, BLE and Z-Wave.


New SoundDeviceMaskedSamplesGenerator class?

class acoular.sdinput.SoundDeviceSamplesGenerator has acoular.tprocess.SamplesGenerator as its base. Do we better have a similar new class acoular.sdinput.SoundDeviceMaskedSamplesGenerator based on acoular.tprocess.MaskedSamplesGenerator? Yes, it is not an issue, but will be more convenient if acoustic array has invalid channels or invalid samples.

Ideally you would mask invalid channels already in the device. Another option is to use MaskedTimeInOut as the next processing block after SoundDeviceSamplesGenerator. This should give the functionality of a SoundDeviceMaskedSamplesGenerator


UBTU-20-010461 - usb-storage remediation doesn't pass benchmark

Describe the Issue
There's a minor change needed at https://github.com/ansible-lockdown/UBUNTU20-STIG/blob/devel/tasks/fix-cat2.yml#L3046.  You set /bin/true while the benchmark checks for /bin/false, and thus becomes a finding.
Expected Behavior
V-251505 should pass benchmark
Actual Behavior
V-251505 fails benchmark with:
Tests:
false (All child tests must be true.)
[false (/etc/modprobe.d contains a file that contains 'install usb-storage /bin/false')

Control(s) Affected
V-251505
Environment (please complete the following information):
All below items are N/A, see line link to fix-cat2.yaml...

branch being used: [e.g. devel]
Ansible Version: [e.g. 2.10]
Host Python Version: [e.g. Python 3.7.6]
Ansible Server Python Version: [e.g. Python 3.7.6]
Additional Details:

Additional Notes
Anything additional goes here
Possible Solution
Enter a suggested fix here

hi @kfiresmith
Thank you for the feedback, This has been a long standing issue with /bin/false vs /bin/true. Many details allow either when reading specific details, in this case it does ask for /bin/false.
However with true and false both having the same impact the difference is purely down to the return code at boot time.
with bin/false it will return a non 0 return code meaning that there will be failures logged at boot time (when there shouldn't be as it is as expected), where as bin/true give a 0 return code meaning this is desired and expected.
This has been a long going discussion with STIG and the community either should be acceptable when it comes to auditing.
I hope that makes sense?
Thanks
uk-bolly


Notebooks end up with attachment in cell attributes when it should not

When I opened a notebook in vscode.dev and made a change, almost all cells had added "attachment" to the cell attributes. Not sure what was driving this.

This is driven by the notebookAttachmentCleaner most likely. It's what is responsible for upkeeping all of the base64 attachments stored behind the notebook. This was implemented last summer to support the attachment format the Jupyter uses to store images within the notebook.
It should behave such that the cell attributes should only contain the attachment field after an image has been pasted in using that provider specifically (which is the default for jupyter iirc). Currently, the attachment field just isn't removed when there are no attachment style images within the cell, which causes cells to retain the field.
I can look into tweaking that if we feel it's an issue. Is this causing any bigger issues or is it just an unexpected field to be seeing?

Is this causing any bigger issues or is it just an unexpected field to be seeing?

The result would be users will end up seeing this in their SCM view every time when making a minor change to some other cell. i.e. this would result in unwanted changes to the notebook file and users have complained about that in the past.
Its not a breaking change, but one that will end up annoying users eventually.

All I did was edit a cell (just text, no images/pasting/etc)

@pamelafox thanks for the update! Yep, this will get taken care of next week. The intended behavior is that only cells with the images specifically stored as attachments will receive that field.

Verifier, please test with both ipynb.pasteImagesAsAttachments.enabled set to true and false.


Can we have wheelPropagation always = false?

Could we have an option to have wheelPropagation persist whether scrollbars are enabled or not?
For example, when the content area isn't tall enough to enable scrollbars the user can scroll the parent element even with
wheelPropagation : false.
For a demo, see http://codepen.io/anon/pen/mJaeKR and remove some of the content of the scrollable red area so that it is no longer scrollable. I would like scrolling of the parent element to behave exactly like it did when the red area was tall enough.
Thanks for the awesome work on this awesome plugin!

Perfect-scrollbar strives to behave like the native scrollbar.
When an element is not scrollable, scroll propagates upwards, as such perfect-scrollbar follows this convention.
Also, in your scenario perfect-scrollbar is not the cause nor the solution. When an element is non-scrollable, perfect-scrollbar does not receive scroll event. What you are seeing is your browser's default behaviour.

@DanielApt I understand that this is native browser behaviour, I was actually just wondering if we could have it as an option. wheelPropogation = false is not default browser behaviour, so with that logic, it would also be nice to offer a sort of "alwaysOnWheelProgogation".
Thanks for the quick reply!

I am having the same problem, I hope the parent element can be scolled if there is no need to scroll in the child element, can you please fix this issue?


Suppress warnings in contrib directory

I'm building YDB from source according the instruction. And I'm having  huge amount of warnings in contrib directory. Can you suppress them?

Internal ticket is YMAKE-91.

Fixed, just checked it.


QUESTION: Timeline for 0.11.0 release?

Hi Folks,
Is there a timeline for the official release of version 0.11.0?
Also is there in the meantime an official repository supporting the build of the snapshot preview for 0.11.0-SNAPSHOT-hadoop2.jar?
Cheers!
Kurt

Hi,
Thanks alot for the reply and sorry for the slow reply just getting back to this.
I did build the shaded jar as you mentioned.
For bigquery jar, I am missing some classes and getting compile erros even though they are in documentation (note: I changed the pom.xml to the latest bq rev version of 374 from 370 in master)

com.google.api.services.bigquery.BigqueryScopes:  Not sure why this is not there in the shaded jar, its in the documentation and been there for a while, but its absent:

https://developers.google.com/resources/api-libraries/documentation/bigquery/v2/java/latest/index.html?overview-tree.html

com.google.api.services.bigquery.model.TimePartitioning:  There is a new attribute 'field' part of a beta release, and getter and setter for this in the google doco below and should be in the apis for this revision version, but in the generate class in the jar this is missing.

https://developers.google.com/resources/api-libraries/documentation/bigquery/v2/java/latest/index.html?overview-tree.html
For 1., when I compare my classes generate (ref attached image), seems I am missing a few classes, so fels like Im missing something that is excluding these for some reason?  You can see this comparing the image to the google link of classes in the jar
For 2. Do I need to specify something  in the POM to include experimental features?
Sorry to bother on this probably very simple for you, just not sure why the differences exist and not experienced at maven to resolve myself
Hope you can help, thanks heaps!

You can try to disable jar minimization by removing this line:
https://github.com/GoogleCloudPlatform/bigdata-interop/blob/1ca97a02ab9732a2305f9734c126d2577468a3e9/bigquery/pom.xml#L186
To further assist I need more details, may you provide a use case? How you try to use BigQuery connector? Also, please share modified pom.xml.

Hi,
Thanks for this.
Use case: Exploit a new BQ feature only now in beta not in current published version 0.10.3-hadoop2 (just checked there is a 0.10.4 now but nor does that.)
We use https://github.com/samelamin/spark-bigquery library (scala) which itself uses below (defined in build.sbt)
"com.google.cloud.bigdataoss" % "bigquery-connector" % "0.10.3-hadoop2"
This under the hood uses an older version of the googles bigqeury APIs, which does not contain a feature I need, namely on TimePartitioning there is a new attribute called 'field' and getters and setters (beta released a few days ago).  This is key to enabling true event time in terms of BQ partitoning, not ingest time.
Thus, I am trying to build the 0.11 snapshot myself (shaded so has all the dependencies in the uber jar), which, as it uses new versions of the BQ API, does have access to this new feature.
Alas, Im having troubles in doing so as we have previously discussed.
Is there anywhere where the snapshots are build nightly or other?
In terms of POM.xml, the root and bq pom.xml isnt really changed, except I tried to use the very latest api version to be sure - rev374 - master has rev370.  Below is all I changed myself, I tried your option on the minimise
<google.api-bigquery.version>v2-**rev374**-${google.api.version}</google.api-bigquery.version>

Be a great help to get this working.  Hope this is enough to help and thanks for your time assisting.
Thanks
Kurt

Where are you trying to use spark-bigquery library? On Dataproc cluster or standalone application? May you share pom.xml/build.sbt of your app?

Hi thanks for getting back so quick much appreciated!
I am using Databricks (Spark SaaS product on AWS) not gcp.  Weve been BigQuery customers for sometime and Ive been using this library for a while.  This is the first time Ive needed to get a custom build of the spark-bigquery library (using a cusomt build of the bq connector from the interop library) in order to get access to gcp bq beta API features:
 "com.github.samelamin" %% "spark-bigquery" % "0.2.3"

...which in its own build.sbt has the below dependency
"com.google.cloud.bigdataoss" % "bigquery-connector" % "0.10.4-hadoop2

Ive would be commenting out above spark-bigquery dependency from build.sbt in my own app and putting the custom spark-bigquery assembly below in my own sbt /lib directory as you do in scala.  THe custom spark-bigquery would use the shaded library below instead.
bigquery-connector-0.11.0-SNAPSHOT-hadoop2-shaded.jar

Anyhow - my own build.sbt below, but I would comment out the spark-bigquery maven dependency if only I could get spark-bigquery to build with the shaded jar (with some new code in spark-bigquery to reference the new TimePartitioning.field attribute - my main objective!.  But I cant get the spark-bigquery library to build (as previous post on missing BigQuery scopes and others) when I put the generated shaded jar here.
name := "sdv-analytics-lib"

scalaVersion := "2.11.8"

fork in Test := true

javaOptions ++= Seq("-Xss128M", "-Xms1536M", "-Xmx2048M", "-XX:MaxPermSize=2048M", "-XX:+CMSClassUnloadingEnabled")

resolvers += Opts.resolver.sonatypeReleases
resolvers += "Java.net Maven2 Repository" at "http://download.java.net/maven/2/"

libraryDependencies ++= Seq(
  "org.apache.spark" %% "spark-core" % "2.2.0" % "provided",
  "org.apache.spark" %% "spark-streaming" % "2.2.0" % "provided",
  "org.apache.spark" %% "spark-sql" % "2.2.0" % "provided",
  "org.apache.spark" %% "spark-hive" % "2.2.0" % "test",
  "com.holdenkarau" %% "spark-testing-base" % "2.2.0_0.8.0" % "test",
  "com.github.samelamin" %% "spark-bigquery" % "0.2.3"
)

libraryDependencies += "com.amazonaws" % "aws-java-sdk" %   "1.7.4" % "test"
libraryDependencies += "org.apache.hadoop" % "hadoop-aws" % "2.8.1" % "test" excludeAll(
  ExclusionRule("com.amazonaws", "aws-java-sdk"),
  ExclusionRule("commons-beanutils")
)

// Below is for testing using the spark-testing-base package
parallelExecution in Test := false)

I will try to package working jar with new BigQuery connector using your build.sbt config and will report results later.
But most probably you don't ship new BigQuery connector jar to Databricks Spark cluster - I don't see any fat jar configuration in your build.sbt, so I assume that your job/application jar doesn't have bigquery classes in it, and old bigquery connector jar that already has been deployed to cluster is used at runtime, or bigquery connector jar not deployed at all.

Hi,
Thanks so much!
For my own app, as Im using a standard scala spark-bigquery release (scala 2.11 - 0.23) published on maven, I upload this library seperately and its deployed on the spark clusters at startup as a seperate library - as its standard, I dont need to build a fat jar, this is the only runtime library Im dependant on.
I do have the scala plugin that allows me to execute 'sbt assembly' calls if I need to build an uber jar with all dependencies included.  If I was building my own spark-bigquery library (to include the shaded jar we are generating), I would need to with this and use the assembly
https://github.com/sbt/sbt-assembly
Awesome thanks
Kurt

Hi Igor,
Any luck with this?
Cheers mate

p.s  - feel free to contact me on<EMAIL_ADDRESS>if you need a direct line to chat and share artifacts.   REALLY appreciate your help :)

Hi Kurt,
I was able to make it work just by modifying spark-bigquery built.sbt file (no need to build latest bigquery-connector) by adding new "com.google.apis" % "google-api-services-bigquery" % "v2-rev375-1.23.0", dependency to it and building spark-bigquery library with sbt assembly command. It should produce spark-bigquery-assembly-0.2.3-SNAPSHOT.jar fat jar that has all dependencies including latest google-api-services-bigquery library.
Please try to use this fat jar and let me know if it works.
Best,
Igor

Hi Igor,
Awesome thanks for this.  This did compile and assemble ok, have an issue to look into as getting 404 errors though from gcp bq endpoint.  Think there is some http endpoint URL differences perhaps between versions?  Anything you would know of?  Anyhow - Ill keep trying, progress.  Really appreciate your help on this, many thanks! :)
Kurt

We just released BigQuery connector v0.11.0: http://search.maven.org/#artifactdetails|com.google.cloud.bigdataoss|bigquery-connector|0.11.0-hadoop2|jar
Try to use it directly as a dependency in spark-bigquery lib and see if it works.
If 404 errors persist, please, post exception stack trace here.

Hi Igor,
Thanks heaps!  This is awesome.....I did try this with the updated 0.11.0, but ran into a different exception around guava I think Im looking at.

Will let you know once I get over this.
Cheers!

To fix this you need to exclude guava instead of guava-jdk5 when depending on latest bigquery-connector in spark-bigquery:
"com.google.cloud.bigdataoss" % "bigquery-connector" % "0.11.0-hadoop2"
  exclude ("com.google.guava", "guava"),

Closing this issue because BigQuery connector 0.11.0 has been released.


⚠ ClamAV has degraded performance

In 7c40cde, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: ClamAV performance has improved in df91b8e after 5 minutes.


feat: Added ability to print globals as part of debug messages

This allows debug messages to print the contents of globals. Globals are indicated by brace symbols " { } "
debug "r3_button_broken is currently {r3_button_broken}"

I have added the function to resolve globals to all debug levels (info, warning etc) but due to bug 219 I can't test other debug levels so I'm not sure if the behavior is correct.
If everyone's happy with the "{ global }" notation, I'll need to update the documentation in the documentation repo.
The alternative is Godot string notation
debug "Name %s is %d years old", name, age

But I don't know how to extend the parser to cope with this so I went with what I knew how to code :D
Output for valid global
2022-4-3T11331 (D)	Running command debug with parameters [r3_button_broken is currently True]
2022-4-3T11331 (D)	debug command issued 	[r3_button_broken is currently {r3_button_broken}]

Invalid global :
2022-4-3T105254 (D)	Running command debug with parameters [r3_button_broken is currently Null]
2022-4-3T105254 (D)	debug command issued 	[r3_button_broken is currently {invalid_global}]

Fixes https://github.com/godot-escoria/escoria-issues/issues/205

Thanks!


Fix missing re-activation of bullet physics sleep feature

Adds the missing option of re-enabling the sleep feature in bullet physics once a body had the sleep feature disabled.
Fixes #27715

Thanks!

Cherry-picked for 3.1.2.


TIGRESS A/B core issue, apparent data loss.

Though I've created a pull request with a fix in, I'm creating an issue to highlight this problem so hopefully more people see it, as it effects completed and ongoing analysis of TIGRESS data.
A line in the tigress code for checking B vs A core had a case issue.
if(hit->GetName()[9] == 'a')
It seems at some point in the past a/b were lowercase, and this line got missed during iterations.
The result was that ~10% of data replaced the A core with B core, which is a problem as often the B core is un-calibrated/set to 0.
I've checked with some recent 2017 erbium data and @jhenderson88 looked at some older Mg data. We both found this had cause a ~10% data loss, which does not appear to be energy correlated.
This could still be a problem for other TIGRESS analysis as presumably there may be some correlations with combinations of events in the DAQ as to which core A or B is processed first.
I have updated the section to centralise things to the mnemonic class
if(hitchan->GetMnemonic()->OutputSensor() == TMnemonic::EMnemonic::kA)
this should be done everywhere possible to abolish such manual checks and avoid problems in future. I don't think this is a problem in GRIFFIN as A & B are treated differently?
Here is example of data before (red) and after (blue) the change. (The B channels here were using the same calibration as A i.e. a bad cal rather than zeroed)

I want to say that if people missed this memo, they aren't going to catch it anymore. Shall we close is?


[Bug]: Access to release note of 3.30.21

Describe the bug
Hi!
Similar to #375, the release notes link on the 3.30.21 page points to a restricted Google Doc site, so we can't read the release notes.
To Reproduce

Go to https://github.com/nmfs-stock-synthesis/stock-synthesis/releases/tag/v3.30.21
Click on release notes
I get an error message saying "You need access. Request access, or switch to an account with access."

Expected behavior
I expected to be able to read the 3.30.21 release notes.
Screenshots
No response
Which OS are you seeing the problem on?
No response
Which version of SS3 are you seeing the problem on?
No response
Additional Context
No response

I added a pdf file for the link that will automatically download instead of including the link to the google doc.


Update resources.md

added a new JS type documentation

@Ishaan28malik  commit message should be in detail of what change you have made. It shouldn't be update README.md
I'm merging this for now but remember it for future 😄  👍

@vicky002 Thanks for the information, I will keep this in mind for future commits.


Links in descriptions

For example
https://www.ebi.ac.uk/ols4/ontologies/ro/properties/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FRO_0002204
The description has CURIEs in it. It would be quite simple to turn these into links. The same goes for URLs in text (which I believe OLS3 handles).

Couldn't resist implementing this one as it was a small change but improves the display of core OBO ontologies. See description in OLS3:

Vs. OLS4:

Couldn't resist implement this one as it was a minor change with an impact on core OBO ontologies. OLS3:

OLS4:

That is a pretty cool idea


Opening a gitter.im room ?

Everything’s in the title !
It’d be nice to be able to chat in real-time about dev, and support, imho.

Would it be an option to use the GeoRust discord chat?

Why not. I must admit having nothing to install, and being just a click away from chat is nice, but if people prefer discord, then so be it :)

As it is just me at the moment working on this crate I will close this issue. Feel free to open an issue if there are any items you would like to discuss


fix: export TPT type

What does this change?
exports ThirdPartyTag type
Why?
to be used in frontend

:tada: This PR is included in version 0.8.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Automated cherry pick of #3606: influxdb: 记录结果中的tags

Cherry pick of #3606 on release/2.12.
#3606: influxdb: 记录结果中的tags

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@5dfdb10). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #3608   +/-   ##
==============================================
  Coverage                ?   6.93%
==============================================
  Files                   ?     499
  Lines                   ?   83680
  Branches                ?       0
==============================================
  Hits                    ?    5800
  Misses                  ?   77386
  Partials                ?     494

Flag
Coverage Δ

#aFlag
6.93% <0%> (?)

Impacted Files
Coverage Δ

pkg/util/influxdb/influxdb.go
0% <ø> (ø)

pkg/compute/models/loadbalancerbackends.go
2.8% <0%> (ø)

pkg/compute/models/loadbalancers.go
1.71% <0%> (ø)

pkg/compute/models/loadbalancer_backendstatus.go
0% <0%> (ø)

pkg/compute/models/loadbalanceragents.go
2.25% <0%> (ø)

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 5dfdb10...605c061. Read the comment docs.

/lgtm

/approve

/approve


Custom events

Is it possible to fire custom events?

DOM Delegate listens to events, it doesn't fire them.  I believe DOM Delegate should handle custom events the same as any non-custom events…  Have you run into problems?


Add version: pnpm.pnpm.6 version 6.32.23

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run

@wingetbot waivers Add Validation-Executable-Error


Declare compatible with Neos 7.x

Any plans to merge this PR @kdambekalns @robertlemke @kitsunet ?


Make sure shellhandler is populated in cluster store

Also factor out cluster store creation so it's not done twice.

https://github.com/rancher/rancher/issues/16714
https://github.com/rancher/rancher/issues/16715


Typescript react-spring/dist/addons

This isn't an issue, but I wanted to a solution for getting typescript to resolve Parallax or any other addons that may live in dist/addons in the future.
Declare the following in global.d.ts at your project root or you can do what I did, which was create types/react-spring-addons.d.ts, and then include the file in tsconfig.json e.g. "files": ["types/react-spring-addons.d.ts"]
declare module 'react-spring/dist/addons' {
  import { Parallax, ParallaxLayer } from 'react-spring'
  export { Parallax, ParallaxLayer }
}

I am working on a PR for types for the hooks and I had to solve this problem as well while doing it, so if I get this thing to work it'll probably be fixed in react-spring soon 👍

It's fixed as of the currently published version (can import react-spring/addons) :tada:

Oh that's awesome! I'm going to close this issue then since it should just work according to the existing docs.


Add Synology with no backup job configured

Hello,
Thank you for this plugin.
I try to add a nas or there is no backup job configured and I get this in the logs:
{'api': 'SYNO.Backup.Task', 'code': -2, 'reason': 'Unknown', 'details': 'API SYNO.Backup.Task does not exists'} 20:44:19 – (ERREUR) Synology DSM (intégration personnalisée)
How to correct this?
Thanks

that would be loevely! i mean there is one but official way is the best


Yeelight celling light color temp error

Home Assistant release with the issue: ~0.75
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.): osx, rasbian
Component/platform: Yeelight
Description of problem:
The slider of temperature's first 50% works as 0~100%
set it to 100% will cause light unavailable for a while
Error when calling <function YeelightLight.set_colortemp at 0x6238bc90>: {'message': 'general error', 'code': -5000}

Please follow issue template

rgb light bulb has 1700K warm min color and work fine, but celling lamps has 2700K and work only till 50% on slider color temp

The upstream library supports handling the color temperature on model basis: https://gitlab.com/stavros/python-yeelight/commit/5d940035a5be76d88ddc39324e6ba05ef139fd20 - the platform should be modified to use the model information from netdisco (or config, falling back to default 2700k) and adjust the {min,max}_minreds accordingly.

Actually this was already being done by @syssi in https://github.com/home-assistant/home-assistant/pull/14083 which I somehow missed. So this is a duplicate of #13785 and I will close it as such.


settle_funds return 0 usdt to my address

sol address:7ewn8oj7MWyhZE5qFux1npzUnuT4XCVvBvYiMHehYvBb
usdt address:8pkzuX9GjrgEFuX4JXQeV4hcSjwTba59yC92vSfbz45H
fida address:4BCnuuQXHXEMiUVYYA7mw2Jc5AyX5q1FcTRDmvnV9uDR
i submit an order https://explorer.solana.com/tx/522X9qN66UMbSoLk5Sry9iRcm9zFFoaR1M34qysJSedtCQ5893ofNhxx61uaqnRxj4b8cadfXH4YEM1BV1Bd3WKP , then i've cancellled it twice , not sure why.. https://explorer.solana.com/tx/54GUkmszRxT9g8T9GFL2PZRyi8Z6PDKzmT5STkVVbGcHoQRgRNC6HUeChTuggKDdmFsn1GM6WLHrbx3MeQJVAHfZ and https://explorer.solana.com/tx/46XJr3zDs94tmDNgjXHhQJTYFQfPnjyKKrzrRtYcWYNJ9672zEiv9XxZZsmuHj2h3N1fnNVfMA5po8K1QLe1zhvb
then not sure what i did there  when i've tried to settle_my funds https://explorer.solana.com/tx/2ph3m68QKaxjyyk2SmBQ2m2j6XF7ksYjMiz9hVo9eo5toKhPopQRj8XT6AA8AdPUXBNEo39cy5zf91WHYC8i2WMS
open_orders_account = market.find_open_orders_accounts_for_owner(owner_address=PublicKey('7ewn8oj7MWyhZE5qFux1npzUnuT4XCVvBvYiMHehYvBb'))
but when i do now settle_funds it sends me 0 usdt back all the time
https://explorer.solana.com/tx/36Rca4VQQe7dodh2VTavXRTPJZGQuknhc4wRt4ST2s8GgQijbFJKwmoDsxgBJnHYrutKQzzCuQtuRc41mfPzUSeZ and https://explorer.solana.com/tx/4gJyqXLH7Xr4XcfwsTjgbjDbFBasHhQjaPjBwkxAk8Cd9hU92xqUHgw2sbRGcP3KonCrFu3PFADF6CoE5PYLHFa4

please dm me on dicord cryptoguy100786#0098

how to get my usdt out of https://explorer.solana.com/address/Dygr7hmVgydf6Cs4CF34EbXbD8xhJJVMXjvYJCR7LqmM ? thanks

I added some client-side validation to prevent this from happening now.
https://github.com/serum-community/pyserum/commit/2944582a4930b687373ecd86204d7ad575858bf1

I added some client-side validation to prevent this from happening now.
2944582

amazing, please also add a comment somewhere what represents base_wallet and quote_wallet, if someone use it for first time it's so confusing (at least for me it was)i had no idea to put there my own addresses(my own usdt address for pair/usdt i knew but not sure where base_wallet or quote_wallet)..so i did a lot of tries until i screw up

settle_funds it sen

indeed it is confusing, maybe you can explain it here, more in details ?


Unable to receive the web push from firefox.

Describe the bug
Send a web push, chrome can receive the web push, but firefox can't.
Tested send from the firebase api explorer, both chrome and firefox can receive.
To Reproduce
$message = (new Factory)
  ->withServiceAccount($serviceAccountJson)
  ->createMessaging();

$json = '
  {
    "topic": "scmp_exclusive",
    "webpush": {
      "data": {
        "title": "This is title",
        "body": "this is body",
        "icon": "https://cdn.i-scmp.com/sites/default/files/styles/280x224/public/d8/images/methode/2020/05/25/efcaa2a8-9dd4-11ea-96ff-7aff439fc3be_image_hires_005459.JPG?itok=CpJJMZSO",
        "click_action": "https://google.com"
      }
    },
    "fcm_options": {
      "analytics_label": "20200626090654.3085867"
    }
  }
';

$payload = json_decode($json, TRUE);
dump($payload);
$result = $message->send($payload);
dump($result);

Expected behavior
both chrome and firefox browser can receive the web push.
Screenshots
Tested in firebase api explorer with the same payload, both chrome and firefox can receive web push

Environment (please complete the following information):

OS: Alpine Linux
PHP version: 7.2.31
Firebase SDK Version: [4.44.0, 5.5.0"]

Additional context
Add any other context about the problem here.

Unfortunately, I can't reproduce/debug the problem if you don't share the actual payload that you're using.

Here is the testing payload
{
  "message": {
    "topic": "exclusive",
    "webpush": {
      "data": {
        "title": "This is title",
        "body": "this is body",
        "icon": "https://cdn.i-scmp.com/sites/default/files/styles/280x224/public/d8/images/methode/2020/05/25/efcaa2a8-9dd4-11ea-96ff-7aff439fc3be_image_hires_005459.JPG?itok=CpJJMZSO",
        "click_action": "https://google.com"
      }
    },
    "fcm_options": {
      "analytics_label": "20200626090654.3085867"
    }
  }
}

Thank you for the added information! I used your payload to test it with chrome and with Firefox and it worked on my machine™.
Here are some hints to help hopefully debug this on your side:
Check if the message arrives at the target browser if sent directly
use Kreait\Firebase\Messaging\CloudMessage;

$payload = CloudMessage::fromArray($payload)->withChangedTarget('token', $firefoxToken);

$result = $message->send($payload);
dump($result);

If the message does arrive in your browser (in subsequent tests, messages took up to 2 minutes to be delivered in my case), the Firefox App Instance might not be subscribed to the given topic. You can check the subscription status with
$appInstance = $messaging->getAppInstance($firefoxToken);
dump($instance->isSubscribedToTopic('scmp_exclusive'));

Let me know if this helps

Thanks for you information.
Finially , i find that the problem payload.
{
    "topic": "scmp_exclusive",
    "webpush": {
      "data": {
        "title": "South China Morning Post",
        "body": "National Security Law: Hong Kong police granted sweeping new powers",
        "icon": "https:\/\/cdn.i-scmp.com\/sites\/default\/files\/styles\/280x224\/public\/d8\/images\/methode\/2020\/07\/07\/a130b5a2-bf9d-11ea-8c85-9f30eae6654e_image_hires_002515.jpg?itok=fuA9VTNC",
        "click_action": "https:\/\/www.scmp.com\/news\/hong-kong\/politics\/article\/3092070\/national-security-law-hong-kong-polices-sweeping-new-powers",
        "nid": "3092070",
        "topic": "'hong_kong' in topics || 'china' in topics"
      }
    },
    "apns": {
      "headers": {
        "apns-priority": "10",
        "apns-topic": "com.scmp.newspulse"
      },
      "payload": {
        "aps": {
          "mutable-content": 1,
          "alert": {
            "title": "National Security Law: Hong Kong police granted sweeping new powers",
            "body": "Hong Kong police granted sweeping new powers"
          }
        },
        "title": "National Security Law: Hong Kong police granted sweeping new powers",
        "body": "Hong Kong police granted sweeping new powers",
        "url": "https:\/\/www.scmp.com\/news\/hong-kong\/politics\/article\/3092070\/national-security-law-hong-kong-polices-sweeping-new-powers",
        "image": "https:\/\/cdn.i-scmp.com\/sites\/default\/files\/styles\/250x250\/public\/d8\/images\/methode\/2020\/07\/07\/a130b5a2-bf9d-11ea-8c85-9f30eae6654e_image_hires_002515.jpg?itok=1-2ctin9",
        "entity_id": "3092070",
        "section_id": "318206",
        "topic_id": "2",
        "alert_topic_name": "Hong Kong,China",
        "alert_topic_display": "National Security Law",
        "uuid": "032ccea0-bf8d-11ea-8c85-9f30eae6654e",
        "action_type": "article",
        "push_time": "20200707000717"
      }
    },
    "android": {
      "priority": "HIGH",
      "restricted_package_name": "com.scmp.newspulse",
      "data": {
        "android_channel_id": "general",
        "title": "National Security Law: Hong Kong police granted sweeping new powers",
        "body": "Hong Kong police granted sweeping new powers",
        "url": "https:\/\/www.scmp.com\/news\/hong-kong\/politics\/article\/3092070\/national-security-law-hong-kong-polices-sweeping-new-powers",
        "image": "https:\/\/cdn.i-scmp.com\/sites\/default\/files\/styles\/250x250\/public\/d8\/images\/methode\/2020\/07\/07\/a130b5a2-bf9d-11ea-8c85-9f30eae6654e_image_hires_002515.jpg?itok=1-2ctin9",
        "entity_id": "3092070",
        "section_id": "318206",
        "topic_id": "2",
        "alert_topic_name": "Hong Kong,China",
        "alert_topic_display": "National Security Law",
        "uuid": "032ccea0-bf8d-11ea-8c85-9f30eae6654e",
        "action_type": "article",
        "push_time": "20200707000717"
      }
    },
    "fcm_options": {
      "analytics_label": "20200707000717.hong_kong.3092070"
    }
  }

When the payload has  android -> restricted_package_name , firefox cannot receive the web push.
after remove the restricted_package_name, firefox can receive.
also tested in firebase api explorer, firefox also cannot receive. and have a message Property "restricted_package_name" does not exist in object specification.
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#Message
the restricted_package_name is part fo the adnroid config.
In my case, seem not related to the php package.

Thank you for sharing this, it certainly will help others facing a similar situation. 🤗
As this is not directly related to the SDK, I'll close the issue, but feel free to add further comments.


Fix docs of class Tone

In order to fix the documentation of the class Tone, I did 2 things:

fixed the typo on the docs comment.
changed the type name in  Tone/fromContext.ts to differentiate it from the class name.

thanks for the PR!


Unable to query workflows library in 1.1 API as documented

The docs (http://rackhd.readthedocs.io/en/latest/rackhd/graphs.html#api-commands-for-graphs) say to do the following to get a list of Graphs:
GET /api/1.1/workflows/library
However, this is the response I get when doing so:
$ curl localhost:9090/api/1.1/workflows/library | python -m json.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    84  100    84    0     0   3995      0 --:--:-- --:--:-- --:--:--  4200
{
    "message": "Could not find graphobject with criteria {\"instanceId\":\"library\"}."
}

The server side logs show the following:
5:21:01 PM http.1 |  [info] [2016-08-03T17:21:01.189Z] [on-http] [Services.Configuration] [Server] Configuration value is undefined, u…
5:21:01 PM http.1 |   -> /node_modules/on-core/lib/services/configuration.js:73
5:21:01 PM http.1 |  [error] [2016-08-03T17:21:01.202Z] [on-http] [Http.Services.RestApi] [Server] Could not find graphobject with cri…
5:21:01 PM http.1 |   -> /lib/services/rest-api-service.js:323
5:21:01 PM http.1 |  error:
5:21:01 PM http.1 |    message: Could not find graphobject with criteria {"instanceId":"library"}.
5:21:01 PM http.1 |    name:    NotFoundError
5:21:01 PM http.1 |    context:
5:21:01 PM http.1 |      criteria:
5:21:01 PM http.1 |        instanceId: library
5:21:01 PM http.1 |      collection: graphobjects
5:21:01 PM http.1 |    status:  404
5:21:01 PM http.1 |  path:  /workflows/library
5:21:01 PM http.1 |  NotFoundError: Could not find graphobject with criteria {"instanceId":"library"}.
5:21:01 PM http.1 |      at /home/vagrant/src/on-http/node_modules/on-core/lib/common/model.js:407:27
5:21:01 PM http.1 |      at tryCatcher (/home/vagrant/src/on-http/node_modules/on-core/node_modules/waterline/node_modules/bluebird/js…
5:21:01 PM http.1 |      at Promise._settlePromiseFromHandler (/home/vagrant/src/on-http/node_modules/on-core/node_modules/waterline/n…
5:21:01 PM http.1 |      at Promise._settlePromiseAt (/home/vagrant/src/on-http/node_modules/on-core/node_modules/waterline/node_modul…
5:21:01 PM http.1 |      at Promise._settlePromises (/home/vagrant/src/on-http/node_modules/on-core/node_modules/waterline/node_module…
5:21:01 PM http.1 |      at Async._drainQueue (/home/vagrant/src/on-http/node_modules/on-core/node_modules/waterline/node_modules/blue…
5:21:01 PM http.1 |      at Async._drainQueues (/home/vagrant/src/on-http/node_modules/on-core/node_modules/waterline/node_modules/blu…
5:21:01 PM http.1 |      at Immediate.Async.drainQueues [as _onImmediate] (/home/vagrant/src/on-http/node_modules/on-core/node_modules…
5:21:01 PM http.1 |      at processImmediate [as _immediateCallback] (timers.js:383:17)

It's clearly trying to interpret library as a graph ID instead of an endpoint, as /api/1.1/workflows/<instanceID> is a valid endpoint to retrieve a specific graph.
/api/1.1/workflows/tasks has the exact same issue (on-http thinks "tasks" is an instanceID".
/api/1.1/workflows/library/<injectable name> works fine
The 1.1 API swagger spec is expecting this endpoint to work as well: https://github.com/RackHD/on-http/blob/master/static/monorail.yml#L653
Is there another way to query the list of graphs available?

Ah - by seeing the logging output when running the Web GUI, I see that GET /api/1.1/workflows/library/* is what I really want here.
So there is a doc and API spec issue. Also, /api/1.1/workflows/tasks/* does not work, so it's unclear to me what the difference betwee workflows/tasks and workflows/tasks/library is intended to be. I think the former may not be necessary at all?

@codenrhoden sorry, yeah - it's sort of a crappy evolution of our original thinking (or lack thereof) around the URI structure here. The 1.1 setup never really worked the way we envisioned it, and we're replacing the structure significantly with the 2.0 API to be /api/2.0/workflow/graphs to get the list of workflows, and /api/2.0/workflows/tasks to get the list of individual tasks that can be composed into workflows.
While it's not a full solution for this, https://github.com/RackHD/docs/pull/309 should help with at least some of the 2.0 API pieces with it's examples, and we need to deprecate the 1.1 API and update it's documentation appropriately. In the hosted docs there was supposed to be an update, but it doesn't look like it's rendering properly:

I would rather think this is a bug for code rather than a doc issue.
I think the biggest problems is that there is a lot mismatching for API 1.1:

/api/1.1/workflows/library/* is to get all graph definition, but /api/1.1/workflows/task/library/* will not get all task definition.
/api/1.1/workflows/library/:injectableName is to get a graph definition, but no API /api/1.1/workflows/tasks/library/:injectableName to get a task definition.

I guess the reason why use /api/1.1/workflows/library/* to get all graph definitions is to distinguish the /api/1.1/workflows/:instanceId and /api/1.1/workflows/tasks. But if we carefully design the sequence of router, we can let these APIs work at expected because the instanceId will never be a string like tasks.
This is my PR to fix this issue as my preference: https://github.com/RackHD/on-http/pull/402


Mercury#_attemptConnection():  this.backoffCall is occasionally undefined

I think it's a result of the ordering of
      call.start();
      this.backoffCall = call;

in Mercury#_connectWithBackoff()

Not seen in quite a while.


Trivial spelling correction in comment of shell_eval

Just a drive-by fix as I was reading this…

Can I save that one till the next time I hack the lfe_shell? One word seems a bit too little for a whole commit. :-)

Sure.
I wouldn't have bothered but github makes these PRs quick and painless
On 9 Sep 2015 23:38, "Robert Virding"<EMAIL_ADDRESS>wrote:

Can I save that one till the next time I hack the lfe_shell? One word
seems a bit too little for a whole commit. :-)
—
Reply to this email directly or view it on GitHub
https://github.com/rvirding/lfe/pull/151#issuecomment-139064293.


Overview of the Apple source releases bump

Apple's source releases are only guaranteed to be compatible when they are part of a system release. Bumping all the packages together makes for a big diff that's hard to review.
To deal with this I'm bumping all the packages in a topological order. Since updating packages one by one isn't really an option I'm adding them in a separate attribute set. Once everything's merged we can switch over, hopefully requiring little more review effort.
I'll be opening PRs gradually and adding them to this list to preserve some overview.

[ ] #272998
[ ] #272999
[ ] #273003
[ ] #273006
[ ] #273009
[ ] #273010
[ ] #273011
[ ] #273012
[ ] #273013
[ ] #273014
[ ] #273015

[ ] #273016

[ ] #273017

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nix-macos-monthly/12330/47

Thinking ahead to after https://github.com/NixOS/nixpkgs/pull/229210 lands, is it possible the source selection stuff could be usable by other SDKs to pull in source-based components appropriate to their versions?

Apple's source releases are only guaranteed to be compatible when they are part of a system release.

Is that limited to the SDK or all source releases? I had most of adv_cmds-213 building with the 10.12 SDK (which I need to pick back up). How would that fit into this picture?

Re source selection, I haven't really thought about it. I think it would currently go in the wrong direction though, it enables subbing SDK things into a "source release" rather than the other way around, which I think is what we'd actually want, i.e., start from an SDK and only overlay bits of source releases when we manage to make them functional enough?
The compatibility is not an explicit policy, it's just a consequence of Apple's source dump model of FOSS.

Re source selection, I haven't really thought about it. I think it would currently go in the wrong direction though, it enables subbing SDK things into a "source release" rather than the other way around, which I think is what we'd actually want, i.e., start from an SDK and only overlay bits of source releases when we manage to make them functional enough?

I think we’re on the same page. Take an SDK then replace bits with source releases (or source-derived headers plus stubs) as we make them work.

The compatibility is not an explicit policy, it's just a consequence of Apple's source dump model of FOSS.

It was actually system_cmds I got updated not adv_cmds. Prompted by https://github.com/NixOS/nixpkgs/pull/295650, I’m planning to open a PR to update it once I confirm the stdenv bootstrap builds on both x86_64-darwin and aarch64-darwin.

https://github.com/NixOS/nixpkgs/pull/296321 is the system_cmds update PR.