twitches

This is a great project. Thank you very much for it.
I also repeated it, however, I am having problems with some settings - when approaching the end point, the ZableCam twitches instead of smooth braking.
https://youtu.be/fO23YbsISy8
And also, in the neutral position, when nothing happens, it automatically rolls back (the holding force is insufficient)
Can somebody help me set it up?

I am planning to get back to this project in the next months but do not have any spare time at the moment.
What ESC are you using? I am planning to use the oDrive only in near future.

Hi Wernerd. Nice to heare you :)
Thank you for your feadback.
I'm using Flipsky VESC based controller. It's working fine in Limited mode but not in End points mode


WIP: srpm: use relative paths

https://github.com/packit-service/packit-service/issues/344
https://github.com/packit-service/packit-service/issues/363
so that we have one set of variables we can use both in sandcastle and
locally in packit CLI
CC @lbarcziova

closing in favor of #698


Url boostrap-map-js error 404

The page https://esri.github.io/bootstrap-map-js/src/js/bootstrapmap.js is not available. It shows the error 404 site not found. Why?

@mariajosemontoya this project isn't being maintained. If you can provide more info on your requirements we can direct you to a more appropriate direction?

I had to same issue today. Were you able to resolve it? I found bootstrapmap.js here: https://github.com/Esri/bootstrap-map-js/tree/master/src/js but I wasn't able to simple copy and replace in my project. Now I get the error: BootstrapMap.create is not a function. Any idea what is going on?

@mariajosemontoya this project isn't being maintained. If you can provide more info on your requirements we can direct you to a more appropriate direction?

We are developing a prorotype for a web application with a arcgis.com map. The web application uses bootstrap, so we use that library. Could we get rid of that library and use directly ArcGIS JS API and still get a responsive app? Has the JS API included all the features from that bootstrap library?

Could we get rid of that library and use directly ArcGIS JS API and still get a responsive app?

I can't offer any advice on your existing library, but I can definitely say yes the JS API 4.x map and widgets are designed to be responsive. The most obvious example is popups.

Has the JS API included all the features from that bootstrap library?

JS API 4.x now includes some of these responsive features as related to the mapping UI components. However, for building additional UI components outside of the map, you might also take a look here: https://github.com/Esri/calcite-components.

as mentioned in the README, the project which superseded this one is https://github.com/Esri/calcite-maps.
this repo should be archived.

Calcite maps is also deprecated. I don't recommend using it. We'll get this README updated.


require .png works in chrome but not firefox

I'm not sure what I've done, but I have this image:
notFoundUrl: require("../../img/petals.png")

That webpack seems to find and load just fine in Chrome but not in Firefox.  My webpack loader config looks like:
      ,
        test: /\.(png|jpg)$/
        loader: 'url-loader?limit=8192' # inline base64 URLs for <=8k images, direct URLs for the rest

See for example: (http://zulily.github.io/react-datum/docs/examples/).   The last two tiles on the left should have the petals.png image but show as broken, and render without a src on Firefox.  I tested with two different machines with Firefox 42 and one hopelessly stuck on 36.
Thank you for your help.

I did a bit more debugging on this issue.  In Firefox, the base64 encoded 'url' looks quite different on Firefox and Chrome debuggers.
In Chome, the module exports returned from webpack_require(24) =
"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAGQAAABoCAYAAAAHIFUvAAAAGXRFW…dk7GCMERBgUpCgmqJbQEcPxlgBIVDohNbFrwJGR/8XYAA/IBnrVTxJagAAAABJRU5ErkJggg=="

In Firefox, the same method returns a much bigger image src that displays renders in the DOM with the image tag having src=""
Interestingly,  I tried setting the Chrome image src to the data above in firebug console and, viola, petals.  See attach screenshot and text file for the full firefox base64 data.
I tried to just hard code the chrome value in source code but that didn't work either on firefox.

webpackImageData.txt

This issue was moved to webpack/url-loader#20


RT API meta-metric

It would be useful to have a meta-metric like fastly_rt_up that indicates if the exporter has a valid connection to the RT API for each service.

I like it.

LGTM, Thanks!


admin: cannot easily locate challenge

as a superuser, it is not possible for me to quickly locate a challenge to modify or inspect without knowing either the parent or the challenge id.

Actually you need to know both the parent and the challenge ids because of the way the URL is constructed.


qutebrowser: add setuptools as a dependency to fix startup

Motivation for this change
#68314

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

backported in 5c89877e2e73449da197f8d590678368454fbedb


how to loginWithUsername not loginWithEmail

I can't find in the package or docs any place to loginWithUsername
how can I login with username not email?

@martijnwalraven is there a way to do this?

@martijnwalraven is this really hard to implement. We are willing to edit the code to login with username as it is critical for us. Any advice?
I found the methods for logging in with email here:
https://github.com/martijnwalraven/meteor-ios/blob/affe8d13a876a0e6e7c95656339d496cbc54a649/Meteor/METDDPClient%2BAccountsPassword.m
How should we edit this to login with username? That is all we need.

I'm sorry I haven't responded before, I'm really caught up in other work.
Logging in with username should have been in here in the first place, and it's rather easy to add. Basically, all you need to do is replace email with username everywhere :)

@great no problem martin, thanks! I just needed to know that, I was digging through the code to try and figure it out but I couldn't quite get all the way to the bottom of it to see the solution. Thanks and sorry about bugging you!
Will try this an close the issue with a report of how I got logging in with username to work


[ZEPPELIN-4408] Return exception message when Interpreter code is incomplete

What is this PR for?
When there's a syntax error in your code such as missing a closing parentheses etc. an exception message "Incomplete expression" will be returned to make it easier to debug.
Currently paragraph simply goes into finish state and makes it harder to know if the code is complete or not.
What type of PR is it?
Improvement
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4408
How should this be tested?

On Spark interpreter run (println("Hello World")

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Thanks for the contribution, @amakaur  Could you add unit test  ?

ping @amakaur

@zjffdu sure.

ping @zjffdu

LGTM


Add dependabot to manage node dependencies versions

See- https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#example-of-a-basic-setup-for-three-package-managers

I'm enthusiastic about this idea and fully support its implementation in upcoming versions. That's why I'm assigning it a low priority for now.


fix csv missing fields issue and empty csv on _source fields

Description
[Describe what this change achieves]
Issues Resolved
#206
#202
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #206 (3c46a92) into main (56008de) will decrease coverage by 9.76%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #206      +/-   ##
============================================
- Coverage     62.60%   52.83%   -9.77%
  Complexity      297      297
============================================
  Files            99       66      -33
  Lines          4190     2135    -2055
  Branches        661      245     -416
============================================
- Hits           2623     1128    -1495
+ Misses         1424      867     -557
+ Partials        143      140       -3

Flag
Coverage Δ

dashboards-reports
?

reports-scheduler
52.83% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...s-reports/server/routes/utils/dataReportHelpers.ts

...rts/server/routes/utils/savedSearchReportHelper.ts

dashboards-reports/test/propsMock.js

...ashboards-reports/server/utils/validationHelper.ts

...ic/components/main/loading_modal/loading_modal.tsx

...orts/server/routes/utils/converters/uiToBackend.ts

...itions/report_trigger/report_trigger_constants.tsx

dashboards-reports/common/index.ts

...s-reports/public/components/main/reports_table.tsx

dashboards-reports/server/model/backendModel.ts

... and 23 more

Continue to review full report at Codecov.

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


Sprint 8 requirements

This makes some UI changes to both user type dashboards and adds buttons to connect an account management page

Added sprint 9 requirements to this branch as well


Does websocket need authentication?

publicClient is working fine, but websocket is giving me CORS header ‘Access-Control-Allow-Origin’ missing error.  Any suggestion is appreciated.

Yea what is up with this?

I was told that CORS headers need to be set on the resource https://ws-feed.gdax.com/ , so I think only gdax developers can do this.

@nengine I also came across this issue, I ended up moving all of my websocket code out of the browser and to a webserver.

Maybe I'm underslept, but the gist of these last two comments is that the library does not work, yet there are docs for it, so ppl r just gonna waste time testing code that is objectively non-functional. Cool. Maybe take out the websocket section of the tut or provide working code?

Installing from github ( npm install coinbase/gdax-node ) fixed all the issues I was facing including the 404 error. It might be worth it to take the npm install gdax command out from the readme entirely.

Even after installing from coinbase/gdax-node does not work for me on the client side Vue.js app mounted inside Rails 5.1 with webpacks shown in example #1.  On the other hand, it works fine on server side express.js app as shown in example #2, #3.  May be this is what @azamatsmith saying about moving to webserver.  But ideally it should work on the client side too right?  @LRonHubs what client side app/framework you are using?
example 1 (Vue.js client app)
<template>

{{ message }}

    <button @click='load'>Load data</button>

</template>

example 2 (express.js server app)
const Gdax = require('gdax');
const publicClient = new Gdax.PublicClient();
const websocket = new Gdax.WebsocketClient(['LTC-USD']);

websocket.on('message', data => {
  console.log(data);
});

example 3 (express.js server app)
const Gdax = require('gdax');
const publicClient = new Gdax.PublicClient();
const WebSocket = require('ws');

const ws = new WebSocket('wss://ws-feed.gdax.com');

ws.on('open', function open() {
  const subscribeMessage = {
      type: 'subscribe',
      product_ids: ['LTC-USD']
  };
  ws.send(JSON.stringify(subscribeMessage));

  var heartbeatMessage = {
    type: 'heartbeat',
    on: true,
  };
  ws.send(JSON.stringify(heartbeatMessage));
});

ws.on('message', function incoming(data) {
  console.log(data);
});

Right now we don't support embedding our client into web pages, so you would need to proxy all requests. This might change in the future, we don't have any immediate plans though. Closing this in favor of https://github.com/coinbase/gdax-node/issues/33

What did you meant to proxy all requests?  Thanks.

He means you need to set up a small server (e.g. in node.js) that sits on the same machine as your browser (i.e. same vs cross-origin); then the server forwards all requests from the browser (i.e. proxies) to the GDAX api. see https://en.wikipedia.org/wiki/Same-origin_policy

Has anyone made or found a small server that they could share? It would be nice to not have to remake it.


Browser Cache and ServiceWorker

I've implemented ServiceWorker cache on one of my website combined with expire headers for static resources so JS included.
Now I have a strange behaviour. It looks impossible to invalidate the cache on the user browser.
It is related to the ServiceWorker or to the Long Lasting expire headers.
Using CTRL+F5 works only on the first refresh. If I reopen the page it looks like the previous version.
Can you address to some documentation on cache invalidation?

ServiceWorker isn't for traditional caching exactly but for making your app work offline. For offline case you need to version your service worker with your assets like in this tutorial http://www.html5rocks.com/en/tutorials/service-worker/introduction/.
Then when your app updates, you just bump the version which forces a service worker update and a new install. In the new install you add new assets to the cache keyed with the new version identifier and remove old caches that are based on key that is older than the current version identifier.
There is probably a full featured offline app service worker tutorial somewhere but I forgot where.

Also, for development I'd have an if inside the worker to not do any caching while in development.

Cache control is provided by https://fetch.spec.whatwg.org/#requestcache, but hasn't been implemented by Chrome yet.
However, if you find yourself cache-busting here, it's often the sign that you should just fix your cache headers.


ARROW-2251: [GLib] Keep GArrowBuffer alive while GArrowTensor for the buffer is live

It prevents GC-related crash.

Partially right. shared_ptr<Tensor> keeps shared_ptr<Buffer> alive but memory in the shard_ptr<Buffer> may be freed when the shared_ptr<Buffer> just refers external memory. It's caused by creating shard_ptr<Buffer> by Arrow::Buffer.new("...data...") in Ruby. (It creates GArrowBuffer in C.) The "...data..." should be alive while the Arrow::Buffer is alive. shared_ptr<Buffer> is only alive without this change. Both shared_ptr<Buffer> and GArrowBuffer are alive with this change. The GArrowBuffer should keep the data alive.
I'll send one more pull request to improve memory management in GArrowBuffer.

I see, so there's a "weak" reference to memory that is held by another buffer object. We have to deal with some issues like this in Python to handle dependency chains where the shared_ptr<Buffer> is not aware of memory relationships expressed at the Python level


Fix typo in project.pbxproj

This typo causes the following error

Unable to create file '{{ cookiecutter.formal_name }}.xcodeproj/project.pbxproj'
Error message: 'dict object' has no attribute 'forma_name'

Using

Python 2.7.10
cookiecutter==1.4.0

Thanks for the report and Pull Request!


Harvest Totals only for Last 25 Harvested

Is there a setting we can change to allow for "Total of all Harvested"?  Also possibly an "average XEM per harvest".

@BloodyRookie after all the inices that we've changed in db, do you think we could add query for that, that would be fast enough? (I think so)

What about a button "show total"?

The total and average harvested info should be only for the account displayed in the gui, right?
(An overall total/average for all blocks would be something to display in nembex maybe.)

Yes of course, the account which is currently selected in the GUI (NCC interface in the browser) should only be able to show the total harvested fees for that account, not all existing XEM accounts.


Extensive logs while pulling non existing image

Description:
Extensive amount of logs are printed stating the status if image pulling when cells are started with non existing dependency cells.
Steps to reproduce:

Delete wso2cellery/pet-be-cell:latest-dev image if you have it in the local repository.
cellery run wso2cellery/pet-fe-cell:latest-dev -n pet-fe -l petStoreBackend:pet-be -d

The issue still exists when pulling composites, it's resolved for cells.
cellery run wso2cellery/pet-fe-comp-cell:latest-dev -n pet-fe-comp-cell-inst -d
✔ Connecting to registry.hub.cellery.io
✔ Fetching metadata
✔ Pulling image wso2cellery/pet-fe-comp-cell:latest-dev
✔ Removing old Image
✔ Saving new Image to the Local Repository
Image Digest : sha256:7875d04057cb708ee9109075fc7f68e00522e7e5cd42b57a0e74807a48625f3f
✔ Extracting Cell Image wso2cellery/pet-fe-comp-cell:latest-dev
✔ Reading Image wso2cellery/pet-fe-comp-cell:latest-dev
Info: Main Instance: pet-fe-comp-cell-inst
Info: Validating dependencies
Info: Instances to be Used
INSTANCE NAME                  CELL IMAGE                          USED INSTANCE             KIND            SHARED
pet-be-complatest-dev1248      wso2cellery/pet-be-comp:latest-dev  To be Created             Composite       -
pet-fe-comp-cell-inst          wso2cellery/pet-fe-comp-cell:latest-dev To be Created             Cell            -
Info: Dependency Tree to be Used
pet-fe-comp-cell-inst
└── petStoreBackend:pet-be-complatest-dev1248
Info:
⠋ Connecting to registry.hub.cellery.io
⠙ Connecting to registry.hub.cellery.io
⠹ Connecting to registry.hub.cellery.io
⠸ Connecting to registry.hub.cellery.io
⠼ Connecting to registry.hub.cellery.io
⠴ Connecting to registry.hub.cellery.io
⠦ Connecting to registry.hub.cellery.io
⠧ Connecting to registry.hub.cellery.io
⠇ Connecting to registry.hub.cellery.io
⠏ Connecting to registry.hub.cellery.io
⠋ Connecting to registry.hub.cellery.io
⠙ Connecting to registry.hub.cellery.io
⠹ Connecting to registry.hub.cellery.io
⠸ Connecting to registry.hub.cellery.io
⠼ Connecting to registry.hub.cellery.io
⠴ Connecting to registry.hub.cellery.io
⠦ Connecting to registry.hub.cellery.io
⠧ Connecting to registry.hub.cellery.io
⠇ Connecting to registry.hub.cellery.io
⠏ Connecting to registry.hub.cellery.io
⠋ Connecting to registry.hub.cellery.io
⠙ Connecting to registry.hub.cellery.io
⠹ Connecting to registry.hub.cellery.io
⠸ Connecting to registry.hub.cellery.io
⠼ Connecting to registry.hub.cellery.io
⠴ Connecting to registry.hub.cellery.io
✔ Connecting to registry.hub.cellery.io
Info:
⠦ Fetching metadata
⠧ Fetching metadata
⠇ Fetching metadata
⠏ Fetching metadata
⠋ Fetching metadata
⠙ Fetching metadata
⠹ Fetching metadata
⠸ Fetching metadata
⠼ Fetching metadata
⠴ Fetching metadata
✔ Fetching metadata
Info:
⠦ Pulling image wso2cellery/pet-be-comp:latest-dev
⠧ Pulling image wso2cellery/pet-be-comp:latest-dev
⠇ Pulling image wso2cellery/pet-be-comp:latest-dev
⠏ Pulling image wso2cellery/pet-be-comp:latest-dev
⠋ Pulling image wso2cellery/pet-be-comp:latest-dev
⠙ Pulling image wso2cellery/pet-be-comp:latest-dev
⠹ Pulling image wso2cellery/pet-be-comp:latest-dev
⠸ Pulling image wso2cellery/pet-be-comp:latest-dev
⠼ Pulling image wso2cellery/pet-be-comp:latest-dev
✔ Pulling image wso2cellery/pet-be-comp:latest-dev
Info:
⠴ Removing old Image
✔ Removing old Image
Info:
⠦ Saving new Image to the Local Repository
✔ Saving new Image to the Local Repository
Info:
Info: Image Digest : sha256:c32056cedd32b8432600c7360142484cefcf59de8ceddaad49e7e2b7c42768bb
Info:
Info:
Info: ✔ Successfully pulled cell image: registry.hub.cellery.io/wso2cellery/pet-be-comp:latest-dev
Info:
Info: What's next?
Info: --------------------------------------------------------
Info: Execute the following command to run the image:
Info:   $ cellery run registry.hub.cellery.io/wso2cellery/pet-be-comp:latest-dev
Info: --------------------------------------------------------
Info:
Info: starting instance pet-be-complatest-dev1248
✔ Starting main instance pet-fe-comp-cell-inst
✔ Successfully deployed cell image: wso2cellery/pet-fe-comp-cell:latest-dev
What's next?
Execute the following command to list running cells:
$ cellery list instances

Are you using the latest SDK? This is working as expected with the latest SDK.
cellery run wso2cellery/pet-fe-comp-cell:latest-dev -n pet-fe-comp-cell-inst -d
✔ Connecting to registry.hub.cellery.io
✔ Fetching metadata
✔ Pulling image wso2cellery/pet-fe-comp-cell:latest-dev
✔ Removing old Image
✔ Saving new Image to the Local Repository

Image Digest : sha256:719d93a1bc2e78041e5117b029ebb8b50b7697e7a28cd53257dd2159176500f5

✔ Extracting Cell Image wso2cellery/pet-fe-comp-cell:latest-dev
✔ Reading Image wso2cellery/pet-fe-comp-cell:latest-dev
Info: Main Instance: pet-fe-comp-cell-inst
Info: Validating dependencies
Info: Instances to be Used
------------------------------------------------------------------------------------------------------------------------
INSTANCE NAME                  CELL IMAGE                          USED INSTANCE             KIND            SHARED
------------------------------------------------------------------------------------------------------------------------
pet-be-complatest-dev6pl5      wso2cellery/pet-be-comp:latest-dev  To be Created             Composite       -
pet-fe-comp-cell-inst          wso2cellery/pet-fe-comp-cell:latest-dev To be Created             Cell            -
------------------------------------------------------------------------------------------------------------------------
Info: Dependency Tree to be Used

pet-fe-comp-cell-inst
└── petStoreBackend:pet-be-complatest-dev6pl5

Info: starting instance pet-be-complatest-dev6pl5 f8ca859d424404cbe4e3808ef3973dc1dc169095f5
✔ Starting main instance pet-fe-comp-cell-inst

✔ Successfully deployed cell image: wso2cellery/pet-fe-comp-cell:latest-dev

What's next?
--------------------------------------------------------
Execute the following command to list running cells:
  $ cellery list instances
--------------------------------------------------------

@anuruddhal : Just an additional question, this log doesn't say that pet-be cell is not present and hence it's pulling the image from hub. Don't we need to show it as well ?. In my original issue, that was the case I was trying.

@hasinthaindrajee Added more logs via https://github.com/wso2-cellery/sdk/commit/7acd6620716eeb10d67065f000cecc8e3c31585e

I was using some latest build as of yesterday. However, I downloaded the today's build as of 1:33PM LKT, and it's working with this. Therefore, we can resolve the original problem. Thanks.


Can I deploy it on Railway?

On deploying on railway I am getting this error: Error: Unexpected server response: 403. anyway to deploy it on railway?

It should work, but I don't have any experience with Railway.


SQL 2019 on permise

external table wizard do not work for sql server 2019 3.1 ctp

fresh install resolved.

@sneevand Glad it worked out for you.  :-)


[#1615] bug fix for creating citation

@gantian127 - Have merged this with develop and updated beta, please verify on beta.

@mjstealey The bug is fixed on Beta. Thanks


Inconsistent ordering of output to STDOUT

I have found that mixing different methods of writing to stdout results in inconsistent ordering of the output.
The following simple program illustrates this:
// Test sequencing of STDOUT

#include <pico.h>
#include <pico/time.h>
#include <pico/stdio.h>
#include <pico/stdio_usb.h>
#include <stdio.h>

int main (int argc, const char **argv)
    {
    stdio_init_all();
    while ( ! stdio_usb_connected() ) sleep_ms(1000);
    char a = 'A';
    char b = 'B';
    fwrite (&a, 1, 1, stdout);      // Output the character 'A'
    printf ("%c", b);               // Output the character 'B'
    fflush (stdout);
    printf ("\n");
    }

Clearly the expected output is AB. However, in practice the output is BA.
The CMakeLists.txt file I am using is:
cmake_minimum_required(VERSION 3.12)
set(CMAKE_C_STANDARD 11)
set(CMAKE_CXX_STANDARD 17)
include($ENV{PICO_SDK_PATH}/external/pico_sdk_import.cmake)
project(sio_test C CXX ASM)
pico_sdk_init()
add_executable(${PROJECT_NAME} main.c)
target_link_libraries(${PROJECT_NAME}
  pico_stdlib
  pico_time
  pico_stdio
  pico_stdio_usb
  )
pico_enable_stdio_usb(${PROJECT_NAME} 1)
pico_add_extra_outputs(${PROJECT_NAME})

A slightly refined example with the same result
// Test sequencing of STDOUT

#include <pico.h>
#include <pico/time.h>
#include <pico/stdio.h>
#include <pico/stdio_usb.h>
#include <stdio.h>

int main (int argc, const char **argv)
    {
    stdio_init_all();
    while ( ! stdio_usb_connected() ) sleep_ms(1000);
    char a = 'A';
    char b = 'B';
    fprintf (stdout, "%c", a);      // Output the character 'A'
    printf ("%c", b);               // Output the character 'B'
    fflush (stdout);
    printf ("\n");
    }

This is because we try to reduce code size by preventing the HUGE amount of FILE handling code used by fprintf and friends from being pulled in just for a simple printf. This means that printf does not go thru the C-library, whereas fprintf does, and the latter is what is buffering.
You can fix your problem, by moving the fflush(stdout) after the fprintf, but also we will be adding
PICO_STDIO_SHORT_CIRCUIT_CLIB_FUNCS define in the next release, which you can set to 0 to for printf to go thru the c-library

You can set PICO_STDIO_SHORT_CIRCUIT_CLIB_FUNCS=1 in your target_compile_options if you want to mix printf and fprintf(stdout). The reason we don't do that by default is that otherwise you pull in all the C library FILE handling code


Next Track Action

Hi was wondering is there a way to create a countdown card. That shows the next track action eg
Free Practise 1  3d 04h 36m 25ss
Then its changes to the FP2 then FP3 then Qualifying and finally Race.
Thanks
Mark

Check the type countdown ;-)


ssh

When I click on the ssh connection remote host function on the interface, it prompts robot@sy's password:, but I make sure that my password is entered correctly, but I will always be prompted to re-enter it. I don’t know what to do. If you know why, please let me know I am grateful.

In most cases the user does not exists or the password is wrong.
Which function of the node manager did you use? Are errors or warnings printed in the terminal where you launched the node manager?

I assume it was solved, please reopen if not!


Expose certificate request type in SslServerCredentials

Fixes https://github.com/grpc/grpc/issues/14381.

CC @jiangtaoli2016

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,956      Total (=)      1,955,956

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,888      Total (=)     10,843,888

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,956      Total (=)      1,955,956

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,882      Total (<)     10,843,883

 No significant differences in binary sizes

Known failures:
https://github.com/grpc/grpc/issues/16471
https://github.com/grpc/grpc/issues/13379

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,968      Total (=)      1,955,968

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,892      Total (>)     10,843,888

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,965,108      Total (=)      1,965,108

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,887,891      Total (=)     10,887,891

 No significant differences in binary sizes


Long Distance Travel System

As it currently stands, attempting to find a path to a destination too far away will result in trying to access unloaded chunks and will crash the pathfinder. Even if this crash was patched, it still limits the distance that the bot can travel. In addition, the time it would take to find such a path would be beyond unreasonable for any realtime applications.
My proposal for a long-distance travel system could be to use two sets of grids to run the pathfinder on. The smaller grid is the standard grid that uses regular Minecraft blocks as we have now. The second grid is a larger grid where each node is 16 blocks away from each other, along the XZ plane. When traveling distances greater than 64 blocks, the bot would first try to find a path on these larger grid units. (By default, these all considered completely connected.)
After a path is discovered across the larger grid, the bot will attempt to find a path from each node in the path to the next. If no valid path can be discovered between two large grid units within a 16 block range, the connection is removed from the large grid and the large grid is recalculated. If paths are found, the distance from one node to the next is saved as the distance between both nodes on the larger grid.
This approach also has a few other benefits. Because the solver is running multiple separate pathfinding instances, these can be run async. This means that after the large grid solves at the first small grid solves, the bot can start moving instantly while the rest of the path solves. The bot can start traveling a distance of 10,000+ blocks without any initial delay.
Also, various post-processing effects can be applied to the large grid as well, such as straight pathing.
Lastly, when coming to situations such as the spawn wall of 2b2t (A famous wall around spawn, with a radius of 2km) The bot would be smart enough to know how to tackle going around this. The solver would just tackle finding new paths for the smaller grid instances, so all paths can be correctly solved with <10ms of processing on each segment. The bot would keep trimming connections on the large grid where paths could not be found, meaning the bot would learn to go around the wall after seeing the chunks download. In theory, the bot could literally sprint an entire 10km distance on unknown terrain without pausing or stopping to update more of the path as chunks are downloaded.

In theory, this approach can be done recursively for larger and larger distances without adding any more calculation time. The bot could walk to the world border without stopping or having any startup delay.

This is already covered by the fact that paths are recomputed each time a chunk is loaded. Long distance travel have been working for a while.

In the latest versions of pathfinder, the bot will actively crash when traveling distances over ~100 blocks due to reading unloaded chunks.

Unloaded chunks are considered as air and do not crash the bot. (Tested with a view distance of 3 chunks and timeout of 10000ms) Are you sure you have the latest version and the crash is not coming from your code ?
The timeout can be increased for testing purpose, but for production use, it should never exceed 1 tick or it will give noticeable effects.

Just wrote a small test for it. It seems to crash on some servers but work perfectly fine on others? My localhost server worked as expected, but the public test server reliably crashes the client each time.
So, what causes that issue then?

Try to trace exactly which line gets you that error and whether there's a
null check missing there
On Sat, Aug 1, 2020, 12:59 TheDudeFromCI<EMAIL_ADDRESS>wrote:

Just wrote a small test for it. It seems to crash on some servers but work
perfectly fine on others? My localhost server worked as expected, but the
public test server reliably crashes the client each time.
So, what causes that issue then?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Karang/mineflayer-pathfinder/issues/39#issuecomment-667513588,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437TGQ4TLZEN6TGW2DGTR6PYQ5ANCNFSM4PROZ74A
.

I'm connected on the test server, tried a bunch of versions, cannot reproduce the crash.

Sarica is my bot. Just did it and it froze my terminal.

There it is:
Error: write EPIPE
    at afterWriteDispatched (internal/stream_base_commons.js:154:25)
    at writeGeneric (internal/stream_base_commons.js:145:3)
    at Socket._writeGeneric (net.js:784:11)
    at Socket._write (net.js:796:8)
    at doWrite (_stream_writable.js:403:12)
    at writeOrBuffer (_stream_writable.js:387:5)
    at Socket.Writable.write (_stream_writable.js:318:11)
    at Framer.ondata (/home/thedudefromci/Documents/workspace/prismarine-gameplay/node_modules/readable-stream/lib/_stream_readable.js:681:20)
    at Framer.emit (events.js:310:20)
    at addChunk (/home/thedudefromci/Documents/workspace/prismarine-gameplay/node_modules/readable-stream/lib/_stream_readable.js:298:12) {
  errno: 'EPIPE',
  code: 'EPIPE',
  syscall: 'write'
}

That error means writing after bot disconnected
On Sat, Aug 1, 2020, 13:20 TheDudeFromCI<EMAIL_ADDRESS>wrote:

There it is:
Error: write EPIPE
at afterWriteDispatched (internal/stream_base_commons.js:154:25)
at writeGeneric (internal/stream_base_commons.js:145:3)
at Socket._writeGeneric (net.js:784:11)
at Socket._write (net.js:796:8)
at doWrite (_stream_writable.js:403:12)
at writeOrBuffer (_stream_writable.js:387:5)
at Socket.Writable.write (_stream_writable.js:318:11)
at Framer.ondata (/home/thedudefromci/Documents/workspace/prismarine-gameplay/node_modules/readable-stream/lib/_stream_readable.js:681:20)
at Framer.emit (events.js:310:20)
at addChunk (/home/thedudefromci/Documents/workspace/prismarine-gameplay/node_modules/readable-stream/lib/_stream_readable.js:298:12) {
errno: 'EPIPE',
code: 'EPIPE',
syscall: 'write'
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Karang/mineflayer-pathfinder/issues/39#issuecomment-667516056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437W4SZQWB5ZO7TU5F7LR6P3BFANCNFSM4PROZ74A
.

As you said earlier the issue was coming from prismarine-viewer, I consider this one closed.


Update Swift test case for handling JSON objects

One of the test cases for Swift and Swift 3 allows the action to return a string even though this is not the accepted signature of a Swift action.  We should either:

remove this test
update the epilogue.swift code to fail gracefully if the user uploads an action that returns strings.

Changed merged as part of PR #1325


Import Tags: Importing a CSV file under Windows OS in Chrome fails with invalid file format

Take whatever CSV file and import it in Chrome on a Windows OS (you can use a VM):

In logs we have the following message:

@cabch Customer issue, to be fixed asap 😊

waiting for VM to be created to test fix


Mutate Record Data

Package
filament/filament
Package Version
v3
Laravel Version
v10
Livewire Version
v3
PHP Version
PHP 8.2
Problem description
When using the mutateRecordDataUsing method in EditAction, if the model has a date cast, it is always returned in UTC time zone, even if the Laravel app config time zone is set to something else.
This happened because of using attributesToArray method to get model data which use serializeDate method which use toJSON to return "the ISO-8601 string (ex: 1977-04-22T06:00:00Z) with UTC timezone".
Expected behavior
This is more of an unexpected behavior than a bug, but I think it should return the date in the same time zone as in my app configuration.
Steps to reproduce
Create model with date cast, then use EditAction to edit any record and use mutateRecordDataUsing
Reproduction repository
https://github.com/filamentphp/demo
Relevant log output
No response

The code is not present in the reproduction repository


Remove duplicated import

Purpose

Just removed the duplicated imports.

https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/app/backend/approaches/readretrieveread.py#L5-L9

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test
NA
What to Check
NA
Other Information

Before:
$ flake8 --select=F811
./app/backend/approaches/readretrieveread.py:9:1: F811 redefinition of unused 'AzureOpenAI' from line 5

After:
$ flake8 --select=F811
# No error

thanks for the PR 👍🏻


[Experiment] Allow @apply-ing utility classes that aren't explicitly defined but would be generated

Resolves #150.
This PR introduces a solution to the long-standing problem of wanting to use @apply with classes that don't exist in the same CSS tree.
This issue most commonly comes up when someone is working with Vue and wants to use @apply in the <style> block of a single file Vue component. It seems like basically every Vue project is setup to run PostCSS on every <style> block independently instead of on the final concatenated CSS, which means if you have 100 components, Tailwind is run 100 independent times, and each run is isolated and can't see any of the classes in the other runs.
This PR solves this by always generating all of Tailwind's utilities (including those registered by plugins) and using it as a fallback table for @apply if the class can't be found.
I'm not ready to fully commit to this without getting folks to try it out and report feedback, so this PR only enables this functionality if you add an experiments key to your Tailwind config file:
module.exports = {
  // ...
  experiments: {
    shadowLookup: true
  }
}

Because this is an opt-in experiment, it's going to remain undocumented outside of this PR for now, and I reserve the right to yank it or break it without following semver, so please don't rely on this functionality for production sites right now, just test it out locally and give me your feedback.

I'm trying to get this working with Laravel Mix, but without success. Is any additional setup required outside of adding the shadowLookup flag to the tailwind config?
  // ...
  options: {
    prefix:    '',
    important: false,
    separator: ':',
  },

  experiments: {
    shadowLookup: true,
  },
};

In a Vue component, I have this style block:
<style lang="postcss">
  .card-chart {
    @apply rounded;
    /* ... */
  }
</style>

The generated styles include the unprocessed @apply rounded;.
I'm using Tailwind v0.6.3, and I tried adding the plugins key to the Webpack config. It seems like I should somehow pass the tailwind config to the js method, but it only accepts an input and output. Here's my webpack.mix.js:
// ...

mix
  .webpackConfig({
    plugins: [tailwindcss('./tailwind.js')],
    resolve: {
      modules: [
        path.resolve(__dirname),
        path.resolve('./resources/assets/js'),
        path.resolve('./node_modules'),
      ],
    },
  })
  .js('resources/assets/js/app.js', 'public/js').sourceMaps()
  .postCss('resources/assets/css/main.css', 'public/css', [
    postcssImport(),
    tailwindcss('./tailwind.js'),
  ])
  .sourceMaps()
  .purgeCss();

Before I added the plugins key to the Webpack config, the @apply directive just wasn't processed; after adding, I get an error: TypeError: arguments[i].apply is not a function.

@curtisblackwell The problem in this case is your mix configuration. If you use the postCss function to specify your plugins, they are only applied to that CSS file, not to your Vue style blocks.
To configure those PostCSS plugins for all processed CSS, use the options method instead:
  // ...

  mix
    .webpackConfig({
      plugins: [tailwindcss('./tailwind.js')],
      resolve: {
        modules: [
          path.resolve(__dirname),
          path.resolve('./resources/assets/js'),
          path.resolve('./node_modules'),
        ],
      },
    })
    .js('resources/assets/js/app.js', 'public/js').sourceMaps()
-   .postCss('resources/assets/css/main.css', 'public/css', [
-     postcssImport(),
-     tailwindcss('./tailwind.js'),
-   ])
+   .postCss('resources/assets/css/main.css', 'public/css')
+   .options({
+     postCss: [
+       postcssImport(),
+       tailwindcss('./tailwind.js'),
+     ]
+   })
    .sourceMaps()
    .purgeCss();

That fixed it, thanks!

Is this still an experiment or is it production ready? I assume it is production ready as it is merged but there's no documentation about it so I'm unsure if I should use it or not.

It's on by default for a while now, don't need to configure it.


gthumb, cinnamon.pix: Fix build with exiv2 0.28

Description of changes
Tested building with exiv2 0.28
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build gthumb cinnamon.pix

Will also backport a fix for https://github.com/NixOS/nixpkgs/commit/bdf1a96570808dc9e11cfbb1ffa5b8a7ff001e2d shortly.


Where to find changelog ?

In the config file we have a mention of the changelog.

Read the changelog before changing this value

Where actually do I find that changelog ?
Let's say I wanted to upgrade nix from 2.3.6 to 2.3.7 and therefor use another nixpkgs channel.
Is this foreseen or not yet ?

Oh thanks for the heads up. Indeed we do not have any Changelog yet. We should definitely create one, so please keep this issue open as long as it is missing.
The stateVersion behaves similarly to these in NixOS and Home Manager, they reflect the version of state as NixOS version number. Currently this flag is not used anywhere and only the values 19.09 and 20.03 are allowed. We will add 20.09 and separate channel for it as soon as NixOS 20.09 is released.

This is for nix-on-droid defaults, and I don't think anything depends on it yet. We'll use it in 20.09 to flip useUserPackages to true (#65), nothing else. Feel free to proceed with your plans, this won't interfere.

Changelog is now published at https://github.com/t184256/nix-on-droid/blob/master/CHANGELOG.md

Changelog is now published at https://github.com/t184256/nix-on-droid/blob/master/CHANGELOG.md


App crashing on opening the MessageCenterActivity

MessageCenterActivity}: java.lang.IllegalStateException: This Activity already has an action bar supplied by the window decor. Do not request Window.FEATURE_SUPPORT_ACTION_BAR and set windowActionBar to false in your theme to use a Toolbar instead.
P.S: I migrated from 5.8.3 to 6.1.0 and My message center is crashing now.

Hi @rohitgarg29 ,
Thanks for bringing this to our attention.
I think what's happening is, the Material Theme of our Message Center clashes with the theme of your app.
I did find a couple of style items that could help with this.
You can try adding these to your app's theme
<item name="windowActionBar">false</item>
<item name="windowNoTitle">true</item>

Or if you'd only like these items to apply to Apptentive interactions, then put them within an ApptentiveThemeOverride theme like below
<style name="ApptentiveThemeOverride">
    <item name="windowActionBar">false</item>
    <item name="windowNoTitle">true</item>
</style>

We'll explore how we can add this solution to our SDK.
Let me know if this helps and thanks again :)

I have already tried the first part, it was not working but Thanks for the 2nd one. It worked for me. Now I have to just match the Survey and MessageCenter themes to my app's theme. Thanks for quick response.


Add patch ability to update paypal order

Based on https://github.com/paypal/Checkout-Ruby-SDK/blob/685b0637404f3f38cfb5234d294293c294f175de/lib/orders/orders_patch_request.rb we are able to use PATCH to update Paypal Order information

Thanks! Can you please describe the flow that requires this new endpoint?

@kennyadsl  -- on our site, we use a single page checkout with PayPal. Because we don't have address at the time of checkout, and we have the delivery step removed from checkout, we found this messed the flow up quite a bit.
The solution was to manually force an update on the order after we receive back the address and can update tax accordingly. At least that was my understanding of the problem @jtapia created the solution.
In general it was helpful to be able to patch the order how we needed based on a customized checkout flow. The gem seems to skip tax calculations with the delivery step removed.

@jtapia @jakemumu thanks, that makes sense. Is there any way to add some tests for this new endpoint and behavior?

@jtapia @jakemumu I'm closing this, the new approach is to always install frontend related stuff in the target application with the generator instead of providing them through the engine and then resort to monkey patching. We're about to release one last version supporting solidus_frontend and then we'll switch to the new mode and only support solidus_starter_frontend.


Update sentry to new version that supports Laravel 5.3 <

Fixes composer error on installs that are October Build 420 =<
Fixes #2

Thanks @CptMeatball


Display transformer warning in datasets without a schema

Describe the bug
When data is uploaded without a schema defined, the transformer from run -> dataset does not run as there is no schema. At the moment this information is only visible in the run transformation log;

It would improve UX if this message was included in the "No Schema" warning displayed in the datasets view to explain empty datasets. At present, it is not clear to users why a dataset has not been produced from a test upload;

On Hold due to https://github.com/Hyperfoil/Horreum/discussions/1603


const eql = @import("std").mem.eql;

In chapter 2 for example, the following is required:
const eql = @import("std").mem.eql;
This line comes from chapter 1. I think it is good to repeat this import atleast once on chapter 2 to avoid that people have to backtrack every page in order to get something working.

closed in https://github.com/Sobeston/ziglearn/commit/5b4d2ff2588bc7c0019d924db01d8a5f274304ef


Add VE information (pre commits) as an argument to prepare check state

Protocol Change Proposal
Summary
Very simple fix. I found myself using Vote Extensions for the block being committed in prepare check state (in ABCI++). This is done in my application to speed up a process. I'm implementing the changes locally to do so on my branch but I was wondering if other people need this. Unless i'm missing something, if prepare check state passes, then the vote extensions in the precommits will be the same as the ones that we can query when we move on to the next block. Unless I'm missing something 🙊.
Problem Definition

Don't think so
Proposal

The implementation is very simple. I have implemented it on my local fork. Vote extensions are already available in the state argument of the ApplyBlock function of the BlockExecutor. We would simple need to pass it to the Commit() function instead of passing an empty context (or can pass it as an additional parameter).

Sorry, I didn't understand your proposal. https://docs.cometbft.com/v0.38/spec/abci/abci++_methods#prepareproposal already contains local_last_commit with VE (vote extensions). Same as ProcessProposal and FinalizeBlock. https://github.com/cometbft/cometbft/issues/1957 Commit will likely  be removed in the future.


cmd/go: go run produces indirect dependencies in go.mod

What version of Go are you using (go version)?
Latest go devel: go version devel +d278f09333 Thu Jul 19 05:40:37 2018 +0000 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What did you do?
cd `mktemp -d`
curl -sS https://swtch.com/hello.go >hello.go
go mod -init -module=example.com/test
go run hello.go
cat go.mod

What did you expect to see?
go.mod
module example.com/test

require rsc.io/quote v1.5.2

What did you see instead?
module example.com/test

require rsc.io/quote v1.5.2 // indirect

It's OK to see // indirect if we use go get rsc.io/quote but it's a little bit strange to see this artifact after go run.
I believe go run should work exactly like go build and resolve the imports with go mod -sync implicitly.

I believe go run should work exactly like go build and resolve the imports with go mod -sync implicitly.

Note that go build does not do the same thing as go mod -sync: it will add modules as needed (because that can be done locally), but won't remove them (because that requires a broader analysis of transitive imports).

Oh, sure, I forgot about this difference :)
My point is it's better for go run to behave like go build as everyone assume it.

go run allows you to run files that are not actually part of the package in normal use: for example, consider src/cmd/go/testdata/addmod.go:
https://github.com/golang/go/blob/c814ac44c0571f844718f07aa52afa47e37fb1ed/src/cmd/go/testdata/addmod.go#L5
It seems reasonable to update the go.mod file with whatever you needed to actually build those files, but they really are “indirect”, in the sense that they are not included by any possible build that imports packages from your module. If you happened to run a file that is also part of a package, go mod -sync should remove the // indirect comment. (If that doesn't happen today, please reopen.)

Perfectly makes sense, thank you!


Integrating Schematron rules for references

eLife is implementing a set of Schematron rules to validate the content of references. We would like to integrate these into the Texture reference tool to ensure that the reference list and in-text citations match our style requirements.
https://github.com/elifesciences/reference-schematron
We have set up an API service to run XML files against the Schematron at two stages in the production process - just after the article is typeset and just before publication - using slightly different sets of rules (the first will generate queries to the authors to request missing details).

This is an important functionality but think we should wait until we have the user interface + data model in place generally.
The approach we want to take is to display an issue pane, where all problematic places are shown. And by clicking on them you get taken to the corresponding form field. We can have a relatively simple rule set evaluated in Javascript to accomplish that. We need to investigate how hard it is to compile schematron rules and evaluate them in Javascript. Ideally we can use a light-weight toolchain (ideally all Javascript) so we don't need to connect to a service to perform rule checking.

I think we should not integrate schematron into the editor at this point. You can run the checks after editing in a separate process. Let's see how far we get with live-validation inside Texture and then consider plugging in more complex schematron rules or translating them to rules we can evaluate in the browser.


perl: don't use libxcrypt on FreeBSD

Description of changes

Tested by building pkgsCross.x86_64-freebsd.perl from x86_64-linux.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is there a reason we don't just do enableCrypt ? !stdenv.isFreeBSD?

@ofborg build pkgsCross.x86_64-freebsd.perl

assert (enableCrypt -> (stdenv.isFreeBSD || libxcrypt != null)); above too. Should we knock out libxcrypt across the board with FreeBSD?

Should we knock out libxcrypt across the board with FreeBSD?

I thought about that, but I don't think we should.  Given that libxcrypt is in FreeBSD Ports, there must be a reason to want it.

Sounds good. I guess we should see why the FreeBSD people do what they do, but for now we are correctly imitating them.


CodeCop warnings

I see that the models don't take the implicit and explicit withs into account:

Pushed a fix for this issue. It will be made available in the next release of mdAL (and its corresponding VS Code extension).


Add GET_CONTENT and INSERT actions to support 3rd party app integration

This branch adds support for 3rd party app integration/automation using
standard "otpauth://" URIs
(https://github.com/google/google-authenticator/wiki/Key-Uri-Format).
The GET_CONTENT intent action will return the current code for an
existing token. The INSERT action will install a new token and return
the current code (and the token secret to allow stateless operation by
the intent sender). Both actions are subject to user confirmation.
These two actions will allow a 3rd party app to alleviate the cubersome
and error prone user process of being prompted for an OTP code,
switching to FreeOTP, memorizing or copying the code to the clipboard,
switch back to the original app, and finally entering the code. The 3rd
party app should appropriately handle the exception cases of FreeOTP not
being installed or the user denying the requested action.

I submitted this back in 2016 as #85. This is the same code, re-based on the current master with a few android pieces brought up to date.


Create daily-quote-generator.md

What does this PR do?
solve issue : #608
The app displays a new inspirational quote each day, providing motivation and positivity to users. The quote updates in real-time with a visually appealing clock and date display.
Related PRs and Issues
See my project -

Live app :  Link
Blog link : Link

Checklist

[x] I have read read the Contribution Guide
[x] If the PR changes or adds functionality, I have updated the relevant documentation

@quest-bot loot #608

@NathanTarbert , please review my pr.

Excellent job @Vaishnavi-Raykar!

@NathanTarbert is this issue still because I am also working on this ?

@nitesh2920, yes it is

@quest-bot loot

@quest-bot loot #608


Enhanced view to work on atoms and with obserable lens.

This required update to latest Bacon Atom.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0a6fa85). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   97.63%
=========================================
  Files             ?        1
  Lines             ?      844
  Branches          ?        0
=========================================
  Hits              ?      824
  Misses            ?       20
  Partials          ?        0

Continue to review full report at Codecov.

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


Sendability of Globals is not checked in Task's closure

Describe the bug
No warning is emitted when a closure passed to a Task references a mutable global variable.
Steps To Reproduce
class Cat {
    var name = "Tom"
}

class Globals {
    var cat = Cat()
}

let glob = Globals()

func one () {
    Task {glob.cat.name="Max"} // Expected Warning about some nonSendable moving into a different concurrency domain
}

Expected behavior
I excpected a warning along the lines of

Capture of 'glob' with non-sendable type 'Globals' in a @Sendable closure

No such warning is emitted.
Environment

OS: MacOS 12.6 (Intel), Xcode 14.0.1
Xcode Version/Tag/Branch: 14.0.1

Additional context
Normally, with -warn-concurrency enabled, Swift/Xcode warns about non-sendables crossing concurrency domains.

This is fixed by SE-0412, which is enabled under -strict-concurrency=complete in Swift 5.10.


Add Spec and Talent Summary to Player Tooltips

We'll only be able to do this for players in inspect range, but still useful information to have.
And since we can pull the level and # of talents... we can also put in some sort of "UNSPENT TALENT POINTS" warning if someone is missing talents.

Ideally this will just work for people in-range when you mouse-over them.
If this only works when you click on someone and then mouseover them after that... let's push it to another release. It's not that important.

Replaced by #208


Fixed Single User Registration

Now only a single person can register as the "owner" of the blog.

Found an issue:
Repro:

Log in.
Go to localhost:#####/Account/Register by manually typing it into search bar.

Expected:

Redirects you back to homepage
Does not allow you to register again

Actual:


Create About page

when someone clicked the about button in the home page, then About page will open. I want to add this feature under JWOC. Please assign me this issue.

Hey @mrbhatt2348 , I would like to work on this issue under JWOC. Can you please assign it to me?


Cannot import project with conectors

Description:

Create an Integration project with Google firebase. Add connector exporter and composite application projects as well. Import the connector and use its operations in an API.

Remove .tmp and .metadata folders from repo. This step is needed as there is a lot of files not relevant to the source I want to pack and send over.

Close the studio and start it pointing to a different workplace.

Import the earlier projects as below.

You will see in API there are errors. When clicked on it, all the configuration is lost!!

Affected Product Version:
7.0.2
OS, DB, other environment details and versions:

This happens due to connector not available in the workspace when project which uses the connector is imported. Adding the connector before importing this will solve the issue. Possible duplicate - https://github.com/wso2/devstudio-tooling-ei/issues/897


Create Blog “2022-06-13t04-33-25-842z-vb-first-blog-article”

Automatically generated by Netlify CMS

👷 Deploy Preview for silver-mandazi-ba8cea processing.

Name
Link

🔨 Latest commit
56c183cff1cc888e9664ac8509d15fdb011b2632

🔍 Latest deploy log
https://app.netlify.com/sites/silver-mandazi-ba8cea/deploys/62a6be7384ea19000898d6e0


Account: Saved Keypairs

Preview is available here:http://laboratory-pr1138.previews.kube001.services.stellar-ops.com/

@quietbits On the Save Keypair page, should we follow the same pattern as on the Create Account Keypair page  and hide the secret key as ********. Wdyt?

@quietbits On the Save Keypair page, should we follow the same pattern as on the Create Account Keypair page and hide the secret key as ********. What do you think?

@janewang , yes, we can mask the secret key. :+1:

Separately, when my mouse hovers over the public key, my cursor turns to this 🚫 . I think it should be the same as the Create Account Keypair page.

The input fields are disabled, that's why you see the 🚫 icon on hover. We can change that to read-only, but the design has the disabled style. It's an easy update.

The input fields are disabled, that's why you see the 🚫 icon on hover. We can change that to read-only, but the design has the disabled style. It's an easy update.

I think the design should be consistent in saved keypairs and in create keypairs. Thank you for the update!

Preview is available here:http://laboratory-pr1138.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr1138.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr1138.previews.kube001.services.stellar-ops.com/

I think we should reset the generate keypair inputs when switching from mainnet to futurenet. its public key input stays intact without private key input.
https://github.com/user-attachments/assets/c54029ef-2c8a-44f8-bda6-be4106133778

Fund Account and Saved Keypairs styling on mainnet should match

I think we should reset the generate keypair inputs when switching from mainnet to futurenet. its public key input stays intact without private key input.
mainnet-to-futurenet.mov

Good idea, we should reset the keypair when the network changes. Issue created.

Preview is available here:http://laboratory-pr1138.previews.kube001.services.stellar-ops.com/


Fixes map2 and map3 while improving error messages

Fixes #32. Fixes #22. Closes #31.
This has a fairly sever refactor of the error handling, but the outcome is that map2 and friends don't loose errors, and oneOf has easier to understand error messages (which are also more explicitely represented in the types).

Is this an alternate take on https://github.com/BrianHicks/elm-csv/pull/31, similar to how you opened two PRs with optional field approaches?

Sort of. It incorporates most of the approach of #31, but since this also changes the error type, the 2 PRs are not mutually compatible.
The main differences on error handling side is:

oneOf errors are made more explicit in that we make it clear to the user that they only need to fix one of the errors, not necessarily all the errors (which neither the existing code nor #31 do)
Your comment about sorting by row is incorporated (we first sort by type to enable the grouping calculation, but then the grouped errors are sorted by starting row of the range).
This also includes some tests, but these could be easily back ported to #31.

Hi @BrianHicks. Sorry I dropped the ball on these PRs as I had them working in our vendored version and I completely forget these existed. I think this one is now good to go?

Thanks so much for taking care of this issue. It's been an annoyance for a while and I'm glad it's gonna get better. ❤


Web3 Data Science Class Proposal

What is it?
Currently pitching it to some CMU faculty

Finished that today via email


Frequent 500 Errors

Hi,
I've been using this API for a few days and I've noticed that every day more than a few times the vercel app crashed and herokuapp app was not running.

https://lost-ark-api.vercel.app/
And with herokuapp, if a 500 error occurs, API responds with plaintext "Internal Server Error".

Just making sure, you know this is happening since I haven't seen any issue relating to this.

https://lost-ark-api.vercel.app/ working for me fine but bother vercel and heroku are free options. I have a vps but i refuse to use it to host this api as it will absorb all the bandwidth im allowed. only other options is if i change api to pay option or get donated a vps

Yes, it is working fine right now. However, there could be some problem within the code that is causing the 500 errors, I suppose.

Yes, it is working fine right now. However, there could be some problem within the code that is causing the 500 errors, I suppose.

nothing wrong with the code as i run it on my own vps server with 0 issues, likely the services


no :notice on translation_class.validates

When defining translation_class.validates :column, presence: true
And in admin panel, if leaving field blank Save button does not work, and no notice.
using
gem 'rails_admin'
gem 'rails_admin_globalize_field'

Not enough info.


[shuffle] annotate API call arguments and return types

Created interface definition for Transaction, Event, SigningMessage and LedgerInfo
Changed client methods to accept type arguments and returns type
Switched to call get account for account core resource instead of looking up DiemAccount resource
Renamed devapi functions postTransactionBcs, postTransactionSigningMessage and postTransactionJson to use same names defined by API/client

/land


[ASK] Is it possible to write and build android, window, macOS, web like Flutter?

in Flutter, you can build multi-platform apps with the same code and the same configuration.
I looked up KMP getting started. But It looks like it doesn't work that way. But more look like using Jetpack compose in Window or Android or macOS. And can't build for other platforms. Is that right?
If there's a way or additional work for each platforms but can work with one project, How can I achieve that?

You may use Compose Multiplatform to build an app to run on android and dekstop platofrms: window, macOS, linux. For those targets, you can share the most of the UI code.
Compose Multiplatform also provides "Compose for Web", which enables us to develop web apps using the same Composable approach, but the UI components API is different (it mimics HTML). This UI code is web-only and it can't be shared with desktop and android.

Other than that, Compose Multiplatform has Experimental!!! targets. For example: "Compose for Web (Canvas)", or MacOS, IOS.  The UI code for those can be reused between all targets.
Here is an example of such an app: https://github.com/JetBrains/compose-jb/tree/master/experimental/examples/chat-mpp

Feel free to reopen this question if you want to follow up.
Closing this issue for now.

Can build for windows and linux with kotlin/native?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Posixpath error when running unsloth on T4 server

File "/home/ubuntu/anaconda3/envs/chatbot/lib/python3.10/site-packages/starlette/routing.py", line 732, in lifespan
async with self.lifespan_context(app) as maybe_state:
File "/home/ubuntu/anaconda3/envs/chatbot/lib/python3.10/site-packages/starlette/routing.py", line 608, in aenter
await self._router.startup()
File "/home/ubuntu/anaconda3/envs/chatbot/lib/python3.10/site-packages/starlette/routing.py", line 711, in startup
handler()
File "/home/ubuntu/lynkgrid_chatbot_backend_python/api/router/websocket.py", line 28, in load_model
model, tokenizer = phi3()
File "/home/ubuntu/lynkgrid_chatbot_backend_python/src/model.py", line 59, in phi3
model, tokenizer = FastLanguageModel.from_pretrained(
File "/home/ubuntu/anaconda3/envs/chatbot/lib/python3.10/site-packages/unsloth/models/loader.py", line 146, in from_pretrained
model_name = _get_model_name(model_name, load_in_4bit)
File "/home/ubuntu/anaconda3/envs/chatbot/lib/python3.10/site-packages/unsloth/models/loader.py", line 95, in _get_model_name
new_model_name = __get_model_name(
File "/home/ubuntu/anaconda3/envs/chatbot/lib/python3.10/site-packages/unsloth/models/loader.py", line 64, in __get_model_name
elif load_in_4bit and SUPPORTS_FOURBIT and model_name.lower() in FLOAT_TO_INT_MAPPER:
AttributeError: 'PosixPath' object has no attribute 'lower'. Did you mean: 'owner'?

I added a str() guard to force it to be a string


Semver support

Hello, have been a happy user of this package for 6 months or so however the latest commits were not backwards compatible.
Any chance of tagging a release and implementing semver?

Hello, thank you for your feedback.
Release/Tag: https://github.com/chriskonnertz/open-graph/releases/tag/v1.0.0
I will stick to semantiv version from now on.

thanks much appreciated!


not Supporting in typescript

found there is no package available for typescript
npm install @types/react-native-cookies

you need to add a cookieManager.d.ts file to your project
declare module "react-native-cookies" {
    function clearAll(useWebKit = false): void
    function get(url: string, useWebKit = false): string
    function set(cookie: string, useWebKit = false): void

    interface CookieManager {
        clearAll(useWebKit = false): void
        get(url: string, useWebKit = false): string
        set(cookie: string, useWebKit = false): void
    }
}

I have forked the repo here: https://github.com/safaiyeh/react-native-cookie-store
We can create issues and PRs there to continue the development of the project.


On-Chip calibration does not update calibration table - values do not differ from 'gold' factory values.

Steps to reproduce with a d415 running on ubuntu 18

reset camera to gold factory calibration

CustomRW -g

save calibration table
CustomRW -r -f gold.xml

run rs-depth-quality > more > on chip calibration > intrinsics|extrinsics > white wall > apply new

dump new calibration table CustomRW -r -f new.xml

observe that new.xml and gold.xml are identical

Hi @Chandler  The -r option allows you to read the calibration parameters currently stored in a device, and save them as a backup to an .xml file.  It is not saving the calibration parameters into the device.  To save parameters to the device, -w is used instead of -r.
My interpretation of the procedure that you described is that you are not using the Dynamic Calibrator to perform a re-calibration.  Instead, you are exporting the calibration settings as they currently are into an xml file.
Then you perform an On-Chip calibration, and use CustomRW to export the current calibration settings again to a new filename.  When you compare the two files their calibration details are identical, suggesting that either the On-Chip calibration process did nothing or that the changes were not burned to the camera when the Apply New button was clicked.  Is my interpretation correct, please?

@MartyG-RealSense you are correct, using rs-depth-quality and apply new does not burn new values into the calibration table. I tested this on a d415 and d455. I'd be curious to know if you can reproduce this.
I cannot try with realsense-viewer because the on-chip calibration routine freezes when I use that tool.

update! I was able to get calibration to "do something" e.g. produce a slight calibration change via realsense-viewer
Steps:
realsense-viewer > more > calibration data > factory reset & save as gold.json
realsense-viewer > more > on chip calibration > extrinsics & medium > apply
realsense-viewer > more > calibration data > factory reset & save as new.json
A slight difference is found, indicating that calibration had an effect.
$ diff gold.json new.json

I'm not sure why my earlier sequence doesn't work, perhaps because I was using white wall which I now know is not the recommended calibration mode.

I think the issue may have been that I was using realsense viewer 2.34 and in the follow up test I upgraded to 2.38

It may indeed have been due to SDK 2.34, as I recall that this version had problems with the On-Chip Calibration function.
https://github.com/IntelRealSense/librealsense/issues/6231
Great to hear that you resolved your calibration problem by changing versions!


Account, Product, Shop should be in enabled(or disabled) state.

In order not to delete the Account, Product, Shop directly, we should put on "state" making Account, Product, Shop looks like being deleted.

帳號需要多一個權限的欄位，以區別一般跟超級帳號

或是再開一個超級帳號的表

#49


Change password for admin user

Is there a way to change the admin-password?

i think it depends on the way you started this project - if you were using docker-compose, you can set the admin pw inside the .yaml file


fixed typo

I found a typo in onnxconverter_common/perfstats.py.

right : onnxconverter_common
wrong : onnxconvert_common

So, I fixed it.

I corrected only the typo. But, I don't know why CI Job failed.


Fix sf4 compatibility

BC break:

When a callback is defined as ["Valid\FQCN", "method"], the bundle will replace the static call to Valid\FQCN by a call to the service named Valid\FQCN if it exists in the container (and is public). If you want to do a static call, please use a FQCN that is not registered in the container. With the new access by FQCN container, I have no way to detect if you want to go with static or not. If anyone has an idea on how to deal with it I would be happy to hear it.
Parameters sm.callback_factory.class, sm.twig_extension.class and sm.callback.cascade_transition.class have been removed.

If some of you guys can test it with both sf3 & sf4 it would be great. Thanks!

I believe Sylius 1.2 needs this.


CDB_Math_Mode(torque_category) fails on embeds

Today a torque cat map that worked correctly on the editor wasn't displaying any points on embeds and public pages. The error returned by windshaft was:
"TorqueRenderer: column reference "torque_category" is ambiguous"

For the record, there wasn't a column called torque_category on the table.
Once the -torque-aggregation-function was changed to count(cartodb_id) it went back to rendering points publicly, but obviously that's not the solution to the problem
@rochoa @xavijam @javisantana

https://github.com/CartoDB/cartodb/blob/master/lib/assets/javascripts/cartodb/models/carto/torque_cat.js#L32

the problem is torque wrapping a wrapped query:
select *, (CASE WHEN "hour" = '04:00' THEN 1 WHEN "hour" = '21:00' THEN 2 WHEN "hour" = '01:00' THEN 3 WHEN "hour" = '03:00' THEN 4 WHEN "hour" = '00:00' THEN 5 WHEN "hour" = '02:00' THEN 6 WHEN "hour" = '22:00' THEN 7 WHEN "hour" = '23:00' THEN 8 WHEN "hour" = '20:00' THEN 9 ELSE 10 END) as torque_category FROM (select *, (CASE WHEN "hour" = '04:00' THEN 1 WHEN "hour" = '21:00' THEN 2 WHEN "hour" = '01:00' THEN 3 WHEN "hour" = '03:00' THEN 4 WHEN "hour" = '00:00' THEN 5 WHEN "hour" = '02:00' THEN 6 WHEN "hour" = '22:00' THEN 7 WHEN "hour" = '23:00' THEN 8 WHEN "hour" = '20:00' THEN 9 ELSE 10 END) as torque_category FROM (select * from parts7a) _cdb_wrap) _cdb_wrap

this is backend, the query is being wrapped twice

Being hotfixed with changeset 3cb74e11c4d49bed2d3f1913421ca1b3e318fe4b
Doesn't fixes the source of multiple calls but at least doesn't modifies state of layer and should avoid the double wrapping.

ok, hotfix worked, I had to perform a "vizjson touch" to regenerate it but now the wrapped query is ok for the failing user


ci: fix uffizzi

I think the uffizzi-preview.yml file runs from main meaning we need to merge this to test it 🤮
The zip file content is now nested due to the changes in the previous step, so this change just flattens the zip contents which might/should fix things

Ah well! I tested on MacOS and it didnt ask so...maybe just merge and see?

Ah well! I tested on MacOS and it didnt ask so...maybe just merge and see?

Sure, haha, what's the downside? :)


Validators are not registered in the storage

The list of validators in the storage is empty. It seems that it is not properly connected to the events.
The validator candidates endpoint always returns an empty list.

Validators is returning now the current list. Further improvements will be done after discussion in #735


Firefox noncompliant with GDPR

Describe the bug
Firefox (Thunderbird as well) enables GDPR incompatible telemetry. Since, it's not reasonable to build firefox multiple times, just disabling it by default is the legally safe option.
See
https://techcrunch.com/2024/09/25/mozilla-hit-with-privacy-complaint-in-eu-over-firefox-tracking-tech/
Steps To Reproduce
I didn't see any issue mentioning Firefox and gdpr, which makes it incredibly unlikely for the maintainer to have corrected this already for possibly an unreleased version of Firefox.
I also didn't see any comments in the source code mentioning GDPR, suggesting it is unmanaged.
Expected behavior
Don't show any nagging screen (only wasting the time of people everywhere who just want to use Firefox) on startup, but just disable telemetry. I'd patch out the entire feature, but that might be controversial. If that's bad for branding, just call it Iceweasel or NixFox.
Notify maintainers
@lovesegfault @hexa

Correcting ping: @mweinelt

Feel free to take this upstream.

Besides this PPA thing, the official firefox contains hopeless amounts user-hostile garbage ("experiments", ads in the homepage, google safebrowsing, proprietary add-ons, more telemetry etc.)
If you find any of these things annoying, you should probably use librewolf (already packaged).

It's unclear what you want to take upstream, since there are multiple independent issues.
One of them is how the "feature" should work (I think, as long as Firefox is not bug free there is no reason for user data, because they can still do work without user data; their false argument is that they need user data to make Firefox better).
Another is that since computers are used by multiple people, it would be impossible to collect consent from everyone, which technically voids the concept of asking for permission or agreeing to anything.
Subconclusion I, distributing any software for which no contract is signed of the form I will never allow anyone to use this account besides myself for every application collecting telemetry, is incompatible with GDPR.
Principle: Nixpkgs should not make illegal behavior easy, because this is incompatible with legislation in The Netherlands, where the foundation is located.
Subconclusion II, Firefox (and other telemetry gathering software) should not be distributed.
The technical question then becomes whether the installation is just modified at run-time (if this is even possible) or whether because of branding issues something with a different name should be distributed like Iceweasel.
PS I understand this message might be a shock to many organizations wishing to use telemetry
Conclusion, the legally safest option is disabling telemetry in the code by patching it out and removing the branding. Every other solution would require consent from Mozilla and/or complex legal issues potentially exposing the foundation to many long legal conflicts.
Taking it upstream would mean asking people without a working understanding of GDPR (@joepie91 in one of the threads got some weak commitment, but I don't think it's enough in general as explained above) about something we (at least I do) to already be noncompliant. I don't have any questions for them; nixpkgs could collaborate with other distributions to agree to follow those, but I generally don't ask others when I already know what to do, which I believe I have more than adequately explained.
(The technical solution selected eventually is not of great interest to me personally. )
In a broader sense, the real legal fun (read: nightmare for anyone with telemetry and without a wall of legalese) begins when applying this to closed source products with telemetry. I hadn't considered this before, but if e.g. Chrome currently even collects one timestamp "to improve the product" they are probably breaching GDPR.

I second mweinelt. Nixpkgs is not in the habit of modifying package defaults for users preferences. This is an upstream issue. As for legality, Nixpkgs is not legally responsible for the GDPR compliance of the packages it provides. We are not storing any data packages may collect.

@justinlovinger First if all this is not a democracy.
Secondly, you are assuming that if the foundation doesn't collect the data, it's not doing anything wrong. There's no evidence of that assertion being true.
Regardless, this is an issue that should be handled by the foundation, not by a maintainer.

@joepie91, I am not saying such NixOS options could not be useful, but I argued that the "show it once" has no valid implementation, because you can't assume a single user account is used by just one user. Yes, I understand that everyone in tech would think that's "not how you so it", but there's no legal requirement to have multiple user accounts on a computer.
So, while you might consider it to be a reasonable compromise the fact of the matter is that your legal opinion is clouded by too much technical experience about how things should be in some technological utopia.
If the logical conclusion (which I might add was not disputed) is applied, the problem is solved in nixpkgs for the Firefox package or some Iceweasel variant until upstream breaks it. I already suggested the possibility of collaboration with other distributions. As such, your way of portraying me, is dishonest.
What you are doing is expanding scope for an issue that's already complicated enough as it is.
So, while you are claiming without proof that it's not productive my approach is goal directed; a single patch would turn it off for everyone and it would be solved for the next months. To automate it, I suspect even a LLM can modify the code given the right entry point to produce a patch to remove the telemetry. I also think it's not productive to discuss people being productive or not, especially given such a weak support for your position.
I mentioned your name, because I thought it was relevant, but you don't seem to understand your judgement has been clouded by bias. I did imply that it's in principle a good thing that you engaged with them, but where you go wrong is that you speak as if your opinion holds legal value. If you do have an opinion consistent with the law, feel free to share it, but right now you are just being used as a tool by a large corporation despite thinking you are doing good.
Mozilla will do whatever they can get away with and you basically give them an excuse to break the law and tell a judge in a decade "we thought it was OK and there was a discussion with users and even joepie, who we listened to and even removed the dark patterns. Aren't we good boys?".
Let's say there's a shared NixOS installation in a retirement home and someone wants to look up a recipe for cookies using a browser. Let's further assume they have had some brain injury and can't even remember a password anymore. Do you think such people would actively consent to telemetry or go to the settings every single time to opt-out? Of course not.
Telemetry has been the Wild West, but the party is over.
Finally, it's not much of a fight, since nobody even challenged my line of reasoning.

Well, if you insist on writing a long post of insults and accusations instead of taking my advice (as someone who is actually familiar with the processes here), then there's nothing left for me to do here.
I've told you how to get this problem solved effectively. If you choose to ignore that, that's your call, but then the consequences are also yours.

Enough, y'all.


Add documentation for single variable aliases

Right now Spin, Spins, Binary, Binaries, Integer and Integers are not included in the docs.

And now also https://github.com/dwavesystems/dimod/pull/1074


Replace interface{} with any

Result of running perl -p -i -e 's#interface\{\}#any#g' **/* and make fmt.

It seems gofmt can do this as well with rewrite rules, I will try that as well, if it works, make fmt will automatically fix these.

I don't think I'll chase this further to autofix via make fmt because it would mean we have to run the two formatters back to back, something which I'm absolutely not fond of doing.

LGTM as soon as the CI passes. Unfortunately, it is potentially not as easy as that (but the CI will show that): https://stackoverflow.com/questions/71628061/difference-between-any-interface-as-constraint-vs-type-of-argument

I guess the difference should hopefully not matter, but there is a certain risk of runtime error, so I'll also try to review the changes for any usage inside generic functions.

I will do the same on the 1.20 branch, just to make backports easier.


Move runOnExisting parameter from Create to Items

This is the change I made locally to get app instance creation to work for today to work around #7.

This will be fixed in the Seq server API, so this code change is not needed.


Add precommit hook

About this change - What it does
Introduces husky and lint-staged to run scripts on pre-commit if there are changes in coral.
Resolves: #112
Why this way

prepare script in package.json is needed in this form ('cd .. && husky install coral/.husky') because .git folder is not on the same level as the package.json (see documentation)
adds lint-staged page to enable us to control which scripts have to run dependent on where a file changes:

right now we only need to run the linting pre-commit hooks on changes in TypeScript and TSX files, since we have no linting for markdown etc.

in pre-commit is a check to see if the staged files are in the coral directory, so we don't run tests when something outside coral changes.

Is a general personal note: I would have not introduced lint-staged as a depedency as I think similar behaviour can be achieved with bash tooling.

Is a general personal note: I would have not introduced lint-staged as a depedency as I think similar behaviour can be achieved with bash tooling.

Adding here what we decided about this in a call to be transparent:

we will leave lint-staged for now, because it improves readability to enable others to get an overview about the processes more quick when compared to bash scripts
we'll come back to the topic pre-commit-hooks later and check out pre-commit, which looks like a promising tool to only have one place where we define things while being very readable 💃


draft: replace bpf_main function in wasm module with main

Description
It's related to issue#116
We need replace the host api in wasm-runtime that execute bpf_main function with wasm_application_execute_main.

Some records:
There are some problems when trying to use wasm_application_execute_main instead of ewasm_program::call_wasm_init:
Firstly, in the previous approach, some settings of ewasm were required to execute the bpf program in wasm, for example:
int
create_bpf(wasm_exec_env_t exec_env, char *ebpf_json, int str_len)
{
    ewasm_program *program =
        (ewasm_program *)wasm_runtime_get_user_data(exec_env);
    assert("program is null" && program != nullptr);
    return program->create_bpf_program(ebpf_json);
}

The above code requires a properly set ewasm_program, which can be obtained through the user_data field in exec_env.
However, when using wasm_application_execute_main, it creates a new execution environment internally, causing the user_data field in exec_env to be NULL, resulting in program being NULL in the code segment above.
Secondly, although wasm_application_execute_main has three parameters:

module_inst – the WASM module instance
argc – the number of arguments
argv – the arguments array, if the main function has return value, (int*)argv stores the return value of the called main function after this function returns.

However, argc and argv are set to 0 and NULL respectively inside wasm_application_execute_main, so there is no way to pass ewasm_program to create_bpf through argv.
Frustratingly, I do not have an appropriate solution to use wasm_application_execute_main to achieve this task.

You may refer to how we solve this problem in https://github.com/eunomia-bpf/wasm-bpf
Thanks for your working! We would need to use the wasi specify APIs in wamr for main function entry.


Add randomizers for all message types sent to NOC

This is a feature request for the backend.

[x] Gateway status
[x] Router uplink
[x] Router downlink
[ ] Router status
[x] Broker uplink
[x] Broker downlink
[ ] Broker status
[ ] Handler status
[ ] Network Server status

While at it, also move to a separate package to reduce the dependencies of (for example) clients.

Moved to https://github.com/TheThingsNetwork/api/issues/2


upgrading google compute, storage and azure compute libs to latest major versions

Pull Request Test Coverage Report for Build 4019

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.341%

Totals

Change from base Build 3981:
0.0%

Covered Lines:
9238

Relevant Lines:
9993

💛  - Coveralls


Fix bash command for Windows

Notion ticket link

Ticket Name

Implementation description

Windows needs double slashes on this command to work appropriately. Could you double check that this still works on MacOS?

Notes

Checklist

[ ] My PR name is descriptive, is in imperative tense and starts with one of the following: [Feature],[Improvement] or [Fix],
[ ] I have run the appropriate linter(s)
[ ] I have requested a review from the RCD team on GitHub, or specific people who are associated with this ticket

Oh interesting...single slashes have always worked for me 🤔
@leogjhuang could you please confirm if this is an issue on mac? Alternatively I think simply using bash might also work

Changed to just use bash


Moved BaseStep to Steps

Scope & Purpose
Moved the class BaseStep in BaseStep.h from arangod/Graph/Providers to arangod/Graph/Steps.

[ ] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.9: (Please link PR)
[ ] Backport for 3.8: (Please link PR)
[ ] Backport for 3.7: (Please link PR)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[x] Enterprise PR: #879
[ ] GitHub issue / Jira ticket:
[ ] Design document:

EE PR: https://github.com/arangodb/enterprise/pull/879


React Native prop types validation

React fails to validate View on GatewayDest as a value of component property.
Failed prop type: Invalid prop `component` supplied to `GatewayDest`.

Code:
import React, {Component} from 'react'
import {View} from 'react-native'
import {GatewayProvider, GatewayDest} from 'react-gateway'

class RootComponent extends Component {

  /* ... */

  render () {
    const RootRoute = createRootRoute(this.state.isAuthorized)
    return this.state.isReady ? (
      <GatewayProvider>
        <View style={{flex: 1}}>
          <RootRoute ref={(el) => (this.rootRoute = el)} />
          <Notifier/>
          <GatewayDest name="inputAccessory" component={View}/>
        </View>
      </GatewayProvider>
    ) : null
  }
}

Same issue here.

Since it's expecting a string or function, this satisfies the prop type:
<GatewayDest name="inputAccessory" component={ props => <View { ...props } /> }/>


[feat] MDR-level as an option for limiting the AI answers

I think we could define the process.env.LIMIT_MDR_LEVEL_RESPONSE = [MDR0, MDR1....] to set the requested level of responses - of course giving the lowest possible value for the demo purposes

examples:
MDR3 (which we really don't want):

MDR0 (which we could want to have):


Rectangle Area Light ported from Type to Property

Fixes #
I confirm I have signed the Contributor License Agreement.

Closing due to new light shape as property PR created


Changes for embedded mode

Following changes have been done:

Start LTS with BookKeeper object
Use Bookkeeper object in ReadRequestChains
Use Bookkeeper object in parallel warmup
Fix Parallel warmup for the case of CachingFS getting used by disabling caching on configuration used in parallel warmup
Fix logging: Fix log levels, show full exceptions whereever available instead of exception message
Recover from loss of connection to master BK in workerBK
Use prefix+suffix cache location if count based locations not found
Add new module 'rubix-prestosql' for prestosql versions

Codecov Report

Merging #338 into master will decrease coverage by 0.32%.
The diff coverage is 46.62%.

@@            Coverage Diff             @@
##           master     #338      +/-   ##
==========================================
- Coverage   50.28%   49.95%   -0.33%
==========================================
  Files          66       70       +4
  Lines        3162     3365     +203
  Branches      350      377      +27
==========================================
+ Hits         1590     1681      +91
- Misses       1484     1582      +98
- Partials       88      102      +14

Impacted Files
Coverage Δ

...com/qubole/rubix/spi/RetryingBookkeeperClient.java
15.15% <0%> (ø)
:arrow_up:

...rc/main/java/com/qubole/rubix/spi/CacheConfig.java
20.94% <0%> (-2.18%)
:arrow_down:

...prestosql/CachingPrestoGoogleHadoopFileSystem.java
0% <0%> (ø)

...om/qubole/rubix/core/NonLocalReadRequestChain.java
0% <0%> (ø)
:arrow_up:

...java/com/qubole/rubix/core/CachingInputStream.java
0% <0%> (ø)
:arrow_up:

...ole/rubix/prestosql/CachingPrestoS3FileSystem.java
0% <0%> (ø)

...qubole/rubix/core/DummyModeCachingInputStream.java
0% <0%> (ø)
:arrow_up:

.../com/qubole/rubix/presto/PrestoClusterManager.java
64.15% <0%> (-1.24%)
:arrow_down:

.../prestosql/CachingPrestoNativeAzureFileSystem.java
0% <0%> (ø)

...va/com/qubole/rubix/core/NonLocalRequestChain.java
0% <0%> (ø)
:arrow_up:

... and 25 more