Dasiy ACE Javascript error

Every time I try to use this product, I get this Javascript error:

And then it finds no errors.
When I upload a different file, I get the same error and the same results. It will not overwrite the previous report unless I close & reopen the application. Same Javascript error.
So this effectively does not work.
Windows 10

Please provide the following details if possible or relevant:

[] the version of Ace impacted by the issue (as returned by the ace -v command).
[] the version of Node used to run Ace (as returned by the node -v command).
[] your operating system and version.
[] if the issue is a bug when running Ace: the error message as produced in the log file (you can enable debug logging with the --verbose option).
[] if the issue is about the HTML report: the browser(s) and version(s) you used.
[] if possible, let us know if you can share a sample input file to help us reproduce the issue.

Hello, would you mind trying the latest build from this link please:
https://github.com/daisy/ace-gui/releases/tag/latest-windows
(the filename should be Ace.by.DAISY.Setup.1.0.2-alpha.1.59.exe or another future increment such as -alpha.1.60, -alpha.1.61 etc.)

Symantec is saying the file isn't safe and "growing evidence that the
file is untrustworthy."
On 3/10/2020 2:51 PM, Daniel Weck wrote:

Hello, would you mind trying the latest build from this link please:
https://github.com/daisy/ace-gui/releases/tag/latest-windows
(the filename should be |Ace.by.DAISY.Setup.1.0.2-alpha.1.59.exe| or
another future increment such as |-alpha.1.60|, |-alpha.1.61| etc.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/daisy/ace-gui/issues/103?email_source=notifications&email_token=AOY4XQF3E3LFWPMXLNKMKYTRG2D4PA5CNFSM4LFFUEW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOMV6PY#issuecomment-597253951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOY4XQHAB2Q4ZJT7BQ2TE4TRG2D4PANCNFSM4LFFUEWQ.

Yes, standard procedure for Windows and Mac OS to report apps that are not signed with recognized certificates from reputable organizations. In this particular case, the latest automated builds of Ace App are not signed at all, so there are additional warnings when the app is installed and launched.

.exe doesn't run.  It says I need an app to install it.  And no, I don't
want to search for an app in the store.
On 3/11/2020 11:04 AM, Daniel Weck wrote:

Yes, standard procedure for Windows and Mac OS to report apps that are
not signed with recognized certificates from reputable organizations.
In this particular case, the latest automated builds of Ace App are
not signed at all, so there are additional warnings when the app is
installed and launched.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/daisy/ace-gui/issues/103#issuecomment-597686859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOY4XQEC3QYPVIIN7MTOTX3RG6SBFANCNFSM4LFFUEWQ.

Hello, what the exact error message?
With unsigned apps in Windows, there is a warning message that appears in a popup dialog box which the user can expand in order to reveal an additional button that allows the application to install / run.

I had the same JavaScript error with the Ace 1.1.0, triggered when viewing the Outlines tab, but only happened once and could not be replicated.


esp8266 reverse-engineering

A bit offtopic, but - saw your (I guess so) topic on bbs.espressif about packet injection work you did. Would like to make sure that folks who're interested in getting more of esp8266 know about each other's efforts and hopefully stay in touch. Some my stuff of interest mentioned here: https://github.com/tommie/lx106-hal/issues/1#issuecomment-96367093

Hi,
It's nice to meet people working around Esp8266. I really believe this chip
has potential, but Espressif is not moving towards opening their low level
stack. I see some open frameworks arising here and there, as the Sming, I
guess lead by some russian guys.
I've been seeking packet injection cause I have this crazy idea of making a
mesh framework for the ESP, without AP associations and all the 802.11
stuff, using just probe packets with a protocol stuffed into it, in a real
multi-to-multi scenario. It could replace solutions like zigbee and other
low power wireless devices, apart from being open sourced.
I'm probably not that familiar with such low level programming as you are
and I'm really learning a low from your tools. I'll try to make my way
around the ScratchABit https://github.com/pfalcon/ScratchABit and see if
I can patch some interesting rom functions.
Thank you for your work and reaching out to me. Let's definitely keep in
touch.
On Thu, Apr 30, 2015 at 9:59 AM, Paul Sokolovsky<EMAIL_ADDRESS>wrote:

A bit offtopic, but - saw your (I guess so) topic on bbs.espressif about
packet injection work you did. Would like to make sure that folks who're
interested in getting more of esp8266 know about each other's efforts and
hopefully stay in touch. Some my stuff of interest mentioned here: tommie/lx106-hal#1
(comment)
https://github.com/tommie/lx106-hal/issues/1#issuecomment-96367093
—
Reply to this email directly or view it on GitHub
https://github.com/israellot/esp-ginx/issues/2.

I really believe this chip has potential, but Espressif is not moving towards opening their low level stack.

Well, there're even bigger problems with Espressif SDK, like completely messed up licensing, see http://www.cnx-software.com/2015/04/24/wipy-wi-fi-board-for-iot-runs-micropython-on-texas-instruments-cc3200-crowdfunding/#comments .

I see some open frameworks arising here and there, as the Sming, I guess lead by some russian guys.

Most of these are application-level frameworks which tends to use adhoc Espressif API instead of standard socket / TCP/IP APIs. However, taking a fresh look at Sming, I found https://github.com/kadamski/esp-lwip , which is something I had in my TODO, and very glad that there're people who actually can to do it right and making it truly open-source.

I'm probably not that familiar with such low level programming as you are and I'm really learning a low from your tools.

Well, it's good approach to try learn new (generic) things when working on reverse engineering on some closed product, because otherwise it can be just waste of time. I'm already glad that hacking with ESP8266 made me look into lwIP (I didn't have experience with it before). And I'm looking forward to learn more of how 802.11 protocol works ;-).

I'll try to make my way around the ScratchABit https://github.com/pfalcon/ScratchABit and see if I can patch some interesting rom functions.

Thanks. It works with https://github.com/themadinventor/ida-xtensa and while it is work in progress, should already let to do some useful things.

If you guys are interested, check out my repo. I have found ways to send (almost) arbitrary wifi frames, as well as receiving complete frames (it's not monitor mode, but can receive broadcast frames and frames with your MAC address).


Plugin breaks optional chaining in build

I found that when I enable this plugin in my project, je "optional chaining" hello?.world no longer works.
It does work when running npm run dev, but does not when running npm run build.
Given you use hello?.world in the project, when building, the source becomes hello.world. The optional chaining is completely removed.
I added this plugin to https://github.com/imomaliev/vue-ts and modified some files slightly:
main.ts
declare global {
    interface Window {
        axios :any
    }
    let axios :any
}

import {createApp} from 'vue'
import App         from<EMAIL_ADDRESS>import axios from 'axios'
window.axios = axios
await window.axios.get( '/csrf' )

createApp( App ).mount( '#app' )

HelloWorld.vue

<template>

Text

</template>

tsconfig.ts
//    "strict": true,

vite.config.ts
import {defineConfig} from 'vite'
import vue            from '@vitejs/plugin-vue'
import topLevelAwait  from 'vite-plugin-top-level-await' // required for bootstrap.ts

// https://vitejs.dev/config/
export default defineConfig( {
    build:   {
        target: 'es2022',
        minify: false,
    },
    plugins: [
        topLevelAwait( {
            // The export name of top-level await promise for each chunk module
            promiseExportName: '__tla',
            // The function to generate import names of top-level await promise in each chunk module
            promiseImportName: i => `__tla_${i}`,
        } ),
        vue()],
    resolve: {
        alias: [{find: '@', replacement: '/src'}],
    },
} )

Using these minimal changes, I was able to reproduce the problem.
I have not yet put in effort to figure out the exact cause of this problem, but it would be nice if it could be solved.

Sorry, I just found it's because my workaround for a SWC bug:
// Workaround swc-project/swc#3808
visitOptionalChainingExpression(expression: SWC.OptionalChainingExpression) {
  return this.visitExpression(expression["base"]);
}

My workaround causes the lost of the optional chaining. All optional chainning expressions are replaced with their base expression.
I can't remember what I'm doing when writing the workaround, especially the patch I submitted to SWC upstream turned out to be correct ...

Fixed in v1.2.0.


Fix: Use return type declarations

This PR

[x] uses return type declarations in test code where appropriate

Follows #675.

Thank you, @chartjes!


fix(template) - refactor and split code for test helper

What?

Why?
JIRA: EXT-

How to test? (optional)

Current dependencies on/for this PR:

main

PR #304

PR #307

PR #316

PR #317   👈

This stack of pull requests is managed by Graphite.


Calendar start and end date are not correctly generated

The start_date is always set to the last day of the previous month while the end date is set to one day earlier than the it should be. In this way i miss getting the data fro the 28th of feb and 31st of march in my example
"https://my_example/get/calendar/92/?start_date=2014-01-31T23:00:00.000Z&end_date=2014-02-27T23:00:00.000Z&user_id=4"."
https://my_example/get/calendar/data/?start_date=2014-02-28T23:00:00.000Z&end_date=2014-03-30T22:00:00.000Z&user_id=4".".
I used the latest unminified heatmap with this initialization:
function getUpdateUrl(){
    return url_get_calendar_data +"?start_date={{d:start}}&end_date={{d:end}}"+"&user_id="+getUserId();
}

    cal.init({
        itemSelector: "#example-g",
        data: getUpdateUrl(),
        start: selected_date,
        cellSize: 25,
        itemName: ["hour", "hours"],
        cellPadding: 4,
        domain: "month",
        subDomain: "x_day",
        range: 1,
        legend: [1, 2, 4 ,8 ],
        displayLegend: false,
        nextSelector: "#nextMonthSelector",
        previousSelector: "#prevMonthSelector",
        highlight: ["now", selected_date],
        subDomainTextFormat: "%d",
        subDomainTitleFormat : {
            empty: "No data on {date}",
            filled: "{count} {name} {connector} {date}"
        },
        domainLabelFormat: "%B %Y",
        onClick: function(date,value) {
            $.event.trigger(
                {
                    type: "changeDate",
                    newDate: new Date(date)
                })
        },
        afterLoadData: pre_format_data
    });

If there is more information needed or if you think i did something wrong, please let me know.
Thanks

I am in Asia/Kuala_Lumpur. Still face the same problem

I have the same issue.
After a brief check it appears that the end date is using the same date at midnight 00:00:00. This excludes 1 day from the domain.
If the end date is converted to 23:59:50 or better at Day+1 at 00:00 it seems to work.
I have corrected the function as follows: adding endDate.setDate(endDate.getDate() + 1).
parseURI: function(str, startDate, endDate) {
		"use strict";

		// Added to correct bug in date selection
		endDate.setDate(endDate.getDate() + 1)

		// Use a timestamp in seconds
		str = str.replace(/\{\{t:start\}\}/g, startDate.getTime()/1000);
		str = str.replace(/\{\{t:end\}\}/g, endDate.getTime()/1000);

		// Use a string date, following the ISO-8601
		str = str.replace(/\{\{d:start\}\}/g, startDate.toISOString());
		str = str.replace(/\{\{d:end\}\}/g, endDate.toISOString());

		return str;
	},

May be can be check it and introduce it into the code.
Thanks,
Fabio

.toISOString() should always return an UTC time, so not timezone dependent.
If your backend is not returning the correct dates, it may be because it does not parse the date with the correct timezone.
the endDate is indeed the last subdomain of the calendar, so it it's a yearly calendar by days, endDate is 31 December, at 00:00, and you indeed lose data for the last day.
v4 will fix this issue


Parse Query results (AWS + MongoLab + Android)

I have migrated to AWS, MonboLab(data migrated according to parse guide) and am currently testing on android. I have the latest parse-server and latest android SDK version running. So here are 2 problems found after the migration, when android return results from the ParseQuery:

when there are 4 pointers, using query.include("pointer"), the data returned from the pointers are null, which shouldn't since checking mongo 3 pointers have data, and only 1 is null. When I remove this pointer that returns null, the others 3 pointers return data normally. So, is there a include limit issue? how that null pointer is messing all other pointers?

data that have Read or Write permission ACL to the current user are not being returned, unless the data has public permission. Is there any ACL migration setup I'm missing here? I've checked mongo and all classes seemed to have been migrated normally.

Here is the query definition:
ParseQuery<ParseObject> query = ParseQuery.getQuery("Offer");
query.include("seller");
query.include("buyer");
query.include("seller_currency_rate");
query.include("buyer_currency_rate");
query.whereEqualTo("active", true);
query.whereNotEqualTo("seller", currentUser);
query.whereNotEqualTo("buyer", currentUser);
query.whereGreaterThanOrEqualTo("amount", currentUser.getDouble("minimum_amount"));
query.whereLessThanOrEqualTo("amount", currentUser.getDouble("maximum_amount"));
query.whereEqualTo("seller_currency", currentUser.getString("seller_currency"));
query.whereEqualTo("buyer_currency", currentUser.getString("buyer_currency"));
query.orderByDescending("createdAt");
query.findInBackground(new FindCallback<ParseObject>() {

Appreciate any help. Thanks!

Did anybody have issues with ACL when doing a ParseQuery?

This is a possible bug, and a test-case could be written to test if a null pointer causes failing results.  Are you still having this issue on 2.1.3?

Thanks Fosco,
So, I was on 2.0, now with 2.1.3 there seems to be no problem querying null pointer. But... now I can't login with any email/password user account, exception was facebook user account which let me confirm the null pointer issue was gone. And the problem 2 I've mentioned above, related to ACL still persists on android, I can't see records that have ACL read or write to current user, I only see records that have ACL public read/write access.
Just so you know, after updating to 2.1.3, on android I have only changed the server url and reinstalled the app.
I'm also testing this migration app on iOS, with same configuration keys, mongo, server, everything... and there was no problem related to user accessing, or any ACL issue so far. Cloud code seems to be working fine too.

If you can set the environment variable VERBOSE=1 and capture the queries from iOS/Android and spot any difference, that would help... Just added a PR to fix some android specific functionality earlier, and I'm sure there's more to be done.

There you go. I don't see any significant difference.
Android
GET /parse/classes/Offer { host: 'parseserver-xxx-env.elasticbeanstalk.com',
  'x-real-ip': '<IP_ADDRESS>',
  'x-forwarded-for': '<IP_ADDRESS>, <IP_ADDRESS>',
  'content-length': '305',
  'accept-encoding': 'gzip',
  'content-type': 'application/json',
  'user-agent': 'Parse Android SDK 1.13.0 (com.xxxx.xxxx/4) API Level 21',
  'x-newrelic-id': 'xxxxxxx==',
  'x-parse-app-build-version': '4',
  'x-parse-app-display-version': '1.1.2',
  'x-parse-application-id': 'xxxxxxxx',
  'x-parse-client-key': 'xxxxx',
  'x-parse-client-version': 'a1.13.0',
  'x-parse-installation-id': 'xxxxxxxxxx',
  'x-parse-os-version': '5.0.2',
  'x-parse-session-token': 'r:xxxxx',
  'x-forwarded-port': '80',
  'x-forwarded-proto': 'http' } {
  "include": "buyer_currency_rate,seller,buyer,seller_currency_rate",
  "where": "{\"$or\":[{\"seller\":{\"__type\":\"Pointer\",\"className\":\"_User\",\"objectId\":\"5glMupmjyC\"}},{\"buyer\":{\"__type\":\"Pointer\",\"className\":\"_User\",\"objectId\":\"5glMupmjyC\"}}]}",
  "order": "-updatedAt"
}

iOS
GET /parse/classes/Offer { host: 'parseserver-xxx-env.elasticbeanstalk.com',
  'x-real-ip': '<IP_ADDRESS>',
  'x-forwarded-for': '<IP_ADDRESS>, <IP_ADDRESS>',
  'content-length': '245',
  accept: '*/*',
  'accept-encoding': 'gzip, deflate',
  'accept-language': 'pt-br',
  'content-type': 'application/json; charset=utf-8',
  'user-agent': 'xxxx/3 CFNetwork/758.2.8 Darwin/15.3.0',
  'x-newrelic-id': 'xxxx==',
  'x-parse-app-build-version': '3',
  'x-parse-app-display-version': '1.1.2',
  'x-parse-application-id': 'xxxxx',
  'x-parse-client-key': 'xxxxx',
  'x-parse-client-version': 'i1.12.0',
  'x-parse-installation-id': 'xxxx',
  'x-parse-os-version': '9.2 (15D21)',
  'x-parse-session-token': 'r:xxxx',
  'x-forwarded-port': '80',
  'x-forwarded-proto': 'http' } {
  "include": "buyer,seller",
  "order": "-updatedAt",
  "where": {
    "$or": [
      {
        "seller": {
          "objectId": "gghAJsj2dy",
          "className": "_User",
          "__type": "Pointer"
        }
      },
      {
        "buyer": {
          "objectId": "gghAJsj2dy",
          "className": "_User",
          "__type": "Pointer"
        }
      }
    ]
  },
  "limit": "25"
}

Glad the null pointer issue is fixed... The ACL issue seems well covered in tests, so you'd need to provide some more details or do some troubleshooting / test writing your self.  If you are still having issues, please open a new issue.  Thanks.


Adding Authentication Header to Request

Trying to stream media from an API that requires the header "Authorization: Bearer ".
I've used the following to inject the header:
@Injectable()
export class ApiAuthInterceptor implements HttpInterceptor {
  constructor( @Inject(forwardRef(() => SessionProvider)) private session: SessionProvider) { }
  intercept(req: HttpRequest<any>, next: HttpHandler) {
    let auth: any = {};
    if (this.session.auth) auth = this.session.auth;
    const newReq = req.clone({ headers: req.headers.set('Authorization', 'Bearer ' + auth.access_token) });
    return next.handle(newReq);
  }
};
@NgModule({
  providers: [
    ApiProvider,
    { provide: HTTP_INTERCEPTORS, useClass: ApiAuthInterceptor, multi: true }
  ]
})

This works great for images, and video will load and play, but the file appears to download in its entirety and play. Also the video time is listed at --:-- and the seek control slider is disabled.
If I disable all authentication on the API and streamed the same file it worked normally, buffering, seek, etc.
Is there a proper way to add the "Authentication" header to the stream request?

+1
I've been looking for a way to do this too. Would be handy to be able to pass headers in.

+1
Would be very useful

@s1rc @Arathmorr @kbr5 if any of you finished this would you be able to provide a PR?

Would be a very usefull feature.

https://github.com/nchutchind/cordova-plugin-streaming-media/pull/229


⚠ ClamAV has degraded performance

In 85d3662, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 56 ms

Resolved: ClamAV performance has improved in 092d9f1.


While Loops: handle exiting a loop from within a conditional block

The existing logic doesn't recognize that you can break out of loops inside of an if statement, since it only checks for LEAVES_LOOP in the main scope.

The self-check is still failing on 3.6 because the StackedScopes.loop_scope annotation will also need to be changed.
I'm going to look into why we don't catch this on 3.7+.

I can update that. does the type for the base Scope class not need to be changed?

does the type for the base Scope class not need to be changed

Yes I think so. That's another thing that pyanalyze should catch by itself.


Inflight Batching via Python Client

Hi Team,
Any updates on Inflight Batching support with Triton via Python client?
Thanks!

It is not supported yet. We are working on it. There will also be a standard solution to integrate TRT-LLM with the Python backend of Triton soon.

It is not supported yet. We are working on it. There will also be a standard solution to integrate TRT-LLM with the Python backend of Triton soon.

Could you please tell me how long it will be online? I am looking forward to it. Thanks

Just to be clear, you can deploy the c++ trt-llm backend (with in-flight batching capabilities) in Triton, and then use a Python client to send requests to it. Example clients can be found in https://github.com/triton-inference-server/tensorrtllm_backend/tree/main/inflight_batcher_llm/client for example.
We have also added a Python BLS backend that can be used to implement more complex logic when orchestrating the preprocessor, the trt-llm backend and the postprocessor. See https://github.com/triton-inference-server/tensorrtllm_backend/blob/main/all_models/inflight_batcher_llm/tensorrt_llm_bls/1/model.py
If you are asking about a python backend with the same functionality as the C++ trt-llm backend in https://github.com/triton-inference-server/tensorrtllm_backend/tree/main/all_models/inflight_batcher_llm/tensorrt_llm, this is still under development. We are still actively working on it but cannot commit to a date yet.

HI, Any update on the python backend? It could be a blocker for the adoption of some json formatter package.

Python backend for inflight batching can be found here: https://github.com/triton-inference-server/tensorrtllm_backend/blob/main/all_models/inflight_batcher_llm/tensorrt_llm/1/model.py
It uses the Python bindings to the C++ executor API.


Issue building with cmake 3.17 and Visual Studio 2019

I'm trying to learn about creating a c# assembly with cmake, and this project seems to be a good starting point.
Unfortunately it doesn't seem to work with what I have installed on my system (cmake 3.17, Visual Studio 2019), or using my normal cmake sequence of commands.
I do:
$ git clone https://github.com/Aschratt/DotNetWithCMake.git
$ cd DotNetWithCMake/
$ mkdir build
$ cd build
$ cmake .. -G "Visual Studio 16 2019" -A x64

But cmake cannot find various files it needs:
-- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.18363.
CMake Warning at CommonLib/CMakeLists.txt:2 (PROJECT):
  the following parameters must be specified after LANGUAGES keyword:
  <IP_ADDRESS>.

CMake Error: Could not find cmake module file: CMakeDetermine<IP_ADDRESS>Compiler.cmake
CMake Error: Could not find cmake module file: C:/Users/VRTogether/src/DotNetWithCMake/CMakeFiles/3.17.0/CMake<IP_ADDRESS>Compiler.cmake
CMake Error at CommonLib/CMakeLists.txt:2 (PROJECT):
  No CMAKE_<IP_ADDRESS>_COMPILER could be found.

CMake Error: Could not find cmake module file: CMake<IP_ADDRESS>Information.cmake
-- Configuring incomplete, errors occurred!
See also "C:/Users/VRTogether/src/DotNetWithCMake/CMakeFiles/CMakeOutput.log".
See also "C:/Users/VRTogether/src/DotNetWithCMake/CMakeFiles/CMakeError.log".

Manually running ../CMakeFiles/3.17.0/CompilerIdCSharp/CompilerIdCSharp.exe suggests that maybe VS2019 is too new, but I'm not sure:
$ ../CMakeFiles/3.17.0/CompilerIdCSharp/CompilerIdCSharp.exe
INFO:compiler[Microsoft unknown]
INFO:platform[Windows]
INFO:arch[x64]
INFO:compiler_version[9999]
$

I've looked into the issue and could reproduce it with CMake 3.18.1. The original template has been created with CMake 3.14 and VS 2019. I don't know why it worked in the first place, but making the VERSION attribute for the projects explicit resolves the issue for me.
Note that there were some other minor issues (mostly wrong naming, since I've ported this template out of an existing project I've been working on). You can pull the last two commits and see if it works for you. Let me know if you have any further problems! 🙃

Closing for now. Let me know if you still have trouble! 🙂

Thanks, that fixed it!


Is there any examples about swap other token for eth

Dear sir,
I want to swap other token (i.e usdt or dai) for eth, but I can't find any example in this repo, can you provide some support。
（please forgive my bad english and writing format）

https://github.com/Nethereum/Nethereum.Uniswap-V2-and-V3/blob/main/Nethereum.Uniswap.Testing/UniSwapV2PairTests.cs

Is the unit test named ShouldBeAbleToGetThePairForDaiWeth? But is just swap for weth

Sorry, i can only see eth for dai and eth for dai for usdt, can you be more detailed?

Those are the examples on how to swap using Uniswap.

https://github.com/Nethereum/Nethereum.Uniswap-V2-and-V3/blob/main/Nethereum.Uniswap/UniswapV2Router02/UniswapV2Router02Service.cs#L497

Got it !!!  thanks for help
https://github.com/Nethereum/Nethereum.Uniswap-V2-and-V3/blob/fec9bc6bb3a2a22243f63c526a0f0dafc6cab4e7/Nethereum.Uniswap/UniswapV2Router02/UniswapV2Router02Service.cs#L571


Add logic to ls and stat to process arbitrary metadata keys

Closes #806

Thanks for the review @labkode! Made the change.


Prolog seems to be a directory instead of a submodule

Not a big deal... just thought I'd point it out.
I might also be wrong. I just noticed that it was showing up in the repo languages and got confused by the amount of prolog and gnuplot up in here.

The commit is https://github.com/exercism/trackler/commit/af74efbb5041b2dcf5bfd3db7ed8c340c3e9e084.
Might be the missing .git here unlike other languages.

That's probably it.


what mean about "bimo"

hi, i have a question , what mean about class name "bimo". thanks very much. :)

bimo 双轮车

bimo 双轮车

get！thanks！


DOcker 部署有问题。

今天又来测试，
1. 清理所有内容
docker-compose down
docker system prune -f
2. 重新启动
docker-compose up -d
3. 进入容器并启动服务
docker exec -it ten_agent_dev bash
cd /app
make build
make run-server
总是到make run-server 之后， 后台报错如下，
前端界面是都能进，但是没有服务,
2024-10-30 22:53:08 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:53:08 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:53:08 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:53:08 ten_agent_playground  |   port: 49483
2024-10-30 22:53:08 ten_agent_playground  | }
2024-10-30 22:53:08 ten_agent_playground  | Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:53:08 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:53:08 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:53:08 ten_agent_playground  |   errno: -111,
2024-10-30 22:53:08 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:53:08 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:53:08 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:53:08 ten_agent_playground  |   port: 49483
2024-10-30 22:53:08 ten_agent_playground  | }
2024-10-30 22:53:08 ten_agent_playground  | Failed to proxy http://ten_agent_dev:49483/api/dev-server/v1/graphs/camera_va_openai_azure/nodes Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:53:08 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:53:08 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:53:08 ten_agent_playground  |   errno: -111,
2024-10-30 22:53:08 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:53:08 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:53:08 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:53:08 ten_agent_playground  |   port: 49483
2024-10-30 22:53:08 ten_agent_playground  | }
2024-10-30 22:53:08 ten_agent_playground  | Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:53:08 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:53:08 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:53:08 ten_agent_playground  |   errno: -111,
2024-10-30 22:53:08 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:53:08 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:53:08 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:53:08 ten_agent_playground  |   port: 49483
2024-10-30 22:53:08 ten_agent_playground  | }
2024-10-30 22:45:46 ten_agent_demo        |   ▲ Next.js 14.2.4
2024-10-30 22:45:46 ten_agent_demo        |   - Local:        http://localhost:3000
2024-10-30 22:45:46 ten_agent_demo        |   - Network:      http://<IP_ADDRESS>:3000
2024-10-30 22:45:46 ten_agent_demo        |
2024-10-30 22:45:46 ten_agent_demo        |  ✓ Starting...
2024-10-30 22:45:46 ten_agent_demo        |  ✓ Ready in 76ms
2024-10-30 22:49:32 ten_agent_demo        | Starting agent for request ID: {"request_id":"3e235f44-17f2-49c4-b718-b01b349685a1","channel_name":"agora_gmwdd9","user_uid":162468,"graph_name":"camera_va_openai_azure","properties":{"agora_rtc":{"agora_asr_language":"en-US"},"openai_chatgpt":{"model":"gpt-4o","greeting":"TEST ","checking_vision_text_items":"["Let me take a look...","Let me check your camera...","Please wait for a second..."]","prompt":"USEFULL\n"},"azure_tts":{"azure_synthesis_voice_name":"en-US-AndrewMultilingualNeural"}}}
2024-10-30 22:49:32 ten_agent_demo        | AGENT_SERVER_URL: http://ten_agent_dev:8081/start
2024-10-30 22:52:23 ten_agent_demo        | Starting agent for request ID: {"request_id":"bcfc6c10-2465-4dab-bcf9-e580b0767c57","channel_name":"agora_1uenu9","user_uid":156227,"graph_name":"va_openai_azure","properties":{"agora_rtc":{"agora_asr_language":"zh-CN"},"openai_chatgpt":{"model":"gpt-4o-mini","greeting":"TEST ","checking_vision_text_items":"["让我看看你的摄像头...","让我看一下...","我看一下，请稍候..."]","prompt":"USEFULL\n"},"azure_tts":{"azure_synthesis_voice_name":"zh-CN-YunxiNeural"}}}
2024-10-30 22:52:23 ten_agent_demo        | AGENT_SERVER_URL: http://ten_agent_dev:8081/start
2024-10-30 22:52:27 ten_agent_demo        | Starting agent for request ID: {"request_id":"e3a7ef19-a7ed-48ad-8e25-e34b5efa769e","channel_name":"agora_1uenu9","user_uid":156227,"graph_name":"camera_va_openai_azure","properties":{"agora_rtc":{"agora_asr_language":"zh-CN"},"openai_chatgpt":{"model":"gpt-4o","greeting":"TEST ","checking_vision_text_items":"["让我看看你的摄像头...","让我看一下...","我看一下，请稍候..."]","prompt":"USEFULL\n"},"azure_tts":{"azure_synthesis_voice_name":"zh-CN-YunxiNeural"}}}
2024-10-30 22:52:27 ten_agent_demo        | AGENT_SERVER_URL: http://ten_agent_dev:8081/start
2024-10-30 22:54:09 ten_agent_playground  | Failed to proxy http://ten_agent_dev:49483/api/dev-server/v1/packages/reload Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:54:09 ten_agent_playground  |   errno: -111,
2024-10-30 22:54:09 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:54:09 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:54:09 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:54:09 ten_agent_playground  |   port: 49483
2024-10-30 22:54:09 ten_agent_playground  | }
2024-10-30 22:54:09 ten_agent_playground  | Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:54:09 ten_agent_playground  |   errno: -111,
2024-10-30 22:54:09 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:54:09 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:54:09 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:54:09 ten_agent_playground  |   port: 49483
2024-10-30 22:54:09 ten_agent_playground  | }
2024-10-30 22:54:09 ten_agent_playground  | Failed to proxy http://ten_agent_dev:49483/api/dev-server/v1/graphs/camera_va_openai_azure/nodes Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:54:09 ten_agent_playground  |   errno: -111,
2024-10-30 22:54:09 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:54:09 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:54:09 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:54:09 ten_agent_playground  |   port: 49483
2024-10-30 22:54:09 ten_agent_playground  | }
2024-10-30 22:54:09 ten_agent_playground  | Error: connect ECONNREFUSED <IP_ADDRESS>:49483
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-10-30 22:54:09 ten_agent_playground  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-10-30 22:54:09 ten_agent_playground  |   errno: -111,
2024-10-30 22:54:09 ten_agent_playground  |   code: 'ECONNREFUSED',
2024-10-30 22:54:09 ten_agent_playground  |   syscall: 'connect',
2024-10-30 22:54:09 ten_agent_playground  |   address: '<IP_ADDRESS>',
2024-10-30 22:54:09 ten_agent_playground  |   port: 49483
2024-10-30 22:54:09 ten_agent_playground  | }

port 8080 is not up and running.
code: 'ECONNREFUSED', means connection attempt got rejected by the server. Normally make clean and re-run make build would fix it.

On the UI, top right corner, the green bar means the connection status. Making sure that's green, otherwise it's not gonna work. :)

@Walkman1W Let me know if you still have the problem after restarting.

port 8080 is not up and running.
code: 'ECONNREFUSED', means connection attempt got rejected by the server. Normally make clean and re-run make build would fix it.

Do I need to recompile the ten_agent_build container? @cyfyifanchen

oh Thanks a lot , That's work for me!

oh Thanks a lot , That's work for me!

Glad you got it figured out, what did you do? Rerun the commands


objects created in separate python processes cannot be fetched cross process

Hi, I have a custom django-admin command called aggregateevents that performs a map/reduce over my mongodb instance and saves the events using python-stdnet into redis. The strange thing is that when I run my app server using the django runserver command, none of the objects that were saved using the custom aggregateevents command can be found. They are there, because if I rerun the custom command it can see the previously saved objects. Here is the definition of my object:
import logging
from stdnet import orm
logger = logging.getLogger(name)
class RedisEvent(orm.StdModel):
lystKey = orm.SymbolField()
eventDate = orm.DateTimeField()
lystName = orm.CharField()
lystLink = orm.CharField()
profileTitle = orm.CharField()
profileLink = orm.CharField()
profilePic = orm.CharField()
text = orm.CharField()
orm.register(RedisEvent,'redis://<IP_ADDRESS>/?db=0', keyprefix='lystee', timeout=3600)
logger.debug('total aggregated: ' + str(RedisEvent.objects.all().count()))
Shouldn't all python processes be able to fetch saved instances of objects stored in Redis, as long as the connection string, db number, and key prefix match?

Once an object is saved in redis, it can be retrieved from anywhere as long as you use the same connection string.
To check that the connection string is the same have a look at the RedisEvent._meta.cursor attribute.


Update trace feeders URL

Trace feeders URL now matches that used by PAW. This fixes an issue that lead to responses being empty.

Thanks @rclapp
I can confirm that the trace_cell_feeders function is working as expected. However, the check_cell_feeders doesn't return the expected value yet.
Am I missing something? Is the output below expected?
from TM1py import TM1Service

with TM1Service(address='localhost', port=12354, ssl=True, user="admin", password="apple") as tm1:
    cell_trace = tm1.cells.trace_cell_feeders(cube_name="c1", elements="e1,e1")
    print(cell_trace)

    check_result = tm1.cells.check_cell_feeders(cube_name="c1", elements="e1,e1")
    print(check_result)

<EMAIL_ADDRESS>'../$metadata#ibm.tm1.api.v1.FeederTrace', 'FedCells': [{'Fed': True, 'Cube': {'Name': 'c1'}, 'Tuple': [{'Name': 'e4', 'UniqueName': '[d1].[d1].[e4]', 'Type': 'Numeric'}, {'Name': 'e1', 'UniqueName': '[d2].[d2].[e1]', 'Type': 'Numeric'}]}], 'Statements': ["['d1':'e1'] => ['d1':'e4'];"]}
<EMAIL_ADDRESS>'../$metadata#Collection(ibm.tm1.api.v1.FedCellDescriptor)', 'value': []}

I have a ticket open with IBM, will keep you posted.
From: Marius Wirtz @.>
Reply-To: cubewise-code/tm1py @.>
Date: Tuesday, August 30, 2022 at 7:30 AM
To: cubewise-code/tm1py @.>
Cc: "Clapp, Ryan" @.>, Mention @.***>
Subject: Re: [cubewise-code/tm1py] Update trace feeders URL (PR #794)
Thanks @rclapphttps://github.com/rclapp
I can confirm that the trace_cell_feeders function is working as expected. However, the check_cell_feeders doesn't return the expected value yet.
Am I missing something? Is the output below expected?
from TM1py import TM1Service
with TM1Service(address='localhost', port=12354, ssl=True, user="admin", password="apple") as tm1:
cell_trace = tm1.cells.trace_cell_feeders(cube_name="c1", elements="e1,e1")

print(cell_trace)

check_result = tm1.cells.check_cell_feeders(cube_name="c1", elements="e1,e1")

print(check_result)

@.***': '../$metadata#ibm.tm1.api.v1.FeederTrace', 'FedCells': [{'Fed': True, 'Cube': {'Name': 'c1'}, 'Tuple': [{'Name': 'e4', 'UniqueName': '[d1].[d1].[e4]', 'Type': 'Numeric'}, {'Name': 'e1', 'UniqueName': '[d2].[d2].[e1]', 'Type': 'Numeric'}]}], 'Statements': ["['d1':'e1'] => ['d1':'e4'];"]}
@.***': '../$metadata#Collection(ibm.tm1.api.v1.FedCellDescriptor)', 'value': []}
[image]https://user-images.githubusercontent.com/15182131/187425386-168aa459-19b8-4f27-8fb1-ab7906e78464.png
—
Reply to this email directly, view it on GitHubhttps://github.com/cubewise-code/tm1py/pull/794#issuecomment-1231535918, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEK7GZVEBU2NDRVCZJNAXA3V3XWB5ANCNFSM57IAM4KA.
You are receiving this because you were mentioned.Message ID: @.***>


feat(#325): Handle Try-Catch Statements

Correctly handle method exception tables and try-catch statements.
Closes: #325

History:

feat(#325): enable integration test
feat(#325): add more instructions
feat(#325): accuratly handle method exceptions
feat(#325): add DirectivesTryCatch
feat(#325): write the test for DirectivesTryCatch
feat(#325): write trycatch blocks into bytecode
feat(#325): save try-catch-block into bytecode
feat(#325): correctly wrtie tryCatch statement into bytecode
feat(#325): enable most of the integration tests related to exceptions
feat(#325): add javadocs for several classes
feat(#325): add one more puzzle for refactoring
feat(#325): fix all qulice suggestions
feat(#325): fix all xcop suggestions

PR-Codex overview
This PR focuses on improving the bytecode representation in the JEO project. It includes changes such as replacing instruction with opcode in XmlInstruction, adding support for try-catch blocks in DirectivesMethod, and removing unused methods in XmlBytecodeEntry.
Detailed summary

Replaced instruction with opcode in XmlInstruction
Added support for try-catch blocks in DirectivesMethod
Removed unused node method in XmlBytecodeEntry
Added new bytecode instructions for loading values from arrays
Added label name in DirectivesLabel
Added exception method in DirectivesMethod
Updated method names and added exception handling in BytecodeMethod

The following files were skipped due to too many changes: src/main/java/org/eolang/jeo/representation/xmir/XmlNode.java, src/main/java/org/eolang/jeo/representation/xmir/XmlMethod.java, src/main/java/org/eolang/jeo/representation/bytecode/BytecodeTryCatchBlock.java, src/main/java/org/eolang/jeo/representation/xmir/XmlTryCatchEntry.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesTryCatch.java, src/test/java/org/eolang/jeo/representation/xmir/XmlTryCatchEntryTest.java, src/test/java/org/eolang/jeo/representation/directives/HasMethod.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesMethodVisitorTest.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here


Add Zoe to Preconfigured Tools

Added a link to Zoe, an ESLint-based tool similar to XO and Standard.

Zoe looks really cool. Thank you!


Implement DynamicDelegateAugments.CreateDynamicDelegate

@AlexGhiondea could you please provide a brief explanation of what this issue is about?

Make https://github.com/dotnet/corert/blob/26413145abcbdd49468db230a6f29784494f6f46/src/System.Private.CoreLib/src/Internal/Runtime/Augments/DynamicDelegateAugments.cs#L39 work

Thanks!

Fixed on the ProjectN branch by deleting the API (unused)

@fadimounir This API still exists: https://github.com/dotnet/corert/blob/26413145abcbdd49468db230a6f29784494f6f46/src/System.Private.CoreLib/src/Internal/Runtime/Augments/DynamicDelegateAugments.cs#L39
As the comment suggests, it is done via IL toolchain magic...

@jkotas The API really is unused. The thing that is used is CreateObjectArrayDelegate method (defined above). That one is just a piece of delegate thunk work that I track as the "last damn delegate thunk I need to implement before being finally done with this". We can make this issue track that thunk, although I haven't tracked thunks with issues in the past. I haven't done the thunk yet because I don't have means to test it.

As the comment suggests, it is done via IL toolchain magic...

The comment is inaccurate. The API is really not used. The API that is used is the CreateObjectArrayDelegate one, and only used if FEATURE_DYNAMIC_DELEGATE is not enabled (and this feature is actually enabled by default today, so even the CreateObjectArrayDelegate API seems to be unused)

Sorry, I misread something in Michal's comment. Do we want to use this issue to track that thunk that Michal is talking about, or just close the issue? (I already closed it, but we can reopen it and have it track the thunk work if needed)

If CreateDynamicDelegate is not used, we should delete it from the code.

Sorry, I see you have just delete it.


callback for bot.sendmessage

I have this code and i want to recive a callback for sendMessage
can u help me to  find callback for sendMessage
var register = function (chatId, from, command) {
var member = {
		fname:command,
		tCode:from.id,
		tFname:from.first_name,
		tLname:from.last_name
	}
	member.fname=command;
bot.sendMessage(chatId, 'insert your last name : ')
.then(payload => {
			console.log(payload)
		})
		.catch(function (error) {
			console.log(error);
		});
}

What do you mean as "callback"? Callback is a function which will be executed after sendMessage(), but you use .then() and execute code

i want to catch sendMessage callback. how can i catch that?
for inlineKeybord message we can use this
			bot.sendMessage(chatId, "select answer", { 				reply_markup: { 					inline_keyboard: [{text:'text1',callback_data:'data1'},{text:'text2',callback_data:'data2'}], 				}, 			}) 				.then(() => { 					bot.once("callback_query", answer => { 						console.log(answer) //this is my callback 					}) 				})
but for text message how we can catch callback
`
bot.sendMessage(fromId, 'What should I search for?')
.then(() => {
// callback for sendMessage
})
`

I do it
 bot.sendMessage(chatId, 'insert a name')
	.then(payload` => {
		bot.once('message', (msg) => {
                       console.log(msg) // callback for sendMessage
               });
	})

@milad145 I think you want to register on a reply to message. If that's the case, then your code will misbehave horribly if bot is used by more than one user (highly likely).
You probably want to use onReplyToMessage, like this:
// not tested, I probably made some small mistake somewhere
bot.sendMessage(chatId, 'insert a name', {
    reply_markup: {
        force_reply: true
    }
}).then(payload => {
    const replyListenerId = bot.onReplyToMessage(payload.chat.id, payload.message_id, msg => {
        bot.removeReplyListener(replyListenerId)
        console.log(msg) // here's the reply which is I think what you want
    })
})

@GingerPlusPlus
thank you, it was very usefull
but for inline_keyboard what we can do?
how we can pass chatId to callback_query
bot.once("callback_query", answer => {
  console.log(answer)
})

@milad145 Chat id is in the message field: https://core.telegram.org/bots/api#callbackquery


Implement path:remove

I considered adhering more closely to the traditional Unix rm and rmdir commands. For example, by implementing each independently and supporting the --force option. However, I concluded there are insufficient reasons to do so. In particular, the POSIX --force (or -f) option is most often used solely for its side-effect of making elimination of a non-existent path a non-error. I also don't like that -f also fixes permission errors to allow allow removing files. If we decide that feature is needed it should be added under a distinct option (e.g. &fix-perms).
Related: #1659

I don't see a good reason to deviate from Go, which has os.Remove (non-recursive) and os.RemoveAll (recursive). It's not clear why you reimplemented recursive removal instead of using os.RemoveAll.

I feel &ignore-missing is better named &missing-ok (there's precedent in *[nomatch-ok]). It is not exactly ambiguous, but it requires a bit of thinking to deduce what "ignore" exactly entails (in this case, ignoring any error from missing files).

I also feel this command shouldn't live in path. It's my fault for letting in is-dir, is-regular, temp-dir and temp-file, but I'd like to make path just about manipulating paths themselves, and create a new os module to mirror Go's os package. But feel free to leave it there and I'll do the cleanup after merging.

I mostly agree with your feedback, @xiaq. I need to think about whether a new os module is preferable. On the one hand I am inclined to agree given issue #1659 that I opened. I even noted this tension on where such commands should live in that issue. The question is how tightly we want to bind Elvish builtins to the Go package that underlies their functionality? This obviously has implications for the path:stat command I want to see merged. Should that also be named os:stat?

I don't see a good reason to deviate from Go, which has os.Remove (non-recursive) and os.RemoveAll (recursive). It's not clear why you reimplemented recursive removal instead of using os.RemoveAll.

Because the Go os.RemoveAll documentation says this:

RemoveAll removes path and any children it contains. It removes everything it can but returns the first error it encounters. If the path does not exist, RemoveAll returns nil (no error). If there is an error, it will be of type *PathError.

It is not clear that is the preferable behavior to expose since it elides (hides) some errors. My implementation exposes all errors. I also haven't tested the os.RemoveAll behavior. Does it actually delete all files that can be deleted even if there is an error deleting a particular path? The documentation of os.RemoveAll is ambiguous on that point.

I don't see a good reason to deviate from Go, which has os.Remove (non-recursive) and os.RemoveAll (recursive). It's not clear why you reimplemented recursive removal instead of using os.RemoveAll.

The main problem with using os.RemoveAll is that it silently ignores a non-existent path. Which we only want to do if the &missing-ok (or &ignore-missing) is true. So using that Go function requires adding an explicit test whether the path exists. It is simpler to just use os.Remove and recurse if the path is a non-empty directory. Not to mention aggregating removal errors which os.RemoveAll makes possible while os.Remove does not.
I am going to close this P.R. since the implementation is moving from the path module to a new os module in light of previous feedback. The new P.R. will include a comment why the Go os.RemoveAll is not used.


remove all the print() statements and use some form of logging instead

The following functions have been modified:

plot.py
test.py
train.py
tutorials/1-Introduction/China_A_share_market_tushare.py
tutorials/2-Advance/Crypto_Feature_Importance.py
tutorials/2-Advance/FinRL_PortfolioAllocation_Explainable_DRL.py
tutorials/2-Advance/execution_optimizing.py
tutorials/2-Advance/nas100_gpu_podracer.py
tutorials/2-Advance/stock_jq.py

the following can be written a function?
logger = logging.getLogger()
logger.setLevel("DEBUG")
file_handler = logging.FileHandler("./log.txt", mode="a", encoding="utf-8")
file_handler.setLevel("DEBUG")
file_handler.setFormatter(
logging.Formatter(fmt="%(lineno)s---%(asctime)s---%(message)s")
)
logger.addHandler(file_handler)

have you revised all print() to logging?

have you revised all print() to logging?

I have checked all run files at present, and I will continue to check other files in the package later.

Thanks for your advice. I'm doing this, I have a question, which folder would be more appropriate for the "log" function to be placed? meta? Or create a new folder, like utils?

i prefer creating a log folder.

@hoeckxer  good suggestions. thanks. glad to work with you.
@chennnuo pls revise it as the above suggestions. thanks.

Hey guys good about using a log Decorator?
https://ankitbko.github.io/blog/2021/04/logging-in-python/

Thank you very much for everyone's suggestions, I will take your suggestions seriously to revise and improve!

Hey guys how about using a log Decorator?
https://ankitbko.github.io/blog/2021/04/logging-in-python/

@eyast impressive idea.
@chennnuo
you do not need to close it.
you can revise PR locally and push it again.

@chennnuo  Just to check that this is fixed in the PR https://github.com/AI4Finance-Foundation/FinRL-Meta/pull/195
right?  Do we need a further operation?

@XiaoYangLiu-FinRL Sorry, I haven't finished fixing it yet, I'll fix it soon and let you know.

@chennnuo No problem.  Remember to use the most updated branch, to avoid conflict. Thanks.

@XiaoYangLiu-FinRL Ok thanks for the heads up, I'll keep an eye on that.


[Feature request] pyrosm.OSM.to_graph has a misleading name

Going along with the conventions set forward by, e.g., pandas, methods of data classes/objects that follow the form to_${format} export the local object’s data to ${format}.
pyrosm.OSM.to_graph() is more of a static method, and would be better called something along the lines of graph_from_nodes_and_edges().
It is a rather trivial change, but potentially breaks derived works. Still, it seems like a as-soon-as-possible-or-never thing to change to follow common conventions.

How about network_to_graph, or graph_from_network?

Graph and network are synonyms, so this is a bit ambiguous as well 🙂 (which one is used depends on the discipline). I think graph_from_nodes_and_edges() is the most unambiguous name to use but as said it's quite chunky, and because it is used very often by pyrosm users who continue working with network analysis libraries, it would mean repeating that long name time after another... 😄

please make it a @staticmethod, since it’s not using anything related to the class or instances.

Yes, this is something that should be changed 👍🏻


Turtle: improve ordering of ontology terms

https://github.com/atextor/turtle-formatter/issues/22
Currently rdfs:Class comes before owl:Ontology

use a query to find all types of things in the ontologies
use --subjectOrder to sort them in the best possible way

added to Makefile
  --subjectOrder owl:Ontology		\
  --subjectOrder rdfs:Class		\
  --subjectOrder owl:Class		\
  --subjectOrder rdf:Property		\
  --subjectOrder owl:ObjectProperty	\
  --subjectOrder owl:DatatypeProperty	\
  --subjectOrder owl:AnnotationProperty \
  --subjectOrder owl:NamedIndividual	\
  --subjectOrder owl:AllDifferent	\
  --subjectOrder owl:Axiom

Still need to find all types

Yes, we did this for RDFS, we should do for ttl too
Eventually this should be an item in the RDFS spec

This is still blocked by

https://github.com/atextor/owl-cli/issues/21
https://github.com/atextor/turtle-formatter/issues/27


ldap configuration via docker compose or CLI

Question:
I am trying to automate portrainer deployment. My problem is there is no real easy way to configure the ldap configuration without going through the web GUI. Am i correct or is there a way to do this, for example, via docker compose or CLI?
Thank you for such a nice product
Kind Regards
Goncalo

Hi @GoncaloBorges
Indeed, there is no way to automate the LDAP configuration via docker-compose/CLI. However, you can tune the LDAP configuration via the Portainer HTTP API post-deployment.
Hopes this answer the question, feel free to ask if you need more information.


Multicast packets circumvent app isolation

With CoreOS out-of-the box:
core@core-01 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
...
Status: Downloaded newer image for bboreham/mcast:latest
root@f7f69b63a0b7:/#
root@f7f69b63a0b7:/# /home/mcreceive <IP_ADDRESS> 5050
Received 3 bytes from <IP_ADDRESS>: HI
Received 3 bytes from <IP_ADDRESS>: HI
Received 3 bytes from <IP_ADDRESS>: HI
Received 3 bytes from <IP_ADDRESS>: HI

Now on the second machine:
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
...
Status: Downloaded newer image for bboreham/mcast:latest
root@3fb6b80d2820:/#
root@3fb6b80d2820:/# /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
HI
^C
root@3fb6b80d2820:/# exit

For some reason it didn't arrive on the first attemp, let's try again...
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@711ca39b82d3:/#
root@711ca39b82d3:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@711ca39b82d3:/# exit
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@a44b9ab53823:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@a44b9ab53823:/# exit
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@5e14e4888104:/#
root@5e14e4888104:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@5e14e4888104:/# exit
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@7f844a353553:/#
root@7f844a353553:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@7f844a353553:/#

To reproduce this, you can do:
git clone https://github.com/errordeveloper/weave-demos
cd weave-demos/felix; vagrant up

Then vagrant ssh core-01 and vagrant ssh core-02.

Just to be sure, check rp_fileter:
$ for i in /proc/sys/net/ipv4/conf/*/rp_filter; do echo $i: `cat $i`; done
/proc/sys/net/ipv4/conf/all/rp_filter: 1
/proc/sys/net/ipv4/conf/default/rp_filter: 1
/proc/sys/net/ipv4/conf/docker0/rp_filter: 1
/proc/sys/net/ipv4/conf/dummy0/rp_filter: 1
/proc/sys/net/ipv4/conf/eth0/rp_filter: 1
/proc/sys/net/ipv4/conf/eth1/rp_filter: 1
/proc/sys/net/ipv4/conf/lo/rp_filter: 0
/proc/sys/net/ipv4/conf/veth0114561/rp_filter: 1
/proc/sys/net/ipv4/conf/veth2310286/rp_filter: 1
/proc/sys/net/ipv4/conf/veth3188b88/rp_filter: 1
/proc/sys/net/ipv4/conf/vethwepl1293/rp_filter: 1
/proc/sys/net/ipv4/conf/vethwepl1485/rp_filter: 1
/proc/sys/net/ipv4/conf/vethwepl1875/rp_filter: 1
/proc/sys/net/ipv4/conf/weave/rp_filter: 1

Let's try to run docker daemon with --icc=false...
If you use weave-demos/felix, do this
$ git checkout docker-icc-false
$ vagrant destroy -f ; vagrant up

and then back in.
core@core-01 ~ $ ps -ef | grep docker | grep icc
root       987     1  4 12:16 ?        00:00:12 docker --daemon --host=fd:// --insecure-registry=<IP_ADDRESS>/0 --icc=false
core@core-01 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
...
Status: Downloaded newer image for bboreham/mcast:latest
root@3a11d59950e7:/#
root@3a11d59950e7:/# /home/mcreceive <IP_ADDRESS> 5050
Received 3 bytes from <IP_ADDRESS>: HI
Received 3 bytes from <IP_ADDRESS>: HI
Received 3 bytes from <IP_ADDRESS>: HI

^C
root@3a11d59950e7:/# exit

I have repeated most of the same commands on core-02:
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@2a43aaed4e03:/#
root@2a43aaed4e03:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@2a43aaed4e03:/# exit
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@ce66b715f7de:/#
root@ce66b715f7de:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@ce66b715f7de:/# exit
core@core-02 ~ $ docker attach `sudo weave run <IP_ADDRESS>/24 -ti bboreham/mcast:latest`
root@bca0694a2f9b:/#
root@bca0694a2f9b:/# echo HI | /home/mcsend <IP_ADDRESS> 5050
Begin typing (return to send, ctrl-C to quit):
root@bca0694a2f9b:/# exit

Can you check whether rp filtering is set on the ethwe interfaces in the containers? (Those are the ones with the ipv4 addresses attached, and so that where the rp filtering will occur, if anywhere.).  I.e., do:
weave/bin/docker-ns <container id> sh -c 'for i in /proc/sys/net/ipv4/conf/*/rp_filter; do echo $i: `cat $i`; done'

with the docker-ns script from the weave repo.
I get (not using coreos):
/proc/sys/net/ipv4/conf/all/rp_filter: 1
/proc/sys/net/ipv4/conf/default/rp_filter: 1
/proc/sys/net/ipv4/conf/eth0/rp_filter: 1
/proc/sys/net/ipv4/conf/ethwe/rp_filter: 1
/proc/sys/net/ipv4/conf/lo/rp_filter: 1

FTR, @dpw was unable to reproduce this.

With two containers on the same machine, I can't reproduce this:  mc packets don't reach the receiver program.
The rp_filter settings on my receiving container, by default, are:
/proc/sys/net/ipv4/conf/all/rp_filter: 1
/proc/sys/net/ipv4/conf/default/rp_filter: 1
/proc/sys/net/ipv4/conf/eth0/rp_filter: 1
/proc/sys/net/ipv4/conf/ethwe/rp_filter: 1
/proc/sys/net/ipv4/conf/lo/rp_filter: 1

Note that 1 is the strictest setting (0 is no filtering, 1 is strict filtering, 2 is loose filtering).  Also, the all/rp_filter setting interacts with the per-if settings in a surprising way. See the kernel docs on this at https://github.com/torvalds/linux/blob/master/Documentation/networking/ip-sysctl.txt#L989
So, as expected, if RP filtering is at its strictest setting, the receiver does not get the packets.
To confirm that RP filtering is responsible and that I haven't messed something else up, I turned it off, by setting ethwe/rp_filter and all/rp_filter to 0 for the receiving container.  And then the receiver program does see the packets.
Note that there is some odd statefulness on the receiving socket which can lead to confusion.  If I have RP filtering enabled, start the receiver program, and disabled RP filtering, it will see packets without a restart of the program.  But if RP filtering is enabled again, the program will continue to see packets! The program has to be restarted for the change to affect it.

I just reproduced a problem using a scenario suggested by Ilya, even with RP filtering enabled:

Start 3 containers, let's call them A, B and C, with A and B on one subnet and C on another.

Run the MC receiver on A and the sender on C.  As expected, A does not see packets from C.

Run the MC sender on B.  As expected, A sees packets from B.

But after A has received packets from B, it can now magically receive packets from C!

FTR, here is what I was doing, it's got output of tcpdump as well: https://gist.github.com/errordeveloper/c28ebae41b6d1b7e7ced

@errordeveloper ping

Out of interest, what's the plan on this?  Me and Ilya talked about reporting this to kernel developers, but even if anything comes of that, it is unlikely to have much singnificance on timescales that matter to weave.  So I'm wondering if there is something more?

IMO we should certainly report this to the kernel devs. Let's see what that reveals about the nature of the problem and when/where any fix might appear.

I already have some knowledge about the nature of the problem, although no idea how to fix it.
But if we report it and some kindly kernel developer takes it seriously and develops a fix (and I wouldn't get too hopeful about that), it's usually at least 3 months until such a change will appear in a released kernel.  And then a few weeks until the bleeding edge distros pick that up.  Even in the very best case, it's a few months.
And then there are RHEL and Ubuntu LTS, where we have to treat the kernels as more or less unchanging.
So it seems to me we ought to take our own position on this issue.  Maybe we don't actually think it is very serious.  Or maybe we do consider it serious, in which case we can think about workarounds (maybe a per-subnet iptables rule to prevent reception of multicast packets from other subnets?).
I do think we should report it in any case, but that's just because I think reporting bugs in open source software is The Right Thing To Do (whatever reception they encounter).

Where weave is right now, I reckon this issue warrants a couple of days work max. So if there is a reasonable chance of developing a workaround in that time then let's go for it.

Just an update for those who reading this, it's not a Weave bug.

@rade should it be retagged with kernel-bug or something similar? May be just removing bug tag would make sense..?

I'd leave the bug tag. The behaviour is buggy, regardless of the cause.

Didn't @dpw reproduce the problem on a single machine, or am I misreading that comment?

Didn't @dpw reproduce the problem on a single machine, or am I misreading that comment?

Yes, but I was still using weave and docker.  Though we might have confidence that those are not implicated when on a single machine, Ilya is trying to strip it down to the point where it can be reported to the Linux network developers with some chance of them paying attention.

@dpw it'd be great if you could have a look at the setup script. I have based on a ServerFault post. It does what's needed, but I am not quite sure what exactly is the role of the tap device there...

@dpw it'd be great if you could have a look at the setup script. I have based on a ServerFault post. It does what's needed, but I am not quite sure what exactly is the role of the tap device there...

Yeah, it looks a bit more complicated than I'd expect.  I'd expect you just need two netnamespaces connected to a bridge via veth pairs.   Like the instructions in https://github.com/zettio/weave/blob/master/docs/dockerless.txt , but without the third veth pair for the weave router.

@errordeveloper is trying to strip it down to the point where it can be reported to the Linux network developers with some chance of them paying attention.

Understood, but surely if the problem can be reproduced on a single machine, we should produce instructions - not involving docker or weave - for doing that. Currently @errordeveloper's setup appears to be using multiple vagrant VMs. I doubt that would go down well with the kernel devs.

Oh, just looking at the instructions again, they are using just a single vagrant VM? If so that's fine. Though I suspect even that is asking a bit much, especially since the VM is based on coreos and the Vagrantfile is far from simple.

Exactly, there is only one Vagrant VM, which is only a tool of avoiding human errors by repeated automation. My intention is to post generic instructions to the netdev list. A good reason to use CoreOS here is that it actually runs latest (or at least very recent) vanilla kernel release.

I see. So all the vagrant stuff is really just there for convenience; the setup script + multicast send/receive invocations should reproduce the problem on most Linuxes.
I guess we'd want to find something more standard than mcsend/receive. Would iperf work? or omping?

mint is another one.

@rade good point, I somehow overlooked that idea... I'll make sure to use something that few distros have packages for.

I guess we'd want to find something more standard than mcsend/receive. Would iperf work? or omping?

I doubt that the Linux kernel network developers consider any of those to be standard.
If mcsend/receive are what I think they are, then they are trivial C programs, and so probably acceptable.

@errordeveloper did you submit this to the linux kernel devs?

Submitted just now.

worth prodding?

Probably, but for best result we should CC some folks who might have otherwise not noticed the post. Any ideas who we could CC?

I have just tried this on a 4.2.0-35 kernel, and the behaviour is unchanged :(

One way to prevent this is to insert a couple of rules inside the receiving containers that drop packets to the multicast destination when they are not sent from an IP in the same subnet. E.g.,
# ./bin/docker-ns rcv iptables -I INPUT -d <IP_ADDRESS>/4 -j DROP
# ./bin/docker-ns rcv iptables -I INPUT -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/4 -j ACCEPT

We can insert these rules in weave attach.
That doesn't help when using the Docker Network Plugin though :(


Streetview widget is not working

Appreciating your efforts, the Streetview widget is not working even if i have used a working Google API key.
Thank you so much for your help.
Best Regards,
Dawit

The StreetView widget still not working with Calcite Maps (and other similar approaches) as the widget code is dependent on the TitlePane dijit. This should be fixed in the widget itself. Closing this issue since this is an issue for cmv-app, not specific to cmv-calcite-maps.


Make sure to link to the built copy of libtree-sitter.a

I've just realized that the script will build tree-sitter, but link to whatever copy pkgconfg reports. This means that the built runtime is not necessarily what is included in the xcframework.
If everything looks good, the binary included is the result of this invocation.

is it?
the PREFIX=$TMP_BUILD_DIR/build make install suppose to make the .pc flags file point to the build version, not to any particular.
here are the expected paths in .pc
install -d '/var/folders/5b/s1q90k655dg41bwfvwrmkw_c0000gn/T/tmp.wKgcty2o/build/lib/pkgconfig'
sed -e 's|@LIBDIR@|/var/folders/5b/s1q90k655dg41bwfvwrmkw_c0000gn/T/tmp.wKgcty2o/build/lib|;s|@INCLUDEDIR@|/var/folders/5b/s1q90k655dg41bwfvwrmkw_c0000gn/T/tmp.wKgcty2o/build/include|;s|<EMAIL_ADDRESS>\
	    -e 's|=/var/folders/5b/s1q90k655dg41bwfvwrmkw_c0000gn/T/tmp.wKgcty2o/build|=${prefix}|' \
	    -e 's|<EMAIL_ADDRESS>\
	    tree-sitter.pc.in > '/var/folders/5b/s1q90k655dg41bwfvwrmkw_c0000gn/T/tmp.wKgcty2o/build/lib/pkgconfig'/tree-sitter.pc

the intention of:
export PKG_CONFIG_PATH=$(pkg-config --variable pc_path pkg-config)${PKG_CONFIG_PATH:+:}${PKG_CONFIG_PATH}

is to override pkg-config paths to use the build one, not any other. It looks like this is where it fails, and result in
++ pkg-config tree-sitter --cflags
+ CFLAGS='-arch arm64 -arch x86_64 -mmacosx-version-min=10.13 -O3 -I/opt/homebrew/Cellar/tree-sitter/0.20.6/include'

^ that's unexpected indeed. I wonder if we can rather force pkg-config to use our .pc than hardcode paths. The flags for tree-sitter and for plugins are not necessarily the same flags. wdyt?

thanks!
I've applied a fix manually in https://github.com/krzyzanowskim/tree-sitter-xcframework/commit/c365565f76623fa939234002593d9135e00809a1 and released an updated build. Closing this PR for now.


bunnyhop legit ?

Read the code and you can see what you need to do "&& hops_hit > config.misc.max_hops_hit))" aka				config.misc.max_hops_hit <--- legit tells you were to put it


[7.x] Fix misleading docblocks in EnumeratesValues trait

The docblocks for whereNull and whereNotNull seem to have been swapped. This PR fixes that.
Cheers!

Will do 🙂


npm presence

Is this package published on npm? From your package.json it looks like it should map to coinbase package, but in the npm registry there is a different package with that name already (the official one). Would you mind publishing this one with a different name, so users can depend on this package by npm name instead of github remote?

This package is published under the coinbase package's 0.1.X version numbers. If you do an npm install<EMAIL_ADDRESS>you will get this package.
I wrote this package before coinbase offered any official node wrapper for their api. Since creating one, they reached out and asked if they could use the name going forward. At that point, we pointed the module's repo property to the new repository, under their name.


[AJ-1075] Fix copy status to clipboard in WDS troubleshooter

https://broadworkbench.atlassian.net/browse/AJ-1075
This fixes a bug introduced in #4042. Currently, when copying the status to the clipboard, the proxy URL is copied as "[object Object]". This fixes it to copy the actual proxy URL.

Integration test failure is unrelated (run-rstudio failed and that test is generally flaky).


Fix docstring (#5471)

Pull request opened by the merge tool on behalf of #5471

Merged in 72a8033b83e03602f8425e51511a33bc2909c519


Update UG.

Codecov Report

Merging #20 (b985410) into master (a99f694) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #20   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 a99f694...b985410. Read the comment docs.


Save current language in localStorage

With #283 this would be so much easier.
Also we can use navigator.languages to discover the preferred language of the users when they haven't selected their preferred language at first visit.


Set depth=all when checking out a specific branch

If we need a specific branch then we can't clone with depth=2 we need to use
depth=all; otherwise the checkout of the branch will fail

The periodic tests for the v0.7-branch are currently failing because the
checkout is failing because we can't checkout the requested
branch kubeflow/testing#498

This change is

/assign @gabrielwen

/retest

unittests failed trying to delete the directory I suspect it was related to recent issues with our NFS share.
/test all

/lgtm

/approve


middleware: slaving zones

Figure out how to implement and use a slave zone middleware that retrieves zones over AXFR, IXFR or rsync?

Let's take an example from my current setup:
zone "rikribbers.nl" {
    type slave;
    masters { <IP_ADDRESS>; 2a00:f10:121:400:252b:5421:6ba3:3d10; };
    file "/var/lib/bind/rikribbers.nl";
    zone-statistics yes;
};

So, this means a couple of things

be able to receive and act on incoming notifies
requery the master at intervals specified in the SOA parmeters
dropping the zone; SERVFAIL when expire is expired
ability to configure masters
where to put the zone (use assets path by default?  ~/.caddy)

Looking at https://www.knot-dns.cz/docs/1.6/html/configuration.html, need idea: no concept of slave zone (per se). It is just a keyword in the configuration. Rought idea for config syntax (btw: supermaster is also a cool idea).
rikribbers.nl {
	transfer db.rikribbers.nl master_ip/name...
}

transfer itself will have some more options
transfer {
	file db.rikribbers.nl
	from master_ip/names...
	<options 'n stuff>
}

transfer can work, it only need to point to a zonefile, or should we use some kind of abstraction that it allows to query other middleware what their zone looks like. The latter is nice, but I have no idea how this will look. As a first pass, using a file as an intermediate way of communicating should suffice.

otoh, slaving a zone (i.e. responding to axfr/ixfr) is highly middleware specific; not sure if this can be done as a generic middleware and should just be done in the (e.g.) file middleware. It boils down to sending notifies and then responding to transfer requests.
slaving zones might be diff., but (as said) not sure yet.

This will be an option in the file middleware.
If we ever get something that will read from a database, we'll revisit. Or maybe the whole read from thing must be abstracted and shared between middlewares?

Slaving zones is highly middleware specific and needs a better abstraction. For example a SOA serial strategy needs more thought before supporting more than 100 zone changes a day. Here is some light reading on that problem: https://lists.dns-oarc.net/pipermail/dns-operations/2016-March/014623.html

LOL ;-)

See the secondary middleware - not perfect yet, but working. Closing for now. Once all this stuff is functional we'll do another passover and make it perfect.


Old toolchains kept around, not updated

I have a browser bookmark to a local copy of Rust Nightly’s docs, kept up to date by rustup. Lately I had noticed discrepancies between that and doc.rust-lang.org, and assumed that Nightly was slightly late compared to master.
It turns out that, at some point, rustup started including the host(?) triple in the toolchain’s directory name, e.g. $RUSTUP_HOME/toolchains/nightly-x86_64-unknown-linux-gnu. But a $RUSTUP_HOME/toolchains/nightly directory (and beta and stable) was still there, with some never-updated older version, and that’s what I was looking at.
Should rustup.rs remove these old toolchains automatically?

This happened because of a one-time change in the naming structure here a few months back. I didn't bother to add any upgrade code (sorry...). This specific bug isn't going to come up again, but some additional code to clean up any directories (and files in the update-hashes dir) would be prudent (would have been more prudent in the past).


chore: update arrow datafusion to datafusion

Which issue does this PR close?

Closes #.
Rationale for this change

update arrow datafusion to datafusion
What changes are included in this PR?

Are there any user-facing changes?

Let's go

I noticed something like pr, closing, I will start learning to participate in this project


[FEA] Update GpuCoalesceBatchesSuite to work with AQE enabled

Is your feature request related to a problem? Please describe.
GpuCoalesceBatchesSuite tests fail when AQE is enabled, because they don't use the final execution plan when asserting that the plan is correct.
Describe the solution you'd like
I would like to be able to run the tests with AQE enabled.
Describe alternatives you've considered
N/A
Additional context
N/A

The coalesce HostColumnarToGpu test doen't make sense as written when AQE is enabled. It is checking that no part of the plan runs on CPU except for the Parquet scan, but when AQE is enabled, the Parquet scan becomes a query stage that runs on the CPU and results in transitions that the test is not expecting.
I don't think there is value in modifying this test to work with AQE and we should just ignore it if AQE is enabled.

Fixed in https://github.com/NVIDIA/spark-rapids/pull/567


Added currentSrc method

Implementation was missing for this method thus breaking compatibility with other plugins like analytics

Thanks for the PR :)


Fix doc --open crate name.

Fixes #1595.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @wycats (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Thanks for the PR! Could this re-use Target::crate_name, however to deduplicate logic?

Updated to use crate_name, still need to explicitly replace for --package however.

@bors: r+ ccfcc9008c3926d59ee614f98dd1c0c2a8b737c1
Thanks!

:hourglass: Testing commit ccfcc90 with merge e2372a8...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


fastly: 10.10.0 -> 10.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/fastly/cli/releases.
meta.description for fastly is: Command line tool for interacting with the Fastly API
meta.homepage for fastly is: https://github.com/fastly/cli
meta.changelog for fastly is: https://github.com/fastly/cli/blob/v10.11.0/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.11.0 with grep in /nix/store/mpv0k4nvh8ww8wbiqzvqjh8ckxhgm3c0-fastly-10.11.0
found 10.11.0 in filename of file in /nix/store/mpv0k4nvh8ww8wbiqzvqjh8ckxhgm3c0-fastly-10.11.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fastly

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mpv0k4nvh8ww8wbiqzvqjh8ckxhgm3c0-fastly-10.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fastly https://github.com/r-ryantm/nixpkgs/archive/18eab3db52842674432737dc5e1449ab000dee6b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/18eab3db52842674432737dc5e1449ab000dee6b#fastly

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mpv0k4nvh8ww8wbiqzvqjh8ckxhgm3c0-fastly-10.11.0
ls -la /nix/store/mpv0k4nvh8ww8wbiqzvqjh8ckxhgm3c0-fastly-10.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

fastly

Maintainer pings
cc @ereslibre @shyim for testing.

Result of nixpkgs-review pr 317872 run on x86_64-linux 1

1 package built:

fastly


Install Issues

Hello ,
Can help to look at the this install issue.
LM-SHC-16502628:swagmock qiangli3$ npm install swagmock
npm ERR! Darwin 16.7.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "swagmock"
npm ERR! node v6.11.2
npm ERR! npm  v3.10.10
npm ERR! code ENOSELF
npm ERR! Refusing to install swagmock as a dependency of itself
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/qiangli3/work/swagger/swagmock/npm-debug.log

probably named the project swagmock and NPM did not like it?
Saw this post and this might be related - http://thisdavej.com/node-newbie-error-npm-refusing-to-install-package-as-a-dependency-of-itself/


Import Error

ImportError                               Traceback (most recent call last)
 in ()
1 import python_speech_features
----> 2 from python_speech_features import mfcc
3 from python_speech_features import delta
4 from python_speech_features import logfbank
5 import scipy.io.wavfile as wav
ImportError: cannot import name 'mfcc'
How can i solve this error?

you're going to have to give me some more information.  I have just upgraded my version using
'pip install python_speech_features --upgrade' and it runs the code just
fine.
On Thu, Aug 17, 2017 at 9:51 AM, ngragaei<EMAIL_ADDRESS>wrote:

ImportError Traceback (most recent call last)
in ()
1 import python_speech_features
----> 2 from python_speech_features import mfcc
3 from python_speech_features import delta
4 from python_speech_features import logfbank
5 import scipy.io.wavfile as wav
ImportError: cannot import name 'mfcc'
How can i solve this error?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jameslyons/python_speech_features/issues/49, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABn1QWQBBqWpwPYBbdar4rGqlFpufF14ks5sY4BygaJpZM4O5nhO
.


DrugBank ID being dropped between untyped compendium and final ChemicalEntity compendium

We have the following entry in babel_outputs/intermediate/chemicals/partials/untyped_compendium:
{'MESH:D014568', 'DrugCentral:5109', 'UMLS:C0042071', 'UNII:83G67E21XI', 'CHEMBL.COMPOUND:CHEMBL1201420', 'RXCUI:11055', 'DRUGBANK:DB00013'}

However, when we look at the final clique in babel_outputs/compendia/ChemicalEntity.txt, it looks like this:
{"type": "biolink:ChemicalEntity", "identifiers": [{"i": "UNII:83G67E21XI", "l": "UROKINASE", "d": [], "t": []}, {"i": "MESH:D014568", "l": "Urokinase-Type Plasminogen Activator", "d": [], "t": []}, {"i": "UMLS:C0042071", "l": "urokinase", "d": [], "t": []}, {"i": "CHEMBL.COMPOUND:CHEMBL1201420", "l": "UROKINASE", "d": [], "t": []}, {"i": "DrugCentral:5109", "l": "urokinase", "d": [], "t": []}, {"i": "RXCUI:11055", "d": [], "t": []}], "taxa": []}

So why was the DrugBank ID dropped? The simplest explanation would be that it's not a preferred prefix for ChemicalEntity, but it is. So what's going on?

DrugBank identifiers are present in Babel 2024mar14 but not in 2024jul13. Those two releases are very similar, so it's either one of the few changes we made between them or some error we're running into in reading the Biolink model information.

This has somehow fixed itself in PR #335 -- as far as I can tell, all I did was update the Biolink Model version, but I'm not sure how that would have caused a problem. I'll add this to my tests and then close it.


Misc.: Use github action to run CI on linux and macos

closes #3272

CI working with github actions for linux, macos and windows.
It seems, it needs to be on master branch to start working, so for looking at the result, see on my fork: https://github.com/t20100/silx/actions/runs/499115931
Here is the matrix of effectively tested features:

os
GUI
OpenGL
OpenCL

linux
✓
✓
✗

macos
✓
✓
✓

windows
✗
✗
✗

CI working with github actions for linux, macos and windows.
It seems, it needs to be on master branch to start working, so for looking at the result, see on my fork: https://github.com/t20100/silx/actions/runs/499115931
Here is the matrix of effectively tested features:

os
GUI
OpenGL
OpenCL

linux
✓
✓
✗

macos
✓
✓
✓

windows
✗
✗
✗

Any idea why OpenCL is failing on linux ? it should work, no ?

Any idea why OpenCL is failing on linux ? it should work, no ?

I just checked with pyFAI, and the OpenCL part is also skipped on GH-actions
LGTM.

I just checked with pyFAI, and the OpenCL part is also skipped on GH-actions
LGTM.

Thanks for the merge! Let's see how it goes...
For OpenCL on linux, only ocl-icd-opencl-dev is installed so there is probably no OpenCL device installed (I took it from our .travis.yml)

Thanks for the merge! Let's see how it goes...
For OpenCL on linux, only ocl-icd-opencl-dev is installed so there is probably no OpenCL device installed (I took it from our .travis.yml)

Looking at it, https://github.com/silx-kit/silx/blob/master/ci/intel_opencl_icd.sh is no longer called.

Looking at it, https://github.com/silx-kit/silx/blob/master/ci/intel_opencl_icd.sh is no longer called.


How to disable pa_encoding_from_string feature?

I'm on Ubuntu 18.04 which comes with PulseAudio 11 as best as I can tell. I'm trying to write something that uses pulse-binding-simple, but I can't work out how to disable the pa_encoding_from_string feature which is on by default. I can disable it for pulse-binding but it seems to be enabled again as soon as I try to use pulse-simple.

Sorry for the oversight, I have added the feature flag to the simple and mainloop-glib crates to extend control of it and published the change in v2.2.2, which hopefully will fix that for you :)

Do you have an example of how this would work? I tried default-features = false on the simple crate, but the feature was still enabled.
See https://gist.github.com/thejpster/92d791374f8f20c2ae42a4cb10e4dfe2, using
[dev-dependencies.libpulse-binding]
version = "2.2"
default-features = false

[dev-dependencies.libpulse-simple-binding]
version = "2.2"
default-features = false

no I don't sorry, and I'm a little too busy just at the moment to investigate, so appologies in any delay if a further fix is needed
oh, you could try setting features to an empty set instead of the default-features mech
features = []

Of course there is also always the option of filing a bug report against the package to get the maintainer to backport the symbol file fix :)

Ok, I've spent quite a bit of time on this and I can't get these bindings to build. If I try and disable the default flags in the libraries I'm using, using my App's Cargo.toml, the flag remains enabled - seemingly via some dependency chain I can't control.
I've proposed #8, which disables the flag by default, allowing people to opt-in if they need it and they've got an OS that supports it.

@thejpster Apologies for the delay. I managed to find a few minutes yesterday to look at this more, and I believe I have fixed it now in v2.2.3.

Thanks, v2.2.3 works for me.


termbox library panic

Sometimes sshs crashes with the following runtime panic:
panic: runtime error: slice bounds out of range

goroutine 40 [running]:
github.com/nsf/termbox-go.PollEvent(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/Users/iwittkau/go/pkg/mod/github.com/nsf/termbox-go@v0.0.0-20180819125858-b66b20ab708e/api.go:348 +0x91e
github.com/jroimartin/gocui.(*Gui).MainLoop.func1(0xc0000e2240)
	/Users/iwittkau/go/pkg/mod/github.com/jroimartin/gocui@v0.4.0/gui.go:354 +0x30
created by github.com/jroimartin/gocui.(*Gui).MainLoop
	/Users/iwittkau/go/pkg/mod/github.com/jroimartin/gocui@v0.4.0/gui.go:352 +0x57

Looks like termbox-go AND gocui are not actively maintained anymore.
We should try to move to tcell which conveniently has a termbox compatibility package.


Add Retention for aggregation

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：
Problem Summary(Required) ：

Add Retention to calculate retention rate.
input/output of Retention is both Array.

retention is a aggregate function to compute from input(array) to output(array), result is consist of (0|1) value, It's format is follows:
ARRAY retention(Array[cond1, cond2, cond3, cond4...]);
cond is predicates, and

The 1th element of output ARRAY is compute with cond1.
The nth(n > 1) element of output ARRAY is compute with(cond1 && condn).

Its' usage, For example,
Get the proportion of people who place payments on January 2, 2020 that included by total people click on January 1, 2020:

SELECT retention[1],
       retention[2],
       retention[2] / retention[1] AS retention
FROM
  (SELECT retention((toDate(TIME) = '2020-01-02' AND event_type = '点击'),
  (toDate(TIME) = '2020-01-03' AND event_type = '支付')) AS retention
   FROM test_retention where toDate(TIME) IN ('2020-01-02', '2020-01-03')
   GROUP BY UID) t;

@Pslydhh Can you provide some detail information for this function. better to give some examples.

@Pslydhh Can you provide some detail information for this function. better to give some examples.

I've add definition and usage of retention, but maybe need adjust its format later.

run starrocks_be_unittest

run starrocks_clang-format


Adds GitLab Pages example

Adds a GitLab Pages example, and a general section for WASM code size specific to CSR applications.
I am not sure if the WASM code size things are well-placed there, but I felt like I should mention them here.
If not, feel free to move that section elsewhere.

Thanks for taking the time to make a PR.
Two things

There's already a whole chapter on optimizing WASM binary size. Maybe you could look it over, compare to what you've written here, and add anything that's missing to that chapter?
Adding GitLab Pages at the top of the list makes the diff for this very hard to read, because git interprets that as deleting all of the GitHub Pages content and replacing it, and then adding it back in below. Could you edit this so GitLab Pages is appended to the end of the list as a fourth option, rather than inserted at the top as the fourth option? That will make it much easier for me to review.

Thanks!


Auto-import sub-modules

Note that the default Module decorator does not set any reflect metadata, so there's not really a good way to tell if something is a module. Instead, we should define metadata on the module class from the AutoloadModule decorator, which we can use to recognize them.

After giving this some more thought, this might not be a good idea since it's not a given that a module should include all modules in its direct subdirectories... Closing (for now)


Revert [SPARK-27300][GRAPH] Add Spark Graph modules and dependencies

This reverts commit 709387d66003b9f9c847488c101156a71231eddf.
See https://issues.apache.org/jira/browse/SPARK-27300?focusedCommentId=16990048&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16990048 and previous mailing list discussions.
What changes were proposed in this pull request?
Revert the addition of skeleton graph API modules for Spark 3.0.
Why are the changes needed?
It does not appear that content will be added to the module for Spark 3, so I propose avoiding committing to the modules, which are no-ops now, in the upcoming major 3.0 release.
Does this PR introduce any user-facing change?
No, the modules were not released.
How was this patch tested?
Existing tests, but mostly N/A.

CC @s1ck @dongjoon-hyun @mengxr @rxin

Test build #115464 has started for PR 26928 at commit 156bb72.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20266/
Test PASSed.

Test build #115464 has finished for PR 26928 at commit 156bb72.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115464/
Test FAILed.

Test build #115466 has started for PR 26928 at commit 54b7740.

Although I merged the original PR, I'm +1 for @srowen 's decision according to the current AS-IS status.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20268/
Test PASSed.

This is a dependency and module PR and all build combination test passed by GitHub Action.
Jenkins UT result is irrelevant because there was no added tests before.
Merged to master.

Test build #115466 has finished for PR 26928 at commit 54b7740.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115466/
Test PASSed.

Thx @srowen for picking this up. I closed the related PRs ... Farewell!


containerd runtime v2 logging plugin args parsing refacto

What is the problem you're trying to solve
the containerd runtime v2 logging plugin args are not well formatted which makes their parsing quite difficult.
In this nerdctl PR https://github.com/containerd/nerdctl/pull/959  I am customizing the behavior of the logging plugin by passing some parameters in the logURI : "binary://BIN?max-files=1&max-size=10"
URI is parsed into Args {BIN, max-files, 1, max-size, 10} => makes the task of parsing quite difficult
Describe the solution you'd like
"binary://BIN?KEY1=VALUE1&KEY2=VALUE2"  ==> {BIN, KEY1=VALUE1, KEY2=VALUE2}
What would be the impact of this refacto ?
Additional context
No response

Sounds like a breaking change.

makes sense


Notify users about latest stable version of every minor release line

longhorn/longhorn#3014

@PhanLe1010 because you introduce a new setting, please also update the manifests and charts of longhorn/longhorn, longhron/longhorn-manager.

@innobead
This setting is a hidden system setting. I think we don't need to modify any chart similar to the latest version setting

@innobead
This setting is a hidden system setting. I think we don't need to modify any chart similar to the latest version setting

Thanks for the clarification!


Does unirest support other request methods like PROPFIND, VIEW, LINK ?

Hello
I added Unirest.customMethod() in the code for VIEW request but it doesn't seem to be working. Is there any workaround in unirest to support methods other than the six listed in the docs ?

We are preparing a new version which does support this. Stay tuned it should be soon. If you need it today the OpenUnirest project which will be merged into this one supports it https://github.com/OpenUnirest/unirest-java

Hello, this should be resolved or addressed in Unirest 2. Please see the upgrade guide for important changes.


0.23.1 error: Tried to set an option (hideLegend) that was not declared

Search terms

Expected Behavior

Version 0.23.1 generates documentation successfully as it did for previous versions 0.23.0 and 0.22.17.
Actual Behavior

Typedoc fails with the error message in the issue title.
Steps to reproduce the bug

The pull request opened by Renovate: https://github.com/jstritch/easy-git-annex/pull/11
Environment
Repository: https://github.com/jstritch/easy-git-annex

Looks like I missed mentioning that in the release notes - that option has been removed, the theme no longer has a legend.

Thanks for the fast reply.

After removing hideLegend and updating the link syntax, my documentation builds successfully.
https://jstritch.github.io/easy-git-annex/
Thanks again. Enjoy the rest of your day!


Update docs to clarify that new app pipeline is automatically generated.

What
Updated docs as title indicates. Based on feedback that it was unclear how a new app's pipeline is created.  Also removed redundant step regarding bootstrapping pipelnes.
How to review
Check update is accurate.
Who can review
Anyone

should we change this to a sidenote at the instead of removing? the pipeline for me definitely didnt get auto generated
Pipelines should be auto-generated. This will serve as a prompt to investigate the auto-generation if there are issues in this area in the future


update mraa and node-red-gpio from upstream

Update mraa and node-red-gpio from upstream with latest versions, removing all unneeded patchsets which were ported.

When will it be possible to (also) pull the nod-red nodes via the palette from npmjs.com?

I think it's not possible due to difference between mraa ids inside types. It's possible to update to latest version of package in palette manager unfortunately.

In case users want to update to a custom Node RED version and then install the IO nodes themselves.

I've checked update from 0.0.6 version to 0.2.0, seems works fine for me. It is possible with manual update:
cd /usr/lib/node_modules/node-red/node_modules/; npm install<EMAIL_ADDRESS>-g;


Use cases

Provide a few use cases and confirm features of hypercomplex numbers.
Describe the solution you'd like
Jupyter Notebook
Additional context
Redirect from README.md to this file.

Finished in e8e6ac0.


Deature/peer peers

@brokenprogrammer
Adds the logic of peers adding other incomming/outoing peers. This is still centralized amongst the seeder and not really a network yet, but a small step in the right direction.

I am looking into https://github.com/libp2p/js-libp2p as a candidate for the network layer / communication protocol. It is an implementation of an industry consensus standards and comes with a lot of nice functionality such as a secure Kademlia DHT implementation, which is pretty much what we are looking for.

closing in favor of https://github.com/feldmanchain/feldmanchain-on-prem/pull/4


partners numbers not synced

Seems that the banner is undercounting the contributions.

@dalekunce I think this might just be an issue of what we labeled those as. Looking at the all example, 57,749 matches what we have on the leaderboards under changesets.
My assumption is the mis-match in values might be happening because the total displayed under the Teams are a summation of buildings, roads (by #), and potentially other edits as well.
Will look into this to verify, but I imagine changing the term to 'total edits' might be a good idea even if just initially.

@dalekunce - We were using changeset submissions as the metric for contributions in several areas across the site. With the latest update, "Contributions" now refers to the sum of all additions and edits, both in the partner page and on the leaderboard.
There were some additional discrepancies in the road and building counts caused by not filtering for unique changesets, which have been rectified.


Include uvx binary to docker image.

Fix #4763
Summary
Modify the Dockerfile to include the uvx binary in the docker image ghcr.io/astral-sh/uv.
Test Plan
I have verified that the uvx binary is included in the Docker image built with the following command and can be executed.
# cd repository root
docker build -t uv:add_uvx .
docker run --rm --entrypoint /uvx uv -V

uv-tool-run 0.2.21

Thank you.


[maser] Separate performance tests [6945]

Port of #884 to master

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows

Failed test not related.