Arangodb not getting deployed on AWS EKS cluster though worked on local K8s cluster

Hi,
I am trying to deploy Arangodb on aws EKS cluster by following instructions on this documentation : https://arangodb.github.io/kube-arangodb/docs/using-the-operator. I was unsuccessful to deploy it on aws EKS cluster. However, deployment happened successfully on local K8s cluster.
Local K8s cluster : K3S version 1.28.4
ArangoDeployment mode : Cluster
Kube-arangodb manifest version : 1.2.37 as well as 1.2.36
Arangodb version : 3.10.8
AWS EKS Cluster version : 1.26
I was getting startup probe failure error with connection refused when cluster coordinator pods were getting up. Attaching the snapshots :

K8s services created while deploying the setup(attaching its snapshot)

Note : I had tried with helm charts as well as K8s manifest files. Both resulted in the same error.
Please advise.

Hi,
currently supported ArangoDB versions include: 3.10.x, 3.11.x ; Somehow the versions you mention completely won't match this scheme?

@dothebart I was actually referring to kube-arangodb manifest version : https://github.com/arangodb/kube-arangodb/releases/tag/1.2.37 Let me edit.
Which uses 3.10.x for arangodb image.

Hello!
I do not think it is related to ArangoDB itself.
An issue like this happens when the ArangoDB Coordinator can't connect to the Agents/DBServers. Often, this issue is caused by DNS setup.
To check the issue - can you share logs from the Operator and Coordinator?
Best Regards,
Adam JAnikowski.

@ajanikow
One of the error was
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/arangodb_operator": stat /usr/bin/arangodb_operator: no such file or directory: unknown
Another error was :
tcp <IP_ADDRESS>:8529: connect: connection refused

@piyushkumar13 First error is strange, it does not come from crdn pods. You probably have used arangodb image as the image for Operator installation via helm.
Second one is valid error - we just need Operator and CRDN logs to continue (20 last lines)

The issue is resolved. Seems like it was the access issue at my end. I had limited access on my EKS cluster, which resulted into few of the CRDs/deployments not working properly.

Great, thanks for letting us know.


Virus

☣B̷U̷G̷ H̷O̷L̷E̷S̷S̷ N̷O̷ A̷N̷T̷I̷ M̷A̷D̷E̷T̷"☣
📵📵ࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣩࣻࣳࣳࣳࣳࣻࣻࣳࣳࣳࣳࣻࣻࣳࣳࣳࣳࣻࣻࣳࣳࣳࣳࣻ📵⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢⃢
Pada tanggal Rab, 14 Des 2022 6.19 PM, Lefinkenv1 @.***>
menulis:

Hi
Le mer. 14 déc. 2022 à 08:12, Kadamviswa @.***> a
écrit :

—
Reply to this email directly, view it on GitHub
https://github.com/noob-hackers/infect/issues/53, or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A4FIGTVLXIDGTFBWVEPYW3LWNFXMTANCNFSM6AAAAAAS6DFBNM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/noob-hackers/infect/issues/53#issuecomment-1351025831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2HU6X3EYE546Z2B6BRHGS3WNGUMBANCNFSM6AAAAAAS6DFBNM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Bug: nodeos logging strange behavior

There is very strange behavior  when using extended logging (using logging.json).
What is observed:
"enabled - bool value to enable/disable the appender" - does not seem to work at all, nor in appenders, nor in loggers section.
For example:

if additional loggers are specified, nodeos - pushes messages, even if they are enabled:false
stdout stream seems not to work at all, if you configure it as an appender and specify in logger, messages are pushed only to stderr stream
If you configure a gelf-type appender and do not enable it - nodeos pushes a message in stderr like opened GELF socket to endpoint host:port and  indeed makes connection and pushes messages to the receiver specified
if you specify level:off and enabled:true - nodeos pushes some log lines in stderr....it is a bit confusing, maybe it would be better to drop level: off and keep enabled value as in (refer syslog rfc5424), though making it work

Tested on v2.0.1 tag, built from sources, Ubuntu 18.04.2 LTS.

Despite being in the logging.json file, those knobs have not been implemented yet. And we are currently reviewing the different avenues to approach modifying the logging facility.

We are closing this issue. We are aware of this and other issues in fc::logger and will create a mega-issue linking this and the other logging-related issues soon to address all problems in one effort.


Plain English overview and digest, on homepage

The homepage of Metriq could give a (plain English) overview and digest of key metrics and the state-of-the-art across the field of quantum technology.

(See https://metriq.info/SOTA)


Remove async from backend data retrieval

use request.head instead

Cannot be done, head requests are not supported by API


[AMORO-2993] Enrich optimizing metrics

Why are the changes needed?

Close #2993.
Brief change log

As mentioned in the issue

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Codecov Report
Attention: Patch coverage is 75.00000% with 20 lines in your changes missing coverage. Please review.

Project coverage is 32.89%. Comparing base (08183b7) to head (eef6de6).
Report is 15 commits behind head on master.

Files
Patch %
Lines

...che/amoro/server/table/TableOptimizingMetrics.java
75.86%
13 Missing and 1 partial :warning:

...va/org/apache/amoro/server/table/TableRuntime.java
72.72%
4 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2994      +/-   ##
============================================
+ Coverage     32.85%   32.89%   +0.03%
+ Complexity     3825     3824       -1
============================================
  Files           557      557
  Lines         46227    46305      +78
  Branches       6107     6120      +13
============================================
+ Hits          15189    15233      +44
- Misses        29843    29872      +29
- Partials       1195     1200       +5

Flag
Coverage Δ

core
32.89% <75.00%> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Hi @baiyangtx, @zhoujinsong update code and add document, PTAL

The last refresh snapshot should not be any of optimizing or maintainenace snapshot committed by amoro. So I suggest merging pr #3058 before pushing it forward

@XBaith Some conflicts need to be fixed.

@zhoujinsong @baiyangtx I exclude the snapsthos produced by Amoro, PTAL and feel free to merge this PR


I miss this project so much

Just wanted to let you know <3

Me too <3 hope it will  be back one day.

Duplicated of https://github.com/dfm/osrc/issues/165


Require pillow>=10.0.0, catch drise failure due to low mask_res or num_masks

Description
In telemetry, we found that two exceptions were thrown. Firstly, drise throws ValueError when num_masks or mask_res are too low. This is caught by the try-except block and the _get_fail_str method subsequently runs into an AttributeError because it doesn't have a textsize method. This is due to a breaking change in v10.0.0 of Pillow.
This PR therefore

requires Pillow>=10.0.0 explicitly so that dependencies can't later accidentally downgrade us. We are already using Pillow==10.0.0 in our environments, so this isn't necessarily a change, just insurance.
uses the new method textbbox instead of textsize from Pillow which avoids the second exception
catches the ValueError from drise and provides a corresponding user error with informative message to the user.

A simple way to reproduce this is to take our dpv2 test cases and run test_object_detection_pipeline_rai.yaml with num_masks=1 and max_evals=10 (to make it faster).
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #2181 (7b6576f) into main (8898e82) will decrease coverage by 5.08%.
Report is 3 commits behind head on main.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2181      +/-   ##
==========================================
- Coverage   78.34%   73.27%   -5.08%
==========================================
  Files          26       14      -12
  Lines        2152     1216     -936
==========================================
- Hits         1686      891     -795
+ Misses        466      325     -141

Flag
Coverage Δ

unittests
73.27% <0.00%> (-5.08%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

...responsibleai_vision/managers/explainer_manager.py
62.97% <0.00%> (-1.32%)
:arrow_down:

... and 12 files with indirect coverage changes


Typo

[Enter feedback here]
Typo: to integrate your CI/CI process with most Azure services.

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

ID: 2c9fbc1a-8e3f-31c9-64c2-5a21cd9c5aec
Version Independent ID: 692a9a5a-e49a-1295-6bd9-8a82410adaf0
Content: Deploy to Azure index to content - Azure Pipelines
Content Source: docs/pipelines/overview-azure.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

@alex-cloud Thanks! Fix will go live soon.


Split compress into compress and left-justify

The compress arguments both removes vertical space between comments and left-justifies the comments. Separate these two functionalities with separate arguments which can be combined if the user so wishes.
For example, here's what the arguments should produce with this given input:
    // Comment 1

    // Comment 2

--compress
    // Comment 1
    // Comment 2

--left-justify
// Comment 1

// Comment 2

Implemented by 153f092.


feature request: port v0.7.0 feature to 1.21.1

Describe the Request
The new update
Screenshots
No response
Modloader Type
Neoforge
Modloader Version
1.21.1
Additional Context
No response

Oh,if that was the problem,don't worry! I can wait👍

Thanks for your understanding 💜

As the Winter Drop already be here, I don't have the time to backport to 1.21.1 and before, I will focus on the next minor bump (1.22) to change how I handle multiple version of minecraft with mod update !
I will close this issue as Not planned
Thanks for your understanding 💜

ig,at this point just warn people that latest 1.21.1 version is broken


Confusing Documentation \ Changelog

Sorry to open an issue \ question for this.
In the Readme.md, it says:
"Note that observer automatically applies React.memo to any component you pass to it."
I see that this was added in https://github.com/mobxjs/mobx-react/commit/516a21ebd4656a29e2a98decd8307c7ad0b64d19 (Post v6)
However, in the changelog, it says:
"Using PureComponent is now recommended."
https://github.com/mobxjs/mobx-react/blob/master/CHANGELOG.md
So should we be using the following code? ie: Going through our current observed components, and making them Pure?
@observer
class SomeClass extends PureComponent

You are right, it is confusing :) The React.memo is relevant for a functional components only. For class components, you should indeed use PureComponent (which is equivalent).
PR welcome if you can write it in a more understandable form.


Roomba not responding to Plugin - Freezing Homebridge

Hello, it's been a week since I noticed that the rumba accessory is unresponsive, resulting in a homebridge freeze.  everything is fine after rebooting homebridge but about 24 hours after the problem comes back.  someone can help me ?  Thank you

probably same issue as issue 66: configure without autoRefreshEnabled nor keepAliveEnabled, basically an on off switch.   I have been using mine that way for months and although not much features, HB is stable.

It's ok. Thanks 👍🏼


this form shows too tall buttons, 2x taller than usual buttons in UI

Xubuntu 20
Also - ugly borders around top info-text.

Those buttons do seem overly large, but I do not understand the comment about the border or whether it is ng or theme dependent. Attaching screenshots of ng window in first, Enlightenment, then XFCE, both with a Vertex dark application theme.

I use a raised panel when I want to user to see it, I am an engineer, not an artist so functionality is more important to me than "first look appearance"


Updated Dutch translation

🙂

Thanks Vistaus, yes, it was a lot of work, sorry I let it go for so long.  I don't expect much UI changes from now on, certainly nothing to the extent we see here.
Thanks for that translation, I have merged your change, will release in a few days at the most.
Vistaus, I plan to setup a github Translators team for tomboy-ng, don't be surprised if you see your (user)name pop up. That will add you to the Tomboy team as well. The rest of Tomboy is, effectively inactive but you might get tomboy-ng bug reports, if so, easily blocked or withdraw if you don't want to work that way. It will be just used to let people know when a new version is coming out so, very low traffic once setup.
Davo

Thanks Vistaus, yes, it was a lot of work, sorry I let it go for so long.

No problem! I love translating, so it was fun for me! 🙂

Vistaus, I plan to setup a github Translators team for tomboy-ng, don't be surprised if you see your (user)name pop up. That will add you to the Tomboy team as well. The rest of Tomboy is, effectively inactive but you might get tomboy-ng bug reports, if so, easily blocked or withdraw if you don't want to work that way. It will be just used to let people know when a new version is coming out so, very low traffic once setup.

Thanks for letting me know! 🙂


[mesheryctl] Switching Context Not Aborted

See mesheryctl Command Tracker for current status of commands.
Current Behavior

While switching context, mesheryctl prompted that it would delete my current deployment so I refused to switch.
It prompted, its aborted but still switched the context and my deployment
Desired Behavior

This misbehavior should be fixed and mesheryctl should abort if user gives an input of n.
Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Meshery Server Version: stable-v
Meshery Client Version: stable-v
Platform: Docker Kubernetes

Contributor Guides and Handbook

📚 mesheryctl Contributing Guide
📺 Beginner's guide to contributing to Meshery and mesheryctl
⌨ mesheryctl Command Tracker
⌨ Meshery CLI Commands and Documentation
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Can you assign this issue to me?

// @suhail34 @zakisk

Can you assign this issue to me?

Sure 👍
Have you been able to built and run mesheryctl locally?

yes, I have @theBeginner86


Verify that data is being parsed correctly and ending up BigQuery

DISCO has been running in sandbox for a month or more now, but I have not verified that the parser is correcting parsing the output and that data is still ending up in BigQuery.
Verify this, then push the deployment to staging and production and retired the "utilization" experiment.

I have spot checked DISCOv2 data in BigQuery and have verified that it is getting parsed correctly.
I have just submitted a PR to get DISCOv2 into staging. Once in staging we can compare production and staging data to be sure they line up as expected. Production and staging collect from the same switch, so this will allow us to directly compare what is collected by the utilization experiment and DISCOv2.

This is now done. Since staging scrapes the same switches as production we were able to compare the utilization experiment data in production with the disco data in staging for the same switch.


[view] Prisma references wrong entry in view

Bug description
I'm aware that views in Prisma are still a preview feature. However, I must report this issue because it gives me a lot of trouble.
Right now, if you want to include nested objects from a view, Prisma might return an entry, that is incorrectly referenced.
When I look at the entries in Prisma Studio, it's clear that some issue exists during joins. See attached screenshot. In the view we have one asset, but when opening the referenced entry in Asset table, the reference is wrong.
Note: I had the same issue with portfolio mappings, and I managed to fix them by adding @unique identifier to portfolioId in the view definition. However, that approach didn't work on assets. Am I doing something wrong or is this really a bug? 🤔

How to reproduce

Generate DB based on the provided models
Run this script to create the view
Run prisma pull to fetch the view into schema.prisma
Modify the view to match the one I pasted in the issue
Create some dummy data via Prisma Studio
Try to execute my TS snippet

 create or replace
view
  "AssetTransactionView" as
select
	JOINED.id,
	JOINED.symbol,
	JOINED.name,
	SUM(
    case
      when JOINED."transactionType" = 'BUY' then JOINED.amount
      else 0
    end
  ) - SUM(
    case
      when JOINED."transactionType" = 'SELL' then JOINED.amount
      when JOINED."transactionType" = 'CLOSE' then JOINED.amount
      else 0
    end
  ) as "transactionAmount",
	SUM(
    case
      when JOINED."transactionType" = 'BUY'
      or JOINED."transactionType" = 'CLOSE' then JOINED.quantity
      else 0
    end
  ) - SUM(
    case
      when JOINED."transactionType" = 'SELL' then JOINED.quantity
      else 0
    end
  ) as "transactionQuantity",
	SUM(JOINED.dust) as "totalDust"
from
	(
	select
		a.id,
		a.name,
		a.symbol,
		at."transactionType",
		at.amount,
		at.quantity,
		at.dust
	from
		"Asset" a
	left join "AssetTransaction" at on
		a.id = at."assetId"
	where
		at."isValid" = true
	group by
		a.id,
		a.name,
		a.symbol,
		at."transactionType",
		at.amount,
		at.quantity,
		at.dust
  ) as JOINED
group by
	JOINED.id,
	JOINED.name,
	JOINED.symbol;

Expected behavior
The asset prop in portfolioAssetTransactionView entries should have the same id as assetId
Prisma information
model Portfolio {
  id                                String             @id @default(cuid())
  name                              String
  assetTransactions                 AssetTransaction[]
  value                             PortfolioValue[]
  assets                            Asset[]            @relation("AssetToPortfolio")

  portfolioAssetTransactions        PortfolioAssetTransactionView[]
}

model Asset {
  id                String             @id @default(cuid())
  symbol            String
  name              String             @unique
  assetTransactions AssetTransaction[]
  portfolio         Portfolio[]        @relation("AssetToPortfolio")
  portfolioAssetTransactionView PortfolioAssetTransactionView[]
}

model AssetTransaction {
  id              String          @id @default(cuid())
  assetId         String
  quantity        Decimal
  amount          Decimal
  weight          Decimal?
  transactionType TransactionType
  portfolioId     String?
  userId          String
  createdAt       DateTime        @default(now())
  updatedAt       DateTime        @updatedAt
  dust            Decimal         @default(0)
  isValid         Boolean         @default(true)
  price           Decimal
  asset           Asset           @relation(fields: [assetId], references: [id], onDelete: Cascade)
  portfolio       Portfolio?      @relation(fields: [portfolioId], references: [id], onDelete: Cascade)
}

view PortfolioAssetTransactionView {
  portfolioId     String   @unique
  name            String
  assetId         String
  assetName       String
  symbol          String
  startingCapital Decimal
  totalAmount     Decimal   @db.Decimal
  totalQuantity   Decimal   @db.Decimal
  totalDust       Decimal?  @db.Decimal
  portfolio       Portfolio @relation(fields: [portfolioId], references: [id])
  asset           Asset     @relation(fields: [assetId], references: [id])

  @@unique([portfolioId, assetId])
}

enum TransactionType {
  BUY
  SELL
  CLOSE
}

  const portfolioAssetTransactions =
    await prisma.portfolioAssetTransactionView.findMany({
      where: {
        portfolioId,
      },
      include: {
        asset: true,
      },
    });

Environment & setup
OS: macOS
Database: PostgreSQL
Node.js version: v19.1.0
Prisma Version
prisma                  : 5.1.1
@prisma/client          : 5.1.1
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 6a3747c37ff169c90047725a05a6ef02e32ac97e (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 6a3747c37ff169c90047725a05a6ef02e32ac97e (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.1.1-1.6a3747c37ff169c90047725a05a6ef02e32ac97e
Default Engines Hash    : 6a3747c37ff169c90047725a05a6ef02e32ac97e
Studio                  : 0.492.0
Preview Features        : views

Relations in views currently are technically supported, whatever happens there is coincidence and can totally be wrong - as it seems you are reporting.
Do I understand correctly that the view shows/contains the correct assetId in its data, but when clicking (or returning) the asset relation to the Asset model (which is defined via the assetId relation scalar) it is showing/returning the wrong Asset entry?
(The id in Studio is unfortunately cut in a way that I can not fully compare the values.)
To double check: What exactly does running that findMany return and how is it unexpected?

I've managed to fix this issue by simply placing the asset before portfolio and removing @unique
view PortfolioAssetTransactionView {
  portfolioId     String
  name            String
  assetId         String
  assetName       String
  symbol          String
  startingCapital Decimal
  totalAmount     Decimal   @db.Decimal
  totalQuantity   Decimal   @db.Decimal
  totalDust       Decimal?  @db.Decimal
  asset           Asset     @relation(fields: [assetId], references: [id])
  portfolio       Portfolio @relation(fields: [portfolioId], references: [id])

  @@unique([portfolioId, assetId])
}

You understood correctly. The result of findMany returned entries that have correct values. But the referenced  asset was wrong. For example, from the screenshot you can see that I highlighted the row that has symbol=BTC , while when opening the asset entry I get ORB asset.
Please note that I managed to fix this issue by removing @unique from portfolioId .
Now I need to check if the referenced portfolios are correct

Thanks for the update.
Now that you explained it again, I can also see that obviously the assetId and referenced id do not match:

We'll have to look into this when we implement relations for views. This bug is a good starting point to understand what is going wrong there. Thanks!
And great you found a workaround for now.

You're welcome. Since I'm debugging my project as we "speak". I'll update this issue with more information. Hopefully later during the day

@janpio
After a couple of hours of debugging, I can tell you that changing the position of entities in the view did make a difference.
Now, I'm not sure what was the reason for that. I haven't looked at the Prisma code, but could it be that you recreate views, based on the position of referenced models? 🤔
Also, another thing that I've found is that filtering in views, based on a nested property doesn't work as expected.
Here's a code snippet that should return all portfolios with transactions given a certain userId:
const publicPortfoliosWithTransactions =
    await prisma.portfolioAssetTransactionView.findMany({
      where: {
        totalAmount: {
          gt: 0,
        },
        totalQuantity: {
          gt: 0,
        },
        portfolio: {
          deletedAt: null,
          userId,
        }
      },
      select: {
        assetName: true,
        portfolioId: true,
        totalAmount: true,
        totalQuantity: true,
        portfolio: {
          include: {
            user: {
              select: {
                name: true,
                email: true,
              },
            },
          },
        },
      },
    });

However, when executed, I get all entries from PortfolioAssetTransactionView and because of that, I need to filter them manually. This really sux, especially because this one isn't obvious at first. As I said in the beginning, I'm aware that this is still a preview feature, but it would be really good if this could be resolved soon 🙏
 // 2. Retrieve all public portfolios that have transactions > 0
  const publicPortfoliosWithTransactions =
    await prisma.portfolioAssetTransactionView.findMany({
      where: {
        totalAmount: {
          gt: 0,
        },
        totalQuantity: {
          gt: 0,
        },
      },
      select: {
        assetName: true,
        portfolioId: true,
        totalAmount: true,
        totalQuantity: true,
        portfolio: {
          include: {
            user: {
              select: {
                name: true,
                email: true,
              },
            },
          },
        },
      },
    });

  // For some reason Prisma filters are not working for portfolio
  // That's why we have to filter manually
  const result = await calculatePortfolioMetrics(
    publicPortfoliosWithTransactions.filter(({ portfolio: p }) => {
      return (
        p.userId === userId &&
        p.isPublic &&
        p.deletedAt === null &&
        p.isAuthorVisible
      );
    })
  );

Can you split out the "filter does not work as expected" bit into its own issue?
That should work correctly already, so is really surprising.
With a separate issue, we can reproduce this by its own and hopefully fix it sooner.
Regarding your observation that the order of things makes a difference... yeah - that also surprises me. I have no idea how that could be relevant. But we'll figure it out.

Thank you. I wish you the best of luck.
Of course. Here's the link: https://github.com/prisma/prisma/issues/20577


Idea of using Serf as another transport config

Right now we have SSH hardcoded in.  Enough said.
https://www.serfdom.io/

We will have to transfer the serf binary to each remote host.  This will require using SSH first.

Check out how blender uses serf.  Ideas: assume serf is already on the system and have it download all the modules.  Still gotta find a way to collect the task results though


OpsGenie Notifier, fixes and additions:

OpsGenie notifier confused the description and message fields
Also added the notes field.
Added verbose description template (taken from pushover

:+1: otherwise.


refactor: directly config logrus' default Logger rather than create a new one

Signed-off-by: Allen Sun<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
In the component of dfget, the Logger is regarded one field of the configuration, and it will be transferred to other places where logger recording is needed.
Since when dfget process is started to the status of its exit, the log configuration will not change, then I think we can directly use the default logrus.Logger in pkg logrus. And we only need to configure the default logger's LogLevel, Formatter and Output via:

logrus.SetOutput()
logrus.SetLevel()
logrus.SetFormatter()

Ⅱ. Does this pull request fix one issue?

no, just refactoring
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
no
Ⅳ. Describe how to verify it
no
Ⅴ. Special notes for reviews
none

Codecov Report

Merging #372 into master will decrease coverage by 3.02%.
The diff coverage is 23%.

@@            Coverage Diff             @@
##           master     #372      +/-   ##
==========================================
- Coverage   57.54%   54.52%   -3.03%
==========================================
  Files          43       44       +1
  Lines        2127     2133       +6
==========================================
- Hits         1224     1163      -61
- Misses        838      909      +71
+ Partials       65       61       -4

Impacted Files
Coverage Δ

dfget/core/helper/test_helper.go
0% <ø> (ø)
:arrow_up:

dfget/config/config.go
84.84% <ø> (-0.31%)
:arrow_down:

cmd/dfget/app/log.go
0% <0%> (ø)

dfget/util/log.go
0% <0%> (-85.72%)
:arrow_down:

...core/downloader/back_downloader/back_downloader.go
0% <0%> (ø)
:arrow_up:

cmd/dfget/app/server.go
65.62% <0%> (+11.77%)
:arrow_up:

dfget/core/uploader/uploader_util.go
65.45% <0%> (ø)
:arrow_up:

dfget/core/regist/register.go
97.72% <100%> (ø)
:arrow_up:

dfget/core/downloader/downloader.go
100% <100%> (ø)
:arrow_up:

dfget/core/uploader/uploader.go
27.7% <22.72%> (+1.12%)
:arrow_up:

... and 5 more

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 7be3346...e9e3285. Read the comment docs.

It's better to retain the test file: dfget/util/log_test.go.

I have recalled the deleted file. Thanks for your review. @lowzj

LGTM


Update Docs. Very less information or wrong information

First of all, I see that the App is exposed at port 8080 in my computer. Is it because it recognizes the environment as a dev environment ? But I didn't set any environment of that sort, so I think the App is exposed at port 8080 by default and not 80 as mentioned in the Docs

Developers should be informed to apply for SES limit increase in the Docs. I learned this from a YouTube tutorial when checking about SES.

Developers should also be informed about how to setup and get their Goolgle OAuth credentials by creating a project in the Google Developers Console and how they should set authorized origins and redirect (or callback) URLs

Developers should be informed to create a User in Amazon IAM and that the user should be given both programmatic and console access like below :

so that it creates an auto-generated password too for the user, which has to be set in the .env file. Or else it creates a lot of issues! And password isn't optional, from what I see in the application

The links to install docker is all good. But I see that there are some issues with running the command docker-compose up and works only if we use sudo docker-compose up or else we have to create something called Docker group it seems, to get rid of the sudo . Check this :
Stack Overflow Issue

@AndrewGHC I can make PRs actually. But do tell about refinements and I will work on this.
I also plan to create a simple tutorial for the whole setup in Medium

@karuppiah7890 Thanks again for this feedback, you've identified some key issues with the Readme that I've now fixed.

Thanks for spotting this, I've now corrected the port.
This information is now included.
This information is now included.
This process is currently described in the tutorial video - but it is a good point that we may need to write this process down.
Root permissions shouldn't be necessary to run Docker, the issue in the SO link has multiple competing solutions, suggesting that this may be an issue with specific version of Docker.

Thanks again for your feedback.

@AndrewGHC For 4, the procedure isn't explained properly in the video. @QuincyLarson only asks us to create a pair of Access Key and Secret Access Key, see here YouTube Demo 1m:22s. He doesn't tick the AWS Management Console Access. The demo still works. I guess it wasn't a problem then. But now, the .env file instructions mention that AWS Access keys are encrypted with the user specific password. So, if no password is created for the user, I don't know if Amazon encrypts or what happens, but the application however throws an error about no passwords in .env, in the console

@AndrewGHC  And about 5, well, I have the latest version of Docker. And I am still getting issues. Are you sure there is no procedure of even adding the user to the docker group ? Because I was just trying that, and it doesn't seem to work out. Searching what is the issue


rework getters.rs

Minor refactors
Introducing ShortestPathIterator for iterating on the components of a shortest path.
Test it

There, I rebased it and updated the binary, does it work ?


Is it possible to change the name of the build in Build-Parallel?

I am using the following script to run builds in parallel (simplified):
Build-Parallel @(
    @{ File="build.ps1"; name="foo" }
    @{ File="build.ps1"; name="bar" }
)

the log output is
Start (1/2) build.ps1
Start (2/2) build.ps1
...

is it possible to have the log like
Start (1/2) build.ps1 "foo"
Start (2/2) build.ps1 "bar"
...

This is not possible as such. The script has no customization like this.
I am not sure about "name" for such header info. For IB it is just a particular
parameter name and IB does not know it. Other authors may prefer "Title" or
"BuildName", etc.
But IB knows about "File" (and shows it) and "Task". In theory IB may also show
task names in headers in addition to files.
Then, for example, you may add/have tasks foo and bar to your scripts.
Then call:
Build-Parallel @(
    @{ File="build.ps1"; Task="foo" }
    @{ File="build.ps1"; Task="bar" }
    @{ File="build.ps1"; Task="task1", "task2" }
)

outputs something like:
Start (1/3) build.ps1 foo
Start (2/3) build.ps1 bar
Start (3/3) build.ps1 task1, task2
...

This kind of change is possible and probably useful out of box.
What do you think?

Unfortunately, your version won't help me. In my case all parallels have the same file and task, but different parameters.
Thank you for the clarification.

You can can create artificial / bespoke  tasks designed for exactly this purpose.

Sorry, closed by mistake. What about showing all parameters then?

We can add the parameter ShowParameter ([string[]] for one or more).
Example:
Build-Parallel -ShowParameter Name @(
    @{ File="build.ps1"; Name="foo" }
    @{ File="build.ps1"; Name="bar" }
)

outputs something like:
Start (1/3) build.ps1 Name: foo
Start (2/3) build.ps1 Name: bar
...

I think this solves your issue.
And it is "secure", it's up to an author to use or not.

done
https://github.com/nightroman/Invoke-Build/blob/master/Release-Notes.md#v587

This is exactly what i'm looking for.
Many thanks!


New sample: Export vector tiles

Description
PR to add a new Kotlin sample "Export vector tiles" in Edit and Manage Data category.
Links and Data
Sample Epic: runtime/common-samples/issues/2886
What To Review

Review the code to make sure it is easy to follow like other samples on Android
README.md and README.metadata.json files

How to Test
Run the sample on the sample viewer or the repo.

I’m getting an error message running the export vector tiles job. The error is:

Null pointer: extent must be provided.

I’m not sure why I’m getting this error since I can see the area of interest is set, could I get some help with this? The job and loads run fine if I do not use an ItemResourceCachePath in exportVectorTilesTask.exportVectorTiles()

Changing basemap to use ARCGIS_NAVIGATION_NIGHT which can export vector tiles

The ItemResourceCache  folder path exists prior to calling Job.start() but sometimes gets deleted on Job.start() which then causes the getCause() internal CoreRequest error. Will investigate more into this

Added a check to only start a job when the previous job has been completed asynchronously.


nixos: avoid side effects to fileSystems if possible

This is a good idea in itself.
Additionally, it avoids issues if users want to use mkDefault in their fileSystems config and have no persistent directories.

@talyz Hi, I have fixed the formatting.  Please have look.


FIRMessagingTokenFetchOperation went isFinished=YES without being started by the queue it is in

Description
Title is the error I get in the console when I try to log in in my app. I do not have the steps to replicate this 100%, but the most reliable way I have been able to replicate this is when updating my app from an older build (e.g. from TestFlight) to a newer one.
Reproducing the issue

//  This function causes a crash when FirebaseApp.app()?.delete is called.
private func setupFirebase(completion: @escaping () -> Void) {
    let filePath = /* dynamic file path based on scheme */
    let fileopts = FirebaseOptions(contentsOfFile: filePath)!

    if FirebaseApp.app() != nil {
        FirebaseApp.app()?.delete { _ in
            DispatchQueue.main.async {
                FirebaseApp.configure(options: fileopts)
                completion()
            }
        }
    } else {
        FirebaseApp.configure(options: fileopts)
        completion()
    }
}

Firebase SDK Version
8.15.0
Xcode Version
13.2.1
Installation Method
Swift Package Manager
Firebase Product(s)
Messaging
Targeted Platforms
iOS
Relevant Log Output
2022-11-10 20:41:43.007368+0530 FL3XX Crew[26026:6210149] 8.15.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2022-11-10 20:41:43.007590+0530 FL3XX Crew[26026:6210149] 8.15.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2022-11-10 20:41:43.010022+0530 FL3XX Crew[26026:6210149] 8.15.0 - [Firebase/Messaging][I-FCM040000] Register request to https://fcmtoken.googleapis.com/register content: X-osv=15.1&device=5488829666173685770&X-scope=*&plat=2&app=com.fl3xx.FL3XX-Crew&app_ver=2.10.18&X-cliv=fiid-8.15.0&sender=254709422554&X-subtype=254709422554&appid=flDI2kpMJUPir9FrFgYHGb&apns_token=s_c98ea63054cc629fbd159eb8802e5edbdb6e377e90d83c96c021757aad9ae27d&gmp_app_id=1:254709422554:ios:fcb5d2224a9896447108e3
2022-11-10 20:41:43.035170+0530 FL3XX Crew[26026:6211053] 8.15.0 - [Firebase/Messaging][I-FCM034001] Token fetch successful, token: flDI2kpMJUPir9FrFgYHGb:APA91bEFTI9wwnDypNjqG6gXYKC6kq7mQcKy1QVtRc1rhr2lvA0Oj3d2biN9AQbXzbykXtj1mnd1c-IBKDwE5dsDUOTYV8PwlRhbGm68yXWayBHwQx5ZlBkggVjkFPes0cps2Wb392sW, authorizedEntity:<PHONE_NUMBER>54, scope:*
2022-11-10 20:41:45.933263+0530 FL3XX Crew[26026:6211053] 8.15.0 - [Firebase/Crashlytics][I-CLS000000] Cannot instantiate more than one instance of Crashlytics.
2022-11-10 20:41:45.934792+0530 FL3XX Crew[26026:6211053] 8.15.0 - [Firebase/Crashlytics][I-CLS000000] Cannot instantiate more than one instance of Crashlytics.
2022-11-10 20:41:45.936848+0530 FL3XX Crew[26026:6211053] 8.15.0 - [Firebase/Core][I-COR000006] Deleting app named __FIRAPP_DEFAULT
2022-11-10 20:41:45.937006+0530 FL3XX Crew[26026:6211053] 8.15.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add `FirebaseApp.configure()` to your application initialization. This can be done in in the App Delegate's application(_:didFinishLaunchingWithOptions:)` (or the `@main` struct's initializer in SwiftUI). Read more: https://goo.gl/ctyzm8.
2022-11-10 20:41:45.989793+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x123d9e110 went isFinished=YES without being started by the queue it is in
2022-11-10 20:41:45.989838+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x1258b32a0 went isFinished=YES without being started by the queue it is in
2022-11-10 20:41:45.989867+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x125878f20 went isFinished=YES without being started by the queue it is in
2022-11-10 20:41:45.989949+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x112556e20 went isFinished=YES without being started by the queue it is in
2022-11-10 20:41:45.990113+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x122049a50 went isFinished=YES without being started by the queue it is in
2022-11-10 20:41:45.990213+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x1259e7c20 went isFinished=YES without being started by the queue it is in
2022-11-10 20:41:45.992591+0530 FL3XX Crew[26026:6209977] *** FIRMessagingTokenFetchOperation 0x1259f25e0 went isFinished=YES without being started by the queue it is in

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

{"object":{"pins":[{"package":"abseil","repositoryURL":"https://github.com/firebase/abseil-cpp-SwiftPM.git","state":{"branch":null,"revision":"583de9bd60f66b40e78d08599cc92036c2e7e4e1","version":"0.20220203.2"}},{"package":"Alamofire","repositoryURL":"https://github.com/Alamofire/Alamofire.git","state":{"branch":null,"revision":"8dd85aee02e39dd280c75eef88ffdb86eed4b07b","version":"5.6.2"}},{"package":"AppAuth","repositoryURL":"https://github.com/openid/AppAuth-iOS.git","state":{"branch":null,"revision":"3d36a58a2b736f7bc499453e996a704929b25080","version":"1.6.0"}},{"package":"BetterSheet","repositoryURL":"https://github.com/egeniq/BetterSheet.git","state":{"branch":null,"revision":"3755b61311812e6751029f1bff47640f3779adc7","version":"1.0.0"}},{"package":"BonMot","repositoryURL":"https://github.com/Rightpoint/BonMot.git","state":{"branch":null,"revision":"2df34a28c97e2413c44a7be70b6dd15adf783baf","version":"6.1.1"}},{"package":"BoringSSL-GRPC","repositoryURL":"https://github.com/firebase/boringssl-SwiftPM.git","state":{"branch":null,"revision":"dd3eda2b05a3f459fc3073695ad1b28659066eab","version":"0.9.1"}},{"package":"CocoaLumberjack","repositoryURL":"https://github.com/CocoaLumberjack/CocoaLumberjack.git","state":{"branch":null,"revision":"0188d31089b5881a269e01777be74c7316924346","version":"3.8.0"}},{"package":"Defaults","repositoryURL":"https://github.com/sindresorhus/Defaults.git","state":{"branch":null,"revision":"981ccb0a01c54abbe3c12ccb8226108527bbf115","version":"6.3.0"}},{"package":"Firebase","repositoryURL":"https://github.com/firebase/firebase-ios-sdk.git","state":{"branch":null,"revision":"111d8d6ad1a1afd6c8e9561d26e55ab1e74fcb42","version":"8.15.0"}},{"package":"FXKit","repositoryURL":"git@git.fl3xx.com:FL3XX/FXKit-ios.git","state":{"branch":"qatar-exec","revision":"085ca2c01d01362128731fd6a3f68eadab5d2f5e","version":null}},{"package":"FXLogin","repositoryURL":"git@git.fl3xx.com:FL3XX/FXLogin-ios.git","state":{"branch":"qatar-exec","revision":"b23f642c5c796cf914f4fc34348b1d674b98df05","version":null}},{"package":"GoogleAppMeasurement","repositoryURL":"https://github.com/google/GoogleAppMeasurement.git","state":{"branch":null,"revision":"ef819db8c58657a6ca367322e73f3b6322afe0a2","version":"8.15.0"}},{"package":"GoogleDataTransport","repositoryURL":"https://github.com/google/GoogleDataTransport.git","state":{"branch":null,"revision":"5056b15c5acbb90cd214fe4d6138bdf5a740e5a8","version":"9.2.0"}},{"package":"GoogleSignIn","repositoryURL":"https://github.com/google/GoogleSignIn-iOS.git","state":{"branch":null,"revision":"9c9b36af86a4dd3da16048a36cf37351e63ccfe1","version":"6.2.4"}},{"package":"GoogleUtilities","repositoryURL":"https://github.com/google/GoogleUtilities.git","state":{"branch":null,"revision":"68ea347bdb1a69e2d2ae2e25cd085b6ef92f64cb","version":"7.9.0"}},{"package":"gRPC","repositoryURL":"https://github.com/grpc/grpc-ios.git","state":{"branch":null,"revision":"8440b914756e0d26d4f4d054a1c1581daedfc5b6","version":"1.44.3-grpc"}},{"package":"GTMSessionFetcher","repositoryURL":"https://github.com/google/gtm-session-fetcher.git","state":{"branch":null,"revision":"4e9bbf2808b8fee444e84a48f5f3c12641987d3e","version":"1.7.2"}},{"package":"GTMAppAuth","repositoryURL":"https://github.com/google/GTMAppAuth.git","state":{"branch":null,"revision":"6dee0cde8a1b223737a5159e55e6b4ec16bbbdd9","version":"1.3.1"}},{"package":"IQKeyboardManagerSwift","repositoryURL":"https://github.com/hackiftekhar/IQKeyboardManager.git","state":{"branch":null,"revision":"474f849accae40fe61b5302d9b057dd48ee073ba","version":"6.5.9"}},{"package":"JTAppleCalendar","repositoryURL":"https://github.com/patchthecode/JTAppleCalendar.git","state":{"branch":null,"revision":"89bc6f1c0426b3bd2856409ec600333a7d087e1b","version":"8.0.4"}},{"package":"KeychainSwift","repositoryURL":"https://github.com/evgenyneu/keychain-swift.git","state":{"branch":null,"revision":"96fb84f45a96630e7583903bd7e08cf095c7a7ef","version":"19.0.0"}},{"package":"leveldb","repositoryURL":"https://github.com/firebase/leveldb.git","state":{"branch":null,"revision":"0706abcc6b0bd9cedfbb015ba840e4a780b5159b","version":"1.22.2"}},{"package":"Logger","repositoryURL":"https://github.com/f-meloni/Logger","state":{"branch":null,"revision":"53c3ecca5abe8cf46697e33901ee774236d94cce","version":"0.2.3"}},{"package":"Lottie","repositoryURL":"https://github.com/airbnb/lottie-ios.git","state":{"branch":null,"revision":"b4bd0604ded9574807f41b4004b57dd1226a30a4","version":"3.5.0"}},{"package":"MagazineLayout","repositoryURL":"https://github.com/airbnb/MagazineLayout","state":{"branch":null,"revision":"8cb3e72038b056317c8402d9ad52fb1c7dbd68db","version":"1.6.11"}},{"package":"MSAL","repositoryURL":"https://github.com/AzureAD/microsoft-authentication-library-for-objc","state":{"branch":null,"revision":"31a806298d6aa71b40504e7ebda6d6a8923f0ebf","version":"1.2.5"}},{"package":"Moya","repositoryURL":"https://github.com/Moya/Moya.git","state":{"branch":null,"revision":"b3e5a233e0d85fd4d69f561c80988590859c7dee","version":"14.0.0"}},{"package":"nanopb","repositoryURL":"https://github.com/firebase/nanopb.git","state":{"branch":null,"revision":"7ee9ef9f627d85cbe1b8c4f49a3ed26eed216c77","version":"2.30908.0"}},{"package":"Nimble","repositoryURL":"https://github.com/Quick/Nimble.git","state":{"branch":null,"revision":"7a46a5fc86cb917f69e3daf79fcb045283d8f008","version":"8.1.2"}},{"package":"NSObject-Rx","repositoryURL":"https://github.com/RxSwiftCommunity/NSObject-Rx","state":{"branch":null,"revision":"3dc30072b740ec35a3949ac8a8217f590a7c59b7","version":"5.1.1"}},{"package":"Nuke","repositoryURL":"https://github.com/kean/Nuke.git","state":{"branch":null,"revision":"7f73ceaeacd5df75a7994cd82e165ad9ff1815db","version":"9.6.1"}},{"package":"PackageConfig","repositoryURL":"https://github.com/shibapm/PackageConfig.git","state":{"branch":null,"revision":"bf90dc69fa0792894b08a0b74cf34029694ae486","version":"0.13.0"}},{"package":"PanModal","repositoryURL":"https://github.com/jordanpichler/PanModal.git","state":{"branch":null,"revision":"8f38a7c4490dccb77eba62f6824af1833be7d845","version":"1.2.8"}},{"package":"Promises","repositoryURL":"https://github.com/google/promises.git","state":{"branch":null,"revision":"3e4e743631e86c8c70dbc6efdc7beaa6e90fd3bb","version":"2.1.1"}},{"package":"Quick","repositoryURL":"https://github.com/Quick/Quick.git","state":{"branch":null,"revision":"09b3becb37cb2163919a3842a4c5fa6ec7130792","version":"2.2.1"}},{"package":"QuickLayout","repositoryURL":"https://github.com/huri000/QuickLayout","state":{"branch":null,"revision":"6be62decbe508d8fc8f9dbafc349d05bab03c38b","version":"3.0.1"}},{"package":"Reachability","repositoryURL":"https://github.com/ashleymills/Reachability.swift.git","state":{"branch":null,"revision":"c01bbdf2d633cf049ae1ed1a68a2020a8bda32e2","version":"5.1.0"}},{"package":"ReactiveSwift","repositoryURL":"https://github.com/Moya/ReactiveSwift.git","state":{"branch":null,"revision":"f195d82bb30e412e70446e2b4a77e1b514099e88","version":"6.1.0"}},{"package":"Realm","repositoryURL":"https://github.com/realm/realm-cocoa.git","state":{"branch":null,"revision":"d6f68b8f613dca3b13430da5e0be5d27b500f486","version":"10.7.7"}},{"package":"RealmDatabase","repositoryURL":"https://github.com/realm/realm-core","state":{"branch":null,"revision":"018adb3469c2882904febca251778129ef4a9b70","version":"10.7.2"}},{"package":"Rocket","repositoryURL":"https://github.com/shibapm/Rocket","state":{"branch":null,"revision":"f75c9736733b489a3456b4f3a47cf13adb99f197","version":"0.9.2"}},{"package":"RxDataSources","repositoryURL":"https://github.com/RxSwiftCommunity/RxDataSources","state":{"branch":null,"revision":"a18cee01c9ee55f04d0c7eb15c77a96c3648c88e","version":"4.0.1"}},{"package":"RxExpect","repositoryURL":"https://github.com/devxoul/RxExpect.git","state":{"branch":null,"revision":"c3a3bb3d46ee831582c6619ecc48cda1cdbff890","version":"2.0.0"}},{"package":"RxGesture","repositoryURL":"https://github.com/RxSwiftCommunity/RxGesture","state":{"branch":null,"revision":"867f176b6695829e350fafc00b5a849bb46a1857","version":"3.0.3"}},{"package":"RxOptional","repositoryURL":"https://github.com/RxSwiftCommunity/RxOptional.git","state":{"branch":null,"revision":"98a1895918e9ba9735a15207dd9c7120e9f51843","version":"4.1.0"}},{"package":"RxSwift","repositoryURL":"https://github.com/ReactiveX/RxSwift.git","state":{"branch":null,"revision":"cec68169a048a079f461ba203fe85636548d7a89","version":"5.1.3"}},{"package":"RxSwiftExt","repositoryURL":"https://github.com/RxSwiftCommunity/RxSwiftExt","state":{"branch":null,"revision":"9620cd55a58c1cf3370375140c45379c40049f55","version":"5.2.0"}},{"package":"RxViewController","repositoryURL":"https://github.com/devxoul/RxViewController","state":{"branch":null,"revision":"2974fc02742497ee26ba3622ced199818d580444","version":"1.0.0"}},{"package":"Signals","repositoryURL":"https://github.com/blinkmeoff/Signals.git","state":{"branch":"master","revision":"3f7fb488a24d3494d451f2301540e14f9f8a50ee","version":null}},{"package":"Siren","repositoryURL":"https://github.com/ArtSabintsev/Siren.git","state":{"branch":null,"revision":"9173fc529731705a737658b2801ccbc19dd385c8","version":"5.8.1"}},{"package":"SkeletonView","repositoryURL":"https://github.com/Juanpe/SkeletonView.git","state":{"branch":null,"revision":"b640c1d8eee79c3a5ad6e0ae1afd2ae0fea30423","version":"1.29.3"}},{"package":"SkyFloatingLabelTextField","repositoryURL":"https://github.com/Skyscanner/SkyFloatingLabelTextField.git","state":{"branch":null,"revision":"a0750ebbc7311f3b3debf99c5e59338e854afa59","version":"4.0.0"}},{"package":"SnapKit","repositoryURL":"https://github.com/SnapKit/SnapKit.git","state":{"branch":null,"revision":"f222cbdf325885926566172f6f5f06af95473158","version":"5.6.0"}},{"package":"swift-log","repositoryURL":"https://github.com/apple/swift-log.git","state":{"branch":null,"revision":"6fe203dc33195667ce1759bf0182975e4653ba1c","version":"1.4.4"}},{"package":"SwiftProtobuf","repositoryURL":"https://github.com/apple/swift-protobuf.git","state":{"branch":null,"revision":"88c7d15e1242fdb6ecbafbc7926426a19be1e98a","version":"1.20.2"}},{"package":"SwiftDate","repositoryURL":"https://github.com/malcommac/SwiftDate.git","state":{"branch":null,"revision":"6190d0cefff3013e77ed567e6b074f324e5c5bf5","version":"6.3.1"}},{"package":"SwiftEntryKit","repositoryURL":"https://github.com/jordanpichler/SwiftEntryKit.git","state":{"branch":null,"revision":"a4f66016562d6dc2253e3f72e6af9dfa64b34ccb","version":"1.2.7"}},{"package":"SwifterSwift","repositoryURL":"https://github.com/SwifterSwift/SwifterSwift.git","state":{"branch":null,"revision":"933f27d8e7fa0bf8200a5d6235e0de383b801126","version":"5.3.0"}},{"package":"SwiftMessages","repositoryURL":"https://github.com/SwiftKickMobile/SwiftMessages","state":{"branch":null,"revision":"b29dd21090b708aa0ae9ecbaf6e2d0487028dc3f","version":"9.0.6"}},{"package":"SwiftShell","repositoryURL":"https://github.com/kareman/SwiftShell","state":{"branch":null,"revision":"beebe43c986d89ea5359ac3adcb42dac94e5e08a","version":"4.1.2"}},{"package":"TOCropViewController","repositoryURL":"https://github.com/TimOliver/TOCropViewController.git","state":{"branch":null,"revision":"d0470491f56e734731bbf77991944c0dfdee3e0e","version":"2.6.1"}},{"package":"Yams","repositoryURL":"https://github.com/jpsim/Yams","state":{"branch":null,"revision":"c947a306d2e80ecb2c0859047b35c73b8e1ca27f","version":"2.0.0"}}]},"version":1}

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

FYI I cannot update Xcode or Firebase version till 2023 so that is not an option for now.

Elsewhere on the internet where Operation went isFinished=YES without being started by the queue it is in:

https://github.com/robertmryan/AFHTTPSessionOperation/issues/7
https://stackoverflow.com/questions/42789556/what-do-i-do-with-this-exception-tripped-shortly-after-cancelling-all-operations
https://stackoverflow.com/questions/48137896/operation-went-isfinished-yes-without-being-started-by-the-queue-it-is-in

Thanks for reporting, @p16r. I tried to reproduce the issue but I wasn't able to get the same error. Could you clarify on what you mean by "I have been able to replicate this is when updating my app from an older build (e.g. from TestFlight) to a newer one."? Does it mean you're updating your app itself or the SDK version? Also, did you make any changes in your code that might be the possible cause the issue?

I mean the most reliable method to replicate this crash is by updating the app from a previous build e.g. 2.10.4 build 299 to 2.10.4 build 300. i.e. I download 2.10.4-299 from TestFlight and use it on my phone, then download 2.10.4-300, and when I first run the new build, it will crash. But next run onwards it won't.
I'm not changing any of the Firebase-related code in between builds.

Hey, just wanted to give an update on this issue. I was able to avoid this crash by replacing existing completion-based API calls with async/await calls.


Add stream.reset to libp2p types

Is your feature request related to a problem? Please describe.
We currently need a @ts-ignore to use stream#reset.
Describe the solution you'd like
We should add the reset method to the appropriate type declaration.
Additional context
#1533

resolved in #1533


[Governance] Align on how we want to manage Governance Parameter Updates

Objective
Design & document how governance parameters should be designed, updated, and maintained. In doing so, determine how they should be governed both in the short & long term.
Origin Document
In Morse (v0), we rolled our own on-chain parameter governance. With Shannon (v1), we are aiming to follow best Cosmos SDK practices to stay up to sync with the latest maintain and build on top of efforts from the community.
Morse (v0)
In Morse:

We use the now deprecated Cosmos x/params module. All parameters live in one place and are namespaced.
Leverage a custom-built multi-sig library.
Created the pocket tx change_param CLI command to execute the results of voted on proposals based on discussions in forum.pokt.network.

Shannon (v1)
In the Cosmos SDK, given that ADR 46 has passed, every module now maintains it's own params and x/params is deprecated.
Below is a code snippet taken from cosmos/mint/v1beta1/tx.proto w/ the new standard of how params should be updated:
// Msg defines the x/mint Msg service.
service Msg {
  option (cosmos.msg.v1.service) = true;

  // UpdateParams defines a governance operation for updating the x/mint module
  // parameters. The authority is defaults to the x/gov module account.
  //
  // Since: cosmos-sdk 0.47
  rpc UpdateParams(MsgUpdateParams) returns (MsgUpdateParamsResponse);
}

// MsgUpdateParams is the Msg/UpdateParams request type.
//
// Since: cosmos-sdk 0.47
message MsgUpdateParams {
  option (cosmos.msg.v1.signer) = "authority";
  option (amino.name)           = "cosmos-sdk/x/mint/MsgUpdateParams";

  // authority is the address that controls the module (defaults to x/gov unless overwritten).
  string authority = 1 [(cosmos_proto.scalar) = "cosmos.AddressString"];

  // params defines the x/mint parameters to update.
  //
  // NOTE: All parameters must be supplied.
  Params params = 2 [(gogoproto.nullable) = false, (amino.dont_omitempty) = true];
}

// MsgUpdateParamsResponse defines the response structure for executing a
// MsgUpdateParams message.
//
// Since: cosmos-sdk 0.47
message MsgUpdateParamsResponse {}

A few things to note here:

The authority address is used to determine who can updates params
There is a note next to the  implementation requiring that All parameters must be supplied
There is no CLI entrypoint to update these as everything is done through on-chain proposals via x/gov

Until Shannon is mature enough to transition to complete on-chain governance via proposals as described in x/gov, we need to use PNF to maintain the address to manage these params.
In practice, this potentially means using the x/authz module to delegate from authtypes.NewModuleAddress(govtypes.ModuleName).String() to some address maintained by the foundation (e.g. foundationAddress).
For example, the following will is an example for the tokenomics parameters:
authority := authtypes.NewModuleAddress(govtypes.ModuleName).String()
foundationAddress := "xxx"
tokenomicsUpdateParam := &tokenomicsmoduletypes.MsgUpdateParams{}
  // repeat this for every `MsgUpdatePrams` method
authorization := authz.NewGenericAuthorization(proto.MessageName(tokenomicsUpdateParam))
grant, err := authz.NewGrant(time.Now(), authorization, nil)
if err != nil {
	panic(err)
}
grantMsg := &authz.MsgGrant{
	Granter: authority,
	Grantee: daoAccount,
	Grant:   grant,
}
// grantMsg needs to be included in genesis

Goals

Understand the best-practices of how other projects maintain on-chain governance parameters
Make it easy to view, manage and maintain an amalgamation of different governance params
Study what we can leverage from x/gov, x/upgrade, x/auth and x/authz
Provide the tooling & documentation needed to interact with these params for testing & production purposes
Determine what parameter governance solution we want to deploy TestNet & MainNet with

Deliverables

[ ] Document (a playbook) on how to manage & maintain on-chain governance params with the selected solution
[ ] A PR that delegates parameter update authorization from the gov module to the PNF owned address
[ ] An investigation into updating PRs that involves:

[ ] Understanding why other Cosmos SDK apps don't have a CLI for this
[ ] If we keep our CLI, a PR that makes it possible to update one parameter at a time

[ ] Create follow-up work / tickets that captures some of the non-goals below

Non-goals / Non-deliverables

Adding parameter update code flows to all modules
A documents (i.e. a playbook) that explain how to use x/gov & x/upgrade in MainNet

General deliverables

[ ] Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
[ ] Testing: Add new tests (unit and/or E2E) to the test suite.
[ ] Makefile: Add new targets to the Makefile to make the new functionality easier to use.
[ ] Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.

Creator: @Olshansk

In terms of next steps, what I'm going to do is reach out to someone in the Cosmos ecosystem that has experience with Protocol upgrades & Governance params to get feedback on potential next steps from their experience.

Note to self: @h5law update max delegated gateways to follow this pattern

Capturing a tl;dr list of questions (without links to keep things simple) that we need to get feedback on.

Is there an "accepted" multisig library we should be using with the Cosmos SDK as an ABCI application? Note: Threshold signing is not necessary, just multiple signatures tied to one address.
Is there an on-chain feature flag system? For example, enable a code-path or change a value at a specific height.
What is the "accepted" way to have a trusted on-chain address (see 1) to drive state changes (see 2)?

I'm closing this out because we have a plan and it's a matter of transitioning everything over nwo.


[SandaloneInstaller] Warn if different ruby used

The goal is to avoid confusion when user is running
bundle/bundler/setup.rb with a different ruby_version than the one
used to install gems.
I just did a rough patch. I would like to discuss to get something cleaner since:

the setup.rb file is currently version agnostic, maybe some users are installing gems with different ruby versions in bundle/ruby/ so that their app can run with multiple ruby versions?
a warning in the output might not be the cleanest solution, failure is a possibility.
we could also test for the existence of directoris for all the paths in setup.rb, I am afraid that this might cause issues or unnecessary warnings.

I'm not sure I understand what problem this is solving, can you please explain what issue this PR is addressing?

ping @brugidou

I want to avoid confusion when the setup.rb file is run with a different ruby version than the one used during the bundle install --standalone.
The use case I have in mind is that I use bundle install --standalone for myapp, package the whole directory in a tarball and ship it to a server to run my app with ruby -r ./bundle/bundler/setup.rb bin/myarr.
If the server is running a different ruby version than the one I used to build the tarball, it won't work and it's hard to debug.

In that case, I think you should be adding the ruby version you need to your gemfile -- by default, bundles should be able to work across multiple ruby versions

OK I understand


Invite you and your Minecraft Modification to introduce to the player/audience in Taiwan.

Hello! We are the Cite Media Holding Group. a publisher in Taiwan. For now we’re devoted to Minecraft promotion, Our company is expected to publish a book entitled <The 100 Most Favorite Minecraft Modification for Game Talents> (tentative title) in December. And we will invite well-known Minecraft Game Talents in Taiwan to carefully select the 100 most recommended Minecraft Modification in the world and introduce them to readers with words and pictures. We think that the Modification of Minecraft you created is quite rich in content and suitable for being selected in the 100 recommended lists. To publish this book, we need to obtain your consent to capture the pictures of your game (less than 10, hereinafter referred to as the authorization target) so that vast readers of Minecraft can understand your work through the introduction of this book. Neither party has to pay the fee for this authorization, but in order to protect the rights and interests of both parties, this email will be used as the basis for authorization that you agree to authorize our company to use the authorization target free of charge in <The 100 Most Favorite Minecraft Modification for Game Talents> (tentative name) by means of, but not limited to, reproducing, distributing and public transferring. If you agree to the authorization, please reply to this email directly and fill in the following information (the following information is only for future reference of the authorizers and sending books, which will not be used for other purposes) to just inform us that you "agree to authorize the pictures free of charge". If you would like to provide your address, we would be very happy to present you a book in return after it is published.
Cite Media Holding Group
Vice General Manager
Daniel Wang
Add：10F, No.141, Sec 2, Misheng E. Rd., Thongshan Distric, Taipei City 10483, Taiwan （R.O.C.）
E-MAIL：
<EMAIL_ADDRESS>TEL：(02)2500-7600  ext.2670   MOB：0916-252-365

Sure, you have a permission to use pictures/screenshots of the mod.
Please don't redistribute any self-compiled builds or jars, though.

thank you:)
thraaawn<EMAIL_ADDRESS>於 2020年2月17日 週一 下午7:21寫道：

Closed #417 https://github.com/thraaawn/CompactMachines/issues/417.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thraaawn/CompactMachines/issues/417?email_source=notifications&email_token=AOQ3QRRR4BQ7MPTOV3PCVBDRDJXNPA5CNFSM4KWM6RNKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWVSZFVI#event-3043332821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOQ3QRTJMCPTQJCHGJEYO73RDJXNPANCNFSM4KWM6RNA
.


Error on building: fatal error: sundials/sundials_context.h: No such file or directory

Recursive git clone was used to perform installing. At folder Exec/RegTests/EB_FlowPastCylinder, make gives
Loading ../../../Submodules/amrex/Tools/GNUMake/comps/gnu.mak...
Loading ../../../Submodules/amrex/Tools/GNUMake/sites/Make.unknown...
Loading ../../../Submodules/amrex/Tools/GNUMake/packages/Make.sundials...
GNUmakefile:265: warning: overriding recipe for target '/'
GNUmakefile:240: warning: ignoring old recipe for target '/'
Generating AMReX_Config.H ...
Generating AMReX_Version.H ...
Compiling AMReX_NVector_MultiFab.cpp ...
In file included from ../../../Submodules/amrex/Src/Extern/SUNDIALS/AMReX_NVector_MultiFab.H:19,
                 from ../../../Submodules/amrex/Src/Extern/SUNDIALS/AMReX_NVector_MultiFab.cpp:12:
../../../Submodules/amrex/Src/Extern/SUNDIALS/AMReX_Sundials_Core.H:6:10: fatal error: sundials/sundials_context.h: No such file or directory
    6 | #include <sundials/sundials_context.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [../../../Submodules/amrex/Tools/GNUMake/Make.rules:262: tmp_build_dir/o/2d.gnu.MPI.EXE/AMReX_NVector_MultiFab.o] Error 1

Hi there,
You first need to install the Third Party Libraries (TPL) by doing a make TPL. You have an example of that particular case in the tutorials.

Aha! Sorry I missed this one. I believe this will do. Thanks for your reply.


Walkthrough is broken once we add Directory.Build.props

After adding Directory.Build.props which overrides the output directory to be under _build, deployment of the resulting app fails because the appxrecipe file cannot be found
The file is in:
C:\Users\asklar\source\repos\rn64Reunion\windows\_build\x64\Release\RN64Reunion (Package)\bin\RN64Reunion (Package)\RN64Reunion (Package).build.appxrecipe
However the packaging project looks for it in:
C:\Users\asklar\source\repos\rn64Reunion\windows\RN64Reunion (Package)\bin\x64\Release\RN64Reunion (Package).build.appxrecipe

I am not able to repro this issue - here's a repro of consuming the SimpleMathComponent in a Project Reunion app: https://github.com/angelazhangmsft/ProjectReunionSimpleMathProjection
I was able to deploy the app fine. If there's a repro, I can look into it

Closing since I wasn't able to repro. Feel free to reopen with a repro project if this issue occurs again.


maps navigation to take a while to load

When I call start navigation (with very good internet ) the load time is very slow ;sometime taking up to 9 whole seconds to load .
is there a way to load faster cos my guess is the styles a loaded into memory of some sort , is there a way for load it ahead of time or initialise the load on start of the app.

Stale issue message


Update examples to work with Platform IO

Describe the bug
Not all examples are included with Platform IO and some have issues running

So you want to flash using Platformio in CLion.
Well, you're in luck. I figured it out. The first thing you have to do is make sure Platformio is installed using pip install platformio. After that, open up CLion and install the Platformio plugin. When you do this, you'll have to restart, and then you want to create a new project. A Platformio option will appear in the new project dialog, and you'll get options for dozens of boards. It will look like this:

Select the board you need, and choose "arduino" as the framework. The platformio.ini file you get will look something like this:
src_dir = .

[env:heltec_wifi_lora_32_V2]
platform = espressif32
board = heltec_wifi_lora_32_V2
framework = arduino

To prepare to compile, you want to change the src_dir to where your own code resides. I want to point mine to main.cpp, which is currently in this directory structure:

My platformio.ini now looks like this:
[platformio]
src_dir = src

[env:heltec_wifi_lora_32_V2]
platform = espressif32
board = heltec_wifi_lora_32_V2
framework = arduino
monitor_speed = 115200
monitor_filters = time

As you can see, I also set the monitor_speed and monitor_filters for the board. But now comes the part we're waiting for. The dependencies can be listed line-by-line like so, using either Platformio identifiers or github links!
lib_deps =
; ClusterDuck Protocol
;    https://github.com/Project-Owl/Crypto.git
     jgromes/RadioLib @ ^4.4.0
;    bblanchon/ArduinoJson @ ^6.17.3
    https://github.com/Call-for-Code/ClusterDuck-Protocol.git

; uncomment for OTA update
; upload_port = duck.local

This can go right under the rest of the platformio.ini. Here, the CDP is linked, which will take care of all the other libraries except for RadioLib. That is included with Platformio's own identifier for the library.
[[Notes On Includes]]

Platformio's plugin does not keep CLion from sounding the alarm on missing libraries. Many of us use the visual queues provided by our editors to know what's installed and what's missing. Dependencies managed by Platformio won't give the editor a heads-up. So a poriton of the main.cpp for this project will look like this:

The code will still compile, given other conditions of C++ files are met.

There is a way around this: editing the CMakeLists file to explicitely declare include directors. This could look something like below:

include_directories(lib/pubsubclient/src/ lib/arduino-timer/src)

The lib folder is in the top of your directory tree, and the libraries are right below, with typical C++ project structure. If you want to include directories from CMakeLists, then you will have to have all those libraries locally somewhere. But, you will have code completion working.

One of those other conditions is typical C++ formatting helper functions. I noticed that .ino files from the Arduino IDE allow you to define helper functions in any order, meaning the parser will look first, compile later. CLion follows standard rules in that all helpers have to be defined before they're used, so many of the sketch files will have to be re-arranged.


Double check Q15 results

Cypher spec was changed in 385a4e166af49cb8ba2eb05725960ed10f91215e.

PostgreSQL bi-15 implementation seems unaffected by the change.

Great, thanks for checking.


remove max limits

We had noticed scaling issues and long queue times for messages within
sqs, this is probably the first step to actually just removing the
separate webhook and serving requests directly to the scale up lambda
Signed-off-by: Eli Uriegas<EMAIL_ADDRESS>

this has already been merged in closing.


Adapt recipes for LTS v1.0.2

I made adaptions to mcmc and the dark-matter notebooks to work for LTS v1.0.2
I also updated the env files.
Resolves #13
Resolves https://github.com/gammapy/gammapy/issues/4351

I also wonder if it is worth still having the dark matter recipe because this information is now available in a tutorial
https://docs.gammapy.org/1.2/tutorials/api/astro_dark_matter.html

Thanks @Astro-Kirsty !
Have you checked whether the notebooks run fine? I had noticed some time ago that the interactive edition was not running at all.

To clean the notebooks (black and strip, you can use the scripts here:
from utils import notebook_black, notebook_strip

notebook_black(path_to_notebook)
notebook_strip(path_to_notebook)

Thanks @Astro-Kirsty !
Have you checked whether the notebooks run fine? I had noticed some time ago that the interactive edition was not running at all.

Yes it worked fine for me

@registerrier, I just had to adapt the version of jupyter-lab to ensure it works correctly.
All is good now


Deleting the opening Post of a Thread on the Dashboard causes errors

Deleting Posts in a Thread is possible on both the Admin UI and the frontend, although the first Post (which is created when creating the Thread) can't be deleted on the frontend. However, when deleting all the posts from a Thread on the Admin UI, it will cause NREs when trying to view the Thread or the Forum the Thread is in.
Possible solutions:

Don't let the users with Admin UI access deleted the last Post in a Thread, instead show a warning that in this case the Thread itself should be deleted.
When trying to delete the last Post in a Thread, show a warning stating that the Thread will also be deleted. If the user clicks "OK", then both that Post and its Thread should be deleted.

So what do you think about the possible solutions? The first one is easier, the second one may require some JS to modify the message that comes with the RemoveUrl property.
I think the first one may be better.

Hmmmm, I kinda think that number 2 is better - you have the warning saying the thread will be deleted, and you dont want to make it harder to delete threads?

So be it, sir!


unknown field "repoPasswordSecretRef" in io.k8up.v1.Restore.spec

Description
Hi Team,
I am performing restore operation from s3 to pvc. but having issue with field "repoPasswordSecretRef".
Could you please check it seems an issue .
Additional Context
No response
Logs
k apply  -f restore.yaml -n test

error: error validating "restore.yaml": error validating data: ValidationError(Restore.spec): unknown field "repoPasswordSecretRef" in io.k8up.v1.Restore.spec; if you choose to ignore these errors, turn validation off with --validate=false

 cat restore.yaml
apiVersion: k8up.io/v1
kind: Restore
metadata:
  name: restore-test-mfw
  namespace: snapshot-test

spec:
  repoPasswordSecretRef:
    name: backup-repo
    key: password
  restoreMethod:
    folder:
      claimName: mfw-restore
  backend:
    s3:
      endpoint: http://minio-service:9000
      bucket: k8up
      accessKeyIDSecretRef:
        name: backup-credentials
        key: username
      secretAccessKeySecretRef:
        name: backup-credentials
        key: password

Expected Behavior
restore yaml should be deploy
Steps To Reproduce
No response
Version of K8up
2.2.0
Version of Kubernetes
v1.20
Distribution of Kubernetes
kubernetes

Hi @vfolk30
The repoPasswordSecretRef key should be under the spec.backend object, see: https://k8up.io/k8up/2.3/references/api-reference.html#k8s-api-github-com-k8up-io-k8up-v2-api-v1-backend

Thank you @Kidswiss .
In tutorial documents its no very clear thats why I have faced this problem. I am new to k8up and performing a POC
https://k8up.io/k8up/2.3/tutorials/tutorial.html#step_4
SAMPLE FILE FROM TUTORIAL:
apiVersion: k8up.io/v1
kind: Restore
metadata:
name: restore-test-mfw
namespace: snapshot-test
spec:
repoPasswordSecretRef:
name: backup-repo
key: password
restoreMethod:
folder:
claimName: mfw-restore
backend:
s3:
endpoint: http://minio-service:9000
bucket: k8up
accessKeyIDSecretRef:
name: backup-credentials
key: username
secretAccessKeySecretRef:
name: backup-credentials
key: password
I assume it should be updated,

Hi @vfolk30
This one seems correct to me: https://github.com/k8up-io/k8up/blob/master/docs/modules/ROOT/examples/tutorial/restore/wordpress.yaml
Also, the snippet here is correct: https://k8up.io/k8up/2.3/tutorials/tutorial.html#_how_does_k8up_work
I've skimmed through the tutorial and didn't find a wrong yaml file.

@vfolk30 Fixed with #704. Thanks for reporting it!


Export as React component

Specific Demand
Export Dioxus component as React component so it can be used in React apps
This would be great for gradual adoption.
Implement Suggestion
It doesn't have to be fancy at first - e.g. no props.

This would be a great addition! It might be better as an external library instead of including this in the main Dioxus repo, but Dioxus should expose the primitives required to implement this. This example illustrating how to make Yew work with react could be a good starting point

We suggest doing webcomponents with dioxus.
https://github.com/ilaborie/dioxus-web-component is a great library for this.
We probably won't support this any time soon, but web components are a decent approach in the interim.


Don't use Windows API

Details
Currently, we use Windows API to read and write resources. If we replace those with manual reading and writing of PE files (potentially a huge undertaking), this library could then be fully cross-platform. Not sure if it's a lot of use to be able to edit resources of Windows PE files on non-Windows operating systems though.

Just used Ressy to make a small command line tool to change the version number of exe files on our CI server (Linux). It worked with wine no issue.

Just used Ressy to make a small command line tool to change the version number of exe files on our CI server (Linux). It worked with wine no issue. I know its not ideal, but just wanted to let people, who might be looking, know.

Nice 🙂 Glad it worked for you.

Another reason not to use Windows API:
It seems that all the resource functions create temporary files on disk when reading/writing resources. These files are not always deleted, for example if the function fails in some very fatal way. Additionally, if the PE is corrupted (easy to reproduce by changing a random string to a shorter/longer string without updating the pointers in the headers), then these files end up growing indefinitely and never get deleted. Working with binary files ourselves gives us more control and lets us avoid such problems.

Maybe these classes could be helpful:

https://learn.microsoft.com/en-us/dotnet/api/system.reflection.portableexecutable.pereader
https://learn.microsoft.com/en-us/dotnet/api/system.reflection.portableexecutable.managedpebuilder


"Service Unavailable" error when adding dependencies [1.19.4]

I put in:
dependencies {
modImplementation 'net.kyrptonaught:customportalapi:0.0.1-BETA63-1.19.4'
include 'net.kyrptonaught:customportalapi:0.0.1-BETA63-1.19.4'

}
and it pops up with the error as:
Could not GET 'https://server.bbkr.space/artifactory/libs-release/net/kyrptonaught/customportalapi/0.0.1-beta63-1.19.4/customportalapi-0.0.1-beta63-1.19.4.pom'. Received status code 503 from server: Service Unavailable
how do I fix it? (Updating to 1.20 is not an option for me.)

It fixed itself but now I have a different issue...


Underscores in scope name

I notcied scope names cannot have underscores contained in them and I have an npm scope that has an underscore. I'm sure there's a good reason for it and I would agree scope names should use hypens instead of underscores as it's the standard case convention the JS world seems to use but thought I would create an issue for backwards compatibility purposes.
FYI I wasn't able to find any package names in the top 10,000 that contain an underscore in their name using @[^/]*_[^/]*\/

We are intentionally only allowing hyphens.
We also disallow it because it is confusing for users to have to remember "did this package / scope" use underscores or hyphens. This is an annoying problem in the Rust community for example.


Bump Version of ReTerm to Latest

Changelog of ReTerm between these two releases

I tested with toltecmk. The generated .ipk file installed fine and fixed the inverted colors issue I was having with the original version (also possible removed the duplicate icons in oxide).

What OS version did you test on? The testing branch is in the middle of adding 3.3.2 support, so I'll need to verify that it works on 3.3.2 against toltec testing before I merge. I'm also holding off on merging anything until the stable merge is done for ease of testing the stable merge stuff.

What OS version did you test on? The testing branch is in the middle of adding 3.3.2 support, so I'll need to verify that it works on 3.3.2 against toltec testing before I merge. I'm also holding off on merging anything until the stable merge is done for ease of testing the stable merge stuff.

This was on <IP_ADDRESS>6 against testing

Alright, this will also need to be tested again 2.15. I'll try to take some time after I get the stable merge accross the finish line to validate on both my devices.

Alright, this will also need to be tested again 2.15. I'll try to take some time after I get the stable merge accross the finish line to validate on both my devices.

Although, you can't actually use ReTerm on 2.0 or the rM1 because neither have support for the folio keyboard. So maybe changing the supported device/firmware string would be more apt.

Although, you can't actually use ReTerm on 2.0 or the rM1 because neither have support for the folio keyboard. So maybe changing the supported device/firmware string would be more apt.

You can connect an external keyboard, or pipe evdev input through to the device via various methods on the rM1, which is why I added ReTerm with both rM1 and rM2 support.

Oh cool!

When attempting to run this on a rM2 running <IP_ADDRESS>9

Same error on the rM1

Is it worth it to figure out/do you know why the changes break 2.0 support?
Also, it looks like you made changes to the package file inside the ReTerm repo, do those need to be propagated into this instance of the package file.

Is it worth it to figure out/do you know why the changes break 2.0 support?

It looks to be an intentional change to have the application stop if no keyboard is detected.

Also, it looks like you made changes to the package file inside the ReTerm repo, do those need to be propagated into this instance of the package file.

They may be worth including. I haven't looked at what the changes were.

I've marked this as a draft, as it will need to be reworked to split the package into the OS 2.x and OS 3.x versions.


[Bug]: Cannot parse constant-decl when array-member-type-descriptor is a type-reference

Description
Code:
type A int;
const A[] ARR_52 = [1, 2, 3];

Parser output:
type A int;
const A MISSING[] MISSING[=][]  MISSING[;]ARR_52  MISSING[]= [1, 2, 3];

The output of the parser is wrong.
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

const int[] ARR_52 = [1, 2, 3]; gets parsed though.

Workaround is to use parenthesis.
const (A[]) ARR_52 = [1, 2, 3]; // works
const (A)[] ARR_52 = [1, 2, 3]; // works

const M|map<int> mUnion3 = {a: 1, b: 2}; // cannot parse
const (M|map<int>) mUnion3 = {a: 1, b: 2}; // can parse
const map<int>|M mUnion3 = {a: 1, b: 2}; // can parse

Should be the same reason.


Fixed edge-case with server launch.

[x] I have run rspec and corrected all errors
[x] I have run rubocop and corrected all errors
[x] I have tested this change locally and tried to launch the server as well as access a project, and with that at least one build
[x] If there is an existing issue, make sure to add Fixes ... as part of the PR body to reference the issue you're solving

Changes
Fixed edge-case with server launch when Services.ci_config_git_repo_path exists, but the directory doesn't have the necessary configuration files.
Rationale
When setting up fastlane.ci again, I ran into an issue where the configuration repository was not cloned properly. The directory for Services.ci_config_git_repo_path existed, but it was missing the necessary configuration files: users.json, projects.json, and environment_variables.json.

I have never subscribed to this thread, someone is doing this to my phone And I want reversed, or stopped all off these things. Please. Someone is stealing all my info and getting g into my accounts, and pretending they are me. I mean I k ow who it is, just don't k ow how to stop it


Hbase 14850

HBASE-14852 and HBASE-14853 are both already marked closed.
Could you limit this to just new changes for HBASE-14850?

Are you still interested in working on HBASE-14850? Without a response, this issue will get closed as stale.


Generated commit - bump version to 1.26.0-SNAPSHOT

Tests are expected to fail because there is no published 1.26.0-SNAPSHOT version for http/oauth clients.


add 3 VRFs (blue, red, yellow)

see https://github.com/opiproject/opi-evpn-bridge/blob/2d7ea90f6a281affe82f74b0879a1a5c15fca77c/conf/example.conf

https://github.com/opiproject/opi-evpn-bridge/pull/18

The code changes are being reviewed now.


Expose setVolume for ContainerRequest

Sorry for being so slow. I merged https://github.com/alexbiehl/testcontainers-hs/pull/17 which is basically this PR.


Update 2018-11-28-wg-net-survey.md

Blitz can have negative connotations for some folks so this PR renames the Tokio Doc link to reflect the revised name of the post.

Good catch, thanks!


Add npm package

Looks like they encourage themes to be published on npm:

https://thelounge.chat
https://www.npmjs.com/search?q=keywords%3Athelounge-theme&page=0&perPage=20

Should we also create a package and edit the install instructions?

Oh, missed their standards. As I tried to push it to npm, I realized there is already another version of Dracula theme for The Lounge. Oh snap. As there is no screenshot, I don't know what's different in @SpaceLenore's version. I have used only colors defined here and flattened it out. Can we join forces?
Another option is for me to release it for different package name like thelounge-theme-dracula-flat or something.

Let's see what @SpaceLenore thinks. If there's no response we can create a thelounge-theme-dracula-official.

Yes, let's give this some time. thelounge-theme-dracula-official sounds good.

Hi!
I do agree that joining forces sounds like a good idea. I currently don't have any screenshots (but I do plan to add some) you can install the theme with the command thelounge install thelounge-theme-dracula to try it out if you wish to. In short, it is the standard Dracula colours and no shadows.

I'll test it out soon when I have more time from work. The straight out difference when looking at the code is that I use more CSS vars and style more components like things in mobile and network and channel list, but otherwise feels like a similar approach to mine. Could we add @SpaceLenore as another conributor to this team, merge the repos in some way and publish this repo linked to npm or how should we do this? Suggestions? @zenorocha

Finally got time to look into this more carefully.
@SpaceLenore/thelounge-theme-dracula version:

@dracula/thelounge version:

So it seems both are good in their own ways, mine is based on more polished look and parts from thelounge-theme-crypto, some modern preferences like timestamp on the right and some minor fixes for mobile interface, darker sidebar etc., also I have fixed preview contrasts etc., as @SpaceLenore's version has more direct approach and timestamps on the left.
Code-wise I already commented:

The straight out difference when looking at the code is that I use more CSS vars and style more components like things in mobile and network and channel list, but otherwise feels like a similar approach to mine. Could we add @SpaceLenore as another conributor to this team, merge the repos in some way and publish this repo linked to npm or how should we do this? Suggestions?

So what do you suggest? These two feel like completely different themes, the biggest differences being perhaps whether the dark or light sidebar is preferred or not. Both use the official colors though. In my opinion two separate themes is not a bad idea either and I'm open to publishing a npm package for my version as well. But before that I want to hear your opinions.

@ronilaukkarinen Thanks for the nice overview of the differences! I agree that our themes are quite different even if we use the same colors so I agree that two different repos and packages might be a good idea.

Would definitely love to see this version of Dracula also pushed to npm. Agree it looks like there definitely exists space for both!

Would definitely love to see this version of Dracula also pushed to npm. Agree it looks like there definitely exists space for both!

Any word on this @ronilaukkarinen / @zenorocha?

@xnaas Thanks for the ping! I can go ahead and release this as thelounge-theme-dracula-official. I'll let you know!

Npm package is now created.
@xnaas Theme can be now installed with thelounge install thelounge-theme-dracula-official. Tested it and it works.
@zenorocha Does the page update automatically at https://draculatheme.com/thelounge? I have updated the installation instructions.


Port to 1.18.2

Hello, could you please tell me if it's possible to port Armor Stands to version 1.18.2? Will you do the porting?

If I do port it to 1.18.2 it probably won't be for a long time. It's a lot of work to maintain multiple versions and I do this as a hobby, so if I was going to do it I'd wait for a good stable version of the mod, then port it back and never touch the 1.18.2 version again.
That being said, this and all my mods are licensed under MIT, which is fully permissible. If you or anyone else wants to port and rehost it, you are perfectly allowed to do so!


Google Translate doesn't get unit tested in CI (Github Actions)

Root cause:
The method to authenticate Github Actions code to Google Cloud is described here (this is code provided by Google). After a checkout of the repository, the authentication methods create temporary JSON files in the repository folders. However, nbdev 2.0 CI code checks out the repository again using the Github actions/checkout@v3 with the default clean=true option, overwriting the Google Cloud JSON authentication files. Subsequent calls to Google Cloud therefore cannot be authenticated anymore.
The proper way to fix this would be:

Fork fastai/workflows
Add an option clean_repo to fastai/workflows/nbdev-ci/actions.yml to allow setting the clean option for actions/checkout@v3 (default: true)
Add the code to add Google Cloud authentication to this repository in .github/workflows/test.yaml with the option clean_repo=false set
Test this fix with the forked fastai workflows
Submit PR to fastai
After PR is accepted change .github/workflows/test.yaml to use fastai/workflows again instead of the fork

The workaround is to run unit tests with nbdev_test on a local Jupyter notebook instance (ideally with GPU support) or on Google Colab (also ideally with GPU runtime)


Error generating scaffold

Hello when I install the library for scaffold gives me the following error in laravel 5.1 ReflectionException]
Class Illuminate \ Support \ Composer does not exist
this-law run the command php artisan make: scaffold Tweet but I believe migration and seeder, unemployment does not go beyond that, does not create the models, or the views or controllers as say only laravel 5.1, I have not tried in laravel 5.2 or 5.3

Hello,
has a branch called "laravel-5.1" that solved it's problem or you can replace manually in file "src/Commands/ScaffoldMakeCommand.php" the line:
use Illuminate\Support\Composer;
to
use Illuminate\Foundation\Composer;
So sorry for it problems, in future new version don't has more it.
:)

Thanks for the quick response and fix the error


docs: improve CodeSandbox integration

Fixes #3927.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4010   +/-   ##
=======================================
  Coverage   99.84%   99.84%
=======================================
  Files         185      185
  Lines        3251     3251
=======================================
  Hits         3246     3246
  Misses          5        5

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 5532548...080a37e. Read the comment docs.


Upgrade to julia 1.8

This PR:

Upgrades to julia 1.8 (will upgrade to 1.9 in follow up)
Updates the manifest files
Adds JET to the examples env
Deletes the perf folder, since all of our test runs in the examples / gpuenv environments

bors r+


structure: unary operators

Checks whether unary operators are defined on the right side of the variable.
recorded in #66
fixes #29

Thanks for your contribution @wickedOne!

@wickedOne
The rule is Place unary operators (!, --, ...) adjacent to the affected variable
The implementation doesn't work correctly.
Actual result:
// good
$a = !$b;
// good
$a = ! $b;
// good
$a = ++$b;
// good
$a = ++ $b;
// bad
$a = $b++;
// good
$a = $b ++;

Expected result:
// good
$a = !$b;
// bad
$a = ! $b;
// good
$a = ++$b;
// bad
$a = ++ $b;
// good
$a = $b++;
// bad
$a = $b ++;

Please check out #125, merged and released in v3.0.3.
Thanks in advance!


General changedHandler for AttachedBehaviors

When you create an AttachedBehavior with multiple properties, this leads to having a lot of different changedHandlers. So it'd be nice if we could come up with a general handler, which gets called no matter what property changes.
Also we should think about the possibility to batch property changes and trigger the callback only once. As an example let's say you wrap Bootstraps Popover and in the handler you'd like to re-initialize the component. So instead doing it for each property change, having them stashed and only executing the function ones would be nice.
Regarding naming I'd propose one of the following:
onChanged
onPropertyChanged
propertiesChanged
anyChanged
the serialization should contain the propertyName as well as the newValue for the prop.

Ok this one is kinda deprecated and alternatively dynamicProperties solve the same thing as well


Fix verticalMargin setter.

Fixes bug where verticalMargin is string (eg: 12px) and has same numeric value as opt.height.

Coverage remained the same at 70.525% when pulling de6b430dafe0982c9a9998233d8a589bc3d8c5df on jonapgar:patch-1 into fa4f2d0d076120f380f475eb71cbc585c4e4197b on troolee:develop.

@jonapgar Can you provide a fiddle or some environment where I can see what exactly this bug is?

I'm closing this because there wasn't an example provided, but if you can show me where this is fixing something in a new PR, I will happily merge!


move execute( to fedloop

encapsulation means it should probably be somewhere else, it doesn't make sense for it to be in parse

see #1 for commits, messed up commit messages

merged pr


The example of calculating daily returns on the homepage is wrong

On the homepage it is described how you can use the diff method on a series to calculate the daily returns from a series of prices Link to homepage
I think that example is wrong - you write "To calculate daily returns, we need to subtract the price on previous day from the price on the current day. This is done by using the Diff extension method (another option is to use Shift together with the overloaded subtraction operator). Then we divide the difference by the current price and multiply the result by 100.0 to get value in percents."
This gives the formula:
(CurrentPrice - PreviousPrice) / CurrentPrice
But this is wrong the formula should be:
(CurrentPrice - PreviousPrice) / PreviousPrice
As described on wikipedia
The code on the homepage looks like this:
var returns = msft.Diff(1) / msft * 100.0;
But should be like this (assuming the key is a DateTime):
var returns = msft.Diff(1) / msft.SelectKeys(x => x.Key.AddDays(1) * 100.0;

Thanks for pointing it out. This is definitely wrong. Will fix it.

@zyzhu I found a more elegant way to calculate the return/pct change:
var returns = msft.Diff(1) / msft.Shift(1);
It could be useful to have a built in function called PctChange (like pandas pct_change


SELECT statement with IN clause

The following query (see here for more legible version)
SELECT C_DocType.C_DocType_ID,NULL,COALESCE(C_DocType_Trl.Name,C_DocType.Name) AS Name,C_DocType.IsActive FROM C_DocType LEFT JOIN C_DocType_TRL ON (C_DocType.C_DocType_ID=C_DocType_Trl.C_DocType_ID AND C_DocType_Trl.AD_Language='es_AR') WHERE C_DocType.AD_Client_ID=1010016 AND C_DocType.AD_Client_ID IN (0,1010016) AND C_DocType.c_doctype_id in ( select c_doctype2.c_doctype_id from c_doctype as c_doctype2 where substring( c_doctype2.printname from length(c_doctype2.printname) ) = ( select letra from c_letra_comprobante as clc where clc.c_letra_comprobante_id = 1010039) ) AND ( (1010094!=0 AND C_DocType.ad_org_id = 1010094) OR 1010094=0 ) ORDER BY 3 LIMIT 2000
casts:
net.sf.jsqlparser.parser.ParseException: Encountered " "IN" "in "" at line 1, column 345.
Was expecting one of:
    <EOF>
    "FOR" ...

Column 345 would be the part C_DocType.c_doctype_id in ( select c_doctype2 ...

Shall I try fix this issue or anybody solved this already?

Sorry. I missed your issue. The problem is not "in" but the substring(a from b) construct. JSqlParser does not support this one. There is already a pull request for this. In fact there are two.

@wumpz this too is not an issue anymore

Cool. Thx for testing this.


curious about the react version..

it says failed in the readme, does it build or is it mostly just an earlier attempt?

@makeiteasierapps was working on this version, I'm not sure what the current state is. Most recent work has been done on the flutter app.

https://github.com/makeiteasierapps/Friend/tree/main
Please see the readme


Feature request - only scan during specified time period

Hi, sorry this is not a bug.
I think it would be cool if you could specify that we only scan for occupants during a specific time range. For example I don't want or need it to scan if I am on the network while I'm sleeping.

@wi-brewer If you don't need to scan you can always enable/disable the module with a cron job. (There is another module that make this easy for you, but I forgot which one.) So I don't see the need to add that functionality into the module.

@E3V3A  - would that be MMM-ModuleScheduler by any chance? :)