text:
Crash after changing metro.config.js - > node_modules\expo-router\entry.js: traverse is not a function

Describe the bug
after changing metro.config.js to
module.exports = {
...config,
transformer: {
...config.transformer,
babelTransformerPath: require.resolve(
"react-native-react-bridge/lib/plugin"
),
},
};
i can't start react app anymore:
node_modules\expo-router\entry.js: traverse is not a function
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Platform:

OS: iOS, Android, wen
Running on: Device, Browser
Version of this package: ^0.11.0

Additional context
Web Bundling failed 826ms
error: node_modules\expo-router_error.js: traverse is not a function
Web node_modules\expo-router/entry.js ░░░░░░░░░░░░░░░░  0.0% (0/1)
Metro error: node_modules\expo-router\entry.js: traverse is not a function
Call Stack
MetroBundlerDevServer.getStaticResourcesAsync (node_modules/@expo/cli/build/src/start/server/metro/MetroBundlerDevServer.js)
process.processTicksAndRejections (node:internal/process/task_queues)
async MetroBundlerDevServer.getStaticPageAsync (node_modules/@expo/cli/build/src/start/server/metro/MetroBundlerDevServer.js)
async (node_modules/@expo/cli/build/src/start/server/metro/MetroBundlerDevServer.js)
Web Bundling failed 10ms
error: node_modules\expo-router\entry.js: traverse is not a function
Web Bundling failed 9ms
error: node_modules\expo-router\node\render.js: traverse is not a function
Web Bundling failed 12ms
error: node_modules\expo-router_error.js: traverse is not a function
› Detected a change in babel.config.js. Restart the server to see the new results. You may need to clear the bundler cache with the --clear flag for your changes to take effect.

Facing the same issue!

Thanks!
I've released a patch 0.11.1. Could you try it?

Hey! The patch 0.11.1 worked, the error is gone but now I'm facing the following:
ReferenceError: Property 'n' doesn't exist, js engine: hermes.
To reproduce it, just create an Expo project and follow the instructions on this package's Homepage to create a demo project.

Hey! The patch 0.11.1 worked, the error is gone but now I'm facing the following:
ReferenceError: Property 'n' doesn't exist, js engine: hermes.
To reproduce it, just create an Expo project and follow the instructions on this package's Homepage to create a demo project.

Are you suggesting we use the new_script function as is but instead of using a path we copy the whole code block in myAlert.js inside the double quotes? Or should we not use the new_script function at all and refer to our code in a different way? We're struggling to understand how we should reference the code block. This is our standalone setup that runs by itself in html/js that we are trying to run inside the react component using react-native-react-bridge: https://gist.github.com/zserge/6617cdbf328aac76913ff9ae85350c10

I am also facing same issue with version 0.11.1.

Having the same issue. Any ideas?

0.11.2 is released. Thanks!

authors: accelerate-dm edjiang iabdulhannan inokawa katche70

repo: inokawa/react-native-react-bridge


text:
Not supported server-side rendering (SSR)

Issue details
used @inotom/vue-go-top in a gridsome project, it works normal in develop environment, but causes window is not defined error when use gridsome build to build.
Had found the reason is that "gridsome build uses server-side rendering (SSR) to create a fully rendered page",  and by referring the gridsome doc here: Add External Scripts - without-ssr-support, i used the following code:
<template>
  <div class="layout" :class="{ 'sticky-header': $route.path === '/' }">
    <Navbar />
    <!-- <Header /> -->
    <slot/>
    <ClientOnly>
    <go-top :has-outline="false" :size="50" :max-width="320" bg-color="#38b2ac"/>
    </ClientOnly>
    <Footer />
  </div>
</template>

<script>
import Navbar from "@/components/Navbar"
// import GoTop from '@inotom/vue-go-top'
import Footer from "@/components/Footer"

export default {
  components: {
    Navbar,
    Footer,
    GoTop: () =>
        import ('@inotom/vue-go-top')
        .then(m => m.GoTop)
        .catch()
  }
}
</script>

but it now doesn't work even in develop environment. Could anybody help here?

Using process.isClient to load GoTop only on browser will eliminate the error.
const GoTop = process.isClient ? require('@inotom/vue-go-top').default : null;

export default {
  components: {
    Navbar,
    Footer,
    GoTop,
  }
}

Client API - Gridsome

Using process.isClient to load GoTop only on browser will eliminate the error.
const GoTop = process.isClient ? require('@inotom/vue-go-top').default : null;

export default {
  components: {
    Navbar,
    Footer,
    GoTop,
  }
}

Client API - Gridsome

Woo, Thanks @inotom !☺ It had been solved by this way.

source: gharchive/issue

authors: inotom kuleyu

repo: inotom/vue-go-top

license: MIT

license_type: permissive

license_source: github-api


text:
Link example projects

[x] Move Example Projects to GitHub

[x] Angular
[x] React
[x] Vue

[x] Search for occurrences in our docs
[x] Replace occurrences of example projects to the new Github Repos
[x] Update the core elements dependency to 1.0.0 in the example projects

New Repositories

https://github.com/inovex/elements-example-angular
https://github.com/inovex/elements-example-react
https://github.com/inovex/elements-example-vue

The codesandbox for the elements-angular package is not working correctly. We have to wait for codesandbox to provide a fix. I created a separate issue: https://github.com/inovex/elements/issues/128

repo: inovex/elements


text:
QA deployment (dev instance)

As a developer I want to preview the main branch on a QA stage, so that I have more confidence to rollout a new version and to test new features.

dev instance does now exist


text:
feat: (Un)ban participants (Frontend Implementation)

Description

This PR includes the frontend implementation of the ban feature implemented in #3770.
Closes #3618.
Changelog

Implemented a button to ban and unban a participant or moderator

Unbans can be found via the "disconnected" filter on the participants list

Added 2 tests to check whether that button exists

A confirmation window to ensure the action is intended

A toast confirms the action

Fixes the backend API to return the correct banned status

Prevents clickthrough on the Dialog Component and adds a custom classname for specific styling

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] The light- and dark-theme are both supported and tested
[x] The design was implemented and is responsive for all devices and screen sizes
[x] The application was tested in the most commonly used browsers (e.g. Chrome, Firefox, Safari)

(Optional) Visual Changes

Update:
Role buttons for banned participants are now removed and the participant name is centered.
Additionally the opacity is only reduced (increase from 0.2) to 0.6 to improve readability.

@brandstetterm It is more or less intentional.
IIRC @BenedictHomuth implemented the backend side in such a way that if a participant is banned, a forbidden error is thrown.
If you want to, I can change it to a 404 error, this leads to the 404 page in the frontend too.
For reference this is located in boards.go:123.

@brandstetterm It is more or less intentional. IIRC @BenedictHomuth implemented the backend side in such a way that if a participant is banned, a forbidden error is thrown. If you want to, I can change it to a 404 error, this leads to the 404 page in the frontend too.
For reference this is located in boards.go:123.

jFYI: Yes, we discussed about it and settled with 403 as seen here

So what are you suggesting? I am a teapot? :p

source: gharchive/pull-request

authors: BenedictHomuth CronJorian


text:
Update screenshots

[x] Create screenshots of all fitting

[x] network admin pages/modules

[x] /wp-admin/network/sites.php (new columns)
[x] /wp-admin/network/site-info.php?id=2 (edit site, MLP Tab)
[x] /wp-admin/network/site-new.php (example data of a new site)
[x] /wp-admin/network/settings.php?page=mlp (all checkboxes ticked, at least one active CPT)
[x] /wp-admin/network/settings.php?page=language-manager

[x] admin pages/modules

[x] /wp-admin/ (dashboard widget)
[x] /wp-admin/post-new.php (Translation meta boxes and additions to the Publish meta box)
[x] /wp-admin/edit-tags.php?taxonomy=category
[x] /wp-admin/edit-tags.php?action=edit&taxonomy=category&tag_ID=1&post_type=post (example term)
[x] /wp-admin/profile.php (Your preferred backend language)
[x] /wp-admin/widgets.php (Language Switcher widget)

[x] front-end modules

[x] Quicklinks
[x] Language Switcher widget

[x] Integrate Screenshots into

[x] readme.md (for GitHub)
[x] readme.txt (for wordpress.org)

Now live on https://wordpress.org/plugins/multilingual-press/screenshots/
Upload currently only on svn - http://plugins.svn.wordpress.org/multilingual-press/assets/

network settings
frontend view
table of sites with new columns

[ ] Update readme.md after new git structure necessary
[ ] Upload screenshots from svn - assets

As soon as the issue/164_file_structure branch is merged into master, this can be closed as well.

authors: bueltge tfrommen

repo: inpsyde/multilingual-press

license: mit

license_source: bigquery


text:
Utxo storage

This corresponds to https://github.com/input-output-hk/rust-cardano/pull/286. It removes genesis data (since that's now in exe-common). It also adds a debug command for decoding utxo files, e.g.
curl http://localhost:12080/mainnet/utxos-delta/0/1 | cardano-cli debug decode-utxos

Don't you need to update the cardano-deps submodule too ?

@NicolasDP Done!

authors: NicolasDP edolstra

repo: input-output-hk/cardano-cli


text:
Issue with wiki documentation (mentions deprecated? cardano-db-sync-extended)

Summary
As a developer trying to experiment with graphql I came across this misleading documentation.
https://github.com/input-output-hk/cardano-graphql/wiki
The data returned by this API is sourced from a PostgreSQL database produced by [cardano-db-sync-extended](https://github.com/input-output-hk/cardano-db-sync/tree/master/cardano-db-sync-extended)

The cardano-db-sync-extend url is missing and I believe this is deprected by standalone cardano-db-sync?
Steps to reproduce the bug

go to https://github.com/input-output-hk/cardano-graphql/wiki
read the first line

Actual Result
Invalid documentation mentioning deprecated cardano-db-sync-extended
Expected Result
Valid documentation mentioning deprecated cardano-db-sync
Environment
https://github.com/input-output-hk/cardano-graphql/wiki
Platform

[X] Linux (Ubuntu)
[X] Linux (Other)
[X] macOS
[X] Windows

Platform version
n/a
Runtime

[X] Node.js
[X] Docker

Runtime version
n/a

I ran into this issue as well, super confusing. You have to use the inputoutput/cardano-db-sync:13.0.0 image & add EXTENDED as a environment variable & set it to true.
//  Kubernetes pod
image: inputoutput/cardano-db-sync:13.0.0
          name: ocs-cardano-testnet-db-sync
          env:
            - name: NETWORK
              value: testnet
            - name: EXTENDED
              value: "true"

Thanks for opening this issue. I've corrected the Docker Compose file in https://github.com/input-output-hk/cardano-graphql/commit/41c71e09963bb5d2c57626b0637f058eb770b3e0, and will update the Wiki to reflect the upstream changes.

authors: Jack-0 rhyslbw thatsbrandon

repo: input-output-hk/cardano-graphql


text:
CAD-2147: Support additional scripts in structured metadata.

Additional comments per commit.

I should point out that the failing CI here is expected; I'm waiting for Ryan's PR on generalising the tests to fix things.

@redxaxder Please note that in the last commit I changed the CDDL format to match the encoder, because it seemed completely non-obvious to me how to use Coders to represent the suggested format. But perhaps you or @TimSheard know how to do this easily, in which case I'd welcome a commit changing the representation (or just advice as to how to do this). This can either be part of this PR or a follow-up

@redxaxder Please note that in the last commit I changed the CDDL format to match the encoder, because it seemed completely non-obvious to me how to use Coders to represent the suggested format. But perhaps you or @TimSheard know how to do this easily, in which case I'd welcome a commit changing the representation (or just advice as to how to do this). This can either be part of this PR or a follow-up

Your chosen encoding here is actually smaller than the one before. (In the case where there are two kinds of metadata, which is where we are). I think it might we worth talking about longer term plans for this.

repo: input-output-hk/cardano-ledger-specs


text:
investigate "db-analyser tool"

could this tool help us in any way?

https://github.com/input-output-hk/ouroboros-network/pull/3435/files

< In progress >
Tried to use it with our local testnet cluster. I encountered some problems and decided to open a ticket:
https://github.com/input-output-hk/ouroboros-network/issues/3554
Slack Thread:
https://input-output-rnd.slack.com/archives/CDA6LUXAQ/p1640116503106600

thank you @ArturWieczorek

repo: input-output-hk/cardano-node-tests


text:
Expose LocalTxSubmissionClient data constructor

Any user of the LocalNodeClientProtocols IPC interface will need to construct this type. Hence it needs to be exported.

Also can you tell me more about your use case that you should need to use LocalTxSubmissionClient directly?

Also can you tell me more about your use case that you should need to use LocalTxSubmissionClient directly?

Of course. In https://github.com/input-output-hk/hydra we are connecting to a local cardano-node to submit transactions using the ouroboros node-to-client protocol. Lately I tried to use the IPCmodule from cardano-api, instead of ouroboros-network-framework and protocols directly.

I pushed a commit to fix the compile error.

repo: input-output-hk/cardano-node


text:
[CSM-116] Add TLS to Daedalus HTTP/WebSocket interface

Don't merge - this should be merged to master
This implements TLS over HTTP using warp-tls package: https://github.com/input-output-hk/cardano-sl/blob/master/src/Pos/Web/Server.hs#L77
It also adds TLS over WebSockets using wai-websockets package: https://github.com/input-output-hk/cardano-sl/blob/master/src/Pos/Wallet/Web/Server/Sockets.hs#L84 https://github.com/input-output-hk/cardano-sl/blob/master/src/Pos/Wallet/Web/Server/Methods.hs#L142
Certificates are generated during Daedalus installation (PR here https://github.com/input-output-hk/daedalus/pull/293 ).
To test TLS one first have to generate certificates with code from PR above:
[akegalj@notebook daedalus]$ cd installers/tls/
[akegalj@notebook tls]$ sh ../build-certificates-unix.sh
Generating certificates.
...
============================================================================
[9/9] Cleanup
============================================================================
Oll Korrect

Node will initially look for generated certificate in folder where it is run from (if certificate path is not explicitly set). So to test it we will copy it to cardano-sl repo folder where we will test. Go to cardano-sl repo:
[akegalj@notebook cardano-sl]$ cp ../daedalus/installers/tls/tls/server/server.{crt,key} .
[akegalj@notebook cardano-sl]$ cp ../daedalus/installers/tls/tls/ca/ca.crt .

Now we can normally try to build and run the project (in prod or dev mode):
[akegalj@notebook cardano-sl]$ scripts/build/cardano-sl.sh
[akegalj@notebook cardano-sl]$ scripts/launch/demo-with-wallet-api.sh

You can test is everything ok with TLS backend with curl:
[akegalj@notebook cardano-sl]$ curl --cacert ca.crt -v https://localhost:8090/api/settings/sync/progress

If you got the response - we are doing fine. Lets see how to use it with client-api now. All of endpoints that require talking to backend will be given one additional parameter as a first parameter. Lets see this by example first (before this you should build client-api as you always do - if you don't know how to do it ping @akegalj and he will expand):
[akegalj@notebook cardano-sl]$ cd daedalus/
[akegalj@notebook daedalus]$ node
> var api = require('../output/Daedalus.ClientApi')
undefined
> var tls = api.tlsInit('/home/akegalj/projects/serokell/cardano-sl/ca.crt')
undefined
> tls
[ Tuple { value0: 'protocol', value1: 'https:' },
  Tuple { value0: 'hostname', value1: 'localhost' },
  Tuple { value0: 'port', value1: 8090 },
  Tuple {
    value0: 'ca',
    value1: <Buffer 43 65 72 74 69 66 69 63 61 74 65 3a 0a 20 20 20 20 44 61 74 61 3a 0a 20 20 20 20 20 20 20 20 56 65 72 73 69 6f 6e 3a 20 33 20 28 30 78 32 29 0a 20 20 ... > } ]
> api.syncProgress(tls).then(console.log).catch(console.log)
Promise {
  <pending>,
  domain:
   Domain {
     domain: null,
     _events: { error: [Function: debugDomainError] },
     _eventsCount: 1,
     _maxListeners: undefined,
     members: [] } }
> { _spPeers: 0,
  _spNetworkCD: { getChainDifficulty: 2 },
  _spLocalCD: { getChainDifficulty: 2 } }
> api.getWallets(tls).then(console.log)
Promise {
  <pending>,
  domain:
   Domain {
     domain: null,
     _events: { error: [Function: debugDomainError] },
     _eventsCount: 1,
     _maxListeners: undefined,
     members: [] } }
> []

As shown in example above, API changed in a way that we have to provide tls options as a first parameter. We can load tls options with api.tlsInit and they will configure TLS. Important is to mention that tlsInit will load file provided in filepath from filesystem. As Daedalus UI is built with Electron - which doesn't allow usage of filesystem from UI threads - usage is intended as:

call tlsInit in Electron main thread where filesystem is available
provide loaded tls options from step above ^ whenever you have to communicate with the backend as a first parameter

These methods changed and now require tls options as a first parameter. Other parameters are intact:

testReset
getWallet
getWallets
updateWallet
renameWalletSet
deleteWallet
getAccount
getAccounts
getWalletAccounts
updateAccount
deleteAccount
isValidAddress
getLocale
updateLocale
updateTransaction
getHistory
getHistoryByAccount
getHistoryByWallet
getAddressHistory
nextUpdate
applyUpdate
reportInit
blockchainSlotDuration
systemVersion
syncProgress
importBackupJSON
exportBackupJSON
notify

Other endpoints don't require tls.
Follow up is to check performance of TLS once it is merged in Daedalus UI and used. We might have to slightly reconfigure in order to optimize https://issues.serokell.io/issue/CSM-368 if performance will decrease after this is merged.

Closing in favor of https://github.com/input-output-hk/cardano-sl/pull/1172

repo: input-output-hk/cardano-sl


text:
Minor fixes.

Description

Linked issue

Type of change

[ ] 🐞 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 change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

@erikd Do we merge it or is the fix already in develop?

Closing this in favor of #3565 so it can be run thought CI.

authors: erikd jcmincke yihuang


text:
Flaky STAKE_POOLS_JOIN_05 - Can join when stake key already exists

Context

https://github.com/input-output-hk/cardano-wallet/pull/2214#issuecomment-705079913
Test Case

https://github.com/input-output-hk/cardano-wallet/blob/master/lib/core-integration/src/Test/Integration/Scenario/API/Shelley/StakePools.hs#L530-L553
Failure / Counter-example
 src/Test/Integration/Scenario/API/Shelley/StakePools.hs:530:5:
  1) API Specifications, SHELLEY_STAKE_POOLS, STAKE_POOLS_JOIN_05 - Can join when stake key already exists
       uncaught exception: RequestException
       DecodeFailure "{\"code\":\"network_unreachable\",\"message\":\"The node backend is unreachable at the moment. Trying again in a bit might work.\"}"

  To rerun use: --match "/API Specifications/SHELLEY_STAKE_POOLS/STAKE_POOLS_JOIN_05 - Can join when stake key already exists/"

Resolution

QA

Got an error from GitHub and created again, but seems the first one got through -> #2230

repo: input-output-hk/cardano-wallet


text:
Fix integration tests

Issue
None, but bors was failing for unrelated reasons in #764, and I was able to reproduce the same failures locally.
Overview

[x] Allow ports up to 65535 in CLI (we might generate them randomly https://input-output-rnd.slack.com/archives/GBT05825V/p1569852386030200)
[x] Don't way 65 seconds for log output, because "waitForConnection" will time out in that time.

Comments

bors try

bors try

stack test cardano-wallet-jormungandr:integration --ta '--match "/No backend required/Launcher CLI tests/LAUNCH - cardano-wallet launch [SERIAL]/LAUNCH - Invalid block0 file (not a serialized block)/"' Passes locally for me, but failed in CI last time. The very final Alert-line does not appear in the CI's stdout.
test/integration/Test/Integration/Jormungandr/Scenario/CLI/Launcher.hs:155:13:
--
  | 1) No backend required, Launcher CLI tests, LAUNCH - cardano-wallet launch [SERIAL], LAUNCH - Invalid block0 file (not a serialized block)
  | "\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 16:48:44.36 UTC] Using state directory: /var/lib/buildkite-agent/.local/share/cardano-wallet/jormungandr/testnet\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 16:48:44.36 UTC] Running as v2019.9.13\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 16:48:44.36 UTC] Wallet backend server starting...\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 16:48:44.36 UTC] Node is J\246rmungandr on testnet\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 16:48:44.36 UTC] Database layer started.\n\ESC[34m[iohk.cardano-wallet.launch:Info:ThreadId 4]\ESC[0m [2019-09-30 16:48:44.36 UTC] Generated J\246rmungandr's configuration to: /var/lib/buildkite-agent/.local/share/cardano-wallet/jormungandr/testnet/jormungandr-config.yaml\n" does not contain "As far as I can tell, this isn't a valid block file: test/data/jormungandr/secret.yaml"

Checking CI's stderr:
bors try

bors try

What kind of sorcery is this? Either 0d43cc4 weirdly fixes the tests, or the tests are flaky.
bors try

@rvl any idea?

bors r+

Adding an assertion and then having the tests pass tells me that the tests are still flaky. Something is failing before it reaches the parse block file bit. I am guessing that jormungandr fails to start, however no log messages are shown. Perhaps jormungandr exits because the block file in its config is invalid.

Adding an assertion and then having the tests pass tells me that the tests are still flaky

@rvl I don't think the added assertion has anything to do with it to be honest. More likely, the port bound was the issue here.

bors r+

bors r-

bors r+

bors try

bors try

bors r-

bors r+

bors r+

bors r+

bors r+

authors: Anviking KtorZ rvl


text:
Fix/ddw 257 Prevent dragging of images within the application

This PR disables dragging of static UI images elements:

TopBar: Node sync status icon
General Settings > Display: Theme thumbnail images
Paper wallet certificate > 3rd dialog: Paper wallet certificate thumbnail

Screenshots:

Review Checklist:
Basics

[ ] PR is updated to the most recent version of target branch (and there are no conflicts)
[ ] PR has good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance tests are passing (npm run test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (npm run dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (npm run package / CI builds)
[ ] There are no flow errors or warnings (npm run flow-test)
[ ] There are no lint errors or warnings (npm run lint)
[ ] Text changes are proofread and approved (Jane Wild)
[ ] There are no missing translations (running npm run manage-translations produces no changes)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (npm run storybook)
[ ] In case of npm dependency changes both package-lock.json and yarn.lock files are updated

Code Quality

[ ] Important parts of the code are properly documented and commented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-rendering
[ ] Any code that only works in Electron is neatly separated from components

Testing

[ ] New feature / change is covered by acceptance tests
[ ] All existing acceptance tests are still up-to-date
[ ] New feature / change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review:

[ ] Merge PR
[ ] Delete source branch
[ ] Move ticket to done on the Youtrack board

Reviewing this now …

authors: DominikGuzei nikolaglumac

repo: input-output-hk/daedalus


text:
[Partnership] Consider dStore, part of Catalys project dCloud as a Data + Metadata Decentralized Distributed Data Storage platform

Hi, it was sort of obvious to me since I started following this research, but in the  Decentralized software updates video from Cardano Virtual Summit 2020 you explicitly mention the need for Data + Metadata Decentralized Distributed Data Storage platform.
Me and my main partner in crime have both years of relevant experience in the Data Storage industry, myself, I have 7 years of working experience with NetApp producs, 3 of which were a Professional Consultant Role at NetApp UK&I directly, I also have relevant experience with scale-out distributed GPFS storage  (IBM Spectrum Scale now), CEPH and current Decentralized Distributed Data Storage projects running on blockchain such as Storj.

Our intent for dStore MVP is the ability to run GitLab OSS version locally (probably via Docker) but having the Git repository data stored on the dStore platform via AWS S3 compatible gateway. We plan to implement the best features of Storj, Filecoin and CEPH in one solution, thus I believe it would be better if we take this part of a research and delivery and cooperate as opposed to developing own solution...
I made an elevator pitch for dCloud as a whole on The Cardano Effect podcast, I will try to make a dStore pitch on my own The Storage Guy channel...
Would this be an area to cooperate on, could we schedule a call to get your functional and non-functional requirements to make sure we would be able to support the Decentralized Software Updates efforts on our platform, it would then bring a great benefit that the Cardano Treasury could pay it's own operational costs for hosting all of it's relevant source-code and associated metadata...
Other References:

Decentralized Cloud Platfom proposal on IdeaScale

@romainPellerin, can we discuss this synergetic aliance?

I just got off of the call with @romainPellerin, the Decentralized Storage Solution piece is not within scope of the current contract, and we can discuss possible partnerhsip and it's feasibility once proposal for "Cardano Phase 2" is being finalized or after it is voted on... We are thinking follow-up call in one to two months when there will be more claridy regarding dCloud project.


text:
updating changelog and removing versioning

Versioning our ledger spec with dates instead of semantic-ish versions.

There's a benefit in removing any reference to git, since it gets removed in the nix build and would in any case force a rebuild on each new update, even if the spec hasn't changed.

There's a benefit in removing any reference to git, since it gets removed in the nix build and would in any case force a rebuild on each new update, even if the spec hasn't changed.

good point, now is probably also a good time to remove the git reference

Should we still tag commits ?

That's a good question. I think we should not.

repo: input-output-hk/fm-ledger-rules


text:
Fix(extension): LW-7358 fix incorrect time being shown for activities

Checklist

[x] JIRA - LW-7358
[x] Proper tests implemented
[x] Screenshots added.

Proposed solution
Date/Time was formatted as UTC instead of local time resulting in the times shown in the UI being off by user's time offset, so the fix consists in extending the time/date formatting helpers to allow for utc vs local time and use local time in activity. The formatters were refactored to require explicitly stating the time standard (local vs UTC) to make the intention clear to the caller/reader and avoid future confusion.
These helpers were also used to format data about blocks (used in activity details modal) and UTC was used there apparently intentionally, so to make that clear, this PR involves also refactoring the formatted time fields to explicitly contain "utc" in their name to make this clear to the reader and avoid confusion as the values are plain strings.
I also noticed that we needlessly append "AM/PM" to otherwise 24H-formatted times in the activity and the transaction times in the details modal are 12H-formatted, so I unified both to 24H (while keeping the transaction detail time in UTC) - agreed with PM on that, see JIRA task comments for context
Testing
Visit "Activity" tab and check that the time of activities corresponds to the actual (local) time they happened at (e.g. via block explorer). Check also that UTC time shown in the activity details is correct
Screenshots
Before:

After:

Allure report
allure-report-publisher generated test report!

smokeTests: ❌ test report for 9ba0db6d

passed
failed
skipped
flaky
total
result

Total
33
2
0
0
35
❌

Please use the format template in constant and then we're good to go 🎉

repo: input-output-hk/lace


text:
[LW-8649] Adds data url for connect source in csp

Checklist

[x] JIRA - LW-8649
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Adds data URL for connect source in CSP
Testing
Get the branch, run yarn cleanup && yarn install move to apps/browser... run yarn dev load unpacked extension. It should now work.
Screenshots
N/A

Allure report
allure-report-publisher generated test report!

smokeTests: ❌ test report for a5470341

passed
failed
skipped
flaky
total
result

Total
30
2
0
0
32
❌

Nice work tracking this down @VanessaPC. It would be good to add some detail to the commit message, as this is lacking context on why the change is needed.

Addressed -> 4f2a60ddb9e8966d0df95684502c256ee0554d66  I also updated the ticket for further details.


text:
ECS-3077 Apply style guide, tighten some sentences.

Content

This PR includes a review of the protocol description in protocol.md
Pre-submit checklist

Branch

[x] Tests are provided (if possible)
[x] Crates versions are updated (if relevant)
[x] Commit sequence broadly makes sense
[y] Key commits have useful messages

PR

[y] No clippy warnings in the CI
[y] Self-reviewed the diff
[y] Useful pull request description
[y] Reviewer requested

Documentation

[x] Update README file (if relevant)
[x] Update documentation website (if relevant)
[x] Add dev blog post (if relevant)

Comments

Issue(s)
Relates to ECS-3077
Relates to #YYY or Closes #YYY

Committed some more improvements. Looks good, @NeilBurgess42 please mark the PR as 'ready for review'.
Over to @jpraynaud .
Thanks so much, everyone!

repo: input-output-hk/mithril


text:
Can Ouroboros.Consensus.Storage.ChainDB.Impl.Follower be simplified via its private registry

After Issue #2892, the combinator that provides a private registry will be used to allocate Follower. Can the Follower implementation rely on the privateness of the registry in order to offload some of the tracking its doing to the registry? Basic idea: when we close the Follower, it can close its private registry.

@Jasagredo
https://github.com/input-output-hk/ouroboros-network/blob/8d44955afdebcf9cc521f60e3a9f31e853ace2c1/ouroboros-consensus/src/Ouroboros/Consensus/Util/ResourceRegistry.hs#L679-L681
https://github.com/input-output-hk/ouroboros-network/blob/c82309f403e99d916a76bb4d96d6812fb0a9db81/ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs#L170-L178
I think the only step we could take for this Issue would be to replace the uses of closeFollowerState with closeRegistry. We might be able to eliminate another thin layer if we also relied on the private registry to remove the key from the cdbFollowers field.
Generally speaking, just because I closed something in a registry doesn't mean I can close the whole registry. However, because this registry is private to the follower, that's exactly what it means. Thus the Follower's clean-up logic need not duplicate what is already in the clean-up handler's for the items in its private registry.
I haven't checked the tests, but the implementation at least does seem to only invoke newFollower with a private registry:
$ git grep -C1 -w -e newFollower -e closeFollower -e 'chainSync.*ServerFollower' -- 'ouroboros-consensus/*hs'
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-    Tip
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs:  , chainSyncBlockServerFollower
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-  , chainSyncBlocksServer
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs:  , chainSyncHeaderServerFollower
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-  , chainSyncHeadersServer
--
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs:chainSyncHeaderServerFollower
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-    :: ChainDB m blk
--
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-    -> m (Follower m blk (WithPoint blk (SerialisedHeader blk)))
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs:chainSyncHeaderServerFollower chainDB registry = ChainDB.newFollower chainDB registry getSerialisedHeaderWithPoint
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs:chainSyncBlockServerFollower
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-    :: ChainDB m blk
--
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-    -> m (Follower m blk (WithPoint blk (Serialised blk)))
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs:chainSyncBlockServerFollower chainDB registry = ChainDB.newFollower chainDB registry getSerialisedBlockWithPoint
ouroboros-consensus/src/Ouroboros/Consensus/MiniProtocol/ChainSync/Server.hs-
--
ouroboros-consensus/src/Ouroboros/Consensus/Network/NodeToClient.hs-      bracketWithPrivateRegistry
ouroboros-consensus/src/Ouroboros/Consensus/Network/NodeToClient.hs:        (chainSyncBlockServerFollower (getChainDB kernel))
ouroboros-consensus/src/Ouroboros/Consensus/Network/NodeToClient.hs-        ChainDB.followerClose
--
ouroboros-consensus/src/Ouroboros/Consensus/Network/NodeToNode.hs-      bracketWithPrivateRegistry
ouroboros-consensus/src/Ouroboros/Consensus/Network/NodeToNode.hs:        (chainSyncHeaderServerFollower (getChainDB kernel))
ouroboros-consensus/src/Ouroboros/Consensus/Network/NodeToNode.hs-        ChainDB.followerClose
--
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/API.hs-      --
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/API.hs:    , newFollower ::
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/API.hs-           forall b. ResourceRegistry m
--
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/API.hs---
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/API.hs:-- See 'newFollower' for more info.
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/API.hs---
--
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl.hs-          , stream                = Iterator.stream  h
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl.hs:          , newFollower           = Follower.newFollower h
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl.hs-          , getIsInvalidBlock     = getEnvSTM  h Query.getIsInvalidBlock
--
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs-    closeAllFollowers
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs:  , newFollower
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs-  , switchFork
--
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs-
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs:newFollower ::
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs-     forall m blk b.
--
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs-  -> m (Follower m blk b)
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs:newFollower h registry blockComponent = getEnv h $ \CDB{..} -> do
ouroboros-consensus/src/Ouroboros/Consensus/Storage/ChainDB/Impl/Follower.hs-    -- The following operations don't need to be done in a single transaction

Ultimately, this seems moot at the moment. The Follower is only closed (a) by its private registry bracket and (b) when closing the ChainDB (grep for closeAllFollowers). But even so the current code has some unnecessary details in the Follower close function.

repo: input-output-hk/ouroboros-network


text:
Batch transactions in the mempool

Description

description of the pull request, if it fixes a particular issue it should link
the PR to a particular issue, see
ref
Checklist

Branch

[ ] Commit sequence broadly makes sense
[ ] Commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[ ] Self-reviewed the diff
[ ] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[ ] Reviewer requested

Under a VERY specific situation we encounter the errors which we are looking for:

Node adds tx 8922e396 which produces TxOuts 8922e396 (TxIx 0-10)
Node adds txs 18b1134e...d07cc4f2bf which consume TxOuts 8922 (0-9)
Node adopts a block which contains tx 8922
Node resyncs the ledger state, revalidating 18b1134e...d07cc4f2bf
Node tries to add a003b45 which consumes TxOut 8922 (10)
getStatePair reports the following:

The transactions to add are these:
- `a003b45`: `[8922e3 (TxIx 10)]`

The transactions to keep are these:

The keys needed by all of them are these:
- `[8922e3 (TxIx 10)]`

Current values and diffs in mempool:
- `CardanoLedgerTables [] []`

So:

18b1134e...d07cc4f2bf which previously were valid, are now invalid
Therefore TxOuts 8922 (0-9) must be gone when resyncing?

The code for resyncing basically calls getStatePair and then runs the transactions. How could this be called and still get a wrong version of the changelog?
implSyncWithLedger is invoked by forkSyncStateOnTipPointChange when the result from this pseudo-call changes:
ledgerTipPoint . ledgerState <$> fmap LedgerDB.ledgerDbCurrent . LgrDB.getCurrent cdbLgrDB $ chainDB

And then getStatePair through ChainDB.getLedgerStateForTxs and Query.getLedgerStateForKeys does the following:
ldb0 <- atomically $ LgrDB.getCurrent cdbLgrDB
...
(a, ks) <- m (LedgerDB.ledgerDbCurrent ldb0)

So here comes the feared question. Might the dbchangelog be outdated when pushing blocks?
Investigating...

Tracing the dbChangelog that is set when doing chain selection shows that indeed the dbChangelog is correct (or at least it is not empty as I was expecting). A more important detail: adding tracers to the chain selection code (which slow down the code), results in no tx rejection anymore. It seems there is a race on the LedgerDB?

So after some time of investigation I can conclude the following in this regard:
The logic underneath seems correct. Every transaction that is reported as failing, is indeed already included in a block by the other node.
So it seems to be just a matter of performance and not of bugs. Need to re-evaluate the priorities after this revelation.


text:
Eq instance only supports a pair of Tuples. Request to make it indefinite

I was using the:

Plutus Playground

Link to gist with saved setup that reproduces the issue:
https://gist.github.com/shaansundar/d0b7aecab6c4d55d90ebfd58eb96f4a0

Error:
Compilation Error, Line 89, Column 1 (jump)
 error:
    • No instance for (Schema.ToSchema (Bool, Bool, Bool))
        arising from a use of ‘Playground.Schema.endpointsToSchemas’
    • In the expression:
        Playground.Schema.endpointsToSchemas
          @((Data.Row.Internal..\\) ((.\/) ((.\/) BlockchainActions (Endpoint "give" Integer)) (Endpoint "grab" (Bool,
                                                                                Bool,
                                                                                Bool))) BlockchainActions)
      In an equation for ‘schemas’:
          schemas
            = Playground.Schema.endpointsToSchemas
                @((Data.Row.Internal..\\) ((.\/) ((.\/) BlockchainActions (Endpoint "give" Integer)) (Endpoint "grab" (Bool,
                                                                                Bool,
                                                                                Bool))) BlockchainActions)
   |
89 | mkSchemaDefinitions ''GiftSchema
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Closing as we have dropped the support of Plutus Playground. This shouldn't be a blocker anymore.

repo: input-output-hk/plutus-apps


text:
SCB message queue

Ideally using some kind of decent library for this kind of thing. Probably doesn't need to be super fancy, but a good testing story would be great.

So far, eventful is looking pretty promising. It appears to be quite mature, and has support for in memory & SQL stores, cached folds over the database, and testing support. I'm rigging up a prototype to exercise the main features before committing...

Last commit in 2017, though :grimacing:

True, true. That might be a sign that it's basically done, though that feels a bit optimistic.
It's not the only option of course...

...research continues. :-)

authors: krisajenkins michaelpj

repo: input-output-hk/plutus


text:
Pass an argument that hydra passes to prevent CI doing something different

Otherwise it will try and build the git revs, which we don't want.
Draft until I see if it works.

oops, needs to be from a branch in the repo


text:
Chore: migrate to shared github actions

Description
This is an experiment in using shared github actions for some common tasks: https://github.com/inrupt/javascript-style-configs/pull/21
Checklist

[ ] All acceptance criteria are met.
[ ] Relevant documentation, if any, has been written/updated.
[ ] The changelog has been updated, if applicable.
[ ] New functions/types have been exported in index.ts, if applicable.
[ ] New modules (i.e. new .ts files) are listed in the exports field in package.json, if applicable.
[ ] New modules (i.e. new .ts files) are listed in the typedocOptions.entryPoints field in tsconfig.json, if applicable.
[ ] Commits in this PR are minimal and have descriptive commit messages.

This PR bumps the version to .
Checklist

[ ] I used npm version <major|minor|patch> to update package.json, inspecting the changelog to determine if the release was major, minor or patch.
[ ] The CHANGELOG has been updated to show version and release date - https://keepachangelog.com/en/1.0.0/.
[ ] @since X.Y.Z annotations have been added to new APIs.
[ ] The only commits in this PR are:

the CHANGELOG update.
the version update.
@since annotations.

[ ] I will make sure not to squash these commits, but rebase instead.
[ ] Once this PR is merged, I will push the tag created by npm version ... (e.g. git push origin vX.Y.Z).

I think we may actually want these workflows to just be used as part of the pipeline on the one workflow — or, at least, have all the on: push workflows together as a pipeline with multiple jobs.

Absolutely, we'll want one workflow running off reusable ones running on push and gating PRs.
We'll also want a couple running on various schedules.
It seems sensible to start with the CI on: push: one.

This has been done by @NSeydoux in another PR, closing

authors: ThisIsMissEm matthieubosquet

repo: inrupt/solid-client-notifications-js


text:
Add tests

After #20 it might be nice to stand-up some tests with karma-webpack or similar - this will probably help reduce the maintenance overhead and make dealing with PRs a little easier.

#20 is fixed. This is unblocked! :tada:
Once we have tests I’d like to get the old Android tests and some of the other open PRs cleaned up.

Would a PR submitted using mocha be ok?

@dardone any tests are better than no tests!
Ideally I want them to be able to run in browserstack or something similar to verify that we get things like oldish Android working and not regressing
If the nwb tool has opinions I would like to follow those for consistency in insin/* repos, but that isn't a hard rule for now.
Thank you for considering taking in this effort.

Sounds good. We use a combination of nightwatch and mocha on a project I've been working on, so I'll just submit my other PR for this project before you guys require tests!

authors: dardrone iamdustan muffinresearch

repo: insin/react-maskedinput


text:
wrong syntax in tests

/test/shams/core-js.js line 11
return; should not be there
/test/shams/get-own-property-symbols.js line 11
return; should not be there
those syntax errors causing IDEs to highlight your package as faulty

It should, in fact, be there - these are node modules, in which top level return is allowed. If your IDE is marking it as a syntax error, your IDE is faulty.

authors: alesak ljharb

repo: inspect-js/has-symbols


text:
fixed some issues and add some restapis for creation service - [closed]

In GitLab by @liyanq528 on Sep 25, 2017, 04:26
Merges 20170911 -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:02
closed

repo: inspursoft/board


text:
download_stories doesn't work

L = instaloader.Instaloader(dirname_pattern=out_path, download_video_thumbnails=False, download_geotags=False, download_comments=False, save_metadata=False, compress_json=False, post_metadata_txt_pattern=None, storyitem_metadata_txt_pattern=None, max_connection_attempts=3, request_timeout=None, rate_controller=None, resume_prefix='iterator', check_resume_bbd=True)

L.load_session_from_file(login_username)
L.download_stories(ids, fast_update=False, filename_target=':stories')

this morning my code stopped working.
Has something changed on the instagram side?

it was a login problem

repo: instaloader/instaloader


text:
Context factory and session factory

Currently there is no way to customize the instantiation of session objects. I would need to use a dedicated proxy for the connections to insta.

waiting for workflows to be run

@aandergr would you please approve the workflow run?

@aandergr  PR updated to retain backwards compatibility -> please allow workflows to run

We will not mark Instaloader deprecated and switch to a new main class.
The workflows can be run locally, we use Pipenv for dependency pinning so the exact versions that are used in the workflows can be easily installed in a virtual environment. The commands that are executed are described in .github/workflows.

We will not mark Instaloader deprecated and switch to a new main class.

Please let me know why.
I see design flaws with this class that I tried to eliminate while keeping backwards compatibility.
If you don't deprecate it, you'll always have to cope with impacts of these flaws -> for long term maintenance of this project, that will cause headaches

It's important to understand that deprecating a core class has significant implications, even if backwards compatibility is maintained. Deprecation signals to users that they should begin transitioning to a new class, which can introduce confusion and a perception that the current design is fundamentally flawed or unstable. This is not a message we want to send unless there is a compelling, unavoidable reason to do so.
In the case of Instaloader, the issues you've identified can be addressed within the existing API design, as you mentioned. This approach allows us to improve the class without causing disruption or requiring users to adapt to a new interface. By enhancing the current design rather than creating a new one, we maintain consistency and avoid the overhead associated with maintaining multiple parallel implementations.
While I agree that forward-thinking design is crucial, it's equally important to balance innovation with stability. For long-term maintenance, we believe it's more efficient to refine and iterate on the existing class, addressing flaws incrementally while preserving the established API. This approach minimizes potential headaches by reducing the complexity that comes with maintaining deprecated code and managing transitions.

authors: Henkhogan aandergr


text:
114359 - Adding description for synthetic test PATCH API

Adding new OpenAPI: PATCH SyntheticTest

Story / Card
ui-backend PR

This PR cannot be merged until 242 is completed

repo: instana/openapi


text:
Update flag text format in ilab model evaluate commands in README

Adjusted the text format of some flags in the
commands section of the README for improved readability and consistency.

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

force pushed to fix the commit message

@Mergifyio backport release-v0.18

authors: alinaryan nathan-weinberg

repo: instructlab/instructlab


text:
phoenix(constellation)

https://github.com/instructlab/taxonomy/issues/830
If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

...
...
...

Input given at the prompt

   ...

Response from the original model

  ...

Response from the fine-tuned model

  ...

Contribution checklist

[ ] The contribution was tested with ilab generate
[ ] No errors or warnings were produced by ilab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file contains at least 5 seed_examples
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)
[ ] An attribution.txt file in the same folder as the qna.yaml file
[ ] Content does not include PII or otherwise sensitive or confidential information
[ ] Content does not include anything documented in the project's Avoid these Topics guidelines

Closing per the combined PR here: https://github.com/instructlab/taxonomy/pull/1159

authors: gharunsaikumar jjasghar

repo: instructlab/taxonomy


text:
Add support/validate for Torch 2.5 (required for Intel Gaudi 1.19.0)

Open question: Can we unbound torch going forward?

This blocks https://github.com/instructlab/instructlab/issues/2669 as we'll need the training library to support this before we can attempt bumping it in the CLI
Is this ticket itself blocked by https://github.com/instructlab/training/issues/293?

@JamesKunstle - should we update this issue to cover new request in ilab repo https://github.com/instructlab/instructlab/issues/2772

@ktam3 Seems like we need to bump torch for everybody, this issue can just continue to exist, we'll take care of this.

From the conversation between prarit and nathan in https://github.com/instructlab/instructlab/issues/2669 - it looks like we should be treating version bumps as separate requests for each arch? Does that make sense in the training repo?

Updating description to make this more general to cover gaudi and ROCm

authors: JamesKunstle ktam3 nathan-weinberg

repo: instructlab/training


text:
Allow setting the root of a filesystem

It would be useful to be able to specify a filesystem with an arbitrary root - e.g.
fs = LocalFileSystem(root='C:/temp')

All operations would then be performed relative to this root - e.g. fs.ls('/') would then list the contents of C:/temp

This is an interesting idea. pyfilesystem2 has something similar.
Rather than adding this capability to LocalFileSystem or the general spec, I would write a new implementation PrefixFileSystem which operates on any other filesystem and does the path manipulation you would need here. This would be like the caching file systems, with target_protocol and target_options kwargs.
Another idea from pyfilesystems2 would be to generalise this further: to be able to "mount" any other filesystem as some given path, so that, for instance "/s3/" lives alongside normal local files. I'm not certain how useful that is, given the differences between implementations.

On the other hand, we already have ._strip_protocol() on all filesystems that would be a natural and easy place to put this logic.

I do like the PrefixFileSystem  idea. We have something like that. However, the interaction of ls and _strip_protocol is tricky imo. The former needs to reverse the latter. Then, some operations don't seem to use _strip_protocol so we override major operations like get and rm as well. Furthermore, stripping root might not catch all affected detail fields of ls.
Did you think a PrefixFileSystem would work solely by overriding _strip_protocol? Maybe I'm on the wrong foot here.

Based on what I read on this post, I put this to work and it seems to be working fine based on a few tests.
import os
from fsspec.implementations.local import LocalFileSystem, stringify_path, make_path_posix

class PrefixLocalFileSystem(LocalFileSystem):

    def __init__(self, root_path='/', *args, **kwargs):
        self.root_path = stringify_path(root_path)
        super().__init__(*args, **kwargs)

    def _strip_protocol(self, path):
        path = stringify_path(path)
        if path.startswith("file://"):
            path = path[7:]
        return os.path.join(self.root_path, path).rstrip("/")

Based on what I read on this post, I put this to work and it seems to be working fine based on a few tests.
import os
from fsspec.implementations.local import LocalFileSystem, stringify_path, make_path_posix

class PrefixLocalFileSystem(LocalFileSystem):

    def __init__(self, root_path='/', *args, **kwargs):
        self.root_path = stringify_path(root_path)
        super().__init__(*args, **kwargs)

    def _strip_protocol(self, path):
        path = stringify_path(path)
        if path.startswith("file://"):
            path = path[7:]
        return os.path.join(self.root_path, path).rstrip("/")

@brunorpinho , I don't think so, because the output of ls would include the original real paths of files, not their prefixed versions. Lots of other methods depend on ls (glob, find, any recursive-enabled method).
In any case,  it would be a shame to provide something like this to the local files only.

@martindurant yep, I see.

This would be extremely useful with s3 filesystems, so that you can change the fs root to the specified bucket without prefixing the bucket to every path

Perhaps you could make another implementation that wraps an arbitrary backend filesystem and does all the path manipulations? That's the kind of thing going on with the caching filesystems and ReferenceFileSystem, so there are precedents. Also, universal_path's implementation might be useful using Path-like objects.

I see thanks for the suggestions!
Do you have any specific pointer for the universal_path and Path-like objects?

See https://github.com/Quansight/universal_pathlib , and feel free to ask further questions there.

A bit unrelated, but my 2c about Path-like objects: we need to be careful with those, as things might get really slow if you create lots of them. We have this problem with PathInfo's in dvc right now and working on getting rid of those in favor of using strings. It is also easy for anyone writing a new filesystem to accidentally hinder the performance when working with batches of files.

things might get really slow if you create lots of them
Can you link to an issue? It's unclear if creating PurePath and/or accidental IO is concerning you.

@ahirner It is creating PurePath, not accidental IO. When dealing with hundreds of thousands of files, creating PurePath for each one of those is takes significant time. Just bringing this up for the record, but it is not like this is unusual or not known. I see that @lucmos took good care of that in #745

authors: ahirner brunorpinho dc-devops dhirschfeld efiop lucmos martindurant


text:
url_to_fs does not work with ssh (host argument missing)

When using 'url_to_fs("ssh://host/folder1")' I get the following error message:
TypeError: __init__() missing 1 required positional argument: 'host'
I am not sure of what is the issue since the function '_get_kwargs_from_urls' correctly retrieves the host from the URL, but the FS creation is called with empty args and kwargs (and has been a long time sicne I read that part of the code).

I have been checking and open_files (using underneath get_fs_token_paths) seems to work.
This "get_fs_token_paths" is the actual method exported in init.py but url_to_fs seems in general a better name for an external API. Also it seems url_to_fs is actuall not very much used anywhere in the code.
Additionally I see there is a huge amount of repetition between get_fs_token_paths and url_to_fs. Could be an idea to merge them (partially or completely)...

Copying the relevant part from get_fs_token_paths seems to work...
def url_to_fs(url, **kwargs):
    """Turn fully-qualified and potentially chained URL into filesystem instance"""
    chain = _un_chain(url, kwargs)
    if len(chain) > 1:
        kwargs = chain[0][2]
        inkwargs = kwargs
        for i, ch in enumerate(chain):
            urls, protocol, kw = ch
            if i == 0:
                continue
            inkwargs["target_protocol"] = protocol
            inkwargs["target_options"] = kw.copy()
            inkwargs["fo"] = urls
            inkwargs = inkwargs["target_options"]
        protocol = chain[0][1]
        urlpath = chain[-1][1] + "://" + split_protocol(urls)[1]
        fs = filesystem(protocol, **kwargs)
    else:
        protocol, urlpath = split_protocol(url)
        cls = get_filesystem_class(protocol)

        options = cls._get_kwargs_from_urls(url)
        urlpath = cls._strip_protocol(url)
        update_storage_options(options, kwargs)
        fs = cls(**options)
        urlpath = fs._strip_protocol(url)
    return fs, urlpath

Would you like to make this into a PR, with a test for the ssh case?
On February 16, 2021 2:58:25 AM EST, juliospain notifications@github.com wrote:

Copying the relevant part from get_fs_token_paths seems to work...
def url_to_fs(url, **kwargs):
"""Turn fully-qualified and potentially chained URL into filesystem
instance"""
   chain = _un_chain(url, kwargs)
   if len(chain) > 1:
       kwargs = chain[0][2]
       inkwargs = kwargs
       for i, ch in enumerate(chain):
           urls, protocol, kw = ch
           if i == 0:
               continue
           inkwargs["target_protocol"] = protocol
           inkwargs["target_options"] = kw.copy()
           inkwargs["fo"] = urls
           inkwargs = inkwargs["target_options"]
       protocol = chain[0][1]
       urlpath = chain[-1][1] + "://" + split_protocol(urls)[1]
       fs = filesystem(protocol, **kwargs)
   else:
       protocol, urlpath = split_protocol(url)
       cls = get_filesystem_class(protocol)

       options = cls._get_kwargs_from_urls(url)
       urlpath = cls._strip_protocol(url)
       update_storage_options(options, kwargs)
       fs = cls(**options)
       urlpath = fs._strip_protocol(url)
   return fs, urlpath

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/intake/filesystem_spec/issues/539#issuecomment-779656960

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

You mean you used the correct syntax I suggested, but got the same issue you posted?

Exactly. I have delimited the error to _un_chain:
In [5]: fsspec.core._un_chain('libarchive://file1.txt::simplecache::ssh://host/home/user/test.7z', {})
Out[5]:
[('libarchive://file1.txt', 'libarchive', {}),
 ('simplecache://host/home/user/test.7z', 'simplecache', {}),
 ('ssh://host/home/user/test.7z', 'ssh', {'host': 'host'})]

In [6]: fsspec.core._un_chain('simplecache::ssh://host/home/user/test.7z', {})
Out[6]:
[('simplecache://', 'simplecache', {}),
 ('ssh://host/home/user/test.7z', 'ssh', {'host': 'host'})]

Notice how the simplecache path is different in both calls, having in the first one the path including the host which seemed to cause the error.
This part here seems wrong:
        if (
            protocol in {"blockcache", "filecache", "simplecache"}
            and "target_protocol" not in kw
        ):
            bit = previous_bit.replace(previous_protocol, protocol, 1)

It is only replacing the protocol from the ssh path, but it should probably split the path (such that the host gets stripped) and attach the cache protocol name.

This should be made clear in the docs

Ok. I will create a PR. I actually found a way to make it work with any file-like object as long as seekable (by the way, the same restriction applies to the zipfile system in read mode).

And this modification seems to work for me:
    out = []
    previous_path = None
    for bit in reversed(bits):
        protocol = split_protocol(bit)[0] or "file"
        cls = get_filesystem_class(protocol)
        extra_kwargs = cls._get_kwargs_from_urls(bit)
        kws = kwargs.get(split_protocol(bit)[0] or "file", {})
        kw = dict(**extra_kwargs, **kws)
        if (
            protocol in {"blockcache", "filecache", "simplecache"}
            and "target_protocol" not in kw
        ):
            bit = "protocol://" + previous_path
        out.append((bit, protocol, kw))
        previous_path = cls._strip_protocol(bit)
    out = list(reversed(out))
    # We should only do the url rewrite if the cache is in the middle of the chain
    if out[0][1] in {"blockcache", "filecache", "simplecache"}:
        out[0] = (f"{out[0][1]}://", out[0][1], out[0][2])
    return out

But again, I am no expert on this library, so please take a look and comment.

I would appreciate if you were to make that a PR, and create a set of tests. The test cases are really the best way to see if things are working correctly, and your case is complicated enough to tax the logic thoroughly.

Yes, I will. I have identified in the tests a simple "ftp" server which can be used for this check.

Martin, two questions:

Is the documentation correct regarding chaining?

I always found confusing that the chaining is that from right to left, from the docs:
simplecache::zip://*.csv::gcs://bucket/afile.zip
I.e. first open the bucket, then open the file, then cache the files. The more logical for me woud have been gcs://bucket/afile.zip::zip://*.csv::simplecache (operations performed left to right).
I found some code in url_to_fs and get_fs_token_paths which is certainly confusing (dead code constructing a inkwargs that later is not used), and I was wondering if the order is as well correct (the code seems to do it reversed).

Additionally, is the example above really working?

In get_fs_token_paths I see "expansion" of urls if the url is a string, but this is missing in the "chained" case or in case of list of urls. In those case I don't see expansion.
PS:
I would as well make clear in the docs that for example this is not working:
simplecache::zip://*.csv::gcs://bucket/*.zip
Since each zip file is a distinct filesystem (and at some point in the code it is checked that the filesystem is the same for all the final open files).

authors: juliospain martindurant


text:
Error when running an app using node command

Hello guys, i'm having  an error when i'm running my application with node command
root@edison:~# node intruderAlert.js
module.js:549
    throw err;
    ^

Error: Cannot find module 'mraa'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/root/intruderAlert.js:2:12)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)

my nodejs version is  8.11.3
Could anyone help me to resolve this problem  ? . I was thinking it because my nodejs version is > v6 so it cause the error when running the app

Hi @vijvcic, you might have to compile mraa from source with a custom version of swig for node 8 support. Please refer to the documentation here and let us know if you have further questions.

authors: Propanu vijvcic

repo: intel-iot-devkit/mraa


text:
gsoc: project: Comparison demo

Project Description
This idea came from this web page: https://www.alaska.org/how-big-is-alaska/oregon
The page shows users comparisons of several characteristics between Alaska and other States within the United States of America.
This is an excerpt reproduced from the above mentioned website.

Population Density
Oregon has 37 times more people per square mile.
If Oregon's population density were the same as Alaska’s, only 97,246 people would live in Oregon rather than 3,559,596 (based on 2003 data).
High Point
Alaska’s high point, Mt. Denali (20,320 feet), rises 1.7 miles above Oregon’s high point, Mount Hood, at 11,239 feet.
Not only is Mt. Denali the highest mountain in North America, but Alaska has 15 other peaks higher than any in the continental U.S.

The goal here is to build a dataflow that will allow users to compare any two arbitrary things.
Get the two things to compare.
Skills

Python
HTTP Requests

Difficulty
Beginner/Intermediate
Related Readings

https://intel.github.io/dffml/master/contributing/gsoc/2021/index.html

Getting Started

Read the contributing guidelines

https://intel.github.io/dffml/master/contributing/index.html

Go through the quickstart

https://intel.github.io/dffml/master/quickstart/model.html

Go through the data flow related docs and tutorials

https://intel.github.io/dffml/master/tutorials/dataflows/index.html
https://intel.github.io/dffml/master/examples/integration.html
https://intel.github.io/dffml/master/examples/shouldi.html
https://intel.github.io/dffml/master/examples/dataflows.html
https://intel.github.io/dffml/master/examples/mnist.html
https://intel.github.io/dffml/master/examples/flower17/flower17.html
https://intel.github.io/dffml/master/examples/webhook/index.html

Read about what data flows are and how they work

https://intel.github.io/dffml/master/concepts/index.html#dataflows
https://intel.github.io/dffml/master/concepts/dataflow.html

Come up with a basic example where the user will see inputs moving through the
network.

Make it simple and include a few operations.
Get the DataFlow running.

Look at the code in dffml/df/memory.py and understand how it relates to the
docs covering DataFlows conceptually.
Plan out what all needs to change within dffml/df/memory.py and the other
code and examples that would change as a result.

Potential Mentors

John Andersen
Saksham Arora

Tracking and Discussion
This project is related to the following issues. Please discuss and ask
questions in the issue comments. Please also ping mentors on
Gitter when you post on the following
issues so that they are sure to see that you've commented.

https://github.com/intel/dffml/issues/919

Misc
Demo idea, make a page like this https://www.alaska.org/how-big-is-alaska/oregon set things to compare and have dataflow do lookups maybe using nlp.
The demo should be based on dataflows so that it can be easily extended to other domains (other than states)

I ready to work on this task but can you guide me like from where can I start?

repo: intel/dffml


text:
deviceplugin: don't call method on a nil value.

If grpc.Dial() call fails, a nil connection object is returned. Don't defer a conn.Close() call before checking the error value.

Codecov Report

Merging #92 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #92   +/-   ##
=======================================
  Coverage   76.22%   76.22%
=======================================
  Files          10       10
  Lines        1127     1127
=======================================
  Hits          859      859
  Misses        250      250
  Partials       18       18

Impacted Files
Coverage Δ

internal/deviceplugin/server.go
87.23% <100%> (ø)
:arrow_up:

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 a8b11df...d2e829b. Read the comment docs.

authors: codecov-io ipuustin


text:
add pad_to_buckets in evaluation for hpu performance

Type of Change
lm_eval evaluation enhancement
Description
buckets = [64, 128, 256, 512, 1024, 2048, 4096, 8192]
This change will pad the input length to the nearest upper bound in buckets, which will avoid creating many graphs for different lengths to leverage the HPU accelerator.

[x] pad_to_buckets is a new argument for LMEvalParser
[x] auto device is enabled if pad_to_buckets is not set.
[x] add hpu evaluation support in example.
[x] install evaluation when install neural_compressor_pt.

Expected Behavior & Potential Risk
lm_eval example test gives the same result as before.

https://inteltf-jenk.sh.intel.com/job/INC_LLM_accuracy/137/artifact/report.html

repo: intel/neural-compressor


text:
e2e sanity: lock unified driver onto host-1

This is necessary because we need to know on which host we have to
create staging directories before calling the driver.

It seems to have the desired effect (driver runs on host-1), but I still got one sanity test failure:
KUBECONFIG=`pwd`/_work/clear-kvm-kube.config REPO_ROOT=`pwd` go test -timeout 0 -v ./test/e2e -args -ginkgo.focus=sanity.Node.Service.*should.work
...
• Failure [27.351 seconds]
sanity
/nvme/gopath/src/github.com/intel/pmem-csi/test/e2e/storage/sanity.go:39
  Node Service
  /nvme/gopath/src/github.com/intel/pmem-csi/vendor/github.com/kubernetes-csi/csi-test/pkg/sanity/tests.go:44
    should work [It]
    /nvme/gopath/src/github.com/intel/pmem-csi/vendor/github.com/kubernetes-csi/csi-test/pkg/sanity/node.go:364

    Expected error:
        <*status.statusError | 0xc000b34190>: {
            Code: 3,
            Message: "mount filesystem failedexit status 32",
            Details: nil,
            XXX_NoUnkeyedLiteral: {},
            XXX_unrecognized: nil,
            XXX_sizecache: 0,
        }
        rpc error: code = InvalidArgument desc = mount filesystem failedexit status 32
    not to have occurred

    /nvme/gopath/src/github.com/intel/pmem-csi/vendor/github.com/kubernetes-csi/csi-test/pkg/sanity/node.go:447

with this change, error is same. I think the fix does not work because the actually serving running controller pod was started before e2e code runs (on node-2), and that remains running and serving through the tests. There is another controller pod deployed by e2e test (where fix of current PR applies), but that pod exits approx. 30s after test start
We seem to have bigger overall confusion about who starts controller and how long it runs,

[commenting on merged PR]
asking just in case, @pohly when you renamed some pods to have "unified" in name,
you did not rename that one (test/e2e/storage/sanity.go, line 97)
		// Wait for pod before proceeding. StatefulSet gives
		// us a well-known name that we can wait for.
		f.WaitForPodRunning("pmem-csi-controller-0")

is this intentional?
I understand we create a pod there in BeforeEach section, but why we always wait for
that single pod that runs as pre-started deployment?
Would it make more sense to wait for pmem-csi-unified-0 ?
But if yes, what about namespace as it runs in dedicated pmem-XXXX/ namespace.
I tried a test run with rename pod name ( to pmem-csi-unified-0).
Success rate and testing time remains same, but output is somewhat (6%) shorter, so there was some effect. I will try to make sense from the diff to see what was it...
at least error was mentioned 1166 times in original output and 996 times in changed cases,
so statistically there was improvement. More deeper analysis will follow

I haven't looked at the context, but probably that name should indeed have been renamed.

The wait is there to ensure predictable runtimes for the following tests. Here we know that starting up a new pod can take a long time, so f.WaitForPodRunning can use a long timeout. Then the tests themselves can have shorter timeouts to fail faster when something else is wrong.

closer look to output confirms, the diff in msgs containing word error, is caused by different wait pattern.
Original version: wait returns immediately (as pre-created pod runs already), followed by few extra connection refused". Reconnecting... messages per case, totaling in about 100 more such messages per test cycle. So it seems we indeed should replace the name there (I will prepare a PR).
But its also notable that total time for test cycle remained same.

authors: okartau pohly

repo: intel/pmem-CSI


text:
Put the DOM event in the Event argument passed by On* functions

To allow for example:
A [Attr.HRef "#"; Text "Do something"]
|>! OnClick (fun _ ev ->
    doSomething()
    ev.Event.PreventDefault() // Don't go to '#'
)

Right now the only way to do this is to use AddEventHandler or JQuery.On inside OnAfterRender, instead of OnClick.

Bitbucket: https://bitbucket.org/intellifactory/websharper/issue/174
Originally reported by: Loic Denuziere
Originally created at: 2013-10-17T11:33:44.338

This is a simple change for keyboard and mouse events, but it is a breaking change for other events because we currently don't pass anything, so the callback type would change from 'T -> unit to 'T -> SomeEventType -> unit.

authors: Tarmil intellifactory-bb

repo: intellifactory/websharper


text:
Type annotations

Further tasks for having full type annotations in TypeScript:

[ ] 1) Convert WebSharper's runtime.js to TypeScript
[x] 2) Add types to translations of module let values
[x] 3) Create separate TS interfaces for F# union cases. Full type of the union type MyUnion = X of int | Y of string would be type MyUnion = MyUnion.Class & (MyUnion.X | MyUnion.Y) where MyUnion.X is defined with { $:0; $1:number } (form of unions in WS runtime)
[x] 4) Whenever a string/array is converted to an IEnumerable, wrap it in a StringEnumerator/ArrayEnumerator immediately, instead of handling translation of GetEnumerator specially
[ ] 5) local variables should not be collected on top of function scope any more, but defined with let/const (#816) so that TS type inference can resolve their types.
[ ] 6) Types with Prototype(false) should translate to a TS interface, declaring the types of the properties (values are plain objects).
[ ] 7) Some lambdas need type annotations. For example the lambda (x: number, y: string) => [x, y] has its return type resolved to (string | number)[]. It has to be annotated like (x: number, y: string):[number,string] => [x, y] because obviously (string | number)[] is not compatible with [number,string].
[x] 8) Allow the Type attribute on generic parameters to specify that only types are allowed that translate or is compatible with a specific TS type. For example, on Seq.average proxy, the result is always a number but it is generic in .NET. If the proxy would define it like let Average<[<Type "number">] 'T> (s: seq<'T>) : 'T, then WebSharper would know that in TS, it can erase the T type parameter and have it translate to number, also throw a compiler error when it is used with a type that is not mapped to number.
[ ] 9) Transform checks against interfaces to a function that returns a user-defined type guard.
[ ] 10) Print type aliases for delegates. Have resolved names for them, translate to it in signatures.
[ ] 11) (optional) Print consts for enum cases, have a type alias for them (just aliasing number)
[ ] 12) Map types of 2-dimensional arrays

On 4): To not have a messy type for IEnumerables, it is easier to have them tranlate directly to the interface type. This needs a runtime change in the handling of enumerating on strings and arrays: instead of a runtime type check at the point of the GetEnumerator call, wrap strings and arrays where they are converted to a sequence into StringEnumerator/ArrayEnumerator helpers that implement GetEnumerator.

Needs some more casts for accessing this within members of the union class as a strongly typed union (in TS, a union of cases). Type checks has to be translated against the class type, not the combined union type.

Was solved by extending built-in Array and String to have GetEnumerable. Need to set the prototypes in WebSharper.Main.ts.

We can't rely on type inference to resolve the type of every var because WebSharper might need to print uninitialized variables. The type of every local variable will be persisted, so that var/let declarations without assignment can have the type annotation.

Type annotations will not be stored for lambdas but tuple value creation because they are the underlying cause for this error. A tuple will be always translated with type annotations, like <string, number>["hello", 3].


text:
Html sketchapp support

This adds initial html-sketchapp-cli support for color, colorpalette and type.  I think adding a data-sketch-symbol={image title} if an image has a title could be useful too.

Cool, thanks! I assume you've tested this with html-sketchapp-cli?

authors: Kilian herrstucki

repo: interactivethings/catalog


text:
#resource- broken in links

I have a schema with some depth (like a user with an attribute thumbnail being a $ref to an image schema), an article having an author attribute iself being a user...
The generated markdown for the attribute table looks like:
 **[author:thumbnail:URL](#resource-date)** | *uri* | URL to an image file ...

The problem is the #resource-date is clearly false here, and in all my Attributes table they are "randomized".
No so randomized, in fact their quantities are right (if I have 6 attributes for the thumbnail (an image) of a user, I have 6 #resource-image, but in the wrong place.
Also (probably the same bug) some attributes does NOT have links on some cases they should have, and some which should not have (local strings) may have links.

The links are relatively new, so it sounds as though some edge cases just need more attention. The misdirection seems clear enough, could you provide a bit more detail on places where you expect links (or not) and aren't getting what you expect?

Actually, could you provide a specific example around the mis-linking as well? Pretty sure I've narrowed it down (https://github.com/interagent/prmd/blob/master/lib/prmd/templates/schemata.md.erb#L28), but having something specific would help be more certain.

authors: JulienPalard geemus

repo: interagent/prmd


text:
Dynamically loading a remote Cell script from an existing Cell app and injecting into the existing Cell app.

I was trying to implement an app that consists of just an input field initially, which when submitted will dynamically load a remote script and do something on onload event, using Cell.
More specifically, I was trying to find a way to load a remote cell app from an existing cell app, and inject it into the existing cell app.
But I ran into a problem. When loading a remote script dynamically, it is not possible to know what variables have loaded as a result of that script. The new manual instantiation feature introduced in https://github.com/intercellular/cell/issues/125 doesn't help because we have no knowledge about the newly introduced variables in the root context.
Anyway here's the half-finished code. The only problematic part is the Fill in the blank here part inside onload(). Once that's figured out, everything should just work.
{
  $cell: true,
  _load: function(url) {
    this.querySelector("#script_slot").$components.push({
      $type: "script",
      src: url,
      onload: function() {
        /*
         * Fill in the blank here
         * Need to turn the loaded gene objects into cells
         * but we do not know what variables have loaded.
         */
      }
  	});
  },
  $components: [
    {
      id: "script_slot",
      $components: []
    },
    {
      $type: "input",
      placeholder: "Enter a javascript url and press enter",
      onkeyup: function(e) {
        // when the enter key is pressed, find the nearest ancestor
        // that contains _load() and call that function.
        if(e.keyCode === 13) this._load(this.value);
      }
    }
  ]
}

Trying to figure out a nice and clean way to tackle this.
it could be done through a modification of the API, or maybe there's a way to do this without modifying the API. Maybe there's a clean way.

do i understand this correctly that you are you looking for a way to determine which global variables have been added after loading a script?
if so, could some of the answers in this thread help or do the trick?
https://stackoverflow.com/questions/17276206/list-all-js-global-variables-used-by-site-not-all-defined

Thanks for sharing!
Yup, in fact this is how Cell implements its automatic instantiation mechanism https://github.com/intercellular/cell/blob/develop/cell.js#L501
But the challenge I'm trying to point out here is that currently there's no way to detect whether a variable has already been used or not.
In the example above, we need to detect only the variables that have been dynamically loaded as a result of the script load. The Object.keys(window) approach will return all the variables, not just the newly added ones. Hope I'm making sense, it's a niche scenario but I think it can be powerful if we can figure this out.

repo: intercellular/cell


text:
Create Login and New Account/Register functionality

#Acceptance Criteria

[x] #16
[x] #6
[x] #15
[x] #17
[x] #18
[x] #134
[x] #136

#Design

Main subtasks are implemented for this Epic story.
Other bugfixes will probably be standalone tickets.

repo: interledger/testnet


text:
Log oulinks for all users of Browser.

This makes is such that anyone using the Browser class (e.g. Umbra) will see the outlinks in their logs.

What's the reason for this change?

To make it so that users of the Browser class can few outlinks discovered. In this case, Umbra will log the outlinks as well.

I don't think we want all this logged in brozzler-worker. Gonna decline.

I'd rather not do that either. I thought it would be useful to print the outlinks that way for brozzle-page, but I wouldn't normally use logging for this kind of output (many lines without the timestamp prefix etc)

authors: BitBaron nlevitt

repo: internetarchive/brozzler


text:
Site map env var

create an env var for the sitemap
make a local and prod command for the cli
split the docker compose files

@webb-ben history seems messy but going to squash this so it will be fine in the git history. feel free to review at your convenience

repo: internetofwater/scheduler


text:
OpIntentValidator raises exception before recording query

report.json is not attached because
s2_redacted.html attached instead.  Codebase version used for test was 51ef12212b91387c95e3293d54d0f60bfb087cc8.
s2_redacted.html.zip
Test check
None; scenario effectively crashes when it is not at a check.
Difference from expected behavior
uss_qualifier should never have exceptions to report to the user under nominal circumstances.  If exceptions are raised under expected conditions (e.g., raising QueryError), they should be caught and applied to a check or normal flow control logic.  In this case, failure to do so made it so the query critical to identifying and resolving the problem (the call to get op intent details from the USS under test) was not recoded in the report.
Additional context
This also affects OpIntentValidator, so we probably want to finish merging #428 before addressing this issue.

Another example
s2_redacted.html.zip

When all the PRs that mentioned this issue are merged (at the time of writing this #501, 502 and #503 are still open) I think this issue can be closed as those changes ensure that queries are recorded when some functions of DSSInstance are used.
Now the same issue is very probably present in other parts of the codebase as the error handling for querying USSes/DSS is quite inconsistent.
I believe the approach I used in DSSInstance enables flexibility in the error handling while being able to ensure queries are recorder, at the price of a slightly heavier call site. It could probably be extended to other calls but I'm not sure of what kind of priorities this would have now.

All mentioned PRs are merged.  We'll keep in mind error resilience as we develop and improve, but I believe this specific issue can be closed.

authors: BenjaminPelletier mickmis

repo: interuss/monitoring


text:
🛑 Zeeuws Museum is down

In 216934c, Zeeuws Museum (https://www.zeeuwsmuseum.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zeeuws Museum is back up in b9df455.

repo: intk/intk-upptime


text:
30 mins slot issue

What's the current behavior?
In my event wrapper component
const hourStart = moment(event.start).hour(),
const hourStop = moment(event.end).hour(),
const gridRowStart = hourStart+1,
style:{{gridRow: ${gridRowStart} / span ${hourStop - hourStart}}}
this is how iam dealing with hour slot case but what if slot is  30mins or  10:30am to 11:30am case how to deal that case

Try converting everything to minutes
example: const hourStart = moment(event.start).hour()*60 + moment(event.start).minute()
I don't if this will work but give it a try

authors: eightshone kumargugloth

repo: intljusticemission/react-big-calendar


text:
Why don't I have the '+n more' btn?

As you can see I have some events for the day. And I see only the part of the second event. I want to see '+1 more' button with popup. Could you help me, please?

Try playing with the height of the calendar, see if it shows ?

@RaedsLab Yeah, if I change the height it works. But, actually, I would like to have '+1 more' btn, because in this case height will be too big and it will be inconvenient.

Perhaps this button is shown only when we have more then 2 events per day (3 and more).

@jquense  Maybe. But I think that it would be better if I can set in the property, for example, something like "show more button if I have more then 1 event per day". And at the same time we don't need to add any "dummy" events or do some difficult calculations. By default this property might be equal 3 for example. And in this case, if, for example, my events too big I can manipulate the height of the calendar and this property for getting pretty view. Of course maybe I'm wrong about something.

It can't work  like that because of how the styles are set up. the calendar takes as much space as you tell it and then fits the amount of events that it can in the space. If you want to achieve that effect you can make the calendar a size where the amount of events you want fit in it. The problem here tho is there is a bug or edge case. It's a bit tough to troubleshoot it tho with an example in codesandbox or similar

I'm looking for a reproduction of this bug I can use to debug the issue yeah!

I am closing this due to inactivity from the original poster. If this issue needs more attention feel free to reopen.

authors: RaedsLab arecvlohe dkorolev1 jquense


text:
Error authenticating /auth/failure?message=invalid_response

I'm getting an error trying to sign on with Facebook/Twitter that just started yesterday out of the blue. I can't seem to find anything that I would have caused it (checked the gemfile for updated gems there aren't any; checked all my authorization methods, haven't changed).
I've tried to debug it but I can't figure out where in the process this error would be coming from. Looking in the omniauth code it looks like the invalid_response comes from a json error in the response from the authenticator.
Anyone else seeing this?!

I have the same problem as @robotmay
Requiring MultiJSON (pure_json 1.6.1) hasn't helped at all, I'm running 1.9.2 on Rails 3 (on Heroku).
I still get the invalid_response failure when omniauth is trying to authenticate to twitter.
Any luck on this? (This is my first experience with rails).

I have the same problem: http://localhost:3000/auth/failure?message=invalid_response
The page says:
Routing Error
No route matches [GET] "/auth/failure"

The JSON pure fix does not help.
Running 1.9.2 already / Rails 3.1.
rajibahmed's solution does not work
Already using omniauth.auth (Railscast 241)

Any progress on this? Like a andycasey, this is my first experience with Rails.

So apropos my previous post, it seems twitter have changed their api calls. Try this:
def self.create_with_omniauth(auth)
	create! do |user|
		user.provider = auth["provider"]
		user.uid = auth["uid"]
		user.name = auth["info"]["name"]
	end

I am also seeing this issue
Running:
Rails 3.1.0
omniauth 1.0.1
omniauth-oauth 1.0.0
omniauth-oauth2 1.0.0
omniauth-twitter 0.0.7
on ruby-1.9.2-p180
if I log request.env["omniauth.auth"], I can see my response from Twitter, but I'm still getting a 500 'invalid_response' error.
I tried explicitly adding a JSON parser to my gem file to no avail.
Any other troubleshooting ideas?

Hi @technicolorenvy,
I revisited this problem last night. I originally had the problem on Heroku using a cedar stack, but now I am running on a bamboo-mri-1.9.2 stack. To fix the 'invalid_response' routing problem I added
:omniauth_callbacks => 'authentications'

to my devise_for routing, such that my config/routes.rb file contains this line:
devise_for :users, :controllers => { :omniauth_callbacks => 'authentications', :registrations => 'registrations' }

I did have some other minor issues along the way, so if you still encounter problems let me know - I managed to get it all working in the early hours of the morning.

Hey @andycasey,
I'm running w/out devise as I don't really need folk to login, per se. I more need them to grant me access to their twitter user's location, username, etc, etc.
i'm less concerned with the routing issue (I'll fix that when the time comes) and more perplexed with the fact that I'm getting the auth failure to begin with. Research seems to point towards this issue stemming from a malformed JSON response w/in omniauth (or one the related omniauth gems).
any other useful obvious bits that I may be missing?

Ok, found my issue
i didn't realize that omniauth was throwing a invalid_response error if I had an error in my controller. This seems heavy-handed, but now I know.

I am also facing this issue with my app.
Using Rails 3.1.1 ,
ruby 1.9.2p290
Using oa-more (0.2.6)
Using oauth (0.4.5)
Using oauth2 (0.4.1)
Using oa-oauth (0.2.6)
Using twitter (1.6.0)
When I sign it using twitter, then the app redirects to give Error authenticating /auth/failure?message=invalid_response
but when I go back to homepage, it shows signed it. So, even when the credentials are valid, it is redirecting in a wrong way.
PS: I don't have any route set for /auth/failure at present.

authors: andycasey erskingardner magicmike neerajnsit technicolorenvy

repo: intridea/omniauth


text:
Issues Mac m1 zsh shell resolved

Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 1342, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 1424, in connect
self.sock = self._context.wrap_socket(self.sock,
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/ssl.py", line 500, in wrap_socket
return self.sslsocket_class._create(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/ssl.py", line 1040, in _create
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/ssl.py", line 1309, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/bin/kwlfilecheck", line 8, in
sys.exit(get_file_list())
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/click/core.py", line 1128, in call
return self.main(*args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/kwltracking.py", line 7, in get_file_list
df = pd.read_html('http://introcompsys.github.io/spring2022/activities/kwl.html')[0]
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/util/_decorators.py", line 311, in wrapper
return func(*args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/io/html.py", line 1113, in read_html
return _parse(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/io/html.py", line 919, in _parse
tables = p.parse_tables()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/io/html.py", line 239, in parse_tables
tables = self._parse_tables(self._build_doc(), self.match, self.attrs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/io/html.py", line 758, in _build_doc
raise e
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/io/html.py", line 739, in _build_doc
with urlopen(self.io) as f:
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pandas/io/common.py", line 239, in urlopen
return urllib.request.urlopen(*args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 523, in open
response = meth(req, response)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 632, in http_response
response = self.parent.error(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 555, in error
result = self._call_chain(*args)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 747, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 517, in open
response = self._open(req, data)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 534, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 1385, in https_open
return self.do_open(http.client.HTTPSConnection, req,
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 1345, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123)>
tylermakhoul@126 courseutils %

open /Applications/Python\ 3.7 or whatever version you have /Install\ Certificates.command

repo: introcompsys/courseutils