text:
Update Posts “a-post-with-code-samples”

Automatically generated by Netlify CMS

👷 Deploy Preview for joseluizcoe-site processing.

Name
Link

🔨 Latest commit
c6adfd3bb18ecbf96f43b35da480138d38ea09e2

🔍 Latest deploy log
https://app.netlify.com/sites/joseluizcoe-site/deploys/633a06de7fc8500008aa5363

repo: joseluizcoe/joseluizcoe-site


text:
Support diacritics

So I stumbled on matching city names in Germany and particularly I have this:
'Gross-Gerau' .score('Groß-Gerau') => 0

I wonder if there's any chance that you can support mapping it first without diacritics as an option in the config? would be much easier this would be usage (as I see it):
'Gross-Gerau' .score('Groß-Gerau', { diacriticsMap: true }) => 1

or similar

If you add the fuzzy match it should work.
Sent from my iPhone

On Jan 7, 2020, at 9:39 PM, Daniel Chmielowiec notifications@github.com wrote:

So I stumbled on matching city names in Germany and particularly I have this: 'Gross-Gerau' .score('Groß-Gerau') which gives me 0, so I wonder if there's any chance that you can support mapping it first without diacritics as an option in the config? would be much easier
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

source: gharchive/issue

authors: chmieludaniel joshaven

license: mit

license_type: permissive

license_source: bigquery


text:
palindrome words throw an error

When attempting to use any palindrome like:
$ word-search eve tenet madam
it will throw an error:

ValueError: Use words longer than one-character and without punctuation.

word-search --version: 3.5.1

Hey, yes the default generator ignores palindromes as it can cause errors with key coordinates and valid directions. There is a new version (v4.0.0) coming out "soon". The code is basically done, I just need to add some testing for the new features.
One of the new features is custom word validators. You can read a bit about them here.
If you are not interested in building your own word search game object, you can simply disable the word validators from the CLI.
$ word-search eve tenet madam --no-validators
         WORD SEARCH
 ───────────────────────────
 A P T Y C E V X P H Z P K Y
 A M W I T B A W R L X N F Y
 J P S J V E P F M E N T E R
 X Y F C X B H Z A K G E C E
 Z B L O G J A P D D K N W V
 F P J J E I U Q A W F E Q E
 O C D C M X S L M L U T F P
 Y X R A L O I I G B R L Q P
 S R G A P R Y S A D F I G E
 L L S Y E O B A V V W G O Y
 U E R Y D P V U U T N D R O
 I I Z K K R V C W H V G O L
 M L U A Q K Z Y V H L R S W
 Q U C N E Q F I N N B A X Q
 ───────────────────────────
Find words going SE, S, NE, and, E:
EVE, MADAM, TENET

Answer Key: EVE S @ (14, 4), MADAM S @ (9, 3), TENET S @ (12, 3)

To pip install the working version directly from GitHub, just use the command below.
$ pip install git+https://github.com/joshbduncan/word-search-generator

Let me know if you have any questions? Cheers!

authors: danewfie joshbduncan

repo: joshbduncan/word-search-generator

license: MIT

license_source: github-api


text:
[feature] Setup releases with GitHub Actions

As it says on the tin really!

@teschiopol looks good! Agree it needs to tag and push that rather than commit, but nice work!
Did you want to submit a PR?

Do u wanto to trigger that action on every push on master?

Sounds good!

authors: joshghent teschiopol

repo: joshghent/gifbar


text:
Is this project still under development?

Hi Josh,
This project seems like a great idea to me and I was wondering if you are still working on it or it has been superseeded with something else?
Many thanks for the feedback and the cool work!!
Alberto

It's mainly in maintaining mode due to work stuff but it has not been superceded. I hope to get back to it later this month. Are there some features you need?

No, so far I was not able to install it yet :)

authors: almilo joshmarinacci

repo: joshmarinacci/aminogfx


text:
Bug: Multiple stores using the same key does not work properly

I've encountered a bug when two different pages are open at the same time and uses the same store/key.
Reproducible instructions:

git clone https://github.com/PeppeL-G/svelte-persisted-bug.git
cd svelte-persisted-bug
npm install
Open / in a tab in the web browser (store1 is created)
Open /page-2/show in another tab in the web browser (store2 is created)
On the /page-2/show page, click on the Hide counter link (the store2 variable is deleted)
On the / page, click on the inc button (store1 is properly incremented by 1)
On the /page-2 page, click on the Show counter link. store2 is created/retrieved from your internal cache, but it does not contain the incremented number in store1 even though they use the same key

So, in one and the same document, it seems like creating a store with the same key a second time does not use the latest value from local storage.

This seemed like a really weird case when I first read the description, but having cloned the repo and played with the code, it is reproducible. To understand what is happening here, I believe it is important to understand two key things about this library:

When a persisted store is created, it is being kept track of in an internal object, indexing all persisted stores ever created by their key. This means two things:

When creating two persisted stores in the application layer with the same key, it is not two different stores refereeing to the same localStorage key, but instead the same store, as the second time the store is "created" in the application layer, a new store isn't created, but a reference to the earlier store with the same key is simply passed.
Persisted stores are never removed. This means that clicking "Hide counter" here removes the reference to the store in the application layer, but as the library retains a reference to the store it is not actually removed

When a store is not subscribed, it doesn't monitor events from the localStorage. This is done for perfomance reasons (I assume) and is a normal practice within svelte stores.

I believe what is happening here is the following:

You navigate to /, creating store1
You navigate to /page-2/show, creating store2
You navigate to /page-2, deleting the reference to store2 in the application layer (and therefore unsubscribing from it), but keeping it alive in the library layer
You click the inc button on the / page, updating store1 and the reference in localStorage, but as you have unsubscribed from store2, this doesn't recieve the localStorage event, and therefore its value doesn't change
You navigate to /page-2/show, and since store2 has been saved in the library layer, you retrieve this from the library cache with the old value and subscribe to it

Now, this here is a good catch, and one that requires a minor rework of the central structure of this library. I propose two fixes:

Reading from localStorage once a store is subscribed to (just like when creating the store). This ensures consistency, and prevents scenarios like this, where a store becomes stale as a result of having a period of unsubscription.
Removing the library cache of persisted stores. Not only would this fix this specific bug, but I think that it would lead to much more predictable behavior on the user-side, as this would allow to say, have two stores refering to the same key to have different settings. What we are currently doing with both the internal cache, and using the localStorage api is essentially two sources of truth, and I don't believe the cache is necessary, as we can just query the newest value from localStorage. If I (as an app-dev) is interested in keeping the store alive, I should do it in the application layer by importing it from a regular TS file.

I would love to draft up a PR for this, but I just wanted to check in with you @joshnuss, as these are some pretty significant changes to the library

@bertmad3400 Thanks for the detailed analysis!

When creating two persisted stores in the application layer with the same key, it is not two different stores refereeing to the same localStorage key, but instead the same store

Correct. Since the persisted store is essentially a wrapper over a localStorage key, having many copies around seemed like a waste and possible consistency error.

Persisted stores are never removed
What if we fixed that? Then @PeppeL-G's issue would be resolved. Plus, it would fix a potential memory leak for apps that create many temporary stores.

So I have done a lot of digging and experimentation, and have concluded two things: This is more complicated than I assumed, and I'm a dumbass who can't read the manual.
As it turns out, there is a really good reason for the internal store cache, but it isn't the one given by @joshnuss (which even though I fundamentally disagree with is another valid reason for it)

This (Storage Events) won't work on the same browsing context that is making the changes — it is really a way for other browsing contexts on the domain using the storage to sync any changes that are made. Browsing contexts on other domains can't access the same storage objects.

MDN

The need for an internal cache structure is the fact that multiple stores using the same key will not automatically stay in sync on the same page, as the storage event won't propagate. While this has the unfortunate (and un-documented) side-effect that stores using the same key, but different settings will use the settings of whichever store was created first (which can be really confusing), but I see no way around this.
Secondly however, while my analysis was rather thorough it was completely wrong. Store1 and Store2 shouldn't stay in sync because of the storage events (that doesn't even work), but because they are a reference to the very same store. Why this doesn't work I have no clue, and after digging into this source code, related test environment details and web documentation for the last 4 hours, I'm completely toasted. I might have a look at it another day

The need for an internal cache structure is the fact that multiple stores using the same key will not automatically stay in sync on the same page, as the storage event won't propagate
Is it possible to subscribe to storage event multiple times? Then each store could subscribe to the storage event, and unsusbscribe during cleanup and we wouldn't need a global mapping of keys/stores.

Is it possible to subscribe to storage event multiple times? Then each store could subscribe to the storage event, and unsusbscribe during cleanup and we wouldn't need a global mapping of keys/stores.

No, that is unfortunately not possible. As described, storage event's only fire across context, and not in the same context, and while it would be possible to manually fire it, this would be incredibly messy, duplicate events (and related handling) and break standards. I think you made the right call with the caching structure, and as far as I can see, that isn't what's causing the problem in this specific issue

I don't know if you have heard about it, nor if it will be useful for you, but instead of listening to the storage event, maybe the Broadcast Channel API can be helpful.

@PeppeL-G, that's a great point!
If we want to keep cross-tabs working, we could always roll our own channel events.
And then the storage event could be captured

To determine if an event happened outside Svelte (might not need to support this)
To determine if a local storage key was deleted. (still unsure what the behaviour should be is when a key is deleted)

authors: PeppeL-G bertmad3400 joshnuss

repo: joshnuss/svelte-persisted-store


text:
更新成功后删除旧规则存在问题

例如自定义运营商，如果只设置一个中国列表没问题。
但同时设置中国和Google两个运营商列表时，一旦其中一个更新成功但另一个失败，最后会导致所有旧规则列表都被删除。
建议备注使用 “IKUAI_BYPASS-中国”、“IKUAI_BYPASS-Google”这种形式区分是否删除旧列表

感谢建议，因为没遇到过单条记录更新失败的情况，所以忽视了这个可能存在的问题。
后面会考虑在配置文件中单独配置备注名称的方式来处理。

repo: joyanhui/ikuai-bypass


text:
wishlist: add support for dynamic primary zone

Hello,
I wish the support for dynamic primary zones, which means zones that can be updated via nsupdate.
The first draft is create only a zonefile if that zonefile not exists.

I propose to support this by adding a :create_if_missing action to the primary_zone custom resource to mirror what's done by the file resource. This wouldn't persist the data any place. If you were to rebuild the host there wouldn't be any way of starting with that data intact. Does that seem reasonable as a start?

Released in v2.2.0.

authors: huckley joyofhex

repo: joyofhex/cookbook-bind


text:
Ambari Agent can't start in Centos7

Hello all!
As explained in this issue, using the ambari-agent.ini template as provided in the cookbook can lead to an unusable system, since during the chef-client it will try to chown almost all filesystem directories and files to root:root, breaking everything and making it almost impossible to recover if you don't have a snapshot to roll back.
I don't know how to write any test to this rather than just try to install on Centos7.

Thanks @JotaNavarro. I had the exact same issue where outdated ambari-agent.ini blowed up unix permissions on ambari 2.4 by making root:root owner of entire /var directly. I independently ended up putting the same fix and discovered your PR when I was about to open the similar one.
Here is the visual diff.

If you are planning to merge this into master, I would suggest that we keep both old and new keys in the configuration file. But keeping a single configuration file to support multiple ambari version seems like a bad idea to me. It would better to keep a seperate branch for every ambari version.
PS: I copied new configuation from https://apache.googlesource.com/ambari/+/branch-2.4/ambari-agent/conf/unix/ambari-agent.ini

Hello guys, thanks for the updates.
@anurajp I think you are right that we should not keep a mix of old and new keys in the config file. Adding each version in a new branch will make it harder to maintain the cookbook.
I think the best option would be to have a specific template for each version. The recipe would pick the good template depending on the version the user wants.
@anurajp or @JotaNavarro  would you have some time to do such an update on this PR?

source: gharchive/pull-request

authors: JotaNavarro anurajp jp

repo: jp/ambari


text:
setup firewall between kenny and tweek servers

of course ideal would be to have a private network between the two....

specifically mongo (27017) and the tsdb

servers have been decommissioned ...

repo: jparicka/cloudly


text:
No integration

Hi, I have question. When I try to add this integration I put IP of connection server port and username and password of CS. But no integration is load… I have CU3-2 and CS. Than you

Samu for me:-(

repo: jpbaltazar/inels-hacs-new


text:
18.9.41.1

https://ci.appveyor.com/project/jpboyce/cb-cis-windows-2016#L1496

Resolved by 9cc4dbe


text:
Advanced example custom markercluster.

Hello @jperelli.
This is not a issue report. I'm just starting to learn vue and js.
Your plugin helps a lot.
Please show an advanced example for changing the cluster marker color settings via refreshClusters ().
If necessary, I can bring the cog of my component with the map.
Thank you.

Hi, please provide your component code

`

Zoom: {{ zoom }}

            {{ item.title }}

                Подробнее

`

Hey, any news on this ?
I'm trying to change the clusters Icon but I did not find how to...
Where and how should I place the iconCreateFunction option ?
Thanks

@AlexisWalravens iconCreateFunction should be part of the options for the marker cluster.
<l-marker-cluster :options="clusterOptions">
with clusterOptions in you data of the component:
data() {
  return {
    ...
    clusterOptions: {
      ...
      iconCreateFunction: () => {
        ...
      }
    }
   ...
  }
}

all possible options are documented here: https://github.com/Leaflet/Leaflet.markercluster#all-options

authors: AlexisWalravens dolgovdv donni106 jperelli


text:
Revert #252 and replace the bash-specific substitution with a general…

… one using cut.
This has been requested in order to support alpine and busybox, which don't have bash.

Thank you!

authors: alexamirante jpetazzo

repo: jpetazzo/pipework


text:
🛑 Basketball My World is down

In 307ed6f, Basketball My World (basketballmyworld.com) was down:

HTTP code: 403
Response time: 172 ms

Resolved: Basketball My World is back up in 7e577ff after 23 minutes.


text:
🛑 The Airgap is down

In 094468e, The Airgap (https://theairgap.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: The Airgap is back up in fc4df6b after 18 minutes.


text:
ReferenceError: Headers is not defined

This error happens everytime I try to request client.accounts.getBalance({ address: 'my-address'}). The error is the same for other requests.
My code is pretty straight forward :
const { BscScan } = require('@jpmonette/bscscan')
const client = new BscScan({ apikey: process.env.BSC_API_KEY })
module.exports = async req => {
	try {
		let request = await client.accounts.getBalance({ address: req.query.address })
		return request.result
	} catch (error) {
		throw error
	}
}

You can solve this by making sure you have a fetch compatible library installed and loaded.
If you are using node,
yarn add isomorphic-fetch

and in your ts file where you use the client,
import "isomorphic-fetch";

@MonsieurBarti As @richgoldmd said above, bscscan-ts requires the Fetch API which is not packaged in Node.js out of the box. However, you can easily bring your own implementation using either isomorphic-fetch, cross-fetch or node-fetch.
Hopefully that solves your issue. If not, you can re-open the Issue.

authors: MonsieurBarti jpmonette richgoldmd

repo: jpmonette/bscscan-ts


text:
Chart.js viewer

Would you be interested in a viewer for Chart.js ?
I'd be happy to give it a try.

I think the idea is to have a variety of frontends (as plugins), so yeah definitely!

@loicbourgois Yes, this would be a useful addition. I actually have an initial PoC working. It will take me a few days to tidy it up but then we can plan the remaining work required. Thanks!

@neilslinger Let me know if you need any help :)

@loicbourgois There's some work just starting on the plotly branch for plotly, you should be able to see how to start plugging it in

We are always open to contributions of new plugins (see @timkpaine comment above) - but as this is not actively being developed and is not an issue as such, I am closing this for now.  Feel free to submit a PR, or open a new issue with more details about the proposed change, its justification & use case, etc.

authors: loicbourgois neilslinger texodus timkpaine

repo: jpmorganchase/perspective


text:
Build Error: Xcode 11 -> iPhone 11

This app hasn't been updated past Swift 4. PRs welcome.

@jpsim Will try to see what I can do. Haven't seen errors like that in my short career with iOS dev 😢

I have this issue too. These frameworks are built in to Xcode? If so I will look for them.

authors: Striderzet jpsim sorianog

repo: jpsim/CardsAgainst


text:
Breakpoints don't trigger on iPadOS when resizing a window with Stage Manager

Description
iPadOS provides some primitive window management features through Stage Manager. When resizing a React Native view using Unistyles and breakpoints one would expect that as you make the window smaller your UI will re-render with the correct styling for the given set of breakpoints. Instead the UI stays the same and overflows outside of the bounds of the application window.
I'm happy to put together an example repo if necessary, but this behavior seems trivial to reproduce in any repo that I've tried it in.
Interestingly if I console.log the Dimensions.width or Dimsensions.height from the Dimensions package in react-native the values update in realtime as I resize the window. So it seems the RN runtime is detecting the size.
Steps to reproduce

Grab an iPad or an iPad simulator
Enable Stage Manager - https://support.apple.com/en-us/105075
Install your favorite React Native app that uses Unistyles
Change the size of the screen and observe the styles don't update accordingly

Snack or a link to a repository (optional)
No response
Unistyles version
2.7.2
React Native version
0.74.1
Platforms
iOS
Engine
Hermes
Architecture
Paper (old)

Hey 👋 thanks for the report.
Should be easy to do (I guess), and I'm willing to support it as I'm also building cross platform.
Will get back to you, when I will have a plan when to release it.

I was interesting in learning more about unistyles and wanted to take a stab at this myself. It ended up being fairly simple!
https://github.com/jpudysz/react-native-unistyles/pull/209

How cool is that ?! Thank you!
I will review and test it. So most likely it will be merged in 1-2 days.

How cool is that ?! Thank you!

No problem! Happy to help!

authors: jpudysz vanstinator

repo: jpudysz/react-native-unistyles


text:
便于在绑定规则时直接通过 element和check函数验证指定的规则

Checklist for this pull request
Before submitting a pull request, please make sure to follow these rules:

Your code should contain tests relevant for the problem you are solving.
Your commits messages format should follow the jQuery git commit message format (http://contribute.jquery.org/commits-and-pull-requests/#commit-guidelines).
The pull request should reference existing issues or link to a reproducible demo.
Please review the guidelines for contributing (CONTRIBUTING.md) to this repository for more information.

Description
Please describe your pull request.
Thank you!
###########################################################################
Modify the element and check function, increase the rules and messages parameters, to facilitate the realization of some additional verification results in the custom validator, through these two functions directly in the unbound validation rules on the form elements through the verification rules and validate the specified message
修改element和check函数，增加rules和messages参数，便于在自定义验证器中实现一些额外的验证效果，可以通过这两个函数直接在未绑定验证规则的表单元素上通过指定的验证规则和消息进行验证

could you describe your concrete use-case and tell us why those 2 new parameters solve a problem for you (and which)?
thx

authors: niqingyang staabm

repo: jquery-validation/jquery-validation


text:
where I can find list of all options. static keyword is failing

My code is like this
const filename = './src/components/SignUpForm/SignUpForm.js';
const ast = esprima.parse(fs.readFileSync(filename, 'utf-8'), { tokens: true, jsx: true, sourceType: 'module' });

The SignUpForm.js' code is like
40 - export class SignUpForm extends Component {
41 -   static displayName = 'SignUpForm';
42 -   static whyDidYouRender = true;

Getting the following error message. Searching the Internet but not able to get a list of all options to try.
/Users/narendra/Coding/prophecy/metaindex/frontend/node_modules/esprima/dist/esprima.js:1995
                throw this.unexpectedTokenError(token, message);
                ^
Error: Line 41: Unexpected token =
    at ErrorHandler.constructError (/Users/narendra/Coding/prophecy/metaindex/frontend/node_modules/esprima/dist/esprima.js:5012:22)
    at ErrorHandler.createError (/Users/narendra/Coding/prophecy/metaindex/frontend/node_modules/esprima/dist/esprima.js:5028:27)
    at JSXParser.Parser.unexpectedTokenError (/Users/narendra/Coding/prophecy/metaindex/frontend/node_modules/esprima/dist/esprima.js:1985:39)
    at JSXParser.Parser.throwUnexpectedToken (/Users/narendra/Coding/prophecy/metaindex/frontend/node_modules/esprima/dist/esprima.js:1995:21)```

Please help

Demo - https://esprima.org/demo/parse.html?code=class Foo {
    static displayName %3D 'SignUpForm'%3B
    constructor() {
        if (new.target %3D%3D%3D Foo) {}
    }
}

It's not the problem of keyword 'static'. The problem is you cannot declare fields (includes public and private, static and non-static) in the brace of class. You can use a getter/setter or do this outside the class:

class Foo {
static get staticField () {
return '';
}
constructor() {
this.instanceField = '';
}
// instanceField = '';  // error
get instanceField () {
return '';
}
}
Foo.staticField = '';

authors: jianweiqin nsisodiya

repo: jquery/esprima


text:
Migrate to use govvv for builds

Fixes #136

@jrasell this seems to be a flakey import of package gopkg.in/yaml.v2: unrecognized import path

repo: jrasell/levant


text:
Add PyUnfold to conda-forge

This will give users the option to conda install PyUnfold

See conda-forge/staged-recipes#5792

It's in there https://anaconda.org/conda-forge/pyunfold :tada:

repo: jrbourbeau/pyunfold


text:
[assemble] Jdeps fails to find module org.reactivestreams for a Quarkus app

Task List

[x] Steps to reproduce provided
[x] Stacktrace (if present) provided
[x] Example that reproduces the problem (link to git repository is ideal)
[x] Full description of the issue provided (see below)

Steps to Reproduce

Clone https://github.com/aalmiray/q-cli-jlink at e659416
mvn -Passemble package

Expected Behaviour
A custom Java Runtime successfully created at target/jreleaser/assemble/q-cli/jlink
Actual Behaviour
Assembly error due to missing module
jdeps --multi-release base --ignore-missing-deps --print-module-deps universal/io.quarkus.quarkus-fs-util-0.0.9.jar universal/org.jboss.logmanager.jboss-logmanager-embedded-1.0.11.jar universal/io.smallrye.common.smallrye-common-constraint-1.13.2.jar universal/org.reactivestreams.reactive-streams-1.0.3.jar universal/org.eclipse.microprofile.config.microprofile-config-api-2.0.1.jar universal/jakarta.annotation.jakarta.annotation-api-1.3.5.jar universal/io.smallrye.reactive.mutiny-1.7.0.jar universal/org.graalvm.sdk.graal-sdk-22.2.0.jar universal/jakarta.el.jakarta.el-api-3.0.3.jar universal/info.picocli.picocli-4.6.3.jar universal/io.smallrye.config.smallrye-config-common-2.12.1.jar universal/org.eclipse.microprofile.context-propagation.microprofile-context-propagation-api-1.2.jar universal/quarkus-run.jar universal/org.jboss.slf4j.slf4j-jboss-logmanager-1.2.0.Final.jar universal/io.quarkus.quarkus-arc-2.14.0.Final.jar universal/jakarta.interceptor.jakarta.interceptor-api-1.2.5.jar universal/org.slf4j.slf4j-api-1.7.36.jar universal/io.smallrye.common.smallrye-common-classloader-1.13.2.jar universal/io.smallrye.config.smallrye-config-core-2.12.1.jar universal/io.smallrye.common.smallrye-common-io-1.13.2.jar universal/io.smallrye.config.smallrye-config-2.12.1.jar universal/jakarta.transaction.jakarta.transaction-api-1.3.3.jar universal/org.wildfly.common.wildfly-common-1.5.4.Final-format-001.jar universal/io.quarkus.quarkus-development-mode-spi-2.14.0.Final.jar universal/io.quarkus.arc.arc-2.14.0.Final.jar universal/io.smallrye.common.smallrye-common-annotation-1.13.2.jar universal/jakarta.enterprise.jakarta.enterprise.cdi-api-2.0.2.jar universal/io.quarkus.quarkus-picocli-2.14.0.Final.jar universal/io.github.crac.org-crac-0.1.1.jar universal/io.smallrye.common.smallrye-common-function-1.13.2.jar universal/io.quarkus.quarkus-core-2.14.0.Final.jar universal/org.jboss.threads.jboss-threads-3.4.3.Final.jar universal/io.quarkus.quarkus-bootstrap-runner-2.14.0.Final.jar universal/org.jboss.logging.jboss-logging-3.5.0.Final.jar universal/org.jboss.logging.jboss-logging-annotations-2.2.1.Final.jar universal/io.smallrye.common.smallrye-common-expression-1.13.2.jar universal/jakarta.inject.jakarta.inject-api-1.0.jar
Exception in thread "main" java.lang.module.FindException: Module org.reactivestreams not found, required by io.smallrye.mutiny
	at java.base/java.lang.module.Resolver.findFail(Resolver.java:877)
	at java.base/java.lang.module.Resolver.resolve(Resolver.java:191)
	at java.base/java.lang.module.Resolver.resolve(Resolver.java:140)
	at java.base/java.lang.module.Configuration.resolve(Configuration.java:422)
	at java.base/java.lang.module.Configuration.resolve(Configuration.java:256)
	at jdk.jdeps/com.sun.tools.jdeps.JdepsConfiguration$Builder.build(JdepsConfiguration.java:564)
	at jdk.jdeps/com.sun.tools.jdeps.JdepsTask.buildConfig(JdepsTask.java:603)
	at jdk.jdeps/com.sun.tools.jdeps.JdepsTask.run(JdepsTask.java:557)
	at jdk.jdeps/com.sun.tools.jdeps.JdepsTask.run(JdepsTask.java:533)
	at jdk.jdeps/com.sun.tools.jdeps.Main.main(Main.java:49)

Environment Information

Operating System: N/A
JReleaser Version: 1.3.1
JDK Version: 11

The following command successfully produces a list of modules
jdeps --multi-release base --ignore-missing-deps --print-module-deps universal/*.jar quarkus-run.jar

🎉 This issue has been resolved in v1.6.0 (Release Notes)

repo: jreleaser/jreleaser


text:
fctx_draw_commands starts failing sometimes

I have a piece of code that gets called on the minute, determines a resource ID, gets the path via fpath_create_from_resource then draws it using fctx_draw_commands.
sometimes the drawing part falls apart, even if the resource ID never changes.
Here's the piece of code
uint32_t weather_icon_resourceid = weather_icons_day[1].resourceid;
if (w_daynight == 1) {
fctx_set_offset(&fctx, FPointI(122+weather_icons_day[w_icon].offsetx-(temp_offset/30), weather_icons_day[w_icon].offsety));
weather_icon_resourceid = weather_icons_day[w_icon].resourceid;
} else {
fctx_set_offset(&fctx, FPointI(122+weather_icons_night[w_icon].offsetx-(temp_offset/30), weather_icons_night[w_icon].offsety));
weather_icon_resourceid = weather_icons_night[w_icon].resourceid;
}
fctx_set_scale(&fctx, FPointI(180,180), FPointI(168,168));
APP_LOG(APP_LOG_LEVEL_INFO, "weather icon resource id is %lu", weather_icon_resourceid);
weather_icon_path = fpath_create_from_resource(weather_icon_resourceid);
fctx_draw_commands(&fctx, FPointZero, weather_icon_path->data, weather_icon_path->size);
and here are two logs
[22:42:01] main.c:237> Redrawing screen
[22:42:01] main.c:339> weather icon resource id is 9
[22:42:01] main.c:388> Steps: 0
[22:43:01] main.c:237> Redrawing screen
[22:43:01] main.c:339> weather icon resource id is 9
[22:43:01] main.c:388> Steps: 0
[22:44:01] main.c:237> Redrawing screen
[22:44:01] main.c:339> weather icon resource id is 9
[22:44:01] main.c:388> Steps: 0
[22:45:01] main.c:237> Redrawing screen
[22:45:01] main.c:339> weather icon resource id is 9
[22:45:01] fctx.c:887> invalid draw command "
[22:45:01] main.c:388> Steps: 0
[22:46:01] main.c:237> Redrawing screen
[22:46:01] main.c:339> weather icon resource id is 9
[22:46:01] fctx.c:887> invalid draw command "
[22:46:01] main.c:388> Steps: 0
[22:47:01] main.c:237> Redrawing screen
[22:47:01] main.c:339> weather icon resource id is 9
[22:47:01] fctx.c:887> invalid draw command "
[22:47:01] main.c:388> Steps: 0
[22:48:01] main.c:237> Redrawing screen
[22:48:01] main.c:339> weather icon resource id is 9
[22:48:01] fctx.c:887> invalid draw command "
[22:48:01] main.c:388> Steps: 0
(once it starts happening this one will go on and on failing and not draw any icon, in the basalt emulator)
[22:47:04] main.c:237> Redrawing screen
[22:47:04] main.c:339> weather icon resource id is 9
[22:47:04] main.c:388> Steps: 21
[22:48:03] main.c:237> Redrawing screen
[22:48:03] main.c:339> weather icon resource id is 9
[22:48:03] main.c:388> Steps: 21
[22:49:03] main.c:237> Redrawing screen
[22:49:03] main.c:339> weather icon resource id is 9
[22:49:03] ault_handling.c:74> App fault! {b4d23fe5-030c-4a72-99e6-a18e84554cf4} PC: 0x1418 LR: 0x806b021
Program Counter (PC)    : 0x1418     /Users/peter/pebble/PJ-Business/watchface/build/../src/main.c:341
Link Register (LR)      : 0x806b021  ???
(this one sporadically happens and will restart the watchface, on actual basalt hardware with firmware 3.9.1)
both of these happen with SDK 3.9
the FPath has been defined at the top of main.c in this line
FPath *p_bt_icon, *p_tick_mark, *weather_icon_path;
attached is the fpath behind resource id 9
0910dn.fpath.zip

Nevermind. I'm a dummy and just now learned about fpath_destroy(). If that solves my problem I'm closing this issue

That was it, I'll show myself out

repo: jrmobley/pebble-fctx


text:
Interface\AddOns\Auctionator\Auctionator.lua:1274: attempt to index global 'AtrScanningTooltip' (a nil value)

Interface\AddOns\Auctionator\Auctionator.lua:1274: attempt to index global 'AtrScanningTooltip' (a nil value)
VERS:3.2.4   MEM: 18440 KB   DB:42305   SE:0  SL:18  FSCHUNK:  DBVERS:4
REALMS: , Burning Steppes_Horde (0), Sylvanas_Neutral (0), Bloodfeather_Alliance (0), Tarren Mill_Horde (0), Ravencrest_Alliance (81), Runetotem_Alliance (0), Sylvanas_Alliance (11793), Sylvanas_Horde (0), Sanguino_Horde (0), Uldum_Horde (0), Ahn'Qiraj_Horde (0), Kazzak_Horde (42305), Vashj_Horde (0), Kazzak_Alliance (0), Magtheridon_Horde (0), Argent Dawn_Alliance (0), Laughing Skull_Horde (0), Vek'lor_Horde (0), Vashj_Neutral (0)
STACK: Atr_GetSellItemInfo > Atr_SetDepositText > Atr_UpdateUI_SellPane > Atr_UpdateUI > Atr_Idle > Atr_OnUpdate
ADDONS: , _NPCScan, Altoholic, Auctionator, CrossRealmAssist, DataStore, HandyNotes, MasterPlanA, MogIt, Postal, RareSpawnOverlay, Redprints, Skada, WeakAuras, JSHB, DBM
Reported by http://www.curse.com/users/comas82 on 9/9/15
http://www.curse.com/addons/wow/auctionator?comment=5676

Duplicates #6


text:
what is outcome = 201 and when does it happen ?

Thank you

Hi, 201 happens when the fact or the event was not captured because it did not match any rule. I just added a section on error codes to the docs:
https://github.com/jruizgit/rules/blob/master/docs/py/reference.md#error-codes

Thank you!

authors: ammarwm jruizgit

repo: jruizgit/rules


text:
Port commits from proposal repo (2024-02-25 tranche)

This PR catches us up to  4345a8cbe90bd140321d31549a0382d3cbf2546b in the tc39/proposal-temporal repo.
Only 173 more commits to go. (!!!) Thankfully only a fraction of those are polyfill commits, so hopefully it won't be too heavy of a lift.  Probably only 3-4 more PRs like this one.

Ah shoot, I merged this PR without remembering to autosquash the three fixup commits. Sorry guys!

repo: js-temporal/temporal-polyfill

license: isc


text:
Use JSBI instead of big-integer

JSBI has the following advantages over big-integer:

it has better type-safety and mirrors native BigInt behavior (cannot mix native BigInt and number)
has a babel plugin (not configured in this PR) that can transpile away JSBI entirely to use native BigInt instead, for code-size improvements. We should consider shipping a separate package (maybe this should be the default) using this that provides all the Temporal features and uses native BigInt, as I'd guess this will be more common than users wanting to use this on platforms without native BigInt.

JSBI has some disadvantages:

the JSBI.BigInt factory function does NOT support automatically converting native BigInt to a JSBI instance at runtime. Instead, in places where the type might be a native BigInt, we use ES.ToBigInt to convert to a JSBI instance.
does not feature-detect platform availability of BigInts and return those instead of JSBI instances, in the event that a user doesn't use the Babel plugin. We do this ourselves instead with ES.ToBigIntExternal, which guarantees it returns a native BigInt when available, and something with a ToString method that returns the base 10 value of the bigint as a string, which I think is likely the most straightforward way for interop between various bigint compatibility libraries. It would be great if there was a way to properly encode this in typings, and this might be possible with multiple entry points and typesVersions.

Now that we've released, I plan to merge this unless there's any other concerns?

Assuming nothing substantial changed in the meantime, no concerns from me!

Not from me either!

This has actually been surprisingly smooth - I haven't had many problems rebasing it over the past several weeks.

authors: 12wrigja justingrant ptomato


text:
Uncaught (in promise) DOMException: Only secure origins are allowed

Runner stops working after a while using chromium (53.0.2785.116 (64-bit) or arch linux).
This is the URL attached to the error:
https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features
Looks like something to do with loading the service worker.
I tried firefox as well and I get SecurityError: The operation is insecure..

Do you have an example bin url?

Sure.
https://jsbin.com/wegizaf/2/edit?output
I ran it locally and it worked fine.

authors: hakib remy

repo: jsbin/jsbin


text:
🛑 Tandoor is down

In 1735d83, Tandoor ($SERVER_BASE/recipes/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tandoor is back up in 5ed8068.

repo: jscmidt/upptime


text:
🛑 Nextcloud is down

In 37ee581, Nextcloud ($SERVER_BASE/nextcloud/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nextcloud is back up in 5e4369b.


text:
🛑 Piwigo is down

In 84bba6f, Piwigo ($SERVER_BASE/piwigo/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piwigo is back up in 7226a31 after 541 days, 22 hours, 10 minutes.


text:
🛑 Linus-Wordpress is down

In 4676bf5, Linus-Wordpress ($SERVER_BASE/wordpress/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Linus-Wordpress is back up in 1f51cbb after 10 minutes.


text:
🛑 Linus-Wordpress is down

In 6e2d16f, Linus-Wordpress ($SERVER_BASE/wordpress/) was down:

HTTP code: 404
Response time: 121 ms

Resolved: Linus-Wordpress is back up in beec4b3 after 19 minutes.


text:
🛑 Grafana is down

In 70ee2a6, Grafana ($SERVER_BASE/grafana/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grafana is back up in 0b7a3dc.


text:
🛑 Grafana is down

In c27783e, Grafana ($SERVER_BASE/grafana/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grafana is back up in ee6e2c6 after 10 minutes.


text:
Auto formatting API and option. [$300]

JSCS should have the ability to automatically format a given file with the specified rules. There are several challenges here:
For now, we are only going to consider whitespace changes. This approach is outlined here:

Change all rules to use the JsFile traversal methods instead of directly referencing the token by index directly. This allows us to change the underlying token data structure at will while only having to change the traversal methods.
Make all whitespace only rules use the token-assert framework.
Modify the token list so that it includes comment tokens, and a new terminal token called "EOF".
3a. Modify traversal methods to ignore comment tokens as necessary.
Modify comment tokens to include a property called "prefix", which contains the preceding whitespace.
Add a function called errors.fixToken (or some other name), which takes in a token, and the updated prefix whitespace, which modifies the prefix of that token.
Make token-assert call errors.fixToken appropriately.
Modify StringChecker so that it can output the modifed source and save it to disk. It's simply a loop over the token list, printing the prefix followed by the value of the token.
Modify CLI to respect a --fix parameter, which triggers the autoformat option.

Please see https://github.com/mdevils/node-jscs/pull/514 as one possible implementation that ultimately wasn't how we wanted to approach the problem.

There is a $300 open bounty on this issue. Add to the bounty at Bountysource.

So #751 was merged, introducing the infrastructure for autofixing, but not the autofixing itself, is that right? Does someone have plans to work on the next step? If not, would a bigger bounty make a difference?

Yes, it's the next thing im working on. Bounty makes no difference here.

That's awesome @mikesherov! I didn't realize #752 was merged. Is there a running list of rules that need formatters? Now that the API is defined I could help write a few.

hi there
i found this in my inbox:
https://github.com/soliton4/nodeMirror/issues/18
would be a totally cool feature, but it looks like the formatting option is still under construction.
is there any part of it usable and can you point me to a working piece of code?
i basically need the option to input text and get formated text as output.
thank you very much ;D

Hey @mikesherov I'm super interested in this too. Is there any branch I should be watching where this is happening? I would be interested to see how you are thinking about this and see if I can help out!

@jdlrobson and @indexzero, the most helpful thing you can do is review all existing rules and make sure spacing and line break rules are all using the file.assert methods. Those will be the first to get fixed.

Just updated the description with full outline of the approach:

Change all rules to use the JsFile traversal methods instead of directly referencing the token by index directly. This allows us to change the underlying token data structure at will while only having to change the traversal methods.
Make all whitespace only rules use the token-assert framework.
Modify the token list so that it includes comment tokens, and a new terminal token called "EOF".
3a. Modify traversal methods to ignore comment tokens as necessary.
Modify comment tokens to include a property called "prefix", which contains the preceding whitespace.
Add a function called errors.fixToken (or some other name), which takes in a token, and the updated prefix whitespace, which modifies the prefix of that token.
Make token-assert call errors.fixToken appropriately.
Modify StringChecker so that it can output the modifed source and save it to disk. It's simply a loop over the token list, printing the prefix followed by the value of the token.
Modify CLI to respect a --fix parameter, which triggers the autoformat option.

@jdlrobson @indexzero help with 1. and 2. would be greatly appreciated.

@mikesherov, is referencing lines by index a problem? There are also a few rules that are using _operatorIndex.

@TheSavior, operatorIndex is unrelated. Good question though.

i dont know if this is any help to you but i post it anyway.
nodeMirror has a early version of the formatter integrated now. jscs can also be selected as linter. that way its easy to see how well the formatter works.
let me know if this was helpful
also keep me updated if i should pull a new version of the formatter

Here wo go: #1058

@mdevils, let's track what's left:

Saving file in case of not stdin.
Autofixing for validateIndentation.
Strategy for non whitespace fixes.
Converting remaining rules.

Anything else?

Can you give an example of a reasonable non whitespace thing we could fix?

@TheSavior the multipleVarDecl rules. We don't need to solve it now, but we have the come up with something like @gero3's strategy of direct source manipulation followed by AST rebuild or figure out how to manipulate an existing AST.

My intuition says that all of the iterative solutions we are considering are the easy first approach, but won't be robust long term for all possible 'fixes' rules might want. I would think we need a way to have some sort of engine that understands what the rules are doing and could know if any of the rules conflict.
At that point, we would be able to take in a parse tree of a file and step through it applying the applicable rules and convert it step by step into actual code.

Saving file in case of not stdin.

What do you mean? Current implementation saves changes into files.

I must've missed that!

Strategy for non whitespace fixes.

It can be fixing in place if we already doing it in assertion. But I feel like it becomes a mess because of high cyclomatic complexity in some rules.

Strategy for non whitespace fixes.

I think we can leave this as is and focus on whitespaces first.

:+1:

Do we have a strategy for disallowMixedSpacesAndTabs or disallowTrailingWhitespace? Also whitespace related to alignment like requireAlignedObjectValues.
Other whitespace rules (should be the last ones)

[ ] disallowMultipleLineBreaks
[ ] disallowSpaceAfterLineComment, requireSpaceAfterLineComment
[ ] requireLineFeedAtFileEnd

I'l do a PR for requireSpaceBeforeKeywords.

so @jzaefferer just told me about the plan to add formatting to jscs. To be really honest, I would love to see someone else solve this problem for me since I'm not having that much time to work on esformatter and have other priorities in life at the moment... but for what I could see you guys are moving towards a dead end and underestimating the complexity of this problem.
Handling white space is the easiest part of code formatting by far; adding/removing line breaks is tricky (child nodes affects the parent nodes structure) but indentation is the real challenge; specially if you want to support multiple code formats.
There are many reasons why esformatter works the way it does, and today I added some info describing how/why we transform and indent the code that way; it might be worth the read.
I did not spend too much time looking at how you're implementing the autofix but it looks like most of the rules are line based, if that is really the case you will have a really hard time when you try to add/remove line breaks and implement proper indentation. There are so many edge cases that it's basically impossible to handle it all in a single step (indentation should always be the last step otherwise it will be wrong for sure).
I would love if more people contributed to esformatter (fixing what is currently broken) and actually created a plugin to convert the jscs config file into a format that esformatter can understand. I honestly think it would save a lot of headaches to all the people involved.
Nowadays I would even implement esformatter in a different way but some changes would require so much work that it is definitely not worth doing (like building a proper CST instead of using an enhanced AST).
Until I find something that works better than esformatter, or stop using JavaScript, I'll keep developing it, even if it takes forever to finish... - any help is highly appreciated, pull requests with reduced test cases and bug reports are extremely helpful (code is only as good as the tests).
Good luck!
PS: the using the assertion is really the best abstraction that I could think about, it's very similar to how I handle it on esformatter with ws.limitBefore(token, tokenIdOrValue) and ws.limitAfter(token, tokenIdOrValue) - limiting line breaks is way more complex since you might have comments and white spaces in between but I also abstracted the logic the same way...

@millermedeiros Not to speak for the rest of the team, but I really appreciate you coming to provide us this context. Having built esformatter, you definitely have some specific understanding that we may not have.
The assertions we use and having that add whitespaceBefore, as you say, seems pretty consistent with how you have things outlined in the file you linked.
Something I didn't quite get from your document explaining how esformatter tokenizes and how you guys transform, are specific examples.
I'd love to get some more understanding and specific examples that you've run into issues with once we try to tackle indentation. I don't believe we have taken any steps in that direction yet.

@TheSavior there are a lot of edge cases related to indentation, specially for complex nodes like IfStatement, FunctionExpression and CallExpression
There is also the problem of chained member expressions and how they should be handled, specially if you think about the jQuery style guide when special methods cause negative indents...
There are some crazy rules about what should be start/end of the indentation in some cases, specially since we might have optional parenthesis and curly braces...
I'm nailing down one bug at a time, but some problems are very hard to solve if all you have is the line number and/or a vague AST structure. In many cases you need to understand the actual code context and work around the AST limitations.

@TheSavior our token list is a LinkedList and not an Array, so it's very trivial to add/remove items in between (we don't use the context of indexes.. we just edit the LinkedList in place) - every token have a reference to the prev and next tokens, so to add/remove you just need to update the references to prev/next on the adjacent sibling tokens. Every node on the AST also have a reference to the startToken and endToken to make it easier to traverse.

@millermedeiros, you're welcome to help help us solve the problem here in JSCS just as much as we're able to help you in esformatter. I appreciate the concern about the dead end, but I think it's most unfounded if you haven't taken the time to read all we've said about it on our mailing list and in our various issues. If you're truly interested in having someone else solve the problem, and think that esformatters current impl is suboptimal, we should work together here in JSCS to get this done. In regard to specific critiques:
Linked list for token insertion is a must. We just aren't there yet. Our abstraction makes it pretty trivial to add when we finally tackle that problem. Note that we're also working with Esprima and the estree project to attempt to move forward the CST at some point soon so that something like rocambole or what we do now (basically the same work) is available directly from an esprima parse.
As far as indentation goes, I think I have a pretty good grasp on the edge cases, and I'd invite you to read what my existing pull request for autofixing indentation tries to accomplish. It has matured over a long period of time and is fairly lenient in what it enforces. Would love specific feedback there.

@millermedeiros, I'd also like to mention that the negative indentation problem for chained method calls is one of concern but is literally no different then any something like switch/case indentation.
Again, I'd invite you to check out our validateIndentation rule and see how it works before you dismiss it.
With regards to having to do indentation last, that's also a bridge that we may have to come to, but I doubt it. As long as the rules that modify number of lines preserve indentation, it shouldn't matter. But again, we'll see when we get there, and I think JSCS's infra is robust enough to handle that chabge should it be needed to do it last (which is something I suspected, but am not convinced).

@millermedeiros, lastly, I want to just say that personally, we could use your help on JSCS. Is love for us to consider merging the two projects.
No one is telling you to give up on esformatter, and you should continue working on it to your heart's content, but I've seen you express doubt to as to its design and lament its pace of development.
We've tried to build an inclusive, contributor friendly codebase here, and I think JSCS's momentum and contributor base make it the project we should all be working on instead of in esformatter.
Again, you're welcome to do whatever you like, and we appreciate the input and feedback you've given us, so even if you decide to continue developing esformatter into the foreseeable future, no big deal. But I think we could solve more problems together rather than apart and I think JSCS is in a better place at the moment to handle the task. Of course, I could just be biased.
Let me know what you think.

@mikesherov I feel glad for the invite to help on jscs and join forces but I will probably just keep working on esformatter instead. Time is a very limited resource and there are different user needs to be filled.
The design flaw I regret most on esformatter is that I should have built a real CST since the beginning with good helpers for code manipulation; making sure that the CST was as easy as possible to modify (giving more power to plugin authors) and with saner node boundaries - having to search for all the tokens is cumbersome and parenthesis makes things weirder. The main reason why I did this way was because I thought that the tool would only handle white spaces and line breaks, but current plugins are showing that people actually want it to fix other issues as well (quotes, braces, semicolon, etc). I should have also delegated more work to plugins and/or separate libs since the beginning. - jscs structure is no different from that and while you implement code formatting it should become even more similar (eg. start using linked lists).
We are basically approaching the problem starting from 2 opposite directions - I was initially thinking about writing a tool that does basic string diff between esformatter input/output to validate the code style, while jscs uses the validation to correct the differences...
I'm confident you guys will find a solution to all the problems given enough time, just wanted to give a heads up; keep the good work!
PS:  Maybe this idea of having a competitor will motivate me to move faster :D

@millermedeiros thanks for the thoughtful reply. At the very least, perhaps you can help contribute to the CST discussion in the estree repo once that gets underway... as the atuhor of Rocambole, your input is invaluable there.

FYI I resumed esformatter development and closed 20 issues this week (all the reported bugs that we had) and just published v0.5.0 to npm. v0.6 is coming soon with lots of improvements. I promise I won't spam in the next releases, just thought it was a good idea to share in case you guys change your minds and decide to reuse it (or at least decide to borrow some of the test cases). cheers.

Congrats. Good luck with the continued development of your project.

I just put up a sublime plugin that uses the globally installed JSCS version to autoformat your code.
https://github.com/TheSavior/Sublime-JSCS-Formatter
I'm going through the process to get it added to Sublime's Package Manager right now: https://github.com/wbond/package_control_channel/pull/4148

@TheSavior you truly are the savior :)

@TheSavior, awesome work! Would you mind waiting until 1.12 is released before submitting that package? I wouldn't want users to get confused.

@mikesherov Sure thing. This is my first sublime plugin and I really have no idea what I'm doing, so I wanted to jump through the hoops now to get things cleaned up.
If any of you use sublime and know python or want to explore the world of plugins, I would really appreciate any pull requests people have time for. :)

@mikesherov looks like great progress here! I read the comments a bit and saw all the referenced commits for each rule 👍
... is there a place listing all the rules and which ones still need autofixing added? A checklist somewhere would be super helpful. I've finally got a little time and would love to pinch hit and knock a few out.

@indexzero only whitespace, eof and indentation rules are supported at the moment, there is no clear way to support others, more specific rules like disallowAnonymousFunctions or disallowCommaBeforeLineBreak, etc.
Right know, we thinking, either specific assertions for every rule or this.

@indexzero disallowMultipleLineBreaks still needs conversion.
Also, the (no)whiteSpaceBetween rule need to be fixed so that if a comment token exists between the two provided tokens, don't attempt to autofix. See the linesBetween rules for prior art there.
If you can get PR's going for that, I think we're in a fairly good place, and can discuss releasing 1.13, which has the goal of fixing whitespace only.

@indexzero also discovered requireAlignedObjectValues needs conversion as well.

Are changing those 4 rules all that is left before releasing 1.13?

Autofix has been landed, other updates will be iterative, so if no one object, i would like to close this one. Will wait until tomorrow.
As a team, we decided to donate this money to charity organization "Girls Who Code" - https://girlswhocode.com.
Thank you everyone!

Great news everyone :+1:

i agree
is there a api documentation available yet?

@soliton4 Docs in progress: #1231 #1192
There are the very first try also: #1202

Experimenting with this in our build tool and very excited about the possibilities! But now of course we want more ;)
What about non-whitespace fixing? I imagine/hope it shouldn't be too hard to fix errors related to comma's and semi-colons. E.g: anything where the error message is already pointing exactly at where a certain character is missing or should not be.
Are you guys working on this already and should we just add some bounty and/or how can I contribute?
PS: Personally I disagree with people who would like to see this developed in a separate project. Fixing is a core feature. Having software tell you exactly what you did wrong and then subsequently not helping you save time by fixing it seems a bit masochistic to me. It's just like an annoying teacher who keeps hitting you on your fingers every time you make a mistake instead of an assistant that smoothes things out for you.

@dfilatov #1202 — I think the battle begins ;-)

@difosfor https://github.com/jscs-dev/node-jscs/issues/1113 has potential, but there is concern of providing API for modifying AST, since there is obvious danger in that way.
We have this - https://github.com/jscs-dev/node-jscs/issues/1086 as at least one element of protection from ruining your code.
We need to be very careful here.

@markelog can we close this?

This solution was worked on by many individuals in the community. Together, we have decided that the bounty should go to charity: https://groups.google.com/forum/#!topic/jscs-dev/u-Gy0Yh97EU.
As a core team member, I was nominated to handle claiming the bounty, donating the money, and posting a donation receipt on the issue to notify the community of the donation. I will post status updates on this issue to stay transparent until the donation receipt is posted.
To start the claiming of the bounty, I need to close the ticket.

The bounty will be paid out if all backers accept your claim or if no backers reject your claim by May 28, 2015 8:19 AM (GMT).

I'll check bountysource on the 28th (or sooner if all backers accept the claim) to proceed with the next steps.

The bounty was awarded.

I've requested to be paid via paypal.

Bountysource took a $31 cut from the funds. That left a balance of 284 (315 - 31).

👍💪🙌

Getting it transferred to my bank and will then donate that money. Everyone wants a cut of the funds, it seems. Not even charity gets a break from fees!
Will post a donation receipt once that's done.

Just a quick update. The money has reached my account. I'll donate it on Wednesday and post a receipt.

Donation complete. Thanks again to everyone who contributed to the effort.

authors: TheSavior difosfor hzoo indexzero jdlrobson jzaefferer markelog mdevils mikesherov millermedeiros mrjoelkemp soliton4 varemenos zxqfox

repo: jscs-dev/node-jscs


text:
requirePaddingNewLinesAfterBlocks: consider IIFE case

Fixes #1555

Is this ready for review?

Yeah, it seems travis failure is another coveralls trick

LGTM

authors: markelog mrjoelkemp


text:
Update: .editorconfig - fix for invalid indent_style value

@mikesherov
indent_style value - spaces is not valid,
changed to space

Coverage remained the same at 98.75% when pulling c2825ea6fad2509e48b1a7eb2407602d933c8ef6 on valorkin:patch-1 into df7474c1c3adc8ee501b82097f9e7a43f8c519a0 on jscs-dev:master.

Thank you!

authors: coveralls markelog valorkin


text:
E030 and E033 related to typeof definedness check

I've seen the following idiom in minified code (minifier unknown):
"undefined"==typeof a&&(a=1);

This raises a surprising number of warnings and errors:
line 1, col 12, Missing semicolon. (W033)
line 1, col 12, Expected an identifier and instead saw '=='. (E030)
line 1, col 14, Expected an operator and instead saw 'typeof'. (E033)
line 1, col 14, Expected an assignment or function call and instead saw an expression. (W030)
line 1, col 20, Missing semicolon. (W033)
line 1, col 28, Expected an assignment or function call and instead saw an expression. (W030)

6 errors

Even the fully parenthesized version
("undefined"==(typeof a))&&(a=1);

still yields one warning:
line 1, col 32, Expected an assignment or function call and instead saw an expression. (W030)

but that is probably acceptable, and even more importantly, can be suppressed using suitable comments. The errors however can not be suppressed.
And at least to me they indicate that the parser got something fundamentally wrong about the semantics of this expression. The typeof from UnaryExpression binds stronger than the == from EqualityExpression which in turn binds stronger than the && from LogicalANDExpression. At least at first glance, it seems as if the Pratt parser in JSHint should reproduce this, since it apparently has priority 150 for prefix, 100 for == and 50 for &&. But apparently things don't work that way despite these priorities.
Trying to understand the problem, I tried other partially parenthesized forms.
("undefined"==typeof a)&&(a=1);

is back to the single warning, so apparently that gets parsed correctly. However,
"undefined"==(typeof a)&&(a=1);

gave even more problems:
line 1, col 12, Missing semicolon. (W033)
line 1, col 12, Expected an identifier and instead saw '=='. (E030)
line 1, col 14, Expected an operator and instead saw '('. (E033)
line 1, col 15, Expected an operator and instead saw 'typeof'. (E033)
line 1, col 15, Expected an assignment or function call and instead saw an expression. (W030)
line 1, col 21, Missing semicolon. (W033)
line 1, col 22, Expected an assignment or function call and instead saw an expression. (W030)
line 1, col 23, Missing semicolon. (W033)
line 1, col 23, Expected an identifier and instead saw ')'. (E030)
line 1, col 24, Expected an operator and instead saw '&&'. (E033)
line 1, col 26, Expected an operator and instead saw '('. (E033)
line 1, col 26, Expected an assignment or function call and instead saw an expression. (W030)
line 1, col 27, Missing semicolon. (W033)
line 1, col 30, Missing semicolon. (W033)
line 1, col 30, Expected an identifier and instead saw ')'. (E030)
line 1, col 30, Expected an assignment or function call and instead saw an expression. (W030)

16 errors

I was experiencing the same annoyances until I found the expr option.

I just stumbled across this report--sorry we've let it sit for so long. I can
reproduce it reliably on the master branch with the following input:
// jshint expr: true
"" === typeof 0;

Output:
gh-1988.js: line 2, col 4, Missing semicolon.
gh-1988.js: line 2, col 4, Expected an identifier and instead saw '==='.
gh-1988.js: line 2, col 8, Expected an operator and instead saw 'typeof'.
gh-1988.js: line 2, col 14, Missing semicolon.

Strangely, the left-hand side of the equality operator must be a string
literal--numeric literals, RegExp literals, identifiers, null all parse
correctly.

The string is parsed as a statement: this code is linted correctly
0;
"" === typeof 0;

A simpler repro case is "" === "";

This might be fixed by #2716 (I haven't tested it)

This was indeed fixed by gh-2716 and subsequently released in JSHint version
2.9.3. Thanks for reporting!

authors: gagern jugglinmike nicolo-ribaudo ryneeverett

repo: jshint/jshint


text:
[[FIX]] The __iterator__ property is deprecated.

It should be used Symbol.iterator.
Now JSHint throws W103 instead of W104.
(https://developer.mozilla.org/it/docs/Web/JavaScript/Reference/Deprecated_and_obsolete_features#Object_methods)

Good to land when green!

Coverage remained the same at 96.53% when pulling 0ce41e36898ba628c0b93962adcc4bd1b95667e5 on nicolo-ribaudo:deprecated-iterator into e22b21a7bfeed9d1e38d0ed578c787aa9276690b on jshint:master.

What does this Travis CI error mean?
=============================== Coverage summary ===============================
Statements   : 96.53% ( 3703/3836 )
Branches     : 94.31% ( 2835/3006 )
Functions    : 96.9% ( 313/323 )
Lines        : 96.56% ( 3678/3809 )
================================================================================
[error] "2015-05-11T13:47:20.543Z"  'error from getOptions'
/home/travis/build/jshint/jshint/node_modules/coveralls/bin/coveralls.js:18
        throw err;
              ^
Error: Command failed: /bin/sh -c git cat-file -p a3abdb365ee8fa2097095794ef81fb5d7b66779f
fatal: Not a valid object name a3abdb365ee8fa2097095794ef81fb5d7b66779f
    at ChildProcess.exithandler (child_process.js:751:12)
    at ChildProcess.emit (events.js:110:17)
    at maybeClose (child_process.js:1015:16)
    at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
The command "npm run coverage && cat ./coverage/lcov.info | coveralls" exited with 1.
Done. Your build exited with 1.

it means it flaked

This has been annoying us for a little while now. I just opened gh-2378 -- hopefully that will address the problem.

Rebased to include #2378 (because of travis-ci's failure)

committed - 7780613e74d84a992098734350ca11a3ad52bce3 - thanks.

authors: caitp coveralls jugglinmike lukeapage nicolo-ribaudo rwaldron


text:
Input with autocomplete and custom value?

Hi,
is it possible to have a Choices element with options added to it but also the possibility to enter a free value if it is not available in the list of options?
To describe it a little more, I'd like to start typing in a Choices component and a dropdown with predefined options is shown. I can select an option in the dropdown. But if the option I want is not there, the text that I typed in the Choices should be submitted to the form.
Thanks for your reply.
Bart

Hey @bartlenaerts,
Currently that isn't possible but it has been requested before. There is a feature branch for it but it's proven more complicated than I expected!
Thanks

@bartlenaerts did you find an alternative that can do what you've described? I'm needing same feature

No sorry, no solution yet. We are using aurelia and are looking to build our own 'choices' as a native aurelia plugin.

authors: bartlenaerts jshjohnson miguelmota

repo: jshjohnson/Choices


text:
🛑 PlayYourPride is down

In afd1e96, PlayYourPride (https://playyourpride.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PlayYourPride is back up in c2312f4 after 12 minutes.

repo: jshwlkr/upptime


text:
AudioPlayerManager additional API methods

Added AudioPlayerManager support for unpause, get duration, set progress subscription, and set current time,
These additions allow for the creation of an audio player that can:

Display the current playback time of the playing audio
Display the length (duration) of an audio file
Unpause paused audio
Navigate/Scrub/Seek to a specific point in an audio file

If PR is accepted, I'll improve the sample project to demonstrate an AudioPlayerManager with these new features and also add to documentation.

Looks great! Thanks for putting in the effort.

authors: LennonR jsierles

repo: jsierles/react-native-audio


text:
New project mystery

Hi!   Yes, so your existing example project tests ok.
However, when I create a new Unity 2018.2 project (OS X), adding your .cs files, and adding the three asset dirs results in Visual Studio error on:
using Grpc.Core;
I can't figure out why you example project works while a newly-created one doesn't.  I tried adding three dirs to the .csproj xml but they just get removed and nothing changes.

Have you extracted the zip file from releases in Assets/Plugins folder ?
Maybe check that the Scripting Runtime Version is set to .NET 4.x equivalent.
What is the exact error from Visual Studio ?

repo: jsmouret/grpc-unity-package


text:
Fieldsets should be defined per resource path instead of resource type

This is a significant limitation of the existing spec.
If I do a request to a repo resource and want to get multiple related sets of users for each repo in the same request, say, owner, collaborators, watchers, and/or organization.members, there is no way to have a different sparse fieldset for each set of users.
Fields should be able to be defined as fields[owner]=&fields[organization.members]= instead of fields[user].

Each resource can appear only once in a document, even if it is referenced by multiple relationships. That's the rationale for specifying fieldsets by type instead of path.

I see, thanks.  Have you considered allowing the option to return full related documents inline for each related set in addition to the current option to return them all at the top-level and use resource identifier objects in order to support this use case?
Top-level storage with identifiers potentially reduces query/response size, and makes it easy to ensure that only one client object is created on the client even if there are multiple instances of an object in the JSON, but if you can use a library like Backbone-relational that avoids duplicates by identifier by default, or make your custom consumer do that.
Say I want to get all the data for a user page that shows the all the user's details and just their followers' names and location all at once.  If user has 10 fields then doing this all in one query currently will return a significant amount of unnecessary data.

@mwhite The problem with your outlined solution is that it does not specify what happens in case of cycles in your data graph.

True, that would result in unnecessary output duplication for cycles in cases like user.followers.followers.followers.  I guess allowing nested related documents is orthogonal to returning different fields for different paths to the same type.
The request format fields[owner]=&fields[organization.members]= could be supported with no changes to the existing response format, with the fields returned for each top-level object being the union of the fields for each path at which that object occurs.

The idea of a query parameter that restricts fields by relationship path, rather than by type, has come up a few times, and I think it's something we're generally sympathetic to as a possible extension. (If the same resource appeared at multiple paths, its fields would be the union of all the path-based fieldsets applied to it, as @mwhite suggested.) For backwards compatibility, we'd probably have to add a new query parameter to support this, but it wouldn't be hard.

In your examples you haven't specified what the field selection of the main resource of the request would look like. There is no way to define this using a path because it is the "root". Would we just use a fields=name without square brackets?
i.e. repositories?fields=name&fields[owner]=last-name

authors: beauby dgeb ethanresnick maurei mwhite

repo: json-api/json-api


text:
Non empty interface unmarshal crashes

eg:
package main
import (
	jsoniter "github.com/json-iterator/go"
)
type MyInterface interface {
	Hello() string
}
type MyString string
func (ms MyString) Hello() string {
	return string(ms)
}
type TestObject struct {
	Field []MyInterface
}

func main() {
	obj := TestObject{}
	b := []byte(`{"Field":["AAA"]}`)
	jsoniter.Unmarshal(b, &obj)
}

it will return error instead of panic now. same as the std lib

authors: sreekanth-cb taowen

repo: json-iterator/go


text:
Delete i'th item in array

It appears that you can only delete the last item in an array. This seems like a bug as one of the earlier playgrounds allow for deletion of any item in an array. Is it possible to restore this functionality as it seems like it would be quite useful to have (other json form projects also have this functionality).

Hello
Can you give me an example schema so I can test that ?

https://jsonform.github.io/jsonform/playground/index.html?example=schema-array
Add a couple items to the array. You will be able to move items around but cannot delete any but the last item. This functionality was present in an earlier version.

I don't recall a time when we could delete the _n_th item in an array in this lib. Do you have an idea as to which commit would have introduced this regression ?
There has not been any changes on this particular feature over the past year I think.

authors: qstevens tchapi

repo: jsonform/jsonform


text:
Clarification on dataclasses, functools.partial, py/state

Hi all,
I've been debugging an issue in my application where jsonpickle was serializing some custom dataclass objects (where I make a new decorator with functools.partial) as empty, eg:
{
  "py/object": "some.module.path"
}

I think I've identified a small PoC to show why this might be happening, but couldn't reproduce the empty object behavior. Curiously, when working with nested structures of these dataclass objects, the "py/state" key is nowhere to be seen, though I could not reproduce this in a minimal example
Here's the PoC code, using just jsonpickle and stdlib:
import functools
from dataclasses import dataclass

import jsonpickle

@dataclass
class Foo:
    bar: int

print(jsonpickle.dumps(Foo(bar=1)))   # {"py/object": "__main__.Foo", "bar": 1}

dafsaclass = functools.partial(dataclass, slots=True, kw_only=True, frozen=True, init=True)

@dafsaclass
class Flew:
    baz: int

s2 = jsonpickle.dumps(Flew(baz=3))
print(s2)  # {"py/object": "__main__.Flew", "py/state": [3]}
print(jsonpickle.loads(s2))  # Flew(baz=3)

Any ideas on why that might be happening, and if there might be a solution with a custom encoder?

Hey, sorry for not getting back to this sooner. I wasn't able to make any progress on solving this after around 6-8 hours of work back in late May unfortunately, but I believe I was able to reproduce it (not the empty object version though, as you said). I might be able to put more time into this in mid August, but it's also quite possible that I won't have the time. Have you come across any more information about the potential cause or more ideas as for a potential fix in the meantime, or did you have to move on?

The functools partial was for pydantic migration that I ended up tabling, but I would be curious about this! I think one possible avenue of attack would be to understand why Flew uses py/state while Foo uses py/object. I bet if there was some way to force it to use py/object, my own application would work!
Lmk if I can help with providing more examples

authors: Theelx ijustlovemath

repo: jsonpickle/jsonpickle


text:
Validation for category key in iat-html

Presently, you can set both of the category keys to be the same key in the iat-html plugin.  There should be some sort of warning to prevent users from doing this.

Moving to GUI repository issues. 174

authors: jodeleeuw jpellman

repo: jspsych/jsPsych


text:
Add @root virtual binding

For helping those migrate off of handlebars we will add a virtual binding of @root.
Thanks @SerayaEryn for the idea!

https://github.com/jstachio/jstachio/commit/9c66d4a4f4c963d3e0824015a79bcb24d257a391

repo: jstachio/jstachio


text:
Center navbar with dropdown component in tailwindCSS

Description
**Need to create code for Center navbar with dropdown component as per below image. **

The final code should be placed under path tailwind_components/navbars with file name as center_dropdown_navbar.jsx
The file as to be imported to tailwind_components/navbars/collection.js file as per example and added to the navbarCollections list
Post these process, go to components tab (components/navbars) in website and check whether the codepen is updated
Color palete and design is upto creativity

For PR reference - https://github.com/jsvigneshkanna/tailwind_ui_components/pull/76/files
For any issue while creating / importing the component code file, check below sample files
https://github.com/jsvigneshkanna/tailwind_ui_components/tree/master/tailwind_components/buttons
For icons please refer - https://heroicons.com/
Screenshot of the tailwind component

Are you taking this fetaure implementaion
No, This is up for grabs

HI @jsvigneshkanna I can work on this too. Can you assign me please?

Sure @uttampandit , please make sure all 3 PRs are raised

Yeah I will

Hi @uttampandit ,
Just a reminder, you have 3 issues to be solved

Yes sure I am working on it

Sure @uttampandit

authors: jsvigneshkanna uttampandit


text:
Control form on smartphone

layout of the controls do not fit well when displayed on a smartphone

layout adapted

repo: jtbgroup/kodi-search-card


text:
Some menus created without items

Some importers seem to create menus even if there are no menuItems to add.
To keep everything nice and clean, those menus need to be deleted or not created in the first place.

Most likely fixed with 0.2.0

repo: jtiala/lunchwatch-api


text:
Update to JupyterLab 2.0

JupyterLab 2.0 is coming soon, and we can start upgrading to it:

switch to lumino
kernel refactoring: use of sessionContext

Link to the migration guide: https://jupyterlab.readthedocs.io/en/latest/developer/extension_migration.html

repo: jtpio/jupyterlab-extension-examples


text:
Optional visual switch

Fixes #4.
The visual switch is now optional while keeping the keyboard shortcut available.
To install without the topbar extension:
jupyter labextension install jupyterlab-theme-toggle

cc @tbrodbeck

Released 0.4.2 with this change. To update:
jupyter labextension update jupyterlab-theme-toggle

repo: jtpio/jupyterlab-theme-toggle


text:
Move file browser lab plugins to a separate file

Move the file browser lab plugins to a separate file, so it's easier to remove them when the upstream plugins are more reusable.
See https://github.com/jupyterlab/jupyterlab/pull/9667 for more information.
The plugins currently in labplugin.ts are a subset of the refactored ones from https://github.com/jupyterlab/jupyterlab/pull/9667

Closing in favor of #127.

repo: jtpio/retrolab


text:
Add support for creating and retrieving posts

Summary

A post is created with the contents of the post and a signature of the post via the user's wallet
Add a Post structure which holds

The address of the creator
The contents of the post
The signature of the post, which is considered to be the ID of the post

The contract stores a mapping of post signatures to Post structures

postStore

The contract stores an array of post signatures in a community (there's only one community, for now)

communityPostIDs

The user profile stores a list of all of the user's post signatures
A registered user can retrieve a specific post via a post signature
A registered user can retrieve all posts of another registered user
A registered user can retrieve all posts in a community

Extras

Add support for passing CLI arguments to forge test in our CLI wrapper
NOTE/TODO items peppered throughout the contract where I wanted to start with a concept, but keep it basic/simple for the MVP
Move events into their own sol file

Useful for resuse in tests

Separate post & user mgmt tests

Diagram of how the new post related data structures

To view the comparison BEFORE the formatting commit, you can use: https://github.com/juannyG/coms6998/compare/8444de3f69d9aedfd332f76cca55f6c68b72cc39...de995d7c376fb9c62ab7dd38971a1769e25ba061, where 8444de3f69d9aedfd332f76cca55f6c68b72cc39 is the current commit of dev

Not sure if I miss something from the previous meeting. I'm wondering why we need to signed the content. Is it to make it verifiable? I think the whole transaction will already be signed and the content is also included in the call data of the transaction so it's already verifiable that the content is coming from the address owner.

Not sure if I miss something from the previous meeting. I'm wondering why we need to signed the content of the post. Is it to make it verifiable? I think the whole transaction will already be signed and the content is also included in the call data of the transaction so it's already verifiable that the content is coming from the address owner.

Great question! Your 100% correct about the transaction. However, as I was developing this API, here are some of the things I was thinking about:

getPost - how do I retrieve a single post? What is the ID of a post? I can't use the txID, because it doesn't exist yet until AFTER the "create post" tx completes. We can't use the block number, as solidity provides minimal guarantees about available block # information when a contract is processing a request. Maybe it's just the index in an array in the contract, however...
When we move content off-chain and even more so, into something like mongoDB - the signature of the content provides the guarantee that no tampering has occurred since the content was posted. If we store it in a centralized web2 data store without a signature, there's no way to verify the data is in fact.
When we want to transfer ownership of a post or an entire account - instead of relying on a potentially long history of tx receipts (emitted events), the state of the signatures can be updated on chain - i.e. you allow your post to be transferred to me - I can then claim ownership by resigning the content with my wallet.

It felt to me that we get a bit more freedom by decoupling the tx signature from the content signature.

authors: hungchingliu juannyG


text:
entry level improvements & fixes on csi-doctor.sh

[x] improve output readability
[x] multiple mount pod for single pv
[x] app uses multiple pv

Codecov Report
Base: 41.40% // Head: 41.59% // Increases project coverage by +0.19% :tada:

Coverage data is based on head (c623da9) compared to base (fc980f2).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #577      +/-   ##
==========================================
+ Coverage   41.40%   41.59%   +0.19%
==========================================
  Files          32       32
  Lines        3362     3373      +11
==========================================
+ Hits         1392     1403      +11
  Misses       1847     1847
  Partials      123      123

Impacted Files
Coverage Δ

pkg/juicefs/mount/builder/pod.go
58.46% <0.00%> (+3.83%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter timfeirg

repo: juicedata/juicefs-csi-driver


text:
cmd: update sample fallback configs.

Update sample fallback configuration files removing obsolete configuraton for ditched message dumper.

The change is good, just wondering do we actually need this file at all, I mean the fallback config is now embedded to daemonset deployment file.

The change is good, just wondering do we actually need this file at all, I mean the fallback config is now embedded to daemonset deployment file.

I'd like to keep those around in the repo. Both for reference and for cases when I test/debug something without using a daemonset deployment (running the binaries in the host namespace, with NODE_NAME set and -kubeconfig pointing to the configuration for apiserver access). If the concern is that the files might get out of sync with the ConfigMap/inlined versions in the deployment files... that's probably true, but I think it could be solved with some placeholder which gets filled in with the file content, since we anyway keep generating the deployment yamls  AFAICT.

authors: jukkar klihub

repo: jukkar/nri-resmgr


text:
[Good First Issue]: Replicate Existing Cookbooks and Create New Examples - Batch 2.

For context, see: CONTRIBUTING.md and cookbooks/README.md

Overview
We're looking for contributors to help expand our collection of Jupyter notebooks (cookbooks) that demonstrate various AI and automation tasks using Julep's features. This is a great opportunity for newcomers to get familiar with Julep and contribute to the project!
Objectives

Replicate existing cookbooks to ensure they're up-to-date and functioning correctly.
Create new cookbooks based on the ideas listed in the cookbooks/README.md file.

Tasks
1. Replicating Existing Cookbooks

Choose one or more of the existing cookbooks from the list in cookbooks/README.md.
Follow the instructions in the notebook to run it in Google Colab.
Verify that all cells execute without errors and produce the expected outputs.
If you encounter any issues or outdated information, document them for updating.

2. Creating New Cookbooks

Select an idea from the "Potential Cookbooks for Contributors" section in cookbooks/README.md.
Create a new Jupyter notebook following the structure of existing cookbooks.
Implement the chosen use case using Julep's features.
Ensure your notebook includes:

A clear introduction and overview of the task
Step-by-step implementation with explanations
Proper error handling and user guidance
A conclusion summarizing the key learnings

Guidelines for Creating New Cookbooks

Naming Convention: Name your notebook following the pattern XX-Descriptive_Name.ipynb, where XX is the next available number in the sequence.

Structure:

Start with an introduction explaining the purpose of the cookbook.
Include a cell for installing the Julep client.
Create sections for each major step (e.g., Creating an Agent, Defining a Task, Creating an Execution).
Add markdown cells to explain concepts and code.

Code Quality:

Ensure your code is well-commented and follows PEP 8 style guidelines.
Use meaningful variable names.
Handle potential errors gracefully.

Documentation:

Explain each step clearly, assuming the reader is new to Julep.
Include links to relevant Julep documentation where appropriate.

Testing:

Test your notebook thoroughly in Google Colab to ensure it runs without errors.
Include sample outputs where relevant.

Update README.md:

Add your new cookbook to the table in cookbooks/README.md.
Include a brief description and mark it as implemented.

How to Contribute

Fork the repository.
Create a new branch for your cookbook (e.g., cookbook/weather-notification-service).
Develop your cookbook following the guidelines above.
Test your notebook thoroughly.
Commit your changes and push to your fork.
Open a pull request with a clear description of your contribution.

Resources

Julep Documentation
Existing Cookbooks
CONTRIBUTING.md

Need Help?
If you have any questions or need assistance, please don't hesitate to ask in the comments of this issue or reach out on our Discord channel.
We're excited to see your contributions and help grow the Julep cookbook collection!

Long-ass list of ideas

Automated Meeting Scheduler
Description: Schedules meetings by checking participants' availability, sending invites, and managing calendar entries.
Features:
Tools: google_calendar, slack
Step Types: Tool Call, Conditional Logic, Create Event, Send Invitation, Log
Email Categorization and Response Automation
Description: Categorizes incoming emails, prioritizes them, and sends automated responses based on predefined templates.
Features:
Tools: sendgrid, slack
Step Types: Receive Email, Evaluate, Categorize (Conditional Logic), Send Response, Log
E-commerce Order Processing Workflow
Description: Automates the order processing system by handling order placements, inventory checks, payment processing, and shipment tracking.
Features:
Tools: finance, slack, sendgrid
Step Types: Tool Call, Evaluate, Conditional Logic, Update Inventory (Set), Send Confirmation, Track Shipment
Content Moderation and Classification
Description: Reviews user-generated content, classifies it based on predefined categories, and takes appropriate actions.
Features:
Tools: huggingface, wikipedia
Step Types: Tool Call, Evaluate, Conditional Logic, Log, Take Action (Delete, Notify)
Personalized Learning Assistant
Description: Provides personalized learning materials based on user progress, quizzes their knowledge, and tracks improvement.
Features:
Tools: wikipedia, slack
Step Types: Tool Call, Evaluate, Conditional Logic, Create Quiz (Prompt), Track Progress (KV Storage), Loop
Automated Backup and Recovery System
Description: Regularly backs up critical data, monitors backup status, and initiates recovery procedures in case of failures.
Features:
Tools: api_call, slack
Step Types: Schedule (Sleep), Tool Call, Evaluate, Conditional Logic, Initiate Recovery
Smart Home Automation Workflow
Description: Manages smart home devices by responding to user commands, monitoring environmental conditions, and adjusting settings accordingly.
Features:
Tools: slack, weather, dalle
Step Types: Tool Call, Conditional Logic, Update Settings (Set), Loop, Log
Inventory Management and Reordering System
Description: Tracks inventory levels, predicts shortages, and automatically places reorder requests when thresholds are met.
Features:
Tools: airtable, sendgrid, finance
Step Types: Tool Call, Evaluate, Conditional Logic, Create Reorder (Set), Send Notification, Log

For context, see: CONTRIBUTING.md and cookbooks/README.md

Overview
We're looking for contributors to help expand our collection of Jupyter notebooks (cookbooks) that demonstrate various AI and automation tasks using Julep's features. This is a great opportunity for newcomers to get familiar with Julep and contribute to the project!
Objectives

Replicate existing cookbooks to ensure they're up-to-date and functioning correctly.
Create new cookbooks based on the ideas listed in the cookbooks/README.md file.

Tasks
1. Replicating Existing Cookbooks

Choose one or more of the existing cookbooks from the list in cookbooks/README.md.
Follow the instructions in the notebook to run it in Google Colab.
Verify that all cells execute without errors and produce the expected outputs.
If you encounter any issues or outdated information, document them for updating.

2. Creating New Cookbooks

Select an idea from the "Potential Cookbooks for Contributors" section in cookbooks/README.md.
Create a new Jupyter notebook following the structure of existing cookbooks.
Implement the chosen use case using Julep's features.
Ensure your notebook includes:

A clear introduction and overview of the task
Step-by-step implementation with explanations
Proper error handling and user guidance
A conclusion summarizing the key learnings

Guidelines for Creating New Cookbooks

Naming Convention: Name your notebook following the pattern XX-Descriptive_Name.ipynb, where XX is the next available number in the sequence.

Structure:

Start with an introduction explaining the purpose of the cookbook.
Include a cell for installing the Julep client.
Create sections for each major step (e.g., Creating an Agent, Defining a Task, Creating an Execution).
Add markdown cells to explain concepts and code.

Code Quality:

Ensure your code is well-commented and follows PEP 8 style guidelines.
Use meaningful variable names.
Handle potential errors gracefully.

Documentation:

Explain each step clearly, assuming the reader is new to Julep.
Include links to relevant Julep documentation where appropriate.

Testing:

Test your notebook thoroughly in Google Colab to ensure it runs without errors.
Include sample outputs where relevant.

Update README.md:

Add your new cookbook to the table in cookbooks/README.md.
Include a brief description and mark it as implemented.

How to Contribute

Fork the repository.
Create a new branch for your cookbook (e.g., cookbook/weather-notification-service).
Develop your cookbook following the guidelines above.
Test your notebook thoroughly.
Commit your changes and push to your fork.
Open a pull request with a clear description of your contribution.

Resources

Julep Documentation
Existing Cookbooks
CONTRIBUTING.md

Need Help?
If you have any questions or need assistance, please don't hesitate to ask in the comments of this issue or reach out on our Discord channel.
We're excited to see your contributions and help grow the Julep cookbook collection!

Long-ass list of ideas

Automated Meeting Scheduler
Description: Schedules meetings by checking participants' availability, sending invites, and managing calendar entries.
Features:
Tools: google_calendar, slack
Step Types: Tool Call, Conditional Logic, Create Event, Send Invitation, Log
Email Categorization and Response Automation
Description: Categorizes incoming emails, prioritizes them, and sends automated responses based on predefined templates.
Features:
Tools: sendgrid, slack
Step Types: Receive Email, Evaluate, Categorize (Conditional Logic), Send Response, Log
E-commerce Order Processing Workflow
Description: Automates the order processing system by handling order placements, inventory checks, payment processing, and shipment tracking.
Features:
Tools: finance, slack, sendgrid
Step Types: Tool Call, Evaluate, Conditional Logic, Update Inventory (Set), Send Confirmation, Track Shipment
Content Moderation and Classification
Description: Reviews user-generated content, classifies it based on predefined categories, and takes appropriate actions.
Features:
Tools: huggingface, wikipedia
Step Types: Tool Call, Evaluate, Conditional Logic, Log, Take Action (Delete, Notify)
Personalized Learning Assistant
Description: Provides personalized learning materials based on user progress, quizzes their knowledge, and tracks improvement.
Features:
Tools: wikipedia, slack
Step Types: Tool Call, Evaluate, Conditional Logic, Create Quiz (Prompt), Track Progress (KV Storage), Loop
Automated Backup and Recovery System
Description: Regularly backs up critical data, monitors backup status, and initiates recovery procedures in case of failures.
Features:
Tools: api_call, slack
Step Types: Schedule (Sleep), Tool Call, Evaluate, Conditional Logic, Initiate Recovery
Smart Home Automation Workflow
Description: Manages smart home devices by responding to user commands, monitoring environmental conditions, and adjusting settings accordingly.
Features:
Tools: slack, weather, dalle
Step Types: Tool Call, Conditional Logic, Update Settings (Set), Loop, Log
Inventory Management and Reordering System
Description: Tracks inventory levels, predicts shortages, and automatically places reorder requests when thresholds are met.
Features:
Tools: airtable, sendgrid, finance
Step Types: Tool Call, Evaluate, Conditional Logic, Create Reorder (Set), Send Notification, Log

i can work on this

@ijindal1  can you assign this issue to me

hey @ijindal1 , ican you please assign me this issue so that i can start working on it i have some approach to work with this

Hey @prathamesh424 and @Mefisto04 - just comment here with which example each of you want to work on, and can start building a demo. There is no need to assign the ticket actually.

repo: julep-ai/julep


text:
MobileScannerController.start() could use better error handling

The API for MobileScannerController.start() has some issues with usability.

Having to specify a separate function for onPermissionSet feels weird (not to mention its return type is a dynamic Function(bool) instead of void Function(bool))
If start() throws an error, there is no robust way to determine what kind of error it is. We just get a MobileScannerException with a string message. If the message changes, our code might break.

I propose the following:

deprecate the onPermissionSet argument on the controller
add a new enum called MobileScannerErrorCode with enum values for the permission denied error & generic error
replace the error message in MobileScannerException with an error code of the above enum

I'd be happy to implement this change if you want, its pretty small imo.
Version: 3.0.0-beta.2

FYI: I have a PR in the works, I'll hopefully get it out tomorrow.


text:
Is usehooks-ts hooks completely compatible with React Native?

I tried using ts hooks in RN but, i would know if are completely compatible with bare React Native/Expo apps?

Hi, I don't know, never tried and no feedback yet. It works for you?

I don't think so.
Even if it does, it is bound to a very narrow node/React Native version combination:
Have it too low and you can't install the library. Have it too high and you can't use React Native (at least, the version that I've tested) due to transformer errors.

Hey it used to be, we were using it but something has broken lately and it stopped working.
 WARN  Possible Unhandled Promise Rejection (id: 0):
TypeError: (0, __1.useIsomorphicLayoutEffect) is not a function. (In '(0, __1.useIsomorphicLayoutEffect)(function () {
      savedCallback.current = callback;
    }, [callback])', '(0, __1.useIsomorphicLayoutEffect)' is undefined)

Closing this issue due to inactivity, but feel free to reopen or create a new issue if needed. Thanks!

Funny I actually just started using react native again so we'll know soon enough!

authors: JonLemOfficial amritk canpoyrazoglu juliencrn

repo: juliencrn/usehooks-ts


text:
Some help needed please!

Hey There!
thanks for this cool package! I was trying to use this at home and I succeeded to communicate with my HEOS devices. Now I want make a small Angular app and use node express to create APIs to control my devices. But I don't know how pass the response message (for example "now playing" back to the front end, via the API. You can log the responses from the HEOS device (callback function in "onAll" or "on" function), but you have to wait for the promises to be resolved:
app.get('/heos', function (req, res) {
test()
.then(function (data) {
res.send(data)
})
.catch(function (e) {
res.status(500, {
error: e
});
})
});
function test() {
const heos = require('heos-api')
return heos.discoverAndConnect().then(connection =>
connection
.onAll(collectData) //do something to collect return messages
.write('system', 'prettify_json_response', { enable: 'on' })
.write('system', 'heart_beat')
.write('player', 'get_now_playing_media', { pid: 1 })
)
}
Maybe you can help me a little bit?
thanks!

The problem is that the API is purely a stream of messages. When you send a 'volume_up' command to the device and get a 'volume_up, success' back it is obvious that your 'volume_up' was successful, but if you send many messages, there is no way to pair your messages with the responses perfectly.
I use a 'good enough' solution to translate the streams into promises that looks something like this:
const heos = require("heos");

const volumeUp = (connection) => (pid, step) =>
  new Promise((resolve, reject) => {
    connection
      .once(
        {
          commandGroup: "player",
          command: "volume_up",
        },
        (response) => resolve(response)
      )
      .write("player", "volume_up", { pid, step });
  });

heos
  .discoverAndConnect()
  .then((connection) => volumeUp(connection)(156, 10))
  .then(console.log);

.once is not a perfect solution cause the messages can come out of order, and then the wrong response will be paired with the wrong request. It is usually good enough for my use cases. Does this help you or was it something else?

Cool! Thanks a lot, this will help me indeed. I was also considering observables to do the trick, maybe I will experiment with them as well.
Thanks again!

Observables can definitely be viable! That also sounds like a great idea. I think promises make sense for when you are trying to list players and such, but observables could make more sense for keeping a volume knob in an app up to date, or similar.

authors: juliuscc wammesjeroen

repo: juliuscc/heos-api