added numba and fix bugs in Calc and CalcSpectra

Please do not merge pull requests if the tests are failing. Wait for the tests to complete, fix problems if needed, only then merge the pull request. The missing numba dependency in setup.py was now fixed in PR #114.

How do I know if a build is passed or not?  The tick was green, I thought
this was enough.
2018-02-06 16:40 GMT+09:00 Oliver Lemke<EMAIL_ADDRESS>
Please do not merge pull requests if the tests are failing. Wait for the
tests to complete, fix problems if needed, only then merge the pull
request. The missing numba dependency in setup.py was now fixed in PR #114
https://github.com/atmtools/typhon/pull/114.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/atmtools/typhon/pull/113#issuecomment-363336650, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADV4OPEx1GiYY-s2c9Ha3D56XUuDJUiqks5tSAHGgaJpZM4R6lx4
.

There is still a read cross next to 15150fe above. Not sure which green tick you saw. The travis tests take a couple of minutes. During that time the status of travis is shown as 'in progress' above the Merge button. You have to wait until they complete to see the green check mark or the red cross.

Ok, I know which check mark you saw. The first green checkmark (see attached screenshot) only tells you that there are no merge conflicts. Additionally, you have to wait for the Travis tests to complete:

Only when the tests succeed and the second green check mark appears, it's okay to do the merge:

Thanks!  I assumed the other check mark was the correct one.  I will be
careful of this in the future.
2018-02-06 17:25 GMT+09:00 Oliver Lemke<EMAIL_ADDRESS>
Ok, I know which check mark you saw. The first green checkmark (see
attached screenshot) only tells you that there are no merge conflicts.
Additionally, you have to wait for the Travis tests to complete:
[image: screen shot 2018-02-06 at 09 15 47]
https://user-images.githubusercontent.com/665724/35848484-9987a990-0b1e-11e8-8c6c-da263f3c7868.png
Only when the tests succeed and the second green check mark appears, it's
okay to do the merge:
[image: screen shot 2018-02-06 at 09 22 49]
https://user-images.githubusercontent.com/665724/35848715-599d3bf0-0b1f-11e8-9e48-45a33c3ef941.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/atmtools/typhon/pull/113#issuecomment-363346168, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADV4OERY2FkSFE2z6KvWqX9kMG_lRDg1ks5tSAxdgaJpZM4R6lx4
.

NB: for me this has triggered https://github.com/numba/llvmlite/issues/182 . This is not typhons fault but others may encounter the same.

It looks like getting numba to work on an old system is pretty involved.  llvmlite 0.21 apparently needs at least llvm 5.0, the machine on which I work has 3.4.2.  Installing llvm (new or old versions) apparently needs at least cmake 3.4.3, the machine on which I work has cmake <IP_ADDRESS>.  I've asked the system administrator if a newer cmake is accessible so I don't need to compile my own cmake as well (I haven't tried if I have the dependencies for compiling a newer cmake).
Would it be feasible to isolate the component of typhon that has a numba dependency, so that it can be used on old machines without installing a lot of software external to Python from source?  I might succeed in compiling my own cmake and llvm but there may be others with this problem who might try to avoid that.

@gerritholl Have you considered using Anaconda instead of plain pip to avoid the hassle of having to compile all dependencies you need for Python modules manually? Anaconda provides all dependencies pre-compiled and can save you a lot of time setting up an environment. It's not perfect and comes with its own set of issues. But using it for several years  now, I must say that it makes life a lot easier.

I will install anaconda and see if that resolves the GLIBCXX_3.4.14 not found problem.

Thanks, no problem through anaconda.


[WIP] Change to GitHub Actions

Description
This PR drops Travis and switches over to GitHub actions.
Status

[ ] Ready to go

May be of interest to @j-wags and @jaimergp


github oauth

https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps/

create a table allows some github user view the special tags of tasks

no need for minimum features


Submit/Search Functions

SUMBIT/SEARCH FUNCTIONALITY
User Story:
AS A User,
I WANT to be able to click a button
SO THAT I can be given results for what I search
Acceptance Criteria:
GIVEN a submit/search button
WHEN I click on it
THEN I am given results


AppCommands Autocomplete forcing value for choice to be of type Int53

Summary
Regardless of type sent, autocomplete forces and expects the type of the value to be Int53
Reproduction Steps
Created an autocomplete function for a hybrid command.
Set value to be a string.
Minimal Reproducible Code
# Assuming a bot is setup and this is a cog
from discord.ext import commands
from discord import app_commands, Interaction
from typing import Optional, List

# Simulated database functions returning mock team data
def get_league_teams(league_id):
    class LeagueTeam:
        def __init__(self, name, id):
            self.name = name
            self.id = id # Where id is a Discord role id
    return([LeagueTeam("Wombats",<PHONE_NUMBER>402038784), LeagueTeam("Kangaroos",<PHONE_NUMBER>680470109)])

async def team_autocomplete(interaction: Interaction, current: str) -> List[app_commands.Choice[str]]:
    teams = get_league_teams(interaction.guild.id) # returns list[LeagueTeam]

    return [
        app_commands.Choice(name=team.name, value=str(team.id)) # Throws: In data.choices.0.value: int53 value should be less than or equal to<PHONE_NUMBER>740991.
        for team in teams if current.lower() in team.name.lower()
    ]

# Simulated database functions returning mock tier data
def get_league_tiers(league_id):
    """Finds league from db and returns all tiers as objects"""
    class LeagueTier:
        def __init__(self, name, id):
            self.name = name
    return([LeagueTier("Wombat Joeys"), LeagueTier("Kangaroo Joeys")])

async def tier_autocomplete(interaction: Interaction, current: str) -> List[app_commands.Choice[str]]:
    teams = get_league_tiers(interaction.guild.id) # returns list[LeagueTier]

    return [
        app_commands.Choice(name=team.name, value=team.name) # Throws: In data.choices.0.value: Value "Wombats" is not int53.
        for team in teams if current.lower() in team.name.lower()
    ]

class Scheduling(commands.Cog):
    def __init__(self, bot):
        self.bot = bot

    @commands.hybrid_command(name="test")
    @app_commands.autocomplete(team=team_autocomplete)
    async def test(self, ctx: commands.Context, team: Optional[str]):
        await ctx.send(f"Team ID: {team}")

    @commands.hybrid_command(name="test2")
    @app_commands.autocomplete(tier=tier_autocomplete)
    async def test2(self, ctx: commands.Context, tier: Optional[str])

async def setup(bot):
    cmds = Scheduling(bot)
    cmds.setup_checks()
    await bot.add_cog(cmds)

Expected Results
Utilizing a role id as the value, I did not expect it to work as the discord role ids are indeed outside the expected integer range for value. However, even after type converting to a string, it still responds with In data.choices.0.value: int53 value should be less than or equal to<PHONE_NUMBER>740991.
What's more is when I instead did value=f"ID_{team.id}", autocomplate still expects this as an int53 value by responding: In data.choices.1.value: Value "ID_1288528593680470109" is not int53.`
You can see that with the tier in the example above. In using a string, a team name, as the value, we get a simialar error which can be seen below.
In short:
Autocomplete fails with large integer-like strings (even after conversion to str) [See team_autocomplete in example above]
Autocomplete fails with plain strings (like "Wombats") despite these values not being numeric. [See tier_autocomplete in example above]
Actual Results
For the team autocomplete in the example, the logs state:
In data.choices.0.value: int53 value should be less than or equal to<PHONE_NUMBER>740991.
For the tier autocomplete in the example, the logs state:
In data.choices.0.value: Value "Wombat Joeys" is not int53.
In data.choices.1.value: Value "Kangaroos Joeys" is not int53.
Intents
Default, message_content, members
System Information
Python v3.12.4-final
discord.py v2.4.0-final
aiohttp v3.10.3
system info: Windows 11 10.0.22631
Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
get_league_teams and get_league_tiers are simulated functions representing typical usage and that you’re using Discord role IDs (which are large integers).
I would like to not that this behavior limits usage for applications that rely on Discord IDs or similarly large integers, especially when autocomplete functions are expected to accept large identifiers.
For workarounds, I attempted using a surrogate by setting the value as a string representation of the original large integer, but the issue persisted. However, when mapping small integer surrogates to represent the larger integer values, the issue was resolved.
It's possible that I missed something but the docs say nothing about specific supported types for autocomplete. Further, I know from using DiscordPy in other projects that command choices can support strings as values.
PasteBin for logs:
https://pastebin.com/dfVpqPN6
If for some reason a full traceback is neccessary, do let me know.

@acr-bot

@acr-bot


Page Not Found error on kewn scans

Source information
Kewn Scans 1.4.6
Source language
English
Steps to reproduce
Add any title (like Became a Contractual daughter of a soon to be ruined family) from kewn scans to your library and try to read it in app. Opens up blank for a short while then closes up to a page not found error, also occurs if trying to download the chapter.
Expected behavior
Should open up to the chapter image files and able to bypass the ads placed as an overlay on each webpage of the scans site which needs to be closed after a short timer.
Actual behavior
Shows a No pages Found error
Mihon/Tachiyomi version
0.16.5
Android version
Android 14
Other details
The extension opens up in webview which shows the website has an ad overlay on each webpage which has a short timer required to be close before interating with anything on the page. Might be the reason the chapter image files are not being accessed by the extension crawler
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Can confirm this is also happening with kewn 1.4.6 and TachiyomiJ2K 1.7.4


Canto is offline - oliver0 is dead

curate a paper
https://curation.pombase.org/pombe/
is giving an error?

Oh canto is "down"....
oliver zero?

oliver zero?

Unfortunately, yes.  Other machines at System Biology are OK so I think it's just oliver0.
When oliver0 has problems it's always at the weekend.  :-(

closing because it's back
... but how does it know when it's the weekend, so it can fail then?

trying to figure that one out.....


There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.

Category

[x] Question
[ ] Typo
[ ] Additional article idea

Question

I have deployed pnp-modern-search package in appcatalog. trying to add Search Result webpart in modern site page. and getting below errors.

Environment details (development & target environment)

Your Developer Environment: [Windows 10]
Target Environment: [SharePoint Online]
Framework: [Node.js v10.20]
Browser(s): [IE v11 | Edge ]
Tooling: [VS Code]
Additional details: pnp-modern-search v3.16 and 3.15

Could any one please help. Its Urgent!!!!
Thanks in Advance.

Suggest you post this question to the project repo's issue list: https://github.com/microsoft-search/pnp-modern-search
This forum is for SP development questions.


Adding a failoverDelay parameter to wait sometime before triggering a failover

Following this discussion https://github.com/cloudnative-pg/cloudnative-pg/discussions/466 I worked on adding a feature to delay the triggering of a failover when the primary is considered unhealthy.

@francoispqt thank you for this!


Fix RuneIterator.current use

Fixes #119

This looks good. I see that a change in Travis-CI needs to be accounted for here. Let me see if I can fix that shortly.

FYI: I've published this with postgres 2.1.1.


test

Signed-off-by: Craig Jellick<EMAIL_ADDRESS>

Hey @cjellick what's up ?
Bored? Feeling playful?

 My bad!

RESULT: FAIL


Broken with Jest

🏳 Waving a white flag for help here
I have a fully passing eslint test suite/configuration. yarn run eslint '**/*.ts*' works handsomely.
Upon tooling the project to leverage a runner (jest-runner-eslint), the suite blows up. Hundreds of failures are logged:
Resolve error: webpack with invalid interface loaded as resolver
Errors like this, I recall, were solved after I added eslint-import-resolver-typescript to my project. This leads me to believe that something is busted in the way Jest loads .eslintrc.js or uses this module.
Has anyone else experienced this issue?

Invalid issue without any detail information, close for now.
Please provide a minimal runnable reproduction next time.


hash functions return 0 in some cases

Hash functions in this example return 0 instead of a usable value for an unknown reason.
https://github.com/Braqzen/wtf-is-this-wtf-is-that-why-does-the-hash-do-strange-things-why-are-we-even-here-what-is-life-rn

I reproduced this issue on my end using the repo provided by Braqzen.
This issue is bizarre indeed, I could not find a fix but it does not seem to be related to the compiler.
The reason I say it is not related to the compiler is that the same bytecode works when the test uses fuels version 0.44.
Changed Cargo.toml:
fuels = { version = "0.44", features = ["fuel-core-lib"] }

Changed harnes.rs:
#[tokio::test]
async fn testing() {
    let mut wallets =
        launch_custom_provider_and_get_wallets(WalletsConfig::default(), None, None).await;
    let wallet = wallets.pop().unwrap();

    let script_call_handler = MyScript::new(wallet.clone(), SCRIPT_BINARY_PATH).main();

    let response = script_call_handler.call().await.unwrap();

    let mut hasher = Keccak256::new();
    hasher.update(response.value.0 .0);
    let hashed_id = hasher.finalize();

    dbg!(response.value.0);
    dbg!(hashed_id);
    dbg!(response.decode_logs().filter_succeeded());
    dbg!(response);

    // assert!(response.value);
    assert!(false);
}

Note: I have bumped the Rust SDK to version 0.46.
When I run the code in the repo with forc version 0.42.1 the hashing results in 0 values.
When I bump forc to 0.44 the hashes seem to no longer be 0, whether the values are correct remain to be tested.

When I run forc test -l on this code,
script;

use std::{constants::ZERO_B256, hash::keccak256, tx::tx_id};

fn main() -> (b256, b256) {
// fn main() -> b256 {
    let txid = tx_id();

    // log(txid);
    // log(keccak256(txid));

    (txid, keccak256(txid))
    // txid
    // keccak256(txid)
}

// Tests are meant to fail to see diff in values
#[test]
fn test_hash() {
   let id = tx_id();
   log(id);
   let hash = keccak256(id);
   log(hash);
   // assert_eq(hash, ZERO_B256);
}

I get
[
  {
    "LogData": {
      "data": "e3402c40b71c4b8b73175ad1cbe53afd366e6652d5c213e0e9ccba033efd2a61",
      "digest": "9263961b7066816921d3e8a3967670d5359543b4ed242f7e87fdf31bc6a0056c",
      "id": "0000000000000000000000000000000000000000000000000000000000000000",
      "is": 10344,
      "len": 32,
      "pc": 10512,
      "ptr": 10952,
      "ra": 0,
      "rb": 0
    }
  },
  {
    "LogData": {
      "data": "b6947d9f9045520daaf699039461763e5129147eb88f63503b1e9696d62dbb99",
      "digest": "8240bae4853d741b27c5c7d8e97b94bfbfb83f0739f0c2aedec5fa1c404be1d8",
      "id": "0000000000000000000000000000000000000000000000000000000000000000",
      "is": 10344,
      "len": 32,
      "pc": 10576,
      "ptr": 10920,
      "ra": 0,
      "rb": 1
    }
  }
]

and I computed keccak256 of e3402c40b71c4b8b73175ad1cbe53afd366e6652d5c213e0e9ccba033efd2a61 online, which said that its b6947d9f9045520daaf699039461763e5129147eb88f63503b1e9696d62dbb99. So it all looks fine to me.

Seems to work for hex, does not work for values such as keccak256(1). That might be a different issue, padding

Seems to work for hex, does not work for values such as keccak256(1). That might be a different issue, padding

When you do keccak256(1), that's a 1u64, and keccak256(1u64)is6c31fc15422ebad28aaf9089c306702f67540b53c7eea8b7d2941044b027100f, which is what the test prints. On the other hand  keccak256(1u8)` also prints the same value, which is incorrect.
I think that we could fix this since the K256 opcode allows specifying length of the byte sequence to be hashed, and in this case it should be 1 byte, but is incorrectly generated as 8 bytes.
@IGI-111 shall we keep this Issue open to fix this? (and perhaps change the title?). It can stay assigned to me. I'll see what's the right fix.


[SPARK-12552][Core]Correctly count the driver resource when recovering from failure for Master

Currently in Standalone HA mode, the resource usage of driver is not correctly counted in Master when recovering from failure, this will lead to some unexpected behaviors like negative value in UI.
So here fix this to also count the driver's resource usage.
Also changing the recovered app's state to RUNNING when fully recovered. Previously it will always be WAITING even fully recovered.
@andrewor14 please help to review, thanks a lot.

Test build #48410 has started for PR 10506 at commit 710f5de.

Test build #48410 has finished for PR 10506 at commit 710f5de.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48410/
Test FAILed.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Test build #48413 has started for PR 10506 at commit 710f5de.

Test build #48413 has finished for PR 10506 at commit 710f5de.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48413/
Test PASSed.

Can you add a unit test? You might have to mock the completeRecovery method

Sure, will do.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48458/
Test FAILed.

Jenkins, retest this please.

Test build #48463 has started for PR 10506 at commit 3eb0b71.

Test build #48463 has finished for PR 10506 at commit 3eb0b71.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48463/
Test PASSed.

Merged build finished. Test PASSed.

Test build #52223 has started for PR 10506 at commit a117dcd.

@andrewor14 , would you please review this patch again, it is pending here a long time and I think it is actually a bug here. Thanks a lot.

Test build #52223 has finished for PR 10506 at commit a117dcd.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52223/
Test FAILed.

Test build #52225 has started for PR 10506 at commit 7cec07c.

Test build #52225 has finished for PR 10506 at commit 7cec07c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52225/
Test PASSed.

Thank you for your comment for PR #12054. I think changing app state from WAITING to RUNNING in function completeRecovery. Suppose that some app is WAITING before master toggle, then all apps and all workers get known of master changed. But if last signal (WorkerSchedulerStateResponse or MasterChangeAcknowledged) is from some worker, then function completeRecovery is revoked, which means the app I mentioned above is in RUNNING state. If the cluster doesn't have enough resource for all apps, maybe that app will be in a wrong state for a while.

Is anyone still working on this and if not, can you close the PR?

Hi @kayousterhout , I guess the issue still exists, but unfortunately there's no one reviewing this patch. I could rebase the code if someone could review it.

OK fine to leave this open then (I don't have the time or expertise to review this unfortunately)

Test build #73740 has started for PR 10506 at commit 88b58eb.

Ping @zsxwing , hopes you're the right person to review this very old PR, the issue still exists in the latest master, can you please take a review, thanks a lot.

Test build #73742 has started for PR 10506 at commit f231aed.

Test build #73740 has finished for PR 10506 at commit 88b58eb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73740/
Test PASSed.

Test build #73742 has finished for PR 10506 at commit f231aed.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73742/
Test PASSed.

I also don't feel like I know enough to review this, but if you're confident about the fix, i think you can go ahead. The change looks reasonable on its face.

Thanks @srowen , I think the fix is OK, at least should be no worse than previous code.

Could you rebase this? @jerryshao

Sure, I will bring this to update.

Test build #77627 has started for PR 10506 at commit e2d6dbf.

Test build #77627 has finished for PR 10506 at commit e2d6dbf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77627/
Test PASSed.

I think this problem shouldn't have happen in general case, could you give more specific description on your integrated cluster?

@jiangxb1987 , to reproduce this issue, you can:

Configure to enable standalone HA, for example "spark.deploy.recoveryMode FILESYSTEM" and "spark.deploy.recoveryDirectory recovery"
Start a local standalone cluster (master and worker on one the same machine).
Submit a spark application with standalone cluster mode, for example "./bin/spark-submit --master spark://NT00022.local:6066 --deploy-mode cluster --class org.apache.spark.examples.SparkPi examples/target/scala-2.11/jars/spark-examples_2.11-2.3.0-SNAPSHOT.jar 10000"
During application running, stop the master process and restart it.
Wait for application to finish, you will see the unexpected core/memory number in master UI.

This is mainly because when Master recover Driver, Master don't count the resources (core/memory) used by Driver, so this part of resources are free, which will be used to allocate a new executor, when the application is finished, this over-occupied resource by new executor will make the worker resources to be negative.
Besides, in the current Master, only when new executor is allocated, then application state will be changed to "RUNNING", recovered application will never have the chance to change the state from "WAITING" to "RUNNING" because there's no new executor allocated.
Can you please take a try, this issue do exist and be reported in JIRA and mail list several times.

@jerryshao Thank you for your effort, I'll try this tomorrow!

I think the fix is right and the test case also looks good, we'd better merge this after and some new test cases over the application running state issue. @cloud-fan Could please have a look too?

BTW, @jerryshao It would be great if we can add test framework to verify the states and statistics on the condition of Driver/Executor Lost/Join/Relaunch, is there any hope that you would invest some time on that?

It would be great if we can add test framework to verify the states and statistics on the condition of Driver/Executor Lost/Join/Relaunch

@jiangxb1987 can you explain more about what you want?

Currently we don't cover the Driver/Executor Lost/Relaunch cases in MasterSuite, and we have seen several issues related to relaunching drivers in standalone mode, so it would be great if we can write a test frame to verify the Driver/Worker states and statistics(memory/cores etc.) meets our expectations on Worker Join/Lost/ReJoin, and fix the inconsistencies in follow up PRs.

LGTM

Test build #77976 has started for PR 10506 at commit c62889a.

Test build #77985 has started for PR 10506 at commit 0bb82bb.

Test build #77976 has finished for PR 10506 at commit c62889a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77976/
Test FAILed.

Test build #77985 has finished for PR 10506 at commit 0bb82bb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77985/
Test PASSed.

Jenkins, retest this please.

Test build #77990 has started for PR 10506 at commit 0bb82bb.

Test build #77990 has finished for PR 10506 at commit 0bb82bb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77990/
Test PASSed.

thanks, merging to master/2.2! The fix is only 2 lines so should be safe to backport


Run session less then a millisecond

My needs require the session to run fast, less then 1 millisecond as to not inhibit latency to the rest of the system.
But the smallest time the client can run is 1ms because it uses uxr_millis() everywhere to measure timeout,
Is there a reason why it can't be in microseconds or nanoseconds?

I think that there is no reason for having a minimum timeout of milliseconds instead of nanoseconds. Does https://github.com/eProsima/Micro-XRCE-DDS-Client/pull/212 solve your issue?

Yes, it does solve it for my use case, i think using nanos to measure time can be nice, and will allow more flexibility.


PR Review timeline events

PullRequestReview GQL object. Has a body text and decision (accept/reject).

Working!


Improvements in Progress class and Summary view

Summary view (/apm/summary.html) have to display the same columns as currently, but with different/fixed content:

No - index
Authorizable - current authorizable
Action - name of executed action or given name for purpose of ScriptRunner (e.g. progress.show("foreach", "Start of foreach command") - "foreach" will be displayed in Action column)
Parameters - parameters passed to action, in form of list (only evaluated values, and all types of parameters: required, named, flags):

"/content/dam"
["READ", "DELETE"]
glob= "STRICT"
--IF-EXISTS

Status - status of action execution
Messages - list of custom messages

Class Progress should be adjusted to changes from above. Consider simplier way of storing messages, may be it will be enough to store them just as list of strings.

#193


fix string encoding when using xcom / json

closes: #13535
fixes the xcom issue by decoding the byte array of the log file before submitting it to xcom

Would you mind opening this PR to apache/airflow?

Would you mind opening this PR to apache/airflow?

sorry, I thought I did (not enough coffee yet):
https://github.com/apache/airflow/pull/13536

sorry, I thought I did (not enough coffee yet):
https://github.com/apache/airflow/pull/13536


lastSeen API ≠ lastSeen GUI

Hi,
maybe you could add a note that:
lastSeen API ≠ lastSeen GUI
I was struggeling using the API as it didn´t match the UI and got the answer that:
lastSeen API = Last Device Update

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

ID: 71010864-b3f8-23e1-33fe-496f136bf2b7
Version Independent ID: e4c58cda-d42f-4445-3a03-6f4c8c1e6460
Content: Machine resource type
Content Source: microsoft-365/security/defender-endpoint/machine.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@mjcaparas Please help us in resolving this issue. Thanks

Will add note.


Missing config-settings updates for v3.2

Missing some config settings updates for 3.2:

Policy tab (invites, private channel management, public channel management)
webserver mode
max file size
password requirements
system console labeling changes

FYI, after 3.2 changes are merged I'm going to propose some reformatting for this doc

@esethna I think we were planning to update the Policy descriptions for v3.3, so your call what you want to keep/change for v3.2 conifg-settings.
Otherwise only minor comments.

Thanks @jasonblais for the review, made some tweaks based on your comments. Pushing this in but keeping the PR review label so @lfbrock can review when she gets a chance.


training accuracy nearly zero

Hi,
First of all, many thanks for your support.
I tried to train a model using src\train_softmax.py, but the printed training accuracy was nearly zero.
Thanks again.

Accuracy: 0.57967+-0.03103
Validation rate: 0.00167+-0.00224 @ FAR=0.00100
....

arguments.txt
prelogits_hist_max: 10.0
prelogits_norm_p: 1.0
lfw_distance_metric: 1
model_def: models.squeezenet
moving_average_decay: 0.9999
lfw_use_flipped_images: True
validate_every_n_epochs: 1
log_histograms: False
lfw_subtract_mean: True
data_dir: ../data/webface-182x182
learning_rate_schedule_file: ../data/learning_rate_schedule.txt
learning_rate: 0.05
filter_filename:
lfw_nrof_folds: 10
center_loss_factor: 0.0
center_loss_alfa: 0.95
learning_rate_decay_factor: 0.1
embedding_size: 128
max_nrof_epochs: 5
use_fixed_image_standardization: True
nrof_preprocess_threads: 4
models_base_dir: ../train/models
seed: 666
validation_set_split_ratio: 0.1
random_rotate: True
pretrained_model: None
min_nrof_val_images_per_class: 0
image_size: 160
learning_rate_decay_epochs: 5
filter_min_nrof_images_per_class: 0
lfw_batch_size: 10
weight_decay: 0.0004
logs_base_dir: ../train/reult/log
keep_probability: 1.0
gpu_memory_fraction: 0.85
random_crop: True
batch_size: 10
epoch_size: 10
prelogits_norm_loss_factor: 0.0
random_flip: True
filter_percentile: 100.0
lfw_pairs: ../data/pairs.txt
lfw_dir: ../data/lfw-182x182
optimizer: ADAGRAD

3, lfw_result.txt
0	0.56667	0.00933
10	0.57950	0.01033
20	0.58050	0.00767
30	0.57050	0.00500
40	0.57333	0.00600

did you solve the problem? i  miss the same problem...

Hi!!!
I have the problem.do you have a meth to do?

I really want to know how to solve this problem


[API] Change Endpoints endpoints to Environments endpoints

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
There is different names for similar features in UI and API. API Endpoints should be updated to use similar terms in next  minor release.

Actual Behavior
Environments are using old endpoints term.
Steps to Reproduce

Login to Portainer
Check term used for different servers/nodes
Open API documentation from SwaggerHub.
Check term used in API

Portainer logs or screenshots
No response
Enter your Portainer version
2.18.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker
OS and Architecture
Debian 12
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response

My suggestion is to support using /endpoints and /environments in version 2.19.x and in version 2.20.x support for /endpoints would be removed.

"Endpoints" was renamed to "Environments" in version 2.10. For legacy reasons we have kept the old endpoint names, as we don't want to break functionality for anyone that was using the API before we changed the naming scheme. In saying that, I will discuss this with the wider team to see if there's any changes coming in that regard.


How does one initializemiddleware for multiple swagger documents?

The singular call to swaggerTools.initializeMiddleware DOES NOT support this.  You could do this by chaining your calls, so long as each document has a separate base URL and/or the paths do not collide.

Is there a good example in node that allows chaining of initialize calls.  I tried to do something like that but did not seem to work.  The first document that I use to call 'swaggerTools.initializeMiddleware(swaggerDoc, function (middleware)'
seems to take precedence regardless of how many other ones I initialized after it.

It's just like any other callback-based API.  You can use something like async or do it manually yourself:
swaggerTools.initializeMiddleware(doc1, function (mw1) {
  // Do stuff with first middleware

  swaggerTools.initializeMiddleware(doc2, function (mw2) {
    // Do stuff with second middleware

    // Repeat...
  });
});


Added "Neural Implicit Surface Evolution" entry.

Added the "Neural Implicit Surface Evolution" under the "3D Shape Modeling and Processing" section. Added arXiv, github repo and youtube video links as well.

Hi @schardong, 👋
Thank you for your collaboration. The changes have been accepted.


Avatar and biographer name should reflect in chat window

At the moment, when avatar name and biographer name is set, the same is not reflected in chat window.

Getting the same failure- Bot Greeting references do not change change


Add super ninja style mixin to make this even easier to use.

Template tags suck. Settings are globals. What about being able to configure per view?
Imagine this:
class PaginatorMixin(object):
    theme = PAGINATOR_THEME  # from settings but overridable
    caching = PAGINATOR_CACHE # boolean for caching of results for moar speed
    paginate_by = 10 # Because we know for certain we'll be paginating

    def paginator(self):
        # Because we're getting the template here, we can probably cache the load somehow.
        template = get_template(self.theme)
        # Add all the normal paginator stuff
        context = template.add_stuff_like_page_obj()
        return template.render(context)

Usage will be easy:
class MyModelListView(PaginatorMixin, ListView):
    model = MyModel

<!--  Loop through the content -->
{% for mymodel in mymodel_list %}
{{ mymodel.title }}
{% endfor %}

<!-- Call the view method -->
{{ view.paginator }}

And that's it! No loading of template tags. That means code isn't stuck in the dark corner of template tags. It exists in a relative simple model, or better yet easy tested utility functions.

I have a rough of this but it's in a really unclean state. I'll try to get it in this week.


Gallery

Hi all,
I have been discussing creating a Gallery with @LouisDesdoigts. This would just be cool animations and images of apertures with emphasis on the cool things you can do, not the how and why. I was inspired by the (R Graph Gallery)[https://r-graph-gallery.com/].
Regards
Jordan

Yeah, great idea!


1f994.png is missing

Describe the bug
missing emoji png?
To Reproduce
Open for example https://nft.kodadot.xyz/rmrk/detail/7373514-e8fe2f9cd718f4c43f-HQP8Q-HEDGEHOG-0000000000000001
check console

Closed as we have migrated to full emoji picker


Pcre2 concat

Add rule concatenation in pcre2. The command line option is turned off by default, to turn on specify -c 1 .

The rule option handling has been implemented. Also please note I rebased the branch due to the code conflict. Please discard your local one then do git pull.


Feature - header & footer

allows ui-select-header and ui-select-footer directives to be embedded in the select dropdown.
Example Structure with header and footer:
<ui-select>
    <ui-select-match></ui-select-match>
    <ui-select-header>Top of the list!</ui-select-header>
    <ui-select-choices><ui-select-choices>
    <ui-select-footer>Bottom of the list.</ui-select-footer>
</ui-select>

Not sure what's up with travis tests failing, all karma tests pass when I run local gulp.  Looks like most recent PR's are failing their travis tests too.

Bonus side effect - using ui-scrollpoint inside a ui-select-footer, I was easily able to add infinite scrolling to my ui-select choices.

The infinite scrolling benefit is pretty cool.
Since you're prepending/appending the header and footer to the ul element, does that mean the header and footer scroll into/out of view? I think the folks over in #496 were hoping for a static overlay above and below the scrolling area.

Oh yes, you are right.  They do scroll into and out of view.  I think you could might be able to have them stay in place with css?  I will need to test that.  If not, I will think about adding something like a fixed="true" attribute.

I suspected a CSS solution might be applicable too. A quick search around Stack Overflow indicates it might be a bit tricky, though.
That said, I'm not sure there is much that can be done without seriously reorganizing the templates since the top-level element of choices.tpl.html is an ul element. I needed a header for my project, so I did an add-on directive to implement the header functionality, and the approach was much the same as you took.

Ok, well I just read this article: http://webdesign.tutsplus.com/tutorials/sticky-positioning-with-nothing-but-css--cms-24042
Looks like it should be as easy as postion: sticky;  but as the article notes, it is not supported in all browsers yet :(
I tested position: fixed; in chrome, it worked for the header.  I am not going to call it a solution though, because position: fixed; is always supposed to be to the window, not the parent.
I tried using the ngSticky module with no success.
Going to branch my fork and see about adding the fixed property to my uiSelectHeader/uiSelectFooter directives.

Would it make sense to transclude the directives a little higher up the DOM tree?

Also, I was trying out your code and thought it looked a bit better if I included a bootstrap list separator as well:
transcludedChoices.prepend(angular.element('<li>').addClass('divider').prop('role', 'presentation'));
transcludedChoices.prepend(transcludedHeader);

Hmm not sure if it would work with the directives higher in the DOM tree.  If I recall, it is the <ul> element that gets shown/hidden/scrolled.

Yeah, there would have to be some new CSS and custom logic to show/hide those elements, or maybe just a new container around the ul element that can be toggled instead.
For what it's worth, I have your current code monkey-patched in and it's working well.
Is fixing the travis build just a matter of merging upstream changes?

ya just merged upstream and travis build passes now.

I've got a gulped branch at https://github.com/TechNaturally/ui-select/tree/feat-header-footer-bower
You can use it in your bower.json dependencies with:
"angular-ui-select": "TechNaturally/ui-select#feat-header-footer-bower"

The history on this needs fixing - there should not be any merge commit.

Fixed history

It would probably also be good to add documentation and an example so that users know the feature exists once it is available.

Just added a wiki page.  Working on an infinite-scroll example using ui-select-footer and ui-scrollpoint

You'll need to rebase especially following changes to examples in #1550 (you can just move your <script> to the body and update demo.js
Once that's done I'll merge.

@user378230 thanks...  rebased, and renamed/updated the demo to include a basic example.
I am not sure that I could use a <script> tag though, because I need to add ui.scrollpoint as a dependency of demo module and add the infinity object onto DemoCtrl's scope vm.  If you could please advise a method to do this from a <script>, I would be happy to.

@plong0 Can we drop the infinite scrolling portion of the example for now? Instead how about you create it as a plunkr (You can use the examples at http://angular-ui.github.io/ui-select/#examples as a start point) I suggest you could leave a link to the plunkr in your demo-...html file and also on the wiki page.
This way we can get it merged and released sooner. We can look at modifying the examples set up at a later date.
Thanks a lot for your patience and hard work on this :+1:

Hm, can't seem to get it working on plunker
Works in production, but on plunker it doesn't seem to add the <li>'s for header and footer.  Can't figure it out right now.

Hm, looks like things changed quite a bit since I originally opened this PR.  Can't see why with the newer version the <li>'s I add to transcludedChoices aren't coming in.  plunker

It looks like angular v1.2.18 -> v 1.4.x is fine but angular v1.5.0+ is broken. There was probably a breaking change in v1.5.0 that is causing this.

@plong0 I think vm.infinity should be a directive in case of multiple ui-select use. Then we can pass data like $scope.countries as  isolated scope, and be able to change settings (count, limit etc) inside template. WDYT?

@mityalebedev yes, that is a great idea to set infinity as a directive (honestly, I whipped that demo up pretty quick, but definitely in production code an infinite-scroll directive is where it's at).
I hit a block when I started setting up the plunker and the ui-select-header and ui-select-footer directives failed to work...  @user378230 suggested it was a BC in angular 1.5.0, so I will need to dig into that a little bit to try to sort out.  Doesn't seem much sense to merge this PR before it's verified working with 1.5.0.
select.js in the plunker has the latest code of this fork compiled and pasted in if anyone is able to dabble and help figure out why it's broken.  Looks like in the newer version of ui-select, ui-select-choice transclusion has gotten a tad more complicated.

I just poked around at it a bit more, but can't see why it works in angular 1.4 but not 1.5
The trouble appears to be that any children appended to transcludedChoices don't stick around.  Other manipulations like transcludedChoices.addClass('test-class'); seem to work though.
I don't have a whole lot of time to debug the difference between 1.4 and 1.5, so hoping someone in the community can help with that.

up ?

@GDuchemin please post meaningful responses to issues, thanks!
Also not that this PR doesn't work with angular 1.5.x as per previous replies, can't be merged until it does.

I just try reselect the target to prepend and append transcludeHeader and transcludeFooter with element.querySelectorAll('.ui-select-choices'), wrapped all in $timeout and it's seems working.

@GDuchemin maybe post your code?

uiSelectDirective.js after line 230:
`var transcludedHeader = transcluded.querySelectorAll('.ui-select-header');
if(transcludedHeader && transcludedHeader.length){
transcludedHeader.removeAttr('ui-select-header'); //To avoid loop in case directive as attr
transcludedHeader.removeAttr('data-ui-select-header'); // Properly handle HTML5 data-attributes
$timeout(function(){
element.querySelectorAll('.ui-select-choices').prepend(transcludedHeader);
});
}
      var transcludedFooter = transcluded.querySelectorAll('.ui-select-footer');
      if(transcludedFooter && transcludedFooter.length){
        transcludedFooter.removeAttr('ui-select-footer'); //To avoid loop in case directive as attr
        transcludedFooter.removeAttr('data-ui-select-footer'); // Properly handle HTML5 data-attributes
        $timeout(function() {
          element.querySelectorAll('.ui-select-choices').append(transcludedFooter);
        });
      }`

I just defined again the selector before prepend and append code.

var transcludedHeader = transcluded.querySelectorAll('.ui-select-header');           if(transcludedHeader && transcludedHeader.length){             transcludedHeader.removeAttr('ui-select-header'); //To avoid loop in case directive as attr             transcludedHeader.removeAttr('data-ui-select-header'); // Properly handle HTML5 data-attributes             $timeout(function(){               element.querySelectorAll('.ui-select-choices').prepend(transcludedHeader);             });           }

Thanks so much for the input @GDuchemin! your solution for appending after $timeout works in angular 1.4 + 1.5.
I've rebased my branch and done a bit more work to refactor with the $timeout.  I also added a $compile of the ui-select-choices after appending header and footer.
The reason for the re-compile is in case any directives in the header or footer require the ui-select-choices or any of its attribute directives.  For example: in the infinite-scroll demo, the ui-scrollpoint inside the ui-select-footer requires the ui-scrollpoint-target on the ui-select-choices in order to detect when the choices have been scrolled.
Plunker demo updated with latest compiled select.js+select.css copied in.
Everything seems to be working with angular 1.4 + 1.5!
I think this branch might finally be ready to merge...

Great work @plong0 :)

When will this be merged?

@dannydinges if you watch the repo you should get a github notification when this thread is updated, you can then pop by to see if it's been merged. Hope that helps! :smiley:

@plong0, maybe you know, why ng-click in ui-select-header is fired twice?

Hello,
Any idea when this PR will be merged and released?

@user378230 what is the needs: PR test(s) label?

@kotmatpockuh I also encountered the same problem. Did you solve the problem?

@kotmatpockuh @chansx The problem seems to be this. Commenting out the $compile call (line 254 in src/uiSelectDirective.js) worked for me as there was no need for an extra compile in my use case.

@kotmatpockuh @chansx @gpsinghsandhu
Based on the answer @gpsinghsandhu linked to, maybe it needs to $compile each transcluded bit separately rather than the entire selectChoices -  Something like this

Probably merge and release? =)

Any updates on this?

@kotmatpockuh, i encountered the same problem, even worse, ng-if will generate each time you open & close the list.
The reason is that compliation: https://github.com/TechNaturally/ui-select/blob/b743fcce965ad6ed1ab4a200e961d119af774b42/src/uiSelectDirective.js#L254

I`ve created a clean PR that implements header & footer without hacks.
You can create a theme for it, there is no double compilation therefore there is no double click trigger bugs.
https://github.com/angular-ui/ui-select/pull/1930

Could somebody say when this PR will be released?

It has been released. Closing this PR down.

Could you please validate the release number it is supposed to be included in? I checked the latest and

select.js still says version 0.19.7
select.js does not contain any reference to "footer"
the directive uiSelectFooterDirective.js is not in the src folder anymore

Was the feature removed or something?
Thanks

It was removed, there is another PR that waits for a long time to be merged.
https://github.com/angular-ui/ui-select/pull/1982


isShorthandProperty lookup perf. improvement

Isn't key lookup faster than extracting all keys and checking them one by one, at least for a pure json object ?

LGTM


Update svc-cpp.md

It wouldn't compile without these changes
\Svc.cpp(41): error C2561: 'main': function must return a value
.\Svc.cpp(33): note: see declaration of 'main'
.\Svc.cpp(76): error C2664: 'DWORD GetModuleFileNameA(HMODULE,LPSTR,DWORD)': cannot convert argument 1 from 'const char [1]' to 'HMODULE'
.\Svc.cpp(76): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast

@nico-abram : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Bucket Types usage changed/broken in KV 3.0.1

Expected behaviour - bucket type created, prompted to activate new type.
Actual behaviour:
[root@localhost ~]# riak admin bucket-type create n_val_of_2 '{"props":{"n_val":2}}'
Cannot create bucket type n_val_of_2: invalid json

[root@localhost ~]# riak admin bucket-type create user_account_bucket '`cat /tmp/props.json`'
RPC to<EMAIL_ADDRESS>failed: {'EXIT',
                                 {function_clause,
                                  [{riak_kv_console,bucket_type_create,
                                    [["user_account_bucket","{","\"props\":",
                                      "{","\"precommit\":",
                                      "[\"syntax_check\"],","\"postcommit\":",
                                      "[\"welcome_email\",",
                                      "\"update_registry\"]","}","}"]],
                                    [{file,
                                      "/root/riak/rel/pkg/out/BUILD/riak-3.0.1/_build/default/lib/riak_kv/src/riak_kv_console.erl"},
                                     {line,499}]},
                                   {rpc,'-handle_call_call/6-fun-0-',5,
                                    [{file,"rpc.erl"},{line,197}]}]}}

The props.json file is owned by the riak user and is as follows:
{
  "props": {
    "precommit": ["syntax_check"],
    "postcommit": ["welcome_email", "update_registry"]
  }
}

The inline example is copied from https://www.tiot.jp/riak-docs/riak/kv/2.2.6/using/reference/bucket-types/#bucket-types-and-the-allow-mult-setting and the props.json file used is copied directly from https://www.tiot.jp/riak-docs/riak/kv/2.2.6/using/reference/bucket-types/#bucket-type-example
Attempting to create a bucket type with no special properties i.e. riak-admin bucket-type create namespace_bucket '{"props":{}}' also returns "invalid json".
I have tried with both the Yokozuna and non-Yokozuna packages for KV 3.0.1. I also tried with a devrel and got a different path for riak_kv_console.erl in the error that was specific to my devrel build.
Manual experimentation with the json format for the inline example either results in "invalid json" or the same error as when trying to create from a json file.
Non-bucket type creation seems to work fine e.g. taking the curl example from https://www.tiot.jp/riak-docs/riak/kv/2.2.6/developing/usage/creating-objects/#write-parameters gives:
[root@localhost ~]# curl -XPUT -H "Content-Type: text/plain" -d "vroom" http://localhost:8098/buckets/dodge/keys/viper?w=3

[root@localhost ~]# curl http://localhost:8098/buckets/dodge/keys/viper
vroom

These console commands all get handled by relx (having previously been under the guise of nodetool).  Whatever was handling json inputs no longer works in relx.
All the tests attach to the node to set bucket types, so this should still work via riak remote_console:
(riak@<IP_ADDRESS>)1> riak_core_bucket_type:create(<<"maps">>, [{datatype, map}]).
(riak@<IP_ADDRESS>)2> riak_core_bucket_type:activate(<<"maps">>).

This is the best workaround for the moment.  I don't know what's going to be involved in fixing the way relx scripts work to get all the old console commands going again.

I have a fix for this. I'll create a PR shortly.

#1044 fixes this.

https://github.com/basho/riak_kv/pull/1781 resolves the issue when no props are passed - a type is created with empty props

https://github.com/basho/riak_kv/pull/1781 resolves the issue when no props are passed - a type is created with empty props

Fixed in Riak KV 3.0.2. Default bucket type behaviour updated to match 2.x.x from Riak KV 3.0.3

Fixed in Riak KV 3.0.2. Default bucket type behaviour updated to match 2.x.x from Riak KV 3.0.3


Sort toggle button not working

What is the motivation for adding/enhancing this feature?
There is already a button which seems like it is for sorting by Asc and desc but it isn't working
What are the acceptance criteria?
Items are displayed to user on reverse order after clicking button if it was asc before it should be desc and vice-versa
Can you complete this feature request by yourself?

[ X] YES
[ ] NO

Additional information
Please assign this to me
https://github.com/hotwax/commerce-hub/assets/109908523/b1f5f177-6daf-4ece-af93-f6f3cbb1b1ab

Hi @palash018
Are you having any error/warnings in console?
Also I would suggest to check other apps, like fulfillment, picking, inventorycount etc for issues.

@ymaheshwari1 There are no additional errors and warnings when i click on that button but i have warnings and errors which are already present before the button press also you are asking me to look for similar sorting issue in other repos right?
also when i click on the button there is some change happening when i inspect that means it is calling something but the expected result is not happening

Alright @ymaheshwari1 are you able to reproduce this issue?

Alright @ymaheshwari1 are you able to reproduce this issue?

No, everything is working as expected.

Not priority for now. Hence, closing this issue.


x/tools/gopls: improve the UX when the gopls daemon panics

Sometimes gopls panics. Hopefully this is becoming increasingly rare, but by definition panics are unexpected and disruptive to the user experience. vscode-go improves the UX with special handling to identify and capture panics, but for other editor plugins the disruption can be completly opaque: gopls just stops working.  Particularly when running gopls as a daemon, stderr is often /dev/null, and finding the panicking stack involves re-running the daemon and trying to reproduce the panic.
We can do better, by ensuring that stderr is always captured and doing our best to make it discoverable.  Here is one way to achieve this:

If os.Stderr is /dev/null:

create a tempfile with 0600 permissions (conservative permissions since the caller didn't ask us to do this)
Redirect stderr to this temp file (using syscall.Dup2 for POSIX systems, etc.)
defer a cleanup func that redirects back to /dev/null and then deletes the tempfile

In the daemon, if os.Stderr is a normal file, tell the gopls forwarder about it during handshake.
In the forwarder, track whether "shutdown" or "exit" have been called by the LSP client.  Detect abnormal daemon disconnection when "shutdown" or "exit" haven't been called.
On abnormal exit from the daemon, before closing the client connection, inject a message to the effect of "The gopls daemon exited abnormally. Please check the output at path/to/stderr and consider filing an issue at golang.org/issues"

The net effect of this should be that when the gopls daemon panics the deferred cleanup will not run and the temporary stderr will be persisted. Then, the LSP client will get a ShowMessage notification explaining what went wrong, and suggesting next steps.
CC @myitcv @leitzler @bhcleek, who might have opinions on this UX as plugin maintainers.

FWIW, I don't think vim-go needs any special handling in gopls; I probably just enhance vim-go to handle a gopls panic better. It's not too hard to do; I just need to prioritize it.

Thanks very much for raising this.

vscode-go improves the UX with special handling to identify and capture panics

Isn't the issue here that, when working in remote mode, the panic doesn't make its way to the LSP client?
What does VSCode do in that situation? Presumably it suffers the same problem?

If os.Stderr is /dev/null:

In the case of remote mode, isn't os.Stderr always going to be /dev/null for the daemon? Or have I misunderstood something?

In the daemon, if os.Stderr is a normal file, tell the gopls forwarder about it during handshake

Related to the previous point, isn't it generally going to be the case that the daemon will tell the forwarded about the location of its (the daemon's) stderr log file? Because it would seem to be the exception that the forwarder would tell the daemon where to log (because the forwarder will, generally, have a shorter life than the daemon).

On abnormal exit from the daemon, before closing the client connection...

I assume you are talking about the forwarded detecting this condition of abnormal exit, right? And hence talking about the LSP client connection? (as opposed to the forwarder as a client of the daemon)
Just to confirm one point here. We (govim) are treating the forwarded closing the connection to the client (i.e. us, govim) as abnormal. Because in normal operation it would only ever be the LSP client initiating the shutdown. That remains "correct" I assume?

The net effect of this should be that when the gopls daemon panics the deferred cleanup will not run and the temporary stderr will be persisted

This sounds like a real improvement.
Is there some way that the LSP client can also learn about the location of the remote (temporary) stderr log? That would be a nice thing for us to be able to add to GOVIMLogfilePaths in any case.
FWIW we are discussing/working on better restart logic in https://github.com/govim/govim/issues/963. Indeed, per that issue, it would be good to have some test-only way of triggered a panic in the daemon so that we can test the handling via govim.
cc @cespare

Isn't the issue here that, when working in remote mode, the panic doesn't make its way to the LSP client?

That's one issue. In my opinion it is also an issue that each client has to implement their own special handling for panics. For generic LSP clients this is not really possible, which is why I want to implement more graceful handling on our side.

In the case of remote mode, isn't os.Stderr always going to be /dev/null for the daemon

Not in general, because the daemon can be started manually.  But if using -remote=auto, yes.

Related to the previous point, isn't it generally going to be the case that the daemon will tell the forwarded about the location of its (the daemon's) stderr log file

Yes, that is the expectation. It's not enough to have whatever gopls instance starts the daemon set the logfile, because the daemon can be manually managed. If I do gopls serve -listen=:8095 2> /tmp/gopls.daemon.stderr, I would expect that the daemon tell each of its clients about /tmp/gopls.daemon.stderr.

stderr log file

Just to be clear, there's a difference between logfile and stderr. We already tell each forwarder gopls about the daemon's log file, but this file is configured via log.SetOutput, which means it doesn't capture panics.

I assume you are talking about the forwarded detecting this condition of abnormal exit, right? And hence talking about the LSP client connection?

Yes, I should have been more clear in this section (especially for any readers who don't know what the forwarder is). We have the following diagram:
LSP Client --stdin/stdout--> gopls forwarder --tcp/uds--> daemon

Where the gopls forwarder is just responsible for discovering the daemon and forwarding the LSP. But because it operates at LSP level rather than net.Conn level, it is able to do some intercepting of messages along the way. The only place where we currently do this is to set the process environment, but I am proposing that we also use this layer to track whether the LSP client has properly shutdown. This allows us to detect when the daemon exits abnormally.  In this case, we have an opportunity to send a final notification to the LSP client explaining what went wrong. I've tested all this and it works.

Because in normal operation it would only ever be the LSP client initiating the shutdown.

Yes, that's how it is supposed to work.

Is there some way that the LSP client can also learn about the location of the remote (temporary) stderr log

We could do this. The forwarder will have this information because it is exchanged in the handshake. Do you have a preference for how this information is surfaced?

test-only way of triggered a panic in the daemon

Can you just SIGTERM the daemon? From the perspective of govim that should be equivalent.

... which is why I want to implement more graceful handling on our side

Ah, that clarifies things, thank you.

Not in general, because the daemon can be started manually. But if using -remote=auto, yes.

Good point.

I would expect that the daemon tell each of its clients about /tmp/gopls.daemon.stderr.

That makes it clear, thank you.

there's a difference between logfile and stderr

Thanks for clarifying.

Do you have a preference for how this information is surfaced?

Other than "something structured", no 😄

Can you just SIGTERM the daemon?

Won't that entirely side-step all the infrastructure we're putting place for panic handling? It seems to me we're looking to test that as part of any test suite here.

Won't that entirely side-step all the infrastructure we're putting place for panic handling?

No, there's nothing special about panics, and this should work equally well for any other 'crashes'.  But if we need to we can add a non-standard request to force a panic.

Other than "something structured", no 😄

For my own debugging purposes, I have a gopls -remote=<...> inspect sessions command that queries the information exchanged in the handshake as JSON. Would shelling out to a command like this work for you?
@bhcleek, regarding this:

FWIW, I don't think vim-go needs any special handling in gopls; I probably just enhance vim-go to handle a gopls panic better.

Per the above discussion, I think fundamentally when using -remote=auto there's no easy way for LSP clients to implement graceful handling on their own.
Unless there's specific objection, I am planning to go ahead with this plan.  We can iterate as needed, but I think the core of it -- making sure we're capturing STDERR -- will be necessary no matter what.

No, there's nothing special about panics

Right, I see what you're saying - this is effectively something that we as LSP clients can consider "tested". As you say, we can always add a non-standard request in case it becomes necessary to get coverage on this (the SIGTERM approach certainly works well enough for testing our handling of restarting logic - thanks for pointing that out)


fix(firestore-bigquery-export) use modules instead of namespaces

This is a PR to correct the error in the following issue.
https://github.com/firebase/extensions/issues/1533
After checking where the error is occurring, it appears that there is a problem with the require syntax that is importing the module.
I think that the correct code should be as follows (typescripts build to javascripts).
correct:
const firestore = require("firebase-admin/firestore");

In other words, I think the problem is using the global admin namespace, as in the following code.
https://github.com/firebase/extensions/blob/firestore-bigquery-export-v0.1.31/firestore-bigquery-export/firestore-bigquery-change-tracker/src/bigquery/index.ts#L18
This should be redefined as follows (I am aware that it says so in Use modules instead of namespaces).
import { DocumentReference } from 'firebase-admin/firestore';
...
    serializeData(eventData) {
        ...
                if (property.constructor.name === DocumentReference.name) {
                    this.update(property.path);
                }
            }
        });
        return data;
    }

CI isn't running for some reason, closing in favour of https://github.com/firebase/extensions/pull/1561


fix:missing override annotation

Codecov Report

Merging #122 (31bbfc7) into main (9147d8e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #122   +/-   ##
=========================================
  Coverage     65.42%   65.42%
+ Complexity     8413     8408    -5
=========================================
  Files           421      421
  Lines         46528    46528
  Branches       9457     9458    +1
=========================================
  Hits          30443    30443
  Misses        12433    12433
  Partials       3652     3652

Impacted Files
Coverage Δ

...n/java/com/alibaba/fastjson2/JSONWriterPretty.java
88.76% <ø> (ø)

.../com/alibaba/fastjson2/writer/FieldWriterDate.java
88.20% <ø> (ø)

...om/alibaba/fastjson2/writer/FieldWriterObject.java
68.98% <ø> (ø)

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 9147d8e...31bbfc7. Read the comment docs.


Error while trying to install package.

develop branch
I installing the package
;; -*- no-byte-compile: t; -*-
;;; ~/.doom.d/packages.el

(package! emojify)

do make in .emacs.d and there is an error:
Contacting host: orgmode.org:443
Package refresh done
Installing emojify
✓ DONE
Finished!

Deleted old autoloads.pkg.el
✓ Cached package state
✓ Package autoloads included
✓ Removed load-path/auto-mode-alist entries

Eager macro-expansion failure: (error "Found package! call in non-packages.el file (~/.doom.d/packages.el)")
Eager macro-expansion failure: (error "Found package! call in non-packages.el file (~/.doom.d/packages.el)")
--------------------------------------------------

There was an unexpected error:
  Error in private config (doom-private-error)
  packages.el
  (error Found package! call in non-packages.el file (~/.doom.d/packages.el))

Run the command again with the -d (or --debug) option to enable debug
mode and, hopefully, generate a stack trace. If you decide to file a bug
report, please include it!

Emacs outputs to standard error, so you’ll need to redirect stderr to
stdout to pipe this to a file or clipboard!

  e.g. doom -d install 2>&1 | clipboard-program
Detected a running Emacs session.

Restart Emacs or use ‘M-x doom/reload’ for changes to take effect.

What I did wrong?

This is an odd error. It's complaining you are using package! outside of a ~/.doom.d/packages.el file.
Are you sure you do not have something like
(load! "+packages")

in your ~/.doom.d/config.el or ~/.doom.d/init.el? That would cause this error. You musn't try to load init.el, config.el or packages.el yourself, these are special files.

@hlissner I have
(load! "packages")

In my config.el, you said to me that only init.el and config.el loads automatically, so I think I should load packages.el too

Ah I see. My bad. That is not the whole picture: init.el and config.el are the only files loaded at startup, but they are not the only special files.
These are all the "special" files that a module may have:
init.el
config.el
packages.el
doctor.el
autoload.el
autoload/*.el

packages.el is only loaded when Doom needs to see what packages this module needs (like when you run bin/doom refresh or bin/doom install. You don't need to load it yourself.
doctor.el is called by bin/doom doctor, and gives your module a chance to check if its dependencies are properly installed and set up (and complain otherwise).
autoload.el and autoload/*.el should contain functions with an ;;;###autoload cookie. These files aren't loaded until these autoloaded functions are called.


[T4PUB-663] Support nvme boot with ota-client on ROSCUBE-X

Introduction
Supporting nvme boot with ota-client, along with improvement over extlinux_control module and configs module

ota-client now supports 2 kinds of boot-from-nvme-storage mechanism:
1.1: rootfs on nvme storage(tested, working as expected)
1.2: native boot from nvme storage(not tested, but extlinux_control module should support it)
ota-client can automatically detect the present of rootfs on external storage, and also backward support boot with internal storage if the ROSCUBE-X runs on internal storage
refactor to the configs module, use built-in dataclasses to compose Config class
other minor changes and cleanup

Details
The ota-client support 2 kinds of boot-from-nvme-storage mechanism as follow:

When detects the present of external nvme storage, ota-client will first update the partition on nvme storage, and ensure the extlinux.cfg and kernel/initrd files in nvme partition's /boot folder, ensuring the mechanism 1.2.
And then the ota-client will also sync the /boot folder to the corresponding emmc partition, which ensuring the mechanism 1.1.

cp -rdp is working as expected! I simplify the /boot folder updating logic in e793fec and it works on real machine as expected.

@Bodong-Yang I'd like to confirm if the change works properly on ROS CubeX.


Improve keyboard accessibility of the Tabs component

The Tabs component supports moving the focus by Tab key. According to WAI-ARIA Authoring Practices, the keyboard interaction should also support:

Using the ←  / →  arrow key to move focus to the previous/next tab. For performance reasons, we may not want to activate the newly focused tab automatically.
Using the Space or Enter key to activate the tab.

👍 Nice, assigning this to 1.1.0 (next release)


Adds bins to style by size

Closes #10148
Adds a bins pane so we can style by size using the classification method:

cc: @saleiva @makella @rochoa

CR: @xavijam

The CartoCSS generation is working properly=

Is the CartoCSS generation working properly?

Yes, the makeWidthRamp method of the style-converter.js file was already supporting the number of bins.

The future was written... scared. Ok, :es:.

Could we use:
marker-width: ramp([ccc], range(1, 20), headtails(7));

Could we use:
marker-width: ramp([ccc], range(1, 20), headtails(7));

Sure. Much better syntax. I'll make the change.

Ok, syntax updated. Have a look here, please.

i just want to say this is the most awesome thing. this is something that we haven't done properly in the past for proportional symbol maps. i can't say thank you enough for getting this in!! it is amazing.


add IDs to automations for traces

Proposed change

Add IDs to automations so Home Assistant's trace system can be used to locate problems with automations.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR is related to issue: #228

Ya the bulk of this is black formatting the files, but all the ids are just copies of the aliases


process expired

I'm trying to hide the launcher when the game starts and open it after the game closes, after closing the game the function process.Exited doesn't work.

        var process = await launcher.CreateProcessAsync(startVersion, launchOption);
        process.Start();

        this.Hide();
        process.Exited += (s1, e1) =>
        {
             this.Show();
        };

https://stackoverflow.com/questions/4504170/why-is-my-processs-exited-method-not-being-called
process.EnablRaisingEvents = true;


No need for caching in sorted-iterator

Summary
In #71 we changed the block order. while checking the full iteration on Object Store (S3), we saw it is amazingly slow.
What happened is that it switched to Random IO mode:
.. 15:42:50,084  INFO fs.s3a.S3AInputStream - Switching to Random IO seek policy
Detailed Description
After debugging it looks like it happened because we try to seek back compared to the "natural" readahead buffer.
Luckily, now that we changed the block order we can just read the file sequentially without hopping at all. So just removing the seeking part works!
How was it tested?
regular unit tests

What... How is that possible? When you reach a leaf block, you have to go back and seek elsewhere, no?

I was also surprised that it just worked, but what happens is just that the parent blocks are saved in memory, and every time you need to read the next block from the file it is always the "correct" block as we saved it pre-order.

Wow

Are the parents explicitly cached by us? Do we make sure to uncache them? Just to make sure there is no memory leak or something

good point.
I actually thought about that and forgot to check. but it looks like we're good.
the sorted-iterator only has one pointer to Node next and the Node object only has one pointer to parent. So we will maximum log(n) nodes in memory.
BTW, I also need to verify this "Random IO" in the "search" iterator (get()).

ok.. so after looking at get(key) , I saw that we can hop backwards there if we were calling get() multiple times.
So I added assertion to allow only bigger keys, and added functionality to reuse the current state.

Is this ready for release? Is it good for all three of our versions?


The packages section still shows the number of flatpak packages installed, even after uninstalling all flatpaks (and even flatpak entirely)

I'm using 2.2.3, upgraded from a previous version. I tried uninstalling and reinstalling.
I'm using Debian Testing.

fastfetch searchs for installed app folders directly. This issue could happen if you uninstalled flatpak but didn't remove the app folders.
Try removing /var/lib/flatpak and ~/.local/share/flatpak

Thank you, I didn't consider that.


Update npm module

The currently published npm module does not seem to include the latest features. Specifically, flexible array matching via eachLike isn't available.
Would be great to a see a push happening soon. :-)

Done.


newDateInternal does not adjust creation from fixed point date strings

Modifying the in documentation editor to:
Sugar.Date.setOption('newDateInternal', function() {
  var d = new Date(), offset;
  offset = (d.getTimezoneOffset() - 600) * 60 * 1000;
  d.setTime(d.getTime() + offset);
  return d;
});
Sugar.Date.create("1/20/2017 7:15 pm").toString();

Returns "Fri Jan 20 2017 19:15:00 GMT-0800 (PST)" with the above code and if you overload offset to 0. I would expect the date string to be parsed with respect to Hawaii time, ie 5:15pm PST

As the docs mention, newDateInternal is providing access to Sugar's internal date constructor (by default is simply new Date, this overrides it). When you use create to parse a string format, a new date is created, but it's properties are immediately overwritten by the parsed input, so it's effectively not doing anything.

Well the documentation under timezones makes this a bit ambiguous as it implies you can some how use newDateInternal to integrate with timezone support.
However, special options are included that allows Sugar to play nicely with other libraries designed for this purpose. Specifically, the newDateInternal option allows dates created internally by Sugar to be transformed to simulate being in a different timezone.

I don't really see how that is possible. Sugar has great parsing, but I don't see how to easily connect it to timezone support especially without exposing the date parsing parts result.

You're right about the docs, and admittedly this feature is nearly "hidden" in nature, and could be better thought out. It essentially began existence to allow Sugar to play nicely with timezone-js, which has pseudo date objects that conform to the native API. Sugar does not perform any type-checking on dates, so it will allow timezone-js dates to be used, but the problem became that a date would be manipulated from point of creation to the time it was returned, and there was no way to set the timezone in between, so this became the solution. For more context on this, see #342 as well as here.
So now I throw the question back to you? Are you actually trying to do something with timezones? More to the point (as it's a question I've been pondering of late), would Sugar handling timezones be something you're interested in?

Yes timezone support is important for me. We have multiple people around the world interacting with date based data and in our app we want all the data fixed to the same timezone instead of whatever happens to be that persons current local timezone. We used to use moment for this support, and I had to work around Sugar's lack of support by doing the date parse and then reading the parts back out using local interpretation and then using another library to take the [year, month, date, hour, minute, second] parts array to interpret it as the correct timezone.
Note this is still a bit tricky to use because the information about specificity is not exposed by the library. So when you receive back a date object you don't know if the original date string contained only time, an ambiguous date time with no timezone, or a full specified date string.


Disable chat "thumbs up" button by default

Roll out with an experiment

@roblourens looks like some unit tests failed


iOS / Full Multiplatform Support?

Getting official support for ios, and the other kotlin multiplatform targets would be great. It seems like people are forking the library to add this. It'd be great if the main project just did it.

Any news?

@DevSrSouza Any updates here? the fork mentioned above works fine ☝

I will talk with the fork owner and bring the code to here


doc: bump number of providers

It's 74 unique providers by my count from grepping the tree. Let's be conservative and say "over 60" at this point.

ha. nice. merging


Fix Windows build

Changes

Fix Windows build

Codecov Report

Merging #369 (9082a2c) into main (65ca045) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              main      #369    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           66        56    -10
  Lines         2666      1848   -818
  Branches       240        88   -152
==========================================
- Hits          2666      1848   -818

Impacted Files
Coverage Δ

packages/recheck/src/main.ts

packages/recheck/src/lib/native.ts

packages/recheck/src/lib/worker-pool.ts

packages/recheck/src/browser.ts

packages/recheck/src/lib/agent.ts

packages/recheck/src/lib/pure.ts

packages/recheck/src/lib/env.ts

...ges/eslint-plugin-redos/src/rules/no-vulnerable.ts

packages/recheck/src/lib/exe.ts

packages/recheck/src/lib/java.ts

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 65ca045...9082a2c. Read the comment docs.


How to test the model trained on FEMNIST dataset if the users in the testing set are disjoint from the uesers in the training set?

Hi,
I got one problem when i running your code on FEMNIST dataset.
I noted that you labeled the group ids of instances from their user ids. However, as descirbed in your paper, the users in the testing set are disjoint from the users in the training set. Thus, when evaluating the trained model,
python test.py --eval_on test --use_context 1 --binning 1  --ckpt_folders CKPT --n_test_dists 15

I got the following error report
Traceback (most recent call last):
  File "test.py", line 261, in <module>
    test_stats = test(args, eval_on='test')
  File "test.py", line 136, in test
    test_loader, eval_dists, split='test')
  File "/home/wuyx/FL-baseline/utils/eval_utils.py", line 215, in evaluate_mixtures
    accuracies_corners = eval_dists_fn(split, args, model, loader, corner_dists, n_samples_per_dist=n_samples_per_dist)
  File "/home/wuyx/FL-baseline/utils/eval_utils.py", line 144, in eval_dists_fn
    preds_all, labels_all = eval_dist(dist, model, loader, args, n_samples_per_dist)
  File "/home/wuyx/FL-baseline/utils/eval_utils.py", line 114, in eval_dist
    loader.sampler.set_sub_dist(dist)
  File "/home/wuyx/FL-baseline/datasets/utils/samplers.py", line 258, in set_sub_dist
    self.weights = torch.as_tensor(self._get_dist(dist), dtype=torch.double)
  File "/home/wuyx/FL-baseline/datasets/utils/samplers.py", line 275, in _get_dist
    p_over_examples = np.sum(self.group_ids_probs_pre * p_over_groups, axis=1)
ValueError: operands could not be broadcast together with shapes (13328,167) (741,)

where 741 is the number of users in the training set, 13328 and 167 are the number of instances and the number of users in the testing set respectively. I think that's because computing the distribution shift needs special operations when test groups are not sampled identically to the training groups, but i don't understand how to deal with it and i can't find this evaluation process in your repo either.
Looking foward to your answer~

i realize where's the problem now... i accidentally set binning=True. It works fine after i set binning=False.


Task: NuGet Custom wont't let you choose the VSTS Feed

With the NuGet V2 Task it is possible to choose the VSTS (or other) NuGet Feed which should be used (on the Command Restore and Push). This is not possible if i choose custom.
But currently we need this. We are installation a template package for docfx from our vsts nuget-server.

But sadly I can't select our VSTS feed, so the install failed.
Adding the PAT to global nuget.config only works on an on-premise build server. Not with Hosted Builds.
So, please enable adding VSTS feeds on custom Commands. Or add an Install Command ;)

This is also problematic on 'dotnet test' which does an implicit dotnet restore.

Any Update on this? Cant make a nuget install without an private buildserver where I can modify the Global NuGet.config.

Hello! I'm a PM over on the Azure Artifacts team. I wanted to drop in here and address some of these issues with the news that we're currently reevaluating the types of tasks we offer in Azure Pipelines, and looking to focus more on lighter-weight tasks that cover authentication and setup. In lieu of the task redesign, we're going to forego making changes to the current tasks (with a few exceptions). We hope the new tasks we spin up in the next quarter or so are easier and more helpful, be on the lookout!


Metro bundler cannot resolve fonts import

I decided to migrate from bunch of little repositories to one mono-repository.
And here comes the problem: in monorepo metro bundler resolves paths from expo-font in a strange way: it concats absolute path & server address. I wasn't meet that problem when projects were in separated repos
Here is example of strange path created by metro resolver:

Also intresting detail: that problem appears in only when app already fully loaded on device, not while bundling
All configs was created by @nrwl/expo, nothing is changed in them
I already tried to change metro.config, but meet a problem with the resolveRequest, which was null. Funny part is that, resolveRequest was described as a function at metro docs & interfaces
Here's how i import fonts:

Here's where fontConfig come to expo-font hook:

May you help me, please?
I can provide additional info, if u need it. I just don't know what can be useful

is fonts the only thing not loaded? are you using expo-font? if expo-font added to app's package.json? like "expo-font": "*"?

Fonts loaded with expo-font, expo-font added to package.json, only fonts couldn't be loaded

i tried with expo-font on my nx expo example project: https://github.com/xiongemi/nx-expo-poetry/pull/2/files. it works for me out of the box. I did not run into any metro issues.
it works for me for both ios and android simulators.
do you have the correct relative path to your font files?

i tried with expo-font on my nx expo example project: https://github.com/xiongemi/nx-expo-poetry/pull/2/files. it works for me out of the box. I did not run into any metro issues. it works for me for both ios and android simulators.
do you have the correct relative path to your font files?

@NikolaiChirkov  what version of @nrwl/expo are you using? also what does your metro.config.js look like. mine looks like this:
const { getDefaultConfig } = require('@expo/metro-config');
const { withNxMetro } = require('@nrwl/expo');

const defaultConfig = getDefaultConfig(__dirname);

module.exports = (async () => {
  defaultConfig.transformer.babelTransformerPath = require.resolve(
    'react-native-svg-transformer'
  );
  defaultConfig.resolver.assetExts = defaultConfig.resolver.assetExts.filter(
    (ext) => ext !== 'svg'
  );
  defaultConfig.resolver.sourceExts.push('svg');
  return withNxMetro(defaultConfig, {
    // Change this to true to see debugging info.
    // Useful if you have issues resolving modules
    debug: false,
    // all the file extensions used for imports other than 'ts', 'tsx', 'js', 'jsx'
    extensions: [],
    projectRoot: __dirname,
    watchFolders: []
  });
})();

do you have an example repo?

@NikolaiChirkov what version of @nrwl/expo are you using? also what does your metro.config.js look like. mine looks like this:
const { getDefaultConfig } = require('@expo/metro-config');
const { withNxMetro } = require('@nrwl/expo');

const defaultConfig = getDefaultConfig(__dirname);

module.exports = (async () => {
  defaultConfig.transformer.babelTransformerPath = require.resolve(
    'react-native-svg-transformer'
  );
  defaultConfig.resolver.assetExts = defaultConfig.resolver.assetExts.filter(
    (ext) => ext !== 'svg'
  );
  defaultConfig.resolver.sourceExts.push('svg');
  return withNxMetro(defaultConfig, {
    // Change this to true to see debugging info.
    // Useful if you have issues resolving modules
    debug: false,
    // all the file extensions used for imports other than 'ts', 'tsx', 'js', 'jsx'
    extensions: [],
    projectRoot: __dirname,
    watchFolders: []
  });
})();

do you have an example repo?

Version of Expo 14.3.0, exactly same metro.config (all configs was created by default & not changed, only exception - eslint config)

Link to the example app repo: https://github.com/NikolaiChirkov/nx-expo-example

Damn, seems like I solved problem

@xiongemi Thanks for help, if your repo's package.json helps a lot


Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[X] Full version (i.e. not a trial version)
[X] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
FanControl
Description
FanControl is a highly customizable fan controlling software for Windows.
There is no installation; unzip package and start FanControl.exe
Homepage
https://getfancontrol.com/
Download Link(s)
https://github.com/Rem0o/FanControl.Releases/blob/master/FanControl.zip?raw=true
https://github.com/Rem0o/FanControl.Releases/releases/tag/V138
Some Indication of Popularity/Repute
star: 7k
fork: 264
latest commit: Dec 5, 2022

It's already being added in, #9668. I did that.

Thanks Zliced13

@kennedy If you want to add it from my personal bucket, you can add it by running these commands:
scoop bucket add MyScoop 'https://github.com/Zliced13/MyScoop'

scoop install fan-control


WIP - Cyclefeatures

Merging code I have written offline to the main branch. These updates are to enable creation of beep feature matrix with diagnostic features calculated across cycles. Before this update, features are only calculated at the first two diagnostics and a difference of the two is reported.
Updates to intracell_analysis work towards using multiple rate data in the electrodes. Capability for fitting on discharge data has been added and is now the default mode.
Tests need to be written still. I am seeking some guidance on how to do this.
Some class names have changed, so I imagine there may be some changes to files that I did not capture here, such as files that are used to generate the pipeline data and call on the effected classes. I updated dependent files for using the build_feature_matrix notebook.
Issues fixed:
Addresses issue #567

Quoting @pasinger from #567 :

Currently, diagnostic features are calculated at the first and second diagnostic and the difference between the two is reported. This format is amenable to early prediction, but analysis of the battery health across lifetime would be better served by having the features reported across every cycle.

Some diagnostic information is available in the structured data in the diagnostic_summary field, but what's available there is not comprehensive.

I propose making a distinction between 1) "EarlyFeatures", which are a difference on the first two diagnostics (or between the first and some other diagnostic number specified in the featurizer hyperparameters) and 2) "CycleFeatures", which are the diagnostic features reported across all diagnostic cycles.

@pasinger
I think this is a great idea, thanks for the contribution!
The specific implementation can be improved upon. In fact, it might be worth replacing or overhauling the BEEPFeatureMatrix class to accommodate this kind of feature matrix (e.g., n_total_cycles_across_all_files x m_features rather than n_files x m_features). This is something I can do using your fork; this will be faster than going back/forth on changes in a PR. I'll include unit tests for this.
To do this though, I need two things from @pasinger

At least some expected outputs/features for some of the featurizers on known files. So for DiagnosticCycleFeatures, CyclingProtocol, and the intracell changes, I'll need the input file and the expected features (as matrix or vector)
Commit access to this PR branch. See how to do so here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

Hey @ardunn, sounds good. I should have updated the documentation - the BEEPCycleFeatureMatrix is already outputting a feature matrix of dimensions n_total_cycles_across_all_files x m_features. I am certainly open to reworking the class in other ways if there are benefits to it, though! I'll work on getting you permission now, then I'll send you a csv on slack of expected values for a particular cell. Does that work?

Hey @pasinger, so after looking at this in depth, these are the things we should do to bring this PR to completion.
1. Merging BEEPCycleFeatureMatrix into BEEPFeatureMatrix (@ardunn )
Seems like 99% of what BEEPFeatureMatrix does is in BEEPCycleFeatureMatrix. I think we can actually merge that functionality into the BEEPFeatureMatrix class such that it works with both paradigms of feature generation: (a) a feature vector for all cycles and (b) what you have implemented here, a feature vector per cycle.
I will do this and push changes to your branch in the coming days.
2. Intracell analysis needs much more documentation (@pasinger )
So I actually have no idea what is going on in either of the intracell analysis files. If possible, we should add more documentation to both the modules and the classes to explain (scientifically) what the generated features are. The function level documentation is good, but it is really difficult to determine from a birds eye view what is going on in those modules.
I will leave this one up to @pasinger
3. Clarify why we need V1 and V2 of intracell analyses/losses (@pasinger )
I'm not against keeping them both in, but what are the key differences between them? Something to maybe explain in documentation, or remove the v1 if v2 supercedes it.
I will also leave this up to @pasinger
4. Refactoring existing uses of featurizers (@ardunn )
There are quite a few mentions of the existing feature classes which were not renamed (e.g., in the cmd line interface). I can correct these
5. Write tests for new feature classes and improve documentation for existing feature classes (@ardunn )
Based on the files @pasinger sent and completing (1.), I'll be able to do this for the new feature classes

Done

[X] Split BEEPFeaturizer into two child ABCs: BEEPPerCycleFeaturizer, which returns a feature vector for every cycle, and BEEPAllCyclesFeaturizer, which returns a feature vector for every cycler file
[X] Refactor and reorganize all current featurizers into new featurizer submodules all_cycles and per_cycle, making it clear what classes can be used for what context
[X] BEEPFeatureMatrix now accepts both sets of all-cycle and sets of per-cycle featurizers and can successfully collate them into a single dataframes/matrices

Still to do (@ardunn)

[ ] Refactor other modules (e.g., cmd) which use featurizers so that tests will pass
[ ] Update cmd to allow for per-cycler featurizers to be run (or add this as github issue)
[ ] Add tests for new per-cycle featurizers
[ ] Add documentation for new and existing feature classes
[ ] Clean and refactor featurizer_helpers into their respective correct modules

Still to do (@pasinger )

[ ] Confirm where intracell feature classes should go (in per cycle or all cycles featurizers)? it seems like various classes in these modules fit into different paradigms. For example, IntracellCyclesv2 are per-cycle featurizers, and  IntracellFeaturesv2 are all-cycle (one-feature-vector-per-cycler-file) files based on the difference on the 1st vs. 2nd diag cycles
[ ] Confirm that CyclingProtocol class should indeed be a per-cycle featurizer considering it only utilizes a single cycle? Should this class be allowed for both per-cycle and all-cycles uses?
[ ] Clarify this where this get_hppc_resistance_cycle_features comes from?

# In HPPCResistanceVoltagePerCycle
       hppc_resistance_features = featurizer_helpers.get_hppc_resistance_cycle_features(
            self.datapath,
        )


Sample code for DJI Cloud > 1.10.0

The sample code has not been updated since April, however documentation shows there have been multiple DJI cloud updates since then.
As a result latest Dock 2 firmware is not compatible with the DJI Cloud SDK for Java we are currently running.  @DJIsean is this sample code no longer being updated or is there a new mechanism for receiving DJI SDK updates?

The demo has stopped updating, please make the necessary changes according to the updated protocol


Counter nanoseconds do not correspond to Vulkan pipeline statistics

The documentation and the code both state "nanoseconds" for various derived counters. This doesn't seem to be correct when compared to Vulkan's pipeline statistics. A sample profiling primitive assembly shows the following with GPA:
GPUTime = 2489.508102
ExecutionDuration = 2489.076102
ExecutionStart =<PHONE_NUMBER>.079865
ExecutionEnd =<PHONE_NUMBER>.608068
The exact same command buffer shows:
GPU Time = 3.411704 (ms)
GPU Start Time = 8822159.163976 (ms)
GPU End Time = 8822162.575679 (ms)
This is worked out by multiplying the timestamp query with the device's timestampPeriod and then converting nanoseconds to milliseconds.
Using start/end time as hint, the time unit that makes the most sense for GPA's values is possibly microseconds.
Am I somehow misinterpreting this?

Looks like there is some incorrect math in the code that converts Vulkan's timestampPeriod to the clock frequency.  See https://github.com/GPUOpen-Tools/GPA/blob/master/Src/GPUPerfAPIVk/VkUtils.cpp#L231
We believe this is the cause of the issue you're seeing.
Can you try modifying the code to the following:
        // Vulkan's timestampPeriod is expressed in nanoseconds per clock tick, convert to frequency in seconds
        float timestampPeriod = properties.limits.timestampPeriod;
        timestampFrequency    = static_cast<gpa_uint64>(1000000000.0f / (timestampPeriod));

We are currently testing this change, and if you agree it looks good, we will push this change to this repo.
Thanks,
Chris
cc: @amitprakash07

Thank you for looking into this so quickly. I just verified it against the tests that I have and it looks to line up the times that I'm seeing out of the Vulkan pipeline statistics.

Thanks for confirming and for reporting this issue.  I have pushed the fix.

Thank you!


consider adding build instructions

Some of us from cpp land are not very familiar with the Rust toolchain.

Good idea, added some in 7ae1e2ad5a1ff9519b33b5ff767b6a5c2b810c59. Let me know if it works for you.

Thanks, build instructions worked for me.


Examples if possible ?

Could you please provide examples with this lib . would be awesome !

bundle of thanks you with love !


The stop hook appears to be broken

While testing the flannel-docker charm I was trying to reset the environment (juju deployer -T) several times.  The stop hook resulted in an error. This error cause me to have to use --force to destroy the machine.
We should make sure that even the stop hook completes successfully.

This is actually affecting the Docker charm, not docker-flannel. Moving this over to docker here: https://github.com/chuckbutler/docker-charm/issues/18


Updating reference to v2 and v3 of Extension Bundles

This can be separated into two PRs - one for v2, one for v3 - if needed.

Releasing new Host versions.
V3 Release
V2 Release

PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made and CI is passing.

This PR is ready for review but NOT ready to be merged, pending an update from @amamounelsayed.


bugfix/DBC22-1359: Reduce redis replicas to 1 in UAT and PRD

To temporarily resolve issues with Huey jobs getting stuck

https://github.com/bcgov/DriveBC.ca/pull/218/files this might be a better solution?
I assume huey would always select the same db if we just specify it.

@ray-oxd Since redis pods can come and go, would it still work if redis pod 1 got terminated and then red pod 2 took over the active load?

Closed https://github.com/bcgov/DriveBC.ca/pull/218/files after some research. The changes I proposed did nothing, redis-py uses db=0 by default, and that setting only specified which db within a redis instance, not which redis instance to use.
I'm going to approve this since a single redis pod is likely all we're going to need, but we could load-test and learn more about scaling/load balancing multiple redis instances.