Python error Caught exception.

When trying to download this course https://www.memrise.com/course/66669/1-5000-arabic-frequency-audio/
I get this error:
Error
An error occurred. Please start Anki while holding down the shift key, which will temporarily disable the add-ons you have installed.
If the issue only occurs when add-ons are enabled, please use the Tools>Add-ons menu item to disable some add-ons and restart Anki, repeating until you discover the add-on that is causing the problem.
When you've discovered the add-on that is causing the problem, please report the issue on the add-ons section of our support site.
Debug info:
Anki 2.1.9 (ae67c976) Python 3.6.7 Qt 5.12.1 PyQt 5.11.3
Platform: Linux
Flags: frz=True ao=True sv=1
Add-ons possibly involved: memrise2anki-extension-master

Caught exception:
  File "~/.local/share/Anki2/addons21/memrise2anki-extension-master/importer.py", line 840, in importCourse
    raise exc_info[0](exc_info[1]).with_traceback(exc_info[2])
  File "~/.local/share/Anki2/addons21/memrise2anki-extension-master/importer.py", line 146, in run
    course = self.memriseService.loadCourse(self.url, MemriseCourseLoader.Observer(self))
  File "~/.local/share/Anki2/addons21/memrise2anki-extension-master/memrise.py", line 788, in loadCourse
    return courseLoader.loadCourse(self.getCourseIdFromUrl(url))
  File "~/.local/share/Anki2/addons21/memrise2anki-extension-master/memrise.py", line 578, in loadCourse
    level = self.loadLevel(course, levelIndex)
  File "~/.local/share/Anki2/addons21/memrise2anki-extension-master/memrise.py", line 683, in loadLevel
    level.pool.mems.add(self.loadMem(userData, memData, level.pool, self.service.toAbsoluteMediaUrl))
  File "~/.local/share/Anki2/addons21/memrise2anki-extension-master/memrise.py", line 629, in loadMem
    mem.text, remoteImageUrls = markdown.convertAndReturnImages(text)
<class 'AttributeError'>: module 'markdown' has no attribute 'convertAndReturnImages'

This looks like an unhandled case when handling the downloading mems. If you don't want or need any mems, you can possibly work around it by commenting out line 685 of memrise.py. I'll have a look in a few hours and see if I can submit a pull request to fix it properly, though.
Looks like this project might be getting an unprecedented amount of attention over the next few days ;)

With line 685 commented, anki doesn't even start.

Should be fixed now


Multiple logger output files

Is the following possible (in Swift only):

have a custom logger, to log to a separate output log file
have separate log files for info, error, custom (as in number 1 above)

Great project - been using it since my early Obj-C days !

@pkasson This is totally possible. You even have multiple ways to achieve this...
First, you could subclass DDFileLogger, make it configurable with the log level you want and add it multiple times - using the corresponding log level.
Second, you could use a DDLogFormatter as a filter. Simply return nil from its formatting method to prevent the message from being logged.
Then add multiple DDFileLoggers (using different files), each having its own log formatter that filters the messages.
Both is possible in both Swift and Objective-C.

Thanks for the overview ... but not clear some of the steps.  Some post said you can only do this with Obj-C .. any examples or direction would be great and I would push that back as a PR

You would need a custom DDLogFileManager for both solutions (unless you're using completely distinct directories per level, in which case you could pass it to the DDLogFileManagerDefault directly).
final class LevelBasedLogFileManager: DDLogFileManagerDefault {
    let level: DDLogFlag

    private var levelString: String {
        switch level {
        case .verbose: return "VERBOSE"
        case .debug: return "DEBUG"
        case .info: return "INFO"
        case .warning: return "WARNING"
        case .error: return "ERROR"
        default: return "DEFAULT"
        }
    }

    private var logFilePrefix: String {
        levelString + "_"
    }

    init(level: DDLogFlag) {
        self.level = level
        super.init()
    }

    override var newLogFileName: String {
       logFilePrefix + super.newLogFileName
    }

    override func isLogFile(withName fileName: String) -> Bool {
        return fileName.hasPrefix(logFilePrefix)
            // The log file prefix needs to be dropped for `super.isLogFile(withName:)` to recognize the log file name.
            && super.isLogFile(withName: String(fileName.dropFirst(logFilePrefix.count)))
    }
}

Then you can either have a subclass of DDFileLogger, that filters out the corresponding messages:
final class LogLevelFileLogger: DDFileLogger {
    let level: DDLogFlag

    init(level: DDLogFlag) {
        self.level = level
        super.init(logFileManager: LevelBasedLogFileManager(level: level))
    }

    override func log(message logMessage: DDLogMessage) {
        guard logMessage.flag == level else { return }
        super.log(message: logMessage)
    }
}

Or use the default DDFileLogger (passing it the LevelBasedLogFileManager) and assign it a DDLogFormatter that filters the log messages (possibly combined with further log formatters using DDMultiFormatter:
final class LogLevelFilteringFormatter: NSObject, DDLogFormatter {
    let level: DDLogFlag

    init(level: DDLogFlag) {
        self.level = level
    }

    func format(message logMessage: DDLogMessage) -> String? {
        guard logMessage.flag == level else { return nil }
        // TODO: Add whatever formatting is necessary. Or chain using DDMultiFormatter.
        return logMessage.message
    }
}


A graphic for FlowFuse repository on socials and tag lists

Related Issue
https://github.com/FlowFuse/flowfuse/issues/3059
Description
Considerations:

This image will be seen when users are browsing topics on GitHub

example: Scroll this list of low-code projects - note how the better, more prominent entries have a graphic that offers some insight into their offering.

This image will be seen when a link to our repository is made on socials

This is described here: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview

Inspirations:

See this comment
Checkout this list to see what works for others: https://github.com/topics/low-code-development-platform
and this list: https://github.com/topics/low-code
Essentially, a graphic that attracts users to our platform, makes it stand out, offers some graphical notion of what we offer.

Hi @Steve-Mcl here it is 😃

Thanks @Yndira-FlowForge - perfect.


Edit Button Available on Comment Not My Own

I noticed on New A List Apart wants you!, I have an edit button, even though I am not logged in nor am I Daryl.

Just thought that you should be aware of this issue.

Hi Jason, that's a (static) cached template part (cloudflare), you cannot actually use that button to edit someone else's information. Nonetheless you shouldn't be seeing that, getting on to it, thank you for the heads up!

You're welcome! 👍


Bonding curve

Resolves #430

Apologies. Had to organise my fork since the last PR was automatically closed after I branched out.


Implementation of New UI Design for Company Certificates

##Summary
This ticket involves the implementation the new UI design for company certificates based on the existing prototype /companyCertificate. The goal is to update the frontend of the application to reflect the new design and provide a visually appealing and user-friendly interface for managing company certificates.
Tasks

Review the provided new UI design for company certificates and understand the design requirements.
Update the existing frontend codebase to incorporate the new design elements and styles.
Implement responsive design principles to ensure the application is visually appealing and functional on different devices and screen sizes.
Ensure that the new UI design is consistent with the overall application design and branding.

Design

Acceptance Criteria:

[ ] Update the filters to only support

All certificates
Active
Inactive

[ ] Make sure that switching around across the filters works without any issues
[ ] add the MUI upload icon to the "Certificate Upload" button
[ ] add the page description details

en: "Efficiently manage and organize your company certificates with ease. This page provides a user-friendly interface to view, add, edit, and delete company certificates. Stay on top of your certificate management process and ensure compliance effortlessly."
de: "Verwalten und organisieren Sie Ihre Unternehmenszertifikate einfach und effizient. Diese Seite bietet eine benutzerfreundliche Oberfläche zum Anzeigen, Hinzufügen, Bearbeiten und Löschen von Unternehmenszertifikaten.

[ ] Switch the document cards to the new design; ensure to go for a low maintenance effort card and do not design them to huge
[ ] MUI Warning Icon to be displayed on the app card as soon as expiry date is < "today+30days"
[ ] Keep the sub-menu with "view" and "delete" but ensure the correct typo and size usage as well as the sub-menu action when clicking outside the element
[ ] keep the overlay as implemented in the prototype
[ ] the user should not be allowed to submit a certificate without given "valid till" date

Let me know your thought on this implementation @jjeroch

Have added tooltip msg on each icon - warning, checked and closed icons
Warning icon will appear if certificate is expired or about to expire in 30 days
Close icon will appear when certificate in INACTIVE state
Check icon for active state
Delete icon will appear if user has proper access and certificate in ACTIVE state

In my opinion, we can remove the dots from the card as icon representation is more effective


class base library

Hi
I'm so interested why this component is not converted to class base format yet!!
Is'n there any fork which written in typescript or at least a class base js?
is there any plan to make it class base?

Moment 3.x will likely support the newest typescript. Or it won't support any typescript version and you'd have to import it with @types/xxx.
Currently it supports typescript 1.x.

Yeah I know that there is some type definitions for it but I wants to inherit that to customize it for my self but it can not be with just type definitions it must be implemented class way


eject library throws error within a monorepo

Description
ejecting the library throws an error in a monorepo
CodeSandbox/Snack link
No response
Steps to reproduce

requires a monorepo where your gluestack components live within a sub package
execute npx gluestack-ui-scripts eject
it will show this:

$ npx gluestack-ui-scripts eject
┌  gluestack-ui-scripts
hello 2
⏳ Ejecting Components & Theme will copy all the themed components inside './components' folder.

 If you have already ejected the theme or components,
- This will overwrite the existing styles with default one. (It is NOT RECOMMENDED to eject again)
- If you need to eject the components, then save the changes and copy/paste them manually.

 Commit you changes before ejecting, this command with update the imports!!

 If you are already using @gluestack-ui/themed inside your project, running this command will automatically change the imports from @gluestack-ui/themed to the components folder path.
│
◇  Are you sure you want to continue?
│  Yes
│
◇  Enter folder name where you want ejected components.
│  gluestack
│
◇  How do you want to import the components?
│  Relative Path
⏳ Ejecting Components & Theme inside "gluestack". Please wait...
Error copying src folder: Error: Cannot find module<EMAIL_ADDRESS>Require stack:
- /path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/scripts/eject-components/index.js
- /path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Module.require (node:internal/modules/cjs/loader:1225:19)
    at require (node:internal/modules/helpers:177:18)
    at /path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/scripts/eject-components/index.js:137:33
    at Generator.next (<anonymous>)
    at /path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/scripts/eject-components/index.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (/path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/scripts/eject-components/index.js:3:12)
    at installDependencies (/path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/scripts/eject-components/index.js:134:16) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/scripts/eject-components/index.js',
    '/path/to/.npm/_npx/124a6cf0cff875c9/node_modules/gluestack-ui-scripts/dist/index.js'
  ]
}

reason is that it tries to find @gluestack-ui/conf within the node_modules of the sub package, but in cases of monorepo it may live in the root's node_modules
gluestack-ui Version
1.1.16
Platform

[X] Expo
[ ] React Native CLI
[X] Next
[X] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

workaround is to use it in the root, then manually moving the changes.

Hey @macrozone This issue is fixed with the latest release, try it out once using npx gluestack-ui-scripts@latest eject. Closing this issue, feel free to reopen it if you face any problem.

@macrozone On rejecting the components, the changes done by you on the ejected components will be lost, that's why it is not recommended. But if you want original ejected components, yes, you can re-eject.


Sudden Size Increase?

Per a note @  https://github.com/StevenBlack/hosts/releases/tag/3.11.3, this list has suddenly increased in size.  I noticed the last few commits have huge net additions.  Could anyone explain this abrupt growth?

Duplicates & explained in https://github.com/AdguardTeam/cname-trackers/issues/53#issuecomment-1200425861


Fix NetworkPolicy labels for HA VPN

How to categorize this PR?

/area high-availability
/area security
/kind bug
What this PR does / why we need it:
This PR fixes network policy settings when VPN is set up for highly available shoot control planes. One important aspect was missed by the adaptations in #7515: HA control-planes have multiple VPN-Server services which all must be considered when adding Labels for Istio-Ingress and Kube-Apiserver.
Special notes for your reviewer:
/invite @rfranzke
Release note:

NONE

/milestone v1.65

/lgtm


Prebuilt binaries from version 5.0.3 do not work on the Node v12 docker image

Hello,
We're using sqlite3 in a project running with Node.JS 12. Since version 5.0.3, require('sqlite3') fails with a binary dependency error:
$ docker run --rm -it node:12 bash
# npm i sqlite3
[...]
+<EMAIL_ADDRESS>added 104 packages from 140 contributors and audited 104 packages in 7.757s

5 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
# node
> a = require('sqlite3')
Uncaught:
Error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /node_modules/sqlite3/lib/binding/napi-v6-linux-x64/node_sqlite3.node)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1057:18)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
> exit()
# npm i<EMAIL_ADDRESS>[...]
+<EMAIL_ADDRESS>added 99 packages from 152 contributors, updated 1 package and audited 282 packages in 7.922s

6 packages are looking for funding
  run `npm fund` for details

found 5 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
# node
> a = require('sqlite3')
{
  Database: [Function: Database],
  Statement: [Function: Statement],
  Backup: [Function: Backup],
  OPEN_READONLY: 1,
  OPEN_READWRITE: 2,
  OPEN_CREATE: 4,
  OPEN_FULLMUTEX: 65536,
  OPEN_URI: 64,
  OPEN_SHAREDCACHE: 131072,
  OPEN_PRIVATECACHE: 262144,
  VERSION: '3.34.0',
  SOURCE_ID: '2020-12-01 16:14:00 a26b6597e3ae272231b96f9982c3bcc17ddec2f2b6eb4df06a224b91089fed5b',
  VERSION_NUMBER: 3034000,
  OK: 0,
  ERROR: 1,
  INTERNAL: 2,
  PERM: 3,
  ABORT: 4,
  BUSY: 5,
  LOCKED: 6,
  NOMEM: 7,
  READONLY: 8,
  INTERRUPT: 9,
  IOERR: 10,
  CORRUPT: 11,
  NOTFOUND: 12,
  FULL: 13,
  CANTOPEN: 14,
  PROTOCOL: 15,
  EMPTY: 16,
  SCHEMA: 17,
  TOOBIG: 18,
  CONSTRAINT: 19,
  MISMATCH: 20,
  MISUSE: 21,
  NOLFS: 22,
  AUTH: 23,
  FORMAT: 24,
  RANGE: 25,
  NOTADB: 26,
  cached: { Database: [Function: Database], objects: {} },
  verbose: [Function]
}
>

Other known impacted environments: projects deployed to the Node.js 12.x environment on AWS ElasticBeanstalk.

This seems to affect all node alpine containers, independent of the node version. I tested node:16-alpine and node:12-alpine and node-sqlite3 works on none of them.

It looks like node:12 in Docker uses Debian Stretch, which probably ships an older version of glibc. I've updated the build environment recently so we've probably regressed on support for older glibc versions.
In the mean time, you can stay on v5.0.2, compile sqlite3 from source or switch to 12-bullseye, which ships with glibc 2.31 🙂

@Zebreus Linux musl prebuilt binaries was fixed in https://github.com/TryGhost/node-sqlite3/commit/8b2cdd948a382b58162cb491f745ba9167dc7b0f and should be released soon 🙂

The fix for this should be out with 5.0.4 🙂

Released 🙂


Feat/merge loading for radiomics page

Context

Changes & Results

Testing

Checklist
PR

[] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[] My code has been well-documented (function documentation, inline comments,
etc.)

Public Documentation Updates

[] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[] OS:
[] Node version:
[] Browser:

I believe this has been opened by mistake as it doesn't have description and 700 files are changing.


More badges for readme

dependency versions (david-dm.org)
devDependency versions (david-dm.org)
code climate

supa cute


Refactorting DSC resources for preventing conflicts

This change is to fix the DSC resources such that they don't conflict with the newer versions of these resources.

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-libraries-for-java

Hi @fearthecowboy. Refactoring the DSC spec as we discussed to circumvent the DSC spec issue. Could you please review and merge this change. Thanks.

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Approved -- we're just moving the models out of the common definitions file and dropping them locally so the next api version can reference old files without getting the wrong models.


informative text blocks

Is it supposed to look like:
**start of informative comment**
my informative comment
**end of informatrive comment**

What should it look like instead?

I really wish I added more context. Perhaps it was around the prologue and epilog on the informative comment blocks in bold.


Cannot read properties of undefined (reading 'references')

Markdown-it throws uncaught error when I use it
there is the sample: sample to reproduce

You missed mandatory param env in .parse() call.
PS. Please, don't duplicate issues, continue in existing one.


add higher level api for ops data

add higher level api for ops data, such as

insert batch with pd.DataFrame or numpy or tuple
query numpy or pd

thanks for your suggestion. it would be available soon.


Integrate profile settings into Gitness

Implemented API integration for profile settings in Gitness.
Refactored profile-settings-general-page form, moving loading state management out of Playground.
Removed avatar upload and delete buttons as per discussion on 10/4.
Temporarily centered avatar for improved layout.
Created a Gitness-specific copy of sandbox-settings-account-general-page, ensuring Playground remains exhaustive.

https://github.com/user-attachments/assets/4787a5c4-6fba-46ed-a4ac-98a87b480666

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


feat(rpc): Add admin_nodeInfo to get the local node record

Closes #850.
Adds the rpc method admin_nodeInfo, which returns the local node's ENR.
I'd like to ask about this part of the issue:

Additionally, AdminApi in the reth-rpc crate should be exported and constructable: currently it is private and impossible to construct.

AdminApi seems to have been exported with #866 : https://github.com/paradigmxyz/reth/blob/main/crates/net/rpc/src/lib.rs#L19 but what does constructable mean? just providing a new method?

but what does constructable mean? just providing a new method?

Yes, either that or making the fields pub, otherwise we cannot construct the struct. Not sure why none of the structs are constructable, cc @mattsse, maybe there is a reason

but what does constructable mean? just providing a new method?

Yes, either that or making the fields pub, otherwise we cannot construct the struct. Not sure why none of the structs are constructable, cc @mattsse, maybe there is a reason

yeh, let's just add a new function

FWIW the admin_ namespace is not standardized and many nodes do it in different ways.

aight @mattsse made the lint fixes (it was the todo!()s tripping everything up)—should then be g2g pending ci!


Add the docstring for the lr_cd.py

Hi Teammates,
Please review this docstring of algorithm function for milestone 1! Thank you!

Hi Andy, the docstring looks good to me!
I noticed that your input is numpy array, but the data generated in the previous function is dataframe. you might want to convert the data type at the beginning of the function and change to input type to dataframe. There might be better way to achieve this, feel free to modify whichever it's easier.
Also the visualization function will need the estimated y values from this function. Should we also return the estimated y here? Or do that in the visualization function?
Thank you!


refactor(resolvers): Remove resolvers

Codecov Report

Merging #4 (f788f45) into main (033cab2) will increase coverage by 6.34%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
+ Coverage   90.32%   96.66%   +6.34%
==========================================
  Files           8        5       -3
  Lines         186      150      -36
==========================================
- Hits          168      145      -23
+ Misses         18        5      -13

Impacted Files
Coverage Δ

playground/domain.py
100.00% <100.00%> (ø)

playground/iroha.py
91.22% <100.00%> (+9.08%)
:arrow_up:

playground/schema.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 033cab2...f788f45. Read the comment docs.


Added hello service tests

FYI @jlhughes
Kate has a minimal test case here that successfully uses HTTPBox to communicate Java Server to Java Server.  Technically this is from a single Java Server to itself, but its still happening via an HTTP Request.


Typescript does not have a message.text definition

Description
Using the app.message API the callback contains a property called text but the typescript definitions do not have this property
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[x] discussion

Requirements (place an x in each of the [ ])

[ ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ ] I've read and agree to the Code of Conduct.
[ ] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 3.8.1
node version: 16.11.0
OS version(s): MacOS
Steps to reproduce:

Attempt to use `app.message('', i => i.message.text)

Expected result:
The typescript definition exists for .text
Actual result:
No definitions exist
Attachments:

I see this issue which has been closed for the same problem #1209

Hi @TerribleDev, thanks for writing in! As you've already noticed, the currently recommended way is to have if/else statements to check subtype in payloads like https://github.com/slackapi/bolt-js/issues/1209#issuecomment-970304515.

Hi @seratch that makes sense. Would be good to document the subtypes. I feel like getting to the message is a very common usecase


Can not make X-Chain calls after  /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166

Describe the bug
When I make API-calls to the X-Chain I don't get any response.
Calls to health, P-Chain... are working.
To Reproduce

Start node
wait a bit
Make any X-Chain call e.g. avm.getBalance

Expected behavior
get a response
Screenshots
If applicable, add screenshots to help explain your problem.
Operating System
Ubuntu 20.04. 64 bit on ARM Raspi4 8GB plus 16GB swap
gecko 0.5.7 build from source
Additional context
I tried to rebuild gecko 0.5.7
I tried 0.5.5
I tried master
It was working before.
I stopped gecko, removed the db folder, started gecko, imported user and accounts
all of the above was not working
I will add logs here. There you can see the following:
before " /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166"
I can make X-Chain API-Calls.
After that line I can make calls to other endpoints.
When I make a call after that line to the X-Chain I dont get any response.
I stopped gecko with ctrl+c
WARN [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/main/main.go#74: NAT traversal has failed. The node will be able to connect to less nodes.
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/node/node.go#545: Gecko version is: avalanche/0.5.7
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/node/node.go#281: Set node's ID to E9cBEoCDBGi6qFGcW6bfFoyhWpq6Vc57Q
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/node/node.go#394: Initializing API server
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/node/node.go#447: initializing Keystore API
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/keystore
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/node/node.go#459: initializing Metrics API
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/api/server.go#53: API server listening on "<IP_ADDRESS>:9650"
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/metrics
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/node/node.go#439: initializing SharedMemory
INFO [08-10|16:50:11] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/jvYyfQTxGMJLuGWa55kdP2p2zSUYsQ5Raupu4TW34ZAUBAbtq
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/sqjdyTKUSrQs1YmKDTUbdUhdstSdtRTGRbUn8sqK8B6pkZkz1
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/sqjchUjzDqDfBPGjfQq2tXW1UCwZTyvzAWHsNzF2cb1eVHt6w
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/node/node.go#479: initializing Info API
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/info
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/node/node.go#492: initializing Health API
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/health
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/node/node.go#510: initializing aliases
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/node/node.go#338: initializing chains
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/rWhpuQPF1kb72esV2momhMuTYGkEb1oL29pt2EBXWmSy4kxnT
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID:<PHONE_NUMBER>1111111111111111111111LpoYY
    VMID:rWhpuQPF1kb72esV2momhMuTYGkEb1oL29pt2EBXWmSy4kxnT
INFO [08-10|16:50:12] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/vm.go#363: initializing Subnets
INFO [08-10|16:50:12] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/vm.go#349: initializing blockchains
INFO [08-10|16:50:12] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/vm.go#327: Initializing last accepted block as 2gha7M3ebHr1Nm9tuz9rKXVsEpstqkcViFLhJmAdqUshY416W8
INFO [08-10|16:50:12] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/11111111111111111111111111111111LpoYY
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:50:12] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:50:13] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 1 vertices in the accepted frontier
INFO [08-10|16:50:13] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:50:13] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:50:13] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with 2gha7M3ebHr1Nm9tuz9rKXVsEpstqkcViFLhJmAdqUshY416W8 as the last accepted block
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: rrEWX7gc7D9mwcdrdBxBTdqh1a7WDVsMuadhTZgyXfFcRz45L
    VMID:jvYyfQTxGMJLuGWa55kdP2p2zSUYsQ5Raupu4TW34ZAUBAbtq
INFO [08-10|16:50:13] <X Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#54: Initializing consensus engine
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/rrEWX7gc7D9mwcdrdBxBTdqh1a7WDVsMuadhTZgyXfFcRz45L
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/rrEWX7gc7D9mwcdrdBxBTdqh1a7WDVsMuadhTZgyXfFcRz45L/pubsub
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: zJytnh96Pc8rM337bBrtMvJDbEdDNjcXG3WkTNCiLp18ergm9
    VMID:mgj786NP7uDwBCcq6YwThhaN8FLyybkCa4zBWTQbNgmK6k9A6
INFO [08-10|16:50:13] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/zJytnh96Pc8rM337bBrtMvJDbEdDNjcXG3WkTNCiLp18ergm9/rpc
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/zJytnh96Pc8rM337bBrtMvJDbEdDNjcXG3WkTNCiLp18ergm9/ws
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: 1GHaaPbg1YBR4qiATuFNfL2j9StJwmddwXiwm1s9ts5KXvMai
    VMID:sqjdyTKUSrQs1YmKDTUbdUhdstSdtRTGRbUn8sqK8B6pkZkz1
INFO [08-10|16:50:13] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#54: Initializing consensus engine
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/1GHaaPbg1YBR4qiATuFNfL2j9StJwmddwXiwm1s9ts5KXvMai
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: jV7eZZh6Y2a35aaMLUGwBN1g2PNqfuuxLTSHu98EpHyPJDcQJ
    VMID:sqjchUjzDqDfBPGjfQq2tXW1UCwZTyvzAWHsNzF2cb1eVHt6w
INFO [08-10|16:50:13] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/jV7eZZh6Y2a35aaMLUGwBN1g2PNqfuuxLTSHu98EpHyPJDcQJ
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: am6cZ3MqzsbJG5mhNvrX2Z3w5uzRxZtgEacwhNqQ5p5KHAhtM
    VMID:tGas3T58KzdjLHhBDMnH2TvrddhqTji5iZAMZ3RXs2NLpSnhH
INFO [08-10|16:50:13] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:50:13] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/am6cZ3MqzsbJG5mhNvrX2Z3w5uzRxZtgEacwhNqQ5p5KHAhtM
INFO [08-10|16:50:14] /go/src/github.com/ava-labs/gecko/api/health/service.go#90: Health: GetLiveness called
INFO [08-10|16:50:16] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/service.go#301: Platform: GetPendingValidators called
INFO [08-10|16:50:19] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#82: AVM: GetTxStatus called with 2gZTNyRV7DdALck9mukgU8DZz4v9Gu8cvdfXNzP8oLbjgghkQU
INFO [08-10|16:50:20] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#82: AVM: GetTxStatus called with 2gZTNyRV7DdALck9mukgU8DZz4v9Gu8cvdfXNzP8oLbjgghkQU
INFO [08-10|16:50:21] <X Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 135 vertices in the accepted frontier
INFO [08-10|16:50:21] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#164: Bootstrapping finished with no accepted frontier. This is likely a result of failing to be able to connect to the specified bootstraps, or no transactions have been issued on this chain yet
INFO [08-10|16:50:21] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#164: Bootstrapping finished with no accepted frontier. This is likely a result of failing to be able to connect to the specified bootstraps, or no transactions have been issued on this chain yet
INFO [08-10|16:50:21] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#292: finished fetching 0 vertices. executing transaction state transitions...
INFO [08-10|16:50:21] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#333: executed 0 operations
INFO [08-10|16:50:21] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:50:21] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:50:21] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 1 vertices in the accepted frontier
INFO [08-10|16:50:21] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#298: executing vertex state transitions...
INFO [08-10|16:50:21] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:50:21] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:50:21] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with HQDeiNXCxDmETYpd7uRrnoKSeh71kS5cphKibCJMN6G1DmUFH as the last accepted block
INFO [08-10|16:50:21] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 1 vertices in the accepted frontier
INFO [08-10|16:50:21] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:50:21] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:50:21] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with JJoWekhXrFYrcbw6t1wqC37vXT1QWUBskRyGskzBM6Q1sN8XJ as the last accepted block
INFO [08-10|16:50:21] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#333: executed 0 operations
INFO [08-10|16:50:21] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#84: bootstrapping finished with 0 vertices in the accepted frontier
INFO [08-10|16:50:21] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with BhdXsMYpJsjGdgk1wqUWcukurCovwv9hpKMuLv7bJ9jVeSZJj as the last accepted block
INFO [08-10|16:50:28] /go/src/github.com/ava-labs/gecko/api/health/service.go#90: Health: GetLiveness called
INFO [08-10|16:50:32] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/service.go#237: Platform: GetCurrentValidators called
INFO [08-10|16:50:36] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/service.go#440: Platform: ListAccounts called for user 'paco'
^CINFO [08-10|16:50:41] /go/src/github.com/ava-labs/gecko/node/node.go#595: shutting down the node
INFO [08-10|16:50:41] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#131: shutting down consensus engine
INFO [08-10|16:50:41] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#67: finished shutting down chain
INFO [08-10|16:50:41] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#131: shutting down consensus engine
INFO [08-10|16:50:41] <P Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#67: finished shutting down chain
INFO [08-10|16:50:41] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#111: shutting down consensus engine
INFO [08-10|16:50:41] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#67: finished shutting down chain
INFO [08-10|16:50:41] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#131: shutting down consensus engine
INFO [08-10|16:50:41] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#67: finished shutting down chain
INFO [08-10|16:50:41] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#131: shutting down consensus engine
INFO [08-10|16:50:41] <C Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#67: finished shutting down chain
WARN [08-10|16:50:42] /go/src/github.com/ava-labs/gecko/snow/networking/router/chain_router.go#349: timed out while shutting down the chains
INFO [08-10|16:50:42] /go/src/github.com/ava-labs/gecko/node/node.go#599: node shut down successfully
INFO [08-10|16:50:42] /go/src/github.com/ava-labs/gecko/nat/nat.go#138: Unmapped all ports
FATAL[08-10|16:50:42] <X Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#185: forcing chain to shutdown due to closed
INFO [08-10|16:50:42] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#82: AVM: GetTxStatus called with 2gZTNyRV7DdALck9mukgU8DZz4v9Gu8cvdfXNzP8oLbjgghkQU
INFO [08-10|16:50:42] <X Chain> /go/src/github.com/ava-labs/gecko/snow/networking/router/handler.go#67: finished shutting down chain

Sometimes I get a different message on stopping. Here I made a getBalance call.
I always get one of the two FATALs, I did not find a way to say when I get the first or second case.
WARN [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/main/main.go#74: NAT traversal has failed. The node will be able to connect to less nodes.
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#545: Gecko version is: avalanche/0.5.7
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#281: Set node's ID to E9cBEoCDBGi6qFGcW6bfFoyhWpq6Vc57Q
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#394: Initializing API server
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#447: initializing Keystore API
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/keystore
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#53: API server listening on "<IP_ADDRESS>:9650"
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#459: initializing Metrics API
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/metrics
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#439: initializing SharedMemory
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/jvYyfQTxGMJLuGWa55kdP2p2zSUYsQ5Raupu4TW34ZAUBAbtq
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/sqjdyTKUSrQs1YmKDTUbdUhdstSdtRTGRbUn8sqK8B6pkZkz1
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/sqjchUjzDqDfBPGjfQq2tXW1UCwZTyvzAWHsNzF2cb1eVHt6w
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#479: initializing Info API
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/info
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#492: initializing Health API
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/health
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#510: initializing aliases
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/node/node.go#338: initializing chains
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/vm/rWhpuQPF1kb72esV2momhMuTYGkEb1oL29pt2EBXWmSy4kxnT
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID:<PHONE_NUMBER>1111111111111111111111LpoYY
    VMID:rWhpuQPF1kb72esV2momhMuTYGkEb1oL29pt2EBXWmSy4kxnT
INFO [08-10|16:56:54] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/vm.go#363: initializing Subnets
INFO [08-10|16:56:54] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/vm.go#349: initializing blockchains
INFO [08-10|16:56:54] <P Chain> /go/src/github.com/ava-labs/gecko/vms/platformvm/vm.go#327: Initializing last accepted block as 2gha7M3ebHr1Nm9tuz9rKXVsEpstqkcViFLhJmAdqUshY416W8
INFO [08-10|16:56:54] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:56:54] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/11111111111111111111111111111111LpoYY
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/network/peer.go#474: beacon attempting to connect with newer version avalanche/0.5.9. You may want to update your client
INFO [08-10|16:56:55] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 1 vertices in the accepted frontier
INFO [08-10|16:56:55] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:56:55] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:56:55] <P Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with 2gha7M3ebHr1Nm9tuz9rKXVsEpstqkcViFLhJmAdqUshY416W8 as the last accepted block
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: rrEWX7gc7D9mwcdrdBxBTdqh1a7WDVsMuadhTZgyXfFcRz45L
    VMID:jvYyfQTxGMJLuGWa55kdP2p2zSUYsQ5Raupu4TW34ZAUBAbtq
INFO [08-10|16:56:55] <X Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#54: Initializing consensus engine
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/rrEWX7gc7D9mwcdrdBxBTdqh1a7WDVsMuadhTZgyXfFcRz45L
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/rrEWX7gc7D9mwcdrdBxBTdqh1a7WDVsMuadhTZgyXfFcRz45L/pubsub
INFO [08-10|16:56:55] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: zJytnh96Pc8rM337bBrtMvJDbEdDNjcXG3WkTNCiLp18ergm9
    VMID:mgj786NP7uDwBCcq6YwThhaN8FLyybkCa4zBWTQbNgmK6k9A6
INFO [08-10|16:56:56] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/zJytnh96Pc8rM337bBrtMvJDbEdDNjcXG3WkTNCiLp18ergm9/rpc
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/zJytnh96Pc8rM337bBrtMvJDbEdDNjcXG3WkTNCiLp18ergm9/ws
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: 1GHaaPbg1YBR4qiATuFNfL2j9StJwmddwXiwm1s9ts5KXvMai
    VMID:sqjdyTKUSrQs1YmKDTUbdUhdstSdtRTGRbUn8sqK8B6pkZkz1
INFO [08-10|16:56:56] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#54: Initializing consensus engine
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/1GHaaPbg1YBR4qiATuFNfL2j9StJwmddwXiwm1s9ts5KXvMai
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: jV7eZZh6Y2a35aaMLUGwBN1g2PNqfuuxLTSHu98EpHyPJDcQJ
    VMID:sqjchUjzDqDfBPGjfQq2tXW1UCwZTyvzAWHsNzF2cb1eVHt6w
INFO [08-10|16:56:56] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/jV7eZZh6Y2a35aaMLUGwBN1g2PNqfuuxLTSHu98EpHyPJDcQJ
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/chains/manager.go#187: creating chain:
    ID: am6cZ3MqzsbJG5mhNvrX2Z3w5uzRxZtgEacwhNqQ5p5KHAhtM
    VMID:tGas3T58KzdjLHhBDMnH2TvrddhqTji5iZAMZ3RXs2NLpSnhH
INFO [08-10|16:56:56] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#57: initializing consensus engine
INFO [08-10|16:56:56] /go/src/github.com/ava-labs/gecko/api/server.go#106: adding route /ext/bc/am6cZ3MqzsbJG5mhNvrX2Z3w5uzRxZtgEacwhNqQ5p5KHAhtM
INFO [08-10|16:56:58] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#225: AVM: GetBalance called with address: X-JMvox3UMrWpu2ASq8irunQ6na5fujXVDx assetID: AVA
INFO [08-10|16:57:00] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#225: AVM: GetBalance called with address: X-JMvox3UMrWpu2ASq8irunQ6na5fujXVDx assetID: AVA
INFO [08-10|16:57:02] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#225: AVM: GetBalance called with address: X-JMvox3UMrWpu2ASq8irunQ6na5fujXVDx assetID: AVA
INFO [08-10|16:57:03] <X Chain> /go/src/github.com/ava-labs/gecko/vms/avm/service.go#225: AVM: GetBalance called with address: X-JMvox3UMrWpu2ASq8irunQ6na5fujXVDx assetID: AVA
INFO [08-10|16:57:03] <X Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 135 vertices in the accepted frontier
INFO [08-10|16:57:04] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 1 vertices in the accepted frontier
INFO [08-10|16:57:04] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:57:04] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:57:04] <timestamp Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with JJoWekhXrFYrcbw6t1wqC37vXT1QWUBskRyGskzBM6Q1sN8XJ as the last accepted block
INFO [08-10|16:57:04] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#164: Bootstrapping finished with no accepted frontier. This is likely a result of failing to be able to connect to the specified bootstraps, or no transactions have been issued on this chain yet
INFO [08-10|16:57:04] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#164: Bootstrapping finished with no accepted frontier. This is likely a result of failing to be able to connect to the specified bootstraps, or no transactions have been issued on this chain yet
INFO [08-10|16:57:04] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#292: finished fetching 0 vertices. executing transaction state transitions...
INFO [08-10|16:57:04] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166: Bootstrapping started syncing with 1 vertices in the accepted frontier
INFO [08-10|16:57:04] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#333: executed 0 operations
INFO [08-10|16:57:04] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#298: executing vertex state transitions...
INFO [08-10|16:57:04] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/bootstrapper.go#333: executed 0 operations
INFO [08-10|16:57:04] <spdag Chain> /go/src/github.com/ava-labs/gecko/snow/engine/avalanche/transitive.go#84: bootstrapping finished with 0 vertices in the accepted frontier
INFO [08-10|16:57:04] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...
INFO [08-10|16:57:04] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#269: executed 0 blocks
INFO [08-10|16:57:04] <spchain Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/transitive.go#111: bootstrapping finished with HQDeiNXCxDmETYpd7uRrnoKSeh71kS5cphKibCJMN6G1DmUFH as the last accepted block
INFO [08-10|16:57:04] <C Chain> /go/src/github.com/ava-labs/gecko/snow/engine/snowman/bootstrapper.go#230: bootstrapping finished fetching 0 blocks. executing state transitions...

The fatal errors during shutdown are not abnormal (the panic has been fixed for the next release). What's happening is after you hit ctrl c, the node attempts to shut down each chain and if the chain times out while shutting down, the node continues to close all of the resources that it's using including the database, network, etc. In the latter case, this results in an unhandled database error and a panic (which has been fixed for the next release to allow a more graceful shutdown).
As for the X Chain not responding to queries, it looks like in both of these cases the X Chain has not finished bootstrapping. You should see a message from the X Chain that says
Bootstrapping finished...
like you can see for the other chains which are responding when the X Chain has finished bootstrapping. After the X Chain finishes bootstrapping, all of the API calls should work normally.

Hello Aaron,
the node ran since Denali Incentivized Testnet 24/7 without any issues.
Then a month ago or so all the RAM was used 8GB plus 16GB swap. So I restarted the node somewhen around that time the X-Chain calls stopped working. Thats why I tried to start with a blank database. But since then the node ran for I think 2 weeks and is still not bootstrapped (Internet con. 100 Mbit/s)?!?
Normally you get a 404 when you make a call to a chain that is not bootstrapped but I dont get any response.
And if I make the call before the /go/src/github.com/ava-labs/gecko/snow/engine/common/bootstrapper.go#166 I get a correct response for older transactions.


Glowsquitos take fall damage

Glowsquito's are taking fall damage when they certainly aren't supposed to. Found on 1.18 but could be present on 1.17 and 1.16.
Credit to ClephLeSDF#6951 for discovering this issue.

I know it is useless for me to rely on memory alone, but I swear I remember Glowsquitos taking fall damage in 1.16.5 as well.

The issue is not present in 1.16, however it is present in 1.17 and 1.18


Unable to add Feedly/Twitter/Reddit account via webpage on M1 Mac

I'm trying to add my Feedly account to NetNewsWire, and I cannot get the authentication to work. I expect to be brought to the Feedly.com website to give my permission to use my Feedly account, but nothing happens.
Feedly is the only account where I don't just enter my credentials. Instead when I click on the Feedly icon, I get the following popup message (see screenshot below):
Waiting for access to Feedly
A web browser will open the Feedly login for you to authorize access.
And then right away I get another popup:
“NetNewsWire” wants to use “feedly.com” to sign in.
This allows the app and website to share information about you.
When I click on 'Continue' in the second popup window, nothing happens.
I expect to be brought to the Feedly.com website to give my permission to use my Feedly account, but nothing happens.
I'm using v6.0.3 (6035) on macOS Monterey 12.2.1 (21D62) on an M1 Mac. I also tried the latest beta build v6.1b4.

Actually, I just tried to add the Twitter and Reddit extensions and have the same issue. I see a relevant popup, but 'Continue' has no effect.

I just tested this on my Intel Mac with the same versions for macOS and NetNewsWire, and it works as expected.
So maybe it's a M1-specific issue?

Never mind. Quitting both Safari and Netnewswire multiple times did the trick.

Hi, I'm having a similar issue, the difference is there is a pop-up window open (MS Edge) but it is blank. The address bar show: about:blank as well.
I tried this with adding Feedly and Twitter. Same issue. Have tried restart multiple time


Can't disable specific slide based on breakpoint

Hello!
Firstly, great slider, thank you so much.
I have almost completed it, but am trying to remove a specific slide (it is one at the end, used as a spacer) when the slider is being viewed from a mobile.
I first tried using CSS the @media method to display: none the slide at a certain screen width - this does not help however due to how Slick is set up, meaning instead it just displays a blank slide instead.
I then tried to add some jQuery and manipulate the following using the Slick 'Method: slickRemove
$('.myslider').on("click", ".slide_to_be_removed", function () {
    var index = $(".myslider .slide_to_be_removed:not(.slick-cloned)").index(this);
    console.log(index);
    $('.myslider').slick('slickRemove', index);
});

This worked for removing the slide on click, but I want to remove it without a click, just at a certain width.
How would I do this please?
Many thanks
Max

Instead of using on('click'), try detecting the browser width and based on that apply what you need.
See http://stackoverflow.com/questions/16144187/how-to-detect-browser-size-using-javascript
This might help you.


Add required indexes for MySQL datastore

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/hold

/hold cancel


s3dis preprocess error：Area_1_alignmentAngle.txt not found.

run this then error:# S3DIS without aligned angle
python pointcept/datasets/preprocessing/s3dis/preprocess_s3dis.py --dataset_root ${S3DIS_DIR} --output_root ${PROCESSED_S3DIS_DIR}

Have you solved this problem?

It depends on which version of the Raw S3DIS dataset you download. Now an easier way to handle this is to download our processed version on Huggingface.

"Okay, thank you."


feat(doc): add overview content to bao-classic config documentation

PR Description
In this pull request, I'm adding content to the "Overview" section of the getting started documentation for the Bao hypervisor.
This update focuses solely on the "Overview" section, providing a detailed description of the configuration file and its different available fields.
Do you have any suggestions or feedback concerning the content provided in the "Overview" section?

https://github.com/bao-project/bao-docs/pull/66#discussion_r1291263414
@danielRep @josecm  I've improved the guest load description by including a description of the VM_IMAGE macro and a pointer to the 'Guest Image' section, where later it will be described how the guest image is configured. Can you please provide feedback on this change?

Small format tweaks @Diogo21Costa . After these small changes, is fine by me.

@danielRep Fully agree with all the points, thank you for the review! Applied all the changes in https://github.com/bao-project/bao-docs/pull/66/commits/133b7767895ab69e1d2ca77692a4b33fd91bf66e
Currently, the gitlint checker is failing due to unsigned commits, in specific the following ones:
https://github.com/bao-project/bao-docs/pull/66/commits/77e63cfc8344dab6c42cab0bf36cacf673ef5332 - fix(doc): improve documentation readability
https://github.com/bao-project/bao-docs/pull/66/commits/7613bf8dffde6b7566560932a88bfb5da787faea) - fix(doc): improve documentation readability
https://github.com/bao-project/bao-docs/pull/66/commits/d91a99db8a9d3b93748589f70ed1e0cfd16cba20 - fix(doc): improve documentation readability
https://github.com/bao-project/bao-docs/pull/66/commits/8678de35e67a2da0ade648c861481f13e86e7a11 - fix(doc): improve documentation readability
https://github.com/bao-project/bao-docs/pull/66/commits/a02d8162f37a676964fa175388f72467910d4a50 - fix(doc): improve documentation readability
https://github.com/bao-project/bao-docs/pull/66/commits/94a87a5be653045c17ce8827c08e6558dd90caf9 - fix(doc): improve documentation readability
To solve the issue and to maintain the history clean, may I squash all the "fix(doc)" commits into a single one?

Small format tweaks @Diogo21Costa . After these small changes, is fine by me.

@danielRep Fully agree with all the points, thank you for the review! Applied all the changes in 133b776
Currently, the gitlint checker is failing due to unsigned commits, in specific the following ones:
77e63cf - fix(doc): improve documentation readability 7613bf8) - fix(doc): improve documentation readability d91a99d - fix(doc): improve documentation readability 8678de3 - fix(doc): improve documentation readability a02d816 - fix(doc): improve documentation readability 94a87a5 - fix(doc): improve documentation readability
To solve the issue and to maintain the history clean, may I squash all the "fix(doc)" commits into a single one?

Yes, all those commits should be squashed.

@Diogo21Costa you should also refactor this to use the new line limit of 100.

Fix the checker issues when you have the time @Diogo21Costa

@josecm @danielRep Fixed the commit history and the formatting errors, thanks for the review!


Update solution file links

This resolves solution file links and adds some Rider specifics to .gitignore.
Closes #20

Thank you for the update, this looks good in Visual Studio and I'm glad we can also support folks that want to use Rider


Mast: Watch your[\W_]+website[\W_]+is[\W_]+very[\W_]+amazing

Mast requests the watch of the watch_keyword your[\W_]*+website[\W_]*+is[\W_]*+very[\W_]*+amazing. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

your[\W_]*+website[\W_]*+is[\W_]*+very[\W_]*+amazing has been seen in 7 true positives, 0 false positives, and 0 NAAs.

Approved by Thomas Ward in Charcoal HQ


Using Vue 2 - Component Instance Not Found

Hi,
Sorry - I am bit of a rookie here and trying to use VueStrap 2 for Vue 2.
I have below code on my HTML page:

<mySelect name="fruitOptions[]" limit="3" search justified required disabled clear-button close-on-select>
                                                </mySelect>

and this is in my component:
import mySelect from 'vue-strap/src/Select';

Vue.component('contact-api', {
    props: ['user'],
    components: {
        mySelect
    },
    data() {
        return {
            fruitOptions: [ {value:'Apple', label:'Apple'}, {value:'Banana', label:'Banana'}, {value:'Cherry', label:'Cherry'}, {value:'Orange', label:'Orange'}, {value:'Grape', label:'Grape'} ],

However, I am getting below errors:
1)) Unknown custom element:  - did you register the component correctly?
2)) Cannot read property 'name' of undefined
any idea what am i missing?

For vue 2 use my fork: https://wffranco.github.io/vue-strap


Test Pull Request (Automatic Static Analysis Cleanups)

Testing the pull request workflow with a couple changes generated by Agalmic's static analysis tool.

all merged in-- many thanks for the cleanup.


escaping in query strings doesn't work properly

What's going wrong?
Setting a string value via PQL like Set('bl\'ah', fld=ha) sets the literal value bl\'ah in Pilosa rather than the expected bl'ah.
The PQL parser knows to accept the backslash-escaped single quote, but never translates it into just a single quote... it passes the backslash along, which then gets stored in key translation and returned in query responses. The same problem exists for double quoted strings.
func TestQueryingWithQuotesAndStuff(t *testing.T) {
	m := test.RunCommand(t)
	defer m.Close()

	client, err := http.NewInternalClient(m.API.Node().URI.HostPort(), http.GetHTTPClient(nil))
	if err != nil {
		t.Fatal(err)
	}

	// Execute Set() commands.
	if err := client.CreateIndex(context.Background(), "i", pilosa.IndexOptions{Keys: true}); err != nil {
		t.Fatal(err)
	}
	if err := client.CreateFieldWithOptions(context.Background(), "i", "fld", pilosa.FieldOptions{Keys: true}); err != nil {
		t.Fatal(err)
	}

	// Test escaped single quote gets set properly
	if res, err := m.Query(t, "i", "", `Set('bl\'ah', fld=ha)`); err != nil {
		t.Fatal(err)
	} else if !strings.Contains(res, "[true]") {
		t.Errorf("setting escaped single quote result: %s", res)
	}
	if res, err := m.Query(t, "i", "", `Row(fld=ha)`); err != nil {
		t.Fatal(err)
	} else if !strings.Contains(res, `bl'ah`) {
		t.Errorf("value with escaped single quote set improperly: %s", res)
	}

	// Test escaped double quote gets set properly
	if res, err := m.Query(t, "i", "", `Set("d\"ah", fld=dq)`); err != nil {
		t.Fatal(err)
	} else if !strings.Contains(res, "[true]") {
		t.Errorf("value with escaped double quote set improperly: %s", res)
	}
	if res, err := m.Query(t, "i", "", `Row(fld=dq)`); err != nil {
		t.Fatal(err)
	} else if !strings.Contains(res, `d\"ah`) {
		// the backslash is there because JSON needs to escape the
		// double quote since it uses double quotes
		t.Errorf("value with escaped double quote set improperly: %s", res)
	}
}

So, I think we need to establish some actual written rules around how strings get parsed. I wish we could closely follow Go, but we threw that opportunity away by supporting single and double quotes.
So we support strings quoted either by single quotes or double quotes. We'll refer to the character quoting the string as "the quote character".
Between the quote characters, the following values are supported:

any character which is not the quote character or a backslash
\\ means \
\" means "
\' means '

closing issue as project is moving to sql3


Keep istiod from reverting back our changes to caBundle of both istio's validating & mutating webhooks

Using Istio 1.5.4
Infra:
I am using calico cni on an AWS EKS cluster (k8s 1.15.11). EKS doesn't officially support Calico.
Issue:
Now, while installing istio, I noticed that webhooks are not able to reach out to istiod service (/validate & /inject) this is due to the fact that EKS masters/control-plane keep running on amazon-vpc-cni while node groups are on calico. I confirmed this with AWS EKS support team.
Failed calling webhook, failing closed sidecar-injector.istio.io: failed calling webhook "sidecar-injector.istio.io": Post https://istiod.istio-system.svc:443/inject?timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Hence, I planned to use "Ingress" for exposing istiod and opa services.
I made both Istio's validating and mutating webhooks use Ingress endpoint and a respective certificate in caBundle field but istiod kept reverting my changes

Till I snatched the ClusterRole permissions from istiod's service account.

Now the reconcile loop in istiod keeps generating below errors...

Kindly give a configurable option to keep istiod from reverting back my update to caBundle field.

set env INJECTION_WEBHOOK_CONFIG_NAME="" and VALIDATION_WEBHOOK_CONFIG_NAME="" on istiod deployment will disable this


Fibonacci Number [C]

This issue is about [Algo/DS Name](link to resource for the Algo/DS).

[x] Issue Title is in form Algo/DS Name [Language].
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[x] This Algo/DS is worth adding to this repository.
[x] Assign this issue to me (I want to work on this).

[x] I ensure that I am not already assigned to 2 or more issues.

[x] I will send my PR only after I'm assigned to this issue by any maintainer.
[x] I understand that I will be unassigned from this issue if I fail to send a PR for this within a week.

@heisenberg-2505 One Issue per algo in one language and one PR for one issue.
Please stick to the rules.

Is this fine?

Assign this issue to me

Can I contribute to this issue?

Yeah sure. @ican8

please assign this task to me. I would like to work on this issue.

Go ahead! @The-Keshav-Agarwal


Do not produce CSS/IDL extracts for fork specs

This update makes it possible to integrate "fork" specs in web-specs (see https://github.com/w3c/browser-specs/pull/528). Reffy will not produce CSS/IDL extracts for these specs for the time being to avoid running into thorny duplicate issues, see comment in https://github.com/w3c/browser-specs/issues/511#issuecomment-1050958822

I don't disagree. That's meant as a short term measure as I don't have the bandwidth right now to do something smarter. In Reffy, collecting the fragments means also updating the idlnames logic to ignore them. In webref, that means understanding what to do during curation and what to release in @webref/idl.

I'll go with this as it has the merit to exist, and to open the way to merge https://github.com/w3c/browser-specs/pull/528; we can revisit iteratively.


Modified src and dest locations in CentOSVZadapter.py to copy specific lab to container

Hello ovpl team,
I have modified src ( source) and dest (destination) locations in CentOSVZAdapter.py file to avoid copying all labs to container instead of single required lab.
Please review it
Thank you

Reviewed and merged code.


how to correct format a long numeric string?

I set the header like this
 CellProcessor[] processors = new CellProcessor[headers.length];
                for (int i = 0; i < processors.length; i++) {
                    processors[i] = new NotNull();
                }

and the data ：
Object[] row=new Object[]{"2984303180499968","john","male"};
But  the generateed csv file
treat long numeric string(2984303180499968) as scientific notation(2.9843E+15) !
how can I define the cell format just like the poi does：row.createCell(j).setCellValue((String) rowData[j])

anyone knows?

Hi, @geosmart
Did you encounter this problem by opening the CSV file through execel?
This problem is not caused by super CSV, but by Excel, because it is normal to open in notpad++. And if you want to avoid this problem, you can use the following methods:
List<Object> row = Arrays.asList(new Object[]{"\t2984303180499968","john","male"})


Fix handbook linking 0.2.0 version to 0.3.0

Fix https://www.lf-lang.org/docs/handbook/command-line-tools?target=c page linking 0.2.0 to 0.3.0.

@lhstrh Not sure if the review is assigned. Just leaving a note in case of no notifications.

@edwardalee Would you please review this? Just fixed some minor typos while reading the handbook.

LGTM! Thanks.


Mismatched const in function declaration and definition are not resolved correctly

Top level consts are optional in the declaration.
In the following snippet cquery doesn't seem to match the declaration and definition of TestFunc
class Test{
void TestFunc( int x);
};

void Test::TestFunc(const int x) {}

The target mangled names may be the same but Clang USR is different. This will be impossible to implement in cquery. Sorry


Error when starting Android app

I've got this error when I want to start the Android app. In iOS it works fine.
/Users/williamschrauwen/ReactNative/BraintreeSample/node_modules/react-native-braintree-xplat/android/src/main/java/com/pw/droplet/braintree/Braintree.java:22: error: Braintree is not abstract and does not override abstract method onActivityResult(Activity,int,int,Intent) in ActivityEventListener
public class Braintree extends ReactContextBaseJavaModule implements ActivityEventListener {
^
/Users/williamschrauwen/ReactNative/BraintreeSample/node_modules/react-native-braintree-xplat/android/src/main/java/com/pw/droplet/braintree/Braintree.java:108: error: method does not override or implement a method from a supertype
@Override
^
2 errors
:react-native-braintree-xplat:compileReleaseJavaWithJavac FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-braintree-xplat:compileReleaseJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 10.834 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html

Which version of RN are you using?

I've made an example app to test, so the newest version 0.34.1.

I'm getting the same error, using react-native 0.34

ok it looks like there is a fix for this on PR #16 ! if @kraffslol will go ahead and publish the latest to npm and increase the version - we can have the fix.
in the meantime:
"react-native-braintree-xplat": "https://github.com/kraffslol/react-native-braintree-xplat/tarball/master",
in your package.json will get past the error.

Should now be sorted out in the latest version.

yep, I can confirm this is working just fine on the npm version! Thanks @kraffslol


feat: Introduce activationThreshold/minMetricValue for Selenium Scaler

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[x] A PR is opened to update the documentation on (repo) (if applicable)

Related to https://github.com/kedacore/keda/issues/2800
Related to https://github.com/kedacore/keda-docs/pull/843
Fixes https://github.com/kedacore/keda/issues/3253

/run-e2e selenium*

/run-e2e selenium*

/run-e2e selenium*


Fix : Prisma schemas on relation queries page #799

Fix and a little logical modifications, as needed

Hi @rahul3v! You make so many contributions to our doc site - we'd love to send you some Prisma and Prisma Docs stickers. If you feel comfortable, could you contact me on<EMAIL_ADDRESS>so we can organize how to get the stickers to you? :)

Hi @mhwelander, that's great, I would love that having some prisma swags, 🎃


[NO_ISSUE] roll an abstract class that contains common functionality …

Roll an abstract class that contains common functionality for AJAX and Web-socket request handlers

@martin-g  thanks for approval. Test were green locally.


application-BikaStarX.md

Project Abstract

Please provide a brief description of your project here summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

For which grant level are you applying?

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

Please don't refuse grant proposal for Bika, I really need grant funds for development on Polkadot, Substrate and W3F for a better life with Crypto, I will build Bika Novel and BikaSwap or Dapps apps for Polkadot token exchange, Ethereum and Bep-20  , I request that Bika get Grant level 1 for development, I will fully contribute to Web3, so please pay attention and provide grant assistance to Bika, I promise to use grant funds from W3F properly and regularly for Web3 and project purposes, I hope W3F  is more good in making decisions, hopefully W3F can help the Bika project.

I really hope about grant funding for new development and innovation in W3F, but W3F team doesn't have ability to see high utility project grow, W3F team can't understand with new project to develop, I'm disappointed with W3F can't help new project like Bika,  we will not contribute to the polka-dot ecosystem if we do not have the funds for development.

Please give Bika project grant I need funds for new development and innovation in W3F, why W3F always rejects Bika's proposal, I have filled in project details without copying any project, Bika project is an online novel project and has its own uniqueness, why W3F doesn't understand  the state of the new project that requires initial funding to grow, I don't understand W3F about taking action, I have submitted a proposal twice but it was rejected, if W3F does not provide grant assistance to Bika I will not contribute to the polkadot ecosystem because the grant team does not have the ability to see  Projects that need help.

I need only level 1 grants but it's very difficult even though in the W3F program github explains that level 1 grants don't produce a lot of project details and I've filled out detailed project details and you refuse, we are disappointed with W3F's unfairness in the process of this grant program, even though I needed this grant for W3F innovation and development, I was very disappointed.

Please give and give only this time for Bika project level 1 for Web3 development, please answer us and give and give so project can contribute to Web3, Polkadot and Substrate.  I hope Bika project get grant from W3F, project need 10000 USD grant or level 1 grant, give grant to Bika so that I can make a good schedule for project work.


look in stack's work directory for import files

It looks like stack build --ghc-options -ddump-minimal-imports puts GHC's output in a different directory than cabal build --blah-blah-blah. It would be nice if packunused knew how to look in that spot, too, so that it could be used out of the box with stack.

(See specifically http://stackoverflow.com/q/32959393/791604 for details on where stack puts the imports files.)

patches welcome! :-)
(I don't use Stack myself, so I have to rely on contributions)

+1
Also @hvr you should try Stack. You'll love it, it's really good. :smile:


FlexTable: provide event to onRowClick

I have a FlexTable with custom renderer on one of the FlexColumn which returns a Link.
I need a way to avoid running onRowClick callback when cell with Link was clicked.
My suggestion is to provide event as second argument.

I don't understand why that would be necessary. If your custom cell render wants to trap the click event, why not just trap it there?
function yourCustomCellClickHandler (event) {
  event.stopPropagation()
  // Do whatever you do
}

Closing as a no-op.

@bvaughn tried your suggestion and it doesn't work for me because it breaks my Link component making SPA to hit the server and reload. Also it adds an extra div. Moreover, providing event just seems pretty natural for on*Click callbacks.

There's no reason to provide a click event to the onRowClicked callback so you can trap the click inside of a cell. You have the ability to trap the click inside of a cell as I mentioned above. I don't know what you mean by:

it breaks my Link component making SPA to hit the server and reload

Wrapping your Link in a div that stops the event from bubbling should not have any effect on your Link component unless you have your Link component misconfigured somehow (for example, by setting target='_blank' in your Link component which causes it to be handled differently).

Need to notice that the div from the example should be replaced with a span to avoid onclick dead zones (such as div is a block element).
cellRenderer={
  (cellData, cellDataKey, rowData, rowIndex, columnData) => (
    <span onClick={(event) => event.stopPropagation()}>
      <Link to='...'>Title</Link>
    </span>
  )
}

Nice catch, @cyberxndr.


Extend subspan byte offset folding to GPU MMA load/store

This commit extends the existing pattern for folding subspan offsets
into load/store ops to cover GPU subgroup MMA load/store in
FlattenMemRefSubspanPass.

I think there is an unrelated failure?


Adding no_std support

Do you have plans for adding no_std support anytime soon? Thanks!

I'm not quite sure what do you mean; with no_std we can't assume that network exists at all, and therefore, there might be no such concept as a "hostname" at all.
Can you elaborate more on your case?

So I'm working on making the CloudEvents SDK Rust library no_std compatible.
We are thinking of scenarios something like IoT devices running in no_std environments would need to communicate with other devices (I'm sorry if this doesn't make much sense 😅), so your library being able to provide support in such cases would be amazing!

I don't really see how it would work.
As I said before, having the "network host name" concept in system means that we also have some sort of networking. Being able to compile with no_std by itself does not guarantees that, so unless these imaginary IoT devices conform to some widely used specification for providing API with system information (such as POSIX gethostname) I don't think it is up to this crate to support them.
Let's leave this issue opened in case someone else would want to provide the feedback on this topic.


Fix MudForm.IsValid initialization for form components with Required=true (#5196)

Description
Set MudForm.IsValid to false during initialization only if required form components don't have a value.
Previously, IsValid was set to false in any case, even if a required form component had a valid value.
The logic is now encapsulated in a private static helper method IsFormComponentValid so that it can be easily adapted.
Please note that the logic is better than before, but still not 100% correct because it does not take custom validation logic into account.
Fixes #5196.
How Has This Been Tested?
This is implicitly tested by adapting existing tests (e.g. for a MudForm with a contained MudFileUpload component that has a non-null Files parameter) by adapting the IsValid assertions, which are now checking for true.
In some tests, the initial assertion for IsValid==false has been commented out because I cannot tell, what the expected value is if a custom validation function is set. These tests previously only passed "by coincidence". I'm not sure what the best approach is here. Please look for //??? to find my comments.
Type of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added/adapted relevant tests.

The solution is not 100% accurate like you said and the changes to the tests are quite troublesome.
What if we go with a different approach and add a new parameter InitialValidation and set it to false to avoid breaking changes for now. In v8 we might change the default value to true and deal with the test cases then.
If the InitialValidation param is set to true then it triggers an async validation in OnInitializedAsync. This should automatically correct the validity of the form accordingly and would avoid the trouble with custom validation logic of above solution.

Yes, yes and yes ;)

I played with it quite a while and here's the best workaround/solution I could come up with:
public class MudFormV8 : MudForm
{
    [Parameter] public bool InitialValidation { get; set; } = true;

    protected override async Task OnAfterRenderAsync(bool firstRender)
    {
        if (firstRender && this.InitialValidation)
        {
            // Perform "full-fledged" validation in "V8 mode".
            await this.Validate();

            // Clear the initial validation errors to show an initially "clean" form
            await this.ClearValidationErrorsAsync();

            // Reset the IsTouched flag which got implicitly set by the Validate call
            this.ResetTouched();
        }
        else
        {
            // Only call base class implementation in "legacy mode" because it will reset IsValid to false for required fields,
            // even when they do have a valid value.
            await base.OnAfterRenderAsync(firstRender);
        }
    }

    public async Task ClearValidationErrorsAsync()
    {
        // Update overall validation errors (aggregated from form component validation errors)
        // and update IsValid state (aggregated from form component HasError state)
        await this.OnEvaluateForm();

        // Clear form component errors because we don't want to see them on initial form presentation
        foreach (IFormComponent formControl in this._formControls)
        {
            formControl.ValidationErrors.Clear();

            // Clear MudFormComponent<T,U>.ErrorText (via reflection because not exposed via `IFormComponent`)
            PropertyInfo? errorText = formControl.GetType().GetProperty(nameof(MudFormComponent<object, object>.ErrorText));
            errorText?.SetValue(formControl, null);

            // But preserve Error state.
            // This is required so that the form remains invalid if at least one required field is still empty.
            // The downside of this is that invalid form controls are rendered with a red error border, but no error validation message.
            //formControl.Error = false;
        }
    }
}

It's an improved version of MudForm that provides the InitialValidation property that @henon suggested and overrides OnAfterRenderAsync to perform a "full-fledged" validation and then resetting the unwanted validation side effects.
The ClearValidationErrorsAsync method is provided as a public helper so that the validation error state can be reset by users, e.g. when data has been asynchronously loaded.
It works nearly perfectly (for my cases). The only downside is that I have to preserve the IFormControl.Error state. This leads to invalid fields being shown with a red error border (but without a "nasty" validation error message) on the initial form presentation (see screenshot). Please see the comment why the Error state needs to be preserved.
Honestly, all of this is a hacky workaround. The root problem seems to be in MudForm, which assumes that fields/models/values are initially empty until they are touched at least once.


Oracle Cloud & Google Cloud detection, and custom rules for each

Oracle Cloud needs iptables disabled, or properly configured
Google Cloud needs an MTU set so the LXD containers can reach the network outside of the VM.

resolved by commit # 24d8c3f7ed1af91128ffe26cd5f71bf99cb30f69


P01 term for cloud cover

Cloud cover is defined as:

Cloud cover expressed as x/8 (octas). Uses the CloudCover vocabulary.

There some existing terms that come close:
Cloud cover (all clouds) in the atmosphere by visual estimation and conversion to WMO code

http://vocab.nerc.ac.uk/collection/P01/current/WMOCCCAC/
No definition
Broader: Cloud cover height and extent

Cloud cover height and extent

http://vocab.nerc.ac.uk/collection/P02/current/CHEX/
Parameters describing the horizontal and vertical extent of cloud cover

@nicolasvanermen @rubenpp7 Since the first term specifies WMO codes (and we use octas), I think we have to go for the broader term?

Unless there is a WMO scale dedicated to cloudliness and which is easily linked to octas (which I doubt) I guess we should go for a seperate vocubulary.

I guess we should go for a seperate vocubulary.

Why not link to the broad description in http://vocab.nerc.ac.uk/collection/P02/current/CHEX/ ?

OK misunderstood this, if the broader description allows octas as a 'unit' that is fine of course.

Thanks! I'll use that one.


promote-assembly: better log message

When waiting on release controllers, print logs like
Release payload for "x86_64" arch is the "Ready" state. Will check again in 300.0 seconds.

/lgtm


feat(UI): AccessManagement UI to access the role metadata for a dataset

The aim of this feature is to add a new tab for Access Management to enable users to view the required roles (Roles/Policies defined in Access Management System of an organisation) for accessing a dataset in that organisation for a dataset. Also allow user to raise the request for a required role if user dont have access.
People can navigate to a dataset and view list of roles necessary to access that dataset. We can click on a dataset role and request access from that page.
Attaching the RFC for further details
rfc-DatahubUI.pdf
Uploading RFC.-.Addition.of.External.Access.Managemt.pdf…
reference PR - 8499
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@jjoyce0510
could you please take a look.
thanks ,
Ramendra

@Ramendra761 Could you please describe shortly how to use this feature? just deployed 0.12 but didn't see any Access management tab in the UI.

@Ramendra761 nice work!
I enabled access management via the SHOW_ACCESS_MANAGEMENT env var in the gms container and I can see the tab in the UI, but I'm unsure how to add roles that can be granted. Are there any docs on this yet?


Add Contact us page

Describe the bug/feature
Hey @rockingrohit9639
I would like to add contact us page .
Please assign it to me.
Thanks
To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.
Logs
If applicable, add logs to help explain your problem (e.g. the error message and/or exception traceback).
Environment (please complete the following information):

OS:
Browser:

Additional context
Add any other context about the problem here.

Hey, @Shaishav0507 You can start working on this issue. Make sure you complete it in 6 days.


Nesting tab does not work, especially on Android

Current Behavior
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 * @flow
 */

import {
    AppRegistry,
    Button,
    Image,
    StyleSheet,
    Text,
    View,
} from 'react-native';
import React, { Component } from 'react';
import {
    StackNavigator,
    TabNavigator,
} from 'react-navigation';

// Children
class ChildFooScreen extends Component {
    static navigationOptions = {
        tabBarLabel: 'Foo',
    };
    render() {
        return <View style={{ backgroundColor: 'red', marginTop: 200 }}><Text>Foo</Text></View>;
    }
}

class ChildBarScreen extends Component {
    static navigationOptions = {
        tabBarLabel: 'Bar',
    };
    render() {
        return <View><Text>Bar</Text></View>
    }
}

const ChildTabNav = TabNavigator({
    Foo: {
        screen: ChildFooScreen
    },
    Bar: {
        screen: ChildBarScreen
    }
});

class RecentChatsScreen extends React.Component {
  render() {
    return <View>
        <Text>List of recent chats</Text>
        <ChildTabNav />
    </View>
  }
}

class AllContactsScreen extends React.Component {
  render() {
    return <Text>List of all1 contacts</Text>
  }
}

const MainScreenNavigator = TabNavigator({
  Recent: { screen:  ChildTabNav}, // if it is RecentChatsScreen, it does not work
  All: { screen: AllContactsScreen },
});

export default class AwesomeProject extends Component {
    render() {
        return (

            <MainScreenNavigator />

        );
    }
}

AppRegistry.registerComponent('AwesomeProject', () => AwesomeProject);

Expected Behavior

I'd like to display my 'child tab' in RecentChatsScreen, instead of ChildTabNav directly. How could I implement it

software
version

react-navigation
^1.0.0-beta.9

react-native
0.44.0

node
v7.9.0

npm or yarn
0.23.2 (yarn)

I think you can't call  inside a component like you did in RecentChatsScreen, but only in a navigation function like in MainScreenNavigator.

I encountered the same problem, the tab nesting does not work properly

having same issue

same issue here

I don't understand why RecentChatsScreen  shouldn't work, not what you mean with "RecentChatsScreen doesn't work".
Please @imWildCat  provide the error log for it because I can't think of a reason of it not working. If no answer I'll close this in 7 days since it's really old.

Hi there @imWildCat ,
In an effort to cleanup this project and prioritize a bit, since this issue had no follow up since my last comment I'm going to close it.
If you are still having the issue (especially if it's a bug report) please check the current open issues, and if you can't find a duplicate, open a new one that uses the new Issue Template to provide some more details to help us solve it.


⚠ AGEG website (prod) has degraded performance

In 4761749, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 1109 ms

Resolved: AGEG website (prod) performance has improved in 6be1685.


How to make an input parameter/flag default to a named Environment Variable?

As the title says;

I want a flag/input parameter named --foo-bar. (No probs there).
I want --help to show that --foo-bar gets its default value from environment variable FOO_BAR.
(Maybe also show the value of the current envvar FOO_BAR if it exists in current shell/machine)?

All properties of  OptionAttribute are constant  and can't be modified at run-time.
But you can add dynamic contents to help text before /or after options which can be computed using a function at runtime.
           var helpText= HelpText.AutoBuild(result, h =>
		 {
		     h.AddPostOptionsLine(dynamicData());	//add post options dynamic content
		    return h;
		 } , e=>e);

       static Func<string> dynamicData = () =>{
	   var header ="-------Environment Variables----------";
	   var FOO_BAR=Environment.GetEnvironmentVariable("FOO_BAR");
	  return $"{header}\nFOO_BAR={FOO_BAR}";
	};

output:
myapp.exe <IP_ADDRESS>
Copyright (C) 2019 global.com

  -r, --read         Input files to be processed.
  --verbose          (Default: false) Prints all messages to standard output.
  --stdin            (Default: false) Read from stdin
  --help             Display this help screen.
  --version          Display version information.
  offset (pos. 0)    File offset.

-------Environment Variables----------
FOO_BAR=server123

For more details of custom help see HelpText-Configuration


Web2 account signing

add signature and signed message to api for submitting a solution
add web2 account signing to captcha submission

Great work


Map zoom level is too tight (so you can't see the whole planet)

Problematic when you are going over the date line.

Possible solution is to check on resolution and size of maps on load and then set the min zoom level. Maybe not be a top priority


[Build] Tweak how we write commands for the test discovery

This will make the test discovery command logic to be independent of the
global target list in the build plan, which in turns makes it for
multiroot packages.
rdar://problem/53762967

@swift-ci smoke test


Elkan's Algo Implementation

RGB Quantization is well suited for Elkan's algorithm (I think). Create an compare to current version (which is just lloyd's w/ kmeans++ initialization). It looks like the only real downsides of this version is that it is O(k^2) in memory where k = colors, but since we're quantizing to a low color space that's totally fine. Also doesn't work as well in high dimensional spaces, but we're in RGB, so that's not an issue either.

closing as we implemented hamerlys in #4 and that's probably better suited to color quantizing than Elkan's anyways


Does not preserve multidimensional array shape

Hi there, really nice work! One limitation of this approach is that it does not preserve the shape of the array (i.e. the size along each dimension). I wonder if you've considered adding this functionality? If not, it's something I might work on. One way to go about this is to store each value as a map containing a fields 'shape' and 'value'. This is I think the approach taken by msgpack-numpy here [ https://github.com/lebedov/msgpack-numpy/blob/master/msgpack_numpy.py ]. Do you have any thoughts on this or would you recommend a different approach?

@djoshea are you using this code? Did you make the change to preserve matrix shape?

Hey Jeff, No I didn't. The numpy approach seems like it replaces each numpy array with a dict that has the size, the element type, and the data.
I ended up using a simpler, homebrewed serialization format since everything we were sending to our data logger was a Matlab matrix or a string. The serialization happens in Simulink Real-Time and only adds a few extra bytes over the raw data. The upside is that it was easy. The downside is it's homebrewed.
If you just want serialization and don't care about it being Matlab specific, this might be useful http://undocumentedmatlab.com/blog/serializing-deserializing-matlab-data

Actually, using UBJSON looks promising since it's simple, and then jsonlab already supports this in Matlab, as far as I can tell. http://iso2mesh.sourceforge.net/cgi-bin/index.cgi?jsonlab/Doc/Examples#MATLAB_array_demo

We looked into ubjson but I think we had problems reading it in Python on the other side.
I'll take another look. My problem with json lab is that it is written in matlab and very slow.
Sent from my iPhone

On Jun 30, 2016, at 03:37, djoshea<EMAIL_ADDRESS>wrote:
Actually, using UBJSON looks promising since it's simple, and then jsonlab already supports this in Matlab, as far as I can tell. http://iso2mesh.sourceforge.net/cgi-bin/index.cgi?jsonlab/Doc/Examples#MATLAB_array_demo
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.