text:
How auto-pipelining works?

Description
how can I check if something is being executed as a pipeline?
I know that docs says this code is automatically handled as a pipeline because they are in the same "tick":
await Promise.all([
   client.set(...),
   client.set(...),
   client.set(...),
])

but
const promises: Promise<unknown>[] = [];

for (const [key, value] of data) {
    promises.push(client.hSet(key, value));
    promises.push(client.expire(key, ...));
}

await Promise.all(promises);

is this being executed as a pipeline?

Yes, both of them are pipelined as both of them are running all the commands on the same "event loop tick"

repo: redis/node-redis


text:
Update readme and documentation

Prepares README and documentation for the upcoming release.
DO NOT MERGE

See new README here:
https://github.com/redis/redis-vl-python/tree/feat/RAAE-192/documentation-updates

source: gharchive/pull-request

repo: redis/redis-vl-python

license: MIT

license_type: permissive

license_source: github-api


text:
addLastIfExistsAsync API in RedissonDeque appending absurd value to the list in redis

Expected behavior
rBatch.getDeque(redisKey,StringCodec.INSTANCE).addLastIfExistsAsync(value);
This should append a json string value to the already existing redis list with json strings. The key was created with StringCodec.INSTANCE.
127.0.0.1:7002> lrange redisKey 0 -1

"{"Id":12345,"code":"ABCD","time":12345}"
"{"Id":12346,"code":"ABCE","time":12346}"

Actual behavior
Some absurd value is being appended to the list. No error logs seen regarding command timeout or anything like that.
127.0.0.1:7002> lrange redisKey 0 -1

"{"Id":12345,"code":"ABCD","time":12345}"
"[PooledUnsafeDirectByteBuf(ridx: 0, widx: 62, cap: 256)]"

Steps to reproduce or test case
Insert redis key with : rBatch.getDeque(redisKey,StringCodec.INSTANCE).addAllAsync(values);
Append to the above key with : rBatch.getDeque(redisKey,StringCodec.INSTANCE).addLastIfExistsAsync(value);
Redis version
Happening on 5.0.7 as well as 3.0.7
Redisson version
3.15.0
Redisson configuration
Standard cluster mode configuration

Fixed! Thanks for report

Fixed! Thanks for report

Didn't expect such a swift response and fix 😄 . Thanks a lot!
Any ETA on the next release version?

During next month.

source: gharchive/issue

repo: redisson/redisson


text:
this cron 33 3/5 * * * ?  only execute once

redisson version :

org.redisson
redisson-spring-boot-starter
3.16.3

jdk version:
oracle jdk 11
This is the correct expression : 33 3/1 * * * ?
When the starting time is long, the probability will not be executed
33 3/5 * * * ? will be not executed at all, if now time is "2021-10-25 10:03:50"

any body here?

Unable to reproduce.

When the starting time is long, the probability will not be executed

Your cron expression is executed every 5 minutes. How did you set long starting time?

Using this cron  "33 3/5 * * * ?" please, this  encounter problems with high probability
by the way, my redis version is 5.0.4

Unable to reproduce.

When the starting time is long, the probability will not be executed

Your cron expression is executed every 5 minutes. How did you set long starting time?

the version of 3.16.4 looks like right

unfortunately, I reproduce this, when I delete the task and add the same key again at the version of 3.16.4
I don't know what is the reason cause this

@flykarry Can you provide test code?

sorry I have changed to quartz

authors: flykarry mrniko


text:
The stream queue documentation is too sparse to use at all

When the message has not been acked because the consumer crashed, will Redisson automatically process the pending message and send it again? Or do developers need to regularly poll pending and process pending messages by themselves?

Do you mean RStream object?

When the message has not been acked because the consumer crashed, will Redisson automatically process the pending message and send it again? Or do developers need to regularly poll pending and process pending messages by themselves?

You need to request pending messages through pendingRange() method. I added into examples. Redisson doesn't know which logic should be executed before ack

authors: anpbszzz mrniko


text:
rgbfix 16-char title omits last character

rgbfix has a bug where a 16-character title results in the last character being omitted.  The offending line of code is:
int n = snprintf((char *)header + 0x34, 16, "%s", title);

snprintf()' is not an appropriate function to use here because it appends a null-terminating character, however, a null-terminating character is not desired in the case of a 16-char title.
I'm working on a PR for this currently.

Fixed in https://github.com/rednex/rgbds/pull/345

authors: AntonioND huderlem

repo: rednex/rgbds


text:
Pull updates from 0.3.1

Version 0.2.1 (pull from v0.3.1)
New Bundle module and improvement to UI.
New feature:

Bundle module allow bundling physical and digital products on a single price (issue #94, #104).
Get total value of a bundle (issue #97).
Able to add multiple coupons to an order (issue #106, #107, #109).
Coupon can be applied to bundles (issue #108).
Verify and save coupon against all products in an order (issue #110).
Order will now check coupon for multiple_coupons flag (issue #111).
Cleaner UI.

Enhancement:

Added migrations to upgrade database from v0.1 to v0.2/v0.3 (issue #89).
Sidebar is now off-canvas (issue #91).
Exclude tests and non-production files from release package (issue #96).

Bug fixes:

Resolves TokenMismatchException issue on login (issue #88).
User config file will override the default package config file (issue #90).
Add Remember_token column users table never run in migration (issue #105).

Upgrade scripts:

Add migration scripts to help migrate database and folder structure from v0.1 (issue #104).

v0.2 branch still supports Laravel 5.0, which requires PHP 5.4. Many shared hosting servers don't support PHP 5.5 yet.

repo: redooor/redminportal

license: mit

license_source: bigquery


text:
Fire tv xcloud

Improve the app for the Amazon Fire TV 4K Max, it's experiencing a lot of crashes, and if possible, also improve the Brazil server for the Northeast region.

realmente, tem apresentado vários travamentos no fire tv, seria interessante também aumentar a compatibilidade com androids mais antigos

#41

authors: Resplays Willian514 redphx

repo: redphx/better-xcloud-android


text:
runSaga.toPromise never resolves when having takeLatest in the saga

Steps to reproduce
Description of the bug/issue
Having a takeLatest yielded in the saga, and running the saga via runSaga and converting to a promise, promise never resolves:
function* takeSaga() {

}

function* saga() {
   yield takeLatest('foo', takeSaga);
}

runSaga({
   dispatch: () => null,
   getState: () => {},
}, saga).toPromise() // this never resolves!!!

Steps to reproduce the bug/issue
Just run the code above, or better check example below:
Example
https://codepen.io/anon/pen/QRWGEP?editors=0011
Actual results
The returned promise never resolves.
The Expected results
The returned promise should resolve at the end of the root saga, after forking takeLatest, and w/o waiting for takeLatest to execute.
Environment information

redux-saga version: 1.0.2
babel / typescript setup:

		"babel-loader": "^7.1.1",
		"babel-plugin-transform-class-properties": "^6.9.1",
		"babel-plugin-transform-es2015-classes": "^6.24.1",
		"babel-plugin-transform-es2015-modules-commonjs": "^6.26.0",
		"babel-plugin-transform-object-rest-spread": "^6.8.0",
		"babel-plugin-webpack-alias": "^2.1.2",
		"babel-preset-react": "^6.24.1",
		"babel-register": "^6.24.1",

Forked child is attached to the parent task.  Perhaps yield spawn a wrapper function explicitly should not block the root for completion
Quote from saga doc, redux-saga's fork model

Attached forks (using fork)
Attached forks remain attached to their parent by the following rules
Completion
A Saga terminates only after
It terminates its own body of instructions
All attached forks are themselves terminated

Hey there,
spawn works like a charm. Thanks for that, I'm pretty new in sagas, should have known that.
Closing.

authors: ickata zhaoyingdu

repo: redux-saga/redux-saga


text:
take does not catch PUT from child saga

Multiple actions can be dispatched in a small time-window. Our solution involves batching our calls so that there can only be one outgoing api call at a time.
Any subsequently queued server requests will be condensed into one and await return before dispatching.
This is done by adding a blocking 'yield take' to pause taking from a requestChannel until the server call resolves
Simplified code as follows
function* transactionSaga() {
    const requestBuffer = buffers.dropping(1);
    const requestChannel = yield actionChannel(actionIsCreate, requestBuffer);

    yield [
        takeLatest(actionIsRequested, putToChannel),
        fork(watchRequest, requestChannel, requestBuffer, contentBuffer)
    ];
}

function* putToChannel({ payload, meta }) {
    yield call(delay, 200);
    yield put({ type: workingData.transactions.CREATE, payload });
}

function* watchRequest(requestChan, buffer) {
    while (true) {
        const action = yield take(requestChan);

        if (reqBuffer.isEmpty()) {
            yield handleRequest(action);
        }

        // blocked here.
        yield take('DONE');
    }
}

function* handleRequest(action) {
    try {
        yield call(api, packet)
        yield put({ type: 'DONE' })

    } catch (e) {
        yield put({ type: 'err' })
    }
}

referring to this https://github.com/redux-saga/redux-saga/issues/598, but I don't think it's relevant given the complexity of the OP's code.

well, you are doing this yield handleRequest(action); so it will BLOCK here until hanleRequest is done - you have yielded an iterator which is a blocking call
if you want to make this non blocking, just do this instead - yield fork(handleRequest, action);

I will try it out. Just to clarify:
I want handleRequest to BLOCK until the call completes, then and only then take another request from the channel.
Once handleRequest puts "DONE", the watchRequest Saga does not continue.
Redux dev tools shows that DONE was logged, but watch request does not continue.
I would expect that upon receiving 'DONE', watchRequest would take another item from the channel

Thus what I'm learning from what you said, yielding an iterator does not allow watchRequest to continue (even if handleRequest completes)

yup! you are right. 🎊  we're saga-official now

Thus what I'm learning from what you said, yielding an iterator does not allow watchRequest to continue (even if handleRequest completes)

Not at all, yielding iterator will block your saga to the moment of its completion. Your problem was that you have yielded an iterator (handleRequest) IN WHICH you make put(DONE) while watchRequest is still blocked on handleRequest and when it resumes its geting blocked on take(DONE) but it wont resume cause it has already happened.

Thank you for the clarification! I think I follow now.
Bad
watchRequest -> handleRequest -> yield put(DONE)  -> watchRequest on take(DONE)
w/fork
watchRequest, fork(handleRequest) -> watchRequest on take(DONE), handleRequest forked and running.
been a lot of fun learning this library. closing!


text:
Fixing link to WP redux site

Fixing link to the WordPress Redux site in readme.

name: :memo: Documentation Fix
about: Fixing a problem in an existing docs page
Checklist

[x] Is there an existing issue for this PR?

link issue here

[x] Have the files been linted and formatted?

What docs page needs to be fixed?

Section: Intro
Page: Top of first page

What is the problem?
Outdated/broken link.
What changes does this PR make to fix the problem?
Updates readme with correct link.

Thanks!

Thanks!

authors: gmays timdorr

repo: reduxjs/redux


text:
Destructuring or spreading createSelector() args as arrays TypeScript error

Hi, I'm trying to create selectorFactoryFactories however am having trouble with the types and was wondering if there's something I'm missing, or if it's a bug, or if it's impossible. Any and all help would be appreciated.
Edit* The destructuring method works perfectly during runtime, the issue is with the type errors being thrown.
The below case works as expected.
createSelector([
    regularSelectorA,
    selectorFactory('B'),
    selectorFactory('C'),
  ],
  (a, b, c ) => return { a, b, c })

However when I destructure part of the array or the complete array, typescript complains.
createSelector(...[
    regularSelectorA,
    selectorFactory('B'),
    selectorFactory('C'),
  ],
  (a, b, c ) => return { a, b, c })

In the above case typescript errors with expected 2-13 arguments but got 1 or more
createSelector([
    regularSelectorA,
    ...selectorFactoryFactory('B', 'C')
  ],
  (a, b, c ) => return { a, b, c })

In the above typescript also errors with
Argument of type '(OutputSelector<SharedRootState, ReadonlyRecord...' is not assignable to parameter of type '[ParametricSelector<SharedRootState, {}, ReadonlyRecord"...'.

Property '0' is missing in type '(OutputSelector<SharedRootState, ReadonlyRecord<BaseEntity

The definition for selectorFactory and selectorFactoryFactory and regularSelector
function regularSelector(state: RootState) { return state.slice }

const selectorFactory= (attribute) => {
  return createSelector(regularSelector, function (storeState) {
    return storeState && storeState[attribute];
  });
}

const selectorFactoryFactory = (...attributes) => {
    return attributes.map(att => selectorFactory(att)
}

This is a funky issue. I was able to find a workaround for your last scenario, but this doesn't help if the number of values returned from selectorFactoryFactory is variable:
export type PS = ParametricSelector<any, {}, any>;

const selectorArray = concat<PS>(selectorFactoryFactory('B', 'C'), [
  regularSelectorA,
])

createSelector(
  selectorArray as [PS, PS, PS],
  (a, b, c) => ({ a, b, c }));

But I also think your second case is not a reselect type definition issue, it's a language issue, see this example:
const add2 = (a: number, b: number) => a + b;
add2(...[2, 3]);
// [ts] Expected 2 arguments, but got 0 or more.

http://www.typescriptlang.org/play/#src=const add2 %3D (a%3A number%2C b%3A number) %3D> a %2B b%3B
add2(...[2%2C 3])%3B

Looks like there's already even been some prior thinking on this?
https://github.com/reduxjs/reselect/pull/143

const add2 = (a: number, b: number) => a + b;
add2(...[2, 3]);
// [ts] Expected 2 arguments, but got 0 or more.

I think the issue with spreading an array into a function's arguments (above example) is that TypeScript sees the type of [2, 3] as an array (type number[]), which can have any length, so when you spread it, there's no way for TypeScript to know the array has the correct length to fulfll the function's arguments.
You can annotate [2, 3] as a tuple ([number, number]), in which case TypeScript would be able to know whether the tuple length fulfils the function's arguments, but unfortunately it doesn't seem to (https://github.com/Microsoft/TypeScript/issues/24241):
declare const createSelector: (selectors: number[], fn: Function) => void;

createSelector([1,2,3], () => {});
// type error
createSelector(...[1,2,3], () => {});
const tuple: [number, number, number] = [1, 2, 3];
// type error
createSelector(...tuple, () => {});
createSelector([1,...[2,3]], () => {})

As for spreading into the array, I can't reproduce the problem. Here is the code I tried:
// no error
createSelector([selectorFactory('a'), ...selectorFactoryFactory('b', 'c')], (a, b, c) => ({ a, b, c }))

I'm happy to see this ticket getting some love.
@OliverJAsh You hit the nail on the head with:

I think the issue with spreading an array into a function's arguments (above example) is that TypeScript sees the type of [2, 3] as an array (type number[]), which can have any length, so when you spread it, there's no way for TypeScript to know the array has the correct length to fulfll the function's arguments.

Reselect also requires a minimum of two args for the create selector function, so either we'd have to tweak the definitions to allow 0 or more, or find a clever way to decorate what we're passing that is readable as 1 or more
/* one selector */
export function createSelector<S, R1, T>(
  selectors: [Selector<S, R1>],
  combiner: (res: R1) => T,
): OutputSelector<S, T, (res: R1) => T>;
export function createSelector<S, P, R1, T>(
  selectors: [ParametricSelector<S, P, R1>],
  combiner: (res: R1) => T,
): OutputParametricSelector<S, P, T, (res: R1) => T>;

I don't think Typing the input as selector[] is possible since it loses the relationship between the selector's R1 and the parametric selector's R1 .
In the below example an error isn't being thrown because the createSelector has a simplified definition via the number[], which works for the example but I'm not sure how to make it work for Reselect.

declare const createSelector: (selectors: number[], fn: Function) => void;

If variadic types are added to TypeScript, that could be one way of going about this, however it's been under discussion since 2015 so I wouldn't expect it any time soon.
https://github.com/Microsoft/TypeScript/issues/5453

Microsoft announced TypeScript 3 yesterday which allows for generic typing of the spread operator.
We may be able to simplify the Type file for reselect since instead of doing overloads like
// TODO (billg): 5 overloads should *probably* be enough for anybody?
function call<T1, T2, T3, T4, R>(fn: (param1: T1, param2: T2, param3: T3, param4: T4) => R, param1: T1, param2: T2, param3: T3, param4: T4): R
function call<T1, T2, T3, R>(fn: (param1: T1, param2: T2, param3: T3) => R, param1: T1, param2: T2, param3: T3): R
function call<T1, T2, R>(fn: (param1: T1, param2: T2) => R, param1: T1, param2: T2): R
function call<T1, R>(fn: (param1: T1) => R, param1: T1): R;
function call<R>(fn: () => R, param1: T1): R;
function call(fn: (...args: any[]) => any, ...args: any[]) {
    return fn(...args);
}

We would be able to do something like
function call<TS extends any[], R>(fn: (...args: TS) => R, ...args: TS): R {     return fn(...args); }
And this would remove the typescript cap of 13 selectors for reselect.

Any news on the cap of 13 selectors now that we have TypeScript 3?

authors: AlexeiDarmin OliverJAsh blackwood gustavopch

repo: reduxjs/reselect


text:
weakMapMemoize with resultEqualityCheck is provided empty objects for first call.

Hi! Thanks for all the great QOL improvements in Reselect 5, however I've found a pretty major issue with the resultEqualityCheck  option when using the weakMapMemoize memoization. It calls the resultEqualityCheck even if it is the first time the selector has run. This wouldn't be too bad, however this first call is called with empty objects instead of the actual result of the selector. Please see the example below. Obviously this is a bit of a contrived example using strings, but things get pretty hairy if you expect the result to be a Set or another complex object.
const firstMessageSelector = createSelector(
  [(messages) => messages[0]],
  (message) => `${message}!!!`,
  {
    memoizeOptions: {
      resultEqualityCheck: (a, b) => {
        console.log("resultEqualityCheck:", { a, b });
        return a === b;
      },
    },
  }
);

const one = firstMessageSelector(["one", "two"]);
console.log("one:", one);
const two = firstMessageSelector(["two", "three"]);
console.log("two:", two);

Expected Console Output:
firstMessageSelector: one
one: one!!!
firstMessageSelector: two
resultEqualityCheck: Object { a: "one!!!", b: "two!!!" }
two: two!!!

Actual Console Output:
firstMessageSelector: one
resultEqualityCheck: Object { a: {}, b: {} }
one: one!!!
firstMessageSelector: two
resultEqualityCheck: Object { a: "one!!!", b: "two!!!" }
two: two!!!

hmm, this is a good point - the resultEqualityCheck is typed to only expect the result of the memoized function, but the inputStabilityCheck uses the same memoizeOptions and memoize with a different function, one that always returns a new empty object. This is important for how the check works.
I'm not sure of the best fix for this, but I agree it's not great.

Really excited about reselect v5 but +1 on this is upgrade blocking 😞 . We almost guarantee a (development-only) runtime break when resultEqualityCheck does any sort of complex work. (and disabling inputStabilityCheck feels like a band-aid fix)

I could be missing something @EskiMojo14, but this is the code I would have expected for inputStabilityCheck:
const { inputSelectorResults, inputSelectorResultsCopy } =
    inputSelectorResultsObject
const areInputSelectorResultsEqual =
   (memoizeOptions?.equalityCheck ?? shallowEqual)(inputSelectorResults, inputSelectorResultsCopy)

I don't think resultEqualityCheck or maxSize should matter/not sure why we need to setup the full memoize again?

we need to treat memoizeOptions as an opaque value, because it could be anything depending on what memoizer is being used. For example, weakMapMemoize doesn't have an equalityCheck property.
The only way (I can think of) that we can accurately assess that the memoizer, when configured the same way as it is for the output selector, considers the inputs to be different is to do what we do - memoize a separate function that always returns a new reference, with the exact same options used when memoizing the output selector.

authors: EskiMojo14 braeden keegan-lillo


text:
Add global conversation-activity-filter option

Description
It's related to the https://github.com/refined-github/refined-github/pull/4029
It's a great feature! Thanks for that.
Is it possible to keep this setting on for all issues and PRs after page reload? Right now, I have to click on the buttons every time I visit any issue.
Screenshot
PR with conversation-activity-filter turned on:

The same PR after the page reload:

Example URL
https://github.com/refined-github/refined-github/pull/4029

It was proposed but the risk is too high. The feature hides a lot of real content and forgetting it on can cause frustration.
I wonder if there's a way to offer this as an option without offering an option 🤭
What I've been suggesting in these cases is to add a keyboard shortcut so at least you can just press it on load, but nobody ever added it

Any single-letter key that is not already taken. Press ? to see what's not available

repo: refined-github/refined-github


text:
[REF-1742] Radio group prop types fix

Radio group component items and default value to support types other than str

What other types could I put in here and not break? I think we should be more restrictive.

authors: ElijahAhianyo masenf

repo: reflex-dev/reflex


text:
🛑 SmartProtection is down

In 911fc38, SmartProtection (https://smartprotection.com) was down:

HTTP code: 404
Response time: 234 ms

Resolved: SmartProtection is back up in 170d1f8 after 1 hour, 2 minutes.

repo: reinaldoleon/monitoring


text:
🛑 BINUSMAYA (Academic Services) is down

In 39524c6, BINUSMAYA (Academic Services) (https://binusmaya.binus.ac.id/LoginAD.php) was down:

HTTP code: 404
Response time: 1135 ms

Resolved: BINUSMAYA (Academic Services) is back up in 084c579.


text:
🛑 BINUS Career is down

In 398dffc, BINUS Career (https://binuscareer.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BINUS Career is back up in 70c2278.


text:
🛑 GreatNusa.com is down

In ccd5946, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 500
Response time: 2776 ms

Resolved: GreatNusa.com is back up in fbef010.


text:
🛑 GreatNusa.com is down

In de0d145, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 62 ms

Resolved: GreatNusa.com is back up in 63c077a.


text:
🛑 Enrichment Apps is down

In 3756088, Enrichment Apps (https://enrichment.apps.binus.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Enrichment Apps is back up in 1833041.


text:
Special handler for links: url decode for link title

When pasting https://es.wikipedia.org/wiki/Parónimo output should not be Par%C3%B3nimo but Parónimo, as Auto Link Title handles several characters used in widely spoken languages such as Spanish, French, etc.
By the way, are these two plugins compatible? I find Auto Link Title very useful for many sites rarely used, whilst Paste Transform would be a great time saver to avoid manually changing URLs from most used websites.
Thanks for sharing your plugin.

Hello, @jsmm.
Now the plugin work by regexp only with whole string. And the plugin can't know what part of string is url or link title.
It is intresting idea - for add special handler for work with links (i think it is main scenario).
Right now you can change your browser settings for copy url as https://es.wikipedia.org/wiki/Parónimo instead of https://es.wikipedia.org/wiki/Parónimo and browser will be decode escaping. It may have problem with some special chars in a link (space, comma, etc).
If you use firefox it can be changed on page about:config, setting name: browser.urlbar.decodeURLsOnCopy
https://superuser.com/questions/480692/copying-unicode-symbols-from-firefox-address-bar-as-is/1255451

authors: jsmm rekby

repo: rekby/obsidian-paste-transform


text:
Request.body does not seem to interface correctly with ReadableStream

What version of Remix are you using?
1.6.0
Steps to Reproduce
The request.body seems to be a web compatible ReadableStream, but it does not seem to be 100% compatible yet. Reproduce with this:
import {Readable} from "node:stream";

const stream = Readable.fromWeb(request.body);
const x = await s3.upload({
    Bucket: BUCKET_NAME,
    Key: id,
    Body: stream,
}).promise();

This will yield:
TS2345: Argument of type 'ReadableStream<Uint8Array>' is not assignable to parameter of type 'ReadableStream<any>'.
Type 'ReadableStream<Uint8Array>' is missing the following properties from type 'ReadableStream<any>': values, [Symbol.asyncIterator]

This is not just a TS thing, as casting it will result in runtime error:
TypeError: The "readableStream" argument must be an instance of ReadableStream. Received an instance of ReadableStream
    at new NodeError (node:internal/errors:387:5)
    at Object.newStreamReadableFromReadableStream (node:internal/webstreams/adapters:463:11)
    at Function.Readable.fromWeb (node:internal/streams/readable:1403:27)
    at action (C:\Dateien\webdev\paycheck\app\routes\__loggedIn\projects\$projectId\uploadMedia.ts:49:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.callRouteAction (C:\Dateien\webdev\paycheck\node_modules\@remix-run\server-runtime\data.js:40:14)
    at handleResourceRequest (C:\Dateien\webdev\paycheck\node_modules\@remix-run\server-runtime\server.js:442:14)
    at requestHandler (C:\Dateien\webdev\paycheck\node_modules\@remix-run\server-runtime\server.js:42:18)
    at C:\Dateien\webdev\paycheck\node_modules\@remix-run\express\server.js:39:22 {
  code: 'ERR_INVALID_ARG_TYPE'
}

Expected Behavior
I expect request.body to contain an object of type ReadableStream that fulfills all the properties a standardized web ReadableStream has.
I thus expect Readable.fromWeb() to take request.body as a valid parameter.
Actual Behavior
The ReadableStream request.body is not getting accepted by Readable.fromWeb().

Hmm. Interesting. Remix uses this package to support web streams. Which ultimately uses web-streams-polyfill
Here's the line that adds [Symbol.asyncInterator]. I think the issue may be that symbols don't match on name, but by reference. The Readable.fromWeb() is probably returning a different ReadableStream than what Remix uses/expects.
I have a function to convert from node streams to web streams, instead of .fromWeb()
export function nodeStreamToReadableStream(nodeStream: Readable) {
  return new ReadableStream({
    start(controller: any) {
      nodeStream.on('data', (chunk: any) => {
        controller.enqueue(chunk)
      })
      nodeStream.on('end', () => {
        controller.close()
      })
    },
  })
}

@kiliman I did something similar, I now use
    const bodyIterable: AsyncIterable<any> = {
        [Symbol.asyncIterator]() {
            const reader = request.body?.getReader();
            return {
                async next() {
                    const {done, value} = await reader?.read()??{done: true, value: undefined};
                    return {done, value};
                }
            };
        }
    };
    const stream = Readable.from(bodyIterable, {
        objectMode: false,
        highWaterMark: 16,
    });

This should probably make sure back pressure and stuff like that get respected.
But the actual issue is not that the Readable.fromWeb() is returning something wrong, but instead the req.body is not interfacing correctly with the ReadableStream, or am I wrong?

While using the serpapi/serpapi-javascript package (which uses the nodejs/undici HTTP/1.1 client under the hood), imported from a file using the .server. naming convention, i encountered what may be the same problem with the error below.
Ultimately request.body fails the assertReadableStream type check.
/Users/.../node_modules/web-streams-polyfill/src/lib/validators/readable-stream.ts:5
    throw new TypeError(`${context} is not a ReadableStream.`);
          ^
TypeError: First parameter has member 'readable' that is not a ReadableStream.
    at assertReadableStream (/Users/.../node_modules/web-streams-polyfill/src/lib/validators/readable-stream.ts:5:11)
    at convertReadableWritablePair (/Users/.../node_modules/web-streams-polyfill/src/lib/validators/readable-writable-pair.ts:15:3)
    at ReadableStream.pipeThrough (/Users/.../node_modules/web-streams-polyfill/src/lib/readable-stream.ts:211:23)
    at fetchFinale (/Users/.../node_modules/undici/lib/fetch/index.js:973:52)
    at mainFetch (/Users/.../node_modules/undici/lib/fetch/index.js:773:5)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
fatal error: all goroutines are asleep - deadlock!

Looks like this isn't going to be possible as they rely on privately defined symbols in the Node internals to check if the thing passed to fromWeb / toWeb is valid (here, and here). We do however provide the following functions from the @remix-run/node package:

createReadableStreamFromReadable
readableStreamToString,
writeAsyncIterableToWritable,
writeReadableStreamToWritable,

@jacob-ebey Wait, I see that createReadableStreamFromReadable can be used instead of toWeb, but which of those functions acts as a replacement for fromWeb? Seems like it's missing and should be added to @remix-run/node to resolve this issue.

I've also encountered this issue, and I'm trying to use createReadableStreamFromReadable. Could you provide some guidance @jacob-ebey?

authors: ariofrio jacob-ebey kiliman timothymalcham titocosta xdivby0

repo: remix-run/remix


text:
How can I paginate picocli results like Git does it?

Hey there,
I am creating an issue based on a question I raised a few weeks back on Twitter.
I currently have a fun little API that returns results from the Star Wars API. Depending on the query, it returns a lot of results.
I would like to be able to present the results paginated, like Git does it. Like @remkop already mentions it on Twitter, it would be best to leverage already existing infrastructure on the system rather than implement a local pagination.
I've been fiddling around with code for the past few days but I'm afraid I didn't manage to come up with anything conclusive yet. The twitter thread seems to mention IExecutionHandler but I couldn't find anything related in the source code of picocli, so I have been looking at creating a custom IParseResultHandler instead. Past that, I also ran into stdin forwarding issues with ProcessBuilder, so it's hard to come with a minimal reproducible example.
Any help moving in the right direction would be most appreciated!

Just to be clear, I do have some code lying around that attempts to do what is described in the Twitter thread, I simply didn't get it to function as expected just yet.
You can find my attempt here
I tried to strip down as many things as possible in there. Example to be ran with the "planets" argument to trigger the printing of the dummy string

Thank you for raising this!
There are other commitments that I have to take care of first, but I will take a look.

No hurry really, this is not a priority. But I keep tinkering with it and I think someone used to the library might be going faster. Thanks!

No success yet. One small thing:
The planets command should not write to STDOUT, but to the output stream of the commandline:
@Command(name = "planets", description = ["Search for planets"])
class PlanetsCommandPaginateDummy : Callable<Int> {

    @Spec
    lateinit var spec: CommandSpec

    override fun call(): Int {
        spec.commandLine().out.println(dummyLongString)
        return 0
    }
}

I tried writing to a temp file, but no joy yet...

I got it to work with a temp file and by calling inheritIO() on the ProcessBuilder, and calling waitFor() on the Process. You may want to delete the temp file when done.
package nl.lengrand.swacli

import picocli.CommandLine
import picocli.CommandLine.*
import picocli.CommandLine.Model.CommandSpec
import java.io.*
import java.nio.file.Files
import java.util.concurrent.Callable
import java.util.concurrent.TimeUnit
import kotlin.system.exitProcess

const val dummyLongString =
        """
 Found 60 total results for that query
Showing 10 results
 Tatooine
    Climate : arid
    Diameter (km) : 10465
    Gravity : 1 standard
    Orbital period : 304
 Alderaan
    Climate : temperate
    Diameter (km) : 12500
    Gravity : 1 standard
    Orbital period : 364
 Yavin IV
    Climate : temperate, tropical
    Diameter (km) : 10200
    Gravity : 1 standard
    Orbital period : 4818
 Hoth
    Climate : frozen
    Diameter (km) : 7200
    Gravity : 1.1 standard
    Orbital period : 549
 Dagobah
    Climate : murky
    Diameter (km) : 8900
    Gravity : N/A
    Orbital period : 341
 Bespin
    Climate : temperate
    Diameter (km) : 118000
    Gravity : 1.5 (surface), 1 standard (Cloud City)
    Orbital period : 5110
 Endor
    Climate : temperate
    Diameter (km) : 4900
    Gravity : 0.85 standard
    Orbital period : 402
 Naboo
    Climate : temperate
    Diameter (km) : 12120
    Gravity : 1 standard
    Orbital period : 312
 Coruscant
    Climate : temperate
    Diameter (km) : 12240
    Gravity : 1 standard
    Orbital period : 368
 Kamino
    Climate : temperate
    Diameter (km) : 19720
    Gravity : 1 standard
    Orbital period : 463
"""

@Command(
        mixinStandardHelpOptions = true,
        subcommands = [PlanetsCommandPaginateDummy::class, HelpCommand::class]
)
class SwaCLIPaginateDummy : Callable<Int> {
    @Spec
    lateinit var spec: CommandSpec

    private fun executionStrategy(parseResult: ParseResult): Int {
        println("in there")
        val file = Files.createTempFile("pico", ".tmp").toFile()
        this.spec.commandLine().out = PrintWriter(FileWriter(file), true)
        println("writing to ${file}")

        val result = RunLast().execute(parseResult)
        this.spec.commandLine().out.flush()
        println("starting `less ${file.absolutePath}`")
        val processBuilder = ProcessBuilder("less", file.absolutePath).inheritIO()
        val process = processBuilder.start()
        process.waitFor()
        return result
    }

    override fun call(): Int {
        spec.commandLine().usage(System.out)
        return 0
    }

    companion object{
        @JvmStatic
        fun main(args: Array<String>){
            val app = SwaCLIPaginateDummy()
            exitProcess(CommandLine(app)
                    .setExecutionStrategy(app::executionStrategy)
                    .execute(*args))
        }
    }
}

@Command(name = "planets", description = ["Search for planets"])
class PlanetsCommandPaginateDummy : Callable<Int> {

    @Spec
    lateinit var spec: CommandSpec

    override fun call(): Int {
        spec.commandLine().out.println(dummyLongString)
        return 0
    }
}

Thanks for the help! I didn't think about using a temp file, good idea
I can confirm indeed that this does the trick. A few limitations I can see when testing :

The default usage seems to be using less as well currently. I meant to use less only for non help / version commands.
The color output is being lost when forwarding to the less process.
It is visible to the user that we stream to a temporary file, while it is not in, say Git for example.

Thanks again, I don't expect you to test all the comments here :), I'm listing them in case someone else ends up here at some point. I'll be looking if I can improve those myself.

Ok, so getting around the usage and help part is quite simple. You gotta avoid the mambo jambo in case no subcommand is detected.
    private fun executionStrategy(parseResult: ParseResult): Int {

        if (!parseResult.hasSubcommand())
            return RunLast().execute(parseResult)

        val file = Files.createTempFile("pico", ".tmp").toFile()
        this.spec.commandLine().out = PrintWriter(FileWriter(file), true)

        val result = RunLast().execute(parseResult)
        this.spec.commandLine().out.flush() // may not be needed

        val processBuilder = ProcessBuilder("less", file.absolutePath).inheritIO()
        val process = processBuilder.start()
        process.waitFor()

        return result
    }

would work in that case. It could become more complex in a real life application.

Ok so if I understand correctly the coloration is expected since we write to file, without the Ansi escape codes. Let's see if I can do something

Thanks for all the help @remkop. I used your changes and the working example can be found here https://github.com/jlengrand/swacli/blob/main/src/main/kotlin/nl/lengrand/swacli/SwaCLIPaginate.kt.
It is possible to play around with the less options to get more or less info in the output for those that would want to dive deeper into it :).

authors: jlengrand remkop

repo: remkop/picocli


text:
Update to latest Asciidoctor gradle plugin

This PR updates gradle Asciidoctor plugin to latest version.
After applying this PR, gradle ascii works again on master.
Unfortunately, now tabbed panes do not show up any more. :-(
Seems like the used extension is not picked up any more by the new version. I will look into that soon.
For now, the produced index.html is not ready for being published to the web site.

Codecov Report

Merging #1202 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1202      +/-   ##
============================================
+ Coverage     94.30%   94.32%   +0.01%
  Complexity      455      455
============================================
  Files             2        2
  Lines          6676     6663      -13
  Branches       1795     1793       -2
============================================
- Hits           6296     6285      -11
+ Misses          102      101       -1
+ Partials        278      277       -1

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/picocli/CommandLine.java
94.16% <0.00%> (+0.01%)
314.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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

Would it not be easier to revert the last commit (2453cb49)?

Would it not be easier to revert the last commit (2453cb4)?

I force-pushed some changes for this PR, everything is working now:

gradle ascii runs successfully (using the latest version of the asciidoctor gradle plugin)
the produced manual file index.html now shows a tabbed source code pane, showing both the Java and the Kotlin version of the checksum app.

Please note that with the new version of the gradle plugin, html output is now written to build/docs (was: build/docs/html5). I don't know if this breaks your workflow when publishing documents. If so it could be easily corrected by adjusting the outputDir attribute of the asciidoctor task.

Merged. Looks good!
One thing I noticed is that the Copy source function no longer works, but if we have to chose, they are both nice, but I think I like the tabbed examples feature better.
I should look into Groovy and Scala versions of the checksum example too, but at the moment too busy with other commitments...

Merged. Looks good!
One thing I noticed is that the Copy source function no longer works, but if we have to chose, they are both nice, but I think I like the tabbed examples feature better.

Me too!
About the copy function:  I realized already that the copy button is missing, but haven't found time to look into this. Using gradle 5.1, both the copybutton and the tabbed pane are working, so it can be done :-)

I should look into Groovy and Scala versions of the checksum example too, but at the moment too busy with other commitments...

If I remember correctly, there are files for that in the examples section already. I can take that over and will have a look soon.

authors: codecov-commenter deining remkop


text:
Create docker RethinkDB

Write a dockerfile who will launch rethinkDB and documment it

branch : DB_dockerfile_create

Please, someone checkout my branch and read the file. Begin by reading the commit, then each README and then the file I modify. When you're done, do a merge request to master, but do NOT accept it yourself

J'ai merge la branche dans master, aucun conflit et tout semble en ordre

repo: remnil/Geoloc


text:
Invalid fields are not being caught as type errors

Adding an invalid field is not displaying an error indicator. My code:

Graphql schema
type Query {
    article: Artcle
}
type Article {
    title: String
}

this happens for me if a single valid things exists
 const data = await  createClient().query({
      matches: {
        asldkfasdf: true,
      }
    });

src/hasura/hasura.service.ts:29:9 - error TS2353: Object literal may only specify known properties, and 'asldkfasdf' does not exist in type 'matchesGenqlSelection & { __args?: { distinct_on?: matches_select_column[]; limit?: number; offset?: number; order_by?: matches_order_by[]; where?: matches_bool_exp; }; }'.

29         asldkfasdf: true,
           ~~~~~~~~~~

  generated/schema.ts:18019:5
    18019     matches?: (matchesGenqlSelection & { __args?: {
              ~~~~~~~
    The expected type comes from property 'matches' which is declared here on type 'query_rootGenqlSelection & { __name?: string; }'

but
     const data = await  createClient().query({
      matches: {
        id: true,
        asldkfasdf: true,
      }
    });

wont

authors: lukepolo tastywheat

repo: remorses/genql


text:
:pencil: Small typos

One typo and one small doc link fix.

@all-contributors please add @jefftriplett for doc

authors: jefftriplett kjaymiller

repo: render-engine/render-engine


text:
Don't know what this is for

Please add readme

:+1:

just saw your svg, now i know what this is for. closed

authors: koelpinl renke

repo: renke/lognest

license: isc


text:
Buggy Cooldown-Animation for hidden Icons

Found a new small bug :)
The cooldown animation is visible despite hidden icons. I attached a screenshot for a better understanding :)
You can see the clockwise moving animation for the wild mushroom in the upper left corner (under the player portrait) and the cooldown animation on the right side.
http://imgur.com/qniMXFR

Rumour say this has been fixed by Blizzard in 6.1, can you confirm?

authors: pourmar renstrom

repo: renstrom/NeavUI


text:
fix: keep connections open

Description
Keeps connections open indefinitely, as per recommendation by APNs docs.
Resolves #86
How Has This Been Tested?
Not tested
Due Dilligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

just following up if we are merging this in the mainline

@rajesh-blueshift we'll definitely merge this, we've just been super busy with other things. Feel free to use a Git dependency in the meantime, but would love to merge this soon


text:
repclient -index without -server: Servers exhausted

My repclient.config:
{
    "BodyLength": 65832,
    "PadToLength": 4096,
    "MinHashCash": 24,
    "PrivateKey": "",
    "KeyDir": "",
    "SocksServer": "socks5://127.0.0.1:9050",
    "PeerUpdate": 1442861129,
    "BootStrapPeer": "http://mmb4alp3d2vc55op.onion/",
    "PasteServers": [
        "http://ogvizla5pajuax2g.onion/",
        "http://2n4dz35mlptg2ysb.onion/"
    ]
}

Output from repclient -index:
$ repclient -index
Private key(s):
Any server
FATAL: List error: rep: Servers exhausted
$

I have to point repclient to my server using -server URL to retrieve messages.

-index is server specific, the client will not consult the known servers list. Added to todo to fix documentation and error returned in call.

authors: RyanPear saper

repo: repbin/repbin


text:
Add deprecated emit_metric() helper to cog interface

This helps with the transition between the main cog branch and the experimental async branch. Models built for the async branch can be run on either without code changes.
New models should still be using the internal current_scope().record_metric() interface.

This looks good. However it will conflict with #2066 because I've updated tests that work with async models to specify a minimum python version (see for ex https://github.com/replicate/cog/pull/2066/files#diff-922f17529df722a8c4e93788b47410def10f269ce3cd5cff2f768feb2f066336R80). I think the easiest thing would be to change the base of this PR to support-concurrent-predictions-in-child, then get the tests passing (probably just by specifying minimum python version). Then we can either merge this into the support-concurrent-predictions-in-child branch before merging #2066, or merge #2066 first and then this.

Perfect, I'll cherry-pick and fix the tests in #2066

@philandstuff I'm going to merge this into main, then clean-up #2026 ready to be merged.

authors: aron philandstuff

repo: replicate/cog


text:
V1.0.0 Release Requirements

For PGET to hit 1.0.0 release here is a rough list of what is required:
### 1.0.0 Release Requirments
- [ ] Finalize abstractions
- [ ] https://github.com/replicate/pget/issues/37
- [ ] https://github.com/replicate/pget/issues/55
- [ ] Significantly improve testing coverage for critical path code
- [ ] Ensure documentation is updated/better
- [ ] https://github.com/replicate/pget/issues/61
- [ ] https://github.com/replicate/pget/issues/71

1.0.0 is the milestone to where pget can be the default downloader for cog. Please feel free to suggest additional requirements.

repo: replicate/pget


text:
max_length parameter is not honored w/ Vicuna13-b

Running the model:
output = replicate.run(
    "replicate/vicuna-13b:e6d469c2b11008bb0e446c3e9629232f9674581224536851272c54871f84076e",
    input={"prompt": "Which NFL team won the Super Bowl when Justin Bieber was born? Think step by step.",
           "temperature":0.75,
           "max_length":500})

We specify max_length:500, so 500 tokens.
But, the output is 940 words, or 940 * 2.5 tokens.

@bfirsh @mattt @zeke please help!

Hi, @rlancemartin. This sounds more like an issue for the Vicuna-13B model than the Python client library itself, so I'm going to transfer to that repo.
I just tried this myself using the web UI ^1, and the output was within expected range (using OpenAI's tokenizer, 308 tokens; I didn't try feeding it through the model's tokenizer, though).
Can you share any more information to help us diagnose the problem?
/cc @replicate/models

authors: dankolesnikov mattt rlancemartin

repo: replicate/replicate-python


text:
Alpha support for generating yaml only

With this change:
kubectl kots install --yaml --offline --kotsadm-tag 1.16.1 appname > kotsadm.yaml

will generate the admin console yaml for kots 1.16.1

Closing this one in favor of the more kots install to existing airgap cluster workflow. This can be revisited in the future, but at this time, it's not planned.

repo: replicatedhq/kots


text:
Feature: Support to Yubikey (HSM)

What is the task about?
The CLI could implement a nice interface/UX to get the public key information (key info)  and also use the Key for Root Keys on Ceremony (admin ceremony) and Metadata Update/Signing (metadata <metadata|sign>)
It would be interesting if the RSTUF CLI could use the Yubikey (HSM) for Ceremony and Metadata Update/Signing process.
We could take advantage of the implemented HSM Signer support from Secure Systems Lib.
Parent feature
No response
References
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Maybe https://github.com/theupdateframework/tuf-on-ci can be a good reference for this issue?

I recommend to generally use tuf-on-ci as inspiration for Signer integration. Jussi definitely knows how to use the Signer API as it is intended. I high-level comment about the Signer API in RSTUF

Only the CLI (dialog) should need to know about different signers and
At least in theory, the worker should be able to just use any signer with:

Signer.from_priv_key_uri(uri, public_key, secrets_handler)

where the URI could be passed, via service config, the public_key is taken from the trusted root, and the secrets_handler is implemented in a generic way in the worker, making secrets available that are also passed via service config.
I plan to look at how RSTUF uses the Signer API next week and make some more concrete suggestions.

@KAUTH FYI
https://github.com/repository-service-tuf/repository-service-tuf-worker/issues/419

Have a look at admin2 commands for this issue.

authors: MVrachev kairoaraujo lukpueh


text:
MsTest out not attaching all the results file to the report, when running multiple feature tests

Reqnroll Version
latest
Which test runner are you using?
MSTest
Test Runner Version Number
3.5.2
.NET Implementation
.NET 8.0
Test Execution Method
Command line – PLEASE SPECIFY THE FULL COMMAND LINE
Content of reqnroll.json configuration file
dotnet test --logger "trx;LogFileName=TestResults.trx"
Issue Description
Using ReqnRoll with Playwright I wish to attach screenshots and video to a report. However, when .trx file doesn't record all the files attached with the AddResultFile method. Only the first one appears?
I fixed images by I injecting the testContext for each hook and to fix videos I need to add the video for each Scenario, so I a senior has multiple Scenario it gets multiple links to the video!
There looks like two issues, BeforeFeature is executed only once for multiple features and AfterFeature doesn't accept video!
Steps to Reproduce
Create project
add multiple steps
create a hooks file with [Before] and [After] attributes
use _testContext.AddResultFile(path);
Link to Repro Project
No response

You can create files and pass the TestContext to these methods and the issue seems to be the files are deleted and copy copies to the final folder.
Do you know how I can tell what the final output folder will be, ie the one without the Deploy prefix.

You can create files and pass the TestContext to these methods and the issue seems to be the files are deleted and copy copies to the final folder.

I think I am lost now. If this works than what your real problem is? Could you please include some code snippet so that I can better understand?

Do you know how I can tell what the final output folder will be, ie the one without the Deploy prefix.

This is provided by the test runner, maybe you can configure it with a .runsettings file, but I don't know.

@potnoddle Do you have any feedback on this?

Closing this for now, if you have any feedback, please reopen.

authors: gasparnagy potnoddle

repo: reqnroll/Reqnroll


text:
.put results in an empty file

Using the following code I end up with a created file on a webdav server with the size of 0Byte.
	request
	.get('http://www.spielwiki.de/images/d/d9/Test.png')
	.pipe(request
	  .put('https://path.to.webdav.server/remote.php/webdav/mail2webdav/test.png')
	  .auth('user', 'pass', false))

Any ideas what I am doing wrong?
Thank you!

When I change the third parameter of auth to true everything is working as expected.
.auth('user', 'pass', false))

See the documentation about sendImmediately

authors: coldib simov

repo: request/request


text:
🛑 LinuxTalks.co is down

In db8bb35, LinuxTalks.co (https://linuxtalks.co/) was down:

HTTP code: 522
Response time: 15291 ms

Resolved: LinuxTalks.co is back up in 8150a43 after 46 minutes.

repo: reregaga/lor-upptime


text:
Arrow2D Archetype & Visualizer

What
Adds support for 2D arrows.
Lots of copy paste of 3D arrow things, but not so much to be terrible. Was actually pleasantly surprised that I didn't need much codegen-extensions. Deduplication (in particular in the Visualizer) takes more effort than it's worth I figured :)
The full vertical: Archetype, extensions, visualizer roundtrip tests, roundtripable examples!
Only left out dedicated archetype tests since there's nothing new & interesting here really.
That's what the example looks like: (kept it intentionally simple)

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

good eye on c&p errors. Enforcement of positional arguments is important here as well.
Will address on Monday!

So sweet to get in!

The example image looks 3D, which is very confusing for something that is explicitly 2D :)
I suggest removing the blue arrow, or pointing it up-right instead

The example image looks 3D, which is very confusing for something that is explicitly 2D :)

I thought that was a fun twist, but ehrm yeah maybe not helping 😆
I need something like that arrow otherwise our lack of configurable canvas cuts of the labels of the red & green arrow.
Maybe it's enough to just offset its start a bit? That way the origins aren't always zeroed.

updated example:

authors: Wumpf emilk nikolausWest

repo: rerun-io/rerun


text:
Reduce height of top and bottom panels

What

Part of https://github.com/rerun-io/rerun/issues/5589

Before

After

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

Alternatively we adjust the height dynamically, i.e. responding to the viewport size so that they are thin when space is scarce, and thick when there is a lot of space.

Let's try this


text:
Release artifacts to bintray

Modify build setup to publish artifacts to the bintray repos. There are three repositories created under the 'rerun' organization, one for each artifact type:

bin: https://bintray.com/rerun/rerun-bin
rpm: https://bintray.com/rerun/rerun-rpm
deb: https://bintray.com/rerun/rerun-deb

Lots of wrestling with automake, but it works finally.

authors: ahonor stagrlee

repo: rerun/rerun


text:
relax requirement of files being in a ReScript project for formatting

This lifts the current requirement for files to be located in an actual ReScript project to be formatted. It falls back to formatting using the vendored parser pretty printer in the extension itself if the file isn't located in a ReScript project.

Looking good. OK to merge?

authors: cristianoc zth

repo: rescript-lang/rescript-vscode


text:
ICS Calendar attachments are not recognized by outlook

I've tried attaching an ICS Calendar invite. The attachment itself works and is sent to the email. Gmail appears to recognize the ICS file and adds it to the user calendar. Outlook does not recognize it. Using the same domain and same configurations, this will work fine using SendGrid. The only real difference I could see was SendGrid asks for a type key like type: 'text/calendar; method=REQUEST' to make this work with Outlook.

Were you able to get this working or did you migrate to a different service?

Were you able to get this working or did you migrate to a different service?

Sadly still using SendGrid. It's a shame because Id love to use resend.

answered in the examples repo as well: https://github.com/resend/resend-examples/issues/154#issuecomment-2204267914
in the latest version of our SDK (v3.4.0 as of now), the attachments array accepts a content_type param 🙏

@vcapretz  unfortunately this fix for Outlook now produces the same problem on Gmail. The iCal renders in Outlook but Gmail will not recognize it and instead simply allows the ics to be downloaded as an attachment. Any ideas? I would imagine sending calendar invites via email would be popular with Resend.

@tscans I'm running into the same issue suddenly. Gmail no longer recognizes ICS calendar files that it previously did, providing the visual integration directly in the inbox with the Yes No Maybe. It has worked for years and suddenly doesn't. I strongly suspect Google changed something in how they process these things. I read somewhere they're wanting to push people towards registering and using this Schema format instead: https://developers.google.com/gmail/markup/reference/event-reservation#json-ld
But it seems crazy to me that they'd suddenly drop support for what is pretty standard stuff being used by a LOT of applications...

Experiencing the problem of the ics not being recognised by Outlook, but works fine on Gmail. Does anyone know the current state of this problem?
@vcapretz I see the change of yours content_type as snake case was changed to camel case. Is the what is causing Outlook to not recognise it?

authors: aalmho brianjuhl jfade tscans vcapretz

repo: resendlabs/resend-node


text:
npm install fails with ENOENT: no such file or directory, chmod '.../node_modules/drivelist/scripts/darwin.sh'

This is perhaps specific to my machine, which is running GNU/Linux (Ubuntu), but seems like probably not. I'm using node v8.9.4 and npm v5.7.1.
Looks like https://github.com/resin-io-modules/drivelist/tree/master/scripts no longer includes this file?

Yup, that was a bug, fixed by #256 and published as drivelist@6.1.1

All good now, thanks.

authors: andrewmbenton jhermsmeier

repo: resin-io-modules/drivelist


text:
Function to enable the NM service

Write a function that uses the systemd DBus API to enable the NM service.
It should return a result.
Questions:

Should the function return instantly or once the service has been successfully enabled, should this be optional?

https://github.com/resin-io/hq/pull/453


text:
fix(writer): Use uncompressed or estimated size for progress

This makes the writer use the image's uncompressed size, instead of the original size to avoid the progress percentage going above 100%.
Change-Type: patch

@jhermsmeier Can you link me to an image that reproduces the issue, so I can play around with it?

This might connect to #1171 and #638 ?
@jhermsmeier Surely if the final size is only an estimate, then the percentage might still go above 100% if the actual size is bigger than the estimated size?

@jviotti You should be able to see it quite significantly on the support-dmg branch when flashing the Etcher .dmg, as there are a couple hundred MB of compressed zeros in there (and that'll rocket up to 400%+). Otherwise those Pine64 images should also do the trick.

@lurch The issue with gzip is that the original size is stored as a uint32 as the modulo of 2^32 – it can't encode sizes larger than 2^32 - 1, as it doesn't store the factor – meaning, sizes for files over 4GB will always be horribly wrong by design.
Anyways, I don't think this relates to anything gzip specific.

Okay, what about for bz2 images then? Will they end up with progress percentages > 100%

@lurch this has no relation to any file format whatsoever, if the estimates are off because the file format's weird then there's nothing we can do about it. This just mends the logic behind the progress values, as previously the percentage would be calculated based on the file size (i.e. bytesWritten / fileSize), but of course the written bytes would exceed that value, since the uncompressed image will always be larger. Now it's bytesWritten / uncompressedSize, which should not exceed the 100% unless the estimate is too rough or inaccurate.

Agreed. But the commit message was implying that this fixes the progress percentage to never go above 100%, and I was just clarifying (as you've also done) that this isn't always the case ;-)
Might be worth clarifying that in the commit message?
And it does relate to #638 a little bit, see this comment and this comment. (although I'm not familiar with that part of the code, so I dunno if those comments still apply - @jviotti ?)
And if my suggestion in this comment got implemented, then we'd indeed never end up with a progress greater than 100% ;-)

I'm still struggling to understand this fix. If you check the writer code (https://github.com/resin-io-modules/etcher-image-write/blob/master/lib/write.js#L113), you'll see that the pipe starts with the compressed image stream (https://github.com/resin-io-modules/etcher-image-write/blob/master/lib/write.js#L121), and applies the transform stream after the progress stream (https://github.com/resin-io-modules/etcher-image-write/blob/master/lib/write.js#L133).
This was done because we should still be able to calculate a correct progress bar even for images that we don't have a correct uncompressed size for (like bzip2).
With this change, we'd be calculating the percentage from the compressed stream using the uncompressed size, which wouldn't be correct.
Also, what happens if the final value is just an estimate?

Hmm, I see – I was on a completely wrong path with this then.
Let's close this and I'll get to this issue while integrating the blockmap and pipage anyways (which is what I'm working on now).

authors: jhermsmeier jviotti lurch

repo: resin-io/etcher


text:
Fix command PING to work properly

Connects-To: #383
Change-Type: patch
---- Autogenerated Waffleboard Connection: Connects to #383

@horia-delicoti the travis build here is failing because it needs the env vars from our travis settings, which contain credentials used by the tests, and those aren't available to PRs from forked repositories.
Can you make these changes on a branch in this repo, and then open a PR from that? I think you should have permissions for that, but let me know if not. I'm going to close this in the meantime.

authors: horia-delicoti pimterry

repo: resin-io/resin-sdk


text:
Updated CherryPick to v1.1.0

Updated CherryPick to v1.1.0

Additional note that [assembly: AssemblyVersion("1.1.0.0")] and [assembly: AssemblyFileVersion("1.1.0")] should 'match'

Additional note that [assembly: AssemblyVersion("1.1.0.0")] and [assembly: AssemblyFileVersion("1.1.0")] should 'match'

Strange, the AssemblyFileVersion should be set according to the version obtained from AssemblyVersion which is defined in the csproj. If that is not the case, Cyro made a mistake. I was not even aware the file properties showed a different assembly version.

Actually looks like more a result of the build process changing this anyway.. even if it is set as 3 section, seems to write it as 4 anyway. Although it is more visibly apparent because of their Assembly.GetName().Version.ToString(); will grab that instead of showing the 1.1.0 form.

On file it might show as 4 numbers, but it doesn't looks like it's causing much issues as long as people still see in manifest and in assembly that the version matches. I think.

Shouldn't be an issue, but may be a suggestion for their version string to not use that method of grabbing the version. Instead going the other direction of using the Version string to set the assembly attributes.

Good point. I'll escalate an issue to let them know.

An example is shown in https://github.com/resonite-modding-group/ExampleMod/blob/main/ExampleMod/ExampleMod.cs setting the attributes from a version constant, although it looks like they set the version in their csproj instead

Not sure offhand which ways get both to be set 'correctly' but this atleast shows the 'Version' string as 1.1.0

Well, the constant way does sounds more handy, but yeah, they set it in csproj, then used $(version) to define the AssemblyVersion, then Assembly.GetName().Version.ToString(); in the cs file took the version from the Assembly but decided to parse it as 4 numbers instead of its written 3.

We'll see if he changes it, getting matching numbers is important, though in this particular case it at least doesn't break the mod.

authors: SectOLT XDelta


text:
update handle name in service name

import handle as checkout_handle, or change first param on line 33 from checkout_handle to handle

Hi @johnniemorrow
Thank you for the fix!

authors: gvdongen johnniemorrow

repo: restatedev/examples


text:
restic check should report if superseded index files still exist

Output of restic version
restic 0.9.6 (v0.9.6-253-g642da0a0-dirty) compiled with go1.14.3 on linux/amd64
How did you run restic exactly?
Use the repo from /cmd/restic/testdata/repo-obsolete-index.tar.gzfrom
https://github.com/restic/restic/pull/2718/commits/abd85e65c0d23c6ce20807edc410e7393f36d828
(password is "geheim").
This repo contains two index files: {392240e9 e88b8990} which are identical except that  392240e9 supersedes e88b8990. This can be easily checked by running restic cat index on both files.
run restic check -r /path/to/repo with the path to the unpacked repo.
What backend/server/service did you use to store the repository?
local backend
Expected behavior
check should warn that superseded index files still exist in the repo.
Actual behavior
pack f5c03970 contained in several indexes: {392240e9 e88b8990}
pack 88128df7 contained in several indexes: {392240e9 e88b8990}
This is non-critical, you can run `restic rebuild-index' to correct this

Steps to reproduce the behavior
see above
Do you have any idea what may have caused this?
superseded index information is not handled by the check command
Do you have an idea how to solve the issue?
implement handling of superseded indexes within check
Did restic help you today? Did it make you happy in any way?
Makes me happy most days as I learned a lot about go programming when working on restic.
Sometimes makes my family unhappy because I'm spending too much time on it. :smirk:

The superseded field in the index has been removed in https://github.com/restic/restic/pull/4812

authors: MichaelEischer aawsome

repo: restic/restic


text:
Automation for firewall allocation

Type of PR

[x] Documentation changes
[ ] Code changes
[ ] Test changes
[ ] CI-CD changes
[ ] GitHub Template changes

PR Checklist

[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] My code follows the code style of this project.
[ ] I ran lint checks locally prior to submission.
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Purpose of PR

Does this introduce a breaking change

[ ] YES
[ ] NO

Validation

[ ] Unit tests updated and ran successfully
[ ] Update documentation or issue referenced above

Issues Closed or Referenced
Closes #1031

Closing as duplicate.

repo: retaildevcrews/ngsa-asb


text:
docs: fix typos

This PR fixes two typos in README.md. Thank you for publishing useful code. The number of examples should be fix at commit c390a511eeabe670e1ecff932b05407629644a49.
If this repo doesn't accept other's commit, I don't mind if this PR is closed.

Thank you for modifying the typo! I merge this PR.

authors: retarfi upura

repo: retarfi/language-pretraining


text:
handshake on multiplex subscription

Fixes #567, which extended to all read queries: none of them would cause a handshake, so but they would block on the handshake, so they'd have to wait until a write query or an explicit .subscribe was called. Now we explicitly send the handshake on each request unless we've already sent it.

This change is

In that case, shouldn't we just always send the handshake lazily before the first query instead of also attempting it when the socket is opened?

... and then we could just make hz.connect = () => socket.sendHandshake()?

Good point, I'll make that change. Though we still have a potential problem when subscribing to the socket it may not actually send the handshake. There aren't a lot of good reasons to do that though, and we don't expose the socket externally. When we make the jump to typescript it'll definitely be private.

Ok, I made the fix and then reverted it. It doesn't properly emit the disconnected event when there's an error when you do this.

repo: rethinkdb/horizon


text:
Generate export file from list of citekeys

I'm using BBT with pandoc. I'd like to be able to add citations using citekeys, without having manually curate a collection to export the .bib or .json file at the end of the process.
Is it possible to generate a list an export file (BibLaTeX or CSL JSON) from a list of citekeys? If not, could a function be added for that, such as a button in the BBT Preferences and/or as a parameter passed to the CAYW interface?

Would #1477 cover your needs? Sounds similar, but not necessarily the same.

I'm not really following what that is issue is about. I don't really know what the AUX scanner feature does.

The workflow I'm envisioning is being able to add citations to my Markdown document, then extract all of the citekeys at the end and use these to generate a .json file.

I could add a method to the JSON-RPC endpoint.
As to #1477, during a bibtex compilation, multiple files are created as part of the process, one of which has extension .aux and it hold information about the references cited in the latex document. The aux scanner parses the aux file and populates a collection with it.

Oh, got it!

If you don't have one, the #1477 workflow won't help you much; you'd know if you had one, because the latex compile litters the working directory with them.
Sample: output.aux

I rarely use TeX, mostly Markdown to HTML or DOCX. But I think I might be able to make a dummy aux file to fill this purpose.

No, don't do that, I'll get you an endpoint you can post a bunch of citekeys to.

:robot: this is your friendly neighborhood build bot announcing test build 5.2.21.6436 ("export endpoint")
Install in Zotero by downloading test build 5.2.21.6436, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

What's the API for the endpoint?

It's going to be
curl http://localhost:23119/better-bibtex/json-rpc -X POST -H "Content-Type: application/json" -H "Accept: application/json" --data-binary '{"jsonrpc": "2.0", "method": "items.export", "params": [[<list of citekeys>], "<format>"] }'

but it doesn't work yet. In format you can specify either a name (better at the start not necessary) to get one of the BBT formats, or a translator guid to get any one that's available at that moment in Zotero.

found the error. new build incoming.

:robot: this is your friendly neighborhood build bot announcing test build 5.2.21.6438 ("look up by citekey, not itemID, genius")
Install in Zotero by downloading test build 5.2.21.6438, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Awesome! Thank you! It seems to work great.

I'll roll it into a release. I think GH is still on the fritz -- I saw your email, but don't see the message here.

Actually, it's not working for me. I misspoke and deleted.
curl http://localhost:23119/better-bibtex/json-rpc -X POST -H "Content-Type: application/json" -H "Accept: application/json" --data-binary '{"jsonrpc": "2.0", "method": "items.export", "params": [["Bonachecompensationexpatriatesreview2006", "BeckerModelbasedmetaanalysis2009"], "json"] }'

Then it gets no response. Debug ID: XPY8ASZX-euc

Ah, nevermind. It works if I specify csljson for the format, but not with just json.

Thank you again!

My pleasure. I'll roll it into a release when I close a few issues I'm currently working on. I could have json work too BTW, it's just a matter of filtering out csl.

Just json should work now too.

authors: blip-bloop bwiernik retorquere

repo: retorquere/zotero-better-bibtex


text:
Title Export-Error in German papers and books

Hi,
i have a lot of german paper and books in my work. If I´m trying to export from Zotero with Better BibTex, the add-on changes the names to this:
title = {Der {{Güterverkehr}} von Morgen {{LKWs}} Zwischen {{Transporteffizienz}} Und {{Sicherheit}}},
correct would be (used normal bibtex export from Zotero):
title = {Der {Güterverkehr} von morgen {LKWs} zwischen {Transporteffizienz} und {Sicherheit}},
So some of the words whitch shouldn´t start with a capital letter get somehow a transformation.
So far this is only happening with german titles not the english ones.
Any ideas how I can fix this problem?
Best regards
Alex

If you set the language of the reference to German the behavior will be turned off. What the default Zotero exporter does is in fact not correct; German (or more specifically: non-English) titles should not get capitalization protection at all, and if you don't mark your references as non-english, some bib(la)tex styles will still try to capitalize von morgen when rendering your document.

Wait what? This is not happening with your English references? Can you submit a sample of an English reference which doesn't get recapitalization by right-clicking it and selecting "report BBT error"?

ICSKJ57D
this english ref is working fine:
@inproceedings{falie_noise_2007,
title = {Noise {{Characteristics}} of {{3D Time}}-of-{{Flight Cameras}}},
volume = {1},
doi = {10.1109/ISSCS.2007.4292693},
abstract = {Time-of-flight (TOF) cameras are based on a new technology that delivers distance maps by the use of a modulated light source. In this paper we first describe a set of experiments that we performed with TOF cameras. We then propose a noise model which is able to explain some of the phenomena observed in the experiments. The model is based on assuming a noise source that is correlated with the light source (shot noise) and an additional additive noise source (dark current noise). The model predicts well the dependency of the distance errors on the image intensity and the true distance at an individual pixel.},
timestamp = {2016-06-20T07:14:57Z},
booktitle = {2007 {{International Symposium}} on {{Signals}}, {{Circuits}} and {{Systems}}},
author = {Falie, D. and Buzuloiu, V.},
month = jul,
year = {2007},
keywords = {3D time-of-flight cameras,Additive noise,additive noise source,cameras,dark current noise,distance errors,distance measurement,Image analysis,image intensity,Image processing,image sensors,Information analysis,Laboratories,Layout,Lighting,light sources,measurement errors,modulated light source,optical modulation,optical noise,Pixel,shot noise,TOF cameras},
pages = {1--4}
}

Yeah but that has undergone title casing. It's just that all the words that weren't already capitalized are always excluded from titlecasing (words like on, and, etc). The rules for title/sentence-casing and how bib(la)tex expects its input are language-dependent and somewhat crazy.

You don't have to fully type out German in the language field BTW. If you type ger BBT will know enough.

Ahh, ok !
Thank you for the quick response. :-D

Zotero references have a language field.
The Zotero export treats every reference as English but then doesn't follow the proper bib(la)tex rules. Zotero recommends that references be stored in Zotero in sentence case, as that is what the embedded citation processor expects. Bib(la)tex needs references in Title Case for English references (but English references only) and sentence case for non-English. The default Zotero export does a little bit of both; it does do caps protection (which it shouldn't for non-English) but it does not do title-casing (which it should for English titles given its own recommendations)
It is possible to suppress title casing (even though this will on occasion yield non-compliant bib(la)tex) by typing about:config in the address bar of Firefox (assuming you use the plugin version of Zotero), searching for suppressTitleCase, and set it to true. This will keep caps-protection but will never title-case, regardless of language set or not set (also not for references explicitly marked as English!)

Let me just point out that title = {Noise {{Characteristics}} of {{3D Time}}-of-{{Flight Cameras}}}, does not exemplify best practice – one should use [Noise characteristics of 3D time-of-flight cameras] in Zotero, which BBT exports (correctly) as title = {Noise Characteristics of {{3D}} Time-of-Flight Cameras} (both bibtex and biblatex).
Also, at the risk of sounding pedantic, ‘sentence case for non-English’ is not quite right, since non-English languages just don’t make a distinction between title case and sentence case: they have one case that never changes (and though this often happens to look like sentence case, it doesn’t always, as e.g. in German).
Finally let me add that I’m not a big fan of a suppressTitleCase option. I feel there’s only one way to skin this particular cat, and BBT is already doing it quite well. Providing an option which, as you say yourself, ‘will on occasion yield non-compliant bib(la)tex)’ will ultimately do more harm than good.

You're right that "sentence case for non-English" isn't correct. When the reference is non-English, BBT and biblatex alike will just trust the capitalization as you put it in.
I don't like the option either, and I don't want to encourage it, which is why it's a hidden option. But the request to "do what zotero does" comes back occasionally (in the tracker but also just through mail) and some people are quite adamant. It's less effort for me to direct them towards the hidden pref than it is to explain this quite complex issue (and life's too short, and I'm too busy). I personally had absolutely no idea biblatex was so complex under the hood, so I can easily imagine people not knowing or caring about this behavior.

And not only is the time-of-flight reference not best practice, there are styles (Chicago?) where it will simply yield the wrong result.

Actually it’s apa.csl and biblatex-apa, and other sentence-case styles that will yield the wrong result with either [Noise Characteristics of 3D Time-of-Flight Cameras] or title = {Noise {{Characteristics}} of {{3D Time}}-of-{{Flight Cameras}}},.

authors: njbart retorquere uni-hb


text:
6 new documentated instances

They should be all correct as I double checked everything in RetroStudio AND the official Roblox documentation page.

Thank you for your contribution! Can I please have your discord name so you can receive the role?

erazias

repo: retro-dev-rblx/Docs

license: WTFPL


text:
Current line number when in relative line number

This should be a simple good first issue.

code is here

repo: revi-editor/revi


text:
Update generated proxies

Updates stencil-generated files from RevoGrid.
This fixes compilation errors (headerresize case change).
closes #5, closes #6, closes #8

please someone approve this PR.

Updated to 4+

authors: bahablgn dratzinger revolist

repo: revolist/angular-datagrid


text:
Additional FireFox games

I found it on www.lemon64.com
four Firefox games missing from Gdash.
I upload them as core dumps from WinVice to the vsf file.
These are:
Firefox57
000 Whitedash
001 Yellowdash
002 Orange dash
FireFox.zip

By the way.
At https://wowroms.com/
you can find missing No_One games
13,14,15,28,29,32,33,34,35,36,37
Unfortunately, I couldn't find 38.39 anywhere
I pass them in vsf file format
no1.zip

Unfortunately I cann't open your vcf's. Says:
"Magic string mismatch in snapshot"
But I could try to extract cavesets from the games directly, if you give the direct links to ROMs.
P.S.: I've already found White Dash and managed to convert it to gds.

hmm..
Gdash reads WinVice dump snapshots without any problems.
All right.
I am sending the same games on D64 floppy disks
pack.zip

hmm...
I have never before tried to open vsf by GDash.
It worked.

CWS.
I congratulate you on the release of the third game of your series.

@zsommk I've got them all.
https://github.com/revvv/gdash-export-CrLi/pull/44 Additional FireFox and No One's games

OK. Thank you.

BTW,
/caves/No_One/No_One_s_Boulder_32.gds == /caves/The_Blockheads/Boulderdash_32.gds
/caves/No_One/No_One_s_Boulder_33.gds == /caves/The_Blockheads/Boulderdash_33.gds
/caves/No_One/No_One_s_Boulder_37.gds == /caves/The_Blockheads/Boulderdash_37.gds
/caves/No_One/No_One_Boulder_Head_06.gds == /caves/The_Blockheads/Boulderhead_6.gds
So, it's very possible that the maps from No One Boulder 38 and 39, you can't find, are the same as
/caves/The_Blockheads/Boulderdash_38.gds
/caves/The_Blockheads/Boulderdash_39.gds
which we already have.

That would explain a lot.
On the website https://csdb.dk/
there is information:
The Blockheads (TBH)
AKA:
Blockheads Distribution Company BDC B.D.C.
group type :
Fixing Group
Base Country :
Netherlands
User rating: awaiting 8 votes (8 left)
All Members :
No One (ex) .... Coder, Cracker, Hacker
Which means No One is a member of the group.

Here is my full C64 Boulder Dash collection - maybe there are games included that are still missing in GDash?
https://www.dropbox.com/scl/fi/zvb5s8ql8ou77chv5b4ja/BoulderDashCollectionC64.zip?rlkey=3be4157nj59g3tbcci8zsoh81&dl=0

Here is my full C64 Boulder Dash collection - maybe there are games included that are still missing in GDash?
https://www.dropbox.com/scl/fi/zvb5s8ql8ou77chv5b4ja/BoulderDashCollectionC64.zip?rlkey=3be4157nj59g3tbcci8zsoh81&dl=0

Thanks.
I was able to open&extract&convert the following missing cavesets:

Add & TKR Boulder Pack A - E
Artis Boulder Dash Caves
BlockHeads Boulder Head 7
BlockHeads Boulder Head 8
Boulder Dash The Lost Caves 11
Boulder Dash The Lost Caves 12
Boulder Dash The Lost Caves 13
Boulder Dash Cribble
CS Boulder 2
DiamondRush 1 - 5
Exotic Boulder Dash 1
Boulder Dash Expert 1 - 3
RSD Boulder Dash
Final Game 1 - 6
NoOne Final Boulderdash
NoOne Surprise Boulder
NoOne Work Boulder
Rockford Elf Boulder Dash Games
Rockford Profi Boulder 20, 21
Rockford True Boulder 1
Ron Van Schaik Dash 15
Ron Van Schaik Dash 16
Super Dash One
KK Boulder 26, 27, 29, 31, 33 - 40

There are also several collections that need more time to investigate do they bring something unique:

Klaus & Reinhold Boulder Dash 1 - 10
Klaus & Reinhold Boulder Dash 11 - 20
Klaus & Reinhold Boulder Dash 21 - 30
Klaus & Reinhold Boulder Dash 31 - 40
NoOne All Games On One Disk 1 - 6
NoOne All Games On One Disk 7 - 12
NoOne All Games On One Disk 13 - 18
NoOne Final Boulder 1 Speed Up Version
NoOne Final Boulder 2 Speed Up Version

Other missing in GDash and present in your collection games I've already tried to open/extract/convert before.
For instance:

Apollo8502 Boulder Dash + Construction Kit -- Could not import cave data -- unknown cave format!
Boulder Dash 4 Screens -- all caves are empty after conversion
Boulder_Dash_64000 -- Could not import cave data -- unknown cave format!
Boulder Dash 99 A, B, C, D, G, H -- Could not import cave data -- unknown cave format!
Boulder Dash 99 I, J, K, M -- Could not import cave data -- unknown cave format!
Boulder Dash 1001 Unibit -- Could not import cave data -- unknown cave format!
Boulder Dash Advanced TRC -- empty caves after conversion
Boulder Dash Bosh -- Not family-friendly game
Boulder Dash DTV -- Could not import cave data -- unknown cave format!
Boulder Dashes Honz -- the game ends after start
Boulder Dash The Lost Levels 2 -- syntax error on run ttl 2 -- syntax error in 48136
Casey Boulder Dash 2000 -- empty caves after conversion
GeekDash1 -- how to start the game?
Marek Roth Crazy Dream 10 -- Could not import cave data -- unknown cave format!
Match Buster --  Not family-friendly game
Phoenix Runner Up Dash -- Could not import cave data -- unknown cave format!
Ruben Spaans Boulder Dash 50 -- Could not import cave data -- unknown cave format!
SPG's BoulderDash -- Could not import cave data -- unknown cave format!
Super Boulder Dash -- Could not import cave data -- unknown cave format!
Swedish Boulder Dash -- Could not import cave data -- unknown cave format!
Wolfsoft Boulder Dash 9 & 12 -- Could not import cave data -- unknown cave format!

https://github.com/revvv/gdash-export-CrLi/pull/48 new caves from cwscws's C64 Boulder Dash collection

Crazy Dream 10 was done with the XDC Engine from Marek Roth, so the format is certainly different and is therefore not recognized by GDash. There are also new elements in it not available in GDash…

CWS
Maybe you know something from LogicDeLuxe about its XDC engine?
I asked him on www.boulderdash.nl/forum many times about it, but there was no answer.

There is a readme somewhere about CD10. I remember I read it. LogicDeLuxe is hard to reach, I know.

Just a little info: Coolshaker Union Gang KG is Klaus Quindt. I was in contact with him about 18 years ago - he must be over 80 now if he is still alive…

@cwscws
CWS a.k.a. Claus Skrepek

Regarding

Klaus & Reinhold Boulder Dash 1 - 10
Klaus & Reinhold Boulder Dash 11 - 20
Klaus & Reinhold Boulder Dash 21 - 30
Klaus & Reinhold Boulder Dash 31 - 40

First of all, Klaus & Reinhold == The Magic Eye member Papis a.k.a Papi's.
When I converted all 40 cavesets, I found that:

Papis\Boulder_Dash_01.gds == First_Star_Software\Boulder_Dash_1.gds
Papis\Boulder_Dash_02.gds == First_Star_Software\Boulder_Dash_2.gds
Papis\Boulder_Dash_03.gds ~= American_Action\Boulder_Dash_3.bd (different color palette)
Papis\Boulder_Dash_04.gds == Dr_Watson\Dr_Watson_4.gds
Papis\Boulder_Dash_06.gds == Don_Pedro\Boulderdash_VI.gds
Papis\Boulder_Dash_07.gds == Don_Pedro\Boulderdash_VII.gds
Papis\Boulder_Dash_08.gds == Don_Pedro\Boulderdash_VIII.gds
Papis\Boulder_Dash_10.gds == Don_Pedro\Boulderdash_X.gds
Papis\Boulder_Dash_11.gds == Don_Pedro\Boulderdash_XI.gds
Papis\Boulder_Dash_16.gds == No_One\No_One_s_Boulder\No_One's_Boulder_16.gds
Papis\Boulder_Dash_17.gds == No_One\No_One_s_Boulder\No_One's_Boulder_17.gds

So I added all except listed above.

NoOne All Games On One Disk 1 - 6
NoOne All Games On One Disk 7 - 12
NoOne All Games On One Disk 13 - 18
==
\No_One\Final_Boulder\

NoOne Final Boulder 2 Speed Up Version
contains also 2 different games

BOULD.CHANGE1
BOULD.CHANGE2

BOULD.CHANGE1 is almost equal to No_One\Boulder_Change_1.gds (different color palette)
So I decided to replace No_One\Boulder_Change_1.gds by a new one and add No_One\Boulder_Change_2.gds

authors: cwscws renyxadarox zsommk

repo: revvv/gdash-export-CrLi


text:
Fix error message for wrong query frontend address config

Currently the error log prints distributor address instead of queryfront end address.

@weeco

repo: rewe-digital/cortex-gateway


text:
Cinder reports wrong device name

Summary
It seems that the REX-Ray Cinder driver relies on cinder to report the right device name, and also tries to force this by setting the device name by basically passing --device (if defined in opts).
However, according to the documentation:

Using device names as the primary per-instance identifier, and exposing them in the API, is problematic for Nova mostly because several hypervisors Nova supports with its drivers can’t guarantee that the device names the guest OS assigns are the ones the user requested from Nova.

This seems especially true for users of libvirt (like we do), and there are some cases (we experienced them) where it is not possible for the REX-Ray cinder driver to correctly mount the volumes due to a mismatch between the device name reported by Cinder and the actual device name on the VM (= the OpenStack nova instance/server).
Bug Reports
Related reports/pull requests

https://github.com/rexray/rexray/issues/346
https://github.com/rexray/rexray/pull/357
Unfortunately, it does not seem that the code was merged.

Version
We're using the rexray/cinder docker plugin:
"PluginReference": "docker.io/rexray/cinder:0.11.1"

Expected Behavior
Cinder driver attaches volume to VM and mounts it.
Actual Behavior
In certain cases, it seems that the udev magic of the VM or the order of attachments gets somehow in a state where Cinder reports a volume attached to /dev/vdX but the VM reports the device as /dev/vdY.
So the device gets actually attached (also visible via CLI and Horizon GUI), but the reported device there is simply wrong. For example: last time this happened Cinder reported /dev/vdf but on the VM the device was actually /dev/vdi.
Steps To Reproduce
Unfortunately, I'm not sure how to reliably reproduce it, but it seems to happen regularly when attaching and detaching volumes multiple times without restarting the VMs running on OpenStack.
For example: I did this by running Jenkins builds starting Docker containers, mounting REX-ray Cinder volumes.
Configuration Files
IMHO not relevant
Logs
Docker plugin log
The log file contains actually the /dev/vdf vs /dev/vdi case described earlier:
Feb 26 04:39:20 somehost env[4998]: time="2018-02-26T04:39:20+01:00" level=info msg="time=\"2018-02-26T03:39:20Z\" level=debug msg=\"http header\" Libstorage-Localdevices=[cinder=/dev/dm-0::,/dev/vda::,/dev/vda1::,/dev/vda2::,/dev/vda3::,/dev/vda4::,/dev/vda6::,/dev/vda7::,/dev/vda9::,/dev/vdb::,/dev/vdc::,/dev/vdd::,/dev/vde::,/dev/vdh::,/dev/vdi::] host=\"unix:///var/run/rexray/055954627.sock\" route=volumeInspect server=cold-skinner-ki time=1519616360708 tls=false txCR=1519616360 txID=fd40cedf-936a-4f0b-78ce-a1952726fbfc " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:20 somehost env[4998]: time="2018-02-26T04:39:20+01:00" level=info msg="time=\"2018-02-26T03:39:20Z\" level=debug msg=\"getting storage service\" host=\"unix:///var/run/rexray/055954627.sock\" route=volumeInspect server=cold-skinner-ki service=cinder time=1519616360708 tls=false txCR=1519616360 txID=fd40cedf-936a-4f0b-78ce-a1952726fbfc " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:24 somehost env[4998]: time="2018-02-26T04:39:24+01:00" level=info msg="time=\"2018-02-26T03:39:24Z\" level=debug msg=\"manually calculating attachment state\" host=\"unix:///var/run/rexray/055954627.sock\" instanceID=\"cinder=bb137d5d-4e3b-4963-916a-cfc800147085\" route=volumeInspect server=cold-skinner-ki service=cinder storageDriver=cinder task=1 time=1519616364049 tls=false txCR=1519616354 txID=5c00b707-5c77-445c-4f37-67a575dc175f " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:24 somehost env[4998]: time="2018-02-26T04:39:24+01:00" level=info msg="time=\"2018-02-26T03:39:24Z\" level=debug msg=\"including volume\" attachmentState=attached host=\"unix:///var/run/rexray/055954627.sock\" instanceID=\"cinder=bb137d5d-4e3b-4963-916a-cfc800147085\" route=volumeInspect server=cold-skinner-ki service=cinder storageDriver=cinder task=1 time=1519616364049 tls=false txCR=1519616354 txID=5c00b707-5c77-445c-4f37-67a575dc175f " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:24 somehost env[4998]: time="2018-02-26T04:39:24+01:00" level=info msg="time=\"2018-02-26T03:39:24Z\" level=debug msg=\"driver is not StorageDriverVolInspectByName\" host=\"unix:///var/run/rexray/055954627.sock\" instanceID=\"cinder=bb137d5d-4e3b-4963-916a-cfc800147085\" route=volumeInspect server=cold-skinner-ki service=cinder storageDriver=cinder task=0 time=1519616364051 tls=false txCR=1519616360 txID=fd40cedf-936a-4f0b-78ce-a1952726fbfc " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:24 somehost env[4998]: time="2018-02-26T04:39:24+01:00" level=info msg="time=\"2018-02-26T03:39:24Z\" level=debug msg=\"getting storage service\" host=\"unix:///var/run/rexray/055954627.sock\" route=serviceInspect server=cold-skinner-ki service=cinder time=1519616364054 tls=false txCR=1519616364 txID=7220a732-0ae5-400d-6ac4-f784e0bf8f6f " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:24 somehost env[4998]: time="2018-02-26T04:39:24+01:00" level=info msg="time=\"2018-02-26T03:39:24Z\" level=error msg=\"docker-legacy: Mount: my-cinder-volume: failed: open /dev/vdf: no such file or directory\" host=\"unix:///var/run/rexray/055954627.sock\" integrationDriver=linux osDriver=linux service=cinder storageDriver=libstorage time=1519616364061 " plugin=e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a
Feb 26 04:39:24 somehost env[4998]: time="2018-02-26T04:39:24.190295727+01:00" level=error msg="Handler for POST /v1.32/containers/5aa953796a14a6852e7b064f154f9a56f72662db7a79e4daa577008f215b760f/start returned error: error while mounting volume '/var/lib/docker/plugins/e60c67bba2140d9df6092a9c2da33709b9c87cdfaffe899449523af47abbfc0a/rootfs': VolumeDriver.Mount: docker-legacy: Mount: my-cinder-volume: failed: open /dev/vdf: no such file or directory"

I tried to fix the issue, based on https://github.com/rexray/rexray/pull/357:

https://github.com/ederst/rexray/tree/use-disk-by-id-for-cinder
https://github.com/ederst/rexray/tree/use-disk-by-id-for-cinder_2

Also, I have built a docker plugin based on "use-disk-by-id-for-cinder_2" (obtainable from https://hub.docker.com/r/ederst/cinder/tags/), and I'm testing it.
If necessary I can create a pull request out of one of the solution, but I'm not a GO programmer, so I don't expect anything.

Since I've installed the Cinder driver Docker plugin with my code, no errors happened so far. FYI, if anyone is.

It seems the k8s had the same issue in the past https://github.com/kubernetes/kubernetes/issues/33128

authors: ederst kumy

repo: rexray/rexray


text:
How to add class names to markdown components?

I want to control the style of the markdown components using CSS classes. I'm setting the className prop to every component like this:
import React from 'react'
import CommonMark from 'commonmark';
import ReactRenderer from 'commonmark-react-renderer'

const parser = new CommonMark.Parser();
const renderer = new ReactRenderer();

const setMarkdownCSSClassToComponentFunc = (className) => {
  return (component) => React.cloneElement(component, { className })
}

const markdownToComponentArray = (markdownSource, markdownClass) => {
  const ast = parser.parse(markdownSource)
  const componentArray = renderer.render(ast);
  const setMarkdownCSSClassToComponent = setMarkdownCSSClassToComponentFunc(markdownClass)
  return componentArray.map(setMarkdownCSSClassToComponent)
}

export default markdownToComponentArray

This seems to work fine with <p> elements, but it doesn't work at all with other elements like <h2> or <pre>. Can anyone please give me any suggestions?

I just pushed v4.3.3 which makes className a "core prop", which should make sure it's included by all renderers.
Do note that the code you have above will only address root-level components, but that might be OK depending on your use case?
For even more control, you can use custom renderers.

authors: GAumala rexxars

repo: rexxars/commonmark-react-renderer


text:
Fixed README.md

I ran the example but realized that there was a typo in the README.md.
var initCacher = require('sequelize-redis-cache');
var cacher = initCache(db, rc);

should be:
var initCacher = require('sequelize-redis-cache');
var cacher = initCacher(db, rc);

Thanks!

authors: Naoto-Ida rfink

repo: rfink/sequelize-redis-cache


text:
platypus setup should be included in setup.sh

(same as above)

I think users must register to Platypus downloads page for manual download.
(Platypus download)
I wonder if there is a method for automatic download, such as using FTP. Any ideas?

@alexbmp
An automatic download may violate author's policy. So I think we should ask them (as you said).

@xenigmax
I got this reply e-mail from a Platypus developer.

We can include Platypus in our pipeline; it's distributed under a GPL license.
About his "preferences", I think we can notice of him the total download counts.
However, I think downloaders should decide whether they want update notices on Platypus. (Should make a configuration file about this.)
How do you think?

Dear Seongmin,
Thank you for your email.  Since Platypus is distributed under the GPL license it is fine to re-distribute as long as the original license is in place, so yes, you may include it in another open-source package.
Having said that, we would prefer to keep a tally of the downloads of Platypus, as well as a list of emails of users who would like to be informed about version updates.  If there is any way for you to collect this information, we would very much appreciate a regular update of this list, so that we can let grant bodies know of download numbers, and let users know of (infrequent) updates.
Would this be possible?
Best wishes
Gerton

@alexbmp
I think you should not post your emails to a public space.
So I deleted that part.

Good. Let's do it.
2/3
We do not collect personal information including emails.
So..there is no way to do that..

Maybe we can let users know that there is a mailingl list for Platypus. Just simply add that to readme or something. Then they can register if they want..
And.. you and I should register that mailing list.

Shoot... I just found out others can also view our posts here. I'm sorry for that;; Thanks for deleting the part.

Updated my pull request
2), 3)
Updated README.rst in the pull request.
While downloading Platypus, I was automatically included in the mailing list, so okay.
I also think users should enlist on the mailing list if they want to. I shared the current situation, very politely and thankfully, with Gerton about this.

authors: alexbmp xenigmax

repo: rg-korea/rainbow