text:
Failed to list image tags after image build.

In GitLab by @wknet123 on Sep 25, 2017, 15:51

In GitLab by @wknet123 on Nov 8, 2019, 07:38
Closing it as fixed.

In GitLab by @sokril on Nov 8, 2019, 08:12
closed

In GitLab by @sokril on Nov 8, 2019, 08:12
assigned to @liyanq528

repo: inspursoft/board


text:
Support for view_once/disappearing messages

Issue Template Requirements
Pre-Checklist
I made sure...

[x] I read the README.md
[x] I looked over the examples and wiki
[x] my issue hasn't been asked or solved before

Question
View Once
I noticed that medias in ThreadRavenMediaItem (ThreadImageMedia and ThreadVideoMedia) are empty as shown in below screenshot

They probably make a request (with item_id maybe) when you click on the media to load it... But I don't find the proper method to do so.
Disappearing Message
When receiving messages in disappearing mode I am asked to update my instagram client as shown here

Is there a way I can use a more recent client? Or can you provide support to do so?

Looks like this is Instagram's app exclusive feature. The same message is shown in the web version too :-(

source: gharchive/issue

authors: ErrorxCode bloworlf

license_type: permissive

license_source: github-api


text:
Use new doc_id based query to get posts

Fixes #2319.
This uses the new query to retrieve user posts as discussed in the bug comments.
The returned object is (almost) equal to what was returned by the "iphone queries". (But it video_versions is null for images (and maybe sidecars), and carousel_media is null for non-sidecars, so I suppressed the TypeError that happens when trying to index a None.

Is it just a proof of concept? No, should be complete.
Is the documentation updated (if appropriate)? Yes. Nothing changed for the user, only the module documentation was updated.
Do you consider it ready to be merged or is it a draft? Should be now ready.
Can we help you at some point? Suggestions are welcome.

Thank you for the pull request! It seems to work for me at least for images and for videos!

Some comments on the changes:

I used a fixed page size of 12 to emulate the requests done by a browser. Requesting more entries works, but it seems the limit is 33, even if more are asked.
Only after seems to be really necessary for pagination, but again, I included some extra parameters to more closely emulate a browser's query.
I removed the code for including the x-instagram-gis header in the new queries. I did not see this header (or anything similar) in the queries done by the web interface, and it seems to be working fine without it.
I have no idea how the rate limiter works regarding these queries. I used a similar strategy (grouping by doc_id instead of query_hash).

I noticed a small change in behavior regarding posts that are posted by more than one user (I do not know the "official" name - but it's not tagged users, it's when it says "User1 and User2).
Previously Post.owner_profile (and therefore {profile} in filename templates) would always return the user that is being downloaded, even if it's not the main profile of the post. With this new query it may return a different user than the one being downloaded.
This is a consequence of what's returned by the query. There are two fields (owner and user), but both return the main owner of the post. (Some other field does list the other users.)
I wouldn't say this new behavior is wrong, just something to be aware of. It is always possible to use {target} in the filename pattern to name files based on the profile being downloaded, not where they originally came from.

I have been using this code for a couple days, and other users have also reported testing it, and it seems to work.
The documentation has also been updated, so I believe this should be ready for review.

I believe everything should be fixed.
I based this on the master branch, but let me know if you want me to rebase it on the upcoming branch.

source: gharchive/pull-request

authors: RazeBerry ekalin

repo: instaloader/instaloader

license: MIT


text:
[Bug]: Unable to add custom spans with layer arm64 > 96 and x86 > 213

Problem Description
When using the newest versions of the Instana Layer in Nodejs with AutoTrace (wrapping the handler), the auto instrumentation part works fine, but trying to access the current span or adding intermediate spans fails (they are null and intermediate spans are not send to Instana).
After creating a Lambda Function with autoTrace and a function URL using the code blow, when executing the Lambda, we can see the following in the logs:
  | 2024-11-18T15:35:33.933Z | INIT_START Runtime Version: nodejs:20.v43 Runtime Version ARN: arn:aws:lambda:eu-central-1::runtime:4a87b8fceb008240eb9bfe7dc3126c2dec6fe75f06c6a4d8977d0267eb5da2bd
  | 2024-11-18T15:35:34.169Z | 2024-11-18T15:35:34.169Z undefined INFO @instana/aws-lambda module version: 3.21.0
  | 2024-11-18T15:35:34.693Z | 2024-11-18T15:35:34.693Z undefined INFO @instana/aws-lambda module version: 4.0.1
  | 2024-11-18T15:35:34.843Z | 2024-11-18T15:35:34.843Z undefined INFO Method warn of [object console] was already wrapped. Unwrapping.
  | 2024-11-18T15:35:34.844Z | 2024-11-18T15:35:34.844Z undefined INFO Method error of [object console] was already wrapped. Unwrapping.
  | 2024-11-18T15:35:34.869Z | EXTENSION Name: instana-lambda-extension State: Ready Events: [INVOKE, SHUTDOWN]

It looks like the original handler is wrapped in version 3.21.0, while 4.0.1 is used when requiring the package in the code.
Short, Self Contained Example
Lambda code:
const instana = require('@instana/aws-lambda');

exports.handler = async (event, context) => {
    const span = instana.currentSpan();
    const response = {
        statusCode: 200,
        body: JSON.stringify({
            currentSpanId: span ? span.getSpanId() : null,
        }),
    };
    return response;
};

Node.js Version
Lambda nodejs20.x
package.json
-

package-lock.json
-

Hi @janritter Thanks for your report! We will take a look asap!

Hi @janritter
The fix has been successfully released in v4.1.0.
You can now use the following latest layer versions for ARM64 and x86_64 in the region eu-central-1:

x86_64: Layer version 218
ARM64: Layer version 99

Please let us know if you are still encountering any problems.

@aryamohanan thanks for the quick release, I can confirm that it now works on our end

authors: aryamohanan janritter kirrg001

repo: instana/nodejs


text:
System profile prompting has inconsistent numbering

What is the current experience of ilab you've found issue with?
We have several menus where [0] is the "default" option but users can't actually see what it is and get misleading or confusing behavior if they select it
Example below - I hit enter without picking a number, and ilab assumed I picked NVIDIA.
Please choose a system profile.
 Profiles set hardware-specific defaults for all commands and sections of the configuration.
First, please select the hardware vendor your system falls into
[1] AMD
[2] APPLE
[3] INTEL
[4] NVIDIA
Enter the number of your choice [0]:
[1] NVIDIA A100 X2
[2] NVIDIA A100 X4
[3] NVIDIA A100 X8
[4] NVIDIA H100 X2
[5] NVIDIA H100 X4
[6] NVIDIA H100 X8
[7] NVIDIA L4 X8
[8] NVIDIA L40S X4
[9] NVIDIA L40S X8
Enter the number of your choice [hit enter for hardware defaults] [0]:
No profile selected - any hardware acceleration for training must be configured manually.

How do you think the described experience should be?
The first menu should list [0] None of the below and default to exiting early with no profile selected with the same message we give for the second menu, i.e. No profile selected - any hardware acceleration for training must be configured manually.
The second menu should list [0] Hardware defaults (no profile)
What is the benefit of the change you are proposing?
Much less confusing experience for the user

cc @cdoern @JustinXHale curious y'alls thoughts on this

I agree the messaging is very confusing @nathan-weinberg. There are a few things that could be done here:

Clearer messaging: ex. Enter the number of your chose or [0] for no selection
Add [0] to the menu[0 for none/skip] in the menu

Yeah, this is a bug.
Though, i don't think having a [0] None option makes sense.
If a user doesn't have an intel, amd, mac, Nvidia machine..... what do they have? Those are the only hw configurations we support.
The no profile option REALLY confused QE and users with training profiles. I don't think it makes sense to have here.

authors: JustinXHale cdoern nathan-weinberg

repo: instructlab/instructlab


text:
Add a column to the contributor dashboard for taxonomy labels

The taxonomy triage team uses labels on pull requests for tracking and notification purposes. It would be helpful to users to add a few of these labels to the contribution dashboard. Documentation around labels can be found here triaging-contributions.md - instructlab/taxonomy (it is very out of date, i’ll get that updated). IMO we should include “triage-requested-changes”, “e2e-ready”, and “triage-rejected”. Feedback welcome and encouraged!

the "e2e-ready" flag is now named "community-build-ready"

Thanks for opening this issue @juliadenham . Appreciate it. It would be great if you can update the issue, whenever the labels related document is updated, so we can use the latest and greatest.

After discussion with triage team, following is the list of labels that we should translate to either status or action for the user.

cmb-running (status)
cumminity-build-ready (status)
knowledge (status)
legal-hold (status)
precheck-generate-ready (status)
question (action)
ready-to-merge (status)
sdg-unsuccessful (status)
skill (status)
stale (status and possible associated action)
topic-failure (action)
triage-needed (status)
traige-rejected (status)
traiage-request-changes (action)

status labels are just the progress notifications. Action labels are something that requires users attention and might require update to their contribution.
@Misjohns I think if you can help us designing the mock-up that shows the status as well as actions for each contribution, i think this story can get to ready state.

authors: juliadenham vishnoianil

repo: instructlab/ui


text:
🛑 Shopintake is down

In 2d0b2a0, Shopintake (https://www.shopintake.com) was down:

HTTP code: 503
Response time: 1254 ms

Resolved: Shopintake is back up in 0b6f54b.


text:
🛑 FoodB2B is down

In 5892068, FoodB2B (https://www.foodb2b.kr) was down:

HTTP code: 503
Response time: 775 ms

Resolved: FoodB2B is back up in 4d12691.


text:
🛑 Shopintake is down

In c9bd9ac, Shopintake (https://www.shopintake.com) was down:

HTTP code: 403
Response time: 384 ms

Resolved: Shopintake is back up in 8de92b9 after 15 minutes.


text:
PWM on Raspberry Pi still not supported?

Hi there!  The docs say that PWM on Raspberry Pi is still not supported.  Is this still true??
Thanks!

Yes, I've just double-checked and there's no code to support it there, so the docs are correct.

authors: The-Alchemist alext-mkrs

repo: intel-iot-devkit/mraa

license: mit

license_source: bigquery


text:
Garbled text in app

On a Pixel 4, the app shows this Chinese text when connected to OpenBot. Otherwise works normally

Is your phone from China? It may be related to the Java locale.

I have never seen something like this. :) I believe, you are using a cheap Arduino clone with a very long Chinese product name. You can fix this by changing line 963 in CameraActivity.java to
connectionSwitchCompat.setText("Connected");

Please let me know if that fixes your issue.

No, it's a standard Google Pixel 4 from the US. Running Android 11.
Yes, it is a Chinese Arduino clone, although a very nice one (DFRobot Romeo board): https://www.dfrobot.com/romeo.html

That fix worked, thanks!

repo: intel-isl/OpenBot


text:
Question about AUTO path?

When a Page Fault is encountered, will Auto perform all memcpy operations by the CPU, or will the CPU just touch the address corresponding to the page fault as in the DSA example code to deal with the missing page, while the hardware DSA does the memcpy.
I have 1MB of data that needs to be migrated between two addresses, and even though I do this by TOUCHING the first few bytes of each page in the 1MB, in actual execution, I keep running into Page Fault, and what do I need to do to avoid Page Fault in the HW path.

Hey @Yemaoxin
For your first question, when encountering a Page Fault, the CPU will just "take over" and complete the rest of the operation.
For the second part, I don't see how you keep encountering a page fault even after TOUCHING all the pages.

authors: Yemaoxin abdelrahim-hentabli

repo: intel/DML


text:
docs: models: Figure out a way to highlight mutable parameters

Since only selective hyperparameters (that have been exclusively set mutable) will be mutable, we should let users know somehow which ones are.

Related #1094

repo: intel/dffml


text:
add MemPath to type Memory

Preparation patch for vm template.
Due to  HugePages & MemPrealloc are attributes of the memory
and they are related to MemPath, so they are also moved to type Memory.

lgtm

@bergwolf I think this PR has been superseded by your PR introducing VM factory support, right?
If that's the case, let us know and we'll close it.

authors: devimc laijs sboeuf

repo: intel/govmm


text:
[UT] Fix test_precise_math

Before this PR, precise sqrt is lowered to __imf_sqrtf, which is not precise.
__imf_sqrt_rn is added in the new device library updated in https://github.com/intel/intel-xpu-backend-for-triton/pull/2774.
This PR uses __imf_sqrt_rn to get the precise sqrt implemented.

Pass rate: 93.18%->93.19%

I may be missing some context (can you add PR description, please?), but I see our test is indeed failing and we are playing tricks to get it to pass.

Added PR description.

Would llvm/llvm-project#88222 (comment) fix the test without needing to change it?

That is a different issue, we currently need to use cpu result as reference, or else we are comparing with the imprecise result.

repo: intel/intel-xpu-backend-for-triton


text:
Question how can I do multiplication and sum element wise

Some thing like ippAddProduct_32f(...........)
Thanks
Elad

Found same topic:
Feature request: Element-wise multiplication

repo: intel/mkl-dnn


text:
Hi Guillermo, dont be shy

This pull request Will be used yo review your skils at intelygenz
Then, It Will be closed, not merge.
Give us some time to take a look.
Thanks!!

Reviewed. I pass a note to my team mates to send you the conclusions. Thanks!

repo: intelygenz/the-real-devops-challenge


text:
[Bug]: Another invalid "var-use-before-def", 101 flag on a valid GetProperty call

Current Behavior
The following code generates a "var-use-before-def" error by the plug-in parser on the variable "MinSoftwareversion", but there's not a thing wrong with it.
If (Serial_Number eq !null) then Begin
((self.d)['blah'])->GetProperty, CSHDetector_Minimum_Software_Version = $
MinSoftwareVersion
EndIf
Expected Behavior
The plug-in parser should not issue a warning or error state on this syntax.  Every time there's a potential output variable as a keyword, the code is going to be marked up to the point of the mark-up being totally ignorable unless we can interactively turn off warnings like this through a context menu.  The descriptions of the toggles in Preferences aren't particularly useful for situations like this.
GitHub Repo
No response
Steps to Reproduce
Copy the example code.  Easy peasy.
Failure Logs
No response
Operating System

[ ] macOS (Intel x86_64)
[ ] macOS (ARM64)
[ ] Linux
[X] Windows

IDL Version
9.0
Additional Information
No response

I'm going to mark this as won't fix. From a pure IDL perspective, you aren't wrong that the code is technically correct, but think about this problem as a programmer.
Technically, no where in your code is "Serial_Number" defined. If this is a routine definition I would expect to have arguments and keywords where, one of them, would be "Serial_Number" so that there's a source for it and this wouldn't be an issue.
For me, a big reason we have a lot of these errors is to help the flow of code follow patterns that new users to IDL can quickly pick up.
I know there's some big opinions in that statement, so hit me up on teams if you want to chat, Jim and maybe there's a middle ground here!

authors: HGS-jimpendleton znorman-harris

repo: interactive-data-language/vscode-idl


text:
Deploy still asking for password

I have set up the node.js and followed all the steps in the readme. But when i run cap production deploy:check it still asks me for a deploy password. Is this a problem with the ssh in the node? I used the key that i have generated one from my vps. Any idea what might cause it? Is there a more detailed guide on how to set this up?

Hi!
Can you past the part of the Capistrano log that errors? Then we can take a look at it. From what location are you running "cap deploy:check"? Is the key from that location added to the server's JSON configuration?
We're working to bring our documentation back. But also a good thing to add this to the README.

i am running cap deploy:check from my the folder of the project that i want to deploy. The key from that projects github is added to the json configuration.
[[user]]@[[computer]]:~/Projects/[appname] $ bundle exec cap production deploy:check
INFO [2cf820ae] Running /usr/bin/env mkdir -p /tmp/stageapp/ as deploy@[[serverip]]
DEBUG [2cf820ae] Command: ( PATH=/opt/rbenv/shims:$PATH /usr/bin/env mkdir -p /tmp/stageapp/ )
Text will be echoed in the clear. Please install the HighLine or Termios libraries to suppress echoed text.
deploy@188.166.15.123's password:

Okay, thanks for the details.
Just to be sure. On the computer or VPS that you run this command. Did you copy that ~/.ssh/id_rsa.pub key into the configuration key of your server.json configuration file?
So for example, on my own laptop I have this in ~/.ssh/id_rsa.pub:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCuiCTIYcGAbNemW4e1Q0SqfweN2d1Tkhn6xtwiV6/AITgSaW5bFWo/VEUghlCYwYcBgxoOMy0jfUJLS/XG/nQUsL3MKI/oAoFiaVoyDPb/zPvYeWrp3eGi+Ey66luVEVWLdHe1RQqCA52j5mSSCYsjKWt+q8eZWADASyuBsrIZjkdQ8z3ziSeaJdTXPKBKyMPAHd26JFZoBQL39OYcq6xozM7B+IlBoLJhFQRZP1IFjWJYtdYTj2PoByDynfZKltWgS/ouDNIzPhF9ZubXSrwYR4uCXmQbdk+quBItw/RJW7rIlLua24yhoPA/STNel/8Ld33FhMV8D0bx6mj+BrqV michiel@MacBook-Air-van-Michiel.local

This is my SSH key.
And I placed this inside the ssh_deploy_keys configuration in my nodes/188.166.15.123.json:
{
  # ... other options
  "ssh_deploy_keys": [
    "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCuiCTIYcGAbNemW4e1Q0SqfweN2d1Tkhn6xtwiV6/AITgSaW5bFWo/VEUghlCYwYcBgxoOMy0jfUJLS/XG/nQUsL3MKI/oAoFiaVoyDPb/zPvYeWrp3eGi+Ey66luVEVWLdHe1RQqCA52j5mSSCYsjKWt+q8eZWADASyuBsrIZjkdQ8z3ziSeaJdTXPKBKyMPAHd26JFZoBQL39OYcq6xozM7B+IlBoLJhFQRZP1IFjWJYtdYTj2PoByDynfZKltWgS/ouDNIzPhF9ZubXSrwYR4uCXmQbdk+quBItw/RJW7rIlLua24yhoPA/STNel/8Ld33FhMV8D0bx6mj+BrqV michiel@MacBook-Air-van-Michiel.local"
  ],
  # other options
}

Alright that seemed to be the problem. I used the ssh that i generated on the server instead of the computer that i was working on. Thanks for commenting!

Ok! Good to hear that solved it :) Let us know if you have any other questions and open a new issue for those.
Many thanks!
Michiel

authors: cvandermeer michiels

repo: intercity/chef-repo


text:
feat(open-payments): make schema validation in the open-payments client behind a flag

Changes proposed in this pull request

Context
This change adds validateResponses flag to open payments client initialization function. This allows bypassing runtime response validation against the Open Payments OpenAPI specs.
This is particularly useful for the WM extension use case since the openapi validator libraries we use under the hood in @interledger/openapi use ajv schema validation during runtime, which uses unsafe eval , and as a result, prevents us from running it in the extension for manifest v3: https://github.com/ajv-validator/ajv/issues/406.

Fixes #454

Tested in the browser with the extension, I do not see any errors related to the client initialization.

repo: interledger/open-payments


text:
feat: add GraphQL API idempotency/cache middleware

Changes proposed in this pull request

Adding Redis cache layer for backend GraphQL admin API. It uses the idempotencyKey mutation input parameter as the key to cache on (24 hrs TTL)
Adding idempotencyKey parameter to createAsset mutation (just the single mutation for now, wanted initial feedback)

References:

https://shopify.engineering/building-resilient-graphql-apis-using-idempotency
https://stripe.com/docs/api/idempotent_requests / https://stripe.com/docs/error-low-level#idempotency

Outstanding questions:

I went with redis since we already had it included in the project + simple TTL handling. Maybe in-memory is simpler for now?
Without any authentication mechanism for the GraphQL API, there is no proper/reliable way to tell who the client making the request is. The only option would be the user-agent header as well as the ip of the incoming request (which are easily forged). This means that the idempotencyKey can be reused across different clients. Should I add some sort of client identifier to store with the key, or wait until we have a proper authentication mechanism to change it then?
As described in https://shopify.engineering/building-resilient-graphql-apis-using-idempotency, locking a request on the idempotencyKey is necessary to properly handle concurrent requests. I have a branch with a simple redis locking mechanism ready to follow after this PR, and will be part of the GraphQL middleware.

Context

Progress towards #382

Checklist

[x] Related issues linked using fixes #number
[x] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass

I went with redis since we already had it included in the project + simple TTL handling. Maybe in-memory is simpler for now?

This is the more future-proof solution, so yes, let's keep Redis for this.

Without any authentication mechanism for the GraphQL API, there is no proper/reliable way to tell who the client making the request is. The only option would be the user-agent header as well as the ip of the incoming request (which are easily forged). This means that the idempotencyKey can be reused across different clients. Should I add some sort of client identifier to store with the key, or wait until we have a proper authentication mechanism to change it then?

I'd say we "wait" for the auth mechanism. It's on our todo-list (I think) and I don't want to add something temporary that we remove later. We don't have the time for that. If we think this is a high security risk, we should prioritize the auth mechanism.

As described in https://shopify.engineering/building-resilient-graphql-apis-using-idempotency, locking a request on the idempotencyKey is necessary to properly handle concurrent requests. I have a branch with a simple redis locking mechanism ready to follow after this PR, and will be part of the GraphQL middleware.

👍

authors: mkurapov sabineschaller

repo: interledger/rafiki


text:
Extension starts payments even before page load

In Chrome, during prerendering, the extension starts checking/creating payments while we're typing URL in address bar. We should start the sessions/fetching only after page load, not during prerender.
If we change the URL after typing (before hitting enter), the payments continue as if tab was never closed.

https://groups.google.com/a/chromium.org/g/chromium-extensions/c/1ikOwxWiU_g

authors: raducristianpopa sidvishnoi

repo: interledger/web-monetization-extension


text:
[AV2-1207] UX/UI Manual Save button and last save time in assessment UI

Story/Ticket Reference ID from JIRA:
https://intersective.atlassian.net/browse/AV2-1207
Additional Comments:
Updated last save section hight and save button hight.
update last save section padding.
update last save to update through events (rxjs subjects).
update activity-desktop, assessment-mobile to broadcast that event.
Checklist:

[x] Unit test completed?: (Y/N)
[x] Docs folder up to date?: (Y/N)
[x] Add if anything missed: (Y/N)

All checklists are okay.
This PR looks great - it's ready to merge! Please review and let's ship it. :)

Please check jira story comments for video how it works now.


text:
Input() with Key.ENTER and click() don't work as expected

I'm using the standalone version. To run this code use 0.9.6-RC3 because of this reported bug.
I have two questions highlighted below, as comments in the code.
Feature: Amazon UI automation

  Background:
    * def baseUrl = 'https://www.amazon.com/'

  Scenario: Search for item
    Given driver baseUrl
    And def searchTerm = "Explore It"
    And def searchTermEncoded = "Explore+It"

    # Q1: Key.ENTER should trigger the search but nothing happens, like the key isn't sent. Why?
    # When input("#twotabsearchtextbox", [searchTerm, Key.ENTER])

    # So I have to click the search button manually
    When input("#twotabsearchtextbox", searchTerm)
    And click("#nav-search-submit-text")

    # Q2: At this moment, I should be seeing the search results, but I'm still in the homepage. Why?
    Then match driver.url contains "s?k=" + searchTermEncoded
    And locate("div.s-result-list").exists
    And locate("{span}Reduce Risk and Increase Confidence").exists

I tried using the same actions and selectors on Cypress and the flow works. Am I doing something wrong in Karate? Why can't I reach the search results page?

closing as not per process: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue

@dialex I know it is probably a lost cause trying to convert a cypress evangelist ;) but here are the changes I made:
    When input("#twotabsearchtextbox", searchTerm)
    And mouse("#nav-search-submit-text").click()

    Then waitForUrl('s?k=' + searchTermEncoded)
    And locate("div.s-result-list").exists
    And locate("{^span}Reduce Risk and Increase Confidence")

explanation: yes, Karate does use JS for keyboard-input and clicks, each UI automation framework has quirks, there are some details here: https://github.com/intuit/karate/issues/1106#issuecomment-616034457
can this change in the future ? of course, with community support and more people who actually take the time to study the code and make changes. and provide proper bug-reports with working code, instead of "drive-by" issues
for those watching the feed, a reminder that we have a new optional() syntax, and we don't have an exists getter on Element we are renaming it to present to reduce confusion. details here: https://github.com/intuit/karate/issues/1148

haha, I have an open mind ;) Cypress had its problems too in the first years
Here's what I tried:

The test still failed with this change Then waitForUrl('s?k=' + searchTermEncoded)

If we are waiting for the url to change and it never happens, that's because it's not being clicked. So the issue must be the click.

The test still failed with this change And mouse("#nav-search-submit-text").click()

So that click() and mouse().click() are diff syntaxes for the same behaviour This alone is not enough to fix the test

Maybe I need to explicitly wait for the click to happen.

So I added And waitFor('#nav-search-submit-text').click() after the mouse click. This worked... 🎉 sometimes 😢

My results:

⚠ I only got the test passing when I used mouse().click() together with waitFor().click(). Please tell me I don't have to wait for every UI interaction 😱

Is this a requirement? I hope not, even Selenium is capable of waiting for steps and waiting for load pages, but the truth is, it only "worked" when I did this.
And if it's not a requirement, then why do I get this behaviour? Is it specific to the standalone version? It's a really simple test, executed in isolation.

[5 out of 10 runs] ⚠ I noticed that "sometimes" Karate would not input the whole search term (e.g. instead of "Explore It" just "Explore" or "Explore I".

It looks like the mouse().click() step doesn't wait for the previous step to finish. Karate should run all steps of a given test sequentially right? Or are they executed in parallel? (Selenium runs steps sequentially. Cypress runs commands in parallel, but still, each step executes after the previous)

For reference, this is the test code that sometimes works:
Scenario: Search for item
    Given driver baseUrl
    And def searchTerm = "Explore It"
    And def searchTermEncoded = "Explore+It"

    # This one-liner should work, but doesn't
    # When input("#twotabsearchtextbox", [searchTerm, Key.ENTER])
    When input("#twotabsearchtextbox", searchTerm)

    # This should work, but doesn't
    # And click("#nav-search-submit-text")
    And mouse("#nav-search-submit-text").click()

    # This should not be necessary, but it is
    And waitFor('#nav-search-submit-text').click()

    Then match driver.url contains "s?k=" + searchTermEncoded
    And locate("div.s-result-list").exists
    And locate("{span}Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing").exists

@dialex I was using the develop branch so we may both be out of sync. this is why I insist on the process, but your call. here's the developer guide: https://github.com/intuit/karate/wiki/Developer-Guide

for those coming across this thread in the future - after more investigation - the ENTER key was indeed being handled wrong in chrome native, which is now fixed in #1192

authors: dialex ptrthomas

repo: intuit/karate


text:
karate-config.js wasn't loaded correctly if comment block is given before the line of function()

For example,
/**

Karate will invoke this function when starts up.
*/
function() {
...
}

It was loaded only after removed the comment block.

yes this is not supported. functions have to start with the text function

authors: baechul ptrthomas


text:
"looks like" miss

% ./ttop --on
systemctl check 'ttop.timer'
/bin/sh: systemctl: command not found

cmd error: Looks like ttop.timer is already running system-wide
onoff.nim(70)            cmd

@white-dragon could you please let me know OS you use?
You can enable it via Cron like: ‘*/10 * * * * ttop -s‘

I going to implement cron support via --on parameter

альт линукс у меня, причем на sysvinit, тобишь у меня systemctl просто нет вообще
я к тому, что оно говорит что мол мохоже что он системвайд запущен - нифига не похоже :)
очень странное предположение :)

Да, с фразой конечно мимо - поправлю. Причем я начал делать на одной машине - там был крон, а потом, с удивлением, обнаружил что он уже опциональный во многих системах и переделал.

Crontab support added in v0.4.8: https://github.com/inv2004/ttop/releases/tag/v0.4.8
Please let me know if something does not work there


text:
Creating a set does not update affected records

Reproduce

Install Invenio v3.2 (https://inveniosoftware.org/products/framework/)
Login as an admin (i.e. create an account and assign admin role)
Create a new OAI set via the administration interface.

Problem
Creating the sets, starts a background task in celery which then seems to be rate limited. See error below.
[2020-02-17 10:41:54,759: INFO/MainProcess] Received task: invenio_oaiserver.tasks.update_affected_records[73318bac-d8a3-4501-a17b-d53652826b8b]
127.0.0.1 - - [17/Feb/2020 10:41:54] "POST /admin/oaiset/edit/?id=1&url=%2Fadmin%2Foaiset%2F HTTP/1.1" 302 -
[2020-02-17 10:41:55,065: ERROR/ForkPoolWorker-4] Task invenio_oaiserver.tasks.update_affected_records[73318bac-d8a3-4501-a17b-d53652826b8b] raised unexpected: TypeError('must be str, not NoneType',)
Traceback (most recent call last):
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/celery/app/trace.py", line 382, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/flask_celeryext/app.py", line 100, in __call__
    self.app.flask_app.preprocess_request()
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/flask/app.py", line 2241, in preprocess_request
    rv = func()
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/flask_limiter/extension.py", line 511, in __check_request_limit
    six.reraise(*sys.exc_info())
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/six.py", line 703, in reraise
    raise value
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/flask_limiter/extension.py", line 494, in __check_request_limit
    self.__evaluate_limits(endpoint, all_limits)
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/flask_limiter/extension.py", line 366, in __evaluate_limits
    limit_key = lim.key_func()
  File "/Users/lnielsen/envs/my-site-ZNC6mTtx/lib/python3.6/site-packages/invenio_app/limiter.py", line 19, in useragent_and_ip_limit_key
    return str(request.user_agent) + request.remote_addr
TypeError: must be str, not NoneType

@lnielsen with the new dynamic sets, this can be closed right?

authors: lnielsen ppanero

repo: inveniosoftware/invenio-oaiserver


text:
version: post-release bump

Signed-off-by: Jiri Kuncar jiri.kuncar@cern.ch

Coverage remained the same at 97.227% when pulling 1c07938a49f7f3ce4a79f03fade9038206789c52 on jirikuncar:version-bump into 4e59b1f3a2bf8552685a2a70358a74cbae0fc3ae on inveniosoftware:master.

authors: coveralls jirikuncar


text:
[DO NOT MERGE] systemfield: make index aware of prefix

closes https://github.com/inveniosoftware/invenio-communities/issues/620

found an error, some indices were prefixed several times.

This solution is not suitable. The Index would have the prefix and would work by itself. However, invenio-indexer API calls _prepare_index before performing operations (i.e. IndexRecordOp --> indexer.index(record)). This call will mean ending up with the prefix added twice (once from IndexField another from Indexer).
Another alternative is to add a line such as the following every time we want to get the actual index name (without being an indexer call, i.e. IndexRefreshOp).
index=self.indexer._prepare_index(self.record_cls.index)

TL;DR solutions:
a) Make IndexField the sole point of prefix/suffix expansion. This requires lots of changes and is back incompatible for invenio-indexer.
b) Be aware of using _prepare_record when getting the index name from the field. This requires the least changes, but we might end up in trouble in the future if we pass an already prepared index to the function (prefixed twice)
My take, due to the need of a fast fix: go for b) adding an if to check if it has already been prefixed. For now, the only extra place is the IndexRefreshOp.
cc @lnielsen @ntarocco (can discuss tomo after standup)

This last fix is working (see instance indices), also tested creating a community (issue reported) and it works

However,
1- This means that tests will never work with prefixes, since we access the APIClass.index.refresh() directly
2- Need to be aware if we ever do something directly on the index
Makes me think if the refresh should be delegated to invenio-indexer, then the IndexRefreshOp gets and indexer as parameter. Avoiding accessing the API classes/indices directly.

Closing this PR in favour of the ones in indexer/records-resources


text:
mappings: add dynamic template for i18n titles and descriptions

closes #246

@slint unfortunately there is nothing like that at the moment. I could add it, but that is extra work that I'm not sure it fits on the current sprint. At the moment we are testing this indirectly, if you pass a normal string here https://github.com/inveniosoftware/invenio-vocabularies/blob/25ba54bbaee5fd89794067b2c34c6bea20e7fc16/tests/conftest.py#L134 it should fail. I could may do that test, but it feels ad-hoc (note that we have this type of dynamic templates also in rdm-records)

Fine with me, was curious because ES mapping errors/mismatches are usually going under the radar, but if there's code that works with the functionality it should be good :)

@slint sample run:
Normal run
@pytest.fixture(scope="module")
def example_data():
    """Example data for records."""
    return {
    ...
        },
        "description": {
            "en": "Publications",
            "da": "Publikationer",
        },
    ...
    }

tests/resources/test_resources_l10n.py::test_get PASSED

Not a dict, this would fail even without dynamic template. The check is dict vs no dict.
@pytest.fixture(scope="module")
def example_data():
    """Example data for records."""
    return {
        ...
        "description": "Publications",
        ...
    }

ERROR tests/resources/test_resources_l10n.py::test_get - marshmallow.exceptions.ValidationError: {'description': ['Not a valid mapping type.']}

Not a string, this is enforced by the template. However, we can only check that is a string we cannot check that is indexed as search_as_you_type
@pytest.fixture(scope="module")
def example_data():
    """Example data for records."""
    return {
        ...
        "description": {
            "en": 123,
        },
        ...
    }

marshmallow.exceptions.ValidationError: {'description': defaultdict(<class 'dict'>, {'en': {'value': ['Not a valid string.']}})}

authors: ppanero slint

repo: inveniosoftware/invenio-vocabularies


text:
BibIndex: optimise term reading phase

Originally on 2013-04-22
Currently, when an index is processed, WordTable is reading values from the database three times: once for words, once for pairs, once for phrases.  With the advancement of index centralisations (see #852), it would be ideal to refactor WordTable into IndexTable so that it would read term values only once and then launch three tokenisations (for words, pairs, phrases).
Here is example of current status: indexing 50 records, see 3 calls for
add_recID_range(), and see 150 calls to get_fields().  This is not necessary.  If we eliminate this, the expected speed up will not be much though, about 10% perhaps.  Still, could help in some cases, like when BibAuthorID is contacted.
$ sudo -u apache /opt/invenio/bin/bibindex -u admin -w year -a -i 1-50 --profile=cumulative

         24561 function calls (24559 primitive calls) in 0.446 CPU seconds

   Ordered by: cumulative time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.001    0.001    0.446    0.446 bibtask.py:897(_task_run)
        1    0.000    0.000    0.385    0.385 bibindex_engine.py:1443(task_run_core)
        3    0.000    0.000    0.351    0.117 bibindex_engine.py:890(add_recIDs)
      588    0.015    0.000    0.265    0.000 dbquery.py:167(run_sql)
        3    0.011    0.004    0.246    0.082 bibindex_engine.py:1004(add_recID_range)
      588    0.022    0.000    0.221    0.000 cursors.py:136(execute)
      588    0.004    0.000    0.182    0.000 cursors.py:316(_query)
      588    0.147    0.000    0.172    0.000 cursors.py:278(_do_query)
        3    0.002    0.001    0.083    0.028 bibindex_engine.py:742(put_into_db)
      150    0.002    0.000    0.079    0.001 bibindex_engine.py:723(get_field)
      326    0.004    0.000    0.056    0.000 bibtask.py:664(write_message)
       69    0.001    0.000    0.046    0.001 __init__.py:1291(info)
       69    0.004    0.000    0.045    0.001 __init__.py:957(info)
        1    0.001    0.001    0.045    0.045 bibtask.py:1146(check_running_process_user)
        1    0.000    0.000    0.044    0.044 bibtask.py:1131(guess_apache_process_user)
        1    0.042    0.042    0.044    0.044 bibtask.py:1114(guess_apache_process_user_from_ps)
       69    0.001    0.000    0.041    0.001 __init__.py:1066(_log)
       69    0.001    0.000    0.033    0.000 __init__.py:1081(handle)
       69    0.001    0.000    0.032    0.000 __init__.py:1110(callHandlers)
      138    0.003    0.000    0.031    0.000 __init__.py:629(handle)
       46    0.001    0.000    0.026    0.001 bibindex_engine.py:827(put_word_into_db)
       46    0.001    0.000    0.024    0.001 bibindex_engine.py:806(load_old_recIDs)
      438    0.013    0.000    0.023    0.000 cursors.py:114(_do_get_result)
      588    0.003    0.000    0.019    0.000 cursors.py:64(__del__)
        6    0.000    0.000    0.018    0.003 bibindex_engine.py:1160(report_on_table_consistency)
       31    0.001    0.000    0.017    0.001 bibtask.py:633(task_update_progress)
      588    0.004    0.000    0.016    0.000 cursors.py:69(close)
      588    0.004    0.000    0.016    0.000 connections.py:234(cursor)
      588    0.006    0.000    0.012    0.000 cursors.py:94(nextset)
      588    0.012    0.000    0.012    0.000 cursors.py:47(__init__)
      567    0.006    0.000    0.011    0.000 connections.py:253(literal)
        3    0.000    0.000    0.010    0.003 bibindex_engine.py:691(__init__)
      138    0.003    0.000    0.010    0.000 __init__.py:720(emit)
       69    0.001    0.000    0.009    0.000 handlers.py:63(emit)
      138    0.004    0.000    0.009    0.000 __init__.py:593(release)
      207    0.001    0.000    0.009    0.000 __init__.py:606(format)
     2640    0.009    0.000    0.009    0.000 cursors.py:131(_get_db)
      438    0.007    0.000    0.008    0.000 cursors.py:314(_get_result)
        3    0.000    0.000    0.008    0.003 search_engine.py:421(get_index_stemming_language)
      207    0.003    0.000    0.008    0.000 __init__.py:392(format)
        3    0.000    0.000    0.008    0.003 data_cacher.py:75(recreate_cache_if_needed)
        3    0.000    0.000    0.008    0.003 search_engine.py:411(timestamp_verifier)
        3    0.000    0.000    0.008    0.003 dbquery.py:349(get_table_update_time)

Closing this issue; the indexing process was optimised by @gszpura in the meantime.

repo: inveniosoftware/invenio


text:
Component properties: order these by concept / group. How do we do this..?

The properties associated with a UI component, shown on the right hand side of the builder, are currently listed in alphabetical order. We suspect it would be better if they were grouped by related concepts, with the most "popular" shown at the top.

The most fundamental group division is between "style" properties (which will become CSS) and "content" properties (which will become HTML). I've written some ideas about this in #73.

authors: mhsmith ntoll

repo: invent-framework/invent


text:
[bug]: _selectFirebaseProject failed with Valid value range is empty: 0

Is there an existing issue for this?

[X] I have searched the existing issues.

CLI Version
0.2.4
Firebase Tools version
11.2.2
Flutter Doctor Output
2022-07-16T04:46:58.7453516Z Doctor summary (to see all details, run flutter doctor -v):
2022-07-16T04:46:58.9449235Z [✓] Flutter (Channel stable, 3.0.4, on Ubuntu 20.04.4 LTS 5.13.0-1031-azure, locale C.UTF-8)
2022-07-16T04:47:06.7762365Z [!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
2022-07-16T04:47:06.7767234Z     ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
2022-07-16T04:47:06.7769712Z [✓] Chrome - develop for the web
2022-07-16T04:47:06.7771139Z [✗] Linux toolchain - develop for Linux desktop
2022-07-16T04:47:06.7777126Z     ✗ ninja is required for Linux development.
2022-07-16T04:47:06.7778024Z       It is likely available from your distribution (e.g.: apt install ninja-build), or can be downloaded from https://github.com/ninja-build/ninja/releases
2022-07-16T04:47:06.7778856Z     ✗ GTK 3.0 development libraries are required for Linux development.
2022-07-16T04:47:06.7779439Z       They are likely available from your distribution (e.g.: apt install libgtk-3-dev)
2022-07-16T04:47:06.7780643Z [!] Android Studio (not installed)
2022-07-16T04:47:06.7781874Z [✓] Connected device (2 available)
2022-07-16T04:47:06.7782979Z [✓] HTTP Host Availability
2022-07-16T04:47:06.7783403Z
2022-07-16T04:47:06.7784280Z ! Doctor found issues in 3 categories.

Description
2022-07-16T04:48:12.8475881Z melos run fire:cli
2022-07-16T04:48:12.8478573Z   └> npm install firebase-tools --location=global && \firebase --version && \dart pub global activate flutterfire_cli && \flutterfire --version
2022-07-16T04:48:12.8483105Z      └> SUCCESS

2022-07-16T04:48:12.8776281Z ##[group]Run flutterfire config --verbose --project=***********-dev --out=lib/config/firebase.dart --ios-bundle-id=***.****.****.dev --macos-bundle-id=***.****.****.dev --android-app-id=***.****.****.dev --platforms=android,ios,macos,web --yes
2022-07-16T04:48:12.8777264Z flutterfire config --verbose --project=***********-dev --out=lib/config/firebase.dart --ios-bundle-id=***.****.****.dev --macos-bundle-id=***.****.****.dev --android-app-id=***.****.****.dev --platforms=android,ios,macos,web --yes
2022-07-16T04:48:12.8831872Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-07-16T04:48:12.8832144Z env:
2022-07-16T04:48:12.8832396Z   FLUTTER_ROOT: /opt/hostedtoolcache/flutter
2022-07-16T04:48:12.8832710Z   PUB_CACHE: /opt/hostedtoolcache/flutter/.pub-cache
2022-07-16T04:48:12.8833433Z   FIREBASE_TOKEN: ***
2022-07-16T04:48:12.8833650Z ##[endgroup]
2022-07-16T04:48:13.1491773Z Unhandled exception:
2022-07-16T04:48:13.1500645Z RangeError (index): Invalid value: Valid value range is empty: 0
2022-07-16T04:48:13.1501391Z #0      _StringBase.[] (dart:core-patch/string_patch.dart:260:41)
2022-07-16T04:48:13.1501888Z #1      Console.cursorPosition (package:dart_console/src/console.dart:324:15)
2022-07-16T04:48:13.1502400Z #2      Console.windowWidth (package:dart_console/src/console.dart:215:32)
2022-07-16T04:48:13.1502868Z #3      Console.writeLine (package:dart_console/src/console.dart:454:23)
2022-07-16T04:48:13.1503332Z #4      Context.writeln (package:interact/src/framework/context.dart:63:14)
2022-07-16T04:48:13.1503813Z #5      _SpinnerState.render (package:interact/src/spinner.dart:107:13)
2022-07-16T04:48:13.1504311Z #6      Component.interact (package:interact/src/framework/component.dart:48:11)
2022-07-16T04:48:13.1504784Z #7      spinner (package:flutterfire_cli/src/common/utils.dart:160:5)
2022-07-16T04:48:13.1505336Z #8      ConfigCommand._selectFirebaseProject (package:flutterfire_cli/src/commands/config.dart:265:37)
2022-07-16T04:48:13.1505878Z #9      ConfigCommand.run (package:flutterfire_cli/src/commands/config.dart:368:43)
2022-07-16T04:48:13.1506366Z #10     CommandRunner.runCommand (package:args/command_runner.dart:209:27)
2022-07-16T04:48:13.1506887Z #11     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:119:25)
2022-07-16T04:48:13.1507317Z #12     new Future.sync (dart:async/future.dart:301:31)
2022-07-16T04:48:13.1507731Z #13     CommandRunner.run (package:args/command_runner.dart:119:14)
2022-07-16T04:48:13.1508486Z #14     main (file:///opt/hostedtoolcache/flutter/.pub-cache/hosted/pub.dartlang.org/flutterfire_cli-0.2.4/bin/flutterfire.dart:57:48)

Steps to reproduce

Set FIREBASE_TOKEN environment variable on CI machine
Install firebase tools and flutterfire_cli
run the following command

flutterfire config --verbose --project=***********-dev --out=lib/config/firebase.dart --ios-bundle-id=***.****.****.dev --macos-bundle-id=***.****.****.dev --android-app-id=***.****.****.dev --platforms=android,ios,macos,web --yes

Expected behavior
Normally I would expect the following
2022-07-15T16:04:01.0082911Z ⠋ Fetching available Firebase projects...
2022-07-15T16:04:04.4314116Z i Found 3 Firebase projects. Selecting project ******-dev.
2022-07-15T16:04:04.4355239Z i Selected platforms: android,ios,macos,web
2022-07-15T16:04:04.4360690Z Warning - android-app-id (-a) is deprecated. Consider using android-package-name (-p) instead.
2022-07-15T16:04:04.4387477Z ⠋ Fetching registered android Firebase apps for project ******-dev
2022-07-15T16:04:06.2317450Z i Firebase android app ***.******.***.dev registered.
2022-07-15T16:04:08.5409345Z ⠋ Fetching registered ios Firebase apps for project ******-dev
2022-07-15T16:04:08.6221743Z ⠙ Fetching registered ios Firebase apps for project ******-dev
2022-07-15T16:04:10.3256623Z i Firebase ios app ***.******.***.dev registered.
2022-07-15T16:04:12.5518488Z ⠋ Fetching registered macos Firebase apps for project ******-dev
2022-07-15T16:04:14.1523603Z ⠋ Fetching registered macos Firebase apps for project ******-dev
2022-07-15T16:04:14.1692232Z i Firebase macos app ***.******.***.dev registered.
2022-07-15T16:04:17.8653748Z ⠋ Fetching registered web Firebase apps for project ******-dev
2022-07-15T16:04:17.9033981Z i Firebase web app method (web) registered.
2022-07-15T16:04:20.0053433Z
2022-07-15T16:04:20.0057158Z Firebase configuration file lib/config/firebase.dart generated successfully with the following Firebase apps:
2022-07-15T16:04:20.0057687Z
2022-07-15T16:04:20.0092908Z Platform  Firebase App Id
2022-07-15T16:04:20.0093544Z web       1:***********:web:**********************
2022-07-15T16:04:20.0094144Z android   1:***********:android:**********************
2022-07-15T16:04:20.0150042Z ios       1:***********:ios:**********************
2022-07-15T16:04:20.0150509Z macos     1:***********:ios:**********************
2022-07-15T16:04:20.0150699Z
2022-07-15T16:04:20.0151135Z Learn more about using this file and next steps from the documentation:
2022-07-15T16:04:20.0151627Z  > https://firebase.google.com/docs/flutter/setup
2022-07-15T16:04:21.0522547Z
2022-07-15T16:04:21.0523242Z melos run fire:dev
2022-07-15T16:04:21.0525398Z   └> melos run fire:cli && \flutterfire config \  --project=******-dev \  --out=lib/config/firebase.dart \  --ios-bundle-id=***.******.***.dev \  --macos-bundle-id=***.******.***.dev \  --android-app-id=***.******.***.dev \  --platforms=android,ios,macos,web,linux,windows \  --yes
2022-07-15T16:04:21.0526536Z      └> SUCCESS
2022-07-15T16:04:21.0788530Z

Screenshots
No response
Additional context and comments
This was working 2-3 days ago. I'm not sure if it has to do with the recent updates with( firebase-tools, flutterfire_cli, Melos ) or recent firebase disruptions

It seems that when I pipe the command with | bash that's causing the issue.

Recent update to dart_console 1.1.0 (deps for interact) is causing the spinner and cursor issue.  It seems to be working fine again after overriding in pubspec.yaml with the lines below and use a dev dependencies to run.
dev_dependencies:
  ...
  flutterfire_cli: ^0.2.4

dependency_overrides:
  dart_console: 1.0.0

flutter pub run flutterfire_cli:flutterfire configure ...

I have yet to file an issue in dart_console

@timsneath is there anything you can help with?

I'll take a look. Thanks for flagging!

I think I've fixed this in 1.1.2. Could you take a look and see if this solves your issue?

@timsneath awesome, thank you! All works for me now

It's working for me too!

authors: TatsuUkraine thipokch timsneath


text:
Summon round wooden tables for startup poker and family dinner

Waiting on these
https://jerseyshore.craigslist.org/fuo/d/great-4th-of-july-rustic/6623868558.html
We could also scout out local electrical supply companies.

https://newyork.craigslist.org/brk/fuo/d/outdoor-table-and-chairs/6704561031.html

it's too cold now for winter rooftop events. we'll try again in the spring.

authors: cryptogoth varungpta

repo: invisible-college/arcology-website


text:
[enhancement]: Reuse seed when outpainting

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
When outpainting in the unified canvas, if using a random seed, it would be nice to retrive the last seed used in case one likes the result but want to give it more saples or do a minor promt ajustment.
Alternatives
No response
Aditional Content
No response

Seeds at different sizes would not extend the underlying noise, so don't think this would address the underlying ask

authors: Botoni hipsterusername

repo: invoke-ai/InvokeAI


text:
feat(ui): support disabledFeatures, add nicer loading

disabledParametersPanels -> disabledFeatures
handle disabling faceRestore, upscaling, lightbox, modelManager and OSS header links/buttons
wait until models are loaded to hide loading screen
also wait until schema is parsed if nodes is an enabled tab
secret loading screen dismissal button @ top right corner

This all needs to be refactored to support other config things like generation limits (size, steps, iterations, etc.). Marked as draft for now while I work on it.

actually nvm, wanna get this and the img2img merged before working on the config stuff


text:
🛑 Bitwage API (Sandbox) is down

In 99ffc11, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 333 ms

Resolved: Bitwage API (Sandbox) is back up in c35a377 after 6 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 96379c8, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 331 ms

Resolved: Bitwage API (Sandbox) is back up in 03d2da4 after 58 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In d6ed077, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 290 ms

Resolved: Bitwage API (Sandbox) is back up in 7115a9a after 1 hour, 6 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In dc14647, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 72 ms

Resolved: Bitwage API (Sandbox) is back up in 58b6bb2 after 7 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In ac35cc4, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 316 ms

Resolved: Bitwage API (Sandbox) is back up in 2b50f54 after 27 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 994c69e, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 358 ms

Resolved: Bitwage API (Sandbox) is back up in b15315a after 17 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In bf5ecaf, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 81 ms

Resolved: Bitwage API (Sandbox) is back up in 7915dbc after 11 minutes.


text:
Zigbee Offline Geräte werden nicht erkannt

zigbee geräte werden nicht erkannt.
in der experteneinstellung habe ich den timout auf 180min gestellt. leider ohne erfolg. das gerät selber zeigt online an und hat auch eine signalstärke im datenpunkt (10) obwohl es definitiv nicht online ist.
kann man auf die letzte änderung im datenpunkt reagieren?
was macht diese einstellung in der experteneinstellung genau?

Gibt es hier schon was neues wegen dem Status?  Warum die Zeiteinstellung nicht geht ? Oder kann einer sagen wann ein Gerät als Offline gewertet wird. Wäre ja super wenn man es selber bestimmen kann .

Weiss nicht, was ihr fuer Adapter und Versionen habt, schreibt ja keiner.. aber hier funktionierts. (ich schreib auch nicht, wie es geht, muesst ihr ja nicht wissen, ich will auch nicht wissen, warum es bei euch nicht geht :) :)
Ist definitiv kein Issue hier da wichtige Angaben fehlen und kann ignoriert und geschlossen werden.

Adapter Device Watcher: 2.12.1
JS: 6.0.11
admin:7.1.5
node: 18.20.4
linux
Was soll das letzte sein wie finde ich das ?
Hoffe kann mit diesen Informationen weiter helfen? Wäre echt super falls es klappen würde das der z.b,. nutze ich aktuell wenn er 3 Std keine Aktualisierung der batterie erkennt auf Fehler geht, bei meinem Skript. Dieser Adapter würde das ganze Vereinfachen. Und da man in einer anderen Gruppe gelesen hat das der Adapter nicht zuverlässig sei bei Offline Geräten erkundige ich mich ja hier, denke dafür soll es da sein wenn solche Probleme sind. MFG

nee, da fehlen noch zuviele Angaben.

Welcher Zigbee Adapter, welche Version ist installiert?
o/s ist das Betriebssystem, also linux ist sehr allgemein, welches, welche Version?

Und Debug Log providen.
Viele Devices senden nur alle 24h einen Batterie state, kommt aber auf das Device an.
Bitte mehr Details

Nutze Deconz Adapter.
Deconz: 1.4.1
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Ja das kann sein das manche Geräte nur alle 24 Std sich melden wenn ich aber dann eingebe nach 5 Std offline soll der sich melden müsste der ja auftauchen passiert aber nicht. Deshalb war ja nur die Frage mit welchen Wert Offline geprüft wird und welche Zeit.
Wo finde ich den Debug Log ?  in dem auf dem System  unter Protokoll steht ja nichts.


text:
Unknown update for type "relative_rotary"

v3.9.2
Hue_tap_dial_switch
2023-06-13 23:16:56.454  - warn: hue.0 (29629) Unknown update for type "relative_rotary": {"id":"96b48aea-ae4f-4381-a550-4b95d01d246d","id_v1":"/sensors/124","owner":{"rid":"54b90d5c-eb21-41c7-a358-c3295e931d41","rtype":"device"},"relative_rotary":{"last_event":{"action":"start","rotation":{"direction":"counter_clock_wise","duration":400,"steps":15}},"rotary_report":{"action":"start","rotation":{"direction":"counter_clock_wise","duration":400,"steps":15},"updated":"2023-06-13T21:16:54.675Z"}},"type":"relative_rotary"} 2023-06-13 23:16:56.456  - warn: hue.0 (29629) Unknown update for type "relative_rotary": {"id":"96b48aea-ae4f-4381-a550-4b95d01d246d","id_v1":"/sensors/124","owner":{"rid":"54b90d5c-eb21-41c7-a358-c3295e931d41","rtype":"device"},"relative_rotary":{"last_event":{"action":"repeat","rotation":{"direction":"counter_clock_wise","duration":400,"steps":15}},"rotary_report":{"action":"repeat","rotation":{"direction":"counter_clock_wise","duration":400,"steps":15},"updated":"2023-06-13T21:16:55.102Z"}},"type":"relative_rotary"}

Can you show me the objects created for a rotary switch, then I can maybe update them on push too

Edited my first post.

directions:
clock_wise
counter_clock_wise

See also:
https://github.com/iobroker-community-adapters/ioBroker.hue/issues/368

Can you show me the objects created for a rotary switch, then I can maybe update them on push too

See my PR.


text:
Time difference

any idea how i can fix this:
(2175) Time difference between Mihome Vacuum and ioBroker: -1588470200 sec

same message here

Same problem for me with a new S5 MAX. I'm not able to connect with the robot.

(5173) no answer received after after 3 times -> pause miIO.info from request parameters, try again in one hour

I get this, if my robot has no connection to internet, which I wan't. SO if your robbot is connected via Internet to the china server, the time differnece warning is gone.

Can we close this issue?

haven't seen it in a while .. so IMO yes

authors: EddyDsSmartHome daniel-lo dirkhe linchen4000


text:
Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter plex for common errors and appropiate suggestions to keep this adapter up to date.
This check is based on the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.plex
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E184] "common.subscribe" will be removed with js-controller >= 6. Please remove from io-package.json and adapt code if required.
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2024 zefau zefau@mailbox.org" at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019-2024 zefau zefau@mailbox.org" at the start of LICENSE
[X] :heavy_exclamation_mark: [E804] Please process issue [#345] "Compatibility check and testing for node.js 22"

WARNINGS:

[X] :eyes: [W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[X] :eyes: [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

[ ] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Tue, 03 Dec 2024 15:48:45 GMT based on commit 2edd99000c6e6dd6428c0b5a4b3f400608a72602
ioBroker.repochecker 3.2.2

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E955] iob_npm.done not found in .npmignore
:thumbsup:Thanks for fixing the issues.

@iobroker-bot recheck

@ioBroker-Bot recheck

@iobroker-bot recheck

@iobroker-bot recreate

@ioBroker-Bot recreate

authors: ioBroker-Bot mcm1957 ticaki


text:
Adapter crashes after sending picture to bot

After update Node.JS to recommended version 14.18.1 telegram instance crashes after sending bot a picture in privat chat.
With previous version 12.22.7 there were no problems.
Node.js v14.18.1
NPM 6.14.15
Telegram 1.10.0
JS-Controller 3.2.16
ioBroker on RaspberryPi 4G
Logfile:
2021-11-19 11:26:59.415 - error: telegram.0 (16973) Exception-Code: ERR_INVALID_ARG_TYPE: The "listener" argument must be of type function. Received type boolean (true)
2021-11-19 11:26:59.525 - error: telegram.0 (16973) uncaught exception: The "listener" argument must be of type function. Received type boolean (true)
2021-11-19 11:26:59.525 - error: telegram.0 (16973) TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received type boolean (true)
at new NodeError (internal/errors.js:322:7)
at checkListener (events.js:135:11)
at _addListener (events.js:433:3)
at IncomingMessage.addListener (events.js:497:10)
at IncomingMessage.Readable.on (internal/streams/readable.js:853:35)
at ClientRequest. (/opt/iobroker/node_modules/iobroker.telegram/main.js:1050:21)
at Object.onceWrapper (events.js:520:26)
at ClientRequest.emit (events.js:400:28)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
at TLSSocket.socketOnData (_http_client.js:515:22)
at TLSSocket.emit (events.js:400:28)
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

Same problem with JS-Controller 3.3.22 and Admin 5.2.2.
Has anyone an idea of this problem?

Fixed in 1.11.0

Installed version 1.11.0 but same problem with another error
host.raspberrypi
2022-01-26 23:38:15.815	info	instance system.adapter.telegram.0 started with pid 2324
host.raspberrypi
2022-01-26 23:37:45.741	info	Restart adapter system.adapter.telegram.0 because enabled
host.raspberrypi
2022-01-26 23:37:45.740	error	instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

telegram.0
2022-01-26 23:37:45.105	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

telegram.0
2022-01-26 23:37:44.720	error	Exception-Code: HPE_CB_HEADERS_COMPLETE: Parse Error: User callback error

telegram.0
2022-01-26 23:37:44.719	error	Error: Parse Error: User callback error at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

telegram.0
2022-01-26 23:37:44.716	error	uncaught exception: Parse Error: User callback error

telegram.0
2022-01-26 23:37:44.713	error	Exception-Code: ERR_INVALID_ARG_TYPE: The "listener" argument must be of type function. Received type boolean (true)

telegram.0
2022-01-26 23:37:44.712	error	TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received type boolean (true) at new NodeError (internal/errors.js:322:7) at checkListener (events.js:135:11) at _addListener (events.js:433:3) at IncomingMessage.addListener (events.js:497:10) at IncomingMessage.Readable.on (internal/streams/readable.js:853:35) at ClientRequest.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/main.js:1058:25) at Object.onceWrapper (events.js:520:26) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

telegram.0
2022-01-26 23:37:44.711	error	uncaught exception: The "listener" argument must be of type function. Received type boolean (true)

telegram.0
2022-01-26 23:37:44.610	error	Exception-Code: HPE_CB_HEADERS_COMPLETE: Parse Error: User callback error

telegram.0
2022-01-26 23:37:44.609	error	Error: Parse Error: User callback error at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

telegram.0
2022-01-26 23:37:44.608	error	uncaught exception: Parse Error: User callback error

telegram.0
2022-01-26 23:37:44.607	error	Exception-Code: ERR_INVALID_ARG_TYPE: The "listener" argument must be of type function. Received type boolean (true)

telegram.0
2022-01-26 23:37:44.606	error	TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received type boolean (true) at new NodeError (internal/errors.js:322:7) at checkListener (events.js:135:11) at _addListener (events.js:433:3) at IncomingMessage.addListener (events.js:497:10) at IncomingMessage.Readable.on (internal/streams/readable.js:853:35) at ClientRequest.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/main.js:1058:25) at Object.onceWrapper (events.js:520:26) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

telegram.0
2022-01-26 23:37:44.605	error	uncaught exception: The "listener" argument must be of type function. Received type boolean (true)

telegram.0
2022-01-26 23:37:44.600	error	Exception-Code: HPE_CB_HEADERS_COMPLETE: Parse Error: User callback error

telegram.0
2022-01-26 23:37:44.599	error	Error: Parse Error: User callback error at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

telegram.0
2022-01-26 23:37:44.598	error	uncaught exception: Parse Error: User callback error

telegram.0
2022-01-26 23:37:44.590	error	Exception-Code: ERR_INVALID_ARG_TYPE: The "listener" argument must be of type function. Received type boolean (true)

telegram.0
2022-01-26 23:37:44.589	error	TypeError [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type function. Received type boolean (true) at new NodeError (internal/errors.js:322:7) at checkListener (events.js:135:11) at _addListener (events.js:433:3) at IncomingMessage.addListener (events.js:497:10) at IncomingMessage.Readable.on (internal/streams/readable.js:853:35) at ClientRequest.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/main.js:1058:25) at Object.onceWrapper (events.js:520:26) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

Fixed in 1.11.1

Works! 👍 Thank you

authors: GermanBluefox LastPerfectTobi


text:
White screen while using iframe on iOS

Hi,
I am trying to embed google maps embed api, but getting white screen. I am not getting errors in console and also not in the network tab.
Issue is only for iOS and not on android.
My Ionic info:-
macbook-pro:~ Tushar$ ionic info
[WARN] You are not in an Ionic project directory. Project context may be
       missing.

Ionic:

   Ionic CLI : 5.2.4

Utility:

   cordova-res : 0.6.0
   native-run  : 0.2.8

System:

   NodeJS : v10.15.0
   npm    : 6.4.1
   OS     : macOS Mojave

macbook-pro:~ Tushar$

Webview version

    <plugin name="cordova-plugin-ionic-webview" spec="^4.1.1">
        <variable name="ANDROID_SUPPORT_ANNOTATIONS_VERSION" value="27.+" />
    </plugin>

Thanks

+1

Try adding on your config.xml

Can the @deliverymanager method be used?
OR While the white screen You try tapping the screen a couple of times. It will show you the webpage.

Try adding on your config.xml
<allow-navigation href="*" />

It works fine But after I added it I can not open all links with https://
Has anyone come across this?

i am also facing the same issue. White screen on iframe . Althouht added sandbox allow properties and  in config.xml, but still no  luck. Does anyone any suggestions.?

@Singh-KiaTec
In config.xml under <platform name="ios"> add (NOTE this allows everything)
<access allows-arbitrary-loads-in-media="true" allows-arbitrary-loads-in-web-content="true" allows-local-networking="true" origin="*" />
Also, try running the iOS app in the simulator and open up Safari Web Inspector (Enable the Develop menu in Safari then go to Develop > Simulator > App - localhost) and check if you have any error messages...
Also, see #477

@developerjohan01
Thanks for the quick response. and the help. :)
Basically we have iframe loginpage and it does some user login stuff and navigates to a successapage and then sucesspage emits  window.parent.postMessage and the app take those and continue the logic.
Now after  loginpage it navigates to successapage within iframe  and then sucesspage throws error Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Strange thing this happens only for IOS 13.1.x versions.

Tried the  , still no luck for IOS 13.1.x versions.

Just for the information is someone has the same issue with iOS 13.1.1 and iPadOS 13.1.1
sandbox properties issue as per ios release notes.
Impact: Third party app extensions may not receive the correct sandbox restrictions
https://support.apple.com/en-gb/HT210624

those are whitelist problems, you have to allow navigation to external iframes or they won't work, not related to the plugin

repo: ionic-team/cordova-plugin-ionic-webview


text:
The toggle component is easily triggered in scrolling up and down

(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[X] feature request
Current behavior:
The toggle component is easily triggered in scrolling up and down
Expected behavior:
The code does not add a judgment to the Y axis,
resulting in the upper and lower sliding time will trigger

Hello! Thank you for opening an issue with us! Would you be able to provide a sample application via GitHub that demonstrates the issue you are having?
I have a sample app with a page that is nothing more than a list of toggles, and it does not have this issue, so I cannot duplicate.
Thanks for using Ionic!

My page has multiple toggle buttons. When I scroll down the page, if my hand touches the toggle button at the beginning, the button will be triggered, but my finger is actually doing it up and down. Slide the action.
The reason for this problem is that the toggle button does not judge the change in the Y coordinate, and the upper and lower slips are judged to be the switch action.

Here is the app I am using to test:
https://github.com/kensodemann/test-bed-tabs
Go to the "About" tab and then "Open Child One" (use either button). That opens just a list of toggles.
I can easily scroll on without triggering the toggle. Maybe if I start the scrolling by actually touching a toggle off to the right, but I shouldn't do that unless I intend to trigger the toggle.
If you are seeing some different behavior, please provide a sample application demonstrating what you are experiencing.

@kensodemann @coloz could this be related to #12872 and #12260?

@tradeli yes, #12260 is similar

authors: coloz kensodemann tradeli

repo: ionic-team/ionic


text:
bug: Problem with Angular 9 + Ionic 5

Bug Report
Ionic version:
[x] 5.x
Current behavior:
When run ionic serve the app doesn't work

Steps to reproduce:
I try upgrade with follow steps:

ng update @angular/cli@8 @angular/core@8
npm install @ionic/angular@latest @ionic/angular-toolkit@latest --save
ng update @angular/cli @angular/core`

Ionic info:
   Ionic CLI                     : 6.1.0 (/usr/local/lib/node_modules/@ionic/cli)
   Ionic Framework               : @ionic/angular 5.0.0
   @angular-devkit/build-angular : 0.900.1
   @angular-devkit/schematics    : 9.0.1
   @angular/cli                  : 9.0.1
   @ionic/angular-toolkit        : 2.1.2

Ng version
@angular-devkit/architect         0.801.2
@angular-devkit/build-angular     0.900.1
@angular-devkit/build-optimizer   0.900.1
@angular-devkit/build-webpack     0.900.1
@angular-devkit/core              9.0.1
@angular-devkit/schematics        9.0.1
@angular/cli                      9.0.1
@ngtools/webpack                  9.0.1
@schematics/angular               8.3.25
@schematics/update                0.900.1
rxjs                              6.5.4
typescript                        3.7.5
webpack                           4.41.2

my tsconfig.app.json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    "types": []
  },
  "include": [
    "src/**/*.ts"
  ],
  "exclude": [
    "src/test.ts",
    "src/**/*.spec.ts"
  ]
}

Thanks for the issue. Can you provide a repo with the code required to reproduce this issue?

Maybe it's not working because Ionic doesn't support Angular 9 yet?

@nicobytes  I feel like the latest version of Ionic still handles up to Angular 8 (as tried to create any project lets me make only Angular 8 projects). If I try to make a blank app and update with the instructions you provided it compiles without any issues. Can you try  rm -rf ./node_modules && npm i && ionic serve ?

I have the same issue.
Is there any official way to add new project and then upgrade into angular v9? or the templates will be updated to default have angular v9?

You can upgrade an app to Angular 9 by running ng update @angular/core @angular/cli.
The starter apps currently ship with Angular 8 and will be updated to ship with Angular 9 by default soon.

authors: NikolaPeevski fristys liamdebeasi nicobytes nourkrimesh


text:
Added auth check for fund

Added auth check for supply and borrow. In all chains except NEON, user should be authorized to supply or borrow and this should be checked before any actions.In NEON, every user is allowed to do any actions by default.
Tested:
0x8982aa50bb919E42e9204f12e5b59D053Eb2A602: doesn't show auth message for borrow
0x2924973E3366690eA7aE3FCdcb2b4e136Cf7f8Cc: shows auth message for borrow
For supply, it doesn't show msg because all accounts are allowed to supply in chapel

Ok, let's fix CI now

Ok, let's fix CI now

https://github.com/ionicprotocol/monorepo/actions/runs/5936041680/job/16095648676?pr=63
Isn't this related to npm token?

Ok, let's fix CI now

https://github.com/ionicprotocol/monorepo/actions/runs/5936041680/job/16095648676?pr=63
Isn't this related to npm token?

No, it isn't

authors: carlomazzaferro smartdevcom

repo: ionicprotocol/monorepo


text:
v5.7.2 does not work

Describe the bug
v5.7.2 does not work in vscode.

No icon in side bar
No intellisense
No popup when mousing over a value
Trying Alt+Enter gives command 'fsi.SendSelection' not found

I saw another user having the same issue in the editor_support Slack channel.
Steps to reproduce

Open an existing fsx file.
Mouse pointer over a value does not show the popup.
Highlight some code and press Alt+Enter.

Expected behaviour

Icon in side bar
Insellisense
Popup when hovering over a value
Alt+Enter should run the selected code in FSI

Machine info

OS: Windows 10 10.0.19043 Build 19043
.NET SDK version: 5.0.400]
Ionide version: 5.7.2
VSCode version: 1.60.0 (user setup)

Additional context
Reverting to v5.7.1 resolves the issue.

yeah same here. 5.7.2 seems to be broken somehow /cc  @baronfel @Krzysztof-Cieslak

At least it's not only me, I thought I messed too much with these extensions and was crazy removing and reinstalling VS Code. @Krzysztof-Cieslak says here the update is working for him 😕 https://github.com/fsharp/FsAutoComplete/pull/830#issuecomment-916771216
Weird thing is the VS Code logs don't say anything.

I tried by adding a debugger to the "activate" function of Ionide and running an Extension host and did get some errors about missing modules (like "Cannot find module bufferutil") although the stack didn't include Ionide code so not entirely sure if the errors were caused by it. Can it happen that in some machines these missing modules are installed globally and that's why the update works?

I have the same problem. Reverting to 5.7.1 still works however.

Now properly debugging after building this repo. Still not sure what the problem is, but it seems the extension hangs when trying to run cmd /C where dotnet.exe to find the path of dotnet in windows. The "exit" event in the spawned process is never called (nor "close" apparently).

Thanks, this is probably a result of some typing definition updates that came along with the FSAC update. I'll work on rolling those back early this morning and releasing a new version. Gotta get some coffee first though!

Just the change from #1579 makes 5.7.2 work on my computer. Now you ask me why it was working before... I have no idea.
As an aside, in this helper the options set at the top are not being

5.7.3 is rolling out now, and @alfonsogarciacaro I've also made the suggested fix to the helpers - thanks for that spot!

I can confirm. It's fixed for me. Thanks folks

v5.7.3 is working fine for me. Thanks for the quick response!

v5.7.3 still not working on Ubuntu for me, should I open another issue?

authors: akemimadoka alfonsogarciacaro baronfel forki mrboring shazmodan

repo: ionide/ionide-vscode-fsharp


text:
Failed to start language services. Please check if Microsoft Build Tools 2013 are installed

After a recent Ionide upgrade, I am getting the following message "Failed to start language services. Please check if Microsoft Build Tools 2013 are installed". I do not have Build Tools 2013, but I do have Build Tools 2015, and I thought that was the requirement as per the [Readme: Quick Install instructions] https://github.com/ionide/ionide-vscode-fsharp#quick-install-guide.
...I also wonder whether it is related to https://github.com/ionide/ionide-vscode-fsharp/issues/577
OS Version
Windows 10 1511
.NET Framework Version
4.6.1
.NET Core Version
2.0
Ionide Version
3.11.0
Here is the F# Language Service (server) output
Running: C:\Users\cax9124\.vscode\extensions\Ionide.ionide-fsharp-3.11.0/bin/fsautocomplete.exe --mode http --port 8919 --hostPID=9156
spawn C:\Users\cax9124\.vscode\extensions\Ionide.ionide-fsharp-3.11.0/bin/fsautocomplete.exe ENOENT

Here is the F# Language Service output
[11:22:18 ERROR] Failed to start language services. spawn C:\Users\cax9124\.vscode\extensions\Ionide.ionide-fsharp-3.11.0/bin/fsautocomplete.exe ENOENT

Launching vs code from command line inside project dir did not make a difference

Please check if the file C:\Users\cax9124\.vscode\extensions\Ionide.ionide-fsharp-3.11.0/bin/fsautocomplete.exe for sure exists. If not try reinstalling extension (and make sure that antivirus or something like that is not messing with installation)

You were correct, fsautocomplete.exe was missing and the issue went away after re-installing the extension (did not have to adjust antivirus so it must have been a botched extension update). Appreciate your help.

I just got a similar message suddenly.  Was working earlier today and then restarted vscode on a project and it was gone.  i suspect maybe antivirus took it out (avast loves to stomp on fsautocomplete.exe for some reason), but I didn't see it warn me.   Would be nice if the project startup could diagnose this more specifically.  The message MSbuild tools 2013 missing is a real red herring

This is happening for me after the latest VSCode update. fsautocomplete.exe exists in the extensions directory. Have tried reinstalling ionide too.
VSCode info:
Version: 1.31.0 (user setup)
Commit: 7c66f58312b48ed8ca4e387ebd9ffe9605332caa
Date: 2019-02-05T22:35:56.624Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.15063

Checking the Language Server log shows:
...
It was not possible to find any compatible framework version

The specified framework 'Microsoft.NETCore.App', version '2.1.0' was not found.

  - Check application dependencies and target a framework version installed at:

      \

  - Alternatively, install the framework version '2.1.0'.

Looks like the minimum version is now .NET Core 2.1.0? Not sure how this changed, but it was working before VSCode updated itself this morning for me.

This is probably related to this PR: https://github.com/fsharp/FsAutoComplete/pull/335

Installing .NET Core runtime > 2.1 (2.1.7) solved this for me. The MSBuild tools message is very confusing. Also annoying that Visual Studio Installer doesn't let you select a version of the runtime to install. 🙄

Yes, I think I've silently upgraded the .Net Core requirement, sorry for that. And we definitely should have a better error message in this case. PRs welcomed? ;-)

authors: Krzysztof-Cieslak MangelMaxime daz10000 lambdakris tymokvo


text:
Kiwi Browser on Android

Expected Behavior

Extension settings wont remember selection of additional search engines

In extension list uBlacklist has this error

Actual Behavior
Extension is not supported on Google chrome, some extensions are like this, but most are supported. I installed it from zip (Kiwi allows it). It works as expected, but only on Google, not Bing or Brave (no block site button at all, no blocking sites from the list). I tested different versions, all 8.0 are same, 7.0 do not works at all, no 'block site' button. I currently have 8.2.7 installed.
Specifications

Browser: Kiwi Browser
Other extensions/add-ons: uBlock Origin

I found it is browser issue, not an extension. Installed it in Lemur Browser via Chrome Store and everything works fine, sync works as well.

repo: iorate/ublacklist


text:
[Subtask]: Design new send flow as preparation for stardust

Task description
As there will be multiple sending flow for stardust based networks we need to update the sending flow so that the user can easily send IOTA and other assets, while making use of the feature blocks available in the extended output.
Requirements
Design / update design for existing transaction flows:

Send IOTA >= 1Mi
Send IOTA < 1Mi
Add a cancelation date to a transaction
Confirm the storage deposit on a transaction that requires one
Add a public reference to a transaction

Acceptance criteria
Design approved by epic owner / product owner
Creation checklist

[X] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Just missing a custom date picker, hopefully we can find one on the internet to make it easy.

repo: iotaledger/firefly


text:
[Bug report]: FireFly Shimmer Crash when sending Tx

Platform
Desktop
Version
2.0.0.0
Description
When creating a Send TX in FireFly Shimmer, if the first character entered in the Shimmer Amount field is a decimal "." and not a "0", upon moving to the next field, Firefly hangs indefinitely. Simple restart clears issue. Issue doesn't exist if the first character in the number field is a "0"
This occurs on both internal tx and regular send tx.
ie ".0123" vs "0.0123"
Expected behaviour
Expected behavior is any of the following while going to the next step in the workflow:

intelligently auto corrects " .0123" to "0.0123"
prevents going to next field unless format condition is satisfied

Actual behaviour
FireFly UI freezes and must be re-launched.

Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
Launch Firefly
Enter Pin -> Log into profile
Click "Send Funds"
Enter ".0123"
Click Recipient Field
FireFly Hung
Operating System
Windows
Diagnostics
C:\Users\micha\Desktop\IOTA - NFT, Pioneer, Projects\FireFly_Shimmie_Diags.png

Developer Profile
No
Profile Type
Software (Stronghold)
Staking
Never staked
Crash Status
Non-responsive
Error Messages
UI Freezes N/A
Error Logs
No known logs or errors

Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Diagnostics
Version
Language: en
Currency: USD
Node list: https://api.shimmer.network
Platform: win32
Platform Architecture: x64
CPU Count: 4
Total Memory: 16332.3 MB
Free Memory: 7947.8 MB


text:
hotfix: bump wallet-rs to latest commit

Description of change
Currently we are experiencing issues with syncing wallets, and I can not reproduce the issue. However, after exploring and comparing previous releases and commits, as well as discussing with the affected users. I am confident that this issue is in wallet.rs or the way we call the syncAccounts / syncAccount api mixed with the change to wallet.rs. Additionally, wallet.rs have since made a change to default the start address index for syncing accounts to 0 instead of the latests. So if we bump the version I am hoping it will fix the issue.
Because 1.3.1 and 1.3.2 where not merged into main, you can see the accurate diff here: https://github.com/iotaledger/firefly/compare/desktop-1.3.2...bfe8f2258df182a50b4498fe1e5c962738602ffa
Links to any relevant issues
Resolves https://github.com/iotaledger/firefly/issues/2110
Type of change
Choose a type of change, and delete any options that are not relevant.

Fix (a change which fixes an issue)

How the change has been tested
Describe the tests that you ran to verify your changes.
Tested that the wallet compiles, going to test with a user if this fixes their issue before I convert from draft.
Edit: Now tested with user with bug and they no longer have any issues. Currently being tested by closed testing and mods.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
Change checklist
Add an x to the boxes that are relevant to your changes, and delete any items that are not.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that my latest changes pass CI tests
[ ] New and existing unit tests pass locally with my changes

Received a stable commit of wallet.rs team and have tested with 1 user who had the balance bug, and it is now resolved.

Because 1.3.1 and 1.3.2 are not merged into main, you can see an accurate diff of the PR here: https://github.com/iotaledger/firefly/compare/desktop-1.3.2...bfe8f2258df182a50b4498fe1e5c962738602ffa


text:
Create an index on protocol version in ProtocolUpdatesCollection

Now (#729) that we access the protocol parameters frequently it might make sense to have an index on the version.

It seems unlikely that this will ever be a performance concern, so maybe we should hold off?

Yeah, especially now that we don't use the parameters that often anymore.

authors: Alexandcoats grtlr

repo: iotaledger/inx-chronicle


text:
🛑 备用KMS激活服务器 01 is down

In c1ac92f, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 12ba7ca after 16 minutes.

repo: iougemini/ikms-uptime


text:
🛑 备用KMS激活服务器 01 is down

In 2e5b840, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 4737a62 after 16 minutes.


text:
🛑 备用KMS激活服务器 11 is down

In ebadd8e, 备用KMS激活服务器 11 (s01.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 11 is back up in e9fcf8c after 13 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In 160fac2, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in e2899df after 9 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In 64e40c6, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 3edd39a after 11 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In 4e43f4c, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 1750259 after 11 minutes.


text:
Cleanup entry information in UserProfile

This is about cleaning up
    // TODO: we really need to clean this up and rethink what we expose where
    // but that would be a breaking change... let's aim for 0.6
    this.entriesCountProducer = new DefaultValueProducer(this.keyring.getEntries().length);
    this.entriesCount = new ValueAndUpdates(this.entriesCountProducer);
    this.entryLabelsProducer = new DefaultValueProducer(UserProfile.labels(this.keyring.getEntries()));
    this.entryLabels = new ValueAndUpdates(this.entryLabelsProducer);
    this.entryIdsProducer = new DefaultValueProducer(UserProfile.ids(this.keyring.getEntries()));
    this.entryIds = new ValueAndUpdates(this.entryIdsProducer);

From the caller's perspective we have right now the data (simplified, yaml style):
- entriesCount: 3
- entryLabels:
  - "first address"
  - undefined
  - "Savings for bad times"
- entryIds:
  - "ohb9Eufedoo7"
  - "iR4kei9ooF6g"
  - "aoki6Aeph2se"

all those three properties can (and must) be queried explicitly and adding an entry emits 3 different events (count updated, labels updated, ids updated) with inconsistent data between those 3 events (e.g. count becomes 4 but the 4th entry label not yet available).
To simplify this, I propose the following structure
- entries:
  - label: "first address"
    id: "ohb9Eufedoo7"
  - label: undefined
    id: "iR4kei9ooF6g"
  - label: "Savings for bad times"
    id: "aoki6Aeph2se"

This gives us an interface, where the individual entries are represented as an immutable interface like
interface EntryInfo {
    readonly id: KeyringEntryId;
    readonly label: string | undefined;
}

and count is taken from the length of the entries array.

I like this format.
I would also add the index explicitly in the Entry Info, so we can make an update stream later. Index is implicit in the array, but it is important for displaying them in proper order and I would like to add it even if it appears a bit redundant at first.

This will be implemented as a stream of arrays, just like we have now:
public readonly entries: ValueAndUpdates<ReadonlyArray<EntryInfo>>;

so with every update, you get a new list. The order is always preserved due to the underlying data structure. Using IDs, we are able to access specific entries where needed. Given that, I don't see why we should have the index as a separate field.

Okay, just thinking that maybe we would want to update this to diffs, but the number of entries should never get above a dozen or so, where we would want that optimization

repo: iov-one/iov-core


text:
New BPF compiler backend

This ticket tracks the creation of a new compiler backend for bpftrace to replace LLVM.
What's wrong with LLVM?
LLVM produces great bytecode, but it is a very large library. This makes it difficult to use bpftrace on low-resource systems.
Goals of new compiler backend

Small compiled size on disk
Low runtime memory usage
Reasonable BPF code generation
Faster compilations than LLVM as currently used. We'll have far fewer abstractions and optimisation passes, so we'd better be faster!

These are vague goals but hopefully will help guide us as we start implementing. The idea is to be a minimal compiler backend that can still produce reasonable BPF bytecode. It does not need to support all features of LLVM or produce optimal BPF bytecode.
Implementation

A BPF-specific intermediate representation (IR)

Three Address Code, Single Static Assignment IR
Nodes directly mapping to each BPF instruction (load, add, branch, etc.)
Minimal abstractions as there is only a single target and few users of this backend

LLVM IR generation

This will allow us to convert bpftrace over to using the new API before the entire backend is ready, which may let us spot things we haven't thought of
Gives bpftrace the option to use LLVM when available to produce potentially more efficient BPF programs, without us having to maintain two separate "codegen_xxx.cpp" files

Passes over IR

Register allocation
Stack allocation
"mem2reg"
Convert 3-address instructions to 2-address instructions
Other optimisation passes TBD

BPF code generation

Some optimisations are absolutely required, such as on memory placement to avoid blowing the stack, so direct BPF-bytecode emission without an IR is not an option.

Would be great if we could offer it as library other projects can use. That way they can target our IR and use it as an easier way to get LLVM or our compiler as light weight target.

Would be great if we could offer it as library other projects can use. That way they can target our IR and use it as an easier way to get LLVM or our compiler as light weight target.

As long as we:

have a cmake target that supports building a .so or .a + installing library and header file
be careful with what we put in the bpfir headers

it should be pretty easy

The idea is to be a minimal compiler backend that can still produce reasonable BPF bytecode.

I think this issue is vastly understating how difficult such a backend is.
BPF is not just the bytecode. To use modern features, you need ELF output, BTF output, BTF.ext output, full relocation support, potentially CO-RE support, and even btf_tag support. This is a lot of work to redo from scratch - it can be done but at what (opportunity) cost?
LLVM comes with active developers of the BPF backend and lots of documentation, which significantly lowers the barrier to entry. It manages to produce reasonable code out of less-than-reasonable IR in a lot of cases, which is also no small feat.
There are things I'd want from a BPF-specific backend (in particular, knowledge about the constraints on helper arguments - ARG_PTR_TO_STACK etc). However, they definitely don't outweigh the current benefits LLVM brings to the table.
Besides, bpftrace uses clang to parse types - without also reimplementing that, LLVM is still a transitive dependency.
Lastly, without a concrete size target, we can't reasonably evaluate shrinking the current build down first. E.g., maybe if we kill the ORC usage and construct the passes manually instead of using the defaults, we can remove a bunch of code? There are a lot of levers that would ideally be exhausted first before any work starts on a new backend. I'd be happy to read about previous efforts in this space if the consensus is that the needle is immovable.
My primary question here is, what are the target environments where size is prohibitive and what is the desired binary size for these environments?

authors: BurntBrunch ajor danobi fbs

repo: iovisor/bpftrace


text:
Replace ++ and -- code with simpler approach using just the parser

As described in https://github.com/iovisor/bpftrace/pull/448#issuecomment-468310930, this reverts my work from #439 and uses a much simpler approach entirely done in the parser.
I've run the tests from the reference guide and they all still work.
I updated the parser tests accordingly.
I'd be happy to fill in the remaining compound operators for #53 using the same approach as #448 as well, in a separate PR.
@mmarchini can you take a look?

ok, thanks!

authors: brendangregg dalehamel