use pandas.DataFrame, as interface between sampling library and mcmcplotlib

Since DataFrames are simply indexed and labelled numpy arrays (from memory and performance point of view, at least), why don't we use DFs as interface between tracing library and plotting?
e.g. the code might look like this:
import pymc3 as pm
import mcmcplotlib as mcp

with pm.Model() as model:
  ..
  trace = pm.sample(2000..)

trace_df = trace.as_df(varnames=['Intercept', 'x', 'sigma'])

mcp.plot_trace(trace_df, varnames=['x', 'sigma']) #e.g. we are not interested in plotting intercept

So that mcmcplotlib don't have to know about library-specific trace object(s).
And we don't have to pass a list of numpy arrays + list of varnames for plotting.
I believe it is a safe assumption that most users of pymc, pystan and emcee have pandas installed.

If we can avoid the dependency (or have a fallback), I'd strongly prefer that. There are many (probably not a majority) users of pystan/pymc/emcee which will not have pandas installed.

I think pandas is a perfectly reasonable dependency these days.

(strong personal opinion warning)
I believe the whole PyData ecosystem is somewhat crippled by reluctance to use pandas as standard way to access (panel) data. IMO, Scikit-learn should be tightly integrated with pandas, as well as other libraries. And since pandas can act as interface, while something like dask can be an engine, we should embrace it. I like patsy, since it can reduce the amount of boiler plate and does not afraid to be dependant on pandas. In this regard, R has an edge, since dataframes is a standard data interface (as far as I know).
The purpose of mcmcplotlib is to be used in interactive environment, like jupyter, where anaconda is normally used. pystan/pymc/emcee can be used in pure server-side code or ETL, where pandas might not be as relevant, but the output is probably just data, not pretty charts..
I am generally against backward compatibilities, if that means more code to support or (go forbid) more boiler plate for user to write.

I agree Pandas is a very reasonable dependency nowadays. I think the same
goes for seaborn.
El may 25, 2016 7:55 AM, "Volodymyr"<EMAIL_ADDRESS>escribió:

(strong personal opinion warning)
I believe the whole PyData ecosystem is somewhat crippled by reluctance to
use pandas as standard way to access (panel) data. IMO, Scikit-learn should
be tightly integrated with pandas, as well as other libraries. And since
pandas can act as interface, while something like dask can be an engine, we
should embrace it. I like patsy, since it can reduce the amount of boiler
plate and does not afraid to be dependant on pandas. In this regard, R has
an edge, since dataframes is a standard data interface (as far as I know).
The purpose of mcmcplotlib is to be used in interactive environment, like
jupyter, where anaconda is normally used. pystan/pymc/emcee can be used in
pure server-side code or ETL, where pandas might not be as relevant, but
the output is probably just data, not pretty charts..
I am generally against backward compatibilities, if that means more code
to support or (go forbid) more boiler plate for user to write.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/mcmcplotlib/mcmcplotlib/issues/4#issuecomment-221539540

I do agree that we should not re-implement stuff that is available in seaborn already (even though I don't like 200+ lines functions in seaborn).
I don't like that seaborn imports it's style by default, and I don't want to change users mpl default when importing mcmcplotlib, if we can avoid it. Also, seaborn is not installed with anaconda by default atm.

seaborn without style changes

import seaborn.apionly as sns

If we want to go for labeled data (and I think especially for plotting labels are super important), we could also represent the trace as a xarray dataset. Using pandas isn't all that straight forward, as it doesn't have multidimensional dataframes, but the output from mcmc always always has more than 2 dimensions. (see also https://discourse.pymc.io/t/use-xarray-for-traces/73)
xarray is mentioned as the official replacement for pd.Panel in the pandas docs.
I've been using xarray to store traces for some time now in various projects, and this turned out to be really useful.

+1 on using xarray as the central interface.

+1 for xarray
Which interface?

xarray
list of xarrays (xarray.name(?) parameter)
(o)dict of xarrays (key=parameter name)?

Can xarray handle scalars, vectors and matrices in the same object?

@ahartikainen
A trace can be represented by a xr.Dataset very well. It acts a lot like a dict from varname to xr.DataArray, so it is already similar to our current trace object in many ways. See http://xarray.pydata.org/en/stable/data-structures.html

Closing as we have adopted xarray as interface


Make macOS build on Travis

Sigh.  This turned into a beast.  First, travis has a 4mb log limit which boost blasted right through.  So I piped the make stdout to a file.  Then, travis will timeout a build if it doesn't see anything on stdout for 10 minutes, so I had to background make and echo a "I'm still alive" message every minute.  Then, travis has a 50 minute timeout so I had to add caching and checks for whether the cache had been populated or not.  The staged boost installation is very large and would timeout the cache upload, so I switched over to an installed boost.
This is easily the most complicated bash script I've ever written.

Once this gets reviewed, I'll rebase everything down into one commit before merging.

You should run this through http://www.shellcheck.net . You don't have to fix everything because its very nitpicky, but it may have good ideas there.
Also, can you make it do the right thing by default when you run it outside of travis? I think you just have to set CLONE and TRACE to true by default.
Looking at the rest now...


omit error for unimplemented unpacking types

For unimplemented(so far) unpacking types, it should omit error message, and return failed result.
Signed-off-by: xiekeyang<EMAIL_ADDRESS>

Dup of #64?

yes, thanks.


Distribute the knowledge base (kb) files with IDR [Feature Request]

In order to IDR works we need the knowledge base (kb) files, the current folder contains the syskb*.bin files but it's missing the kb<version>.bin files, without them the analysis wont work. It can be found here  inside the 7zip files.

Fixed. Thanks.


[HOLD] Support recording and displaying paths of uploaded files

NOTE: Will work on tests next. Otherwise appreciate code review about choices made so far.
Why was this change made? 🤔
Connects to sul-dlss/dor-services-app#4256
This commit adds a new attribute to the AttachedFile model in order to record, and later display, the full source path of an uploaded file (if supplied). It modifies the Dropzone controller to display paths (if present) instead of base filenames, and makes the duplicate filename checker smart about this. It also fixes a bug with duplicate filename checking caused by https://github.com/sul-dlss/happy-heron/pull/2583/files#diff-81e6b6427ea21d10a73dc41dd6b55cbdccd6002a200ddf5cce9b5e26daee19f6R9.
How was this change tested? 🤨
CI and will be tested in a deployed env

Possibly has some overlap with #2800 -- though I don't think there will be any conflicts

Is this PR still relevant?

@peetucket 💬

Is this PR still relevant?

I don't know. @justinlittman is this now defunct? (Fine by me if so.)

I don't think so, but let's hold onto it until H2 HFS work is done.  Or leave it be?


[Shrines] Bird orbs and GTS

Purchasing a full orb from gts will cause it to not be detected as a full orb via the shrine plugin.

Get full bird orb (static)
Sell it on gts
Buy it from gts
Try to summon bird (zapdos)
See error

For orbs purchased via GTS to be able to summon legendary birds as normal.
Orion, Likely all.

no longer an issue, closing


Module 4 exercises [Ernest Opoku-Kwarteng]

WS2_M4E1_Template.docx

Well done, Ernest. You clearly grasped the material outlined in Module 4 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


[BugFix] BE build respect USE_AVX2/USE_AVX512 compile option

Problem Summary:
Fixes # (issue)
What type of PR is this:

[X] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto backported to target branch

[X] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-3.0


the result looks not good enough(UL training for MIT dataset)

I am not sure if i trained it correctly.

Could you give me some reference or release the pretrained model ?
thank you very much！

I have trained 150 epochs for 5 days.

OK, I got it .


[SQL-137] Admin API OIDC

SQL-137 Enable OIDC auth + admin account shadowing.
This PR wraps the admin API with interceptors that will:

Decode an OIDC token
Check it for claim scope (right now there is just a blanket admin scope)
Ensure that a local admin account is created to shadow

When an account exists, verifies that the OIDC issuer matches

Passes the identity for use by identified admin operations, disabling the subsequent native JWT checks.

This enables OIDC clients to directly hit the admin API, enabling a wide range of use cases and not limiting administration to the provided UI.

Looking through this, I'm still confused as to where and why OIDC needs to be ensured upon every xAPI authorization (as opposed to each admin account authorization). It's not obvious to me looking at the resource routes or the protocols.

I just added @cliffcaseyyet as a reviewer, which was probably something you were going to do once he got back. But I would specifically like him to look at the SQLite changes to see whether or not there are any better ways to perform migrations on that DBMS.

Looking through this, I'm still confused as to where and why OIDC needs to be ensured upon every xAPI authorization (as opposed to each admin account authorization). It's not obvious to me looking at the resource routes or the protocols.

Yep, this is one of the harder things to grok about this, your confusion is warranted. Basically, consider two scenarios:

OIDC is used to authenticate an admin, giving them a "native" app token to do subsequent operations. Ensuring OIDC shadow accounts only happens at the authentication route. This is effectively token exchange, you are exchanging your OIDC token for an LRSQL token and then doing stuff with it.
OIDC is accepted on all admin routes directly. Ensuring OIDC accounts happens any time an OIDC token is used. With this kind of direct federation, all you need is an OIDC token.

In scenario 1, a client MUST use the auth route first to exchange that token. That's an extra step, but that in and of itself isn't too big a deal (though annoying). The complexity comes in over time: lrsql doesn't really have any conception of "refresh tokens" or anything like that, so when the lrsql token expires, you need to go back and do it all over again. This means that in the meantime, in addition to keeping the OIDC token refreshed you need to maintain a lifecycle for the lrsql token, something completely outside of OIDC's purview.
Contrast that with scenario 2, where there is only ever one OIDC token involved. There is no extra request, and all policy (such as exp times) and behavior comes from the OIDC provider, not lrsql. The OIDC client automatically refreshes and handles lifecycle. For a system integrator coming in this is much more what they would expect from OIDC support, the extra request and lifecycle are unknown to that spec. Therefore software that is already OIDC-enabled will "just work" without custom calls and state. While neither scenario is "stateless" per se, scenario 2 has less to worry about.

Yep, this is one of the harder things to grok about this...
I think a lot of my confusion comes from when you say all xAPI authentication, I imagined you would need OIDC when performing LRS operations, like inserting and querying statements. From what you said and from what I saw in the code, it seems like you actually meant "all admin ops, not just logging in."

I think a lot of my confusion comes from when you say "all xAPI authentication", I imagined you would need OIDC when performing LRS operations, like inserting and querying statements. From what you said and from what I saw in the code, it seems like you actually meant "all admin ops, not just logging in."

Both are true...

You can (but are not required to) use an OIDC token to authenticate for LRS actions like posting statements. This covers the (somewhat narrow) use case of an OIDC-enabled web app sending statements to the LRS. Note that this was done in a separate PR, already merged to the feature branch.
You can also use OIDC, with the additional admin scope, to access all admin API actions.

You could use it to just log in and get an LRSQL token, a la scenario 1
Or you could use the OIDC token directly, for instance to create a set of long-lived basic auth credentials


#161255248 Refactor code follow feature

What does this PR do?
It refactors code that implements the following endpoints

/api/profile/<username>/follow
/api/profile/<username>/followers
/api/profile/<username>/following

Description of Task to be completed?

Usernames provided are validated
Users with similar names e.g martin and martinkaburu can be differentiated
Code uses serializers to complete tasks

Related PivotalTracker stories
#161255248

Pull Request Test Coverage Report for Build 280

42 of 46 (91.3%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 92.118%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

authors/apps/profile/api/views.py
20
22
90.91%

authors/apps/profile/models.py
2
4
50.0%

Totals

Change from base Build 278:
0.3%

Covered Lines:
970

Relevant Lines:
1053

💛  - Coveralls


How to disable annoying message "the Granted alias has already been added to /Users/myuser/.zshenv"?

I use assume command in my bash script which assuming role every time I need to login to AWS SSO.
In the output of my script I can see the message every time when:
assume --auto-configure-shell my-profile
[✘] the Granted alias has already been added to /Users/myuser/.zshenv

I definitely could redirect the output to /dev/null like that assume --auto-configure-shell my-profile but when users run script for the first time I want to keep output for interaction with user (e.g. setup preferred browser). So redirect to /dev/null doesn't work for me.
Is there any way to skip this message in my output?

@ls-amet-umierov adding export GRANTED_ALIAS_CONFIGURED="true" should do the trick. Let me know if that works for you!


[OLINGO-1377] add condition for parsing "floating" value of Scale facet type

https://issues.apache.org/jira/browse/OLINGO-1377
I did not see any tests for "variable" value so I am not sure if/where I need to add tests for "floating"

Hi @mibo, can you help review my pull request. They have been there for some time now
Thanks
Devansh

Hi @devanshsoni9 , yes I promise that I will review it in the next days.

Thanks @mibo 👍

Thanks for merging this @mibo.
I wanted to know when is the next release of olingo to determine if I should wait for it or build the jar  locally and integrate that into my code base.

Hi @mibo
It would be great if you can answer my question about the next release date.
Thanks
Devansh

Thanks @mibo


Sunpy_Spectrogram Error in a simple code

From @gmlaghari on March 1, 2016 9:47
Below is my code and I am getting an error on Sunpy 0.6.1
import matplotlib.pyplot as plt
%matplotlib
import sunpy.spectra
from sunpy.spectra.sources.callisto import CallistoSpectrogram
image = CallistoSpectrogram.read('/home/ghulam/caldata/MUPK_20150822_064500_59.fit')
image.peek()

Using matplotlib backend: Qt4Agg

---------------------------------------------------------------------------
UnicodeDecodeError                        Traceback (most recent call last)
<ipython-input-4-9113c813a1c3> in <module>()
      4 from sunpy.spectra.sources.callisto import CallistoSpectrogram
      5 image = CallistoSpectrogram.read('/home/ghulam/caldata/MUPK_20150822_064500_59.fit')
----> 6 image.peek()

/home/ghulam/anaconda2/lib/python2.7/site-packages/sunpy/spectra/spectrogram.py in peek(self, *args, **kwargs)
    435         """
    436         figure()
--> 437         ret = self.plot(*args, **kwargs)
    438         plt.show()
    439         return ret

/home/ghulam/anaconda2/lib/python2.7/site-packages/sunpy/spectra/spectrogram.py in plot(self, figure, overlays, colorbar, vmin, vmax, linear, showz, yres, max_dist, **matplotlib_args)
    563                 get_day(self.start).strftime("%d %b %Y"),
    564                 'Radio flux density',
--> 565    566             ])
    567         )

UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 3: ordinal not in range(128)
              '(' + ', '.join(self.instruments) + ')',

Please guide. The plot doesn't show colorbar as well.
Copied from original issue: sunpy/sunpy#1687

From @gmlaghari on March 3, 2016 6:39
How do I know whether you will have fixed this bug or not?

From @Cadair on March 3, 2016 9:40
hey @gmlaghari is it possible you can provide the file you are using so we can recreate the error?

From @gmlaghari on March 3, 2016 9:57
@Cadair Fits file is attached please.
MUPK_20150822_064500_59.fit.zip

From @Cadair on March 3, 2016 10:2
@gmlaghari I will try and look at it, but I am rather busy at the moment, so I can't promise when.

From @gmlaghari on March 3, 2016 10:7
@Cadair Try it when you get time. I am stuck here little here. Although SunPy is giving error, but plotting spectrogram without colorbar.
Your effort is highly appreciated.

From @gmlaghari on March 8, 2016 4:59
@Cadair Any progress? I am getting same error even on older version.

From @agneet42 on March 30, 2017 12:48
@Cadair with Python3 and Matplotlib 2.0, I get this image with the given fits file.

Does this still count as an error?

From @gmlaghari on July 28, 2016 7:47
@Cadair How to add colorbar in Sunpy spectrogram map?

From @agneet42 on March 30, 2017 12:59
If the default encoding of Python is utf8, I guess this error won't come across?

From @Cadair on March 30, 2017 12:51
looks like this could be a python 2 specific unicode error from the original traceback.

Deleted Spectrogram class and started again.


Windows: One of the first two slashes gets stripped, and fails builds

When running bazel test //tests:test_all on Windows with bash, one of the slashes gets stripped, and Bazel actually tries to run bazel test /tests:test_all (which fails).
Split from #2

It's worth noting that I seem to be able to reproduce this manually from an MSYS32 CLI but not from a Windows DOS CLI. The error produced in the Win CLI is unrelated but indicates that target parsing did occur (hence why it failed processing @bullet).

Any update on a fix? This is a real annoyance running bazel on windows with git bash.

See https://bazel.build/configure/windows#running-bazel-shells and the linked Stack Overflow answer. (This just bit me too!)

Closing this issue because this repository is about to be archived.


jobs top returns no results for one player

While it is rare that only one player would be earning money in jobs, testing the plugin on 4.8.0 and 1.13.1 (Paper), it makes it hard to tell if the command is working when no results are returned.  If there is a record, it should be returned regardless how many there are.
/jobs top (in-game and server console)
[17:22:38 INFO]: Usage: /Jobs top [jobname]
[17:22:38 INFO]: * Shows top 15 players by jobs name.

@Zrips - any update on this issue?  Thanks, Steve

Hmmm, that one works with only one player in list. After next official update, try to retest it and if issue still there for you, reopen ticket and we will have second look.

will do - thanks!


spirv-fuzz: Segmentation fault in FuzzerPassAddLocalVariables.

This can be reproduced on 25ede1ce with this compute shader, seed 488607 and empty donor file.
clspv generates an OpSpecConstant instruction and uses it to specify the size for the OpTypeArray instruction. The problem is that ConstantManager::GetConstantFromInst returns nullptr for OpSpecConstant here https://github.com/KhronosGroup/SPIRV-Tools/blob/60104cd97446877dad8ed1010a635218937a2f18/source/opt/constants.cpp#L304-L320
which is later used without any assertions in
https://github.com/KhronosGroup/SPIRV-Tools/blob/60104cd97446877dad8ed1010a635218937a2f18/source/fuzz/fuzzer_util.cpp#L321-L325

@Vasniktel Similar to the other issue I commented on: I haven't seen this crop up when doing recent fuzzing runs; I reckon the problem has been fixed in the meantime.
Would you be happy to close it?

The problem has been fixed.


Per test code coverage in sonar is missing

maven supports sending per test code coverage to sonar. Gradle doesn't seem to. It would be nice to add this to the build somehow.

sonarqube.com removed support for groovy so this is closed.


WIP: Gracefully handle nothing to do

It can be ok to have 0 deep samples, or a 0 sized data window, meaning nothing to decode in general.
Will address OSS-Fuzz 71692, 71706, 71707

going to change how this works after chatting w/ PH


Added OpenBSD support, using aucat(1)

There's aucat(1) in base, which allows to play WAV files, similar to aplay.
P.S. Thank you for a very useful program;)

Hey, thanks for the PR! Have you tested this? I'll have to trust you because I guess there's no way to test it via GitHub Actions.

I tested it on the last OpenBSDd release (6.9), both in python interpreter and from shell. Everything works!


Add middleware for Model.update()

I was wondering if it is possible to add .pre and .post middleware for update.  I remember vaguely from and IRC discussion that this is currently not available.  @aheckmann said that Model.update call mongodb driver directly. Is there some technical limitation to adding this feature?

Model.update never returns documents to the client. It is simply a command that runs directly on MongoDB. With no documents returned, no hooks can run.

I was thinking more along the lines of a .pre hook.  Could you not have that before it is sent off to mongo-db-native?  I could make my own I guess but it would be nice to have this in conjunction with the save and remove hooks.

i don't think hooking update works right now b/c of the way our inheritance works combined with how hooks works.


SSR + Vuex + JWT

I'm having some hard time getting this to work, and I'd love to see how you guys would do this.
Currently I'm using Vuejs + Vuex + Axios for async HTTP calls. Everything I've done is based on this template, but I don't see any info on how to to the following.
My Vuex actions look like this:
src/store/actions/dashboard/properties.js
import { fetchUserProperties, fetchUserProperty } from '@/src/api/dashboard/properties'

let FETCH_USER_PROPERTIES = ({commit, state}, data) => {

	return fetchUserProperties(data)
	.then((result) => {
		console.log("FETCH_USER_PROPERTIES",result)
		commit('SET_USER_PROPERTIES', result)
	})
	.catch((error) => {
		console.log("error", error)
	})
}

src/api/dashboard/properties
import axios from '@/src/api/axios'

let fetchUserProperties = () => {

	return new Promise((resolve, reject) => {

		axios.get(`/profile/properties`)
		.then((result) => {
			resolve(result.data)
		})
		.catch((error) => {
			reject(error)
		})

	});
}

src/api/axios
import axios from 'axios';
import config from '@/config/config'
import https from 'https'

var instance = axios.create(args);

export let initializeApi = (store, router) => {

	// Set base URL
	instance.defaults.baseURL = config.API_URL

  instance.interceptors.response.use(responseSuccess, (error) => {
    if (error.response.status === 401) {

      store.commit('REMOVE_USER_AND_TOKEN')

      router.push('/login')
    }

    return Promise.reject(error)
  })

  // Auth
	instance.interceptors.request.use((requestConfig) => {

    let token = store.state.auth.token
   	if (token) {
      	requestConfig.headers.Authorization = `Bearer ${token}`
  	}

  	return requestConfig
  });

}

export let updateToken = (token) => {
  instance.interceptors.request.use((requestConfig) => {

    if (token) {
        requestConfig.headers.Authorization = `Bearer ${token}`
    }

    return requestConfig
  });
}

export default instance;

How does this work? Basically, both in entry-server.js and entry-client.js I make a call to this initializeApi function with value of the store.
entry-client.js
import Vue from 'vue'
import { app, router, store } from './client-create-app'
import { initializeApi } from '@/src/api/axios'

// Initialize api
initializeApi(store, router)

// wait until router has resolved all async before hooks
// and async components...
router.onReady(() => {

  // Add router hook for handling asyncData.
  // Doing it after initial route is resolved so that we don't double-fetch
  // the data that we already have. Using router.beforeResolve() so that all
  // async components are resolved.
  router.beforeResolve((to, from, next) => {
    const matched = router.getMatchedComponents(to)
    const prevMatched = router.getMatchedComponents(from)
    let diffed = false
    const activated = matched.filter((c, i) => {
      return diffed || (diffed = (prevMatched[i] !== c))
    })
    const asyncDataHooks = activated.map(c => c.asyncData).filter(_ => _)
    if (!asyncDataHooks.length) {
      return next()
    }

    bar.start()

    Promise.all(asyncDataHooks.map(hook => hook({ store, route: to, router })))
      .then(() => {
        bar.finish()
        next()
      })
      .catch(next)
  })

  // actually mount to DOM
  app.$mount('#app')
})

// service worker
if ('https:' === location.protocol && navigator.serviceWorker) {
  navigator.serviceWorker.register('/service-worker.js')
}

entry-server.js
import { createApp } from './app'
import { initializeApi } from '@/src/api/axios'

const isDev = process.env.NODE_ENV !== 'production'

// This exported function will be called by `bundleRenderer`.
// This is where we perform data-prefetching to determine the
// state of our application before actually rendering it.
// Since data fetching is async, this function is expected to
// return a Promise that resolves to the app instance.
export default context => {
  return new Promise((resolve, reject) => {
    const s = isDev && Date.now()
    const { app, router, store } = createApp()

    const { url } = context
    const route = router.resolve(url).route
    const { fullPath } = route

    if (fullPath !== url) {
      return reject({ url: fullPath })
    }

    if(context.cookies.token) {
      store.state.auth.token = context.cookies.token
    }

    if(context.cookies.user) {
      store.state.user = JSON.parse(decodeURIComponent(context.cookies.user))
    }

    // Initialize API
    initializeApi(store, router)
    // initializeApiV2(store, router)

    // set router's location
    if (route.matched[0].meta.requiresAuth && !context.cookies.token) {
      router.replace('/login')
    }else{
      // set router's location
      router.push(url)
    }

    // wait until router has resolved possible async hooks
    router.onReady(() => {
      const matchedComponents = router.getMatchedComponents()

      // no matched routes
      if (!matchedComponents.length) {
        return reject({ code: 404 })
      }
      // Call fetchData hooks on components matched by the route.
      // A preFetch hook dispatches a store action and returns a Promise,
      // which is resolved when the action is complete and store state has been
      // updated.
      Promise.all(matchedComponents.map(({ asyncData }) => asyncData && asyncData({
        store,
        route: router.currentRoute,
        router: router
      }))).then(() => {
        isDev && console.log(`data pre-fetch: ${Date.now() - s}ms`)
        // After all preFetch hooks are resolved, our store is now
        // filled with the state needed to render the app.
        // Expose the state on the render context, and let the request handler
        // inline the state in the HTML response. This allows the client-side
        // store to pick-up the server-side state without having to duplicate
        // the initial data fetching on the client.
        context.state = store.state
        context.meta = app.$meta()
        resolve(app)
      }).catch(reject)
    }, reject)
  })
}

So I thought this looks and works beautifully. Now all by Axios request get the Authorization header appended and everything is good.
However after hours of debugging I found this:
https://medium.com/@iaincollins/how-not-to-create-a-singleton-in-node-js-bd7fde5361f5
Which means that on the server (NodeJS), my /src/api/axios.js file is getting cached by node.
So that when I require the axios instance in my API files, sometimes it returns an axios instance created by another user, along with the old user interceptors and token. Very bad.
How are you guys handling this case where all HTTP request from the app need to have an Authorization header attached?
I'd love to see how @yyx990803 would do this. Would be nice to have it added to this example too.
Please let me know if you need any more information.

FYI var instance = axios.create(args); in src/api/axios means there will be only one axios instance all through the app.

Not true.
Watch this, I added a few debugging lines.
src/api/axios.js
var instance = axios.create(args);
instance.longandobviuslynotoverwrittenarg = new Date().toUTCString();

src/api/dashboard/properties
import axios from '@/src/api/axios'

let fetchUserProperties = () => {

	console.log("axios:instance", axios.longandobviuslynotoverwrittenarg)
	console.log("axios:instance.request", new Date().toUTCString())

	return new Promise((resolve, reject) => {

		axios.get(`/profile/properties`)
		.then((result) => {
			resolve(result.data)
		})
		.catch((error) => {
			reject(error)
		})

	});
}

And these are the logs I get by refreshing the page.
First request:

Second request:

This also makes some sense after reading:
https://medium.com/@iaincollins/how-not-to-create-a-singleton-in-node-js-bd7fde5361f5
That means that when import a module in node and exporting an object NodeJS reserves itself the rigth to cache that object. So that you can have any guarantee that a new axios instance is created on each new request.

I've said that you're sharing only one axios instance on server, that's why axios.longandobviuslynotoverwrittenarg is always same. You need to wrap axios.create(args) into a function to create another instance for all requests, for example:
// entry-server.js
import axios from 'axios'

export default () => new Promise((resolve, reject) => {
  const instance = axios.create();

  // add interceptors on instance...

I have no idea how to go about this.
Nor how I can add the token to this axios instance from entry-server.js...
Do you know any resources online?
Could you share your own snippet?

PD: I also don't understand why you would add a Promise in there.

It is entry-server.js, so it should return a promise.
You can check https://github.com/JounQin/vue-ssr/blob/master/src/entry-server.js#L13, add axios instance into context to attach it on server via this.$http:
import Vue from 'vue'
import axios from 'axios'

Object.defineProperty(
  Vue.prototype.proto,
  '$http',
  __SERVER__
    ? {
        get() {
          return this.$ssrContext.axios // this.$http will be new for every request
        },
        configurable: __DEV__,
      }
    : {
        value: axios,
        writable: __DEV__,
      },
)

Thanks a lot Sir, I eneded up with this based on your repo.
/src/api/axios
import axios from 'axios';
import config from '@/config/config'
import https from 'https'

const createInstance = (store) => {

	let token = store.state.auth.token

	let instance = axios.create({
		'baseURL': config.API_URL,
		'headers': {
			'Authorization': `Bearer ${token}`
		}
	})

	instance.interceptors.response.use(
		(success) => {
			return success
		},
		(error) => {
	    	if (error.response.status === 401) {
				store.commit('REMOVE_USER_AND_TOKEN')
				router.push('/login')
	    	}
    		return Promise.reject(error)
  		})

	return instance
}

export { createInstance }

src/entry-server.js
import { createApp } from './app'
import { createInstance } from '@/src/api/axios'

const isDev = process.env.NODE_ENV !== 'production'

// This exported function will be called by `bundleRenderer`.
// This is where we perform data-prefetching to determine the
// state of our application before actually rendering it.
// Since data fetching is async, this function is expected to
// return a Promise that resolves to the app instance.
export default context => {
  return new Promise((resolve, reject) => {
    const s = isDev && Date.now()
    const { app, router, store } = createApp()

    const { url } = context
    const route = router.resolve(url).route
    const { fullPath } = route

    if (fullPath !== url) {
      return reject({ url: fullPath })
    }

    const token = context.cookies.token
    if(token) {
      store.state.auth.token = token
    }

    if(context.cookies.user) {
      store.state.user = JSON.parse(decodeURIComponent(context.cookies.user))
    }

    store.commit("SET_AXIOS", createInstance(store))

    /* Initialize API
    let instance = initializeApi(store, router)
    store.state.$axios = instance
    context.$axios = instance
    */
    // initializeApiV2(store, router)

    // set router's location
    if (route.matched[0].meta.requiresAuth && !context.cookies.token) {
      router.replace('/login')
    }else{
      // set router's location
      router.push(url)
    }

    // wait until router has resolved possible async hooks
    router.onReady(() => {
      const matchedComponents = router.getMatchedComponents()

      // no matched routes
      if (!matchedComponents.length) {
        return reject({ code: 404 })
      }
      // Call fetchData hooks on components matched by the route.
      // A preFetch hook dispatches a store action and returns a Promise,
      // which is resolved when the action is complete and store state has been
      // updated.
      Promise.all(matchedComponents.map(({ asyncData }) => asyncData && asyncData({
        store,
        route: router.currentRoute,
        router: router
      }))).then(() => {
        isDev && console.log(`data pre-fetch: ${Date.now() - s}ms`)
        // After all preFetch hooks are resolved, our store is now
        // filled with the state needed to render the app.
        // Expose the state on the render context, and let the request handler
        // inline the state in the HTML response. This allows the client-side
        // store to pick-up the server-side state without having to duplicate
        // the initial data fetching on the client.
        context.state = store.state
        context.meta = app.$meta()
        resolve(app)
      }).catch(reject)
    }, reject)
  })
}

src/entry-client.js
import Vue from 'vue'
import 'es6-promise/auto'
import { app, router, store } from './client-create-app'
import { createInstance } from '@/src/api/axios'
import ProgressBar from './components/ProgressBar.vue'

// global progress bar
const bar = Vue.prototype.$bar = new Vue(ProgressBar).$mount()
document.body.appendChild(bar.$el)

// a global mixin that calls `asyncData` when a route component's params change
Vue.mixin({
  beforeRouteUpdate (to, from, next) {
    const { asyncData } = this.$options
    console.log("beforeRouteUpdate", router)
    if (asyncData) {
      asyncData({
        store: this.$store,
        route: to,
        router: router
      }).then(next).catch(next)
    } else {
      next()
    }
  }
})

// Initialize api
store.commit("SET_AXIOS", createInstance(store))

// wait until router has resolved all async before hooks
// and async components...
router.onReady(() => {

  // Add router hook for handling asyncData.
  // Doing it after initial route is resolved so that we don't double-fetch
  // the data that we already have. Using router.beforeResolve() so that all
  // async components are resolved.
  router.beforeResolve((to, from, next) => {
    const matched = router.getMatchedComponents(to)
    const prevMatched = router.getMatchedComponents(from)
    let diffed = false
    const activated = matched.filter((c, i) => {
      return diffed || (diffed = (prevMatched[i] !== c))
    })
    const asyncDataHooks = activated.map(c => c.asyncData).filter(_ => _)
    if (!asyncDataHooks.length) {
      return next()
    }

    bar.start()

    Promise.all(asyncDataHooks.map(hook => hook({ store, route: to, router })))
      .then(() => {
        bar.finish()
        next()
      })
      .catch(next)
  })

  // actually mount to DOM
  app.$mount('#app')
})

// service worker
if ('https:' === location.protocol && navigator.serviceWorker) {
  navigator.serviceWorker.register('/service-worker.js')
}

Works fine. Thanks again

So please close issue. 🙂


Settings - Backup: Update the design

https://xd.adobe.com/spec/8f259bcd-550e-4f0c-40bb-bdce2ed36fe5-f914/screen/cc6919d9-22e3-4959-9478-f8a80fb3b550/Settings-Back-Up-your-wallet
Main changes:

Changed the text boxes size
Added a text button "copy all to clipboard"

The screen look as per design.


Version 1.5 of C# and Python code

You can change Python code back into v2.0.5 in 'HilbertsCurve_Python' folder, but I have translated this project to C#

Hi @RusMermaid , this looks like a cool project, but I don't think this repo is the right place for it. I would encourage you to start a new repo and just mention that your C# implementation is based on this one

Hi @RusMermaid , this looks like a cool project, but I don't think this repo is the right place for it. I would encourage you to start a new repo and just mention that your C# implementation is based on this one

https://github.com/RusMermaid/Hilberts_Curve_CS Is the project

Hi @RusMermaid , this looks like a cool project, but I don't think this repo is the right place for it. I would encourage you to start a new repo and just mention that your C# implementation is based on this one

I’d prefer to merge our projects

sorry, but I'd prefer they remain separate.


Wrong paper cited at CHANGELOG?

I'm trying to learn about the algorithm used for bootstrapping the CKKS at Lattigo and found a reference to the original BFV paper on the most recent changelog for version 2.0.0. Is that write and Lattigo's CKKS uses BFV's bootstrap algorithm? Or maybe I miss understood the citation?

Hello, you are right, there was a mistake. I corrected it (https://eprint.iacr.org/2020/1203). Thank you very much


Failing all API calls in domain services when the db connection failed in admin ds

Description:

When invoking the API resources in domain services it get the following error
{
    "code": 900900,
    "message": "Error while retrieving organization by name",
    "description": "Error while retrieving organization by name",
    "moreInfo": {}
}

This happens because of the following issue in the admin domain service. This can happen due to the DB pod  atgetting late to ready.
Using Java memory options: -Xms256m -Xmx1024m
time = 2023-03-17T17:02:10.126Z level = ERROR module = wso2/apk_common_lib message = "Error while connecting to database"
time = 2023-03-17T17:02:11.963Z level = INFO module = wso2/admin_service message = "Starting APK Admin Domain Service..."
time = 2023-03-17T17:02:12.008Z level = ERROR module = wso2/admin_service message = "Error while connecting to database"
error: Error while retrieving connection {"code":909000,"message":"Error while retrieving connection","statusCode":"500","description":"Error while retrieving connection","moreInfo":{}}
	at wso2.admin_service.0:getAllOrganizationDAO(organizationDAO.bal:134)
	   wso2.admin_service.0:getAllOrganization(organizationImpl.bal:79)
	   wso2.admin_service.0.$anonType$_2:$get$organizations(internal-admin-api_service.bal:38)
cause: Error in SQL connector configuration: Failed to initialize pool: FATAL: the database system is shutting down Caused by :FATAL: the database system is shutting down
	at ballerinax.postgresql.1:createClient(client.bal:209)
	   ballerinax.postgresql.1.Client:init(client.bal:50)
	   wso2.admin_service.0:init(init.bal:46)

Closing the issues since this is fixed from https://github.com/wso2/apk/pull/259


Remove resize handles from autosize text areas

Fixes #7210, replacing #9651 as per https://github.com/wagtail/wagtail/issues/7210#issuecomment-1325707942. AdminAutoHeightTextInput now inserts a w-field__autosize classname which explicitly disables the resizing handle, leaving resizing fully in control of the jquery.autosize plugin.

Since I do have a strong opinion that #9651 is an incorrect fix and that this PR restores the intended behaviour from when jquery.autosize.js was first added, I will take the above comment and https://github.com/wagtail/wagtail/issues/7210#issuecomment-1327199014 as approval to merge - @thibaudcolas , please shout if that's not the case :-)

Merged in 99eaef6ee67b74060ddf5c742c19fe0ffacbb043


add option to prevent reloading non play modules

Currently all modules in the build reactor are reloaded in development mode. This PR adds an option to exclude non play modules from reloading, so that java modules are not affected with new Classloaders. The default setting is kept backward compatible.

Hi @rafique
Not all modules are reloaded, but only the ones that are dependencies of the application being run. You can modify them and see the results in Play! application after reload.

Hi @gslowikowski
Thanks for taking time to review the PR.
I agree with you that current behavior of reloading dependent modules are usually convenient for most cases. But there are some cases where you might want to exclude some modules from reloading. For example, java/jar modules with Spring (Boot) beans or JPA entities are too heavy to reload on every code changes, takes a long time to load the application for a medium to large application. It's better to exclude those "jar" modules while working on the front end application, that's exactly what this PR does; it adds a configuration option to the play maven plugin to hot reload only the "play2" modules ignoring other java/jar modules.


Model B+ supported?

I've seen issues and troubleshooting posts referring to getting MM running on a Model B+, so I'm not sure if it is officially supported.
The automated installer fails with this message:
Sorry, your Raspberry Pi is not supported.
Please run MagicMirror on a Raspberry Pi 2 or 3.
If this is a Pi Zero, you are in the same boat as the original Raspberry Pi.
You must run in server only mode.
According to cat /proc/cpuinfo, my Pi is a Model B+:
Hardware        : BCM2835
Revision        : 0010
But I'm not sure if that places it in the Pi 1 or 2/3 spectrum.
I'm running the full Raspbian Jessie (Pixel) image from 2017-04-10, so I do not know if I need to downgrade to Jessie Lite, and add the X11 components later.

@dpapathanasiou The difference is mostly hardware changes, like more USB ports and better board arrangement. Unfortunately, that does place you within the same spectrum as the original Raspberry Pi.

@dpapathanasiou What output show you the command?
uname -a
The issue is  if the electron is available for the architecture of your device. If not only the only way is run as serveronly option
You can follow and try the instructions in the installer script. If it work for you  send a PullRequest to fix this.

@roramirez, Can you please explain more about the server mode?
I'm not sure if I got this right, correct me if I'm wrong.
As I'm understanding to make MagicMirror run in the RaspberryPi 1 (My model is the same as @dpapathanasiou) I will have to run it in server mode, because the Electron App is not available to this RPi model architecture. @MichMich writes that installations on the RPi 1 must be run in a Full Screen browser. And here is where I get a little confused (mostly because I don't know Electron). @MichMich reference to the Full Screen Browser is the Chromium or any other browser available in the LXDE Desktop Enviroment (or Pixel), right? And I will open the localhost server of the Magic Mirror server on the browser, correct? All I have to do is then autostart the browser in fullscreen to have the MagicMirror magic.
My "uname -a"  Linux magicmirror 4.9.24+ #993 Wed Apr 26 17:56:54 BST 2017 armv6l GNU/Linux
Thanks,
Deco Martins

The guide you are referring to is talking about version 1. (As stated above the guide). This is version 2 which focusses on RPi 3 but might work on the Pi2 B+. If you need help getting it up and running (for example using the server only mode), please check out http://forum.magicmirror.builders for support and troubleshooting.
I'm closing this issue for now. If you feel this issue should remain open, please let me know.

so that not working. you must use Raspberry Pi 3 Model B+ and Raspberry Pi 3 Model B working great.

I also have a B+. Now the board is getting more and more expensive. I really hope this old stuff can be good used in Magic Mirror.


Design List Block

A “List” is simply a variable model with type “list.” So most of the behavior is similar to the variable design here: https://github.com/LLK/scratch-blocks/issues/372.

Clicking on the list block (it's a reporter) evaluates it and pops up the current value.

Right clicking brings up a context menu that includes the names of all of the other lists, delete, and rename.

A block with a list field (usually “add to”, “delete of”, etc) shows the name of the list and a dropdown arrow.

Clicking on the dropdown arrow shows a dropdown with the names of all the other lists.

Making a new list in Scratch is done with the "Make a List" button in the Data category.

Renaming a list in Scratch can be done by right-clicking on a reporter in the toolbox, but not by right clicking on a reporter in the workspace or by right-clicking on a setter anywhere.

Deletion will behave as variable deletion does. Variable deletion is being decided upon in https://github.com/LLK/scratch-blocks/issues/975

Scratch 2.0 only lets you delete/rename variables from the context menu when right clicking the reporter. Do we want to allow them to also delete/rename variable in the dropdowns as well?

Clicking on the list block (it's a reporter) evaluates it and pops up the current value.

A quick note on this, though technically it's more relevant to the VM (and may already be implemented)..

Scratch reports lists as strings.

If a list contains any items with two or more characters, or any items with zero characters, the items are separated by strings. E.g. [foo, bar, kaz] -> "foo bar kaz"

If a list only contains items with one character, the items are joined together without any space separations. E.g. [a, b, c, 1, 2, 3] -> "abc123"

Just so that there's no confusion when implementing the block and looking at its results!

@liam4 You are correct on the single character concatenation quirk. They will need to keep this in order to stop a few cloud projects from breaking.

@ateesdalejr I've also used it many times for substring procedures:

Looking at this with @ericrosenbaum, we're not seeing how to rename a list in Scratch 2.0. We also got a request from a Scratcher in a workshop (10/16/17) to be able to rename a list in Scratch 3.0, so we wanted to make a note of that request for consideration here.


import openaps install scripts from docs

This will need a corresponding update to the docs.

I see no reason not to go ahead and merge this?


Add a type-specific Spliterator that wraps iterators

This allows up to have a default implementation of spliterator that does
not rely on widened iterators. This means that the horrible hack of the
ImplementsSpliterator interface is no longer needed, and has been
excised.
The cost for this is yet more classes in Spliterators and no longer
getting potential future performance benefits from the JDK's version of
this method (though that is rather unlikely; there is only so much you
can do wrapping an Iterator)

DO NOT SUBMIT This pull request is just to make a diff


Implemented option to opt into Todoist Beta

Implements the feature I've requested in #68. Works by using a ternary operator to switch between index.html and beta.html based on the boolean value of beta in .todoist-linix.json. beta.html is nearly identical to index.html except for a change in the Todoist iframe URL from todoist.com/app to beta.todoist.com/app.

Perfect! Thanks a lot @ceiphr for this pull request and for keeping that unusual formatting in place ;)
I'll make the release pretty soon today

@ceiphr github's file uploader is pretty slow today (for me at least). I'll try to make the release tomorrow. Meanwhile you can pull the latest master and use the app from there.

No worries, I was going to make another PR anyway. Thank you for the update.


NETOBSERV-289 Sort by Date & time by default

This PR will sort table by ColumnsId.endtime if available.

Sorting is also reset when selected columns are updated.

just tested, I'm not sure if it's what we want exactly:

Columns are sorted by time as required, but...
If you sort with another column (it works), then you refresh, sorting is back to time. I guess it should keep whatever the user chosed?

Ah I see it's actually managed via #149

Ah I see it's actually managed via #149 ... Let me test that one then

let's merge https://github.com/netobserv/network-observability-console-plugin/pull/149 and close this one. Thanks :+1:


LinearGradient has a error.

Trying to use a repo from GitHub but I get " The color parameter is not defined " ,Checking the  flutter src , there is a color par.
import 'package:flutter/material.dart';

class Palette {
  static const Color scaffold = Color(0xFFF0F2F5);

  static const Color facebookBlue = Color(0xFF1777F2);

  static const LinearGradient createRoomGradient = LinearGradient(
    colors: [Color(0xFF496AE1), Color(0xFFCE48B1)],
  );

  static const Color online = Color(0xFF4BCB1F);

  static const LinearGradient storyGradient = LinearGradient(
    begin: Alignment.topCenter,
    end: Alignment.bottomCenter,
    colors: [Colors.transparent, Colors.black26],
  );
}

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hi @DanielMohammadii
I have not any problem

you can see the screenshot of vs code.
I am using flutter 1.22 (stable channel)
Thanks.

I was NOT able to reproduce this issue on latest master.

Logs
flutter run -v
run.log
Screenshot

flutter doctor -v
[√] Flutter (Channel master, 1.23.0-8.0.pre.111, on Microsoft Windows [Version
    10.0.19041.508], locale en-US)
    • Flutter version 1.23.0-8.0.pre.111 at C:\Users\Aneesh\Documents\development\flutter    • Framework revision fc85492d7c (15 hours ago), 2020-10-02 11:42:02 -0700
    • Engine revision 87a10f240f
    • Dart version 2.11.0 (build 2.11.0-181.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\Aneesh\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.49.2)
    • VS Code at C:\Users\Aneesh\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.15.0

[√] Connected device (3 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 85.0.4183.121
    • Edge (web)       • edge       • web-javascript • Microsoft Edge 85.0.564.63

• No issues found!

Reproducible code sample
import 'package:flutter/material.dart';

main() => runApp(
      MaterialApp(
        home: MyHomePage(),
      ),
    );

class MyHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Container(decoration: BoxDecoration(
        gradient: Palette.createRoomGradient,
      ),
      ),
    );
  }
}

class Palette {
  static const Color scaffold = Color(0xFFF0F2F5);

  static const Color facebookBlue = Color(0xFF1777F2);

  static const LinearGradient createRoomGradient = LinearGradient(
    colors: [Color(0xFF496AE1), Color(0xFFCE48B1)],
  );

  static const Color online = Color(0xFF4BCB1F);

  static const LinearGradient storyGradient = LinearGradient(
    begin: Alignment.topCenter,
    end: Alignment.bottomCenter,
    colors: [Colors.transparent, Colors.red],
  );
}

Came here for the same issue. Seems somehow IDE related. I am using Android Studio and disabling and enabling again the Dart plugin apparently fixed the issue.

@andreitere  Thank you! Andrei. So I guess the problem is the channel. Cuz for this project, I'm using Beta.Lemm check

When upgrading your Flutter version, make sure to restart your IDE or analysis server.
You shouldn't need to outright disable the Android Studio/IntelliJ Dart plugin, simply pressing the restart button in the analysis server tab should work.
See #63922

I think this may be the same issue described in https://github.com/dart-lang/sdk/issues/43532. You may need to fetch packages and then restart the editor. If the packages have been fetched prior to the analysis server starting, then this should not occur.

I changed the Flutter channel  Stable and upgrade again. now it's working
Flutter channel stable
Flutter upgrade

@DanielMohammadii
You may try the solution as mentioned here and see if it works for you if you want to try and replicate the issue on beta, where you were getting the issue originally.
Also check this comment for reference.
I am going ahead and closing this issue for now. If you again encounter this issue on beta or think this should be kept open, please write in comments and I'll reopen.
Thanks.


Added D to V

Please review, mainly the tech and tags.
Some are trivial, one library per section should be enough to check.

Hmm sorry about it, delay in the previous merge caused this.
Actually I tried to reach you regarding those tags in the previous PR thread, but it looks like you did not notice.
I will also look thoroughly. Most of them are trivial tags except "graphics-game" ones and may be some others.

image processing vs computer-vision: I referred to this https://cs.stackexchange.com/a/7087

In general my mistake was to try to use tech and tags from "technologies.json" as far as I can :)

I will give another pass, meanwhile could you look at image processing vs computer-vision.
Thank you

Will do. re. images vs computer-vision. I think part of it is what would people want to look on their profile. "computer vision" probably sounds cooler than "image processing" for some. But maybe not. I will review and let you know. Thank you!

Fixed some more things, looks okay I guess.
If you have finalised, could you merge it so that I can do another PR.
Thank you

@gmrhub : I just discovered that this is not valid JSON. Line 597 does not have a comma. I recommend you run it through a JSON parser such as jq before a commit.

Sure, thank you.

but please fix this asap :)

oops, sorry I didn't notice. Doing now.


Add support for arrays in records

Record items can currently only use simple types like int, float, etc.
The macro should be named THINGSET_RECORD_ITEM_ARRAY.

Fixed in c8ca352c147a8f57a684b14b5180b5555ae251f5


Have video tutorial ?

Vide tutorial install libhoudini-paket

Yeah, I'm also very confused as to how we go about building the kernel and where we can find device/generic/common.


Remove one of two persistence locations for external-node

🌟 Feature Request
Use just PG as persistence layer for external node
📝 Description
I'd like that all zksync state was stored on PG. Instead of having Filesystem+ PG.
Provide a clear and concise description of the feature you'd like to see.
I'd like that all zksync state was stored on PG. Instead of having Filesystem+ PG.
🤔 Rationale
Having a backup of PG is not enough. FS+PG consistency is not resilient as if you rollback in PG and filesystem as a newer blocks it will break and require full filesystem sync.
There should be only one persistence layer.
Explain why this feature is important and how it benefits the project.
Having a backup of PG is not enough to guarantee state.
Did PITR in PG and broke the consistency between FS+PG which required me to resync entirely the Filesystem, which takes days.
📋 Additional Context
Add any other context or information about the feature request here.

RocksDB is used in performance-critical places (like state keeper cache and merkle tree), using them with postgres will be too slow.
At the same time, Postgres is a source of truth (e.g. RocksDB acts like a cache, so even at loss of RocksDB data, the server will be able to recover it; this will take a while, though).
So, both RocksDB and Postgres are used intentionally and I don't think it'll be feasible to get rid of any of them, at least for now.


Markdown is not auto scrolling.

VSCode Version: Code 1.9.0 (27240e71ef390bf2d66307e677c2a333cebf75af, 2017-02-02T08:31:00.827Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

Steps to Reproduce:

Open Markdown file
Open preview to side
Scroll in markdown window (preview does not scroll) :(

@idvorkin This reproes for me as well. It seems to happen only when the file is opened from the file system directly and not from a folder currently loaded in the file explorer. For instance, from the picture below,

README.md  opened directly as file, will not auto scroll.
generators.md opened from the docs folder which is loaded in the file explorer, auto scrolls fine.
Do you see the same behavior? Probably a path resolution issue.

@fabiorocha Good debugging :) I've got the same behavior.

@idvorkin awesome. What do you think about updating the issue description (step 3)
From:
Scroll in markdown window (preview does not scroll) :(
To:
Scroll in preview window (source does not scroll)
Since it's expected to sync only preview -> source, not the other way around?

I looked briefly at this today and it seems the problem is on vscode\extensions\markdown\src\extension.ts, in the path comparison made in snippet below
context.subscriptions.push(vscode.commands.registerCommand('_markdown.revealLine', (uri, line) => {
  const sourceUri = vscode.Uri.parse(decodeURIComponent(uri));
  vscode.window.visibleTextEditors
    .filter(editor => editor.document.uri.path === sourceUri.path)
    .forEach(editor => {
      const sourceLine = Math.floor(line);
      const text = editor.document.getText(new vscode.Range(sourceLine, 0, sourceLine + 1, 0));
      const fraction = line - Math.floor(line);
      const start = Math.floor(fraction * text.length);
      editor.revealRange(
        new vscode.Range(sourceLine, start, sourceLine + 1, 0),
        vscode.TextEditorRevealType.AtTop);
    });
}));

Note the drive letter:

A simple toUpperCase() on both sides make this work which proves this is the issue. Obviously this isn't a proper fix for OSs that have a case sensitive file system. It also seems that having the lowercase windows drive letter is by design in many places:

So I get a proper fix here would be finding out why editor.document.uri.path doesn't return a normalized path.

I've updated the description, although both directions should work! Thanks for digging in.  By the way, thanks your digging I'm unblocked, and this is a great feature!

Thanks all for the investigation. I've created #20064 which I believe should fix this. As noted, in some Windows scenarios, the  drive letter differs between the preview document and the editor document. Using fsPath should fix this. I'm planning to take the fix into the 1.10 insiders builds and also our next 1.9 recovery build

Thanks for the quick fix @mjbvz! I've looked into this a bit more and the root cause is on the way the original source document's URI is created on \vscode\src\vs\base\common\uri.ts
An else if on "public static file(path: string): URI" would help you avoid all those || on your case and probably prevent other future bugs too.
else if (URI._upperCaseDrive.test(path)) {
// windows drive letter: file:///c:/far/boo
ret._path = path[0].toLowerCase() + path.substr(1);
}

Thanks @fabiorocha. That be worth looking into in the future, but I don't want to touch functionality that is so central for this fix. After reviewing the fsPath logic, I think using it should be safe and address the problem. Path casing issues have caused us lots of trouble in the past, so this is an area that we certainly need to revisit but one that can also be pretty finicky
b4aac1c cherry-picked this workaround into our 1.9 branch to be picked up in the next recovery build

@mjbvz Totally understandable. Thanks again for the quick fix and for the great feature!


Upgrade to Umbraco 10.0.1

With Umbraco 10 out it makes sense to skip over V9 IMO @Shazwazza

LGTM!


server: make the region heartbeat metric units correct

What have you changed? (required)
In TiKV, we use seconds:
let now = SystemTime::now();
let ts = now.duration_since(UNIX_EPOCH).unwrap().as_secs();
req.set_timestamp(ts);

But in PD, we use milliseconds:
regionHeartbeatLatency.WithLabelValues(storeLabel).Observe(float64(time.Now().UnixNano()/int64(time.Millisecond)) - float64(request.GetTimestamp()))

So the heartbeat latency is wrong now.let the unit correct.
What are the type of the changes (required)?

Bug fix (non-breaking change which fixes an issue)

Refer to a related PR or issue link (optional)
https://github.com/pingcap/pd/issues/1121

Need to update the metric bucket too. Also the tidb-ansible grafana template need to update too.

LGTM. PTAL @Connor1996

Is unit of second enough to distinguish latency?

@Connor1996  we only need to know if the heartbeat latency is increasing, that to judge handle the heartbeat become slower.


Simple Swap Factory bytecode checking

Summary

I'm initialising our test environment Bee Factory for JS tests, which operates with its own blockchain network, so I wanted to migrate the SimpleSwapFactory smart contract to it.
Though the transaction was successful on blockchain side, the Bee responded Error: factory fail: not a valid factory contract.
@ralph-pichler helped me with the info it's because the Bee has bytecode verification, where the bytecode has to be exactly identical as excepted, but the last couple of bytes are ignored (the last 64 surely because of the token address parameter of the contract).
Nevertheless to build this exact bytecode from source code is almost impossible, or you need to use all of your luck that you got for your remaining lifetime. During the compilation some particular metadata also will be attached to the bytecode, which does not effect the resulting usability of the contract but it is not considered under this check. Anyhow I tried to compile with the same source code that has been uploaded to etherscan and with the same solc version v0.6.12+commit.27d51765 with the same parameters (optimizer enable, runs 200) but still I get different bytecode result.
Steps to reproduce

deploy ETH20 minter token
deploy SimpleSwapFactory from source code that has been uploaded to etherscan with the prev generated ERC20 token address
start a Bee node with flag --swap-factory-address=$DEPLOYED_SIMPLE_SWAP_ADDRESS

Expected behavior

Accepts the smart contract since I passed explicitly the contract address.
Actual behavior

The Bee process stops, because of invalid smart contract bytecode.

@ralph-pichler , isn't it documented/automated how we compile and deploy our contract?

@nugaon it works as long as you use the bytecode that was generated by the github ci in https://github.com/ethersphere/go-sw3-abi/tree/master/sw3abi


Potentially Outdated QEMU command in book

TL;DR Launch the VM might have an outdated qemu-system command. I got mine working via:
qemu-system-x86_64 -enable-kvm -drive if=pflash,format=raw,file=OVMF_CODE.fd -drive if=pflash,format=raw,file=OVMF_VARS.fd -drive format=raw,file=fat:rw:esp

There were some knits leading up to this (on gentoo) regarding some libslirp.so dependencies. I can potentially help others resolve this if they're experiencing similar issues.
Back on topic though - it seems the necessary command has readonly-on=on required due to a deprecation, and that readonly is no longer allowed on raw (I guess?)

I tested on a couple versions of qemu and don't see any error, so need some additional info. Can you post the full output of the failing command? Also, what does qemu-system-x86_64 --version show?

Closing for now -- feel free to reopen if you can repro the error.


Added pageinate-links custom tag support & improved compatibility

Allows <paginate-links> custom tag (as is mentioned in issue #46) to support a wider range of UI framework
Click handler could be placed at various layers
Updated README.md with these introductions of this feature
Fixed browser compatibility: many browsers (such as Edge) does not  support forEach() function on NodeList (return value of  querySelectAll()).

Ah, just ran into this issue with forEach() on NodeList. Was trying to use polyfill.io but even they don't support it since it's not actually in spec. Would be great if this can be merged in. Thanks for the work @chazeon


NXOS bootstrap program must check for virtual system to guardrail OS upgrade

The nxos-bootstrap program does not guardrail against attempting to OS install on a vNXOS system.  Need to add a check / report / fail for this scenario.

@jeremyschulman can we expand os-selector.cfg to prevent this somehow?  Eg, disabled=True, with an explicit section mapping NXOSv as a model?  For example, your suggestion in https://github.com/Apstra/aeon-ztps/issues/130


Issue 20 queue unbind

This is a cleaned up version of pyalex's fork which addresses https://github.com/paolo-losi/stormed-amqp/issues/20

Thanks for the pull request!

No worries, thanks for looking into this. :-)


[Feature ⭐] Check map validation with fluidfill Algorithm

Feature type
Engine/event/game mechanics
Implementing process / Goal
Check whether map is closed with walls.

## Selects solution

1. Fluidfill Algorithm
2. Sequential checking ?

Working in progress ..

Related code
No response
Note
No response

possible idea
if it's first/last row/column and tile in '0NSEW':
  raise error
elif tile == ' ' and tile.neighbor_has('0NSEW'):
  raise error


Quick start example not work

Hello,
I'm trying to display the elements of a single table using the basic example, but I get the error:
"invalidoperationexception: The operation can not be completed because the DbContext has been disposed".
I'm using MVC5 and EF6.
In the controller the code is identical to the example as shown `below:
[HttpGet]
public ViewResult Index3()
{
    using (var context = new MCS1DBEntities())
    {
        var cts = context.Contracts.OrderBy(b => b.Id);
	return View(cts);
    }
}

The error disappears if I remove the "using" in the allocation of the dbcontext:
[HttpGet]
public ViewResult Index3()
{
        var context = new MCS1DBEntities())
 	var cts = context.Contracts.OrderBy(b => b.Id);
	return View(cts);
}

Thank you.

True, context dispose should be in controller's dispose method, will update the example page.

Would it be possible to use an "IList" collection instead of "IQueryable"?
Thanks again.

You can use any IEnumerable implementation, just be careful with what their implementations imply.

Excuse me again,
but if I use an "IList" collection (return context.Foos.OrderBy(b => b.Id).ToList();) I get the following error:
"The model element passed in the dictionary is of type 'System.Collections.Generic.List1 [Grid4Test.Models.Foo]' but this dictionary requires a model element of type 'System.Linq.IQueryable1 [Grid4Test .Models .foo] '".
Thanks for your patience.

That's the error from your view are you taking @model IList<Foo> as a model for your view?

Damn! I modified the Index2 controller but the view was Index3! Thank you.


CUDA required?

Hi,
I've installed coriander successfully, and now trying to get TF installed on a non-nvidia OpenCL 1.2 GPU (linux).
When running util/run_configure.sh, I see that TF does not select CUDA:
No Google Cloud Platform support will be enabled for TensorFlow
No Hadoop File System support will be enabled for TensorFlow
Found possible Python library paths:
  /usr/lib/python3/dist-packages
  /usr/local/lib/python3.5/dist-packages
Please input the desired Python library path to use.  Default is [/usr/lib/python3/dist-packages]
/usr/lib/python3/dist-packages
No GPU support will be enabled for TensorFlow
checking operating system
Configuration finished

So, does this mean that TF will not get GPU support, so coriander even if it translates OpenCL->CUDA, TF will not use it? Is there a way to force TF_NEED_CUDA?

Just to be sure, I ran the configure script manually, and selected the CUDA installation.
I still have 2 problems:

After compiling and installing coriander (after the build_coriander script) I was able to compile and run the cuda sample program:

odroid@odroid:~/src/cuda$ ./cuda_sample
OpenCL platform: ARM Platform
OpenCL device: Mali-T628
hostFloats[2] 123
hostFloats[2] 222
hostFloats[2] 444

However, trying it again now, compilation fails with a segmentation fault:
odroid@odroid:~/src/tensorflow$ cocl cuda_sample.cu
cocl args: cuda_sample.cu
+ /home/odroid/src/tensorflow/tf-coriander/soft/llvm-4.0/bin/clang++ -DUSE_CLEW -std=c++11 -x cuda -D__CORIANDERCC__ --cuda-gpu-arch=sm_30 -nocudalib -nocudainc --cuda-device-only -emit-llvm -O0 -S -D__CUDACC__ -Wno-gnu-anonymous-struct -Wno-nested-anon-types -I/home/odroid/src/tensorflow/tf-coriander/soft/llvm-4.0/include -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/odroid/src/tensorflow/tf-coriander/soft/llvm-4.0/include -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -Werror=date-time -std=c++11 -ffunction-sections -fdata-sections -O3 -fexceptions -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/usr/local/include/EasyCL -I/usr/local/include/cocl -I/usr/local/src -I/usr/local/src/EasyCL -I/usr/local/src/EasyCL/thirdparty/clew/include -include /usr/local/include/cocl/cocl.h -include /usr/local/include/cocl/fake_funcs.h -include /usr/local/include/cocl/cocl_deviceside.h -I/usr/local/include ./cuda_sample.cu -o ./cuda_sample-device-noopt.ll
/usr/local/bin/cocl_wrapped: line 393: 12486 Segmentation fault      ${CLANG_HOME}/bin/clang++ ${PASSTHRU} -DUSE_CLEW -std=c++11 -x cuda -D__CORIANDERCC__ --cuda-gpu-arch=sm_30 -nocudalib -nocudainc --cuda-device-only -emit-llvm -O0 -S ${ADDFLAGS} -D__CUDACC__ -Wno-gnu-anonymous-struct -Wno-nested-anon-types ${LLVM_COMPILE_FLAGS} -I${COCL_HOME}/include/EasyCL -I${COCL_HOME}/include/cocl -I${COCL_HOME}/src -I${COCL_HOME}/src/EasyCL -I${COCL_HOME}/src/EasyCL/thirdparty/clew/include -include ${COCL_HOME}/include/cocl/cocl.h -include ${COCL_HOME}/include/cocl/fake_funcs.h -include ${COCL_HOME}/include/cocl/cocl_deviceside.h -I${COCL_HOME}/include ${INCLUDES} ${INPUTBASEPATH}${INPUTPOSTFIX} -o ${OUTPUTBASEPATH}-device-noopt.ll

Any ideas why this happens?

TF fails to build with:

ERROR: /home/odroid/.cache/bazel/_bazel_odroid/bf26e11cb9ace4c240bd220fa38d9ec4/external/protobuf/BUILD:73:1: undeclared inclusion(s) in rule '@protobuf//:protobuf_lite':
this rule is missing dependency declarations for the following files included by 'external/protobuf/src/google/protobuf/stubs/time.cc':
  '/usr/arm-linux-gnueabihf/include/stdc-predef.h'
  '/usr/arm-linux-gnueabihf/include/features.h'
  '/usr/arm-linux-gnueabihf/include/sys/cdefs.h'
  '/usr/arm-linux-gnueabihf/include/bits/wordsize.h'
  '/usr/arm-linux-gnueabihf/include/gnu/stubs.h'
  '/usr/arm-linux-gnueabihf/include/gnu/stubs-hard.h'
  '/usr/arm-linux-gnueabihf/include/wchar.h'
  '/usr/arm-linux-gnueabihf/include/stdio.h'
  '/usr/lib/gcc/arm-linux-gnueabihf/6/include/stdarg.h'
  '/usr/arm-linux-gnueabihf/include/bits/wchar.h'
  '/usr/lib/gcc/arm-linux-gnueabihf/6/include/stddef.h'
  '/usr/arm-linux-gnueabihf/include/xlocale.h'
  '/usr/lib/gcc/arm-linux-gnueabihf/6/include/stdint.h'
  '/usr/arm-linux-gnueabihf/include/stdint.h'
  '/usr/arm-linux-gnueabihf/include/locale.h'
  '/usr/arm-linux-gnueabihf/include/bits/locale.h'
  '/usr/arm-linux-gnueabihf/include/ctype.h'
  '/usr/arm-linux-gnueabihf/include/bits/types.h'
  '/usr/arm-linux-gnueabihf/include/bits/typesizes.h'
  '/usr/arm-linux-gnueabihf/include/endian.h'
  '/usr/arm-linux-gnueabihf/include/bits/endian.h'
  '/usr/arm-linux-gnueabihf/include/bits/byteswap.h'
  '/usr/arm-linux-gnueabihf/include/bits/byteswap-16.h'
  '/usr/arm-linux-gnueabihf/include/pthread.h'
  '/usr/arm-linux-gnueabihf/include/sched.h'
  '/usr/arm-linux-gnueabihf/include/time.h'
  '/usr/arm-linux-gnueabihf/include/bits/sched.h'
  '/usr/arm-linux-gnueabihf/include/bits/time.h'
  '/usr/arm-linux-gnueabihf/include/bits/timex.h'
  '/usr/arm-linux-gnueabihf/include/bits/pthreadtypes.h'
  '/usr/arm-linux-gnueabihf/include/bits/setjmp.h'
  '/usr/arm-linux-gnueabihf/include/stdlib.h'
  '/usr/arm-linux-gnueabihf/include/bits/waitflags.h'
  '/usr/arm-linux-gnueabihf/include/bits/waitstatus.h'
  '/usr/arm-linux-gnueabihf/include/sys/types.h'
  '/usr/arm-linux-gnueabihf/include/sys/select.h'
  '/usr/arm-linux-gnueabihf/include/bits/select.h'
  '/usr/arm-linux-gnueabihf/include/bits/sigset.h'
  '/usr/arm-linux-gnueabihf/include/sys/sysmacros.h'
  '/usr/arm-linux-gnueabihf/include/alloca.h'
  '/usr/arm-linux-gnueabihf/include/bits/stdlib-float.h'
  '/usr/arm-linux-gnueabihf/include/libio.h'
  '/usr/arm-linux-gnueabihf/include/_G_config.h'
  '/usr/arm-linux-gnueabihf/include/bits/stdio_lim.h'
  '/usr/arm-linux-gnueabihf/include/bits/sys_errlist.h'
  '/usr/arm-linux-gnueabihf/include/errno.h'
  '/usr/arm-linux-gnueabihf/include/bits/errno.h'
  '/usr/arm-linux-gnueabihf/include/linux/errno.h'
  '/usr/arm-linux-gnueabihf/include/asm/errno.h'
  '/usr/arm-linux-gnueabihf/include/asm-generic/errno.h'
  '/usr/arm-linux-gnueabihf/include/asm-generic/errno-base.h'
  '/usr/arm-linux-gnueabihf/include/assert.h'
  '/usr/arm-linux-gnueabihf/include/string.h'
  '/usr/arm-linux-gnueabihf/include/sys/param.h'
  '/usr/lib/gcc/arm-linux-gnueabihf/6/include-fixed/limits.h'
  '/usr/lib/gcc/arm-linux-gnueabihf/6/include-fixed/syslimits.h'
  '/usr/arm-linux-gnueabihf/include/limits.h'
  '/usr/arm-linux-gnueabihf/include/bits/posix1_lim.h'
  '/usr/arm-linux-gnueabihf/include/bits/local_lim.h'
  '/usr/arm-linux-gnueabihf/include/linux/limits.h'
  '/usr/arm-linux-gnueabihf/include/bits/posix2_lim.h'
  '/usr/arm-linux-gnueabihf/include/bits/xopen_lim.h'
  '/usr/arm-linux-gnueabihf/include/signal.h'
  '/usr/arm-linux-gnueabihf/include/bits/signum.h'
  '/usr/arm-linux-gnueabihf/include/bits/siginfo.h'
  '/usr/arm-linux-gnueabihf/include/bits/sigaction.h'
  '/usr/arm-linux-gnueabihf/include/bits/sigcontext.h'
  '/usr/arm-linux-gnueabihf/include/asm/sigcontext.h'
  '/usr/arm-linux-gnueabihf/include/bits/sigstack.h'
  '/usr/arm-linux-gnueabihf/include/sys/ucontext.h'
  '/usr/arm-linux-gnueabihf/include/bits/sigthread.h'
  '/usr/arm-linux-gnueabihf/include/bits/param.h'
  '/usr/arm-linux-gnueabihf/include/linux/param.h'
  '/usr/arm-linux-gnueabihf/include/asm/param.h'
  '/usr/arm-linux-gnueabihf/include/asm-generic/param.h'
  '/usr/arm-linux-gnueabihf/include/byteswap.h'.
Target @grpc//:grpc_cpp_plugin failed to build
Use --verbose_failures to see the command lines of failed build steps.

So, does this mean that TF will not get GPU support, so coriander even if it translates OpenCL->CUDA, TF will not use it? Is there a way to force TF_NEED_CUDA?

tf-coriander provides an OpenCL implementation of Tensorflow. It doesnt support CUDA devices, except to the extent that such devices provide also an OpenCL-1.2 compatible API.

Just to be sure, I ran the configure script manually, and selected the CUDA installation.

enabling CUDA is not supported.  Please reconfigure from scratch.
Note that you can ignore the message saying it wont use a GPU.  Please mentally reinterpret this to mean 'wont use CUDA, but will use OpenCL'.

Thanks, I will reconfigure and recompile.
I thought CUDA was required (Libs installed and TF support enabled) because I understood you do CUDA - OpenCL translation (TF -> CUDA -> coriander OpenCL), glad to be wrong :)

@hughperkins - re-configuring, but I still get similar errors as above.
Somehow, bazel generates /usr/arm-linux-gnueabihf/include instead of /usr/include
Another thing which is not clear: do I need CUDA installed or not? I've seen some COCL files that reference /usr/local/cuda-8.0 -- will this work with CUDA 6.5? (I can just symlink  /usr/local/cuda-8.0 to  /usr/local/cuda-6.5 if it would made things simpler as long as CUDA 6.5 is OK).
Thanks.

CUDA Toolkit is not only not required, but its presence will actually break the compile process :)
Can you uninstall all CUDA Toolkit versions, and then redo from the configure step please?

(by the way, which files do you see that you feel are referencing /usr/local/cuda-8.0?

This makes sense - after uninstalling CUDA I could recompile again using cocl w/o getting the segm fault.
I also managed to find the correct file to add my include paths to get rid of the error I was getting before. The CUDA references I saw them when looking for include paths, they didn't actually break anything for me.
I still have some errors when compiling some 3rd party packages, but that's for next week :)
Thanks

Interesting to see if this runs on the odroid platform!
On Fri, 8 Sep 2017 at 18:45, mihailescu2m<EMAIL_ADDRESS>wrote:

This makes sense - after uninstalling CUDA I could recompile again using
cocl w/o getting the segm fault.
I also managed to find the correct file to add my include paths to get rid
of the error I was getting before. The CUDA references I saw them when
looking for include paths, they didn't actually break anything for me.
I still have some errors when compiling some 3rd party packages, but
that's for next week :)
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hughperkins/tf-coriander/issues/63#issuecomment-328071338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEc4Dk8RjczEkLPXTsbDDnzax_0rd_ovks5sgRq9gaJpZM4PPKtZ
.

@hughperkins I am now getting this error:
In file included from tensorflow/stream_executor/cl/cl_driver.cc:28:0:
./tensorflow/stream_executor/lib/casts.h: In instantiation of 'Dest perftools::gputools::port::bit_cast(const Source&) [with Dest = long long int; Source = void*]':
tensorflow/stream_executor/cl/cl_driver.cc:1022:61:   required from here
./tensorflow/stream_executor/lib/casts.h:90:3: error: static assertion failed: src and dst types must have equal sizes
   static_assert(sizeof(Dest) == sizeof(Source),

looks like it's coming from CUdeviceptr pointer = port::bit_cast<CUdeviceptr>(location); where port and CUdeviceptr have different sizes (on armhf) ... any idea which one has to be fixed?

Interesting. So, location is a constraint, which is inviolable, fixed by the client application source-code. And so what we need to change is the Coriander definition of CUdeviceptr, which is here:
https://github.com/hughperkins/coriander/blob/master/include/cocl/cocl_memory.h#L40
typedef long long CUdeviceptr;

I dont remember what constraints led me to choose this type, but note that there are conceptually two sets of constraints:

the use-cases in client source-code, which source-code is opensource, and we have legal access to, eg Tensorflow etc
in my opinion, it might be illegal, copyright violation, to look at the CUDA Toolkit include files, to see what type they are using
on the whole, I try to choose the weirdest type possible, given the constraints present in the client source-code, since this reduces the chances of being perceived to have looked at the CUDA Toolkit include files. I'm also reasonably partial to annotating some of the Coriander definitions with references to client code constraints, to justify why a certain type was chosen, if necessary. Once such comments have been present in at least one git commit, I often strip them back out, to maintain code readability

In any case, given the void * castable constraint, you could try something like:
class CUDevice {
};

typedef CUDevice *CUdeviceptr;

There might be a few cascading changes required, since the current declarations might assume a non-pointer type, and need tweaking somehow.

I am trying using unsigned int CUdeviceptr since that's the one used by CUDA as well, hope it won't break out other things ....

Please dont look at things that assume a EULA click-through etc.  Any type you choose should be justified by looking at hte constraints of the client application code, not by looking at CUDA forums etc.

I can compile it now successfully, however I get this error when trying to run something:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow.py", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 666, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 577, in module_from_spec
  File "<frozen importlib._bootstrap_external>", line 914, in create_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
ImportError: /usr/local/lib/python3.5/dist-packages/tensorflow/python/_pywrap_tensorflow.so: undefined symbol: _ZN10tensorflow7functor12ApplyAdagradIN5Eigen9GpuDeviceEfEclERKS3_NS2_9TensorMapINS2_6TensorIfLi1ELi1EiEELi16ENS2_11MakePointerEEESB_NS7_INS2_15TensorFixedSizeIKfNS2_5SizesIIEEELi1EiEELi16ESA_EENS7_INS8_ISD_Li1ELi1EiEELi16ESA_EE

Any ideas?
Thanks.

@hughperkins another update: successfully compiled and running with gcc 6.3
However, it's not working :(
This is the output when running tensorflow/stream_executor/cl/test/test_simple.py
http://paste.debian.net/986023/

Seems plausible that it is linked with this line:

I tensorflow/core/common_runtime/gpu/gpu_device.cc:1070] Ignoring gpu device (device: 1, name: Mali-T628, pci bus id: 0000.0000) with Cuda multiprocessor count: 2. The minimum required count is 4. You can adjust this requirement with the env var TF_MIN_GPU_MULTIPROCESSOR_COUNT.
cl_driver DeviceAllocate 312985600

Is this the device you are targeting?

@hughperkins it's not ...
The Mali GPU has 6 cores in 2 clusters, and that is a warning that the 2-core cluster is ignored (e.g. there is only gpu0). If I run the same program with TF_MIN_GPU_MULTIPROCESSOR_COUNT=2, it can use both clusters (gpu0 and gpu1 are available)...
I think the issue is Limit:                           0 - it means that the memory is limited to 0... so allocating first chunk fails (You can see there is Total Chunks: 0 for all the bins).
Any idea why the limit is 0? What fails to allocate?? (probably in tensorflow/core/common_runtime/bfc_allocator.cc)

@hughperkins  another update :) setting the limit to 312985600 seems to allow some stuff to run, like test_simple.py:
$ python test_simple.py
OpenCL platform: ARM Platform
OpenCL device: Mali-T628
I tensorflow/core/common_runtime/gpu/gpu_device.cc:989] Found device 0 with properties:
name: Mali-T628
major: -1 minor: -1 memoryClockRate (GHz) 600
pciBusID 0000.0000
Total memory: 1.95GiB
Free memory: 498.49MiB
W tensorflow/stream_executor/cl/cl_driver.cc:587] creating context when one is currently active; existing: �\c��D"�ice:
OpenCL platform: ARM Platform
OpenCL device: Mali-T628
I tensorflow/core/common_runtime/gpu/gpu_device.cc:989] Found device 1 with properties:
name: Mali-T628
major: -1 minor: -1 memoryClockRate (GHz) 600
pciBusID 0000.0000
Total memory: 1.95GiB
Free memory: 498.49MiB
I tensorflow/core/common_runtime/gpu/gpu_device.cc:877] cannot enable peer access from device ordinal 0 to device ordinal 0
I tensorflow/core/common_runtime/gpu/gpu_device.cc:877] cannot enable peer access from device ordinal 0 to device ordinal 1
I tensorflow/core/common_runtime/gpu/gpu_device.cc:877] cannot enable peer access from device ordinal 1 to device ordinal 0
I tensorflow/core/common_runtime/gpu/gpu_device.cc:877] cannot enable peer access from device ordinal 1 to device ordinal 1
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1011] DMA: 0 1
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1021] 0:   N N
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1021] 1:   N N
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1083] Creating TensorFlow device (/gpu:0) -> (device: 0, name: Mali-T628, pci bus id: 0000.0000)
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1070] Ignoring gpu device (device: 1, name: Mali-T628, pci bus id: 0000.0000) with Cuda multiprocessor count: 2. The minimum required count is 4. You can adjust this requirement with the env var TF_MIN_GPU_MULTIPROCESSOR_COUNT.
cl_driver DeviceAllocate 312985600
Device mapping:
/job:localhost/replica:0/task:0/gpu:0 -> device: 0, name: Mali-T628, pci bus id: 0000.0000
I tensorflow/core/common_runtime/direct_session.cc:252] Device mapping:
/job:localhost/replica:0/task:0/gpu:0 -> device: 0, name: Mali-T628, pci bus id: 0000.0000

running sess.run a
c: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:819] c: /job:localhost/replica:0/task:0/gpu:0
b: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:819] b: /job:localhost/replica:0/task:0/gpu:0
a: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:819] a: /job:localhost/replica:0/task:0/gpu:0
+++ kCudaHostMemoryUseBFC calling BFC allocator for 1LL << 36 memory (replaced with 312985600)
[[  4.   7.   9.]
 [  8.  10.  12.]]
done

HOWEVER, some tests fail:
test_binary_ops.py::test[uint8-mul-a * b] xfail
test_binary_ops.py::test[uint8-div-a / b] xfail
test_binary_ops.py::test[float32-not_equal-np.not_equal(a, b)] PASSED
test_binary_ops.py::test[float32-maximum-np.maximum(a,b)] PASSED
test_binary_ops.py::test[float32-minimum-np.minimum(a,b)] PASSED
test_binary_ops.py::test[float32-pow-np.power(a,b)] PASSED
test_binary_ops.py::test[float32-mul-a * b] PASSED
test_binary_ops.py::test[float32-sub-a - b] PASSED
test_binary_ops.py::test[float32-squared_difference-(a - b) * (a - b)] PASSED
test_binary_ops.py::test[float32-add-a + b] PASSED
test_binary_ops.py::test[float32-div-a / b] PASSED
test_binary_ops.py::test[int32-maximum-np.maximum(a,b)] PASSED
test_binary_ops.py::test[int32-minimum-np.minimum(a,b)] PASSED
test_binary_ops.py::test[int32-mul-a * b] PASSED
test_binary_ops.py::test[int32-sub-a - b] PASSED
test_binary_ops.py::test[int32-squared_difference-(a - b) * (a - b)] PASSED
test_binary_ops.py::test[int32-add-a + b] PASSED
test_binary_ops.py::test[int32-div-a / b] PASSED
test_blas.py::test_blas PASSED
test_gradients.py::test_gradients Aborted

and running linear_regression exits with the error:
Aborted

Any idea to fix this? :D

I removed the isAligned check completely (no idea what will do... but i didn't get any segm faults yet).
Linear regression: average_epoch_times= 6.146 kernel_compile_time 0.319


feat: add whole channel category types

About
This PR adds every type in channel.
Status

[ ] These changes have been tested against Discord API or do not contain API change.
[ ] This PR includes only documentation changes, no code change.
[ ] This PR introduces some Breaking changes.

Btw would it be possible to have a reference to each type to the docs?
Might be handy for users looking to contribute. Will allow us to update types easierly aswell

Btw would it be possible to have a reference to each type to the docs?
Might be handy for users looking to contribute. Will allow us to update types easierly aswell

nice

yunho, is it possible to fix formatting aswell for the check's to be green?


[Release] Test Arrow Flight in Windows release verification script

This works for me with 0.14.0 rc0. On account of ARROW-5817 I had to check manually that the Python unit tests passed

+1


Destiny Rising APK 4.5 (Android & IOS) Download Latest Version 2024

Destiny Rising APK is a mobile app designed for users looking to enhance their gaming experience. With features that add new levels of immersion, this APK brings exciting options to players who seek customization, ease of use, and added engagement. Whether you’re new to mobile gaming or a seasoned player, Destiny Rising APK provides a range of benefits that enhance your gameplay and interaction with the virtual world.
Download: Destiny Rising APK
Benefits of Using Destiny Rising APK
One of the main advantages of Destiny Rising APK is the level of control it offers. Players can personalize their gaming environment, making it a more immersive and engaging experience. The APK provides unique tools and updates that keep gameplay fresh, ensuring players stay entertained and challenged.
Additionally, Destiny Rising APK has features to improve in-game efficiency. This includes advanced navigational tools and easier access to exclusive content, making it ideal for those who want to level up faster without spending extra money. The app is also lightweight, which means it won’t occupy significant storage space or slow down your device, allowing for a smooth gaming experience.
Features of Destiny Rising APK
Destiny Rising APK comes packed with features designed to cater to diverse gaming needs. Some of the standout features include:
Customizable Settings: Users can adjust graphics, sound effects, and other game settings according to their preferences, providing a tailored gaming experience.
Exclusive Content: The APK often includes exclusive skins, avatars, and items that are not available in the regular game, offering players a unique edge.
Efficient Navigation: With intuitive controls and improved navigational tools, players can seamlessly move around in the game, making gameplay more enjoyable.
Frequent Updates: Destiny Rising APK regularly updates to introduce new features, levels, and items, keeping the experience fresh and engaging.
Is Destiny Rising APK Safe to Use?
Security is a common concern when downloading APKs outside of official app stores. Fortunately, Destiny Rising APK has been tested to ensure it doesn’t contain any malicious software, making it safe for use on most devices. However, it’s essential to download it from a reputable source and keep the app updated to maintain optimal security.
Design and User Experience
Destiny Rising APK stands out with its user-friendly interface and visually appealing design. The menus are easy to navigate, even for beginners, and the graphics are vibrant, enhancing the game’s appeal. The developers have clearly focused on providing a seamless user experience with quick loading times, minimal lag, and efficient responsiveness across various devices.
Conclusion
Destiny Rising APK is a solid choice for anyone looking to elevate their gaming experience. It offers a range of features, from customizable settings and exclusive content to efficient navigation, all while maintaining a user-friendly design. While downloading an APK outside of an official app store requires caution, Destiny Rising APK’s benefits make it worth considering for dedicated gamers.

Beware of the scam, this looks like a malicious link!


CloudFlare does not support 2FA via SMS

It asks for your phone number, but there is no way to receive tokens via text messages. Only Authy is supported.

Doesn't Authy works through sms?

It does and they do.
@nyuszika7h I suggest you look at Authy's website.
Here's a screenshot:

Would you care to explain how it works with CloudFlare? Because I've only seen that work with Humble Bundle.

Hmm true.
I thought they supported that though I could see why they don't as SMS is more insecure than the Authy app.
Could someone who doesn't use Authy confirm that Cloudflare doesn't support SMS TFA?
I use Authy for everything :see_no_evil:

CloudFlare requires Authy and step 2 asks for your phone number. I'm not sure if it's for sms or to identify you as a user in Authy's system.

Like I said, I already tried that, and I didn't get any text message. The next step told me to install the app.


Display the player who counterwarded

Okay, I've decided to split this from #502 because this needs some parser work.
I've used manta to prototype my idea for the counter-warder detection and it seems to be working.
Basically, I'd credit the counter-ward to the player who last hit the ward, which to me seems reasonable.
The wards bounty is static to 100 gold and tracking the observer_left entity and correlating the time stamp with the combat log seems to be reliable to detect a counter ward.
Combat logs XP and Gold gains have reasons, and it seems wards kills are credited in the "0" category which makes it easy to track these down. We need to discard the two first runes as they also gives 100 gold, listed as reason 0, but gives no XP.
I'll try to implement a prototype in clarity soon.

I correctly identify all 5 counter-wards that happened and can credit them to the correct player.
Feel free to add your thoughts.

How do you want to store this data?
One quick approach: Make it a match-level object mapping timestamp to player_slot.  Then whenever you have a obs_left event you can look up any players who have a 100 gold increase at that same time (second).

Something along these lines:
counterwards_log : [{
    "time": 590,                    // timestamp
    "ehandle": 2654379,     // which ward
    "player_slot": 2              // who counter-warded
    "owner_player_slot": 3 // who's ward is it?
}, ...

What do you think about that?
Why not make it player_level like obs_left_log or obs_log?

Implemented in https://github.com/odota/parser/pull/3
There is a separate issue to track the UI update

Why not add the the counterward data to the wardlog.left object?

I believe that is how the current version implements it.  Deward entries have an "attackername" property if they were killed by a player.


throws warning with 'path

@jmeas   nodeJS throws a warning on path. Where path also is an module in nodejS.

Can you provide more details, @kflash? When does NodeJS throws an error? And what version of node are you using?

@jmeas nodeJS v. 12.x. It comes up when I build the repo, and also in TravisCI

@kflash, maybe I'm being dum here, but I can't reproduce it. And I looked at the Travis logs and didn't see the warning there, either. Am I missing something obvious?
By 'build the repo,' what do you mean? Do you mean installing the dependencies, or building the library?
Building the library:

I'd post the ss of installing the deps, but the text doesn't all fit on one page. I don't see a warning, though!

@jmeas I see you didn't get the warning. Strange. I got it the whole day.
Anyway. See documentation for nodeJS 12.2 here.  https://nodejs.org/api/path.html
Path is clearly a part of nodeJS@newest.

@jmeas This is not a new issue it seems. See stackOverflow: http://stackoverflow.com/questions/24897130/path-is-also-the-name-of-a-node-core-module

I know about path, and I've seen this issue before in other projects. I've just never seen it in this project before.
Is it cool to close this issue, then?

I think you can close it. People who sees it should know how to fix it. I'm off for a few minutes, trying to fix your ESlint.


In order to ease the development workflow. It would be more convenient if we moved to Travis CI.

Add Travis CI integration to the project.

Can I work on this?

Hi. I had a doubt, shall I integrate Travis for Docker or Node JS(JavaScript)?

I have little experience with Docker, so Travis for nodejs would be good I think. If you have worked with docker, then you can see which one suits best.

Oh actually docker had been used in the project a bit so that is why I was confused. 😅
I will make it for Node.js for now

Yeah. there was an issue that used docker so someone created a PR using it!

@garimasingh128 Can we close this issue?


update to 7.2, plus gradle plus instructions for compile

This is what  I changed to get it to build and work on ES7.2

@nelg Sorry for the late response. And thank you for your contribution!!
Looks good to me.

And also I released my plugin to Sonatype repository and updated README.


Programmer mode - operation sign disappear when number system changed

Example:

in Programmer mode choose HEX
enter '10', enter '+'
in history string shows '010 +'
change number system to DEC
in history string shows '16' without operation sign
enter '1'
in history string shows '161'
press '='
in history string shows '17'
So when number system changed during formula entering, operation sign is disappear.
This is very confusing.

@Baton34 , thanks for the report. It is as you said, the operation remains but the operator becomes invisible in history string. Might be because I toggled some things when the result was empty. Will look into this once I get time.

Fixed as of #44


Merge pull request #6 from Nerdware-LLC/next

Update README header and badges (file changed on main).

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


Iterate content on the Verify without Verify journey

This iterates the content (as outlined on this Miro Board) to make it clearer about next steps when a user cannot be verified using GOV.UK Verify.

 Iterate content on the Verify without Verify journey