created the game elephant ant man

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #4015

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[
[ ] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @tanishkaa08 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

I can't figure out the conflict of the branch.

Thank you  @tanishkaa08 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


sudo chef-server-ctl reconfigure

Hi,
Can someone help me solve this issue?

Recipe: private-chef::postgresql

user[opscode-pgsql] action create
================================================================================
Error executing action create on resource 'user[opscode-pgsql]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0], but received '8'
---- Begin output of ["usermod", "-d", "/var/opt/opscode/postgresql", "opscode-pgsql"] ----
STDOUT:
STDERR: usermod: user opscode-pgsql is currently logged in
---- End output of ["usermod", "-d", "/var/opt/opscode/postgresql", "opscode-pgsql"] ----
Ran ["usermod", "-d", "/var/opt/opscode/postgresql", "opscode-pgsql"] returned 8
Resource Declaration:
In /opt/opscode/embedded/cookbooks/private-chef/recipes/postgresql.rb
27: user node['private_chef']['postgresql']['username'] do
28:   system true
29:   shell node['private_chef']['postgresql']['shell']
30:   home node['private_chef']['postgresql']['home']
31: end
32:
Compiled Resource:
Declared in /opt/opscode/embedded/cookbooks/private-chef/recipes/postgresql.rb:27:in `from_file'
user("opscode-pgsql") do
action :create
supports {:manage_home=>false, :non_unique=>false}
retries 0
retry_delay 2
guard_interpreter :default
username "opscode-pgsql"
home "/var/opt/opscode/postgresql"
shell "/bin/sh"
system true
cookbook_name :"private-chef"
recipe_name "postgresql"
end
Running handlers:
[2015-02-23T18:10:13+00:00] ERROR: Running exception handlers
Running handlers complete
[2015-02-23T18:10:13+00:00] ERROR: Exception handlers complete
[2015-02-23T18:10:13+00:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 5 resources updated in<PHONE_NUMBER>84 seconds
[2015-02-23T18:10:13+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: user[opscode-pgsql] (private-chef::postgresql line 27) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '8'
---- Begin output of ["usermod", "-d", "/var/opt/opscode/postgresql", "opscode-pgsql"] ----
STDOUT:
STDERR: usermod: user opscode-pgsql is currently logged in
---- End output of ["usermod", "-d", "/var/opt/opscode/postgresql", "opscode-pgsql"] ----
Ran ["usermod", "-d", "/var/opt/opscode/postgresql", "opscode-pgsql"] returned 8

@jigishmehta86 You should open this issue agains the https://github.com/chef/chef-server repo, as this is a chef-server issue, not a chef client issue.
I will say that I've never seen this before, but you've got something going on with the opscode-pgsql user, as it's telling you in the error message:
STDERR: usermod: user opscode-pgsql is currently logged in
Perhaps remove that user and run reconfigure again to see if that fixes the issue. A reconfigure should put the user back. This is the user setup by the chef server for it to access the db.
I'm going to close this issue, but if the above doesn't fix it, please reopen agains the chef-server repo. Thanks.

cool. thanks
i can see the Chef web ui login portal. But when i use admin/p@ssw0rd1 credentials, it shows me a 'Some went wrong' page.
Can you suggest what can be wrong there ?

@jigishmehta86 You must be using open source chef 11 then, is that correct (based on the webui you're referencing)? I'd recommend going with Chef Server 12 - it's the latest and is fully open source. Although it does drop the webui that was used in open source Chef server 11 in favor of Chef Manage, our proprietary webui, which is free for use up to 25 nodes.
That said, to solve this issue you'll want to run chef-server-ctl tail to see the log output and see what error is being thrown. Other than that I can't offer any more specific guidance.

That's correct. I am using the open source chef 11. I will give the above suggestions a shot and see if it resolves my issues.
thanks @mmzyk


Add Python 3.8 to Travis

The https://travis-ci.org/boto/s3transfer/jobs/653864672 fails with
======================================================================

FAIL: test_download_futures_fail_triggers_shutdown (tests.unit.test_s3transfer.TestMultipartDownloader)

----------------------------------------------------------------------

Traceback (most recent call last):

  File "/home/travis/build/boto/s3transfer/tests/unit/test_s3transfer.py", line 484, in test_download_futures_fail_triggers_shutdown

    downloader.download_file('bucket', 'key', 'filename',

AssertionError: "fake download parts error" does not match "FINISHED: <Future at 0x7fd9b8c8b2e0 state=finished returned NoneType>"

-------------------- >> begin captured logging << --------------------

s3transfer: DEBUG: Making get_object call.

s3transfer: DEBUG: EXITING _download_range for part: 0

--------------------- >> end captured logging << ---------------------

Possibly pointing out a race condition at https://github.com/boto/s3transfer/blob/develop/s3transfer/init.py#L490 ?

https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.wait


Modify all Timespans at once

We need a possibility to control all timespans at once in the header.
The options should be:

a custom timespan
today, yesterday
last 7 days
last 30 days
this month
last month

When the control is changed, every view should be updated.

Issue solved with #20


why automatically jumps to some breakpoint far away from X

In debug, when I add a comment on line x, and there is a breakpoint above and below line x, after saving, the program automatically jumps to some breakpoint far away from X. I would like to know how to solve it, thank you very much

Hi @sajsxj
Could you provide more details? I can't reproduce it.
Which version of the plugin are you using?
Does it always happen or only sometimes?

Also is the breakpoint it jumps to in the same function or a different one?

@dkrystki Ok, let me redescribe the problem I encountered, and the rest of the description is in the debug case.
I have attached some pictures below. When the program reaches the last breakpoint, modify the comment two. After the hot load file is executed, the program will automatically jump to the first breakpoint
So how do you get it to jump to the point closest to comment two
Also, I would like to know if there is an option to set up a hot reload file manually or automatically
thanks！！！

Sorry, I forgot to tell you the version, reloadium1.1.1
emmm, maybe it is my improper use. I just started using it yesterday, and I hope you can give me some help

The jump also goes to the current function

Oh I see. It's not really a bug.
When debugging a function Reloadium restarts the whole body of the function on a change.
That is why your first breakpoint is hit.
Back in the days Reloadium would disable breakpoints before the current one to prevent that.
I removed that behavior since it can be beneficial to step through a function once the code is changed.

ok, I see! Thank you very very very much！！！！


[WIP] DMDc

Needs tests and maybe callback integration

Did you pull that example from the paper? That's a good one to keep in mind as a positive proof that added knowledge can be required for equation discovery.

From the book of Kutz and Proctor. But it is also in the paper and on their homepage as a Matlab block I think.


Revert "Merge pull request #8095 from jean-edouard/waitforcrdelete"

What this PR does / why we need it:
This reverts commit d86f5fb8c1e6f5206f3a3d7d8fbd9880df1d99b7, reversing
changes made to 989ac541736c73da1569e6c786fcf4ae65148eb3.
We suspect that this introduced a flakiness on the operator lanes, we are trying to test if the revert fixes it on this PR.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
@jean-edouard FYI
Release note:

NONE

/test pull-kubevirt-e2e-k8s-1.24-operator
/test pull-kubevirt-e2e-k8s-1.23-operator
/test pull-kubevirt-e2e-k8s-1.23-operator-nonroot
/test pull-kubevirt-e2e-k8s-1.22-operator

Root cause is not the fix, but a private quay repository of a new kubevirt virt image.
/close


fix(Tooltip): Postpone tooltip rendering until the next repaint on mobile devices

There is also no significant difference between setTimeout(() => …, 0-3), requestIdleCallback, or requestAnimationFrame but the last one seems to work faster. We will rework the tooltip on mobile devices in the future but we do not have a concept for now.

The performance bottleneck causing this ticket to come about seems to be fixed.


Obsolete copyright info

https://github.com/env-logger-rs/env_logger/blob/52a3e69b38f69469b77502651992f91bdfebb48a/src/lib.rs#L1-L3
There is no COPYRIGHT file in this repo nor does the copyright URL still work. Should these lines be removed/changed?

"The Rust Project Developers" is also not a legal entity that can hold copyright. I'll remove this.

38643a3


Reintroduce & fix gamewindow refactor

Reintroduces the changes and fixes the windows bug from #1420 .
This should probably still be tested on all other platforms.
Edit: Closes #1102 (again).

Tested on macOS and Windows, looks ok to me. 👍


Loading failed for the module with source

Describe the bug
After installing a brand new vite app I get this error in console and the app doesn't load.
Loading failed for the module with source “http://localhost:3000/@modules/vue”.

Steps to reproduce
$ npx create-vite-app my-vite
$ cd my-vite
$ npm install
$ npm run dev

System Info

required vite version: 0.0.0 dev
required Operating System: Windows 7
required Node version: 12.10.0

There's a bug on windows when using 0.11.3
see #70
Altho the error is not the same, do you mind installing the previous version to check if the error is still there?
npm install<EMAIL_ADDRESS>


DELETE /conversation/{conversationId} does not delete the conversation

Expected Behaviour
I use the API to delete an existing conversation from Smarti.
The conversation still exists in the database and the GET /legacy/rocket.chat still returns the deleted conversation with a 200 Code.
On the other hand GET /conversation/{conversationId} can't find the conversation anymore and returns a 400 Code.
Actual Behaviour
DELETE /conversation/{conversationId} should delete the conversation from the database
Steps to Reproduce

POST /conversation
GET /legacy/rocket.chat returns the conversation for the specified channelId
GET /conversation/{conversationId} returns the conversation for the specified conversationId
DELETE /conversation/{conversationId} returns success for deletion 204
GET /conversation/{conversationId} returns 404 conversation not found
GET /legacy/rocket.chat still returns the conversation for the specified channelId
DELETE /conversation/{conversationId} returns 404 conversation not found

Environment
Smarti version 0.7.4-SNAPSHOT
CommitId: d4db0eae3492729ec075ac2999baf25cd8731215

See also: https://github.com/redlink-gmbh/smarti/issues/95

The DELETE operation does mark the conversation as deleted AND deletes all messages. The conversation and its metadata are preserved as those information are required for cloud-sync of the embedded Solr Servers managed by the different Smarti instances.
For clean up one could run a Mongo task that physically deletes all conversations that where marked as deleted for longer as a given time period (e.g. 1 day).
NOTES:

Even when using an external Solr those Information are critical to sync the Index after a down period (as one needs to know what conversations need to be deleted from the index).
When a clean up process is in place Solr Indexes that are out of sync for longer as the configured time period of the clean up process need to be deleted and fully rebuild.

#259 (#260) aim to fix that GET /legacy/rocket.chat returns conversations that are marked as deleted.

Hi @westei,
thanks for investigating on this issue and fixing the PR.
I like the idea using a configureable time period to run a clean up process for obsolete conversations.
I noticed that deleting conversations (and analysis) on MongoDB results in Solr responses that have a numfound e.g. 26, but the docs in the response is less or 0. So it would be nice to trigger the Solr synchronization manually (e.g. via API).
IMOH we should create a separate issue about "Smarti housekeeping".

noticed that deleting conversations (and analysis) on MongoDB results in Solr responses that have a numfound e.g. 26, but the docs in the response is less or 0. So it would be nice to trigger the Solr synchronization manually (e.g. via API).
This could be the case If the conversations in the Response are actually loaded from the MongoDB (based on the ID in the SolrIndex) and NOT reconstructured from the data in the SolrIndex. I will check if this is the case, because it could also explain why sometimes the numFound does not correspond with the number of actual results

IMOH we should create a separate issue about "Smarti housekeeping".
This is part of #222

noticed that deleting conversations (and analysis) on MongoDB results in Solr responses that have a numfound e.g. 26, but the docs in the response is less or 0. So it would be nice to trigger the Solr synchronization manually (e.g. via API).

This could be the case If the conversations in the Response are actually loaded from the MongoDB (based on the ID in the SolrIndex) and NOT reconstructured from the data in the SolrIndex. I will check if this is the case, because it could also explain why sometimes the numFound does not correspond with the number of actual results

The ConversationSearchService loads Conversations and Messages from the MongoDB. In case a Conversation present in the SolrIndex is missing in the MongoDB the following Log message is written on IINFO level
ConversationIndex out of Sync with ConversationRepository: Conversation[id:{id}] is present in the index but not in the Repository!
Solr Results for those conversations are removed. So the number of Results will therefore differ from the numResults reported by Solr

Delete all conversations from the MongoDB
Start a re-sync from Rocket.Chat (new conversations for the same channelId will be created)
Open Smarti Widget (4 numfound, 0 docs)

Log:
2018-06-13 18:29:14.085  INFO 16074 --- [io-8080-exec-10] i.r.s.q.c.ConversationSearchService      : ConversationIndex out of Sync with ConversationRepository: Conversation[id:5b2063407d48d5137ab0ab19] is present in the index but not in the Repository!
2018-06-13 18:29:14.085  INFO 16074 --- [nio-8080-exec-1] i.r.s.q.c.ConversationSearchService      : ConversationIndex out of Sync with ConversationRepository: Conversation[id:5b2063407d48d5137ab0ab13] is present in the index but not in the Repository!
2018-06-13 18:29:14.088  INFO 16074 --- [io-8080-exec-10] i.r.s.q.c.ConversationSearchService      : ConversationIndex out of Sync with ConversationRepository: Conversation[id:5b2063407d48d5137ab0ab17] is present in the index but not in the Repository!
2018-06-13 18:29:14.089  INFO 16074 --- [io-8080-exec-10] i.r.s.q.c.ConversationSearchService      : ConversationIndex out of Sync with ConversationRepository: Conversation[id:5b2063407d48d5137ab0ab13] is present in the index but not in the Repository!
2018-06-13 18:29:14.093  INFO 16074 --- [nio-8080-exec-7] i.r.s.q.c.ConversationSearchService      : ConversationIndex out of Sync with ConversationRepository: Conversation[id:5b2063407d48d5137ab0ab16] is present in the index but not in the Repository!

in what order?

Smari runs all the time.

We can configure Mongo to delete conversations that are maked as deleted automatically after a predefined period see https://docs.mongodb.com/manual/core/index-ttl/

will move this to v0.9.0 as Cloudsync might get away with the Solr Update and if this is the case this will be resolved as we could delete conversations instead of marking them as deleted


Convert async iterators to streams

An initial implementation of what I proposed in https://github.com/rustwasm/wasm-bindgen/issues/2399
It would be nice to have the ability to turn async iterators into Rust streams in the same way we can turn promises into futures. Instead of creating a separate crate for this utility I think it fits well in the scope of wasm-bindgen-futures.

Thanks for this! I'm a bit hesitant to do this at this  time though since it introduces futures-core as a public dependency. AFAIK Stream is intended at some point to make its way into the standard library, right? If so perhaps this could be gated behind an off-by-default Cargo feature?

Thanks for this! I'm a bit hesitant to do this at this  time though since it introduces futures-core as a public dependency. AFAIK Stream is intended at some point to make its way into the standard library, right? If so perhaps this could be gated behind an off-by-default Cargo feature?

Yeah it looks like https://github.com/rust-lang/rust/pull/79023 could land anytime which would also remove the need for the dev-dependency. I'll put this under a streams feature if that's ok?

Yeah it looks like https://github.com/rust-lang/rust/pull/79023 could land anytime which would also remove the need for the dev-dependency. I'll put this under a streams feature if that's ok?

@alexcrichton Added the feature under the stream flag even for the test because it seemed I would have to change the version of wasm-bindgen-test all over the place. Also mentioned the existence of feature in the Readme as experimental which can be made "stable" later when there is core::stream::Stream and perhaps also adding the feature of Stream to AsyncIterator(ReadableStream?) conversion.

@alexcrichton Added the feature under the stream flag even for the test because it seemed I would have to change the version of wasm-bindgen-test all over the place. Also mentioned the existence of feature in the Readme as experimental which can be made "stable" later when there is core::stream::Stream and perhaps also adding the feature of Stream to AsyncIterator(ReadableStream?) conversion.

Looks good, thanks! For a small amount of extra future-proofing, though, could this perhaps be named futures-core-03-stream?

Looks good, thanks! For a small amount of extra future-proofing, though, could this perhaps be named futures-core-03-stream?

Thanks!

Thanks!


Render images as a label for VictoryLine

Bugs and Questions
Checklist

[x ] This is a victory-native specific issue. (Issues that also appear in victory should be opened here)

[x ] I have read through the FAQ and Guides before asking a question

[ x] I am using the latest version of victory-native

[x ] I have checked to make sure that my versions of react-native and react-native-svg are compatible with this version of victory-native. Read about version requirements

[x ] I've searched open issues to make sure I'm not opening a duplicate issue

The Problem
I'm trying to render an Image as a label for VictoryLine with the labelComponent prop
Reproduction
<VictoryChart width={wpF("83%")} height={hpF("39%")} >
                                <VictoryLine
                                    data={[
                                        { x: "09:00", y: 19.86 },
                                        { x: "12:00", y: 22.15 },
                                        { x: "15:00", y: 20.29 },
                                        { x: "18:00", y: 16.19 },
                                        { x: "21:00", y: 12.45 },
                                      ]}
                                    animate={{
                                        duration: 2000,
                                        onLoad: { duration: 1000 }
                                    }}
                                    labels={({ datum }) => datum.y}
                                    labelComponent={ <Image source={require("../../assets/images/meteo/humedad.png")} /> }
                                />
                            </VictoryChart>

victory-native:  6.14.4
react-native: 0.62.0
react-native-svg: 6.14.4

I have the same problem for VictoryPolarAxis and I am very surprised that not more people seem to be asking on how to use icons and images as Labels for their charts.
It seems to be working with background images, but I cant get it to work with labels:
https://formidable.com/open-source/victory/docs/new

I have working example for VictoryPie, maybe you could use it too:
My custom label component:
const CustomLabel = (props: any) => (
  <View
    style={{
      position: 'absolute',
      left: props.x,
      top: props.y,
    }}>
    <Image resizeMode="contain" style={{width: 40, height: 40}} source={planeIcon} />
  </View>
);

My pie chart component:
<VictoryPie
  width={300}
  height={300}
  innerRadius={75}
  labelRadius={130}
  colorScale={['#284177', '#02B8D3', '#F57C00']}
  data={data}
  labelComponent={<CustomLabel />}
/>
``

I have working example for VictoryPie, maybe you could use it too:
My custom label component:
const CustomLabel = (props: any) => (
  <View
    style={{
      position: 'absolute',
      left: props.x,
      top: props.y,
    }}>
    <Image resizeMode="contain" style={{width: 40, height: 40}} source={planeIcon} />
  </View>
);

My pie chart component:
<VictoryPie
  width={300}
  height={300}
  innerRadius={75}
  labelRadius={130}
  colorScale={['#284177', '#02B8D3', '#F57C00']}
  data={data}
  labelComponent={<CustomLabel />}
/>

Hi, May I know the versions you are using? thanks

Finally solved this by passing svg image from 'rn-svg'

const CustomLabel = (props) => (
 <Image
 x={props.x-10}
 y={props.y-10}
 width="5%"
 height="5%"

 opacity="1"
 href={require('../images/ic_pp.png')}
 clipPath="url(#clip)"
/>
);

<VictoryLine
    style={{
      data: { stroke: "#c43a31" },
      parent: { border: "1px solid #ccc"}
    }}
    groupComponent={<G />}
    labels={({ datum }) => datum.y}
    labelComponent={<CustomLabel />}
    data={[
      { x: 1, y: 2 },
      { x: 2, y: 3 },
      { x: 3, y: 8 },
      { x: 4, y: 4 },
      { x: 5, y: 7 }
    ]}
  />
</VictoryChart>

For the non-react-native, I found using <image> for images and <foreignObject> for my custom Icon works:
Images:
<VictoryPie
  data={list}
  labelComponent={<ImageComponent/>}
/>

const ImageComponent = (props) => {
  const width = 16;
  const x = props.x - width/2;
  const y = props.y - width/2;
  return (
    <image
      x={x}
      y={y}
      width={width}
      height={width}
      href={`${my-url-to-my/image.png}`}
    ></image>
  );
};

Icons:
<VictoryPie
  data={list}
  labelComponent={<IconComponent/>}
/>

const IconComponent = (props) => {
  const width = 16;
  const x = props.x - width/2;
  const y = props.y - width/2;
  return (
    <foreignObject
      x={x}
      y={y}
      width={width}
      height={width}
    >
      <Icon
        icon='chart-bar'
      />
    </foreignObject>
  );
};

Hello did your code work? i am trying to make the same thing but on VictoryPolarAxis

I have the same problem for VictoryPolarAxis and I am very surprised that not more people seem to be asking on how to use icons and images as Labels for their charts.
It seems to be working with background images, but I cant get it to work with labels:
https://formidable.com/open-source/victory/docs/new

Hello, did you make it work with polar Axis?


Next.js + link-state + SSR

I receive an error when using apollo-link-state with Next.js/Apollo (modifying the "with Apollo" example in Next.js repository). I'm not sure it is an issue really: I may be missing something.
See the original "with Apollo" example:
https://github.com/zeit/next.js/tree/canary/examples/with-apollo
Here's my code for initApollo:
import { ApolloClient } from 'apollo-client'
import { HttpLink } from 'apollo-link-http'
import { InMemoryCache } from 'apollo-cache-inmemory'
import fetch from 'isomorphic-fetch'

import { ApolloLink } from 'apollo-link'
import { withClientState } from 'apollo-link-state'

import config from '../config'

let apolloClient = null

// Polyfill fetch() on the server (used by apollo-client)
if (!process.browser) {
  global.fetch = fetch
}

const cache = new InMemoryCache()

const defaultState = {
  currentView: {
    __typename: 'CurrentView',
    view: 'list'
  }
}

const stateLink = withClientState({
  cache,
  defaults: defaultState
  // resolvers: {
  //   Mutation: {
  //     switchView: (_, { currentView }, { cache }) => {
  //       const query = gql`
  //         query getCurrentView {
  //           getCurrentView @client {
  //             currentView
  //           }
  //         }
  //       `
  //       const previous = cache.readQuery({ query })
  //       const data = {
  //         currentView: {
  //           ...previous.currentView,
  //           currentView: view
  //         }
  //       }

  //       cache.writeQuery({ query, data })
  //     }
  //   }
  // }
})

function create (initialState) {
  return new ApolloClient({
    connectToDevTools: process.browser,
    ssrMode: !process.browser, // Disables forceFetch on the server (so queries are only run once)
    link: ApolloLink.from([
      stateLink,
      new HttpLink({
        uri: config.apiUrl,
        opts: {
          credentials: 'same-origin' // Additional fetch() options like `credentials` or `headers`
        }
      })
    ]),
    cache: cache.restore(initialState || {}),
  })
}

export default function initApollo (initialState) {
  // Make sure to create a new client for every server-side request so that data
  // isn't shared between connections (which would be bad)
  if (!process.browser) {
    return create(initialState)
  }

  // Reuse client on the client-side
  if (!apolloClient) {
    apolloClient = create(initialState)
  }

  return apolloClient
}

Then I have a gql query in getCurrentView.js:
import gql from 'graphql-tag'

export default gql`
  query getCurrentView {
    currentView @client {
      view
    }
  }

And then I have the component composed with withData (the same file as in the Next.js example), the http queries and the local query:
import { Component } from 'react'
import withData from '../../lib/withData'

import config from '../../config'

import { graphql, compose } from 'react-apollo'
import allProducts from '../../graphql/allProducts'
import getCategoryBySeoName from '../../graphql/getCategoryBySeoName'
import { getCurrentView } from '../../graphql'
// [other imports cut...]

class Categoria extends Component {
//...
}

export default compose(
  withData,
  graphql(getCurrentView, {
    name: 'currentView'
  }),
  graphql(allProducts, {
    name: 'allProducts',
    options: ({ url }) => ({ variables: { categorySeoName: url.query.categorySeoName, limit: config.itemsPerPage, offset: 0 } })
  }),
  graphql(getCategoryBySeoName, {
    name: 'getCategoryBySeoName',
    options: ({ url }) => ({ variables: { seoName: url.query.categorySeoName } })
  })
)(Categoria)

I receive the following error:
Unhandled (in react-apollo:Apollo(Apollo(Apollo(Categoria)))) Error: Network error: Cannot read property 'Query' of undefined
    at new ApolloError (http://localhost:3001/_next/1517221068041/page/categoria.js:21154:28)
    at ObservableQuery.module.exports.ObservableQuery.currentResult (http://localhost:3001/_next/1517221068041/page/categoria.js:20361:24)
    at GraphQL.dataForChild (http://localhost:3001/_next/1517221068041/page/categoria.js:18856:62)
    at GraphQL.render (http://localhost:3001/_next/1517221068041/page/categoria.js:18906:33)
    at finishClassComponent (http://localhost:3001/_next/1517221068041/commons.js:7879:31)
    at updateClassComponent (http://localhost:3001/_next/1517221068041/commons.js:7856:12)
    at beginWork (http://localhost:3001/_next/1517221068041/commons.js:8231:16)
    at performUnitOfWork (http://localhost:3001/_next/1517221068041/commons.js:10230:16)
    at workLoop (http://localhost:3001/_next/1517221068041/commons.js:10294:26)
    at HTMLUnknownElement.callCallback (http://localhost:3001/_next/1517221068041/commons.js:548:14)

Thank you very much for your support.
If I can find a way to solve this issue I may post a PR for a "with Apollo and apollo-link-state" on Next.js.

I think the local store uses the cache on the client side which you can't query on the server side.
This is from the apollo docs:

In the past, Apollo users stored their application’s local data in a separate Redux or MobX store. With apollo-link-state, you no longer have to maintain a second store for local state. You can instead use the Apollo Client cache as your single source of truth that holds all of your local data alongside your remote data. To access or update your local state, you use GraphQL queries and mutations just like you would for data from a server.

https://www.apollographql.com/docs/link/links/state.html

I agree with dav-is: the initial state of apollo-link-state should be created on the server, too and passed to client. All the @client queries should simply be skipped server-side.
Since Next.js + Apollo + apollo-link-state is a great stack, it would be useful to have a working example "with apollo-link-state" on the Next.js repository by the Apollo staff :) @peggyrayzis

I don’t think @client queries should be ignored on the server. The server has everything it needs to run these queries. We set a default in the store on the server and our query and mutation resolvers are define in code that the server has access to.

@dav-is While technically feasible, wouldn't this encounter massive scaling issues? You'd be keeping the entire state of all your users on the server. Either that or have the problem of having to hit the DB every time you want to change something in the user's state. Seems that db-backed user state should be part of some sort of User db object but that this should not be one in the same with the apollo state. The apollo state seems like it should fulfill the same purpose as the redux state - a manageable, local, global state for the client.

@timhuff You'd be keeping the entire state of all your users on the server

The state is reset on every request. Client queries aren’t database calls. And with SSR, client queries would only be setting defaults as it’s the beginning of a request chain. All other client actions would be done in the browser.

@dav-is I see. I was misunderstanding how this would work.

I ended up using Redux for the local state of my Next.js application. I'll switch back to apollo-link-state as soon as I find a good way to use it (or a working example without dynamic import hacks) @peggyrayzis

I was surprised to find there is difficulty supporting this. I expected it would be transparent to next.js.
Perhaps the confusion here is that the terms "server" and "client" are getting overloaded. We have

The graphql server: responds to graphql requests.
The Next.js server: renders the app and sends it to the browser client. (This server "pretends" to act like a browser client: it's really isomorphic to it 😉)
The browser client: fully able to render the app from scratch or pick up from a server-rendered app.
The @client state and queries: the part of the apollo-cache that does not make network requests to the graphql server.

@dav-is Would this be direct analogy to redux SRR?

The data normally in the redux store is now moved into part of the the apollo-cache, it's just "tagged" with @client to indicate it's not connected to a remote graphql server schema.
The "queries" and "mutations" on the @client fields correspond to to reading data from the redux store or dispatching classical ("non-async") actions that result in updates to the store. Now, they just read or update @client fields in the apollo-cache.
The only difference between these @client queries and the "normal" ones are that they do not hit the network, otherwise the result is the same: data read from or written to the apollo-cache.
Thus, the @client queries work the same on the client or the server, and instead of having to send a separate redux store down to the client after SSR, all that state is now contained in the apollo-cache, which we are shipping down anyway.

I was able to make this work with the skip option.
export default compose(   withData,   graphql(getCurrentView, {     name: 'currentView',     skip: typeof window === 'undefined'   }) )(Categoria)

Isn’t that just going to disable the query on the server side? What’s the point in SSR if it can’t render everything on the server?

Hi @dav-is,
I agree with you that the server has everything it needs and should run @client queries/mutations.
I was just posting a different solution since @f2net  solved it by keeping redux.  If he is only using it for the client, maybe he doesn't need to keep redux and can skip the @client queries on the server.
At least in my case, I only needed it to run in the browser and was able to remove redux.

Looks like actions were taken here, so I'm going to close this issue!

@fbartho link to the fix?

@dav-is Up in this thread @leoalves suggested a work-around, and others suggested that separate Feature Requests should be made for adding SSR friendliness to apollo-link-state.
This specific ticket doesn’t have any pending action items — as I read the thread. Please let me know if I misunderstood!

@fbartho the issue is the error thrown in the very first post in the issue. The further discussion talks about workarounds to the general issue, but no actual solutions.

@dav-is Reopening because I didn't understand :P

@leoalves I tried your approach with the new react-apollo Query Component like this
<Query
   query={gql`
        {
          viewer(id: "0x2") {
            id
            email
          }
          authenticated @client
        }
  `}
  skip={typeof window === 'undefined'}
>
  {({ loading, error, data }) => {
    if (loading) return
Loading...
;
    if (error) {
      console.log(error);
      return
Error :(
;
    }
    return
{data.viewer.email}
;
  }}
</Query>

Unfortunately this does not work for me. Any ideas?
Also, will there be an official solution to this problem without workarounds? Thanks!

@hollandThomas I won't be much help here since I never used the Query Component.
But I guess you can always skip before you render the component.
{
typeof window !==  undefined && <Query
   query={gql`
    {
      viewer(id: "0x2") {
        id
        email
      }
      authenticated @client
    }
  `}
>
  {({ loading, error, data }) => {
    if (loading) return
Loading...
;
    if (error) {
      console.log(error);
      return
Error :(
;
    }
    return
{data.viewer.email}
;
  }}
</Query>
}

If that doesn't work the issue is not the skip but something else.

Really curious about this, I made the switch to Apollo with this as one of the real winning benefits (being able to derive initial client state from getDataFromTree). Seems like that isn't the case yet. Whats the plan for implementing this? Any work arounds or custom implementations to get this feature on the server in userland?

In case anyone else wonders about this I was able to get this working with SSR by just not passing the defaults key when rehydrating. if defaults are set the link will write the defaults to cache overwriting your rehydration.

@brad-decker ,did you mean we don't have to bypas SSR with apollo-link-state anymore? do you have an example code ?

@brad-decker I tried something like:
const clientState = (typeof window === "undefined")
  ? { defaults, resolvers }
  : { resolvers }
return new ApolloClient({
  cache,
  clientState,
  uri: config.endpoint
})

But that didn't work. Is it possible to show us your example please?

I noticed that when using writeData directly will add local data to the cache on getInitialProps (SSR):
static async getInitialProps ({ apolloClient }) {
  apolloClient.writeData({
    data: {
      breadcrumbs: {
        __typename: "Breadcrumbs",
        items: ["one", "two", "three"]
      }
    }
  })

  const previous = apolloClient.readQuery({
    query: gql`{ breadcrumbs { items } }`
  })

  apolloClient.writeData({
    data: {
      breadcrumbs: {
        __typename: "Breadcrumbs",
        items: [ ...previous.breadcrumbs.items, "four", "five" ]
      }
    }
  })

  return {}
}

Not great but it seems like it could be a work around?

@brad-decker I'd also be super interested in example code.

Has anyone made any progress on this?

I have this working following the official next.js example repo. Give me a few minutes to make a gist and I'll post it. It's in TS though.

This is working for me currently, but I haven't implemented mutations yet. https://gist.github.com/richbai90/98011174f66ed275d9531ea5813bf4a2

Thanks at @richbai90 that helped a-lot. I have it up and going now. Just a note a "resolvers: {}" object seems to be necessary for stateLink to work. I think the docs mention you only need to declare the defaults object, but I needed both to get this working.

this is what I have. Sorry for the delay:
in my store/ folder I have setup a single entry point that merges configuration objects from different files. config.defaults is the overall default object to write to the store.
export const createStateLink = (cache: InMemoryCache) => {
  // this function will be used to seed state and to reset it when necessary
  const writeDefaults = () => {
    cache.writeData({ data: config.defaults });
  };

  const link = withClientState({
    resolvers: config.resolvers,
    typeDefs,
    cache,
  });

  return {
    link,
    writeDefaults,
  };
};

then in my Apollo client initializer utility:
  // initialize our local state with apollo-link-state.
  const { link: stateLink, writeDefaults } = createStateLink(cache);
  if (!initialState) {
    /**
     * withClientState has a 'defaults' key that you think would
     * be a good way of setting your default state. That's true,
     * only if you want to override the existing values from SSR
     * on the initial client side render.
     *
     * Under the hood, apollo-link-state just calls
     * cache.writeData({ data: defaults }) when default is set
     * regardless of whether data exists yet or not.
     */
    writeDefaults();
  }
  const client = new ApolloClient({
    connectToDevTools: process.browser,
    shouldBatch: true,
    ssrMode: !process.browser,
    link: ApolloLink.from([
      stateLink,
      authLink,
      persistedQueryLink.concat(httpLink),
    ]),
    cache,
  });

  // When reseting the store, write the defaults to the state tree.
  client.onResetStore(writeDefaults);

  return client;

@richbai90  thanks for the workaround ! can you explain, what actually does your code does? does it solves the main issue that we facing with @client on SSR and what if we want to call the @client on the browser only ( we want to access localstorage etc).

With apollo-client v2.5, apollo-link-state was merged into main apollo-client lib.
So now, everything is handled with apollo-client and we don't any to rely on 'stateLink'.
Right now I'm testing initial data load in a page component via getInitialProps(ctx)
 static async getInitialProps(ctx: any) {
    const {
      apolloClient
    }: { apolloClient: ApolloClient<NormalizedCacheObject> | null } = ctx;

    if (apolloClient) {
     const data = await apolloClient.query({
        query: CATALOG_QUERIES.SQ_GET_POSTS,
        variables: { last: 10 }
      });
      console.log('post-page, graphql data loaded', data);

      const data2 = await apolloClient.query({
        query: CATALOG_QUERIES.CQ_GET_VARS
      });
      console.log('post-page, graphql data loaded @client', data2);
    }

    return {};
  }

And
export const CATALOG_QUERIES = {
  SQ_GET_POSTS: gql`
    query AllPosts($last: Int) {
      allPosts(last: $last) {
        id
        title
        text
        createdAt
      }
    }
  `,
  CQ_GET_VARS: gql`
    query Cli_get_vars {
      cli_get_vars @client {
        counter
        counter2
      }
    }
  `
};,

And when page loads it works without problem, i don't know if v2.5 (which uses ssr flag) solved the link-state srr issue, but I think it can be an option to consider.

I'm having the same issue and if I understood correctly @brad-decker is doing is writing defaults values on the cache before is actually initialized. My problem is that the @client resolver depends on values of a different query. So a query has to be executed in the server, I need those values in the cache, and then the client resolver would know what to return.
So pretty much I have this query
 query product($id: ID!) {
    product(where: { id: $id }) {
      isInCart @client
      ...ProductData
    }
  }

in order to return the correct value in the isInCart resolver, I need the data of the product first, and I only have the data when the product query is run on the server the first time. I can't write defaults because I don't have them.
I'm using apollo-client 2.5


Is there a way to have 2 message listeners

I'm running a webhook and bot merged together, so only passing commands with prefix through the message listener is not the best option for. Editing the message.js is not the best way to achieve those different type of listeners, so the optimal way would be to have 2 message.js, one for the webhook and one for the commands with prefix.
Is there any way to do this, with the module setup?

I don't know why you'd think using message.js would be the wrong way to do it - that's precisely what message.js is meant to be used for - receiving all the messages. Guidebot doesn't have the capacity to load 2 different message events, but you could just add your own client.on("messages" in the main file if that's what you want.

Yes, i figured that too. Just old conventions for me to have very different checks and functionality not in the same file with ifs. But yes i figured I could just call client.on once again, dirty way still, but what else should i do. Thanks for the reply. Can be closed.


Custom elements register without global styles breaks slides initialization.

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/xenodochial-water-5qrwep?file=/src/App.js
Bug description
I'm using Swiper custom elements inside React component which is rendered then inside other custom element.
Because of that, I can't insert Swiper styles globally and use register(false) for custom elements registration to prevent styles been inserted into document head and provide styles with the injectStylesUrls param.
In that case swiper-slides stop been properly initialized. No width, attributes, classes are set in swiper-slide nodes anymore.
Expected Behavior
Slides initialization works the same way if register() called without false argument.
Actual Behavior
No response
Swiper version
9.0.5
Platform/Target and Browser Versions
MacOS, Chrome 109
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Check docs https://swiperjs.com/element#injecting-styles, you also need to add styles to the document


Aggregate PR

Aggregate of the following PRs:
https://github.com/wildfly/wildfly/pull/18226
https://github.com/wildfly/wildfly/pull/18193
https://github.com/wildfly/wildfly/pull/18043
https://github.com/wildfly/wildfly/pull/17990
https://github.com/wildfly/wildfly/pull/17856

<--- THIS SECTION IS AUTOMATICALLY GENERATED BY WILDFLY GITHUB BOT. ANY MANUAL CHANGES WILL BE LOST. --->

Wildfly issue links:

WFLY-19715
WFLY-19298
WFLY-19760
WFLY-19464

<--- END OF WILDFLY GITHUB BOT REPORT --->
More information about the wildfly-bot[bot]

All are merged.


Multiserver implementation

Is tehre any way (or best practice) how to implement this JWT for multiserver (multi app) system?
for example: I want to have auth server as a separate application. Then I have multiple servers (apps) like warehouse, crm,... in the ecosystem.
Auth server should be responsible for issuing tokens, handling permissions and user settings. other apps should be able to validate those tokens.

JWT are stateless so you shouldn't have any issues. On the auth server you would want your settings to look something like this:
JWT_AUTH = {
    'JWT_PUBLIC_KEY': <cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKey object>,
    'JWT_PRIVATE_KEY':<cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKey object>,
    'JWT_ALGORITHM': 'RS512',
    'JWT_VERIFY': True,
}

other servers:
JWT_AUTH = {
    'JWT_PUBLIC_KEY': <cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKey object>,
    'JWT_ALGORITHM': 'RS512',
    'JWT_VERIFY': True,
}

This will allow only the auth server to issue new JWT and the other servers to verify the JWT without exposing your private key. You will need to use the cryptography library to set the JWT_PUBLIC_KEY and JWT_PRIVATE_KEY. Documentation can be found here and there is an example in the tests

I think there's an interesting blog post / example project to work on here.

@jpadilla Could you post here a link to that blog post (if you have it). Im really interested in this kind of implementation.


WAMRC terminator bug

wamrc has a bug in the LLVM compilation flow when a compare instruction precedes a parametrized block. I have attached a sample WASM file below that demonstrates this, where the sign extension instruction is inserted after the terminator.
The compiler is built with default flags: cmake -B build; make -C build
bug.tar.gz

Hi, https://github.com/bytecodealliance/wasm-micro-runtime/pull/2622 should fix this issue. Thanks for spotting this issue 😄

Close this issue since it was fixed.


Simplify fragments by using .Params without assignment

What this PR does / why we need it:
Simplify call to .Params and make all fragment code more consistent.

tmp_full didn't seem like the most describing one. For now it's not that temporary anymore and root seemed more descriptive.
Happy that you agree with the refactoring \o/


FAT-4524 - source instance to marc

Purpose
FAT-4524 - oaipmh-enhancement.feature
Approach
How does this change fulfill the purpose?
TODOS and Open Questions

[ ] Use GitHub checklists. When solved, check the box and explain the answer.

Learning
Describe the research stage. Add links to blog posts, patterns, libraries or addons used to solve this problem.


Fix some issues with OSX build

Remove some v2 sources from NuGet.Config
Update dnx package to rc2-16357 (the old package is no longer available)
Use 'ulimit -n 2500' to avoid 'Too many open files' error from dnx
Make sure mono compilers that come with the mono MSBuild bootstrap package have executable permission.

@dotnet-bot test this please

LGTM


Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 8.x

Having a problem after moving site to another server:

Uncaught Error: Module build failed: ModuleBuildError: Module build failed: Error: Missing binding C:\inetpub\XXXXXXX\node_modules\node-sass\vendor\win32-x64-57\binding.node
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 8.x
Found bindings for the following environments:

Windows 64-bit with Node.js 6.x

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass --force to build the binding for your current environment.

I've tried rebuilding node-sass as well as removing node_modules and running npm install but am still getting the same error
Would really appreciate some help with this

NPM version (npm -v): 6.4.1
Node version (node -v): v8.12.0
Node Process (node -p process.versions):
{ http_parser: '2.8.0',
node: '8.12.0',
v8: '6.2.414.66',
uv: '1.19.2',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '57',
nghttp2: '1.32.0',
napi: '3',
openssl: '1.0.2p',
icu: '60.1',
unicode: '10.0',
cldr: '32.0',
tz: '2017c' }
Node Platform (node -p process.platform): win32
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):
node-sass       4.9.4   (Wrapper)       [JavaScript]
libsass         3.5.4   (Sass Compiler) [C/C++]
npm node-sass versions (npm ls node-sass):
+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>deduped --<EMAIL_ADDRESS>

As the error message says you appear to have two versions of node
installed. Make sure you're running npm install or rebuild in the same node
8 environment i.e. same terminal. It's common for many editors to have
their own node versions baked it so double check your tools are using the
same node installation.
On Wed., 17 Oct. 2018, 1:35 am Jon Reeves<EMAIL_ADDRESS>wrote:

Having a problem after moving site to another server:
Uncaught Error: Module build failed: ModuleBuildError: Module build
failed: Error: Missing binding
C:\inetpub\XXXXXXX\node_modules\node-sass\vendor\win32-x64-57\binding.node
Node Sass could not find a binding for your current environment: Windows
64-bit with Node.js 8.x
Found bindings for the following environments:

Windows 64-bit with Node.js 6.x

This usually happens because your environment has changed since running npm
install.
Run npm rebuild node-sass --force to build the binding for your current
environment.
I've tried rebuilding node-sass as well as removing node_modules and
running npm install but am still getting the same error
Would really appreciate some help with this

NPM version (npm -v): 6.4.1
Node version (node -v): v8.12.0
Node Process (node -p process.versions):
{ http_parser: '2.8.0',
node: '8.12.0',
v8: '6.2.414.66',
uv: '1.19.2',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '57',
nghttp2: '1.32.0',
napi: '3',
openssl: '1.0.2p',
icu: '60.1',
unicode: '10.0',
cldr: '32.0',
tz: '2017c' }
Node Platform (node -p process.platform): win32
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):
node-sass 4.9.4 (Wrapper) [JavaScript]
libsass 3.5.4 (Sass Compiler) [C/C++]
npm node-sass versions (npm ls node-sass):
+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>deduped--<EMAIL_ADDRESS>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2512, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWOMzwUTHKhtoIEw8DU8_wXSmi1xCks5ule6XgaJpZM4XegCH
.

Thanks for the response, but I'm not sure that applies here -
This is a newly built server and node has only been installed once.
All the version commands above were run from the same terminal window as the npm install and node-sass rebuild.
I am not using any IDE or other editor.
The binding referenced in the error does exist at that location
Would really appreciate any help in how to troubleshoot this and get it working
Thanks

What the error message says is that during installation your environment
presented as node 6, and so it downloaded the node 6 binary into the
node_modules/node-sass/vendor directory.
You can confirm this by deleting the node-sass folder from node_modules,
running npm install, and watching the npm output as it downloads the binary.
On Wed., 17 Oct. 2018, 7:08 pm Jon Reeves<EMAIL_ADDRESS>wrote:

Thanks for the response, but I'm not sure that applies here -
This is a newly built server and node has only been installed once.
All the version commands above were run from the same terminal window as
the npm install and node-sass rebuild.
I am not using any IDE or other editor.
The binding referenced in the error does exist at that location
Would really appreciate any help in how to troubleshoot this and get it
working
Thanks
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2512#issuecomment-430531492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWBrFVEL5jrwAxzE096lCMNu545MBks5uluVogaJpZM4XegCH
.

Thanks, I tried that but it downloads the same binary - node-sass\vendor\win32-x64-57\binding.node - which I think is the correct one for node 8.12.0?
Is there something specific I should be looking for in the output - I can't see anything that relates to the node version?
I did notice that at first it was using a cached binary from my user profile which I had to manually delete (node cache clean --force did not remove it).  I also uninstalled the windows-build-tools which I originally installed in order to run the node-sass rebuild in case this had put another node version in but it made no difference
I tried the process you described from both Git Bash and PowerShell but both gave the same results ( node -v shows the same in both as well)
Here is the output from npm install after deleting the node-sass folder and cached binary:

PS C:\inetpub\some_website> npm install

<EMAIL_ADDRESS>install C:\inetpub\some_website\node_modules\node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.4/win32-x64-57_binding.node
Download complete .] - :
Binary saved to C:\inetpub\some_website\node_modules\node-sass\vendor\win32-x64-57\binding.node
Caching binary to C:\Users\admin.site\AppData\Roaming\npm-cache\node-sass\4.9.4\win32-x64-57_binding.node

<EMAIL_ADDRESS>postinstall C:\inetpub\some_website\node_modules\node-sass
node scripts/build.js

Binary found at C:\inetpub\some_website\node_modules\node-sass\vendor\win32-x64-57\binding.node
Testing binary
Binary is fine
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies your self.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
added 22 packages from 39 contributors and audited 13677 packages in 9.005s
found 1 moderate severity vulnerability
run npm audit fix to fix them, or npm audit for details

That is the correct binary for Node 8. You should now have the following file node_modules\node-sass\vendor\win32-x64-57\binding.node which will allow you to run node-sass.
Also confirm you don't have two node-sass installs as potentially indicated in the npm ls at node_modules/laravel-mix/node-modules.

That's the same binary I've always had but am still getting the error.
I've just checked the laravel-mix/node_modules and there is no node-sass under there
Any ideas?

OK, our developers have managed to fix the issue.  It was to do with an old version of vue being installed somehow - they did an update on vue, then recompiled all the javascript and the error went away
Thanks for all your help with this

Please write this command on Command prompt
npm rebuild node-sass

sass

thanks very much it works for me.

If your terminal/command prompt says:
Node Sass could not find a binding
for your current environment:
OS X 64-bit with Node 0.10.x
and you have tried the following commands such as:
npm cache clean --force
rm -rf node modules
npm install
npm rebuild node-sass
npm rebuild node-sass
& still NOTHING works..
Just run this in the terminal manually: node node_modules/node-sass/scripts/install.js
now run npm start or yarn start

If your terminal/command prompt says:
Node Sass could not find a binding
for your current environment:
OS X 64-bit with Node 0.10.x
and you have tried the following commands such as:
npm cache clean --force
rm -rf node modules
npm install
npm rebuild node-sass
npm rebuild node-sass
& still NOTHING works..
Just run this in the terminal manually: node node_modules/node-sass/scripts/install.js
now run npm start or yarn start

If your terminal/command prompt says:
Node Sass could not find a binding
for your current environment:
OS X 64-bit with Node 0.10.x
and you have tried the following commands such as:
npm cache clean --force
rm -rf node modules
npm install
npm rebuild node-sass
npm rebuild node-sass
& still NOTHING works..
Just run this in the terminal manually: node node_modules/node-sass/scripts/install.js
now run npm start or yarn start

What worked for me was to add "C:\Program Files\nodejs" on top of Options -> Projects and Solutions -> Web Package Management because node-sass picks up VStudio version of node which is 10 for some reason and not the global one which is 12.


Unix socket support

Any chance or easy hint to get Unix sockets working for a connection?
ArangoDB does support it.
requests doesn't want to support it: Unix domain sockets #2355
Good reasons:

Less overhead. No IP stack needed. Connections through sockets are known to be faster compared to TCP.
More secure. The application can talk via a local socket in the file system which is not exposed as fast as a listening port by misconfiguration.
In Docker you can switch off networking for a container stack if the only IP use is the db connection.

Thanks!

Hey @sausix!
This should be possible given that the ArangoClient constructor supports user-defined HTTP Clients, so we might be able to get away with creating a UnixSocketsHTTPClient that overrides the create_session() and send_request() methods to handle a Unix connection.
Although not natively supported in requests, you could consider the requests-unixsocket package as a workaround.
Here is what the DefaultHTTPClient in python-arango looks like, and here is what I can suggest as a draft for the UnixSocketsHTTPClient:
from typing import MutableMapping, Optional, Tuple, Union
from urllib.parse import urlparse

import requests_unixsocket
from requests import Session
from requests_toolbelt import MultipartEncoder

from arango.http import DefaultHTTPClient
from arango.response import Response
from arango.typings import Headers

DEFAULT_REQUEST_TIMEOUT = 60

class UnixSocketsHTTPClient(DefaultHTTPClient):
    """Unix Socket HTTP client implementation.

    :param unix_socket_url: Unix socket URL.
    :type unix_socket_url: str
    :param request_timeout: Timeout in seconds for each individual connection.
    :type request_timeout: int | float
    :param retry_attempts: Number of retry attempts.
    :type retry_attempts: int
    :param backoff_factor: Backoff factor for retry attempts.
    :type backoff_factor: float
    :param pool_connections: The number of urllib3 connection pools to cache.
    :type pool_connections: int
    :param pool_maxsize: The maximum number of connections to save in the pool.
    :type pool_maxsize: int
    :param pool_timeout: If set, then the pool will be set to block=True,
        and requests will block for pool_timeout seconds and raise
        EmptyPoolError if no connection is available within the time period.
    :type pool_timeout: int | float | None
    """

    def __init__(
        self,
        unix_socket_url: str,
        request_timeout: Union[int, float, None] = DEFAULT_REQUEST_TIMEOUT,
        retry_attempts: int = 3,
        backoff_factor: float = 1.0,
        pool_connections: int = 10,
        pool_maxsize: int = 10,
        pool_timeout: Union[int, float, None] = None,
    ) -> None:
        self.unix_socket_url = unix_socket_url
        self.request_timeout = request_timeout
        self._retry_attempts = retry_attempts
        self._backoff_factor = backoff_factor
        self._pool_connections = pool_connections
        self._pool_maxsize = pool_maxsize
        self._pool_timeout = pool_timeout

    def create_session(self, host: str) -> Session:
        """Create and return a new session/connection.

        :param host: ArangoDB host URL.
        :type host: str
        :returns: requests session object
        :rtype: requests.Session
        """
        # retry_strategy = Retry(
        #     total=self._retry_attempts,
        #     backoff_factor=self._backoff_factor,
        #     status_forcelist=[429, 500, 502, 503, 504],
        #     allowed_methods=["HEAD", "GET", "OPTIONS"],
        # )

        unix_adapter = requests_unixsocket.UnixAdapter(
            self.request_timeout,
            self._pool_connections,
            # connection_timeout=self.request_timeout,
            # pool_maxsize=self._pool_maxsize,
            # pool_timeout=self._pool_timeout,
            # max_retries=retry_strategy,
        )

        session = Session()
        session.mount("http+unix://", unix_adapter)

        return session

    def send_request(
        self,
        session: Session,
        method: str,
        url: str,
        headers: Optional[Headers] = None,
        params: Optional[MutableMapping[str, str]] = None,
        data: Union[str, MultipartEncoder, None] = None,
        auth: Optional[Tuple[str, str]] = None,
    ) -> Response:
        """Send an HTTP request.

        :param session: Requests session object.
        :type session: requests.Session
        :param method: HTTP method in lowercase (e.g. "post").
        :type method: str
        :param url: Request URL.
        :type url: str
        :param headers: Request headers.
        :type headers: dict
        :param params: URL (query) parameters.
        :type params: dict
        :param data: Request payload.
        :type data: str | MultipartEncoder | None
        :param auth: Username and password.
        :type auth: tuple
        :returns: HTTP response.
        :rtype: arango.response.Response
        """
        url_path = urlparse(url).path
        unix_url = f"http+unix://{self.unix_socket_url}/{url_path.lstrip('/')}"

        response = session.request(
            method=method,
            url=unix_url,
            params=params,
            data=data,
            headers=headers,
            auth=auth,
            timeout=self.request_timeout,
        )
        return Response(
            method=method,
            url=response.url,
            headers=response.headers,
            status_code=response.status_code,
            status_text=response.reason,
            raw_body=response.text,
        )

from arango import ArangoClient

# Instantiate the custom Unix socket HTTP client
unix_socket_http_client = UnixSocketsHTTPClient('path/to/unix/socket')

# Create an ArangoDB client instance with the custom HTTP client
db = ArangoClient(http_client=unix_socket_http_client).db(verify=True)

@aMahanna Wow. Didn't expect such a positive and detailed answer. Thank you!
I found the http_client immediately and I was already subclassing DefaultHTTPClient. I also found requests-unixsocket while digging in the issues of requests.
But I had concerns about stability. What about timeouts? What about multithreading?
An official and tested solution would be nice. One that has been tested and used by many people.
Don't get me wrong. You code will probably work and I appreciate it. But it's new and requests-unixsocket is not heavily used too.
I know it's complicated for this project by mostly being dependent of the requests package.
That's basically ok because I trust requests to be grown up and stable. python-arango simply uses requests without any hacky ways so I trust it too. And python-arango has probably a lot of use cases in the world already.
If just requests would allow Unix sockets we had no problems here and other packages would benefit too.
Using Unix sockets is just not common or well known enough. What about making it official for python-arango?
For testing and contributing to the community, I would be in!

Hi @sausix,
Our primary aim with this driver is to maintain platform independence to the greatest extent possible. While Unix domain sockets offer advantages in terms of efficiency for inter-process communication, they are inherently platform-specific. Adding them would introduce a feature that is not natively supported on Windows environments.
The fact that Unix domain sockets are designed for inter-process communication on the same host makes it a relatively niche requirement for our driver. Not saying it's not useful (could be great for testing, for example), but it's way more common for the driver and the database server to be running on different hosts.
In our experience, very specific implementations that are not widely used by a significant portion of our user base can become dusty and challenging to maintain over time ("rotting code").
Don't get me wrong, I'm all for people using Unix domain sockets on top of our driver. We strive to make it as customizable and flexible as possible. I believe the approach suggested by @aMahanna , which involves extending the driver for specific needs, is the most practical solution. This way, we can keep the core driver platform-agnostic while still providing the means for users like yourself to implement more specific functionalities.
I would tend towards closing this as "Won't fix", but if you have any further thoughts or ideas, please feel free to share them with us.

Hey @apetenchea
I fully agree with your arguments. Except running a database should imply it's primarily run on Linux hosts. Maybe there's a statistics? My personal use case will be Docker.
Don't want to argue anymore because I basically fully understand and agree to not break or fork for platform compatibility at too much cost.
I would totally be fine if we close this issue but at least keep @aMahanna 's wonderful snippet anywhere. Maybe here in the docs: HTTP Clients?
Could be marked as experimental and unmaintained. Using sockets would be a good real world use case for an HTTPClient implementation.
I would definitely share my experience by pull requests if Unix sockets would be a seperate docs page for example.
Thank you.

Definitely, we should keep @aMahanna example! It's already available on this issue, which is going to be indexed by search engines, since the project is public. People will be able to get here through a search.
The HTTP Clients page already contains a generic example. We should keep it as simple as possible, therefore I would be hesitant to add the UnixSocketsHTTPClient on top of that.
Nevertheless, you are more than welcome to share your expertise with our community. I'll be moving this thread into a "Show and tell" discussion here.
Please feel free share more info, gists or any relevant code snippets.


Add new command (!scope ?) for questions outside the scope of TOP

Checks

[X] I have thoroughly read and understand The Odin Project Contributing Guide
[X] The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

Do you want to be assigned to this issue?

[X] I would like to be assigned this issue to work on it

Description of the Feature Request
The Discord server gets a lot of general programming questions, outside the scope of TOP, which per the rules aren't answered. It would be neat to have a command that outputs a boilerplate message about how this isn't server for their questions. While I am aware that for the most part this bot is migrating to slash commands, I would propose that in this instance a text command version is also added, given I could see it being used (mostly) in a running message
Acceptance Criteria
- [ ] A new slash command is created which when used prints a message about what questions are in scope (proposed name `/scope`)
- [ ] A new text command is created which uses the same message (proposed name `!scope`)

Additional information
No response

This is fantastic! May I also suggest including a link to the following section in Community Rules
Ask questions about content or projects in our curriculum
The purpose of this server is to support people when they run into issues doing our curriculum. This allows our volunteers to know the exact scope of your problem and correct any poor advice. In addition, this limited scope helps us identify areas in our curriculum that we need to improve.
Do not ask for advice/help on homework or personal projects, even if the topic is covered by our curriculum. Instead, research other servers/communities that offer general programming help.

Only just spotted this got proposed in the discord suggestions a few weeks ago: https://discord.com/channels/505093832157691914/1277817788467122237. Willing to step aside if they still want to do it


Node-RED close server

without waiting clients to disconnect
close child process from Electron
clean all temporary files, this way another user does not open previous work

Seems to be ok in v0.9.5


space-x- not preserved in active: mode

Hi there,
Still loving the lib ❤  I thought I would inform you that spacing is not kept in active mode (only case I tested):
https://snack.expo.dev/dlXET-ZuQ
While clicking and holding on the button, you'll notice that spacing is disabled.
Adding active:space-x-2 to Pressable solve the issue, but I believe it should stay by default. I let you decide if it worth further investigation.

Fixed in 2.0.0-next.53


Introduce basic vim bindings in prompts

closes #27
Description
Incorporates Basic Vim Bindings in prompt
basic vim bindings:

vim key
function

k
up

j
down

l
right

h
left

@timo-reymann
Please do let me know if any changes are necessary.

Looks good to me, verified locally works like a charm 👍

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add Hoverable Library

Similar to context_menu.ts, add support for hovering over things and getting a styled pop-up.
Add a hover pop-up to dice results in the chat that shows individual dice

Done in main