google-sheet-sync can't deploy

How to reproduce these conditions
Sample name or URL where you found the bug
https://github.com/firebase/functions-samples/tree/Node-8/google-sheet-sync
Failing Function code used (including require/import commands at the top)
// Sample trigger function that copies new Firebase data to a Google Sheet
const functions = require('firebase-functions');
const admin = require('firebase-admin');
admin.initializeApp();
const {OAuth2Client} = require('google-auth-library');
const {google} = require('googleapis');
// TODO: Use firebase functions:config:set to configure your googleapi object:
// googleapi.client_id = Google API client ID,
// googleapi.client_secret = client secret, and
// googleapi.sheet_id = Google Sheet id (long string in middle of sheet URL)
const CONFIG_CLIENT_ID = functions.config().googleapi.client_id;
const CONFIG_CLIENT_SECRET = functions.config().googleapi.client_secret;
const CONFIG_SHEET_ID = functions.config().googleapi.sheet_id;
// TODO: Use firebase functions:config:set to configure your watchedpaths object:
// watchedpaths.data_path = Firebase path for data to be synced to Google Sheet
const CONFIG_DATA_PATH = functions.config().watchedpaths.data_path;
// setup for authGoogleAPI
const SCOPES = ['https://www.googleapis.com/auth/spreadsheets'];
const functionsOauthClient = new OAuth2Client(CONFIG_CLIENT_ID, CONFIG_CLIENT_SECRET,
FUNCTIONS_REDIRECT);
// OAuth token cached locally.
let oauthTokens = null;
// visit the URL for this Function to request tokens
exports.authgoogleapi = functions.https.onRequest((req, res) => {
res.set('Cache-Control', 'private, max-age=0, s-maxage=0');
res.redirect(functionsOauthClient.generateAuthUrl({
access_type: 'offline',
scope: SCOPES,
prompt: 'consent',
}));
});
// setup for OauthCallback
const DB_TOKEN_PATH = '/api_tokens';
// after you grant access, you will be redirected to the URL for this Function
// this Function stores the tokens to your Firebase database
(Error in Line 64 index.js) exports.oauthcallback = functions.https.onRequest(async (req, res) => {
res.set('Cache-Control', 'private, max-age=0, s-maxage=0');
const code = req.query.code;
try {
const tokens = await functionsOauthClient.getToken(code);
// Now tokens contains an access_token and an optional refresh_token. Save them.
await admin.database().ref(DB_TOKEN_PATH).set(tokens);
return res.status(200).send('App successfully configured with new Credentials. '
+ 'You can now close this page.');
} catch (error) {
return res.status(400).send(error);
}
});
Error in console: C:\Users\user\src\functions-samples\google-sheet-sync\functions\index.js:64
exports.oauthcallback = functions.https.onRequest(async (req, res) => {
^SyntaxError: Unexpected token (
Steps to set up and reproduce
Followed guide in readme.me
node v6.12.3
npm v5.5.1
firebase v4.2.1

Sample data pasted or attached as JSON (not an image)
firebase.json
{
"functions": {
"source": "functions"
},
"hosting": {
"rewrites": [
{
"source": "/oauthcallback",
"function": "oauthcallback"
},
{
"source": "/authgoogleapi",
"function": "authgoogleapi"
},
{
"source": "/testsheetwrite",
"function": "testsheetwrite"
}
]
}
}

Security rules used
{
"rules": {
".read": true,
".write": true
}
}

Debug output
Errors in the console logs, none
Screenshots
Expected behavior
Should be able to deploy project

Actual behavior
Fails/crashes on firebase deploy/firebase deploy --only functions

You are probably on the wrong branch. The pasted code seems to originate from branch "Node-8". And async isn't supported in node v6, which is by default running in Firebase as of today.

The sample should deploy on a Node8 instance automatically since it is specified in the package.json file: https://github.com/firebase/functions-samples/blob/Node-8/google-sheet-sync/functions/package.json#L22-L24
@christianjkarlsson it simply looks like your issue is that you are running Node6 on your system. Please Switch to Node8.
If you prefer to stick to Node6 you can switch to the master branch, but please be aware that we're not going to maintain these samples anymore.


Link broken in docs

https://shipshapecode.github.io/ember-shepherd/#/docs/usage

Most of the usage documentation can be found in the API Reference for the Tour Service.

Link refers to https://shipshapecode.github.io/docs/api/services/tour which returns 404.

Fixed, thanks!


Fix flaky chainerx.abs test

Fix #6912.
Fixed to avoid non-differentiable inputs.

Jenkins, test this please.

Jenkins CI test (for commit 4dab280b529aceaa4810977873775011de40f76f, target branch master) failed with status FAILURE.

Jenkins, test this please.

Jenkins CI test (for commit 4dab280b529aceaa4810977873775011de40f76f, target branch master) failed with status FAILURE.

Jenkins, test this please.

LGTM!


Documentation site is down

https://state.software/docs/ gives 404

Fixed.  As v6 is currently in development, there are now two sets of documentation https://state.software/docs/v5/ and https://state.software/docs/v6/ - I've added a redirect to default to v5.

both sites seem to be down at the moment.

Hi, the doc's have moved domain to https://steelbreeze.net/state/docs/v5/ and https://steelbreeze.net/state/docs/v6/


[$500] Web - IOUs - location text does not change on selecting 'Use current location'

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.12-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation: @
Action Performed:

Open the app
Click on green plus and click request money -> distance
Open start/finish
Search any location and select the result
Again open same field used in step 3
Ensure that location action is disabled
Remove current location text and select 'Use current location', it will trigger error
Now enable location access and again select 'Use current location'
Observe now that on main distance page, it still displays older location instead of 'Your location', open the same field as step 3 and observe that inside it displays 'Your location' properly

Expected Result:
App should display 'Your location' on selecting 'Use current location' in any waypoint
Actual Result:
App displays older location value instead of 'Your location' on selecting 'Use current location' in any waypoint if location access is enabled after error is triggered
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/433e001f-afef-40eb-8575-f69fcfac454b

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0168cfb95cbebc1039
Upwork Job ID:<PHONE_NUMBER>238655488
Last Price Increase: 2023-12-27

Proposal
Please re-state the problem that we are trying to solve in this issue.
App displays older location value instead of 'Your location' on selecting 'Use current location' in any waypoint if location access is enabled after error is triggered
What is the root cause of that problem?
we don't pass the name field to the location here.
https://github.com/Expensify/App/blob/b950c1eae5535abd5e733a5f9eeecd1bd42b8464/src/components/AddressSearch/index.js#L338-L342
So that the name field will be undefined. Currently, when updating waypoints we are using MERGE method, and the old name value will be retained. It caused this bug
What changes do you think we should make in order to solve the problem?
In here
https://github.com/Expensify/App/blob/b950c1eae5535abd5e733a5f9eeecd1bd42b8464/src/libs/actions/Transaction.ts#L61
We can combine the old transaction and the new change, then use SET method instead of MERGE method as we did here
https://github.com/Expensify/App/issues/30290#issuecomment-1809233095
Note that: MERGE method caused many similar bugs so we usually use SET method when updating waypoints like here
https://github.com/Expensify/App/blob/b950c1eae5535abd5e733a5f9eeecd1bd42b8464/src/libs/actions/Transaction.ts#L162
What alternative solutions did you explore? (Optional)
If we still use MERGE method, I think we should have a general solution instead of fixing case by case (It is so easy to miss similar bugs elsewhere)
https://github.com/Expensify/App/blob/b950c1eae5535abd5e733a5f9eeecd1bd42b8464/src/libs/actions/Transaction.ts#L61
In here we can check if the name field is undefined we will set it to null or address field

Please re-state the problem that we are trying to solve in this issue.
Web - IOUs - location text does not change on selecting 'Use current location'
What is the root cause of that problem?
When we select use current location name field value show as undefined in  selectWaypoint
https://github.com/Expensify/App/blob/main/src/pages/iou/request/step/IOURequestStepWaypoint.js#L169
name: [values.name](http://values.name/),
What changes do you think we should make in order to solve the problem?
https://github.com/Expensify/App/blob/main/src/pages/iou/request/step/IOURequestStepWaypoint.js#L169
Implement more robust handling of undefined values for name in the Transaction.saveWaypoint method by providing a default value explicitly:
name: [values.name](http://values.name/) !== undefined ? [values.name](http://values.name/) : CONST.YOUR_LOCATION_TEXT,
This code explicitly checks for undefined values and assigns CONST.YOUR_LOCATION_TEXT as a fallback to ensure consistency.
Video:-
https://drive.google.com/file/d/1gl9HvRNJUpybpImBi6ey1z4u-ktt-tNd/view?usp=sharing

Proposal
Please re-state the problem that we are trying to solve in this issue.
Web - IOUs - location text does not change on selecting 'Use current location'
What is the root cause of that problem?
The 'Onyx.merge()' will not update the property if its value is undefined.
What changes do you think we should make in order to solve the problem?
In here
https://github.com/Expensify/App/blob/b950c1eae5535abd5e733a5f9eeecd1bd42b8464/src/libs/actions/Transaction.ts#L60
We should set the name of the current location to an empty string.

What alternative solutions did you explore? (Optional)
No
Result
https://github.com/Expensify/App/assets/497313/954ec7a5-150b-450a-8b01-68776162f055
https://github.com/Expensify/App/assets/497313/d7573a6b-e5f5-41fd-bf96-08eeb149192f

Hey @mananjadhav can you review the proposals please?

I’ll reproduce the issue and review the proposals by tomorrow.

I'll review the proposals.

I don't think we should be using Onyx.set. Adding null looks like a straight forward solution. Okay with @ZhenjaHorbach's proposal here.
We can work out in the PR places where saveWaypoint is called and accordingly decide the change in the saveWaypoint or the params.
🎀 👀 🎀 C+ reviewed.

Double checking the expected results

The expected result sounds good, and I guess the name and address should both be Your location in this case.

Thanks!
@ZhenjaHorbach can you raise a pr please?

Pr is in review

Adjusting labels to reflect the PR being in review, seems they didn't update automatically like they were supposed to

PR is on staging

This was deployed to production on January 9, updating title and labels to reflect 7 day hold

I couldn't pinpoint the specific PR that must've caused this.  I also don't think we need a regression test for this.
@stephanieelliott This is ready for payout, can you please post a payment summary?

Summarizing payment on this issue:

Contributor: @ZhenjaHorbach $500 PAID via Upwork
Contributor+: @mananjadhav $500 please request via Newdot

Upwork job is here: https://www.upwork.com/jobs/~1737876297360310272"

@stephanieelliott When should I expect payment?

@stephanieelliott When should I expect payment?

@kaushiktd Payment regarding?

Yes @mananjadhav

$500 payment approved to @mananjadhav based on this comment.

@JmillsExpensify any update on my payment?

@kaushiktd can you clarify what specifically you are expecting payment for? No payment is due on this issue as your proposal was not selected and you were not hired for this job. For more context into how and when Expensify issues payment please see contributing.md

It seems I made a mistake. Sorry!


Expansion

I want to add a Expansion,but i don't know how to do this.
So submit this issues.
I want to the [ ] to <input type="checkbox">.
and the  [x] to <input type="checkbox" checked="checked">.
Thanks for look that.

duplicate of #29

@cebe Thank you

you have to change the parsing of list elements: https://github.com/cebe/markdown/blob/master/block/ListTrait.php#L71


delete redundant files for pytorch pruner

Type of Change
delete redundant file
Description
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
None
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
None

delete useless scripts


feat(ibis): Support pyspark sql data source

(in progress)
Add support to pyspark sql data source, aims to solve issue #708

Close inactive PR over one month


Bump okhttp version to support Android 11

Summary
Android 11 support landed in OkHttp with version 3.14.7, bumping to the most necessary version.
Issue: https://github.com/facebook/react-native/pull/30104

Changelog

[Android] [Changed] - Bump OkHttp version to 3.14.7 to support Android 11
Test Plan

OkHTTP 3.13 requires Android 5 and above, but RN still supports 4.4. Please see https://cashapp.github.io/2019-02-05/okhttp-3-13-requires-android-5
Also it looks like the fix is back ported to 3.12 with https://github.com/square/okhttp/pull/5822.

I'm quoting 3.12.9 changelog from https://square.github.io/okhttp/changelog_3x/#version-3129

Fix: Don’t crash on Android 11 due to use of restricted methods. This prevents a crash with the exception, “Expected Android API level 21+ but was 29”.

Hi @dulmandakh, do you know what has to be done to fix the issue?

Interesting, if it is backported crashes shouldn't be occurring. The original issue mentioned API 30 maybe okhttp hasn't addressed that yet?

Okhttp was bumped just recently, so it only in the master and 0.63 contains buggy version. I requested to cherry pick it for 0.63.4.

Makes sense! Let's close this and link the PR to the original issue and close that one as well.

@safaiyeh so this can be closed now?

let's close the PR 😉


Sixth

Description
I've added the flutter_localizations support, along with creating and generating the local translation files of all the languages added yet. Through these classes added, one can choose relevant translations to add anywhere in the application.
Fixes #377
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@avinashkranjan please review this PR


zsh default shell

It would be neat if zsh was the default shell with easy-arch. What are your thoughts?

I personally use and like Zsh more than bash but the idea is to keep this script as generic as possible (beside some opinionated defaults like the entire BTRFS + LUKS setup). Bash works fine for the majority of people and if you like Zsh you probably know how to install it (feel free to fork this project, add zsh to the list of packages to install and drop a cheeky chsh -s $(which zsh) $(whoami) in the script 😄


Fix warnings

What's wrong?
Several warnings due to incorrect formatting
/Users/laysa.uchoa/Documents/devportal/docs/products/kafka/kafka-mirrormaker/howto/integrate-external-kafka-cluster.rst:7: WARNING: Title underline too short.

Define an external Apache Kafka® service integration endpoint via Aiven console
----------------------------------------------------------------------
/Users/laysa.uchoa/Documents/devportal/docs/products/opensearch/howto/import-opensearch-data-elasticsearch-dump-to-aiven.rst:2: WARNING: Title underline too short.

Copy data from OpenSearch to Aiven for OpenSearch® using ``elasticsearch-dump``
===================================================
/Users/laysa.uchoa/Documents/devportal/docs/products/opensearch/howto/import-opensearch-data-elasticsearch-dump-to-aws.rst:2: WARNING: Title underline too short.

Copy data from Aiven for OpenSearch® to AWS S3 using ``elasticsearch-dump``
===================================================
/Users/laysa.uchoa/Documents/devportal/docs/products/opensearch/howto/import-opensearch-data-elasticsearch-dump-to-aws.rst:13: WARNING: duplicate label copy-data-from-os-to-os, other instance in /Users/laysa.uchoa/Documents/devportal/docs/products/opensearch/howto/import-opensearch-data-elasticsearch-dump-to-aiven.rst

Related to https://github.com/aiven/devportal/pull/1439
In order to fix it, extend the underline to cover the full title

Fixed: https://github.com/aiven/devportal/pull/1452/files


Partitioned backfills with virtual end_date option in Meltano orchestration

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2769
Originally created by @aaronsteers on 2021-05-27 02:23:35

Note: this was created as a possible path forward for #2738. If we assume end_date already exists as a parameter in the tap, then much of this is redundant with the general path laid forward in #2738.

Meltano in theory could implement an emulated end_date option for incremental streams if we take on several assumptions:

The tap stream in question already supports start_date (but presumably not end_date).
The tap stream in question is a sorted stream (would not work for unsorted streams).
Meltano can isolate the tap stream from the rest of the tap's streams by means of standard Meltano selection logic.
Meltano can parse records in-flight and extract replication_key_value for a running stream.

The user would define a backfill by specifying the following input params:

extractor - should map to an extractor in meltano.yml
loader - should map to a loader in meltano.yml
stream_list - array of stream names, likely to exclude smaller dim tables and tables without replication keys
backfill_start_date - furthest back date to query
backfill_end_date - furthest back date to query
partition_period (day, week, month, or year)

Given all of the above constrains and input params:

Meltano breaks the work into n number of partitions based on backfill_start_date, backfill_end_date, and partition_period.

For V1, let's assume exactly 1 partition with a fixed upper and lower bound.

Meltano starts each stream in parallel.
Meltano short-circuits (force-stops) each stream once all of these are true:

a record is seen in-flight with replication_key_value > the end date for the partition
a state message has been received from the target after the above record was seen
the target has emitted the same state message, indicating a successful write

Other Considerations

At any time while the extract is running, records may (by way of being updated) migrate from their current date partition into the latest (n-0) partition. This will mandate a final run with final invocation which includes the batch execution window.
By running partitions in parallel, we cannot protect against duplicates, since records may move between partitions while the streams are in flight. A dedupe logic will be needed, probably in the dbt layer.
The latest stream (n-0) should not be executed until all other streams have completed. This is to ensure that for records which migrate into the latest stream bucket while the stream is happening, the latest version of that record is not going to be overridden by a prior version of the same.
Because this pattern does not exactly terminate the stream on strict partition boundaries, duplicates are to be expected and would need to be accounted for in the downstream process.

Phases
An MVC of this feature might be just the ability to provide a forced_end_date, after which meltano would kill the stream using the rules above. A user could apply this MVC feature towards parallelizing the work themselves using a similar logic until the full Meltano orchestration was possible.
Better and/or related solutions

A very similar orchestration could be implemented more cleanly if the tap supported end_date as a parameter.
#2727 ('Melturbo') could be used as the parallelization orchestrator
If we had support for stream aliasing (perhaps via #2299 or similar), we could land each partition into a differently-suffixed table, rather than loading all into the same table simultaneously.

View 1 previous comment from the original issue on GitLab

Still relevant


VisUI version changed to the latest stable release.

Sorry, had to spam another PR as the previous one doesn't reflect this commit.
@czyzby, if there is no CI for snapshots, I'm afraid I have to ask you to publish Maven artifacts once again, hope that's not a lot of a trouble.
Thanks!

It's OK, thanks for the update!

@czyzby hm, I cannot find the latest snapshot release, is it not published yet?
https://oss.sonatype.org/content/repositories/snapshots/com/github/czyzby/gdx-lml/

I'll clean, rebuild and reupload.

@czyzby guess what? 😃
The last uploaded snapshot jar seems to be broken. There is nothing inside but META-INF.
Check out the size of gdx-lml-<IP_ADDRESS>.10-20190816.082017-7.jar in here
https://oss.sonatype.org/content/repositories/snapshots/com/github/czyzby/gdx-lml/<IP_ADDRESS>.10-SNAPSHOT/

Sonatype was acting weird and throwing 503s, might have been related. Well, I'll try to reupload again.


Cover module/class name having _ and/or numbers

Hi! I found this issue in https://github.com/kachick/ruby-ulid/blob/2bf89942bdb7e57756f7ebc7d88e0a1037c952cd/sig/ulid.rbs#L38
I know, this change is not perfect for Ruby/rbs syntax, especially does not cover 日本語.
But containing _ and numbers are common use-case, so I think adding this might better 🙏
Before

After

Looks #10 aims upward compatible than this PR, Please let me close 🙇♂


Cherry-pick #5601 to stabilization

Overview
This cherry-picks @alexees' change from mrtk_dev to stabilization, to ensure this gets into GA.
Changes

Fixes: #5099

/azp run


update dependencies to fix several vulnerabilities

There are too many vulernabilities to mention and link each of them separately.
Note that the CI may fail with a message like:
><EMAIL_ADDRESS>lint /home/user/git-repos/foundry-release-base
> twolfson-style lint lib/ test/

fs.js:40
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:40:5
    at req_ (/home/dirk/git-repos/foundry-release-base/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/home/user/git-repos/foundry-release-base/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/home/user/git-repos/foundry-release-base/node_modules/graceful-fs/fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:101:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint: `twolfson-style lint lib/ test/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

This also happens to me on Node 14 before the patch, so it's not introduced by the patch. An answer on StackOverflow to a similar problem suggests that this happens with certain newer Node.js versions. However, such versions seem not to be tested on the current CI settings, so it may possibly pass without such an error. On the other hand, there may be different errors due to the tested Node.js versions being rather old.

These are all development dependencies. I appreciate the effort, but seeing as I'm tight on time these days and CI would need a patch, going to close opt to not land this currently =/

Sorry to hear that, but that's an understandable decision.


Correct spelling of 'mergeable' in dev checklist

Fix spelling of "Is it mergable?" in http://khmer.readthedocs.org/en/v1.3/dev/coding-guidelines-and-review.html, which is in doc/dev/coding-guidelines-and-review.txt.
running a spellchecker in general might be good :)

I am working on this issue.

Closed by #804


[Dev] Use "Gandiva" instead of "C++ - Gandiva" label

Describe the enhancement requested
We're using "C++" and "C++ - Gandiva" labels in our templates like https://github.com/apache/arrow/blob/main/.github/ISSUE_TEMPLATE/bug_report.yaml .
Do we need "C++ - " in "C++ - Gandiva"? Can we remove the "C++ - " part and use "C++" and "Gandiva" labels instead of "C++ - Gandiva" label?
Component(s)
Developer Tools

I don't mind personally.

Issue resolved by pull request 44722
https://github.com/apache/arrow/pull/44722


Add deferred udpates and postMessage fallback

Fixes #1399
This PR is an initial pass at making the workbox-broadcast-cache-update plugin work with cache updates on navigation requests. It also adds a basic fallback to postMessage()-ing all window clients in browsers that don't support the Broadcast Channel API.
Note, this PR includes some breaking changes to go along with some of our plans for v4, so I've tagged it accordingly. I'll update this PR with a complete list of breaking changes after the review, but for now the main points are:

A channel name is no longer required (it defaults to workbox, which will be the same default used by workbox-window).
Public BroadcastCacheUpdate and broadcastUpdate methods now take destructured params rather than position params (which made the most sense since channel name is now optional).

Rebased after changing the base branch from master to next (since there are breaking changes).


GH-274 Update jacksonVersion to 2.9.9

Update jacksonVersion to 2.9.9

Thank you, @jmax01; looking forward for more!

Thank you, @jmax01; looking forward for more!

Another soon.


Rumble/vibration not working.

Hello, and than you for this awesome program!
Unfortunately on my side the rumble function is not working for some reason.
I have a Playstation SCPH-110 controller, and connected with a cheap eBay Sony to USB converter (recognized as "Twin USB joystick").
Drivers are installed, and under the default windows 10 x64 built in program called "Game controllers/Properties/Vibration test" it's working properly.
ViGEm is installed, and recognized by xoutput. Under diagnostics force feedback motors count 4. And green mark say okay.
Any idea whats wrong?

I only tested force feedback with a pair of motors (small and big motors). You have a "Twin" joystick that means you have 2 pairs of motors. I think this may be the issue.
I will look into this, if I can emulate 4 motors somehow. If I cannot do that I will release a test version.

I agree on that you have only 2 motors as usual. However the driver states 4, as you can see in the diagnostics.
I cannot promise any ETA, but I will try to work on this.

Thanks, I'll be patient - using this controller for a decade now. :)

The force feedback debug logging is extended in the newer versions. Can you provide me a log file from the latest version?

I also have a Twin USB joystick. I have one of the ports on it disabled since I use various controllers through Steam, as well as your program. Does this logfile help?
XOutput.log


Add a Gitter chat badge to README.md

openaps/oref0 now has a Chat Room on Gitter
@jasoncalabrese has just created a chat room. You can visit it here: https://gitter.im/openaps/oref0.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Using https://gitter.im/nightscout/intend-to-bolus for now, maybe a dedicated room someday


app ui blurred,maybe electron or develop environment

macos 10.15.7
nxshell 1.6.2
My develop mac have install many dev software,such as vscode, nxshell, youdao note，firefox, etc. maybe they all use electron tech. now some of these UI are blurred almost simultaneously, like screenshot,

so this is the electron compatible conflict or some others?
or can restart electron, not restart pc. because restart nxshell ui blurred is still exist.
Thanks!

it still blue when restart macos pc? @tocky0

it still blue when restart macos pc? @tocky0

when restart macos pc, nxshell and other electron software are all recover.
But, what the reason?

Maybe electron issue...


Documentation on timeout options needs clarification

"timeout is the maximum time to execute an operation. It has Buffer type because timestamp in Hive has capacity 64. So for such value, you should use node-int64 npm module."
Right now the documentation just says that the timeout represents "time", but doesn't have any indication of the unit.
Is it the amount of time in milliseconds?
Seconds?
Minutes?
Seems like a pretty easy update to documentation to add in the unit (and potentially an example of setting the timeout).

I ran into this as well, i'm making the assumption that it should be like this?
const Int64 = require('node-int64');    await session.executeStatement(query, {runAsync: true, queryTimeout: new Int64('0x000120000')});
And hopefully that then means 2 minutes timeout?

+1 for improved types and docs on this, as well as accepting a raw number. I'd love to just say { queryTimeout: 300 } for a 5 minute timeout without having to introduce a new library 😬

Hi @xdumaine! Can you please share your code where you're trying to use a query timeout?

Definitely, I appreciate you looking.
  const query = await buildDatabricksQuery(input);

  const queryTimeout = options?.timeoutInSeconds || 1;
  const int64Timeout = new Int64(queryTimeout);

  console.log(
    'Running query with timeout',
    queryTimeout,
    int64Timeout.toString()
  ); // both evaluate to `1`

  const queryOperation = await input.databricksSession.executeStatement(query, {
    queryTimeout: int64Timeout,
  });

  const result = (await queryOperation.fetchAll({})) as any[];
  await queryOperation.close();

@xdumaine Can you please check one more thing for me. So can you please open a query history page, filter by your warehouse, and check the Duration column. It shows the actual query execution time, without various overheads (processing results by server and/or client, data exchange overhead, etc.) - that's the value to which query timeout is applied. await op.executeStatement() often takes more that that due to many reasons, and if you measure the execution time of await op.executeStatement() you most likely will not get the right value

This is what I see, maybe you can help me understand to which value the timeout is applied? I would expect it to apply to _running_ or _executing_ at least, but it would be ideal if I could also apply it to the scheduling time.
My use case is an API request which as a 5 minute timeout on the ELB, meaning I must respond within 5 minutes. If the databricks query can't complete (due to any reason) within, say 4 minutes, I want to cancel is and return an error.

Thank you! Yes, you're correct - if you set a 1s timeout, this particular query execution had to be interrupted. I remember that it was definitely working last time I touched this code. It may be some regression, I need to reach the Thrift backend team

Hi @xdumaine! Sorry for the delay, sometimes even simple things take longer that expected. Turns out, that this option is actually used, but only on Compute clusters. If you run query against SQL Warehouse, the option is ignored and some server configuration is used instead. We're still discussing this behavior with other Databricks developers, but I doubt that this behavior is going to be changed (at least, in the near future). If you need to have a query timeout with SQL Warehouse - you can try to work it around using timer and cancelling the operation. Sorry for the invonvenience.
P.S. PR to allow regular numbers for a queryTimeout option is coming very soon

Thanks @kravets-levko - I've moved on from this for now, but FWIW, I was not able to work around it using a timer and cancelling the operation, because the handle to cancel the operation isn't returned until after it completes:
/** This does not work */

  // start the query
  const queryOperation = await input.databricksSession.executeStatement(query);
  setTimeout(() => {
    // I need a handle on the query operation to cancel it
    // but I don't get that handle until `executeStatement` resolves
    queryOperation.cancel().catch(() => console.error.bind(console))
  }, 5000);
  // the cancel would work if `fetchAll` was the slow part, but it's not, the `executeStatement` is
  const result = (await queryOperation.fetchAll({})) as any[];

Basically - how can I cancel executeStatement if the operation handle isn't accessible until it resolves?

By default, executeStatement will ask Thrift server to wait for query execution and return a part of data - we call this feature DirectResults. It saves few requests to server and is especially handy with small result sets. But you can disable it by passing maxRows: null to executeStatement - in this case, server will just enqueue your query and return immediately

Okay, and probably the last update on this: this behavior is by design. To configure query timeout for SQL Warehouse, other mechanism is available: https://docs.databricks.com/en/sql/language-manual/parameters/statement_timeout.html


Randomly stops responding

After asking Alexa a few questions, "she" randomly stops responding to any wake words.
I have nothing in any of my logs, so I have no idea why it happens.
Could it be a refresh (token) issue? (It should last at least 3600 seconds.)

So nobody else have noticed this issue?

Nothing in the terminal logs, nor the npm start dev chromium logs?
It should say which state it is currently in. Post it here

I've noticed if I ask for something that responds with a non-voice answer it stops responding. i.e. playing music, or easter-egg with sound i.e. "beam me up scotty"

Yes that is a known issue
This module does not support streaming or two-way conversations yet

Is there something you can do about it? It's ok that the module doesn't support streaming or two-way conversations yet, but it's annoying if it gets stuck and Alexa doesn't answer anymore.

No longer stuck on busy state
Fixed, and it's due to a MagicMirror bug
Read more here: https://awesome-alexa.js.org/#/installation?id=modifying-magicmirror-electron


Reverted to ViewDidLoad, used ViewDidLayoutSubviews for Frame update

@jNery looks good feel free to merge. I'll roll out similar solution to other IOS samples thanks.

@macca400 : Thanks. I just tested the 3 samples specified in the issue. But the new issues logged 20 days ago might all be fixed after your changes.


Reveal component

I wrote an initial implementation of the Reveal component for a project I've been working on:
https://gist.github.com/crisu83/9f18311b4350de7a5a59b2192c5b09ee
Any comments?

I'd very much like to see Reveal added to this package. That's the one thing missing preventing us from using it.
With your implementation, is there anyway to dynamically change the inside of the Reveal?
I don't want to have to have dozens of modals on the page waiting to be opened.

Any updates on this? Wanting to update the documentation and I'm currently trying to figure out to get Reveal on react-foundation's develop branch working. If things are going to change drastically soon then I'd prefer to hold off on writing the docs.

@crisu83 any updates?

This has been added


add a little documentation for GIT cmdline flags

Should have had this in the oroginal PR.  Sorry.

No problem at all, and thanks again for the contribution.


Docs readability enhancement: Adding Previous and Next pages Footer

Adding previous and next pages as footers for docs reading would enhance greatly the documentation readability.

Hello!
If this repo is still up, ma I get this issue assigned to work on ?


MNT: Re-rendered with conda-smithy 2.4.5

This is needed as the LLVM stack is largely using conda-build 2 unfortunately. So this downgrades the feedstock's configuration by re-rendering with conda-smithy 2. Should enable the CIs for the feedstock as well. Will happily update once the LLVM stack has been migrated to conda-smithy 3 and conda-build 3. For now this stopgap is needed.

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.


Mark Block as unchecked

I have a section of footnotes that looks like the following
[^1]: https://www.microsoft.com/
[^2]: https://dev.to/noseratio

It would be helpful if I could tell Spelling to skip this entire block. I don't want to whitelist the improper case of Microsoft. Please correct me if I'm wrong, but I don't think I can use a custom word filter to filter out URLs completely because I'm only given the word, not the rest of the surrounding context.

I don't use footnotes that much, so I'm not familiar with how they work. They can include any block of text, right, not just a link? Is the URL being split up by the tokenizer?
The syntax you're using looks different from what I see on https://docutils.sourceforge.io/docs/user/rst/quickref.html#footnotes and https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#footnotes. Is the ^ significant in how the markup is interpreted?

The syntax you're using looks different from what I see on https://docutils.sourceforge.io/docs/user/rst/quickref.html#footnotes and https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#footnotes. Is the ^ significant in how the markup is interpreted?

I should've mentioned that we're using markdown for our docs. I'm going from this - https://www.markdownguide.org/extended-syntax/#footnotes

Oh, wow, I have no idea how Sphinx deals with markdown.
Is your project public, so I could experiment to see what sort of nodes those footnotes are when they appear in the parse tree?

Unfortunately, the project isn't public. I would have to set up something
similar to demonstrate the issue.
On Fri, Jun 24, 2022, 4:22 PM Doug Hellmann @.***>
wrote:

Oh, wow, I have no idea how Sphinx deals with markdown.
Is your project public, so I could experiment to see what sort of nodes
those footnotes are when they appear in the parse tree?
—
Reply to this email directly, view it on GitHub
https://github.com/sphinx-contrib/spelling/issues/183#issuecomment-1165908456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHM5EVLLVZCFQY6TMA3N5TVQYKKFANCNFSM5ZVUTYQA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Providing a sample re-producer would help me determine if we can work around the problem.

I created a proof-of-concept that demonstrates the behavior at https://github.com/dshookowsky/sphinx-test
You'll have to install the myst-parser extension for markdown, but the example shows the same behavior in restructured text.

I added some logging to the builder to see what sorts of nodes are involved. It looks like a bare URL is treated as a regular text node.
[app] emitting event: 'doctree-resolved'(<document: <section "markdown example"...>>, 'example/markdown')
checking source/example/markdown.md:0:<#text: 'Markdown example'>
checking source/example/markdown.md:0:<#text: 'this is very ovbiously mispeled'>
checking source/example/markdown.md:0:<#text: 'with a footnote'>
checking source/example/markdown.md:0:<#text: 'https://github.com/microsoft/microsoft-ui-xaml'>
Writing /Users/dhellmann/Devel/sphinxcontrib-spelling/sphinx-markdown-test/build/example/markdown.spelling

If I change the markdown content to this:
# Markdown example

* this is very ovbiously mispeled
* with a footnote[^1]

[^1]: [https://github.com/microsoft/microsoft-ui-xaml](https://github.com/microsoft/microsoft-ui-xaml)

then the URL is treated as a different type of node, and ignored
 [app] emitting event: 'doctree-resolved'(<document: <section "markdown example"...>>, 'example/markdown')
checking source/example/markdown.md:0:<#text: 'Markdown example'>
checking source/example/markdown.md:0:<#text: 'this is very ovbiously mispeled'>
checking source/example/markdown.md:0:<#text: 'with a footnote'>
Writing /Users/dhellmann/Devel/sphinxcontrib-spelling/sphinx-markdown-test/build/example/markdown.spelling

That's not necessarily ideal from your perspective, since the bare URL is normally valid Markdown syntax for getting a link and the usability of the bare link is a lot nicer. I notice, though, that the HTML output with that format does not make the URL a link where using the []() syntax does. So maybe you want to be using that syntax anyway?
The spell checker is relying on the underlying parser in myst-parser and the tokenizer in PyEnchant, though, so there's not a lot that can be done at this level if the markdown parser doesn't treat the bare URL as a link node.

I added a little more detail to verify, and the #text node is a docutils.nodes.Text instance.

It looks like MyST-parser uses markdown-it which implements the CommonMark style of markdown text. I don't see anything in the CommonMark link syntax docs that covers bare URLs, so it's possible those are not expected to be treated as links.
Another way to cause the URL to be skipped would be to treat it as inline literal text, and wrap it with double back-quotes
``https://github.com/microsoft/microsoft-ui-xaml``

I think that escaping my text or authoring pages in rst instead of markdown
are my best options at this point. Thanks for looking into it.
On Sat, Jun 25, 2022, 2:33 PM Doug Hellmann @.***>
wrote:

It looks like MyST-parser https://github.com/executablebooks/MyST-Parser
uses markdown-it https://markdown-it-py.readthedocs.io/en/latest/ which
implements the CommonMark https://spec.commonmark.org/0.30/ style of
markdown text. I don't see anything in the CommonMark link syntax docs
https://spec.commonmark.org/0.30/#links that covers bare URLs, so it's
possible those are not expected to be treated as links.
Another way to cause the URL to be skipped would be to treat it as inline
literal text, and wrap it with double back-quotes
https://github.com/microsoft/microsoft-ui-xaml https://github.com/microsoft/microsoft-ui-xaml
—
Reply to this email directly, view it on GitHub
https://github.com/sphinx-contrib/spelling/issues/183#issuecomment-1166340369,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHM5ERRZPWSZIJJGXBK7KTVQ5GGVANCNFSM5ZVUTYQA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sure thing. I'll go ahead and close this ticket, then.
Good luck with your project!


Automated Package Upgrade

:tada: This PR is included in version 2.2.209 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feat/project extent

This patch fixes issue  #48.
@zguo - please, review.

Canceled. Waiting for a more generic solution.


Release 9.1.0 RC

Stellar Core 9.1.0 RC (RC1?) has been released: https://github.com/stellar/stellar-core/releases/tag/v9.1.0.

This has been done a long time ago https://github.com/satoshipay/docker-stellar-core/releases/tag/9.1.0. :D


Can't find a property sequence

Hi there.
Not sure if it's bug or I'm doing something wrong, but:

I got this test project, with ellipse whose I color want to change https://www.screencast.com/t/j3FlEfYC.
This is a part of JSON assets array sent to nexrender (not sure value is in correct format, but execution haven't come to it yet anyway):

    {
      "type": "data",
      "layerName": "Shape Layer 2",
      "composition": "ANIMATION_COMP",
      "property": "Contents.Ellipse 1.Fill 1.Color",
      "value": "#ff0000"
    }

This is a part of nexrender custom script:

(function() {
    nexrender.selectLayersByName('ANIMATION_COMP', 'Shape Layer 2', function(layer) {

        var parts = ["Contents","Ellipse 1","Fill 1","Color"];
        var value = { "value": '#ff0000' }

        nexrender.changeValueForKeypath(layer, parts, value);

        return true;
    });
})();

And this is the error I get while rendering:
Error: nexrender: Can't find a property sequence Fill 1.Color for key: Fill 1

Can you give me a hint on what I'm doing wrong?
Thanks.
"@nexrender/worker": "^1.8.4" *

My fault. Tried to modify wrong property chain.

Glad to hear the issue got resolved :)

How did you end up solving this? I am facing the same issue.

How did you end up solving this? I am facing the same issue.
Been long since I wrote it. But as I remember - the problem was - I tried to modify unmodifieable (like calculated) property. And just should'v used other "path" to change the color.

I am facing the same issue.

Been long since I wrote it. But as I remember - the problem was - I tried to modify unmodifieable (like calculated) property. And just should'v used other "path" to change the color.

How can I know the path?

My fault. Tried to modify wrong property chain.

Hey,


License to use

Hi, are you planning on adding a license to share this repo? :)

Just did it 👍

@guichristmann amazing mate! Appreciate it


bind() not picking up changes even when onnew does

I have a pattern like this:
const myStoreFactory = ()=> {
   const foo = state(false)
}

const myStore = myStoreFactory()

const myComponent = ()=>{
   const { foo } = myStore
   foo.onnew(console.log) // This works
   return bind(foo, foo=>{
      return div(foo ? `foo` : `no foo`)
   })
}

const toggle = ()=>{
   foo.val = !foo.val
   setTimeout(toggle, 1000)
}

In some cases, and I can't figure out exactly why, bind() is not picking up the changes even when onnew will fire. Any ideas?

For DOM nodes that are bound to states, they need to connect to the document object (isConnected property needs to be true) before state changes are made.
You can reply to this thread if you have more questions, or close this bug if everything is good.

Thank you.

Please complete the construction of the DOM tree and connect the newly constructed DOM tree to the document object before making any state changes.

Could you explain more? In my case, the issue was async execution where the component was being rendered with a correct initial state, but the state update happening in the then() was not working for bind even though onnew was responding to it. It seems that my DOM tree was constructed and connected, but modifying the state in an async callback failed.

Could you show me the code that is not working?

This works every time, is there any problem with doing this? It seems to eliminate the need to reason through race conditions.
const wrapState = (originalStateVar: State<any>) => {
  const wrapped = state(originalStateVar.val)
  originalStateVar.onnew((v) => {
    wrapped.val = v
  })
  return wrapped
}

return div(bind(wrapState(myStateVar)...))

The problem is GC, every time wrapState`` is called, it creates an event listener for originalStateVarthat will never be cleaned up. Thus there will be problems ifwrapState` is called many times.

I'll see if I can distill it down to a concise example.
I did notice that wrapping the renders in setTimeout also fixed the issue. Could this be a clue? Is there something about waiting until the next tick for the state to settle?
In the mean time, can you please explain more about this statement:

Please complete the construction of the DOM tree and connect the newly constructed DOM tree to the document object before making any state changes.

How is it possible to construct and connect the DOM tree to the document when the tree depends upon state variables? That seems to be a contradiction, can you say more please?

Ok I figured out the issue. I was indeed passing the result of a render function and then connecting it to the document tree later. The debug version of Van didn't complain about this, I wonder if there is a more robust check?
Basically, any reference to a state binding where isConnected===false should complain. I see the debug check, but it wasn't complaining.

This has been a very interesting issue, I'm also finding out that the order of state changes can produce bind warnings, where a bind update scheduled with setTimeout will attempt an operation in the next tick on a component that was unmounted from the document in the previous tick.
This little helper comes in handy:
export const nextTick = () => new Promise((resolve) => setTimeout(resolve))

That way, I can await nextTick() to make sure components are fully unmounted and GC'd before making changes to state variables that might cause that setTimeout state update to be scheduled.

Basically, the key is, before doing:
s.val = ...

make sure all DOM nodes depend on the state s are connected to the document tree.

Another rule you can follow is: whenever you bind a DOM node to states, always connect the DOM node to document within the same synchronous execution block (no await in between).

This can be closed now. It took some learning, but now I understand how to architect things properly for Van.


Two sentences regarding the denial of your pull request.

Added two sentences so people know that they can contribute at any time again, even if their pull request got denied.

Yes, we always look forward to future contributions.
Nice that you added this message in a closed PR.


[New Feature] Automated theme renaming

Opening a new issue for this for organizational purposes. Discussion started in #1223.
We're looking to add a gulp task that does the following:

Replaces all instances of FoundationPress with a custom name, including:

function names
comments
text domain
zip name in package task

Draws from variables in config.yml to set the custom name and paths needed to look for changes
Uses a plugin like gulp-replace to accomplish this

Let me know if I forgot anything and I'll add to the list. Shouldn't be too difficult to accomplish if you are familiar with gulp tasks and FoundationPress.

file rename
class-foundationpress-mobile-walker.php
to
class-theme-name-mobile-walker.php

I'm updating an old FoundationPress based theme and need to keep both versions for now. Thus, I want to have a different name for the latest version I'm working on. Can I please have a full list of files I need to change to have a secure environment to work in? Thank you.


remove Travis CI configuration

travis-ci.org is no more and AFAIK we have not migrated any of these projects to the paid travis-ci.com. Deleting this file since it seems unused any longer and it has an encrypted secret containing my Maven Central credentials / GPG key.
https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/

I deleted the travis-ci.org webhook from this repo too


awaitAsyncOperation with IVectorView result

I'm trying to get BLE notifications working, and it involves using the following generated code:
(from: https://learn.microsoft.com/en-us/uwp/api/windows.devices.bluetooth.genericattributeprofile.gattlocalcharacteristic?view=winrt-22621)
func (impl *GattLocalCharacteristic) NotifyValueAsync(value *streams.IBuffer) (*foundation.IAsyncOperation, error) {
	itf := impl.MustQueryInterface(ole.NewGUID(GUIDiGattLocalCharacteristic))
	defer itf.Release()
	v := (*iGattLocalCharacteristic)(unsafe.Pointer(itf))
	return v.NotifyValueAsync(value)
}

I'm not able to retrieve the result of this from calling this:
func awaitAsyncOperation(asyncOperation *foundation.IAsyncOperation, genericParamSignature string) error {
	var status foundation.AsyncStatus

	// We need to obtain the GUID of the AsyncOperationCompletedHandler, but its a generic delegate
	// so we also need the generic parameter type's signature:
	// AsyncOperationCompletedHandler<genericParamSignature>
	iid := winrt.ParameterizedInstanceGUID(foundation.GUIDAsyncOperationCompletedHandler, genericParamSignature)

	// Wait until the async operation completes.
	waitChan := make(chan struct{})
	handler := foundation.NewAsyncOperationCompletedHandler(ole.NewGUID(iid), func(instance *foundation.AsyncOperationCompletedHandler, asyncInfo *foundation.IAsyncOperation, asyncStatus foundation.AsyncStatus) {
		status = asyncStatus
		close(waitChan)
	})
	defer handler.Release()

	asyncOperation.SetCompleted(handler)

	// Wait until async operation has stopped, and finish.
	<-waitChan

	if status != foundation.AsyncStatusCompleted {
		return fmt.Errorf("async operation failed with status %d", status)
	}
	return nil
}

(from https://github.com/tinygo-org/bluetooth/blob/release/adapter_windows.go)
And that function works fine for other async operations. I'm assuming its because none of them are a generic type like the IVectorView<T> that the NotifyValueAsync function returns.
I've tried the IVector / IVectorView signatures both but they dont work. I'm still currently looking into winrt's weird guid type system but thought I'd post an issue at the same time.
I'm assuming I simply need a GUID for a IVector<GattClientNotificationResult>, but have no clue how to make it.

fixed this by passing another pinterface to the awaitAsyncOperation function:
signature := fmt.Sprintf("pinterface({%s};%s)", collections.GUIDIVectorView, genericattributeprofile.SignatureGattClientNotificationResult)

awaitAsyncOperation(op, signature)


Use tests structure

Coverage decreased (-1.5%) to 92.424% when pulling 6a33f26baf2bbb1b3a3fd3ca9d85c39d2e606ae6 on test into 32efd2601475a782d22f6b5e273b065051539529 on master.

Coverage remained the same at 93.939% when pulling c4d67a558addec875aa0919898d660b857f10ad9 on test into 32efd2601475a782d22f6b5e273b065051539529 on master.


Higher Order Extensions methods

A list of higher order functions that should be added to SqlKata.
These features will be added as an extension project

[ ] SelectCase, WhereCase, HavingCase, and GroupByCase support
[ ] WithDateRange(DateTime from, DateTime to, string alias = "DateRange")
[ ] WhereNullOrEmpty(col)
[ ] WhereNullOrValue(col, 5) --> WHERE ([col] IS NULL OR [col] = 5)
[ ] WithJson(string alias, string[] cols, string json), Read json array as CTE
[ ] WithData(string alias, string cols, List<List<object>> data)

Please add your request in the comment section.

Hi @ahmad-moussawi
The Case support would be of great assistance.  Do you have a timeline on when this will be completed?
PS. Loving SQLKata
Regards

Is there an update here with the Case statements?


#2094-rework-actions-B

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #2094
[x] second attempt at reverted https://github.com/kodadot/nft-gallery/pull/2105

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[x] I've tested PR on mobile and everything seems works
[ ] I found edge cases

Had issue bounty label?

[x] Fill up your KSM address: already paid, thank you

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.
A) -> bought NFT view

B) -> listed NFT view

C -> unlisted NFT view

@yangwao you've mentioned in #2094

you accidentally removed actions for users for their NFTs apparently?

I'm not sure what did you mean by this, could you elaborate? I've attached 3 views I've tested. I've removed the money-cursor in case the NFT isn't listed.

@yangwao you've mentioned in #2094

you accidentally removed actions for users for their NFTs apparently?

I'm not sure what did you mean by this, could you elaborate? I've attached 3 views I've tested. I've removed the money-cursor in case the NFT isn't listed.

Actions when you are owner of NFT wasn't available in prev PR :)


update zlib to version 1.2.10

zlib is updated to 1.2.10 at January 2, 2017, and no old version
package files are maintained at http://zlib.net/

Thanks!


Java 8 Refactoring

Breaking apart the code into pieces that are much easier to test and maintain.
Based on the code in GH-9, so the commit history will become cleaner once that branch is on master.

@sagarsane @jbornemann @jazeren1 : This should be "essentially" done now. Used this as an opportunity to do a number of things, including:

Added a lot of static analysis (e.g., Checkstyle, PMD, Checker Framework)
Using AsciiDoctor and its visualization module to embed PlantUML
Increasing the amount/quality of the documentation a lot
Provide clear extension points for different formats of environment files, receiving status events, etc.
Much better/clearer errors in cases where something is wrong

The previous code this was based off of worked well-enough -- IF you were already intimately familiar with the formats of the files, etc.

Better testability

The PR is pretty big, though much of it is essentially noise: static analysis configuration files, build files changes, equals()/hashCode()/toString() (sure wish Java had the equivalent to Scala's "case classes"), lots of docs, etc.
To get a feel for the documentation (and thus have a better feel for reviewing the code changes), some good places to start are:

https://twcable.github.io/grabbit-cli/docs/javadoc/
https://twcable.github.io/grabbit-cli/docs/javadoc/com/twcable/grabbit/tools/cli/GrabbitCli.html
https://twcable.github.io/grabbit-cli/docs/javadoc/com/twcable/grabbit/tools/monitor/PollingJobMonitor.html

cc: @cculb @masroormohammed

To test the binary, do ./gradlew assemble and the executable binary will be in build/libs without an extension. You can run it just like the old version as a straight executable.


Add support for the BSD platforms

This PR adds the ability to compile and run Ollama on various BSD platforms, specifically DragonFly, FreeBSD, NetBSD and OpenBSD. A couple notes:

It includes support for Vulkan to offload work to the GPU.
It's only been tested on OpenBSD, but hopefully interested parties in this community can test the other platforms.
ollama run is broken on OpenBSD. The readline package uses syscall which OpenBSD has removed from libc and the kernel. Instead, the readline package should be updated to use golang.org/x/sys/unix, similar to how ergochat/readline does it. I didn't want to include that work in this PR.
The tweak in gen_common.sh is to remove a bash'ism so that the file can be sourced from ksh.

On OpenBSD I needed to add these packages:
pkg_add cmake go vulkan-headers
The other platforms will probably have similarly named packages to install.

Just tested the PR in a jail on a FreeBSD server. Packages to install:
pkg install go122 cmake vulkan-headers vulkan-loader
Then ollama can be built successfully on this platform, including vulkan support. Serve, pull and run all work. Thanks for this PR! I intend to test it on a NetBSD machine, too, as time permits.

So trying to build on either NetBSD or DragonFly has not been successful for me.
On DragonFly BSD (after installing the same dependencies as on FreeBSD) the build process failed early on with:
/home/kraileth/git/ollama/llm/llama.cpp/llama.cpp:1539:34: error: 'RLIMIT_MEMLOCK' was not declared in this scope
         if (suggest && getrlimit(RLIMIT_MEMLOCK, &lock_limit)) {
                                  ^~~~~~~~~~~~~~
/home/kraileth/git/ollama/llm/llama.cpp/llama.cpp:1539:34: note: suggested alternative: 'RLIMIT_STACK'
         if (suggest && getrlimit(RLIMIT_MEMLOCK, &lock_limit)) {
                                  ^~~~~~~~~~~~~~
                                  RLIMIT_STACK

So far the llama-cpp port in the FreeBSD ports collection has not made it over to DPorts. It looks likely that this platform is simply not supported by llama.cpp, yet. So here we have a real blocker.
On NetBSD things looks better. The dependencies can be installed like this:
# pkgin install go122 cmake vulkan-headers (if pkgin is configured on the system)
The first step completes with the following warning:
-- Could NOT find Vulkan (missing: Vulkan_LIBRARY) (found version "1.3.275")
CMake Warning at CMakeLists.txt:531 (message):
  Vulkan not found

While there is a vulkan-headers package available it looks like there is no actual vulkan support on NetBSD and thus it is missing the library.
So despite not resulting in a working ollama on all BSD platforms this PR enables building and using it on FreeBSD (I've played with it excessively for a few days now and it works well). It also enables building it on OpenBSD as well as using it to some degree. For the other BSDs it looks like more work will be required.
I would love to see this PR merged: For FreeBSD as it would allow creating a port and packaging ollama. And for the others as a good first step.

This branch has conflicts that must be resolved
Only those with write access to this repository can merge pull requests.

@prep

This is fantastic.

This PR adds the ability to compile and run Ollama on various BSD platforms, specifically DragonFly, FreeBSD, NetBSD and OpenBSD. A couple notes:
1. It includes support for Vulkan to offload work to the GPU.

2. It's only been tested on OpenBSD, but hopefully interested parties in this community can test the other platforms.

3. `ollama run` is broken on OpenBSD. The [readline](readline) package uses `syscall` which OpenBSD [has removed from libc and the kernel](https://marc.info/?l=openbsd-tech&m=169841790407370&w=2). Instead, the readline package should be updated to use `golang.org/x/sys/unix`, similar to how [ergochat/readline](https://github.com/ergochat/readline) does it. I didn't want to include that work in this PR.

4. The tweak in `gen_common.sh` is to remove a bash'ism so that the file can be sourced from `ksh`.

On OpenBSD I needed to add these packages:
pkg_add cmake go vulkan-headers
The other platforms will probably have similarly named packages to install.

I'm trying to build on OpenBSD but getting this message after running the build script:
/usr/local/go/pkg/tool/openbsd_amd64/link: running cc failed: exit status 1
ld: error: unable to find library -lvulkan
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Anyone knows how the Ollama project prioritizes their work and what, if anything, we can do as a community to help get this PR merged?


Kudos

Kudos are a way to reward ourselves users for contributing to the fansub. It's just a number (like the exp in RPGs), but it might be interesting.
For example, assuming the command prefix is !, this should give kudos to the user @Someone
!kudos @Someone

The amount of kudos for the current user could be retrieved by mentioning the bot (@Lolicon) like this:
@Lolicon kudos

This has been implemented in go-lolicon.


Integrate new networks figure into manuscript

This PR integrates the revised networks figure into the manuscript via a PDF export of complete_networks.svg.

Hi Chris, I noticed the new networks figure hadn't yet been integrated into the manuscript, this PR is just for doing that, please go ahead and merge if this doesn't clash with anything you're already working on.


hash is present in the URL passed to load

Describe the bug
In working on #4773, @benmccann stated a couple of behaviors:
(For the duration of this post, fragment === hash.)

prefetch should not rerun for identical routes with different hashes (eg. /prefetch and /prefetch#some-hash).
People should not be using the URL hash property in load.

I would tend to agree that either both or neither of these statements should be true; if 1 then 2 OR if not 1 then not 2. The promise of prefetch is that load will be run -- if the hash is meant to be part of the URL supplied to load, then load should rerun when the hash changes. If the hash should not be part of the URL supplied to load, load should not rerun when the hash changes.
If 1 is correct, this branch will take care of 2. (It was very easy to change and test.)
However, I'm having trouble with the justification of 1 and 2. Looking at the URL spec, I can't find anywhere that says "the content of the document should not change" based on the fragment. The HTML spec also doesn't seem to require that the content of the page remain static regardless of the fragment. (Please note, I'm not an expert in the nitty gritty of the URL or HTML specs, so please correct me if I'm wrong and I'll edit this part to include a correction.) The URL spec defines the fragment as "[a] string that can be used for further processing on the resource the URL’s other components identify." The phrase "can be used for further processing on the resource" in the context of a web document would say to me "...can be used for further processing by JavaScript...", which would suggest we would want to enable users to have access to it in load.
The very existence of things like ReactRouter's HashRouter seem to go against the idea that the document's content should not change based on the hash.
I'm opening this issue as a place to discuss further. If we commit to both 1 and 2, this will be fixed by opening a pull request against the previously-linked branch. If we commit to not 1 and not 2, this will be fixed by leaving 2 alone (exposing the hash to load is the current behavior), and a small modification to #4477 to fix 1. I'm most concerned with SvelteKit continuing to align with expected spec behavior (and the expectations of its users)!
Reproduction
N/A.
Logs
N/A.

System Info
N/A.

Severity
annoyance
Additional Information
No response

The # portion of URLs is not sent to the server by the browser, and so cannot be used as part of determining what's rendered during SSR for that page. When load is run on the browser, hash is available, because we are using the native location object to construct the URL. I would probably tend to say that we should not artificially strip certain data out of the location when calling the load function, but if that necessarily means that people will be confused during SSR, that might force our hand.
SvelteKit also needs to decide whether it sees itself as SSR-first (which is likely something it already sees itself as), which would also answer the question of whether hash-only navigations should be considered. The HTML5 history API has existed for a long time, and - even for SPAs - SvelteKit would likely encourage you to use URLs with different pathnames to refer to different pages. If you want to have a single pathname but different hash values to refer to different pages, you can use a Svelte-only solution with no SvelteKit in sight.

I would probably tend to say that we should not artificially strip certain data out of the location when calling the load function, but if that necessarily means that people will be confused during SSR, that might force our hand.

I would agree that we shouldn't artificially strip data as a general principle. I could see this potentially being confusing during SSR, but I don't think it should be, at least, not to any experienced web developer. Like you said, the fragment/hash portion of the URL is not sent to the server -- this is well-known behavior. Obviously, any references to hash in load would need to be wrapped in if (browser) (or handle the empty hash some other way).

If you want to have a single pathname but different hash values to refer to different pages, you can use a Svelte-only solution with no SvelteKit in sight.

I don't think this is the only use case, though. It doubtless is the majority use case, but say I have a regularly-updated page with lots of headings:

I'm an adventurer

About me

My legs are swole

Then, later, as we all know is inevitable, you take an arrow to the knee and need to retract my-strong-legs with my-terrible-injury. The SvelteKit-y way to do that, IMO, would be to use load:

Granted, there are other ways to do this, but there are other ways to do most things you can do in load.
I could also see removing the hash on the client negatively impacting our friends who run in SPA mode or use adapter-static, potentially?

actually it's good thing it's like this... I even use that hash often... but if you don't need it, it's easy to extract (resp remove it) from URL, But otherway, it would be problem...

The more I think about this, the more I side with Ben's original comment. While I think the URL and HTTP specs leave a lot of room for interpretation as to what the hash can/should be used for (the URL spec practically begs for JavaScript to be able to use it "for further processing"), I feel more and more strongly it should be kept out of load, even artificially, though it should be correctly supplied in the page store on navigation after prefetch has run.
I suppose my final vote would be to merge #4773 in order to fix the page store behavior and prevent prefetch from running multiple times for identical routes with different hashes, then opening a pull request against  https://github.com/tcc-sejohnson/kit/tree/sejohnson-remove-hash-from-load-url to remove the hash from the URL load receives. I'll wait on more feedback from the maintainers before opening that second PR.

There's another consideration here: the behaviour when the user clicks a link with a hash fragment.
Right now, SvelteKit's router bails out when you click  — it updates the scroll position history and updates the page store, but that's all. It doesn't re-run load functions.
So in the case where someone is using url.hash in load for some reason...
return {
  props: {
    hash: url.hash
  }
}

...the page will be incorrect. There are two options:

make url.hash inaccessible in load
re-run load when clicking hash links

Anything else (including the status quo) is broken IMHO.
Re-running load feels too costly, which makes me feel like 1 is a better option, particularly given the other arguments (prefetch behaviour and server/client consistency). We could rerun load if and only if url.hash was accessed, but we can't detect someone accessing the hash via url.href (or url.toString()). (Maybe we treat accessing url.href the same as accessing url.hash for this purpose?)
At the same time, people will get annoyed if url.hash is artifically inaccessible in load. All of which is a longwinded way of saying that I'm not really sure what we should do here.

for me it doesn't make sense to re-run load when hash change / or is accessed, as it's part of URL that shoudln't have effect on content of page, it should have effect only on scroll position.

One way to think about it: if people are referencing url.hash in their load functions today, their apps are already broken (since load doesn't re-run when the hash changes). So it'd actually be fine for us to remove url.hash from load.
If we later decide that we do need to make url.hash accessible in load, I would consider that a non-breaking change. So the semver-galaxy-brain thing to do is to make url.hash inaccessible in load (and fix the sticky page store issue in #4768), which coincidentally is by far the simplest thing to do, implementation-wise.

Somehow even the simplest load function leads to Error: url.hash is inaccessible from load. Consider accessing hash from the page store within the script tag of your component.:
export const load: Load = (e) => {
  console.log(e)
}

Withouts this, I can't even see what actual data I'm receiving.
I mean, ofc there are docs etc, but cmon, svelte-kit is still experimental, things change and break often, googled answers lead to non-existing page docs, etc. I feel like it's easier for me to just print the actual data and see what happens, but somehow this error just completely stops my entire app. Couldn't it be a simple warning or something?


[FEATURE] add frameguard on dev

since soya-next-scripts dev use different code with soya-next-server I need to add frameguard so the behavior on dev and prod would be the same

I don't think we need this in dev, no one gonna attempt clickjacking in your local machine, right? Just like how we enable gzip in production only.


!chore: write upgrade handler for new minimum commission rate

closes #151
reopen #152

Description:

Change staking params' min commission rate to 5%
Update all validators commission rate

Hi @jiujiteiro, I've added the changelog, updated your review, and added logic to not change the validator's commission if it is more than 5%. Please let me know if we need anything else.


udc_pedict.py is thowing error

INPUT_CONTEXT = "sir  iam   manohar  please   respond eos "
POTENTIAL_RESPONSES = ["please give me one or two minutes to check this for you eos ","hi eos"," please give eos ","i have checked and see that you have contacted earlier for the same issue eos ","the replacement policy is applicable from the date of product delivered and this has crossed the sellerreplacementperiod eos hope you understand eos is there anything else that i can help you with today eos ","due to unforeseen reason your return request has been cancelled eos not to worry i have created a new return request for you  eos  is there anything else that i can help you with today  eos ","i request you to confirm when you get that reward points eos ","sorry to keep you waiting its taking a little while to get this information eos thank you for your kind patience  eos ","thank you for sharing the address eos please wait for a minute or two while i check the details  eos "]
When I run udc_predict.py it gives me following error:
Context: sir  iam   manohar  please   respond eos
Traceback (most recent call last):
File "udc_predict.py", line 58, in
print("{}: {:g}".format(r, prob[0,0]))
TypeError: 'generator' object has no attribute 'getitem'
Please let me know if any other information is needed

prob = list(prob) before print("{}: {:g}".format(r, prob[0,0])) line.

In case anyone still has this issue, replacing line 58 with
print("{}: {:g}".format(r, next(prob)[0]))
solved it for me.


Change kube-vip LB IP pool logic

Current setup

We specify a globalippool in the cluster values: here
We create an ipadressclaim using this pool which blocks a single ipaddress: here
We collect the IP from the cluster and edit the CPI helmrelease to create a one-IP pool with cidrGlobal:: here

I don't get why we do that. It means we have a 10-IPs IPAM pool in the MC but the WC as a 1-IP pool 🤷. So the first load balancer will work fine (most often nginx) while subsequent LBs will be stuck on pending.
Proposition
Collect the actual IP pool from the LB IP pool in the MC.
> kg globalinclusterippools.ipam.cluster.x-k8s.io cassino-svc-lb-ips -ojsonpath='{.spec.addresses[0]}'
<IP_ADDRESS>-<IP_ADDRESS>

And patch the Helmrelease with a range-global instead.
EDIT: Actually now I remember. We use an IPaddressclaim to block the IP on the MC side. If we set a range in the WC it could (potentially) be set in multiple WCs.
Ideally we would need something like ipaddressrangeclaim or create a claim for each IP. Somehow.
In the meantime, the solution Could be:

Add an ipAddressClaim in the MC and add an interface in the cluster chart to add the IP to the CPI helmrelease.
Add a field in the cluster values to specify the number of IPs to take from the global pool for the WC pool so we can iterate to create that number of ipaddressclaims and patch the cpi helmrelease with the joined IPs.

Untested : https://github.com/giantswarm/cluster-vsphere/pull/266

I made some small changes to the PR and now several ips can be assigned.

the standard test was green when I ran it last week. However, as of now all providers fail and the reason is related to some already-exists issue with cert exporter configmaps in the default-apps.
This leads me to believe that its related to the default apps changes still being made.

Thanks a lot! I'll test this manually as the E2E tests won't be testing what we're changing here

I created some random lb services on a test cluster and we see the expected behavior.
Three single ip cidrs are added to the helm relesase for lb ip space.
Creating four lb services in a row resulted in these three ips being assigned to the first three and then the fourth one not getting an assignment.

Ok that's good. I think for now we can stick with this being an immutable field and keep 3 as default like you suggested here as it would be more work than worth it to make it a dynamic value. wdyt?

changes were merged


Add more links to the link bar of the inspector

iD has recently got a linkbar in the inspector (https://github.com/openstreetmap/iD/issues/5169#issuecomment-417882031).
In addition to the zoom, the following links or icons could be useful there:

Upgrade tags (https://github.com/openstreetmap/iD/issues/4591#issuecomment-453771534)
Download an incompletely downloaded relation (#5420). The shown link could also serve as an indicator of incompleteness.
Go back to:

the parent relation, when the currectly selected element was selected by clicking an item in the all members section of the parent relation.
the member, when the currect element (a relation) was selected by clicking an item in the all memberships section of the member.

Go forward (undo go back)
Restore the recent multiselection, when the currect element was selected by clicking an item in the multiseletion list.or any subsequent browsing through all members or all memberships item links.
Add the current element to the stored previous multiselection.
Add the current element to the stored previous multiselection.

To prevent cluttering the UI, links should be hidden, when they are inapplicable. Most links are applicable in relatively rare cases only. They would be shown just when they are likely required.
Typical workflows of a Newbie would unlikely led to activation of links 3. to 7., and activated links would get hidden again quite soon.

For iD v3 I converted the "Zoom to this" link to a toolbar item. Most of the items in @slhh's original list could possibly be toolbar items as well. In any case, I don't really see us adding these links as described.


[H01] Complicated deployment scheme for GrandaMento

The initialize function of GrandaMento.sol calls _transferOwnership to assign the contract ownership to msg.sender. However _transferOwnership does not check if the msg.sender is the current owner, this allows any malicious users to call initialize before it is initialized to seize control of this contract. Although we have confirmed with the Celo team their deploy strategy will ensure initialize is successful at deployment time, frontrunners can still delay deployment indefinitely by calling initialize before cLabs developers are able to do so themselves.
Additionally, ownership is assigned twice; once in the proxy, and once within initialize. This means that the call to _transferOwnership in the correctly deployed case is redundant.
Finally, there is very little documentation for future developers outlining the deployment procedure. If the fragile deployment procedure is messed up, then future implementations could have serious security issues.
Consider documenting the deployment procedures in comments, removing _transferOwnership from the initialize function, and putting the onlyOwner modifier on the initialize function. Doing this not only removes the possibility of front-running delaying correct deployment, but also increases the safety of future development efforts and is good coding etiquette.

ask OZ to remove from report

The relevant contracts are our Proxy and GrandaMento implementations. The deployment script that we/the community use is make-release. Our automated release process is well documented.
At deployment time, any new/unregistered contracts such as GrandaMento are deployed by deployCoreContract. This function

deploys an implementation contract and prevents it’s own storage from being initialized using the inherited Initializable constructor
deploys a proxy contract and transfers ownership of this proxy to the registered Governance contract

After deployment, there is no implementation address set on the proxy, so any proxy.initialize transactions will revert in the fallback function. This prevents proxy storage initialization front-running. Only the proxy.owner, which must be Governance if the deployment succeeded, can call proxy._setImplementation or proxy._setAndInitializeImplementation without reverting. This means that only governance in perpetuity can initialize a successful deployment with initialize parameters that have been voted on. A useful property of this approach is several proposals with different parameterizations can be voted on without needing multiple deployments.
The owner storage slot of any proxy deployment is distinct from the owner storage slot inherited from Ownable (ie in GrandaMento). Thus, there is no redundant ownership assignment. This separation allows us to have more modularity in our contracts and granularity of access control.
We are willing to consider making a change to the Proxy constructor which removes the need for a separate _transferOwnership(governanceAddress) transaction. Because there is no security vulnerability here, though, and there is significant code churn as a result, we would prefer to have this change go through the normal review process rather than as an “audit fix”.


Feature fields getters and setters should accept field indexes

I was recently looking at a small program that spent 30% of its CPU time in strcasecmp.

To be honest, I wish they'd only take the field index and never the name, but that's might really upset some users.

Well, a resolution from name to index is a convenience thing, I guess. There could be two separate methods or one that accepts both. But you definitely need the opportunity to use the names.
So, what is your suggestion here?

So we can add fn set_field_by_index(&self, idx: usize, value: &FieldValue), fn set_field_integer_by_index(&self, idx: usize, value: i32) and about 9 more.
But I'm worried that users will just do:
for feature in layer.features() {
    feature.set_field_integer("foo", 20);
}

instead of:
let foo_col = layer.field_index("foo")?;
for feature in layer.features() {
    feature.set_field_integer_by_index(foo_col, 20);
}

just because it's easier to find.

Yeah, either it would be …by_index and …by_name separately or you just have to keep strongly typing it to size :smile: .


[Feature] Mysql subtable with binlog model merge one table

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
I want to megre Mysql subtable into one table and can update by unique key
Use case
No response
Related issues
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

You can use Agg key and replace_if_not_null implement multitable merge.


Datamart Seller Guidelines

The Datamart guidelines for a data vendor/user
Purpose
The guidelines that a vendor or user will read or refer to for their engagement with the datamart.
Intent
To be read by a user to understand how to engage/interact with the datamart.
Completion
A set of guidelines suitable for a "user".
Note
This does not include the legal policy documents for privacy and data access.

TIKI Data Access
We provide users with the opportunity to exchange their data for something that is relevant to them in exchange for sharing their anonymous data. We ensure that the data we collect and share with the buyers and developers about their customers and services always protects the privacy and security of you, our users.
Data Collection and Sharing
When you, the user share their data, you trust us with their information. We understand this is a big responsibility and work hard to protect our your information and put you, the user in control.
Please review our privacy policy (to be written) to understand what information we collect, why we collect it, and how it can be updated, managed, exported, and deleted. We do not share users' personal information with companies, organizations, or individuals outside of Tiki except in certain circumstances described in our privacy policy. Further, our data access policies (to be written) restrict access to identifiable non-public app data of another developer.
Data Accessibility
The data shared with buyers and developers helps them understand the users: from how they found your service, to how they engage with it, and what the users pay for.
The data we provide to buyers and developers is aggregated and anonymized to protect user privacy. For example, buyers and developers have access to their apps’ data regarding:
• device information and when the device has accessed our systems,
• user activities (such as searches, listing impressions, and pre-registration requests),
• user info (such as registered country and language preference) and user-triggered app events (such as installs, updates, uninstalls purchases)
• TBC
Buyers and developers also have access to aggregated data to benchmark their performance across an ecosystem. For example, a game developer could compare user acquisition rates against similar game genres in the same region. This data is aggregated to protect any single developer's performance information from being determined.
Data Contracts
The service offered by Tiki is to help extract and present user data for the generation of insights and analysis.
The contract for payment will be between the buyer and developer and the user. Tiki will not be responsible for the billing or payment to the user for this service.
Support
Please see mytiki.com/support
We continuously work to ensure buyers and developers have the information they need to succeed. For more information on the statistics and insights available to buyers and developers, visit the TIKI Help centre.


Updated npm and bower dependencies, fixed tests and jshint validations

I have updated the dependencies and fixed the tests to make sure that everything is up and running.

Closed in favour of #279


Unify all containers

Get rid of any extraneous containers

Very nearly there. All share the same base instance now plus just their own scripts.

Now depends on compiler-explorer configuration.


Producer message from file

Hey there
I'm new to this extension, I'm reading the documentation but haven't found if there's a way to load the message to be sent from a file.
If I write {{}} I can see some system.path stuff, but I'm not sure if I can use that to tell the producer to send the contents of a file
This is what I'm attempting to do:
PRODUCER message-from-file
topic: mytopic
{{path/to/file.xml}}

This is not supported. In the meantime can just copy the content of the xml file into the .kafka file, eg.
PRODUCER my-producer
topic: mytopic
key: mykey

<foo>
  <bar />
</foo>


[WIP] Use TreeBuilder for Infra and Cloud

Taking over #1702 from @martinpovolny .

@miq-bot add_label WIP

@miq-bot add_label technical debt


Cancel button is in Russian when using Locale

Thanks for publishing and maintaining this package!
It works smoothly but when I use it with Locale cancel button is same in Russian most of the times. Tried flutter clean, re-run without positive result. Other parts of the modal widget is working perfect with locale such as month names.
Locale('uz')

Locale('ru')

Locale('en')

Hi, gonna try to fix this, but im not sure if i can work on the solution before monday. If you need this faster and want to send a PR i can review it

@Macacoazul01 it is not so urgent, I'm displaying that text using conditions so far. I appreciate your time!

@Abdulvaliy the problem is happening because the text on the buttons are related to the locale of the app not the one forced to the dialog:

The year-month grid is built with the locale set on the app:

Is the default language set to russian on your material app? If so this is what causes the behavior.
Im not sure on how to fix this as there is no way to access cancelButtonLabel and okButtonLabel outside the app context (didnt find on my searches), there are some options that i can think:
1-Removing this from the code and adding the strings again as a text parameter as they were before  (I really dont want to go with this path).
2-adding then as optional null values with cancelButtonLabel and okButtonLabel as default.
3-Forcing the locale of the grid to be the same as the app (this already happens if you maintain the locale parameter as null, so noting will change on the code).
try changing the locale in your material app to see if this is really the problem:
  final Locale appLocale = Locale('fr', 'CA');

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      locale: appLocale,

....

This is my MaterialApp

This is the showMonthPicker dialog

I have used locale in the showMonthPicker() as a parameter not in MaterialApp. When I use it in MaterialApp there is no problem.
Thanks, problem is solved!


primary colour is changed

Describe the bug
When you input a specific custom colour for your Primary, Secondary or Tertiary, the tool changes that colour to something else.
This happens in both the web version and the Figma version.
To Reproduce
Steps to reproduce the behavior:

Go to the Figmal plugin, or Web tool
Click on "Primary" and change the colour to hex value #002949, and apply that.
Check the value of the primary colour, it will have been changed to #0061A3.
The value of the primary colour was changed from #002949 to #0061A3.

Expected behavior
The tool should not change a custom colour when its directly specified.
Additional context
This happens in both the web version, and the Figma version.

I believe I'm having a similar issue, possibly related? The system generates a secondary color from the primary color, if I change the secondary color, and then decide to change it back I can't. It won't accept the secondary color it originally generated.
I know the rendered palette isn't supposed to match the source color, but in this instance, something seems off? I'm not sure if this is expected? You will also notice that even dismissing the input alert (clicking cancel) changes the secondary color for some reason even if nothing was changed.
https://user-images.githubusercontent.com/10838153/164592716-e418c527-1e3b-4b5a-a07c-0bf3b566d1be.mp4
I hope this helps, thank you! The Material Theme Builder is a great tool!

That is correct, it is currently expected behavior.


Add buildscript to build installable zip

This commit adds an bash script to build an ZIP file that can be used for the Shopware Plugin Manager.
You should consider tagging your current release, build a zip file and add it to the github release page.
See: https://github.com/shopwareLabs/SwagMediaS3/releases

Thanks i will do tags and releases


Please unlock MetaMask

Describe the bug
I can't get past the "Please unlock MetaMask." message on the RTC dashboard.
To Reproduce
Steps to reproduce the behavior:

Have metamask ready to go
Go to https://play.temporal.cloud/rtc

Additional context
I don't know that much about RTC. I'm pretty sure my metamask is unlocked.

Metamask on that website is no longer functional. In order to pay for credits with metamask you'll need to use the new experimental playground
https://play2.temporal.cloud which will be replacing the playground

Also technically you can use metamask on the current playground but it doesn't respect metamask privacy settings.
The solution to this is to alter the metamask privacy setting that makes it so websites are required to prompt you to unlock your account.
The downside to this is that if you don't disable this afterwards metamask will be injecting itself everywhere.
The solution to this is to use play2 until that supersedes play.temporal.cloud later this month or early next.

Seems that running ethereum.enable() in the dev console gets it running. Also the new website looks good.

Interesting never knew that was possible. I'm going to close this now, if you run into any issues create a new issue referencing this one.
Thanks! Feel free to give your feedback in our telegram, negative feedback is ok as long as it's constrictive.


Cannot download the model checkpoint.

I cannot download the checkpoint from the download assets and all associated links. Please check.

Hi,
Here are the updated links for the checkpoints.
VAE checkpoint

Guidance
Resolution
FID
Model

Yes
256x256
2.28
imagenet256-guidance.pt

No
256x256
5.69
imagenet256-conditional.pt

Yes
512x512
2.50
imagenet512-guidance.pt

No
512x512
10.79
imagenet512-conditional.pt

Thanks!

It can't work!!!


mlflow.exceptions.MlflowException: Run 'LIFFireNet' not found

Kindly let us know how to solve this issue after running
python eval_flow.py LIFFireNet --config configs/eval_ECD.yml
Kindly help

Hi! Have a look at this section of the readme; you should download the pretrained models before you can run an evaluation (or train your own models)

Hi,
I put all the pretrained models in a current directory. But still the same issue with a bug

Hi, I'm having the same problem. After I unzip the mlruns.zip file, I get _MACOSX and mlruns 2 folders. I move the 42 folder under the mlruns 2 folder to the mlruns directory and delete the _MACOSX and mlruns 2 folders. This way I get the same directory structure as you said.


CI with testling-ci

To do:

[ ] update package.json (see http://ci.testling.com/#package.json)
[ ] update tests to produce TAP output using https://github.com/substack/tape (see http://ci.testling.com/#write)
[ ] add a webhook to http://git.testling.com (see http://ci.testling.com/#hook)
[ ] add badge in README.md (see http://ci.testling.com/#badge)

See also #540

There is another alternative called Sauce Labs. Reportedly faster than testling.

Implemented alternative cross-browser compatibility tests via Sauce Labs in #927.


Add number for offending line in File Content Regex rule

Fixes https://github.com/JamitLabs/ProjLint/issues/31

Thanks, will have a detailed look soon and merge if all looks good. But code is fine to me.


Add to member list

{
        "title": "Lukas Möller",
        "url"  : "https://lukas-moeller.ch/blog",
        "feed" : "https://lukas-moeller.ch/api/rss2.xml"
}

Awesome, great to have you in Polyring.
Side note: your blog posts are failing to load for me (it only shows "An unexpected error has occurred.") with tons of TypeError: CSS2Properties doesn't have an indexed property setter for '0' messages in the browser console. I assume you are aware of that, but still wanted to bring attention to it :slightly_smiling_face:

Thanks a lot,  this is a really cool project you started here. And thanks for the bug report, it looked like something from the mdx library I use, should be fixed. I actually wasn't aware of it, so I am happy that you brought it up. I also just deployed my polyring integration - it was pretty easy thanks to the astonishingly simple API.


Fix 1848 date serialization

:tada: This PR is included in version 6.113.3 :tada:
The release is available on:

v6.113.3
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.0.0-beta.11 :tada:
The release is available on:

v7.0.0-beta.11
GitHub release

Your semantic-release bot :package::rocket:


Check memory leak in nuttx

tuvtester running in nuttx.
First run
nsh> free
             total       used       free    largest
Mem:        165104      13136     151968      97376

Second run
nsh> free
             total       used       free    largest
Mem:        165104      13472     151632      97376

Testing with valgrind / linux reports no leaks.

uv__async_start() need revise for nuttx. leak is cause of pipefd[1] is not closed.

When pipe() is called /dev/pipe%d device is created with register_driver() for the pipe but is not removed when both handles are closed. As device can be reused it is OK not to unregister for performance. But it's confusing whether there is other memory leak or not.

Memory leak is fixed for linux and also for nuttx. There was one for linux when checked with valgrind.
For nuttx, as /dev/pipe? file allocates memory, should have to delete the file to check the leak.
But as there is some problem with g_pipeset in nuttx/drivers/pipes/pipe.c sync with pipecommon_freedev() call, second run of tuvtester fails.


small typo in rescaledata.html

Correction of a small typo in the docfile of rescaledata.

Thanks!


Speed value returns -1 and 0

Hey everyone!
I have encountered a problem with speed and heading from watchPosition listener
  useEffect(() => {
    const watchId = Geolocation.watchPosition(({ coords }) => {
      const { latitude: lat, longitude: lng } = coords;
      setCurrentLocation({ lat, lng });
    }, (err) => console.log(err), {
      enableHighAccuracy: true,
    });

    return () => {
      Geolocation.clearWatch(watchId);
    };
  }, []);

The lng and lat values work fine, but the two above are 0 (on Android) and -1 (for iOS) for speed and -1 for heading.
I'm using fake GPS for Android while testing and prepared GPX file for iOS
Thanks in advance!

@MRadek55 have you found a solution for this?
I`m facing the same issue

@MRadek55 have you found a solution for this? I`m facing the same issue

I have encountered that it is only when we are using fake gps or gpx simulation. On real tests it works fine

I can't make it work on physical iOS device. I have a view showing latitude, longitude and speed and despite latitude and longitude continue updating as I move, the speed stays at -1
I have enableHighAccuracy set to false and wifi on, could depend on this?


Package test error

The command TEST_BROWSER_DRIVER=chrome meteor test-packages --driver-package dispatch:mocha fails with the error message Error: When running tests with TEST_BROWSER_DRIVER=chrome, you must first "npm i --save-dev selenium-webdriver chromedriver". I've already run this command and installed the dependencies. This seems like an issue with the way dependencies are loaded when using test-packages vs test. Do you have any ideas how to fix this issue?

Moved to https://github.com/aldeed/meteor-browser-tests/issues/5