[$250] Andriod/IOS - Connect Bank Account - Company page displayed instead Personal Information Page after tap back button on Onfido flow, error message displayed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the app
Log in with the expensifail account
Go to Setting - Workspace
Connect Bank account
Select Connect manually
Put routing number and account number
Follow the flow until you hit Onfido flow
Tap back button

Expected Result:
Personal page displayed instead company Information Page after tap back button on Onfido flow, no error message
Actual Result:
Company page displayed instead Personal Information Page after tap back button on Onfido flow, error message displayed
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/193170438-a5df5569-20f2-48d6-a985-36c4f412fe92.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

I'm pretty confident this can be fixed externally by passing a different prop to the onFido component

👋 The contributor will need an account number and routing number to test with, no?

I tested this flow, but are we sure this is what we want?
I can see comments in RequestorStep.js which says we're explicitly sending them back to the CompanyStep,
// We're taking the user back to the company step. They will need to come back to the requestor step to make the Onfido flow appear again.

Proposal
This is happening because in the following lines of RequestorStep,
https://github.com/Expensify/App/blob/6748e8a6c5363a626490e436c84ecd53df7266c6/src/pages/ReimbursementAccount/RequestorStep.js#L189-L197
We're setting the step as CONST.BANK_ACCOUNT.STEP.COMPANY, which we need to set it to CONST.BANK_ACCOUNT.STEP.REQUESTOR
But just updating the step doesn't help as the onFido component is set o the RequestorStep itself, so on back press it shows a blank page. To fix this we need to move the this.props.achData.sdkToken to state.
    this.state = {
      ...
+   onfidoToken: this.props.onfidoToken,
    };

On L166
-     const shouldShowOnfido = achData.useOnfido && this.props.onfidoToken && !this.state.isOnfidoSetupComplete;
+     const shouldShowOnfido = achData.useOnfido && this.state.onfidoToken && !this.state.isOnfidoSetupComplete;

<Onfido
+      sdkToken={this.state.onfidoToken}
-      sdkToken={this.props.onfidoToken}
      onUserExit={() => {
+           this.setState({ onfidoToken: undefined });
-          BankAccounts.goToWithdrawalAccountSetupStep(CONST.BANK_ACCOUNT.STEP.COMPANY);
+.        BankAccounts.goToWithdrawalAccountSetupStep(CONST.BANK_ACCOUNT.STEP.REQUESTOR);
      }}
      onError={() => {
          Growl.error(this.props.translate('onfidoStep.genericError'), 10000);
+           this.setState({ onfidoToken: undefined });
-          BankAccounts.goToWithdrawalAccountSetupStep(CONST.BANK_ACCOUNT.STEP.COMPANY);
+.        BankAccounts.goToWithdrawalAccountSetupStep(CONST.BANK_ACCOUNT.STEP.REQUESTOR);

      }}

@stitesExpensify @trjExpensify I tested this flow, but are we sure this is what we want?
I can see comments in RequestorStep.js which says we're explicitly sending them back to the CompanyStep

Oh, interesting! 🤔 I wonder why that is? The step before Onfido is personal details, so why do we skip over that page and go back to CompanyStep instead? @kevinksullivan & @marcaaron might know as they worked on this originally, I believe.

Hmm trying to scroll back in my DM with @marcaaron because I believe this was part of the original design since it was easier at the time. I think we kick the user back to the company info step because we don't create the VBA until after a certain point, so this may have to do with that timing and the need to re-submit the info. @marcaaron can you fill in the large gaps in my explanation?

so this may have to do with that timing and the need to re-submit the info.

Can you elaborate on resubmitting the info?
I did a basic test on @akshayasalvi's proposal and it seems to be working. But I haven't tested thoroughly so if there's something specific to be considered when doing this, it'll be helpful if can be linked to the issue.

@kevinksullivan @marcaaron @stitesExpensify Quick bump.

Proposal
The problem is with the error messages we check on catching errors. We don't want to display the error when messages are one of these:
USER_CANCELLED: 'User canceled flow'
USER_TAPPED_BACK: 'User exited by clicking the back button.',
USER_EXITED: 'User exited by manual action.',
Currently, we are missing USER_EXITED message, I'm guessing since it was implemented in some of the later versions on react native onfido SDK.
Solution:

Add a new onfido error message in CONST.js:

USER_EXITED: 'User exited by manual action.',
https://github.com/Expensify/App/blob/11c2d496c3528ee00634440076ed8000bdcea3cb/src/CONST.js#L587-L606

Add check for this message in index.native.js where we are conditional asking on should we display the error(did user exit the flow or something else happened)

https://github.com/Expensify/App/blob/2f5603d8441b4ad05b2e7bcdd277051508c04088/src/components/Onfido/index.native.js#L44-L54
if (
  _.contains(
    [
      CONST.ONFIDO.ERROR.USER_CANCELLED,
      CONST.ONFIDO.ERROR.USER_TAPPED_BACK,
      CONST.ONFIDO.ERROR.USER_EXITED,
    ],
    errorMessage
  )
) {
  this.props.onUserExit();
  return;
}

And now there is no error anymore

Also clear onfido token on RequestorOnfidoStep.js

<Onfido
  sdkToken={this.props.onfidoToken}
  onUserExit={() => {
    BankAccounts.clearOnfidoToken();
    BankAccounts.goToWithdrawalAccountSetupStep(
      CONST.BANK_ACCOUNT.STEP.REQUESTOR
    );
  }}
  onError={() => {
    // In case of any unexpected error we log it to the server, show a growl and return the user back to the company step so they can try again.
    Growl.error(this.props.translate("onfidoStep.genericError"), 10000);
    BankAccounts.clearOnfidoToken();
    BankAccounts.goToWithdrawalAccountSetupStep(
      CONST.BANK_ACCOUNT.STEP.REQUESTOR
    );
  }}
  onSuccess={(onfidoData) => {
    this.submit(onfidoData);
  }}
/>;

VIDEO:
https://user-images.githubusercontent.com/70144379/194034961-d9226719-c3d5-49be-b5e9-ffc1df0b2ccb.mov

@trjExpensify Based on @kevinksullivan's comment it seems we did that only because it was easier that time. Should I evaluate the proposal?

Yeah, at a minimum we want to fix the error appearing when navigating back. I do also think it makes more sense to navigate back to the personal information step instead of the company info step, but I don't have enough insight as to whether there's a show stopper in this:

I think we kick the user back to the company info step because we don't create the VBA until after a certain point, so this may have to do with that timing and the need to re-submit the info

If the proposal encompasses these things, then I don't see a reason why that isn't fine:

No error message when clicking back from Onfido
navigates back to the personal information step
navigating forward again to Onfido to complete it, the request to create the VBA works correctly (i.e you don't run into errors and need to go and re-enter any info in the company step etc)

@trjExpensify In that case @Uros787's proposal seems to be fixing the error part. Should we go ahead and fix atleast that part?

https://github.com/Expensify/App/issues/11461#issuecomment-1268219826 - the video seems to navigate back to the personal info page as well though?

@trjExpensify correct, the problem stated that we should navigate to the personal info page
although as @mananjadhav said we can just fix the error part if we don't want to navigate to the personal info page

Yeah cool, I was just clarifying we seemingly solve both problems with the proposal. Did you test this as well?

Navigating forward again to Onfido to complete it, the request to create the VBA works correctly (i.e you don't run into errors and need to go and re-enter any info in the company step etc)

Yeah I tested the same code when @akshayasalvi proposal's earlier. It does solve both the issues. I thought if we're not sure whether to move back to Personal Information.
If we do plan to solve the transition too, then I am a little confused here because @akshayasalvi also proposed the same solution.

I'm going to tag a few other people that I think are familiar with this flow.
@MariaHCD @nkuoch @ctkochan22 - is there a technical reason why we can't navigate back to the personal step here, instead of skipping over it and navigating back to the company step?

I don't think there's a reason why we can't navigate back to the personal step here. We'd already did that for the back button in the header in this PR: https://github.com/Expensify/App/pull/11232
But looks like we missed changing the navigation for the Onfido component: https://github.com/Expensify/App/blob/dfb5bca05a5b12e62ec86520819fd5a4ac66e405/src/pages/ReimbursementAccount/RequestorStep.js#L189-L192

Awesome, thanks @MariaHCD!

Yes @trjExpensify and @stitesExpensify , good with @Uros787's proposal.
🎀 👀 🎀
C+ reviewed

Cool thanks, let me know where I should apply

Applied.

Hey, I wanted to know if this is eligible for reporting. I had reported the error part on slack (thread) but we decided to do nothing.

@mananjadhav @trjExpensify pr created.

@Uros787 @trjExpensify @stitesExpensify Based on the comment here I feel we should put this on hold until https://github.com/Expensify/App/pull/11719 gets merged.  This is to avoid rework for @Uros787.
Let me know if anyone thinks otherwise.

I agree. Updated the title.

Yep, makes sense. Updated the title to reflect what PR it's held on.

The PR this was held on in merged. Removing the hold. @Uros787 based on the changes in that PR do you see your proposal changing at all?

PR changes are fine, I'll finish the testing by tomorrow.

The PR has gone through C+ review, it's now over to @MariaHCD & @ctkochan22 for review. Actually, @stitesExpensify why aren't you also assigned the PR to review as the CME? 🤔

PR was merged, but I am not sure about BugZero Checklist.  Can you take a look at it @trjExpensify ?

Sure, that's the new checklist for BugZero to ensure we square all these items away. Obviously, the last three won't happen until we hit +7 days from the production deploy, but I can get going on the suggested regression tests to add to TestRail once we hit staging and it passes QA regression testing.

The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

For this one. IIRC, this wasn't actually a regression, we just implemented it to return to the Company step instead of the Personal step. Is that right? What about the Onfido error though, do we know what PR caused that one?

Issue not reproducible during KI retests. (First week)

What about the Onfido error though, do we know what PR caused that one?

Bump on this. If I understand it, we think the USER_EXITED error was added to the Onfido SDK later than when we initially implemented it, and therefore we didn't suppress showing it like we did USER_CANCELLED and USER_TAPPED_BACK. Is that correct?

we think the USER_EXITED error was added to the Onfido SDK later than when we initially implemented it, and therefore we didn't suppress showing it like we did USER_CANCELLED and USER_TAPPED_BACK. Is that correct?

That sounds correct to me.

@trjExpensify This is due for payment

I've settled up with @Uros787. Sent you an offer to accept for C+, and @thesahindia for reporting.

Accepted, thanks!

^^ Settled!


Search from input ID only runs on input

From Bubble forum:
@kbgreenway
Hello @dambusmedia,
Love the plugin and it works great for me most of the time! Only issue I’m having is when I am trying to pull search criteria from another page by sending the query information via the URL.
For example, if I want to search for “cat” on another page, it will redirect me to the search page and send “cat” in the URL. Then, my search input box is set to pull its initial content from the URL so the search input box will say “cat”. The Search&Autocorrect has it’s Input Box ID set to the search input box’s ID Attribute. However, when the search page loads with “cat” displayed in the search input box, the Search&Autocorrect returns no matches for cat when it should show two matches. If I clear the search input box and manually type in “cat”, then the Search&Autocorrect works again.
Not sure what is causing this or if anyone else has experienced this, but any help would be greatly appreciated!

This is due to the getresults function only running on("input")


is a collapsable nav for small viewpoint on roadmap?

Turns out we added it to the roadmap. https://github.com/Shopify/Timber/pull/338


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.9 to before v5.4.180",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a9e6f83c2df199187a5248f824f31b6787ae23ae",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9fc422c9a43e3d58d246334a71f3390401781dc"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "a9e6f83c2df199187a5248f824f31b6787ae23ae",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "c9fc422c9a43e3d58d246334a71f3390401781dc",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "usb: f_fs: Fix use-after-free for epfile\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.180 by commit c9fc422c9a43e3d58d246334a71f3390401781dc, it was introduced in version v4.9 by commit a9e6f83c2df199187a5248f824f31b6787ae23ae. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000336


dan/4896 Bulk Upload Guide Updates

FRONTEND PULL REQUEST
Related Issue

resolves #4896

Changes Proposed

Add equipment_model_id and testkit_name_id to the bulk upload guide as optional fields.

Additional Information

Copy for the guide is in a doc linked in the story.

Testing

Look at it.  Click the link.

Screenshots / Demos

For large changes, please pair with a designer to ensure changes are as intended

deployed on dev7

code itself looks good! approving.
double checking some related things:

Verifying that we haven't turned on these fields in the backend, since they don't seem to be in the TestResultRow object. Let me know if I'm missing something though.
we may also need to update the static site example CSV to include these new columns.

To that first point: I could be wrong but I think these fields are being added specifically for the CSV API (for the FHIR API we are getting these fields from what we have in our database).  For the CSV API these fields should pass through to ReportStream.
For # 2 I'll put up a PR shortly.

code itself looks good! approving.
double checking some related things:

Verifying that we haven't turned on these fields in the backend, since they don't seem to be in the TestResultRow object. Let me know if I'm missing something though.
we may also need to update the static site example CSV to include these new columns.

To that first point: I could be wrong but I think these fields are being added specifically for the CSV API (for the FHIR API we are getting these fields from what we have in our database). For the CSV API these fields should pass through to ReportStream.
For # 2 I'll put up a PR shortly.

ahhh TIL about the secondary CSV endpoint. Thanks!


Linux: Exit to Main Menu always exits game completely.

With CQUI and no other mods enabled under linux, choosing to exit game to Main Menu exits game completely. If specific logs are needed, please let me know which to gather, this is consistently reproducible under Gnome/Mate XFCE/Xubuntu variants.

Sounds like a similar issue to what someone else using Windows 10 was experiencing. Could you provide the Lua.log and Modding.log files so I can compare?

Will do!
On Fri, Jun 30, 2017 at 8:21 PM, Chris<EMAIL_ADDRESS>wrote:

Sounds like a similar issue to what someone else using Windows 10 was
experiencing. Could you provide the Lua.log and Modding.log files so I can
compare?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CQUI-Org/cqui/issues/572#issuecomment-312398209, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHu9x1Eema1U_GCtb7ZAj62gdfFAZpbrks5sJZEFgaJpZM4OLJqm
.

--

QTH KORL Winter Park, Florida | Icom R75 | RFSpace SDR-IQ::Pixel Loop RF-1B
| Uniden HP2
SDR Captures/loggings posted to: https://corq.co when audio quality allows.

Actually, after disabling to test against the game without plugins, and
then enabled CQUI back, it no longer occurs.
As if the toggling off/on of the plugin resolves it. Does toggling a plugin
via steam workshop act like a manual update of the plugin, or should that
happen automatically?
Very odd. Prior to this it would exit to desktop every time. For several
weeks I've noticed this. Attached the logs anyway just in case.
On Fri, Jun 30, 2017 at 8:31 PM, L.T. Easterly<EMAIL_ADDRESS>wrote:

Will do!
On Fri, Jun 30, 2017 at 8:21 PM, Chris<EMAIL_ADDRESS>wrote:

Sounds like a similar issue to what someone else using Windows 10 was
experiencing. Could you provide the Lua.log and Modding.log files so I can
compare?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CQUI-Org/cqui/issues/572#issuecomment-312398209, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHu9x1Eema1U_GCtb7ZAj62gdfFAZpbrks5sJZEFgaJpZM4OLJqm
.

--

QTH KORL Winter Park, Florida | Icom R75 | RFSpace SDR-IQ::Pixel Loop
RF-1B | Uniden HP2
SDR Captures/loggings posted to: https://corq.co when audio quality allows
.

--

QTH KORL Winter Park, Florida | Icom R75 | RFSpace SDR-IQ::Pixel Loop RF-1B
| Uniden HP2
SDR Captures/loggings posted to: https://corq.co when audio quality allows.

Yes, resubbing is often known to fix issues. I'm glad the game seems to be playable now for you! If this issue recurs, please let me know so I can reopen this ticket

Thanks for the tip! will try that next time. Appreciate your time, have a
good night!
On Fri, Jun 30, 2017 at 8:59 PM, Chris<EMAIL_ADDRESS>wrote:

Closed #572 https://github.com/CQUI-Org/cqui/issues/572.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CQUI-Org/cqui/issues/572#event-1146801213, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHu9x_wG-N-0DV20b9wbkAD9qQ4-srPmks5sJZoBgaJpZM4OLJqm
.

--

QTH KORL Winter Park, Florida | Icom R75 | RFSpace SDR-IQ::Pixel Loop RF-1B
| Uniden HP2
SDR Captures/loggings posted to: https://corq.co when audio quality allows.


Docker client version for building the image is hardcoded

I tried to build a RancherOS image by myself following the steps in the documentation. This failed, because the docker version on my host os did not match the version of the client that is downloaded in Dockerfile.dapper, where it is hardcoded to 1.9.1. However it took me quite a lot of time to figure out what went wrong here, because the error message shows the protocol versions, not the program versions.
There build documentation does not mention that Docker 1.9 is required on the build system. Can you please either add this to the documentation or or adjust the build process to automatically install the Docker client for the version that is used on the build host instead of hardcoding 1.9.1?

The build requirements have been updated to say Docker 1.9.1.
http://docs.rancher.com/os/contributing/#building


cellxgene-schema CLI must validate ndarray size in obsm, obsp, varm, and varp

obsm (Embeddings)
The size of the ndarray stored for a key in obsm MUST NOT be zero.
obsp
The size of the ndarray stored for a key in obsp MUST NOT be zero.

varm
The size of the ndarray stored for a key in varm MUST NOT be zero.

varp
The size of the ndarray stored for a key in varp MUST NOT be zero.

I assume "a key" means any key?

I assume "a key" means any key?

Yes since this causes RDS conversion failures - https://github.com/chanzuckerberg/single-cell-curation/issues/597#issue-1842192464

Do we have an existing test case dataset for any of these?

Not to my knowledge. When I was playing around with it, I realized that it also needed to meet other anndata requirements like obsm embeddings must be the same length as obs like:
adata.obsm['test'] = numpy.zeros((adata.n_obs, 0))
adata.obsm['test'].size

@jahilton thank you for these notebooks. They have been invaluable in reproducing the errors.

@jahilton @corismall read for QA

LGTM - QA notebook


Update developer_guide.md

Update the link
https://docs.pipenv.org/ is broken

Coverage remained the same at 96.667% when pulling af51de1f982f22e55c4af6d0198b402292ac126f on pingsutw:patch-1 into a2ae7bff612bf26d0b05a54ddcfc6a400a5c8e89 on kubeflow:master.

Coverage remained the same at 96.667% when pulling af51de1f982f22e55c4af6d0198b402292ac126f on pingsutw:patch-1 into a2ae7bff612bf26d0b05a54ddcfc6a400a5c8e89 on kubeflow:master.


[Asana] Can't create a task for some projects

Extension
https://www.raycast.com/raycast/asana
Description
I don't know why but for most of my projects adding task is not working. After pressing cmd+Enter nothing happens or Raycast crashes and quits.
https://user-images.githubusercontent.com/22954960/208127203-5e77db07-96bb-42a0-af5a-562f66d810cd.mov
Steps To Reproduce

Use Create Task Command
Select project
Set Task name
Press Command+Enter

Current Behaviour
Nothing happens or Raycast crashes
Expected Behaviour
Task is created

it should be fixed in v1.45.1


Support for external agents?

I'd like to run the algorithms with an external agent where surreal doesn't have control of time (like a real robot). See Interefacing with External Agents in Berkeley's Ray library for details and an example. Is this already designed into surreal or is the concept not yet implemented?
Note: I've also created a couple of related issues in https://github.com/StanfordVL/robosuite/issues sorry if one of these are in the wrong place.

The SURREAL agent has to be "internal" now, but we will put external-interfacing on our todo list. Thanks!


Send public and private testcases for graders to view

title

Will take up this issue since it involves the grading/auto-grading system.

Addressed in #633.


Files In other Path in windows 2012 R2

I tried to install Mcollective  Server. The mcollective  startup script is searching for the rb files in program files but they are residing  in c:\programdata
E, [2017-01-12T14:15:54.090010 #276] ERROR -- : pluginmanager.rb:171:in rescue in loadclass' Failed to load Mcollective::Connector::Nats: cannot load such file -- mcollective/connector/nats.rb E, [2017-01-12T14:31:42.388235 #964] ERROR -- : pluginmanager.rb:171:in rescue in loadclass' Failed to load Mcollective::Connector::Nats: cannot load such file -- mcollective/connector/nats.rb
E, [2017-01-12T15:32:04.973901 #1712] ERROR -- : pluginmanager.rb:171:in `rescue in loadclass' Failed to load Mcollective::Connector::Nats: cannot load such file -- mcollective/connector/nats.rb

After copying over the files I am getting  Certificate Error. The  code looks for hostname$.mcollective.pem.
I, [2017-01-12T16:01:54.334402 #2808]  INFO -- : config.rb:167:in loadconfig' The Marionette Collective version 2.9.1 started by C:/Program Files/Puppet Labs/Puppet/mcollective/bin/mcollectived using config file C:\ProgramData/PuppetLabs/mcollective/etc/server.cfg I, [2017-01-12T16:01:54.334402 #2808]  INFO -- : mcollectived:63:in ' The Marionette Collective 2.9.1 started logging at info level
I, [2017-01-12T16:02:00.397256 #2808]  INFO -- : nats.rb:15:in initialize' Choria NATS.io connector using pure ruby nats/io/client 0.2.0 with protocol version 1 E, [2017-01-12T16:02:04.900737 #2808] ERROR -- : runner.rb:107:in rescue in block in main_loop' A failure occurred in the MCollective runner.
E, [2017-01-12T16:02:04.900737 #2808] ERROR -- : runner.rb:108:in rescue in block in main_loop' No such file or directory @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/MOLLECTIVE-TEST$.mcollective.pem E, [2017-01-12T16:02:04.900737 #2808] ERROR -- : runner.rb:109:in rescue in block in main_loop' C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:63:in read' 	C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:63:in ssl_context'
C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:33:in connect' 	C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/runner.rb:164:in receiver_thread'
C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/runner.rb:142:in `block in start_receiver_thread'

@farhandiwan can you confirm that prior to configuring via choria that the config files were factory default? there's some limitation in how the ini module works that makes it currently difficult for me to configure everything correctly if not.
If possible please paste here your server.cfg from that node?

securityprovider = choria
identity = mollective-test.ei.local
connector = nats
collectives = mcollective
main_collective = mcollective
classesfile = C:/ProgramData/PuppetLabs/puppet/cache/state/classes.txt
rpcauthorization = 1
rpcauthprovider = action_policy
rpcaudit = 1
rpcauditprovider = logfile
plugin.rpcaudit.logfile = C:/ProgramData/PuppetLabs/mcollective/var/log/mcollective-audit.log
factsource = yaml
plugin.yaml = C:/ProgramData/PuppetLabs/mcollective/etc/generated-facts.yaml
logfile = C:/ProgramData/PuppetLabs/mcollective/var/log/mcollective.log

The recipies  were applied  on a fresh windows  box.  The recipe  worked well on linux node.

@farhandiwan hmm, this one has no libdir at all, that seems wrong to me, it should have some libdir setting, this would be why it failed to require all the files needed.
I believe libdir would need to be set to C:/ProgramData/PuppetLabs/mcollective/plugins

@farhandiwan ok, thanks, I will have to get a windows machine up and look closer.

Thanks.
Also check the certificate read issue.
I, [2017-01-12T16:16:03.692478 #2520]  INFO -- : config.rb:167:in loadconfig' The Marionette Collective version 2.9.1 started by C:/Program Files/Puppet Labs/Puppet/mcollective/bin/mcollectived using config file C:\ProgramData/PuppetLabs/mcollective/etc/server.cfg I, [2017-01-12T16:16:03.692478 #2520]  INFO -- : mcollectived:63:in ' The Marionette Collective 2.9.1 started logging at info level
I, [2017-01-12T16:16:08.742092 #2520]  INFO -- : nats.rb:15:in initialize' Choria NATS.io connector using pure ruby nats/io/client 0.2.0 with protocol version 1 E, [2017-01-12T16:16:12.992067 #2520] ERROR -- : runner.rb:107:in rescue in block in main_loop' A failure occurred in the MCollective runner.
E, [2017-01-12T16:16:12.992067 #2520] ERROR -- : runner.rb:108:in rescue in block in main_loop' No such file or directory @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/MOLLECTIVE-TEST$.mcollective.pem E, [2017-01-12T16:16:12.992067 #2520] ERROR -- : runner.rb:109:in rescue in block in main_loop' C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:63:in read' 	C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:63:in ssl_context'
C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:33:in connect' 	C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/runner.rb:164:in receiver_thread'
C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/runner.rb:142:in block in start_receiver_thread' I, [2017-01-12T16:17:54.979857 #1320]  INFO -- : config.rb:167:in loadconfig' The Marionette Collective version 2.9.1 started by C:/Program Files/Puppet Labs/Puppet/mcollective/bin/mcollectived using config file C:\ProgramData/PuppetLabs/mcollective/etc/server.cfg
I, [2017-01-12T16:17:54.979857 #1320]  INFO -- : mcollectived:63:in <main>' The Marionette Collective 2.9.1 started logging at info level I, [2017-01-12T16:18:00.026132 #1320]  INFO -- : nats.rb:15:in initialize' Choria NATS.io connector using pure ruby nats/io/client 0.2.0 with protocol version 1
E, [2017-01-12T16:18:05.010482 #1320] ERROR -- : runner.rb:107:in rescue in block in main_loop' A failure occurred in the MCollective runner. E, [2017-01-12T16:18:05.010482 #1320] ERROR -- : runner.rb:108:in rescue in block in main_loop' No such file or directory @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/MOLLECTIVE-TEST$.mcollective.pem
E, [2017-01-12T16:18:05.010482 #1320] ERROR -- : runner.rb:109:in rescue in block in main_loop' C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:63:in read'
C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:63:in ssl_context' 	C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/connector/nats.rb:33:in connect'
C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/runner.rb:164:in receiver_thread' 	C:/Program Files/Puppet Labs/Puppet/mcollective/lib/mcollective/runner.rb:142:in block in start_receiver_thread'

The issue regarding certificates is due to this bit of code here:
https://github.com/ripienaar/mcollective-choria/blob/bc14634e57cb5a462dccd4d5e6c71f69dd0550ba/lib/mcollective/util/choria.rb#L401-L409
On Windows, the mcollective service is running as the LocalSystem user and Process.uid returns 18 for this user (or at least it does in my tests). I got around this by temporarily setting the environment variable MCOLLECTIVE_CERTNAME to the identity of the machine.
I'm not too familiar with Windows so I'm not entirely sure what the most robust way of fixing this is yet.

@dnlsng yeah I saw this too, I'll have to research a bit on whats right, or just assume the client doesnt work on windows but that would be a shame

The 2 PR https://github.com/ripienaar/mcollective-choria/pull/144 and https://github.com/ripienaar/puppet-mcollective/pull/77 should improve things a lot, client wont work on windows though after but the server should work.
Will do more testing and release it later

@farhandiwan if you grab the latest choria module and this one, it should just work, i hope 📦
client wont work on windows


Client Allocation Request for: TEST

Client Allocation Questions
Core Information

Name: TEST
Website / Social Media: TEST.COM
Region: North America
DataCap Requested: 1TiB
Addresses to be Notarized: f000000123123123123
Notary Requested: kernelogic

@dkkapur Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

testing flow - please ignore.

no problemo


Support for executables without relocation data

I can't help but notice that most of my executables that i compile from many compilers (using fpc, for example) do not have relocation data. I think it would be nice to add support for executables that don't have this.

What version of donut are you using and what parameters?

I am using the latest version with these parameters: --arch:x86 -t
--input:test.exe where test.exe is the exe without relocation data.
Le jeu. 8 juin 2023, 14 h 19, TheWover @.***> a écrit :

What version of donut are you using and what parameters?
—
Reply to this email directly, view it on GitHub
https://github.com/TheWover/donut/issues/128#issuecomment-1583128071,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7N52YHSLAD7TUC4QFQET3XKIJSLANCNFSM6AAAAAAY6ENZJM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Regenerate & Delete: Allow users to generate API tokens with the desired access

Allow users to generate API tokens with the desired access:

Regenerate :

Delete:

Hey team! Please add your planning poker estimate with ZenHub @sohel-rp @vivek-devtron


[Containerapp] Add new command az containerapp ssh

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

@panchagnula, I open a PR against Calvin's main here so @calvinsID, @haroonf, and I can coordinate our containerapp releases together


Diaphragm calculation setting doesn't work in fdscript

Issue:
FEM-Design does not respond to the analysis settings in the .fdscript file. Despite setting the diaphragm calculation to "true" in the fdscript, in FEM-Design, it remains set to "None".
https://strusoft.fogbugz.com/f/cases/131204/Diaphragm-calculation-setting-doesn-t-work-in-fdscript

Source of the issue: In .fdscript, the diaphragm calculation parameter is not a boolean, instead it is an integer, and it can take the following values: '0'= None , '1'= Rigid membrane or '2'= Fully rigid


add brotli4j native libs to [codec-http2] pom.xml

Motivation:
the brotli4j native libraries are missing from the [codec-http2] module
Modification:
added brotli4j native libraries to codec-http2/pom.xml
Result:
DataCompressionHttp2Test all tests pass.

@sullis What's your time zone?

@sullis What's your time zone?

I am in the Pacific time zone (US West Coast)

✅ ready to merge

thanks a lot


Add Discount Coupon

Is there a way to add a discount coupon. I am adding a combo widget. If someone adds the combo pack all the item is added in the cart.  I want to add the discount code at the same time.  I am using rivets-cart.min.js

Discount codes can't be added via the Ajax API, so this is outside the scope of Cart.js. Sorry!


Feature Request: More options for the Traffic Graph

The traffic graph (dashboard and dedicated page) is a quite important element to most users of a router/firewall. The following points could be improved:

The time line (scale) is missing (x-axis) - one has to hover the (moving) data points in order to check the point in time of a throughput measurement. A time scale with some timestamps should be present all the time.

The curve permanently compresses the range of the x-axis where it should only be shifted linear over time. Shifting, like a sliding window, allows easier interpretation of the current and past traffic throughput.

The frequency of new data points is a bit low. A new point every one or two seconds would allow finer resolution.

The curve itself looks quite edged (linear interpolation of data points). There should be an option to smooth the edges a tiny bit.

I know: These requirements are met by the current traffic graph of the sister project... I switched a few days ago to OPNsense because of political reasons... OPN is great an clean. But the one thing I am really missing is the kind of traffic graph. Would be very nice to add some options to the traffic graph (especially dashboard widget).

Hi @Alpha-Bravo,
Thanks for this. I am not sure we can fix them all, but these are certainly things to work on as time permits. Marking these as "help wanted", because the wish list for 18.1 is already pretty full.
Cheers,
Franco

I agree. Even in 18.7.1 it looks horrible. To me, the features mentioned by the OP are a must. It would also be nice to remove/add interfaces from each graph. It's a bit redundant to see WAN/IN and LAN/OUT since they are virtually the same. Honestly, and I hate to say this, it needs to be at least as good as the traffic graph in PFSense.

Happy to see this progress indeed.

On 23. Aug 2018, at 20:25, Ad Schellevis<EMAIL_ADDRESS>wrote:
@JesseWV if you would like start this thing moving just let us know, try to keep the pull requests focused and manageable and we'll try to guide you through the process as soon as we can.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

timeout


Editor (editor-0.8.26.js) doesn't work in Safari 9.1 (116<IP_ADDRESS>) under MacOS El Capitan

Hi guys!
It seems there is some issue with editor. It doesn't work since yesterday, if there were any updates?
Screenshots are attached
Editor is shadowed and it's script execution is stopped.

And there is some error in the debugger

In Chrome it works perfectly.

I'm running into the same problem with Safari.

whatever..


Workaround @types/qs breakage

This fixes the @types/qs breakage, where return types were recently made more specific. This caused issues where we assume it's returning 'any'.
With this, it's possible to do a rush update --full
cc @KarishmaGhiya

fyi @sadasant as this may be related to the discussion in https://github.com/Azure/azure-sdk-for-js/pull/8782#discussion_r421941059

This fixes the @types/qs breakage, where return types were recently made more specific.

The more specific return types were added to a version of @types/qs that we are not yet using and this change is so that rush update --full is free to upgrade @types/qs ?

@ramya-rao-a - exactly. This will help unblock us so we can be ready for the upgrade


Webpack optimizations

Webpack rebuilds were slow. I did a bunch of research and profiling and figured out a few ways to optimize the rebuild times:

Profile stats with webpack --config webpack/dev.config.js --profile --json > stats.json and http://webpack.github.io/analyse/. This led to prefetching base.scss which really cut down build times (surprisingly)
I scanned the modules in the profile and saw that we were pulling in packages we weren't using, like all the components of react-bootstrap. This is because webpack 1 doesn't understand ES6 module syntax. So import { Nav } from 'react-bootstrap' imports all of react-bootstrap. I believe webpack 2 fixes this, but we aren't using it. So instead we do import Nav from 'react-bootstrap/lib/Nav'
I removed the redux devtools from our dependencies since we just use the browser extension anyway and so there's no reason to build it and its dependencies.
Instead of excluding node_modules from babel-loader, I told it to only include src. This probably didn't help much, but it was recommended somewhere.
The big change is adding in webpack's DllPlugin. I experimented with a bunch of ways to separate out our vendor code and not have it rebuild, and this seems to be the way to do it (not CommonsChunkPlugin). Essentially you compile a bundle for your vendor files separately and just reference it in your main webpack build. This introduces a new build step npm run webpack-dll everytime a new dependency is added (and those dependencies should also be added to webpack/dll.config.js. But the rebuild times are worth it.

I'm now seeing webpack builds taking between 400ms and 2s (typically around 1s I thnk), down from 3-6s (typically 4.5s).
So after merging this PR, to get started, run:
npm install
npm run webpack-clean-cache
npm run webpack-dll

Then do your dev server as normal. For me, that's in two separate terminal windows:
npm run start-dev
npm run watch-client

Note I ask you to npm install since I updated hard-source-webpack-plugin. I didn't add any new dependencies.

This also pointed out that one of our dependencies is pulling in all of lodash. :(

This will also have implications for the client/production deploy since I modified Html.jsx to include the scripts differently but I didn't test it

ping @vlandham

thanks for all that work @pbeshai !
i thought we were getting rid of lodash? i can work towards removing it if we still are using it somewhere.
Also, looks like our datepicker now no longer requires jquery - so we could update and remove that? https://github.com/airbnb/react-dates/issues/39

We did get rid of lodash, but some of our dependencies are using it. :( and jquery doesn't show up in the build right now, so I'm not sure. but we should still update that date plugin anyway.


TileImage/tileLoadFunction: (slow) sequentially tile loading / pause between tileloadend/start

Hello!
I'm not sure if this is a bug or i'm the first one who cares about that. :)
Describe the bug
When loading tiles with tileLoadFunction, there is a variable "pause" between two tiles (tileloadend and the next tileloadstart).
And because the tiles are loaded sequentially, it takes "too long" to render a layer.
I googled a lot and didn't find an answer or how i can change this behavior.
To Reproduce
See console output on https://jsfiddle.net/hdkpvrac (zoom in)
my browser: Chrome/85.0.4183.123
[3, 8, 9],<PHONE_NUMBER>154, "tileloadstart"
[3, 8, 9],<PHONE_NUMBER>154, "tileloadend"
"pause was (ms)", 41
[3, 8, 10],<PHONE_NUMBER>195, "tileloadstart"
[3, 8, 10],<PHONE_NUMBER>195, "tileloadend"
"pause was (ms)", 27
[3, 8, 11],<PHONE_NUMBER>222, "tileloadstart"
[3, 8, 11],<PHONE_NUMBER>223, "tileloadend"
"pause was (ms)", 23
[3, 8, 12],<PHONE_NUMBER>246, "tileloadstart"
[3, 8, 12],<PHONE_NUMBER>247, "tileloadend"
"rendercomplete, pause sum (ms)", 710

Sure, you could say that's not that much, but if you have multiple layers with many tiles, it adds up to a non user-friendly behavior.
Expected behavior

Faster tile loading. :)
There should'nt be a pause between two tiles (?)
async/concurrent tileloadstart

Thanks for your time. :)

I've seen this too. Needs fixing

OpenLayers uses a per-map tile queue, with a default total of 16 parallel tile loads. If you have a few layers that load slowly, the tile queue will be saturated so other layers won't load fast.
You can configure the map with a higher value for maxTilesLoading, e.g.
new Map({
  maxTilesLoading: 256
});

OpenLayers uses a per-map tile queue, with a default total of 16 parallel tile loads. If you have a few layers that load slowly, the tile queue will be saturated so other layers won't load fast.

Thanks for the hint, but this doesn't change anything in my example:
https://jsfiddle.net/1nhw8aec
🤷♂

here is an example which shows the sequential loading behavior in a better way, i hope. :)
https://jsfiddle.net/jh0a1yuw/
Why is the loading queue of openlayers waiting for one tile before triggering the next one, even if the main thread is idle?
The "setTimeout" in the example above returns immediately and i would expect that openlayers proceed with the next one, not blocking the queue. (the main thread is idle ...)

The problem with your example code is that the url https://xyz is the same for all tiles. That url is used as tile unique key for the tile queue. So make sure the tile url is unique for each tile, e.g. by changing it to https://{z}/{x}/{y}.
I have applied this change to your example, and also changed your test layer so you can see on the map when a tile is loaded: https://jsfiddle.net/xac3q84n/2/

So make sure the tile url is unique for each tile, e.g. by changing it to https://{z}/{x}/{y}.

Woah, thanks man!
I didn't pay much attention to the "url" because in my case its just a "dummy", "tileLoadFunction()" is doing everything (build an url and request).
Now i'm setting just the "dummy" url to "https://{z}/{x}/{y}" and all the latencys are gone, all "tileloadstart"s are triggered at once.
Did i overseen it in the manual? If not, maybe a hint when using tileLoadFuntion is necessary to avoid such "useless" tickets. 🙈
Thanks!

Increasing the maxTilesLoading value helped me. Thanks @ahocevar


Hexi is super awesome. Is it safe to use?

Alright, I know GitHub issues are not typically meant to be used for such comments, but the README said "The Issues page is is Hexi's friendly chat room" ... so, here goes.
I am evaluating my options for HTML5 game development and Hexi is exactly what I was looking for.
I found out about it through your learningPixi repo, and my first concern about Pixi was that it only handles rendering and that the API is too verbose, so Hexi solves exactly these issues for me by smartly simplifying the APIs, and bringing more modules on board for sound, tweening etc. A really solid concept.
My only concern with Hexi, is that it seems to be a one man show, which makes it fragile. I guess it can be a lot of work to keep it up to date with each update of the libraries it encapsulates.
Also, I just noticed there is not much activity since 2016, judging by the code frequency graph... is it because its super stable?
Any words of reassurance on that subject? 🤞

No! 😄
I do not recommend using Hexi for any critical production work.
It needs many more active volunteers who can help with maintenance, and it would need to reach a stable version 1.0 before I could consider recommending its use for production.
Although I use Hexi regularly in my day job (and, yes, I think it's awesome too!!), and it seems to be fairly bug free (?), I don't have enough time at the moment to do the regular weeding that it needs.
It probably needs another 3 months of full time work to get it up to what I would consider production standard.
When I, or a team of dedicated volunteers, is able to do that work and I feel Hexi is ready, I will let everyone know. 😄

Hmm.... that is indeed disappointing...

I already commented some of your post ^^. I could help you to do that. Feel free to add me to the project i will try my best to contribute on it


add Xinfernece runtime for huggingface LLM

/kind feature
Describe the solution you'd like
Hope add https://github.com/xorbitsai/inference as the kserve huggingface LLMs serving runtime

+1

Is it supported in HuggingFace?

Oh, hi @terrytangyuan , xinference is a inference platform which integrated transformers, vllm, and llama.cpp as engines, it’s not directly supported by huggingface.

I see. @jaffe-fly Could you update the title and description to reflect that?

+1


ARTEMIS-163 Simplification of the native layer

This is simplifying the native layer:

no more mallocs after initialization on the native layer (except to new buffers when out of the pool)
adding sync calculation for when initializing the journal

I'm already working on 4096 but I don't want to hold this initial commit for now. I will send another PR over the next few days.
What was done as part of this:

The native layer is now a simplified native implementation. In theory much easier to implement.

The native layer won't call any mallocs for io_submit though, get_iocb is a function that will have a cirtcular cache of objects that will be reused on writes. we used to malloc before every write submit

I have moved stuff around to make it easier to understand (for instance separated packages for nio and aio under the journal)

merged AIOCallback and a useless class IOSubmit into a single IOCallback

added a test on create to sync test performance

The callbacks are also reused now through a circular log

Everything else stayed the same, the whole testsuite is passing and I have executed extensive tests on this (through manual testing)

What was done as part of this:

The native layer is now a simplified native implementation. In theory much easier to implement.

The native layer won't call any mallocs for io_submit though, get_iocb is a function that will have a cirtcular cache of objects that will be reused on writes. we used to malloc before every write submit

I have moved stuff around to make it easier to understand (for instance separated packages for nio and aio under the journal)

merged AIOCallback and a useless class IOSubmit into a single IOCallback

added a test on create to sync test performance

The callbacks are also reused now through a circular log

Everything else stayed the same, the whole testsuite is passing and I have executed extensive tests on this (through manual testing)

its a big PR but looks fine form what ive checked, will merge


Added the 'spo serviceprincipal grant add' command solving #647

Added the 'spo serviceprincipal grant add' command solving #647

Merged manually

Hi @waldekmastykarz,
During I'm attempting to make the coverage of spo mail send cmdlet, I can see an error of coverage.
spo serviceprincipal grant add
       "before all" hook:
     TypeError: Attempted to wrap ensureAccessToken which is already wrapped
      at checkWrappedMethod (node_modules/sinon/lib/sinon/util/core/wrap-method.js:39:21)
      at wrapMethod (node_modules/sinon/lib/sinon/util/core/wrap-method.js:87:13)
      at stub (node_modules/sinon/lib/sinon/stub.js:72:44)
      at Sandbox.stub (node_modules/sinon/lib/sinon/sandbox.js:291:33)
      at Context.<anonymous> (dist/o365/spo/commands/serviceprincipal/serviceprincipal-grant-add.spec.js:22:15)
  --------------
  Error: Stack Trace for original
      at wrapMethod (node_modules/sinon/lib/sinon/util/core/wrap-method.js:112:30)
      at stub (node_modules/sinon/lib/sinon/stub.js:72:44)
      at Sandbox.stub (node_modules/sinon/lib/sinon/sandbox.js:291:33)
      at Context.<anonymous> (dist/o365/spo/commands/mail/mail-send.spec.js:21:15)

I made no change on the spec of this cmdlet and I just made a git pull upstream dev to be ensure that I have the latest version of dev branch.
That's normal ?

@Laul0 , before all hook might fail because tests suite executed before the spo serviceprinciple grant  tests to execute wrapped the ensureAccessToken and never restored its state. Could that be the issue?

Hi @VelinGeorgiev, I didn't work on this cmdlet, I just report when I'm testing my cmdlet (spo mail send) coverage this error appear. I have the latest version of the dev branch (git pull upstream dev).
You can try directly from the dev branch by test the entire solution.

I will run it in few hours and let you know. Meanwhile, you can commit your latest code so I can have a look in case it is not the Dev branch

Sure, I'm not working on the dev branch. I'll do it in few hours

I'd expect tests for spo mail send to be running before spo serviceprincipal grant add so if the latter is throwing issues with beforeAll trying to wrap something that is already wrapped, the issue is likely with spo mail send tests which don't restore objects to their default state.

Yes, tested my Dev branch and it is working as expected. Have to be something with the mail tests.

Ok. We'll see that together Tuesday ;)


Use generic writer instead of PathBuf.

Fixes #2.

@goddtriffin yes that worked perfectly. Thanks for the quick update.


Entities unavailable followed by apparent reset

Version of the custom_component
V0.4.4
Configuration
configured through UI
Describe the bug
All sensors seem to become unavailable on occasion. Once they become available again, the current photo resets to the same one every time. Sometimes it seems like opeing the entity/device page in the frontend can trigger this. The debug logs do not seem to show any activity during the event,yet the device logs do as in screenshots attached.
Use case: I'm using this intergration with wallpanel to have a screensaver photo that updates daily at 04:00 via a service call automation. This seems to work perfectly, but then at some stage during the day the displayed photo reverts to the original one. This hapened with the previous version as well as latest.
Debug log

2023-03-30 03:29:26.838 DEBUG (SyncWorker_6) [googleapiclient.discovery] URL being requested: GET https://photoslibrary.googleapis.com/v1/mediaItems/AMrVKRFzNtwJT4tchGK9ypqykPAvXAjWb1Z06JRjxrMLhBiQBCA-KpEabkpgvQom6CyfoZX9P5vJbjhR4xDLs3UV2WYmcoqLDQ?alt=json
2023-03-30 03:29:43.202 DEBUG (SyncWorker_3) [googleapiclient.discovery] URL being requested: GET https://photoslibrary.googleapis.com/v1/mediaItems/AMrVKREQ8Oog8B1mt0Uqg3e9d7_3yqQJorVfF2Y-tbQr0nGZGYbYl10DKS2VNwQkok5CkjndYjDI?alt=json
2023-03-30 03:29:52.456 DEBUG (SyncWorker_4) [googleapiclient.discovery] URL being requested: GET https://photoslibrary.googleapis.com/v1/mediaItems/AMrVKREg4SH2t61HgJRPf0-y5nX_2gS8mrx3oFwBa_SfVlvsdwLkPkJthi8Az6mJfxWqtYIMs4KglLa0kZdqWP5sMl9LMDqOvw?alt=json

Add your logs here.

Thanks for the work on this integration! Having a curious issue as outlined above. The associated entities, and thus the displayed picture, seem to reset multiple times a day. Any ideas as to how I might better debug this issue?

Perhaps worth noting: when I try to configure the settings from the integrations page, album selection works fine, but the settings option seems like it's missing something from the description? The only option available is metadata. The update interval can of course be set through the provided entity but it reads like a similar option should display here?

Hmm, I've seen it happen once or twice as well. It looks like there is a moment where Home Assistant marks it as unavailable, but I can't really seem to figure out what's the trigger. I'll do some debugging to find it. Loading the device page requests an image to be shown as thumbnail for the image, that could trigger state updates, so my guess is that's the key to the issue.
For the last issue with the options, I'll change that, it's a left over from when the configuration was not per album but for the entire integration.

Thanks for the attention on it. It seems to happen quite regularly on my setup, every few hours. I wonder is there a connectivity issue my end but whatever the cause, is there any way for the entity states to persist after an unavailability event?
Or perhaps an option to have it not poll for updates unless requested? It strikes me that (just in my use case), the integration should request the image at 4am and the image would remain locally until requested again?
It makes sense about the thumbnail triggering it - on that note I have noticed quite a lag between the thumbnail updating after an image update, while testing different configurations of how often wallpanel should check the entity for updates.
Forgive me if I'm talking nonsense, just thinking out loud about it...

Feel free to think along, it's always helpful to read how others interpret what you made!
Did some debugging over night, it probably has to do with Google's OAuth token expiring in combination with the way I'm currently handling adding new albums, so I'll need to make some changes there.
The integration already tries to reduce reloading data as much as possible, in general it will only update data if you actually request an image. So if the interval is one minute, but you don't have any dashboards opened nothing will happen right up to the moment you reopen a dashboard (or look at the device page, due to the thumbnail that is shown there).

thanks @Daanoz for fixing this. Updated to the latest now and looking forward to trying it out.

My issue appears to be solved. Thanks so much.
The only other query I'd have on it is that after a home assistant restart, that same photo is recalled, which makes me think the initial photo selection doesnt adhere to the "random" setting. But it's an easy workaround to call a new photo after a restart via automation so it's not a huge issue, and perhaps by design.
Thanks again.

Yeah, that's default behavior, it actually loads whatever photo you have set as cover photo in Google Photos.

ah, thanks for clarifying that! I hadn't realised. That's perfect I can just set a new cover photo, as i've grown to resent the previous one during troubleshooting 😄


Buddy Nim Java Implementation (Competitive Prorgamming, Game Theory)

Have you read the Contributing Guidelines on Pull Requests?
Yes, of course!
Description
This is the java implementation of the famous CodeChef problem called Buddy Nim which is solved using Game Theory.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #7204

Please review @ankitaggarwal23

Hi @ankitaggarwal23, I'd be grateful if you could provide your feedback on this. Thanks!


Remove node 0.12 for tests

Perhaps pulling the trigger a bit early, but we only really support this for running tests and that seems silly for a build about to exit LTS.

Coverage remained the same at 97.073% when pulling db3d37d47d868f6b4b649754ca0f3a9eaa3c2893 on remove-node-oh-dot-twelve into abff1a61d2fcd9ddcbdbbbab73f878d329668da5 on master.

Seems ok to me.


Beta Vanilla preset doesn't use vanilla surface builders or vanilla surface builders are unused at all

You can see this issue if you look at a badlands biome in the Beta Vanilla preset. I'm not sure if this is to do with the preset itself or the fact the generator doesn't use vanilla's surface builders at all.

I'm aware. This is partly why I am not supporting vanilla biomes and only added a way to generate most of them in a world after many requests.
The vanilla surface builder was made even more tightly integrated with the vanilla noise methods with 1.19, so I could not properly get it to work with the modded terrain gen without significant issues.


Add first pass at Makefile

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Trying out a Makefile for common tasks
@softprops what do you think? A starting point, need more work but something to discuss. 👍 Ref: https://github.com/rusoto/rusoto/issues/1175 .

Since this is scheduled for Rusoto 0.38.0, I won't be working on this until Rusoto 0.37.0 issues are completed. If someone else would like to finish up this work that'd be 💯 . Otherwise I'll get back around to it after Rusoto 0.37.0.

👍 got the build working across stable, beta and nightly channels. Testing failures during make commands next.

Showing a Make command failing causing the job to fail:

Waiting for the check_integration_test to pass on Travis and this is good to go. 😄

@softprops can you take a look at this? I think it's ready to go. 👍


README - Incorrect UID/GID in Security

README says : Postfix will run the master proces as root, because that's how it's designed. Subprocesses will run under the postfix account which will use UID:GID of 100:101. opendkim will run under account 102:103.
But in reality, opendkim run under account 103:104
I'm using the 4.0.2 release (boky/postfix:latest)

Hi,
I will check it out, might have to do something with different distributions.


[Counting] Limiting Edit/Deletes w/ Mute

Feature Description
It would be nice to be able to limit the quantity of edits individuals can make since their last count.
Alternatives Considered
instead of limiting the quantity of edits, maybe an amount of time they have to wait between edits or they get a mute. Could also have the mute time different for edits versus wrong count.
Additional Context
We have one individual who floods the counting channel with edits and deletes. It would be nice to limit their/anyone's ability to do so many edits in a short period of time.

Taking out other members has been fun lol; However, it's getting to the point there is more edits/deletes than actual counts at times...

#40 makes a valid point that users could still delete messages if they were muted... so maybe too many edits/deletes could result in a set time of read-history privileges revoked instead of just a mute?


Feature/f2018071301 add option for warnings per pr review

Add option to limit comments per PR review
Create separate PR reviews depending on the comments to post

Fixes #302

@mmozuras @mknapik could someone review this PR, will appreciate it.
We need this, cause currently pronto is 💥 when trying to post comment to GHE

@mmozuras what do you think of this? Is it good and whether could be reviewed again / merged soon?

@mmozuras what do you think, can we 🚢this soon, we need it when we have bigger PRs.

@dimitrovv let's get this PR cleaned up so there aren't conflicts and I can give it a final once over and merge.

@doomspork, thanks, already done, please review when possible, we need this

@prontolabs/core any final thoughts before I merge this?

Is it possible to disable the comments but fail the check? If I set the max_warnings to 0, the check passes even if there are rubocop errors.


added prims algorithm issue-3304

Have you read the Contributing Guidelines on Pull Requests?
yes i have
Description
prims algorithm is being added to cpp ds files
Prim's Algorithm is used to find the minimum spanning tree from a graph. Prim's algorithm finds the subset of edges that includes every vertex of the graph such that the sum of the weights of the edges can be minimized.
time_complexity_O(ElogV) where v no of vertices and e no of edges
Checklist

[yes ] I've read the contribution guidelines.
[yes ] I've checked the issue list before deciding what to submit.
[ yes] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#3304  added code to this issue please kindly verify

please review my pr and merge prim's algorithm
@bhav09 , @siddharth25pandey @HarshCasper , @ankitaggarwal23

I have added multi line commands added description and all the others are done. please review

@siddharth25pandey i have made the changes and updated the code please verify

@kavyasree-123 Please check carefully, what I wrote earlier. Have a look here+
Please update the Readme file details

hello i have updated readme file please verify @siddharth25pandey

@siddharth25pandey Looks good to me

@all-contributors please add @kavyasree-123 for her code

thank you so much for all mentors..


Add filewatcher package

What does this PR do?
This commit adds a filewatcher package, it is a slitl modified version of libbeat/cfgfile/glob_watcher that instead of watching glob patterns, it watches for specific files.
Why is it important?
Different projects require watching for files, so it makes sense to have it on this shared repository.
Checklist

[ ] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added an entry in CHANGELOG.md

## Author's Checklist
Related issues

https://github.com/elastic/beats/issues/34408

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-02-03T10:18:19.726+0000

Duration: 3 min 41 sec

Steps errors
Expand to view the steps failures

Mage check

Took 0 min 1 sec . View more details here
Description: mage -v check

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.


Fix typos in README

Also enabled TOML syntax highlighting for TOML snippets.

I was going to say that "useable" is preferred to "usable", but Merriam-Webster has the former as a less common variant. For whatever reason, I didn't realize that TOML was supported as a "language" in GFM.
Thanks! Merging.


6.0+ NullPointerException when resolving

A repo whose configurations resolved correctly under gradle-6.0-20190910220033+0000 now fails with the below error in:

6.0
6.0.1
6.1-20191021220025

Expected Behavior
Configurations should resolve correctly.
Current Behavior
org.gradle.api.internal.tasks.TaskDependencyResolveException: Could not determine the dependencies of task ':conjure-java:compileJava'.
...
Caused by: org.gradle.api.artifacts.ResolveException: Could not resolve all dependencies for configuration ':conjure-java-core:compileClasspath'.
...
Caused by: java.lang.NullPointerException
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.SelectorState.hasStrongOpinion(SelectorState.java:345)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.VirtualPlatformState.getForcedVersion(VirtualPlatformState.java:67)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.VirtualPlatformState.isGreaterThanForcedVersion(VirtualPlatformState.java:153)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.selectors.SelectorStateResolverResults.isVersionAllowedByPlatform(SelectorStateResolverResults.java:90)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.selectors.SelectorStateResolver.selectBest(SelectorStateResolver.java:79)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.ModuleResolveState.maybeUpdateSelection(ModuleResolveState.java:372)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.performSelection(DependencyGraphBuilder.java:290)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.performSelectionSerially(DependencyGraphBuilder.java:271)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolveEdges(DependencyGraphBuilder.java:247)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.traverseGraph(DependencyGraphBuilder.java:186)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolve(DependencyGraphBuilder.java:145)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DefaultArtifactDependencyResolver.resolve(DefaultArtifactDependencyResolver.java:123)
	at org.gradle.api.internal.artifacts.ivyservice.DefaultConfigurationResolver.resolveGraph(DefaultConfigurationResolver.java:175)
	at org.gradle.api.internal.artifacts.ivyservice.ShortCircuitEmptyConfigurationResolver.resolveGraph(ShortCircuitEmptyConfigurationResolver.java:86)
	at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.resolveGraph(ErrorHandlingConfigurationResolver.java:74)
	... 168 more

Context
PR: https://github.com/palantir/conjure-java/pull/669/files
Failure: https://circleci.com/gh/palantir/conjure-java/6597?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
Additional notes
This error seems to come from the virtual platform alignment logic.
Note that this repo uses gradle-consistent-versions which automatically creates virtual platforms around modules matching globs found in versions.props. It then adds require constraints on those virtual platforms to enforce minimum versions.
For example, com.fasterxml.jackson.*:* = 2.9.9 creates a virtual platform com.fasterxml.jackson._:_ that captures all components matching the glob, and adds a constraint on it.
This functionality works fine on all other public and internal repos, including on gradle 6.
Steps to Reproduce
Upgrade gradle wrapper to 6.0 or 6.0.1
Your Environment
Build scan URL: https://scans.gradle.com/s/pycj2dg2w6j4w

There was a basic issue with accessing a nullable field ... fix scheduled for 6.2.
Thanks for the report.


Rajatsingh-askaquestion

added a new idea in Idea.md

For the website: Create a page titled 'Ask a Question' where individuals can submit inquiries for the next upcoming guest. This page will serve as a platform for engaging with the forthcoming podcast guest. It will feature the upcoming podcast guest along with a countdown timer to the episode's airing. Below, there will be a comment section where users can share their questions, like and reply to others' comments. The most popular comments will rise to the top, aiding the host in selecting the most asked questions for the podcast.

this looks good!


Update/Add subscribe links for newsletter+magazine

 Subscribe landing page

@Shinsina - this is what they asked for, but ultimately not what they need.  We'll be building out a subscribe landing page so they can have multiple print links (renew vs subscribe), as well as multiple newsletter links and social links.  Otherwise it starts to become a mess in the navigation.


Ollama stops generating output and fails to run models after a few minutes

Hi, I'm running ollama on a Debian server and use the oterm as the interface.
After some chats (just less than 10 normal questions) the ollama fails to respond anymore and running ollama run mixtral just didn't success (it keeps loading).
I noted that the same issue happened, like in #1863 . Is there a solution at the moment? Also, I'm not the administrator of the server and I even don't know how to restart ollama 😂. The serve process seems to runs as another user named ollama. Can anyone tell me how to restart it?
To developers: I can provide some debug information if you need, just tell me how to do it.
Thanks :D

The model I'm running include mixtral:latest and wizard-math:70b.
I have access to an NVIDIA A100 PCI-e 80GB and the inputs are all simple sentences (no more than 100 words) and I ensure that nobody else is using the GPU (I see from nvitop).

Hi @TheStarAlight, would it be possible to share which version of Ollama you are running? ollama -v will print this out. Thanks so much, and I'm sorry you hit this issue

Sure! The ollama version is 0.1.20, just installed three days ago via the shell script. Please tell me if you need more information :)

Would it be possible to test with the newest version 0.1.22, which should fix this? https://github.com/ollama/ollama/releases/tag/v0.1.22
You can download the latest version of Ollama here: https://ollama.ai/download
Keep me posted!

Is this a dupe issue of #1458 ?
Happened to me too on 0.1.22 with mistral on MacOS. Will post again if I can find a way to reproduce.

@glorat I think so, it seems this problem happens on all platforms (linux, macOS and WSL).

@jmorganca I'm sorry that I'm not the administrator of the server and the administrator has not responded to my request😂. I'll try it on my own computer (but it can only run <4b models, even the mistral got very slow after the first evaluation) before the ollama on the server gets updated.
Btw, how can I restart the ollama server process😂? It is started by the user ollama and I cannot stop it without administrator privilege. The process has been hanging on the server for a few days and I just cannot find a way to stop it.
Thank you!

@jmorganca I can confirm that my memory issues have seemed to gone away with my stress test. https://github.com/ollama/ollama/issues/1691 Other issues have surfaced, but I think the ollama version 0.1.22 is a winner.

I'm seeing this behaviour on 0.1.22 too
After a few interactions (in this case codellama 70b) the API stops responding to ollama-webui and "ollama run codellama:70b-instruct-q4_K_M"   just shows the loading animation and never starts.
journalctl -u ollama  doesn't show any errors, just the last successful calls, is there any way to see more detailed logs?

I have the same issue, running version 0.1.22 with mistral

I am experiencing the same issue while running the technovangelist airenamer on version 0.1.23 with any llava. It functions initially but then hangs after a few minutes, causing the CPU usage to reach 100%. Consequently, I am unable to run any models. My system configuration is as follows:

Ubuntu 22.04
2x Nvidia 4090 GPUs
512GB RAM

@jmorganca I tried the new version (0.1.22) of ollama, and broke the ollama on two separate servers with two identical inputs 😂, the problem still exists. However, I notice that the problem occurs when the context gets a bit long (~1600 Chinese characters, 7 prompts). Would it be the problem?

@jmorganca I tried the new version (0.1.22) of ollama, and broke the ollama on two separate servers with two identical inputs 😂, the problem still exists. However, I notice that the problem occurs when the context gets a bit long (~1600 Chinese characters, 7 prompts). Would it be the problem?

I should have illustrated it more clearly. I'm using ollama-webui and qwen:72b (this time a different model), and I forwarded the 11434 port from the remote server for my local webui to access. After the problem happened, I saved the previous chat history and switched to another server, then tried to continue the chat before using the same prompt which caused the problem in the previous server, and it just stuck in the middle as well, just after a single evaluation ...

I am having the same issue with latest version 0.1.24. I works for a few minutes then eventually starts hanging on every request.

I'm seeing this on 0.1.24 as well.  How far back should I rollback in the interim?  Anyone know when this was introduced?

Sorry this is still a problem – what kind of prompt is being sent to the model – is it the same prompt over and over again, or a different one? Thanks!

Sorry this is still a problem – what kind of prompt is being sent to the model – is it the same prompt over and over again, or a different one? Thanks!

I am sending the same preprompt with different user message, one after another (about every 1-2 second) using llama:17b. It crashes 100% of the time within about 10 minutes.

I worked on ollama v0.124 on "mac m3 max 64gb".
The model worked with two models, mistral:latest and openhermes:latest, and after performing the same task several times, the CPU usage increased to 99% and stopped.
I confirmed that it was working with the GPU before the operation stopped.
Before checking the github issue, I thought it was a problem that only occurred on a specific OS (Mac silicon), but it seems to be a problem that occurs regardless of platform.

Sorry this is still a problem – what kind of prompt is being sent to the model – is it the same prompt over and over again, or a different one? Thanks!

I worked on ollama v0.124 on mac m3 max 64gb
The model worked with two models, mistral:latest and openhermes:latest, and after performing the same task several times, the CPU usage increased to 99% and stopped.
I confirmed that it was working with the GPU before the operation stopped.
Before checking the github issue, I thought it was a problem that only occurred on a specific OS (Mac silicon), but it seems to be a problem that occurs regardless of platform.

Sorry this is still a problem – what kind of prompt is being sent to the model – is it the same prompt over and over again, or a different one? Thanks!

@jmorganca Hi, thank you for your attention. I was just doing regular chats using ollama-webui (just like using ChatGPT). But now I cannot reproduce my previous chat anymore, I just had a chat with qwen:72b with longer than 2000 Chinese characters and the problem seemed gone away. But one thing is for sure, in my previous situation (ollama 0.1.22):

I should have illustrated it more clearly. I'm using ollama-webui and qwen:72b (this time a different model), and I forwarded the 11434 port from the remote server for my local webui to access. After the problem happened, I saved the previous chat history and switched to another server, then tried to continue the chat before using the same prompt which caused the problem in the previous server, and it just stuck in the middle as well, just after a single evaluation ...

it seemed that this chat was "poisonous" and the next prompt would crash every ollama server (at lease my 2 servers) in the first run. I'll comment if I find another similar occasion :D

seems we are faceing the same problem in ubuntu, no matter docker env or directly deploy ollama service , after we call the ollama http endpoint serval times, ollama http service will be hang up.

Is there a reproducable way to reproduce the issue? Or if is there any way that we save the verbose log?

I think I'm running into this issue as well.

I am running on the same issue, using mistral with a pre-prompt with a Mac M1 chip. After a couple of generation, the server will not respond until I kill my request

We encounter the same problem on ubuntu 20.04.6 LTS.

I was able to fix this issue by removing the JSON formatting parameter for /api/generate calls

Have the same problem, I'm on mac M2 running ollama desktop version 0.1.27
Using gemma:7b-instruct-q6_K
First boot is run, doing some curl test just to make sure it works fine. But after idle whenever sending curl again when the model boot when offloading to metal, it hang and restarted my Macbook. Its happening all the time.
Can somebody shed some light, should I uninstall and download a new Ollama or is there any setting that can fix this issues?
PS:
@justinwaltrip on Ollama desktop how to remove the JSON formatting?

We are experiencing the same issue on 0.1.28, using official Docker image on Ubuntu 22.04 with 8x RTX A40000.
Running llava:34b with images as part of the request
Will successfully process infrequent requests than suddenly hang on some request and be unresponsive to request until container is restarted.
ollama responds to health checks.

I was just watching this as it hit the issue.
CPU of 1 core hits 100%.
It will just hang here now until I restart the container. This is the output of docker logs ollama
encode_image_[GIN] 2024/03/08 - 06:09:12 | 200 | 19.031746157s |      <IP_ADDRESS> | POST     "/api/generate"
time=2024-03-08T06:09:13.001Z level=INFO source=dyn_ext_server.go:171 msg="loaded 3 images"
[GIN] 2024/03/08 - 06:09:26 | 200 | 18.617710773s |      <IP_ADDRESS> | POST     "/api/generate"
time=2024-03-08T06:09:49.931Z level=INFO source=dyn_ext_server.go:171 msg="loaded 3 images"
[GIN] 2024/03/08 - 06:10:04 | 200 | 14.109569108s |      <IP_ADDRESS> | POST     "/api/generate"
time=2024-03-08T06:13:45.049Z level=INFO source=dyn_ext_server.go:171 msg="loaded 3 images"
[GIN] 2024/03/08 - 06:13:58 | 200 | 13.486728309s |      <IP_ADDRESS> | POST     "/api/generate"
time=2024-03-08T06:14:55.013Z level=INFO source=dyn_ext_server.go:171 msg="loaded 3 images"
[GIN] 2024/03/08 - 06:15:07 | 200 | 12.661186052s |      <IP_ADDRESS> | POST     "/api/generate"
time=2024-03-08T06:16:47.278Z level=INFO source=dyn_ext_server.go:171 msg="loaded 3 images"

nvtop:

%
htop

@justinwaltrip on Ollama desktop how to remove the JSON formatting?

@antonsapt4 Removing the json format param appears to work without issues for me.
Issue may be related to #1910

Note: I don't use "format": "json" and have this issue..

I also have this issue on an M3 Max.  It seems to be somewhat random, but tends to happen more quickly with larger model or larget prompts.  For example, with one model, including only one image per prompt works consistently, but including two per prompt will trigger this issue after some runs...  With a larger model, it happens even with only one image.

#1863 and this seems to be the same issue.

Yes, looks to be the same issue!
🤞 that https://github.com/ollama/ollama/issues/2225 is the resolution!

Even in Ollama version 0.1.30, Japanese text generation stops. I've tried it once with the lightweight "mistral" and three times with "dolphin-mistral" (all 4q), and in total,  at the point of failing generation,  throwing all the input and output characters into the token counter, it stops around 3400-3600 tokens. It feels like it hangs up after generating longer texts for about 6-9 turns (Mac Sonoma14.4.1, 64GB). P.S. using terminal with this experiments, but using PageAssist webui also the same issue occures.

Hi all, this should be fixed in 0.1.31 (hanging when unicode characters are in the prompt). Further fixes for hanging are also in 0.1.32 - stay tuned!

running the 0.1.32 and the issue still persists. using CPU AVX on Debian 12 with llama3 model, gets stuck before my proxy times out after 60 seconds, reloading the page and typing the query again fixes it but it is very annoying

Currently running Ollama 0.1.41, this problem still persists.

@NikitaDeveloperAI this problem may hardly get a universal fix as it's like a whack-a-mole game.
In our case, we stopped using the format='json", and explicitly wrote a prompt that output in the exact json structure we want.
For now, that appears to work with some level of predictability and consistency. Testing it more, but so far, that approach doesn't cause hanging issues with Ollama.


Doesn't generate the file.

The button is present. But after I press it it shows like a quarter of circumference of progress and stops. No file in the destination folder.

[Message:   BepInEx] BepInEx <IP_ADDRESS> - DSPGAME
[Info   :   BepInEx] Running under Unity v2<IP_ADDRESS>89476
[Info   :   BepInEx] CLR runtime version: 2.0.50727.1433
[Info   :   BepInEx] Supports SRE: True
[Info   :   BepInEx] System platform: Bits64, Windows
[Message:   BepInEx] Preloader started
[Info   :   BepInEx] 1 patcher plugin loaded
[Info   :   BepInEx] Patching [UnityEngine.CoreModule] with [BepInEx.Chainloader]
[Message:   BepInEx] Preloader finished
[Message:   BepInEx] Chainloader ready
[Message:   BepInEx] Chainloader started
[Info   :   BepInEx] 2 plugins to load
[Info   :   BepInEx] Loading [DSP Star Sector Resource Spreadsheet Generator <IP_ADDRESS>]
[Info   :DSP Star Sector Resource Spreadsheet Generator] Will use spreadsheet path "E:\LLL\Docs\DSP_Star_Sector_Resources_${seed}-${starCount}.csv"
[Info   :DSP Star Sector Resource Spreadsheet Generator] Initialization complete.
[Info   :   BepInEx] Loading [Copy Inserters Plug-In <IP_ADDRESS>]
[Message:   BepInEx] Chainloader startup complete
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Game beginning
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet modeling reset is not needed.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Game beginning
[Info   :DSP Star Sector Resource Spreadsheet Generator] Loading button
[Info   :DSP Star Sector Resource Spreadsheet Generator] Button load complete
[Info   :DSP Star Sector Resource Spreadsheet Generator] Scanning planets...
[Info   :DSP Star Sector Resource Spreadsheet Generator] 191 planets to be loaded.  Waiting for planets to load.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.
[Info   :DSP Star Sector Resource Spreadsheet Generator] Planet loaded.

Thank you for the report @SketchInInk .  This is broken for me too.  I think an update was pushed for the core game which is causing my background thread not to start.  I'll try to solve it this evening.

@SketchInInk An update with a fix will be out no later than tonight.
Last night the game changed.  This mod's planet loading thread uses the parameter PlanetData.reformMaterial which has changed in the core game to PlanetData.reformMaterial0 and PlanetData.reformMaterial1.  This is preventing the thread routine from starting.
Thank you again for bringing this to my attention.

@SketchInInk An update with a fix will be out no later than tonight.
Last night the game changed. This mod's planet loading thread uses the parameter PlanetData.reformMaterial which has changed in the core game to PlanetData.reformMaterial0 and PlanetData.reformMaterial1. This is preventing the thread routine from starting.
Thank you again for bringing this to my attention.

Good to hear that you already know the reason. Thank you for your good job.

Issue fixed in release v3.0.2.


Get-Help doesn't resolve the script's filespec to a full absolute path if no comment-based help is found in the script

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
When invoking Get-Help for a script that contains comment-based help, the script's filespec is resolved to the script's full absolute path (see https://github.com/PowerShell/PowerShell/issues/19539):
get-help ./foo.ps1

NAME
    C:\tmp\foo.ps1

SYNOPSIS
    syntax

SYNTAX
    C:\tmp\foo.ps1 [[-a] <String>] [[-b] <String>] [<CommonParameters>]

This is not the case if the script doesn't contain comment-based help, only the script's name is output:
get-help ./foo_nohelp.ps1
foo_nohelp.ps1 [[-a] <string>] [[-b] <string>]

This affects both Windows PowerShell 5.1 and PowerShell 7.3.4.
Expected behavior
# for consistency's sake
get-help ./foo_nohelp.ps1
c:\tmp\foo_nohelp.ps1 [[-a] <string>] [[-b] <string>]

Actual behavior
get-help ./foo_nohelp.ps1
foo_nohelp.ps1 [[-a] <string>] [[-b] <string>]

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.3.4
PSEdition                      Core
GitCommitId                    7.3.4
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Name                           Value
----                           -----
PSVersion                      5.1.19041.2673
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.2673
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Visuals
No response

The Working Group reviewed this. We would classify this as a low priority bug. We would welcome a PR to address this issue.

The problem stiill repro'es with 7.4.0


[Bug Report] DateTimePicker editable property does not disable in modal input fields

Element UI version
2.13.0
OS/Browsers version
Mac OS 10.15.4 / Chrome 80.0.3987.149
Vue version
2.6.11
Reproduction Link
https://jsfiddle.net/hxp90jbg/
Steps to reproduce

Create a date picker component with type "datetime"
Add :editable="false".

What is Expected?
If you set editable to false, one would think that all input fields are not editable and only UI clicking works.
What is actually happening?
Only the main input field is disabled from editing, inside the modal the fields are editable.

I think the design is reasonable, otherwise you set another property disabled

Hello @rkiik,
I'm facing the exact same problem and can't find a way to set the editable params to false for the inner input of the datetimepicker.
Did you find a workaround ? Or will I have to use a datepicker and a timepicker separately ?

No update on this issue ?


Mouse Without Borders Cursor Trail on Non Host Machine

Microsoft PowerToys version
0.77.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Mouse Without Borders
Steps to reproduce
Connect two PCS: PC order Left machine with issue(win1022H2)  | Right: Host(win11)
Mouse and Keyboard works fine But after removing the mouse(USB) the Left machine starts displaying Cursor trails Keyboard works fine
✔ Expected Behavior
Normal Cursor display
❌ Actual Behavior
Cursor leaves trails behind pressing a key on keyboard(host) removes the trails
Other Software
No response

/dup https://github.com/microsoft/PowerToys/issues/29700


Quest issue and rendering

One quest in the mana and artifice quests has a blood magic arcane ash instead of the mna arcane ash. Also if you try to build a construct from mana and artifice, minecraft crashes for the player loading the corresponding entity.
Crashlog for said issue: https://pastebin.com/UBPHr6W4

think the mna entity bug is more of a mod issue rather than a modpack issue

Hey!
Thanks for the report, the quest will be fixed next update.
I'll have to test the mna crash out, are you playing on a dedicated server or singleplayer? What type of construct did you create?

I am playing on a server with 12 gigs of ram. i wanted to build a kind of golem with hay bales and an armorstand. when i rightclicked the armorstand with the crafted haybale torso my mc crashed and everyone who was in the same area/loading it

but other than that i need to say the performance of this pack is insane <3

Thank you!
I've looked a bit more into the bug and it seems to be a compatibility error between GeckoLib and Mana and Artifice (https://github.com/Mithion/Mana-And-Artifice/issues/575), I'll update the mod once the issue is fixed or downgrade Geckolib, depending on what the mod author says.

Fixed next update.


Servers should have an optional password

If I want to share my server only with my friends, I want to be able to assign it a password.

This probably needs to be handled in the Room Server PHP

This is done.


1.21 Update

My server members and I would love to have Horseshoes on our server. Any plans for 1.21 update?

Updated to Minecraft 1.21.


wrong URLs for Unicorn & Chimea in properties file

The default URLs of Chimera and Unicorn (properties unicorn.url and chimera.url) are localhost:8080. However, registering queries with that URL (or sending back notifications to Chimera) fails with error vacuous schema part, thrown by the http-library. The solution is simple: just add http as prefix to the URLs.
This needs to be changed in the pom.xml, where properties are set.

Fixed by #181


Convert to new-SDK?

Now that the go-gettable SDK also works in old-appengine environments, would it make sense to port this to use https://google.golang.org/appengine ?

Nevermind, I think this is a dup of #76


Add "Signin with Apple" scafolding

➤ Lee Maguire commented:
The code for this implementation is mostly done but there are a few key blockers:

This is not compatible with Xcode 10 so dropping support for this version will allow the CI to pass.
WWDC has a session on Apple authentication so we need to see what comes out of that.


Can we remove colons on all field labels so they are all consistent

I'm closing this due to the intractability of the issue and the priority it warrants either way. We can always re-open it, but for the moment this is undesirable noise.


filter list help

Sample filterlist format add please

You can get a very early beta if you like
On Thursday, November 7, 2024 at 08:14:48 AM GMT+1, xcbly @.***> wrote:
Sample filterlist format add please
Screenshot_1.jpg (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Tell glog to log everything into STDERR.

Logging errors into a file inside a minimalistic container might not be possible, and glog bails out with an exit code > 0 if it fails.
Fixes #1785

Picked some random reviewers; @containous/traefik, feel free to review as desired. :-)

@emilevauge sure thing 👍 done.


cmd/go: compiler tests fail with ccache

Go compiler tests started failing at 3acd2576ab224d905cfd09208a6d6607ce4b0fb6 when ccache is installed. The new Go test requires CGO and sets HOME to a non-existent directory. This break since ccache is unable to create its cache directory. A simple fix is to set CCACHE_DISABLE=1 to force ccache to use the real compiler. Fixing this fault will avoid confusing failures on systems where ccache is the default system compiler (eg, Fedora).
Related: #17668
@ianlancetaylor

Example test failure:
--- FAIL: TestScript (0.00s)
    --- FAIL: TestScript/mod_case_cgo (0.16s)
        script_test.go:150:
            > env GO111MODULE=on
            > go get rsc.io/CGO
            [stderr]
            go: finding rsc.io/CGO v1.0.0
            go: downloading rsc.io/CGO v1.0.0
            # rsc.io/CGO
            ccache: error: Failed to create directory /no-home/.ccache/tmp: Permission denied
            [exit status 2]
            FAIL: testdata/script/mod_case_cgo.txt:3: unexpected command failure


App crashing

The App crashed first just after I tried to open it after downloading it. Then, I tried downloading it again and it worked. It should the first page but crashed once I pressed track location

Fixed in https://github.com/StAResComp/sifids/releases/tag/v0.3.1


logger: integrate the cloud log service

YodaOS currently uses AliCloud logging service to collect the logs from devices, now it's disabled by default, and we should provide the ways for developer to connect their own log providers like AliCloud and enable it.

This has been finished :)


Update install docs

With #80 merged, we can feel pretty good about people pip installing the package. This means that we support and can recommend a simpler git-less install for users. I have moved the development install instructions to the dev guide page.
Closes #79

@rschwant let me know what you think we should do about the Hera/Cheyenne instructions. I am thinking many parts could be eliminated, just referencing the other install instructions, but we can leave some of the notes that are specific to those machines.

I would be okay with simplifying these instructions for Hera now. Now the only difference with the main instructions is you need to link the cartopy files, so this entire section could be made much simpler. @rrbuchholz how do you feel about simplifying the instructions for Cheyenne now that the process for loading MONET and MONETIO is easier. Zach I am wondering if in the main instructions we want to just move to using http cloning rather than ssh cloning. I keep getting emails from people learning who have not set up an ssh key. To make it simpler we can leave the main instructions as http and the develop instructions as ssh. Developers would likely understand the difference, but people who are very new to Python and GitHub do not. Does this work for you?

@rschwant for the main instructions I am suggesting not to do any cloning. See them here and the developer's guide ones here.

Great that makes sense. The how_to_run.rst and all of the example jupyter notebooks and run scripts still say the following:
import sys; sys.path.append("../../")
from melodies_monet import driver
With this pip install, you can just add the second line correct:
from melodies_monet import driver
Do you mind updating all of these lines for consistency? Perhaps, something like the following
#If you have cloned the MELODIES-MONET repository instead of using pip install, uncomment line below and point to your cloned repository
#import sys; sys.path.append("../../")
from melodies_monet import driver

With this pip install, you can just add the second line correct:
from melodies_monet import driver

@rschwant thanks for pointing that out, I will fix those. import sys; sys.path.append("../../") isn't needed for the dev install either since we are pip installing MM there too, just the local one instead of from the GitHub url.

Great, then this is even simpler. Thanks for updating these other files too.

Current CI failure is because it is (currently) unable to reach the tutorial data on the CSL website

Current CI failure is because it is (currently) unable to reach the tutorial data on the CSL website, and the linkcheck showed that other NOAA domains are down as well.

Yes, the systems will be back up by this afternoon.

Thanks @rrbuchholz

Thanks @rschwant , sounds good.


Corrected typo in readme

Noticed a typo in the readme. See attached screenshot.

Many thanks for your correction and sorry for the late reply.
Merged these nice commits.


Geo result with full dataset

Hi,
Currently i am just getting id and geohash as result.
If i want to get full dataset along with id and deohash then is it possible with geo-nearby?
i am getting as search result:
 [
  {
"i": "AABC",
"g":<PHONE_NUMBER>598182
},
  {
"i": "123dgff",
"g":<PHONE_NUMBER>598182
}
]

I want something like:
 [
  {
"i": "AABC",
"g":<PHONE_NUMBER>598182,
"name" : "test",
"model" : "aa11"
},
  {
"i": "123dgff",
"g":<PHONE_NUMBER>598182,
"name" : "123",
"model" : "aa22"
}
]

Hello!
You probably using internal createCompactSet method. This method only creates a minimum data set, which will reduce memory usage.
For you, I can suggest next code snippet:
const Geo = require('geo-nearby');
const g = require('ngeohash'); // if your npm version <= 2 you should install it first

const data = [
  { id: 1000, name: 'Arkhangel’skaya Oblast’', country: 'RU', coord: { lon: 44, lat: 64 }, admin1: 'Arkhangelskaya' },
  { id: 1001, name: 'Arkhangelsk', country: 'RU', coord: { lon: 40.5433, lat: 64.5401 }, admin1: 'Arkhangelskaya' },
  { id: 1002, name: 'Severodvinsk', country: 'RU', coord: { lon: 39.8302, lat: 64.5635 }, admin1: 'Arkhangelskaya' },
  { id: 1003, name: 'Novodvinsk', country: 'RU', coord: { lon: 40.8122, lat: 64.4165 }, admin1: 'Arkhangelskaya' },
  { id: 1004, name: 'Kotlas', country: 'RU', coord: { lon: 46.64963, lat: 61.25745 }, admin1: 'Arkhangelskaya' }
];

const sortedSet = data.map((r) => Object.assign({}, r, {
    g: g.encode_int(r.coord.lat, r.coord.lon)
})).sort((a, b) => a.g - b.g);

const geo = new Geo(sortedSet, { sorted: true });

geo.nearBy(64.54, 40.54, 5000);

Also if you have static data set, which does not change, you can at first create and sort you data, save it and then only load it in geo-nearby as sorted set.

Thanks! its works for me.


Document memory usage for Cloud Foundry

n/t

We've been discussing this in #2135

Thanks @rogeruiz


Support Content-Range/Last-Modified/ETag in aiohttp.web static handling

I started working on this.

Fixed by #1382
If somebody want to support ETag -- please open a new issue.


Change look of stats page

decrease the width so that the papers are not so wide on wide screens
more padding between tab title and sub-title
look into possibility of generalising chart
change colour of Poisson section so it stands out from the normal section

changes:

leave width be
leave colour be
change navigation to use drop down to separate Poisson and normal

final changes:

do not generalise chart to allow for flexibility