Moose ids

Pull Request Description
What issue does this change request address?
#377
What are the significant changes in functionality due to this change request?
Updates the moose id and updates RAVEN to work with the new MOOSE.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

 FAILED (1)

But this failure goes away if we run the test individually.

The windows failure was because it was missing the prereq that generated the test_more.xsd file.


Add quickPass option to skip heavy tests in tornado-test script

Description
Testing script runs the complete unit-test suite when is invoked. The test suite contains some test that they try to stress the device memory or rely on stable internet connection (high timeout). Thus, testing the whole suite during local development can cause  overhead.
This PR add an option in the test script to do a quick pass, by skipping these tests that cause they delay. This option by default is disabled and they user needs to explictly add it.
Backend/s tested
Mark the backends affected by this PR.

[x] OpenCL
[ ] PTX
[ ] SPIRV

OS tested
Mark the OS where this PR is tested.

[x] Linux
[ ] OSx
[ ] Windows

Did you check on FPGAs?
If it is applicable, check your changes on FPGAs.

[ ] Yes
[ ] No

How to test the new patch?
make jdk21
tornado-test --ea --verbose --quickPass

Add also a new rule in the Makefile: make quick-tests something like that..

Done
The option is make fast-tests


YouTube Page Format Changes

This isn't a question directly about YouTube-dl, but I rather I'd like to know how you guys handled the issue.
Recently, YouTube appears to have changed their format. as discussed here. For some videos, there is no longer a "ytplayer.config" section, and there is instead a "RELATED_PLAYER_ARGS" section which I believe contains the data... not yet sure if it's the same format or what else changed.
If I look in my browser, RELATED_PLAYER_ARGS is there with a lot of data inside. If I download from a software, however, the tag comes out empty as 'RELATED_PLAYER_ARGS': {"rvs":""},
How are you dealing with this, and what else is there to know about these latest changes?
Thanks

The only thing I could do now is waiting for a good genius to fix this.. 👍

Nothing really changed for Firefox UA.

Yeah I agree.. perhaps nothing really changed, because these two beasts still work flawlessly..
1- http://www.saveitoffline.com/#https://www.youtube.com/watch?v=SkRSXFQerZs
2- http://en.savefrom.net/#url=http://youtube.com/watch?v=SkRSXFQerZs&utm_source=youtube.com&utm_medium=short_domains&utm_campaign=www.ssyoutube.com


GetOrAdd called for the same type by multiple threads simultanously

While inspecting this implementation I've noticed the GetOrAdd usage here could be problematic.
Say, if two threads get in the add factory method for the same loader at the same time, wouldn't both threads receive a different loader but only one get stored in the dictionary? (Which would mean only one will get executed and as a result the users code will deadlock).

Never mind, did an extensive multi-thread test on GetOrAdd and while it is possible the factory method gets called twice, it will still return the previously added instance in that case.


How to use?

How to use beyond info on card? https://huggingface.co/oliverguhr/fullstop-punctuation-multilang-large/tree/main
from transformers import AutoTokenizer, AutoModelForTokenClassification
tokenizer = AutoTokenizer.from_pretrained("oliverguhr/fullstop-punctuation-multilang-large")
model = AutoModelForTokenClassification.from_pretrained("oliverguhr/fullstop-punctuation-multilang-large")
thanks in advance
EDIT: nevermind, I found a related issue on Github
https://github.com/huggingface/huggingface_hub/issues/532

Hi @gnmarten,
thanks for the feedback. I added the sample code to the model card.
Just that you know: The pipeline code will only process the first 512 token of your input text and truncate the rest.


in production mode, multiple concurrence, run a moment, throw error.

{ AdapterError: Unexpected error from database adapter: `select` failed ("badConnection").  A connection either could not be obtained or there was an error using the connection.
Additional data:
 { error: Error: Pool is closed.
    at Pool.releaseConnection (/mnt/www/-new/releases/20180926072024/node_modules/mysql/lib/Pool.js:140:36)
...

db mysql, may the reason?

@wuyuedefeng Can you please give me some more information about your project? What version of sailsjs? What is the DB adapter name and version? Also maybe include some code for how you have configured your DB.

Hi @wuyuedefeng with out further information we can not move forward with this issue. I hope you had success in resolving it! To help clean up Sails issues we are closing issues that have not had movement in some time.


[npm 3] Get the packager and CLI to work with npm 3

After npm installing on master (Node 4.1.2, npm 3.3.6) running the packager works fine but trying to load the UIExplorer prints lots of messages like "Unable to resolve module LinkedStateMixin". These unresolved modules do exist under node_modules, so my suspicion is that these files are blacklisted and npm 3's deduping removed the non-blacklisted copy. If this is actually the case and npm 3 is deterministic, then we could blacklist the files that are getting deduped away.

Didn't have much to do tonight so I took a look at this, it looks like it's more of a problem with Watchman, and perhaps how npm has structured things (although I can't see any visual differences there).
On npm 3.3.6, I see this output from repeated 5 times:
[1:03:20 AM] <END>   Loading bundles layout (0ms)

React packager ready.

Recrawled this watch 1 times, most recently because:
/Users/ajwhite/Development/Labs/react-native: kFSEventStreamEventFlagUserDropped
To resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del /Users/ajwhite/Development/Labs/react-native ; watchman watch-project /Users/ajwhite/Development/Labs/react-native`

I pulled up a couple npm versions to compare the difference between running the packager on npm 3.3.6 and npm 2.14.4 (my default). It became clear that watchman was not fully scanning node_modules directory trees.
I was able to narrow it down to looking at the output in crawlers/watchman.js where the files get picked up. I updated that line to:
//..
if (filePath.indexOf('react-tools') > -1) {
  console.log('react-tools file:', filePath);
}
//..

This yields two very different results on npm 3.3.6 and 2.14.4. Here's the comparison of the files that watchman was able to discover between the two in node_modules/react-tools:
Failing version, npm 3.3.6
You'll notice it never goes past
/Users/ajwhite/Development/Labs/react-native/node_modules/react-tools/node_modules/commoner/node_modules/ and ends up skipping all the import files required for the ResultionRequest.resolveDependency method to discover.
Put in gist to avoid 100 lines:
https://gist.github.com/ajwhite/c82ac755389e62350657
Working version, npm 2.14.4
Here, you'll see that they're all discovered
https://gist.github.com/ajwhite/c82ac755389e62350657

This can be reproduced on my npm3-investigating branch.
TL;DR - Nothing in node_modules/react-tools/src ends up getting scanned and thus never becomes added to HasteMap. I only looked as far as node_modules/react-tools, but I'd assume it is an issue for other dependencies. I'm lead to believe this may be an issue with watchman.

The packager blacklists certain paths: https://github.com/facebook/react-native/blob/0ad05043f5f268c6241d34997ca8773b1e88357b/packager/blacklist.js#L15. What happens if you comment some of these out?

I fully commented those out, added others in; nothing.
Gimme 2 mins, I think I got the issue..

Ha.. gotta love this..
watchman shutdown-server. Then run the packager again.
@wez leads to this over in https://github.com/ember-cli/ember-cli/issues/4101#issuecomment-103299380

:sleeping: one of those nights where you find the simple solution after doing everything but that.
Perhaps if that error is caught, and npm is >= 3.x, it can be warned in the console to run watchman shutdown-server.

That recording goes by too quickly for me to see what's going on, and your commentary isn't clear to me (I don't use react-native either, so I'm at a disadvantage), so forgive me if this sounds like a stupid question:
Are you saying that the problem was resolved by restarting the watchman service?
Does the problem recur if you downgrade and upgrade npm again?
If so, could you try a HEAD install of watchman and see if the issue is resolved?
I'm thinking that maybe you hit the problem solved by https://github.com/facebook/watchman/commit/11b1f4abebebf4893e294c85314e27f80d9aa71d

I'm mobile at the moment, but I can expand upon what I had briefly described.
The problem seemed to arise after running watchman on the project that had been installed with npm <3, and then later reinstalled with npm >=3.
It appears to only be after the scenario of upgrading npm, and reinstalling the project with the newer version.
This issue did not surface again after restarting watchman. That appeared to resolve the problem.

@ajwhite Thanks for investigating. Looks like we're good with npm 3 and restarting Watchman will do the trick until the new version is published.
Also I just tested installing the CLI tools and setting up a new project with npm 3 and the sample app worked fine.

@ajwhite please open an issue in https://github.com/facebook/watchman/issues if watchman HEAD doesn't resolve this for you; thanks!

What is the solution to this issue with LinkedStateMixin not being resolved?

Well, unfortunately it does not work well with npm3 flat structure, because it takes some react-tools from the packages I depend on and put in in the top level, whereas it still keeps react-tools inside react-native because of different version. That causes collision name error and makes it impossible to run packager. Any ideas?


Multidimensional metrics

Changes the concept of a metric: originally it was a name and values/aggregated value, now it is a dimension—a name plus an optional source—and values/aggregated value.
Parses source expressions ("source=...") in log lines.
Passes the source—if present—to Datadog as a tag.

@dannygreg: Mind giving this a look-over?


Build Option failBuildOnCVSS of 10.0 fails on 9.8

Describe the bug
If the pom.xml sets the option failBuildOnCVSS to 10.0, the build fails on a 9.8 vulnerability. I am guessing that rounding is occurring in the check.
Version of dependency-check used
The problem occurs using version 7.0.0 of the maven plugin.
Log file
When reporting errors, 99% of the time log file output is required. Please post the log file as a gist and provide a link in the new issue.
For example,
Caused by: org.apache.maven.plugin.MojoFailureException:
One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '10.0':
log4j-1.2.17.jar: CVE-2022-23307(9.8)
See the dependency-check report for more details.
To Reproduce
Steps to reproduce the behavior:

Set 10.0
Have the pom declare a dependency on log4j 1.2.17
Run build with plugin
See error

Expected behavior
If the score is set to 10.0, it should not fail on less than 10.

It fails the build if CVSSv2 or CVSSv3 is on or above the threshold.
https://github.com/jeremylong/DependencyCheck/blob/af5d6dc376d5ca9ac6192764736bb65680c4d9b3/maven/src/main/java/org/owasp/dependencycheck/maven/BaseDependencyCheckMojo.java#L2421
And... that's the case for the CVE, as CVSSv2 score is 10.0

Better link would be https://nvd.nist.gov/vuln/detail/CVE-2022-23307 - you can see the CVSSv2 score.  The issue is not every vuln has a CVSSv3 and not every vuln has a CVSSv2...

Thanks for the explanation!


Implement register-egf command in CLI

Referring to the cli.yaml file, the register-egf command has not been implemented

@michaeldboyd Is this still an open issue?


Testing on SQLite with Pulse installed

Pulse Version
v1.0.0-beta5
Laravel Version
v10.34.2
PHP Version
8.2.10
Livewire Version
v3.2.6
Database Driver & Version
SQLite 3.41.1 (pdo_sqlite library) on macOS 14.1.1 arm64
Description
Pulse doesn't support SQLite.
Fine, no problem - I don't wish to run Pulse in SQLite anyway.
However - I run my tests through Pest using an SQLite database.
When Pest runs the database migrations, the create_pulse_tables migration throws the following error:
Unsupported database driver [sqlite].

  at database/migrations/2023_06_07_000001_create_pulse_tables.php:34
     30▕             $table->text('key');
     31▕             match ($driver = $connection->getDriverName()) {
     32▕                 'mysql' => $table->char('key_hash', 16)->charset('binary')->virtualAs('unhex(md5(`key`))'),
     33▕                 'pgsql' => $table->uuid('key_hash')->storedAs('md5("key")::uuid'),
  ➜  34▕                 default => throw new RuntimeException("Unsupported database driver [{$driver}]."),
     35▕             };
     36▕             $table->text('value');
     37▕
     38▕             $table->index('timestamp'); // For trimming...

I would expect the same result through vanilla PHPUnit, but haven't tested that directly.
Is there a better way of doing this? Can the migration check to see whether it's running in the testing environment and fail silently?
Steps To Reproduce

Create a new Laravel project
Install Pest
Install Laravel Pulse
Run php artisan test

See pull request https://github.com/laravel/pulse/pull/178.


Add how to build

Hi, I've added "How to build" into README.md.
I think it would be helpful!

Thanks @yenchenlin1994! Can I ask you to make a minor change? Rename "how to build" to "how to build with app container support" and add "set shouldUseAppGroupsForStorage to true in KTCoreDataStack.swift and KTSharedUserDefaults.swift ".
In commit  https://github.com/kenshin03/Cherry/commit/668e89f5e5a95a3d7ffb715fc3091ef6354da9e1 I added a switch "shouldUseAppGroupsForStorage" to the above classes and defaulted it to false so people won't get into the app group problem. The app should still work fine although there'll be no data sharing.

OK! I got it.
Done!

Thanks a bunch!


Autocomplete makes Zed use 800% CPU

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
Autocomplete is broken.
Open any project, write something fast like "kjfdsafalasdfjaslk". Watch CPU go 800% and memory is just balooning 11GB now. I think I read there was something done to the autocomplete thingy recently, maybe it is time to revisit that code.
The RPC log is spewing completionItems/resolve and I see "dokumentation" from
{"jsonrpc":"2.0","id":2393,"method":"completionItem/resolve"......

I can reproduce this consistently within JS/TS projects, seems to be an issue with elixir too but not as bad.
Edit: https://zed.dev/blog/zed-weekly-23  <-- think this could be the problem :/
Environment
Zed: v0.112.3 (preview)
OS: macOS 14.0.0
Memory: 64 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
We all know how this is supposed to work :) I mean, superhappy with Zed in general but something is broken with this autocomplete implementation.. maxing out the CPU and chewing memory.
Please let me know how I can assist further.
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

I think it is a little better on the stable channel, butI can easily get zed to chew up several GBs of memory after like 3 minutes use. CPUs also skyrocketing.
Zed: v0.111.6 (stable)
OS: macOS 14.0.0
Memory: 64 GiB
Architecture: aarch64

A fix for this has just gone out! The issue was that we were continuing to resolve documentation for stale or no-longer-visible completion entries as you continued to type, so if there were enough completions, and the server was slow enough, and the user was typing fast enough, they could build up significantly.
Why you were seeing it be better on the stable build we're unsure as it had the same behavior, I'm wondering what else, if anything, might be going on so I'd be curious to hear if you still experience high memory utilization after updating our latest update (preview or stable).

Thanks for looking into this! In some cases I got like 30K language server rpc messages before it was done (thank you node_modules).
Just give me a few moments and I'll see if I can break it again 😸
It might just have been me thinking it was less broken on the stable channel, maybe I just tried it on a smaller project. I do not remember the exact circumstances. I wouldn't stay sleepless over that if were you.

geez, someone should revoke my computer license 🤦🏻  it is having the LSP debug panel open that makes Zed go bananas with CPU and RAM.
Anyways, initial testing on preview 0.114.0 looks very promising. I'm will be very happy to move back into Zed again after a brief hiatus in vscode. Keep up the good work!


Use pino for loging

Pino will send better logins, easier to parse and read for loggly, kibana, etc.

Done, it also send events


Is it Python 3

Original is Python 2
What is very limiting

Original is Python 2
What is very limiting

yes, it's in python3, as we are only using a minimal set of python, if print and division got modified correctly, the original tensorflow version should also be fine to run in python3.


[Question] Blocking retry dashboard

Hi,
In video sessions of Greyhound, there is an information about a dashboard to skip the blocked message or identify the block in consumption.

Is this part of an open source project? If not, is there a way to extract this information from Greyhound?
Thanks
Satya

Hi @Satya758 ,
The dashboard about blocked messages is an internal wix backoffice app (which is quite tricky to open-source) that makes it easier for Wix developers to monitor and debug production. there is a standard grpc endpoint that all services expose and that in turn call Greyhound api to get the relevant information. e.g. blocked messages.
The Greyhound RecordConsumer api for production debugging is called state and it looks like this. (Unfortunately it is currently only available in the Scala-ZIO API I linked.)
Which API are you using? It can actually be quite easy to add this capability to java API here in GreyhoundConsumers interface.
I will add this task (expose state in java api GreyhoundConsumers) to our backlog. If you want to speed things up and contribute, I will gladly assist in guiding you on how to do this.

Hi @natansil
Thanks for the tip, We are using Scala ZIO API, I will have a look into it.
Thanks


TypeError: Cannot read properties of undefined (reading 'getReader')

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome - latest
Operating system and its version: macOS Monterey 12.0.1
PDF.js version: 2.13.216
Is a browser extension: No
Node version: 14.18.2
We are NOT using the provided viewer app. We're building out our own viewer via React.

Steps to reproduce the problem:
We currently trying to upgrade a lot of our dependencies including our bundler (webpack 4).  We upgraded worker-loader to 3.0.8, so we decided to upgrade pdfjs to latest as well. Our pdfjs worker version matches the pdfjs version and we're able to successfully call on pdfjs.
      const loadingTask = pdfjs.getDocument({
        url: props.documentUrl,
        withCredentials: false,
      });
      const downloadedDocument = await loadingTask.promise;

However we are now running into an error when trying to resolve the loadingTask.

We are using the provided pdf from the demo (compressed.tracemonkey-pldi-09.pdf).
We're not sure what the error means and was hoping to get insight on it.

Please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

It looks like ReadableStream support may be missing going by getReader being called on an undefined object instead of a valid ReadableStream (see https://github.com/mozilla/pdf.js/blob/54d4d345d31abead560e1bc54138af6b9baadd6b/test/unit/util_spec.js#L148-L151 for example), but it's impossible to tell for sure without more information as requested above.

This issue happend to me in case project implement MirageJs. when setup MirageJs server to mock api, look like MirageJs modified ReadableStream somehow and pdfjs failed when try read document by url. Remove Miragejs server on project make pdfjs work again


docs(FieldConfig): add a description for properties of the config.

What kind of change does this PR introduce? docs update

This change is

Codecov Report

Merging #563 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #563      +/-   ##
==========================================
- Coverage   93.95%   93.94%   -0.01%
==========================================
  Files          16       16
  Lines         728      727       -1
  Branches      207      207
==========================================
- Hits          684      683       -1
  Misses         44       44

Impacted Files
Coverage Δ

src/core/src/core.ts
100% <ø> (ø)
:arrow_up:

src/core/src/core.module.ts
93.75% <ø> (-0.37%)
:arrow_down:

src/core/src/services/formly.form.builder.ts
97.04% <100%> (ø)
:arrow_up:

src/core/src/components/formly.field.ts
92.24% <100%> (ø)
:arrow_up:

src/core/src/components/formly.form.ts
90% <100%> (ø)
:arrow_up:

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 c383a97...bbae6e6. Read the comment docs.


[Automation] Generate Fluent Lite from resourcehealth#package-2022-10

[Automation] Generate Fluent Lite from resourcehealth#package-2022-10

/azp run java - resourcehealth - mgmt - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-resourcehealth

/azp run java - resourcehealth - mgmt - tests

/azp run java - resourcehealth - mgmt - tests


My project won't open (corrupted JSON?)

ace attorney.zip <--- the project
So I was working on my game, saved it, and closed it like I always do. I then went to open it the next day, and it wouldn't open. The window flashes for a SPLIT second, and crashes the program instantly. I didn't move/delete/touch/edit ANY files or folders, I swear. (this was made with the dev build btw if that matters)
Apparently somehow, my GBSPROJ file got turned into a Binary instead of a JSON file? (according to someone on discord) and I just want help. idk if this can be recovered but i'm completely devastated. I've been working on this game really hard for a while now, and losing it hurts, even if its just a dumb little game.

Unfortunately I don't see any way to recover the GBSPROJ file in that project, looking at it in a hex editor the entire file is file with "0" characters. I've heard of this issue happening only to one person previously and luckily they had a very recent backup.
You say this is on the dev build, could you let me know which operating system are you using (Windows 10?). Any further information you can provide would be a great help.
My theory is that this may be caused by the application closing midway through saving the project but I'm unable to reproduce this from my Mac and I wonder if the issue only affects Windows projects.
If anyone is able to look into this the relevant code is likely around these areas:
https://github.com/chrismaltby/gb-studio/blob/3d87786f434b71feac378158dbb957df078c9739/src/actions/index.js#L198-L214
and
https://github.com/chrismaltby/gb-studio/blob/develop/src/lib/project/saveProjectData.js
The actual file writing is using the fs-extra module but I doubt this is the issue as for this write function it's mostly just a Promise wrapper around the fs.writeFile
https://github.com/jprichardson/node-fs-extra
@bracketJacket I wish there was more I could do to help you here but it doesn't look like there is. I really hope you have some backups that you can at least restore some of the project from.

I'm on Windows 10. I'm sure it saved completely. I just remembered I went to work on it, changed my mind quickly, and simply closed it without savingat all. Then, the next time, it was corrupt like this,

@bracketJacket I completely understand, if this had happened to me I'd be heartbroken. Also I love Phoenix Wright so I really hope you're able to give this another go.
--
I've been spending today trying to reproduce the issue writing stress tests opening, saving closing projects thousands of times in Windows 10 but not able to reproduce anything yet.
I've come across a few related links showing similar issues occurring for people using Notepad++ VSCode and Aseprite.
https://notepad-plus-plus.org/community/topic/13302/fix-corrupted-txt-file-null/60
https://github.com/Microsoft/vscode/issues/9589#issuecomment-235552090
https://community.aseprite.org/t/file-full-of-null-bytes/31/5
https://superuser.com/questions/845270/what-could-cause-the-files-to-be-replaced-with-null-bytes-size-and-timestamp-no
It seems like the file is getting written to a file cache rather than directly to disk and then that cache is not getting flushed. The Notepad++ link has a command for disabling the cache but I would probably advise against doing that.
The VSCode issue ends up linking to a potential fix they implemented though which replaces calls to fs.writeFile to a new function they write called fs.writeFileAndFlush that they claim fixes the issue
https://github.com/microsoft/vscode/commit/974bce453ec0d39996bda3d4bf31707ca1825c94
I'm going to have a go at integrating this into GB Studio to see if it helps.


Unable to install with go get

Excited to kick the tires on bass!
As per the instructions on the home page, I attempted to install bass with the go get command and was met with an error. I'm not really familiar with Go these days so perhaps I did something wrong.
$ go install github.com/vito/bass/cmd/...@latest
go: downloading github.com/vito/bass v0.0.0-20220103020353-a43629f9cd39
go install: github.com/vito/bass/cmd/...@latest (in github.com/vito/bass@v0.0.0-20220103020353-a43629f9cd39):
	The go.mod file for the module providing named packages contains one or
	more replace directives. It must not contain directives that would cause
	it to be interpreted differently than if it were the main module.

I'm on macOS Big Sur 11.6.2 and am happy to provide other info or try out something else to lend a hand with troubleshooting.
Thanks,
+Jonathan

Thanks for the report! Gonna fold this into #20 though. :)
Also macOS support isn't very good right now even though there are binaries for it in the nightly release. Bass uses Buildkit which is Linux only. I would recommend just using Bass in a Linux VM for now. If you want to try setting that up I'm happy to help troubleshoot.
Current ideas for macOS support:

running Buildkit in its own VM and configuring Bass to reach it over TCP, similar to how Docker for Mac works
re-implementing the Docker runtime so you can just use Docker for Mac

I'll get on updating the front page soon.

Opened https://github.com/vito/bass/issues/35 for macOS support.

fyi: macOS support has been added in #37 via a lightweight Linux VM (similar to Docker for Mac)
the README has updated instructions, and a new nightly has been released


Added Coto to a branch

I am learning how to add branches and work with collaborators. For this I created a branch and added Coto as a collaborator to the website.

Coto was added.


[ModuleInterface] Improvements to caching

This picks up where https://github.com/apple/swift/pull/19518 left off, adding a new (very simple) dependency file type (called .sid since it's private anyways, and .swiftinterfacedeps seemed like it was getting a bit long) and improving the cache-key formation to match what @jrose-apple described over in https://forums.swift.org/t/thoughts-on-caching-compiled-parseable-interfaces/16746
Also factored out a common helper along the way that I was going to wind up adding another copy of if I didn't.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 8ed15bbb6a98ab2ce0cf116759a45b3672b91aff

@swift-ci please test and merge

@swift-ci please test and merge

Hm, I haven't looked over the source too closely, but why store this in a separate file, as opposed to part of the built swiftmodule?


Updates to schemas and graphql-schemas

This is an attempt at getting the schemas defined in this repository to match those of a private "upstream" repository as much as possible, while still omitting the upstream's highly-implementation-specfic details (e.g. opinionated enum declarations, references to particular internal systems).

I've finally come back to this, and I've updated schemas in a hopefully-agreeable manner.
Prior to these changes, I could not run terraform integrations locally successfully. With these changes, I can run them successfully.

I made the changes suggested by @BumbleFeng.
I tested that I was still able to successfully run local terraform integrations with these changes.
I'll go ahead and merge this.


 The system return code was<PHONE_NUMBER>; the reason code was ED076232.
The traceback information could not be determined.
LEAID201I - LEAID64 ENTERED (LEVEL 12/05/2016 12.37 PTF-PT00159).
LEAID207I - LEAID64 RETURN FROM ABEND-AID, RC=0.
SIGKILL
[SYSA] bash-5.2$ ls --version
ls (GNU coreutils) 9.5

Further testing seems to indicate the cd into the /dsfs directory is causing zot commands to fail.
SYSA] bash-5.2$ echo $PATH
/hewitt/zopentools/zopen_repo/usr/local/bin:/hewitt/zopentools/zopen_repo/usr/bin:/hewitt/zopentools/zopen_repo/bin:/hewitt/zopentools/zopen_repo/boot:/usr/lpp/IBM/zoau/v1r3/bin:/usr/lpp/IBM/cyp/v3r12/pyz/bin:/usr/lpp/java/J17.0_64/bin:/usr/lpp/java/J8.0_64/bin:/bin:.:/hewitt/coz/current/bin:/usr/local/bin:/usr/local/sbin:/usr/lpp/ported/bin:/usr/sbin:/usr/lpp/NFS:/u/@02858/scripts:
[SYSA] bash-5.2$ cd /dsfs
[SYSA] bash-5.2$ which ls
CEE3512S An HFS load of module CXXRT64 failed. The system return code was<PHONE_NUMBER>; the reason code was ED076232.
The traceback information could not be determined.
LEAID201I - LEAID64 ENTERED (LEVEL 12/05/2016 12.37 PTF-PT00159).
LEAID207I - LEAID64 RETURN FROM ABEND-AID, RC=0.
SIGKILL

@IgorTodorovskiIBM Have you had a chance to duplicate the issue?
thanks
More information:

Hmm, CXXRT64 is the z/OS LE provided C++ runtime library (used when we compile with xlclang++).
I am able to reproduce it:
[ITODOR@PLPSC /dsfs]$ ls
CEE3512S An HFS load of module CXXRT64 failed. The system return code was<PHONE_NUMBER>; the reason code was ED076232.
         The traceback information could not be determined.
SIGKILL
[ITODOR@PLPSC /dsfs]$ /bin/ls
bin     rec     sysout  txt

Interesting if I cd out of the dir and do this:
cd ~
/u/itodor/zopen/usr/local/altbin/ls /dsfs

Then there's no issue

@IgorTodorovskiIBM Further testing seems to indicate the cd into the /dsfs directory is causing any zot command to fail.
[SYSA] bash-5.2$ cd /dsfs
[SYSA] bash-5.2$ which df
CEE3512S An HFS load of module CXXRT64 failed. The system return code was<PHONE_NUMBER>; the reason code was ED076232.
The traceback information could not be determined.
LEAID201I - LEAID64 ENTERED (LEVEL 12/05/2016 12.37 PTF-PT00159).
LEAID207I - LEAID64 RETURN FROM ABEND-AID, RC=0.
SIGKILL

I have xlclang in my path...
[SYSA] bash-5.2$ which xlclang
/bin/xlclang
[SYSA] bash-5.2$ which xlclang++
/bin/xlclang++

I'll dig into it

One way to workaround it is to remove . from your LIBPATH.

Will do...thanks


Project Abandoned?

Hasn't had a update in a long time and I cant seem to get it working, is this dead?

After a year.. I think its dead....

Hello,
The Instance and object storage product of Runabove have graduated as full fledged OVH products. You will find them under the cloud section https://www.ovh.com/fr/cloud/instances/. If you are looking for an API wrapper for java, you may find one here: https://github.com/ovh/java-ovh


Possible ExistValidator optimization

What steps will reproduce the problem?
Having a large amount of ActiveRecord's (500+) that include ExistValidators all cause SELECT EXISTS(SELECT * FROM foo WHERE id=bar) database calls. On a table that has 4 foreign key relations, this is 4 * n queries and after trying to do 500 at once, that quickly balloons to 2k queries.
What is the expected result?
Static cache much like done on the RBAC rules.
What do you get instead?
No cache for ExistValidator, so repeated calls for the same foreign_key cause a new query thus making response time much greater.
Additional info
This of course introduces the problem of more memory use and might not work if system contains too many records, but I'd take more memory use than more queries in our case. It may be beneficial to add cache options like DbManager of rbac. Gauging interest/feedback before I put forth a PR.

Q
A

Yii version
2.0.9

PHP version
5.6.15

Operating system
centos7

How did you get 500 records validated at once?

There not, my bad on explaining. They are iterated through and saved individually so the various beforeValidate and afterSave events can fire. At this point during the save individually, validation is triggered and thus above happens.
I could probably disable validation during the save at that point, but I can't trust the data so I think I need it.
Thanks for quick response.

If you're sure these are always valid, skip validation. If you aren't sure then exist validation isn't the kind of validation to be cached. Each second database may change its state so it should be validated just before it's saved.


Improve visuals of sub tabs in creator panel

This is a task taken from the right panel tabs issue that should be worked on independently.
The idea is to improve the visuals of subtabs, as it feels better to have inactive tabs not being colored with the primary color:

@lusebille mockups: https://www.figma.com/design/wcpetFt6aOKzTszcvPPWLQ/[05%2F24]-Grist-Design?node-id=2761-141496&t=qX4iHFYd8uzsW8kZ-1

Actually, working on the new colors first is required here, if I use the current grays they will not be visible, and If i use the new grays just in this issue it'll feel weird to have just those things having colors different from the main theme…
Waiting for feedback on https://github.com/gristlabs/grist-core/issues/1295 first.


Update sbt-bloop to 1.5.15

About this PR
📦 Updates ch.epfl.scala:sbt-bloop from 1.4.8-19-4d9f966b to 1.5.15
📜 GitHub Release Notes
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "sbt-bloop" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.epfl.scala", artifactId = "sbt-bloop" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #123.


What's the relationship with MarkdownX?

Please see the README


Move control port definition from setting to server

If you have multiple servers in the same configuration file (ie. HTTP & HTTPS), and you need a control port for both. The second server can not bind the control port, already taken by the first one.
A easy fix is to move the control port definition from the setting section to the server section in the configuration file.

In facts,
we can define a control_port in the server structure to overwrite the control_port define in settings.
But it's not documented yet.
William


Clean ups and addition of ntuple campaign

Hi @oksuzian,
You have proposed changes to files in these packages:

data
CampaignConfig
ProjPy
Scripts

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for 9b8ec9f007e81a38524fa071873a07ccd00a674c: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at 9b8ec9f007e81a38524fa071873a07ccd00a674c.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 9b8ec9f007e81a38524fa071873a07ccd00a674c at a172547496577e39e632abf1ef6b766f6ae34552

build (prof)
:white_check_mark:
Log file. Build time: 04 min 20 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 9b8ec9f007e81a38524fa071873a07ccd00a674c after being merged into the base branch at a172547496577e39e632abf1ef6b766f6ae34552.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


Publications All Broken

I use the GNU IceCat broswer
Yesterday some new updates were probably done, that broke all publication pages on Odysee. The list of publications works fine. But only when I click to read an article or to watch a video it does this:

On Brave it works. This is probably some new library not supported by the IceCat. I remember seeing similar errors on IceCat in multiple other places. Like when I click to copy the RSS feed. Or try to make a playlist. It's only with the new features.
It didn't bother me much, since the features were minor. And did not blocked me out of the core functionality. But with this new bug I CANNOT USE ODYSEE ANYMORE. Which is a big problem.
Something had changed recently with how features are implemented that broke support for certain browsers. Please fix it.

Please send us an email at<EMAIL_ADDRESS>with a screenshot of the console tab (press ctrl-shift-I, then console tab).

done


Pin toggle after deepSleep

Sorry for opening an issue here,
I'v exactly the same hardware setup and had problems after sleep:
"ESP.deepSleep(10*1000000)" toggles the pins and sometimes the value at the display changes without interaction.
As I read in many articles, pin change after deep sleep is "normal" and can't be avoided.
Do you know why it works in your setup?
Robert

Hi, opening issues here is wanted!!! I have no much time at all to really work on the code. So with opening issues I can fokus on whats really needs to be improved.
To understand your problem right: The pinchange on wakeup leads to a wrong temperature after the pulse function? Or does it then not even work to send inputs onto the encoder pins?
To be honest i didn't put much effort into the device side, as it was working with the provided code in acceptable fashion.

To understand your problem right: The pinchange on wakeup leads to a wrong temperature after the pulse function?

Not exactly,  the temperature changes without pulse function. Only because of random pin change at wake up.
( It's documented here: https://www.esp8266.com/viewtopic.php?f=5&t=11282 )

Or does it then not even work to send inputs onto the encoder pins? Are you using my code or is it a general question?

I use parts of your code (the idea with the rotary encoder and the pulse function) and the ESP.deepSleep - function which i guess rises the problem.
My code is running now for more than a week without problem with "light-sleep".
When i switch to "deep-sleep" the temperature is changing on the EQ-3 randomly.
Sometimes 0.5C up sometimes down. Once i had bad luck and it went to zero slowly...
Do you have the same temperature on the eq-3 when the pulse function is not used for a longer period?

I guess in my scenario here even a pin toggle would not effect the functionality because the code triggers the value on the thermostat to zero and then up to the server configured temperature. So even if the pin change corrupts the value it's straight away taken to 0 and the intermediate wrong input makes no difference.

I understand, but it will drift if the pulse function is not used for a while...
Do you update the temperature every 15 minutes?
Robert

Hi Robert,
correct. The process in my use case is wakeup - request current temperature from server - pulse to zero and beyond (60 steps) - pulse up to temperature- sleep 15 mins. Due to the speed the pulse happens I guess I didn't even recognize a pin changes during wakeup. And I guess I really have the changes as well. They simply don't bother me due to the use case. While sleeping the temperature stays exactly the same.

correct. The process in my use case is wakeup - request current temperature from server - pulse to zero and beyond

Thank you for clarifying this!
I will go for your concept (pulse to zero and up after sleep) because light_sleep (which takes approx. 600uA in my case) and optimizing "online time" to 300ms empty the NiCd Accu's in about 1 month.


feature: add an alias for the Technology Preview of the new web3.js

Summary
By no means a complete solution, this PR is the start of adding support for the Technology Preview version of @solana/web3.js.
Here, we import the tp version of the library and alias it to web3tp.
Test Plan

Create a wallet and airdrop some SOL to it.

Create a client like so:
import "@solana/webcrypto-ed25519-polyfill";

// Client
const rpc = web3tp.createSolanaRpc({
  transport: web3tp.createDefaultRpcTransport({
    url: "https://api.devnet.solana.com",
  }),
});

const keyPair = await web3tp.generateKeyPair();
console.log(keyPair);

console.log("My address:", pg.wallet.publicKey.toString());
const { value: balance } = await rpc
  .getBalance(pg.wallet.publicKey.toBase58())
  .send();
console.log(`My balance: ${Number(balance) / web3.LAMPORTS_PER_SOL} SOL`);

Observe output
Running client...
  client.ts:
    { privateKey:
   { algorithm: { name: 'Ed25519' },
     extractable: false,
     type: 'private',
     usages: [ 'sign' ] },
  publicKey:
   { algorithm: { name: 'Ed25519' },
     extractable: true,
     type: 'public',
     usages: [ 'verify' ] } }
    My address: 9kShTNxtemuHJzsXBmSPpS4o8vSdPAgBf9uEdAadm9j6
    My balance: 0.01 SOL

Current dependencies on/for this PR:

master

PR #1

PR #2   👈

This stack of pull requests is managed by Graphite.


Point-Budget vs. Mesh-Update

Handle Edge-Case (if notable by users): What happens if already loaded Mesh needs to be updated/loaded but this would exceed point budget.


Add waiting for ctx.Done() when sending StepRunner stop result

Codecov Report

Merging #57 (849a215) into main (0f755b4) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #57   +/-   ##
=======================================
  Coverage   66.47%   66.48%
=======================================
  Files         157      157
  Lines        9457     9458    +1
=======================================
+ Hits         6287     6288    +1
  Misses       2501     2501
  Partials      669      669

Flag
Coverage Δ

e2e
51.08% <83.33%> (-0.01%)
:arrow_down:

integration
58.15% <100.00%> (-0.04%)
:arrow_down:

unittests
48.05% <100.00%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/runner/step_runner.go
89.44% <100.00%> (+0.06%)
:arrow_up:

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 0f755b4...849a215. Read the comment docs.


Add Instance level middlewares

Fix: https://github.com/redis-rb/redis-client/pull/52
There are some use case for middlewares that only applies to a specific connection.
You could implement key namespacing as a middleware for instance, or use it to ban some commands etc, without impacting libraries that use redis-client too.
This can also be used to implement the Semian adapter as a middleware without any monkey patch.
I re-recorded the benchmark, and with this implementation there's no measurable perf impact.
The one downside of this implementation is that it makes it a bit harder for a middleware to be instantiated with some kind of configuration parameters, but it's not impossible at all.
Co-Authored-By: @gremerritt

Ok, I found a few more uses cases for this, so I think it's valuable.


Early termination of training

High Level Description
Want to determine what is the cause of early termination of the training process
Desired SMARTS version
0.6.1
Operating System
Ubuntu 20.04.5 LTS
Problems
the following occurred during my training process:
...
Agent_0: Collided.
Agent_0: Went off road.
Agent_0: Collided.
Agent_0: Went off road.
------------------------------------
| rollout/            |            |
|    ep_len_mean      | 11.4       |
|    ep_rew_mean      | -18.897657 |
|    exploration_rate | 0.638      |
|    success_rate     | 0          |
| time/               |            |
|    episodes         | 284        |
|    fps              | 10         |
|    time_elapsed     | 375        |
|    total_timesteps  | 3808       |
------------------------------------
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
-----------------------------------
| rollout/            |           |
|    ep_len_mean      | 11.3      |
|    ep_rew_mean      | -18.73835 |
|    exploration_rate | 0.634     |
|    success_rate     | 0         |
| time/               |           |
|    episodes         | 288       |
|    fps              | 10        |
|    time_elapsed     | 381       |
|    total_timesteps  | 3851      |
-----------------------------------
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Killed

It happened to more than one algo (i.e. DQN, PPO, A2C) Moreover, the duration that the training process was terminated was not consistent (sometimes after starting for 1 hr, sometimes a few hours, other times a few days). I wonder what is the cause of this phenomenon.

Hi @zyzhang1130,
Could you share a minimum working example to reproduce the error?

the front part was just running normally:
(base) zeyu@ZYNitro5:~$ conda activate smarts
(smarts) zeyu@ZYNitro5:~$ cd SMARTS/competition/track1/train
(smarts) zeyu@ZYNitro5:~/SMARTS/competition/track1/train$ python3.8 train.py
python3.8: can't open file 'train.py': [Errno 2] No such file or directory
(smarts) zeyu@ZYNitro5:~/SMARTS/competition/track1/train$ python3.8 run.py

Torch cuda is available:  True

Logdir: /home/zeyu/SMARTS/competition/track1/train/logs/2022_10_12_15_23_10

/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/intersection/1_to_2lane_left_turn_c/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/gym/logger.py:34: UserWarning: WARN: Box bound precision lowered by casting to float32
  warnings.warn(colorize("%s: %s" % ("WARN", msg % args), "yellow"))
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/intersection/1_to_2lane_left_turn_c/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/intersection/1_to_2lane_left_turn_t/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/intersection/1_to_2lane_left_turn_t/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/merge/3lane_single_agent/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/merge/3lane_single_agent/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/straight/3lane_cruise_single_agent/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/straight/3lane_cruise_single_agent/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/straight/3lane_overtake/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix
Waiting on /home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/smarts/scenarios/straight/3lane_overtake/. ...
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/trimesh/curvature.py:12: DeprecationWarning: Please use `coo_matrix` from the `scipy.sparse` namespace, the `scipy.sparse.coo` namespace is deprecated.
  from scipy.sparse.coo import coo_matrix

Start training.

Using cuda device

Training on 1_to_2lane_left_turn_t.

 Retrying in 0.05 seconds
:device(error): Error adding inotify watch on /dev/input: No such file or directory
:device(error): Error opening directory /dev/input: No such file or directory
2022-10-12 15:29:47.891268: E tensorflow/stream_executor/cuda/cuda_blas.cc:2981] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
<frozen importlib._bootstrap>:219: RuntimeWarning: numpy.ndarray size changed, may indicate binary incompatibility. Expected 80 from C header, got 96 from PyObject
/home/zeyu/anaconda3/envs/smarts/lib/python3.8/site-packages/h5py/__init__.py:46: DeprecationWarning: `np.typeDict` is a deprecated alias for `np.sctypeDict`.
  from ._conv import register_converters as _register_converters
Logging to /home/zeyu/SMARTS/competition/track1/train/logs/2022_10_12_15_23_10/tensorboard/PPO_1
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Collided.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Collided.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Collided.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
-----------------------------------
| rollout/           |            |
|    ep_len_mean     | 10.7       |
|    ep_rew_mean     | -34.955578 |
| time/              |            |
|    fps             | 14         |
|    iterations      | 1          |
|    time_elapsed    | 141        |
|    total_timesteps | 2048       |
-----------------------------------
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went wrong way.
Agent_0: Went off road.
Agent_0: Went off road.
Agent_0: Went off road.

...
until the error showed up in my previous comment.

Were any changes made to the given example at SMARTS/competition/track1?
If yes, what were the code changes?

Does changing hyperparameters in SMARTS/competition/track1/train/config.yaml count? Like changing epochs train_steps (I changed it from the default value to the following.
# Training
  epochs: 5_00 # Number of training loops.

  # Training per scenario
  train_steps: 100_00
  checkpoint_freq: 50_00 # Save a model every checkpoint_freq calls to env.step().
  eval_eps: 2 # Number of evaluation epsiodes.
  eval_freq: 50_00 # Evaluate the trained model every eval_freq steps and save the best model.

Changing the number of epochs and training steps should not cause issues.
From the log, it is seen that the training process was killed. Most probable reasons include out of memory or out of file descriptors.
Try investigating whether the memory consumption by your program is increasing over time.


gpu support

@liupei101  Thank you so much for the package.
Could you please advise is it possible to use GPU support for this TFDeepSurv package?
Thank you!

Only FC layers are used in DeepSurv model, not involving Conv etc, but you can modify code to adapt your environment (GPU or CPU).
PRs are welcomed!

I tried to find a way to use the GPU without modifying the code and since I notice that you have utilized the tensorflow 1.* version for TFDeepSurv. I have done the following:

install the TensorFlow 1.15-GPU version using
pip3 install tensorflow-gpu==1.15
run the TFDeepSurv code under TensorFlow 1.15-GPU  using my GPU[0]
I notice that the percentage of GPU utilization is in the range of  0%~3%
[1] TITAN RTX        | 60'C,   0 % | 23216 / 24217 MB |

I am not sure if this actually uses the GPU or not. I think it uses since I can see the temperature of GPU raise and the percentage is not always 0%. But on the other hand, not sure why the GPU utilization is low.
Could you please advise if I did the right thing? Thank you!


Using docker

Pull Request Test Coverage Report for Build 438

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

Totals

Change from base Build 437:
0.0%

Covered Lines:
817

Relevant Lines:
856

💛  - Coveralls

Pull Request Test Coverage Report for Build 438

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

Totals

Change from base Build 437:
0.0%

Covered Lines:
817

Relevant Lines:
856

💛  - Coveralls

Pull Request Test Coverage Report for Build 438

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

Totals

Change from base Build 437:
0.0%

Covered Lines:
817

Relevant Lines:
856

💛  - Coveralls


CI/CD: No test result or tests did not run

Hi,
I have an simple project with 1 app and 1 test app.

During the CI/CD action under Build\Compiling test apps I receive 2 warnings:

Warning: AL1025 The file at location 'c:\sources\MyApp.Test.altestrunner\last.xml' does not match any definition.
Warning: AL1025 The file at location 'c:\sources\MyApp.Test.altestrunner\Results\MyApp Test.xml' does not match any definition.

The test results in the artifacts are empty, so I assume the tests didn't run:
<?xml version="1.0" encoding="UTF-8"?>
<testsuites />

And in the Summary of the action, there are no test failures:

The warnings can be ignored - they are just the compiler complaining that it doesn't understand these .xml files.
In your build step - you should be able to see whether AL-Go recognizes your test app as a test app:

The way this happens is if you have included it in the "testFolders" setting in .AL-Go/settings.json. If that setting is empty, AL-Go also looks whether the app has a dependency on any of the test framework apps to mark it as a test app.
In the build step you can also see whether your test app gets build and/or whether tests gets run.

Hi,
the warnings indeed vanished after removing the .altestrunner folder.
But My test results are still empty.

The setting of my .github/AL-Go-Settings.json:
{
  "type": "AppSource App",
  "templateUrl": "https://github.com/microsoft/AL-Go-AppSource@main",
  "useCompilerFolder": false,
  "doNotPublishApps": false,
  "templateSha": "4e9dea08cd136dfc344d493e4d247af5b8f8352d"
}

Hi,
The test app has these dependencies:
"dependencies": [
    {
      "publisher": "Microsoft",
      "name": "Library Assert",
      "id": "dd0be2ea-f733-4d65-bb34-a28f4624fb14",
      "version": "<IP_ADDRESS>"
    },
    {
      "publisher": "Microsoft",
      "name": "Any",
      "id": "e7320ebb-08b3-4406-b1ec-b4927d3e280b",
      "version": "<IP_ADDRESS>"
    },
    {
      "id": "5095f467-0a01-4b99-99d1-9ff1237d286f",
      "publisher": "Microsoft",
      "name": "Library Variable Storage",
      "version": "<IP_ADDRESS>"
    },
    {
      "id": "23de40a6-dfe8-4f80-80db-d70f83ce8caf",
      "publisher": "Microsoft",
      "name": "Test Runner",
      "version": "<IP_ADDRESS>"
    },
    {
      "id": "40860557-a18d-42ad-aecb-22b7dd80dc80",
      "publisher": "Microsoft",
      "name": "Permissions Mock",
      "version": "<IP_ADDRESS>"
    },
    {
      "id": "10cb69d9-bc8a-4d27-970a-9e110e9db2a5",
      "name": "_Exclude_APIV2_",
      "publisher": "Microsoft",
      "version": "<IP_ADDRESS>"
    },
    {
      "id": "5d86850b-0d76-4eca-bd7b-951ad998e997",
      "name": "Tests-TestLibraries",
      "publisher": "Microsoft",
      "version": "<IP_ADDRESS>"
    },
    {
      "id": "5cb60033-f8d0-4617-be22-8682df9b824a",
      "name": "Finance BE",
      "publisher": "9altitudes",
      "version": "<IP_ADDRESS>"
    }
  ]

The Test app is also getting build. This is the log during build:
Compiling test apps
     _____                      _ _ _               _           _
    / ____|                    (_) (_)             | |         | |
   | |     ___  _ __ ___  _ __  _| |_ _ __   __ _  | |_ ___ ___| |_    __ _ _ __  _ __  ___
   | |    / _ \| '_ ` _ \| '_ \| | | | '_ \ / _` | | __/ _ \ __| __|  / _` | '_ \| '_ \/ __|
   | |____ (_) | | | | | | |_) | | | | | | | (_| | | |_  __\__ \ |_  | (_| | |_) | |_) \__ \
    \_____\___/|_| |_| |_| .__/|_|_|_|_| |_|\__, |  \__\___|___/\__|  \__,_| .__/| .__/|___/
                         | |                 __/ |                         | |   | |
                         |_|                |___/                          |_|   |_|
  Using Version <IP_ADDRESS>

  Compiling D:\a\GTM-BC-9AFinanceBE\GTM-BC-9AFinanceBE\9A Finance BE.Test
  Using Symbols Folder: D:\a\GTM-BC-9AFinanceBE\GTM-BC-9AFinanceBE\.packages
  Processing dependency Microsoft_Application_<IP_ADDRESS> ()
  Dependency App exists
  Processing dependency Microsoft_System_<IP_ADDRESS> ()
  Dependency App exists
  Processing dependency Microsoft_Library Assert_<IP_ADDRESS> (dd0be2ea-f733-4d65-bb34-a28f4624fb14)
  Downloading symbols: Microsoft_Library Assert_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=dd0be2ea-f733-4d65-bb34-a28f4624fb14&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Processing dependency Microsoft_Any_<IP_ADDRESS> (e7320ebb-08b3-4406-b1ec-b4927d3e280b)
  Downloading symbols: Microsoft_Any_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=e7320ebb-08b3-4406-b1ec-b4927d3e280b&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Processing dependency Microsoft_Library Variable Storage_<IP_ADDRESS> ([509](https://github.com/9altitudes/GTM-BC-9AFinanceBE/actions/runs/7665287782/job/20890930420#step:8:519)5f467-0a01-4b99-99d1-9ff1237d286f)
  Downloading symbols: Microsoft_Library Variable Storage_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=5095f467-0a01-4b99-99d1-9ff1237d286f&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Processing dependency Microsoft_Test Runner_<IP_ADDRESS> (23de40a6-dfe8-4f80-80db-d70f83ce8caf)
  Downloading symbols: Microsoft_Test Runner_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=23de40a6-dfe8-4f80-80db-d70f83ce8caf&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Processing dependency Microsoft_Permissions Mock_<IP_ADDRESS> (40860557-a18d-42ad-aecb-22b7dd80dc80)
  Downloading symbols: Microsoft_Permissions Mock_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=40860557-a18d-42ad-aecb-22b7dd80dc80&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Processing dependency Microsoft__Exclude_APIV2__<IP_ADDRESS> (10cb69d9-bc8a-4d27-970a-9e110e9db2a5)
  Downloading symbols: Microsoft__Exclude_APIV2__23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=10cb69d9-bc8a-4d27-970a-9e110e9db2a5&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Processing dependency Microsoft_Tests-TestLibraries_<IP_ADDRESS> (5d86850b-0d76-4eca-bd7b-951ad998e997)
  Downloading symbols: Microsoft_Tests-TestLibraries_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=5d86850b-0d76-4eca-bd7b-951ad998e997&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Adding dependency to System Application Test Library from Microsoft
  Processing dependency 9altitudes_Finance BE_<IP_ADDRESS> (5cb60033-f8d0-4617-be22-8682df9b824a)
  Dependency App exists
  Processing dependency Microsoft_System Application Test Library_<IP_ADDRESS> (9856ae4f-d1a7-46ef-89bb-6ef056398228)
  Downloading symbols: Microsoft_System Application Test Library_23.3.14876.15704.app
  Url : http://<IP_ADDRESS>:7049/BC/dev/packages?appId=9856ae4f-d1a7-46ef-89bb-6ef056398228&versionText=<IP_ADDRESS>&tenant=default
  Downloading using WebClient
  Adding dependency to System Application from Microsoft
  Processing dependency Microsoft_System Application_<IP_ADDRESS> (63ca2fa4-4f03-4f2b-a480-172fef340d3f)
  Dependency App exists
  Compiling...
  .\alc.exe /project:"c:\sources\9A Finance BE.Test" /packagecachepath:"c:\sources\.packages" /out:"c:\sources\.output\9altitudes_9A Finance BE.Test_<IP_ADDRESS>.app" /SourceRepositoryUrl:"https://github.com/9altitudes/GTM-BC-9AFinanceBE" /SourceCommit:"282bde340280b6df38c4362274206aac385f6065" /BuildBy:"AL-Go for GitHub,v4.1" /BuildUrl:"https://github.com/9altitudes/GTM-BC-9AFinanceBE/actions/runs/766[528](https://github.com/9altitudes/GTM-BC-9AFinanceBE/actions/runs/7665287782/job/20890930420#step:8:538)7782" /assemblyprobingpaths:"C:\Program Files\dotnet\shared","C:\ProgramData\BcContainerHelper\Extensions\bc7665287782\.netPackages\Service"
  Microsoft (R) AL Compiler version <IP_ADDRESS>12
  Copyright (C) Microsoft Corporation. All rights reserved

  Compilation started for project '9A Finance BE.Test' containing '4' files at '08:13:27.356'.

  Compilation ended at '08:13:33.343'.

Yes, the subtype is set to Test
codeunit 71115793 "NAL_Finance BE Test"
{
    Subtype = Test;

Can I send you a .zip file with our test app by mail?

Sure - freddyk at microsoft dot com

@freddydk ,
Thanks for pointing me to the right direction.
For people experiencing the same problem...
From: Freddy Kristiansen
Sent: Friday, 26 January 2024 14:48
To: Job Louage
Subject: Re: Concerning AL-Go Github issue 896
I deleted the install codeunit, which creates the test suite and the install line in the permissions, then it works.
Will delete the repo again.

/Freddy


Support PCM

I test on a Hik camera, but can't get the audio works, so please support the pcm codecs, thank you!
here is the stream info:
Input #0, rtsp, from 'rtsp://xxx:xxxk@xxxxxx:40052/Streaming/Channels/701':
  Metadata:
    title           : HIK Media Server V3.4.62
    comment         : HIK Media Server Session Description : standard
  Duration: N/A, bitrate: 64 kb/s
    Stream #0:0: Video: h264, none, 90k tbr, 90k tbn, 180k tbc
    Stream #0:1: Audio: pcm_alaw, 8000 Hz, mono, s16, 64 kb/s

the original audio stream is:  "Stream #0:1: Audio: pcm_alaw, 8000 Hz, mono, s16, 64 kb/s"
it seems not h264 standard aac codecs, it will work on webrtc ?
it seems, there is  no stream in chrome://webrtc-internals

Statistics RTCInboundRTPAudioStream_2608133663
--
timestamp | 2019/9/26 下午6:26:55
ssrc |<PHONE_NUMBER>
isRemote | false
mediaType | audio
kind | audio
trackId | RTCMediaStreamTrack_receiver_3
transportId | RTCTransport_0_1
packetsReceived | 0
[packetsReceived/s] | 0
bytesReceived | 0
[bytesReceived/s] | 0
packetsLost | 0
jitter | 0

Hey @yourchanges
I am working on this now, I hope to have it done by tomorrow! I will resolve this ticket when all the work is done
Thanks for using Pion!

Awesome!It is useful to IP Camera.

:+1::+1::+1::+1::+1:

I'll test it later.


[feat] Refactor wallet_app/android

[feat] Refactor wallet_app/android
Resolves #93

Organized the Activity files into the ui/activity directory for better structure.
Updated paths in AndroidManifest.xml to reflect new locations of activities.
Ensured all imports and references in Activity files are corrected.

ty!


Caching data for faster SQLite queries

SQLite support setting and getting auxiliary data. These functions may be used by (non-aggregate) SQL functions to associate auxiliary data with argument values. If the same argument value is passed to multiple invocations of the same SQL function during query execution, under some circumstances the associated auxiliary data might be preserved.
This can allow for reusing the decoded protobuf message and the parsed path in the protobuf_extract function reducing the number of decods and parses performed for complex queries.
It is also possible to cache multiple protobuf messages and paths similar to the JSON1 library. This could give an additional speedup at the cost of copying and comparing the entire protobuf message or path adding some additional complexity.

#2


Keep sent_offer and received_offer after expiration

These should be kept in the database after expiration in case an invoice is somehow paid or processed after the expiration time.
The queries that need offers can use filters to only get the ones that are not expired based on the expiration time field.

Done for sent offers: https://github.com/yzernik/squeaknode/pull/865

Duplicate of https://github.com/yzernik/squeaknode/issues/858


make docker demo scripts work for tutorials AND CI

In order to run our sidechain demo on a non-SGX machine in docker:
https://docs.integritee.network/4-development/4.6-demos/4.6.1-sidechain-demo
I needed to patch the compose script:
diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml
index d8093c23..63aa6e00 100644
--- a/docker/docker-compose.yml
+++ b/docker/docker-compose.yml
@@ -1,6 +1,6 @@
 services:
   "integritee-node-${VERSION}":
-    image: "${INTEGRITEE_NODE:-integritee/integritee-node-dev-ias:1.0.35}"
+    image: "${INTEGRITEE_NODE:-integritee/integritee-node-dev:1.0.35}"
     hostname: integritee-node
     devices:
       - "${SGX_PROVISION:-/dev/null}:/dev/sgx/provision"
@@ -43,7 +43,7 @@ services:
       interval: 10s
       timeout: 10s
       retries: 25
-    entrypoint: "/usr/local/bin/integritee-service --clean-reset --ws-external -M integritee-worker-1 -T wss://integritee-worker-1 -u ws://integritee-node -U ws://integritee-worker-1 -P 2011 -w 2101 -p 9912 -h 4645 run --dev"
+    entrypoint: "/usr/local/bin/integritee-service --clean-reset --ws-external -M integritee-worker-1 -T wss://integritee-worker-1 -u ws://integritee-node -U ws://integritee-worker-1 -P 2011 -w 2101 -p 9912 -h 4645 run --dev --skip-ra"
     restart: "no"
   "integritee-worker-2-${VERSION}":
     image: integritee-worker:${VERSION:-dev}
@@ -73,7 +73,7 @@ services:
       interval: 10s
       timeout: 10s
       retries: 25
-    entrypoint: "/usr/local/bin/integritee-service --clean-reset --ws-external -M integritee-worker-2 -T wss://integritee-worker-2 -u ws://integritee-node -U ws://integritee-worker-2 -P 2012 -w 2102 -p 9912 -h 4646 run --dev --request-state"
+    entrypoint: "/usr/local/bin/integritee-service --clean-reset --ws-external -M integritee-worker-2 -T wss://integritee-worker-2 -u ws://integritee-node -U ws://integritee-worker-2 -P 2012 -w 2102 -p 9912 -h 4646 run --dev --request-state --skip-ra"
     restart: "no"
 networks:
   integritee-test-network:

In order to avoid redundancy, I think we should attempt to use the same yml file for CI and manual tutorials. In the best case, by adding --ci somewhere ;-)
And also, I think the tutorials should be more verbose on how to see all the logs if desired:
docker logs fd-integritee-worker-1--1 -f
docker logs fd-integritee-worker-2--1 -f
docker logs fd-integritee-node--1

related: https://github.com/integritee-network/book/issues/33


⚠ Bofrost.de has degraded performance

In b45141b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 709 ms

Resolved: Bofrost.de performance has improved in e7a3a51.


status length issue

Describe the bug
users with LONG statuses conflict with other themes
To Reproduce
Have friends with long statuses and a theme that change the friend list layout
Screenshots

Infomation (please complete the following information)
Discord channel: Stable
OS: Windows
Mod: BetterDiscord
Discord language: English
Additional context
The theme I'm using is DiscordNight

i did some tweaking and i found adding the following into custom CSS helps

.userInfo-2WpsYG,
.peopleListItem-u6dGxF {
  overflow: hidden;
  align-items: center;
  align-content: flex-start;
},
.peopleList-2VBrVI,
.textRuler-1DsANg,
.text-MPIeXO {
    white-space: pre-line;
    text-overflow: clip;
    overflow: hidden;
    align-items: center;
    align-content: flex-start;
    font-size: 14px;
    line-height: 20px;

as you can see in the following screen


Deploy Checklist: New Expensify 2021-09-15

Release Version: 1.0.99-3
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/App/pull/5037
[x] https://github.com/Expensify/App/pull/5060
[x] https://github.com/Expensify/App/pull/5073
[x] https://github.com/Expensify/App/pull/5094
[x] https://github.com/Expensify/App/pull/5136
[x] https://github.com/Expensify/App/pull/5208
[x] https://github.com/Expensify/App/pull/5216
[x] https://github.com/Expensify/App/pull/5229
[x] https://github.com/Expensify/App/pull/5243
[x] https://github.com/Expensify/App/pull/5244
[x] https://github.com/Expensify/App/pull/5248
[x] https://github.com/Expensify/App/pull/5251
[x] https://github.com/Expensify/App/pull/5256
[x] https://github.com/Expensify/App/pull/5257
[x] https://github.com/Expensify/App/pull/5261
[x] https://github.com/Expensify/App/pull/5264
[x] https://github.com/Expensify/App/pull/5288
[x] https://github.com/Expensify/App/pull/5307
[x] https://github.com/Expensify/App/pull/5330

Deploy Blockers:

[x] https://github.com/Expensify/App/issues/5241
[x] https://github.com/Expensify/App/issues/5285
[x] https://github.com/Expensify/App/issues/5286
[x] https://github.com/Expensify/App/issues/5289
[x] https://github.com/Expensify/App/issues/5290
[x] https://github.com/Expensify/App/issues/5291
[x] https://github.com/Expensify/App/issues/5305

cc @Expensify/applauseleads

starting QA

Checking off https://github.com/Expensify/App/pull/5229 because we were able to verify that it works as expected.

Checking off #5291 as it only occurs on one platform and doesn't block the user from sharing PDF files.

I removed the deploy blocker label from https://github.com/Expensify/App/issues/5286 because it's also happening in production, doesn't look like a new bug.

In order to resolve https://github.com/Expensify/App/issues/5290, I have raised a revert PR here. Once this is merged and on the deploy Checklist, I will mark #5290 off the list.

Regression is finished!
Issues found:

https://github.com/Expensify/App/issues/5291
https://github.com/Expensify/App/issues/5286
https://github.com/Expensify/App/issues/5290 - Is failing PR #5251
https://github.com/Expensify/App/issues/5289

Comments added in PRs:

https://github.com/Expensify/App/pull/5216#issuecomment-921061642
https://github.com/Expensify/App/pull/5244#issuecomment-921101313

Thanks

Checking off https://github.com/Expensify/App/pull/5216#issuecomment-921868290

Checking off https://github.com/Expensify/App/pull/5307#issuecomment-921892586 and https://github.com/Expensify/App/issues/5305 since they were tested and it was a pass 🎉

#5290 has been resolved as it was already occuring.

@marcaaron Can you confirm if we are good to check https://github.com/Expensify/App/pull/5330 off on the checklist? Judging by this comment it looks like we are good there?

Yep tested fine for me.

Is this checklist blocked on the verification code bug for switching between E.com and NewDot?

Yes, we were unable to complete QA for https://github.com/Expensify/App/pull/5244

checking off https://github.com/Expensify/App/pull/5244 because we reverted it on https://github.com/Expensify/App/pull/5360 so we could unblock this checklist

https://github.com/Expensify/App/pull/5244 has been reverted in https://github.com/Expensify/App/pull/5360, CPing to staging. Once its on staging I'll check it off the list and move forward w/ the deploy.

Staging deploy was a success, checking off https://github.com/Expensify/App/pull/5360. Looks like there aren't any blockers left here so going to close and proceed w/ the prod deploy!
:shipit:

This issue either has unchecked QA steps or has not yet been marked with the :shipit: emoji of approval.
Reopening!

:shipit:


RYA-491 Repackaged reusable Mongo DB test code into a project named '…

…rya.test.mongo'.

Updated.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/744/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/745/


Add defaultblock in Contract.call

Due to there are different state for each block. We should add support to get function call result from different block state. See #155 thanks @toknT
eg:
$defaultBlock = 'pending';

$contract->call($method, $params, $pending, function ($err, $res) {});

Codecov Report

Merging #157 into master will decrease coverage by 0.4%.
The diff coverage is 72.22%.

@@             Coverage Diff              @@
##             master     #157      +/-   ##
============================================
- Coverage     87.77%   87.36%   -0.41%
- Complexity      717      725       +8
============================================
  Files            47       47
  Lines          1570     1583      +13
============================================
+ Hits           1378     1383       +5
- Misses          192      200       +8

Impacted Files
Coverage Δ
Complexity Δ

src/Contract.php
75.92% <72.22%> (-1.44%)
158 <22> (+8)

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 fff321d...0e30378. Read the comment docs.


Delve cannot debug go-qml example projects

Delve cannot debug go projects based upon go-qml. This can be tested using the examples that come with the go-qml package.
For example, upon running dlv run basiclayouts.go delve successfully compiles the debug binary but then fails to run it and outputs error message:
[Could not launch program: decoding dwarf section info at offset 0x0: too short]

Sorry for the late response, but this is likely due to cgo. Thanks for the report! I have plans to significantly improve cgo support very soon.

Closing as duplicate of #79.


First load on WPF project takes 5 a 10 seconds

In my WPF application i need to make thumbs from photo the user add to the program. To do this i use the ImageProcessor package which works perfect for me. Bu i have one small problem the first use in an application session always takes 5 a 10 seconds to complete every next thumb making in the same session only takes milliseconds.
It looks like the DLL is only loaded on first use. Is there a way to make this faster?

The Framework code yeah, not the new Core stuff?
When ImageProcessor first loads up it does a search through your referenced assemblies to look for pluggable file formats, it shouldn't be anywhere near as slow as that to initialize though. Does your application have a lot of references?
The relevant loading code code that does this code can be found here. Maybe we need to add a few more known assemblies to the exclusion list?

Indeed the Framework code.
That could be it my application has a few dozen assemblies referenced.
Most of them are DevExpress., Google.
I think if those get excluded too, it must go beter.

Yeah definitely. If you could list a couple I could add them, or PR?

I you could just exclude all assemblies starting with DevExpress and Google it would be reduced very much.

Cripes yeah! Will do.

Can you tell when it will be availible as nuget package?

I've got a bit of work to do on the library before I can get a release out I'm afraid. You can see a list of open issues I need to clear out here.
https://github.com/JimBobSquarePants/ImageProcessor/milestones/Framework Consolidation
I'm hoping the community will step up and help.

Hi Jim, Can you give a estimated release date?

The code is finished but I cannot release without updating the docs. I'm gonna do my best to get them done tonight.

New version now released :boom:


Plugin blocks homebridge when Logitech Media Server is offline

As long as the LMS is running everything works fine. But when its powered off, the complete homebridge seems to be blocked. I cant communicate with any other device on homebridge.

Late reply.
I have no solution for this, but you can run individual instances for individual plugins in homebridge: See https://github.com/homebridge/homebridge/wiki/Child-Bridges for details.
But this is definitely an issue which should be addressed.

At the moment, I am running each homebridge plugin in a separate homebridge child instance - not ideal, but it works. But we should look into this.

I've also just encountered a slight variation of this problem. If the ip or port address for the LMS is incorrect, it has the same impact - blocks homebridge.  (in my situation the LMS had a dynamic IP address that not surprisingly changed after it was restarted)

I have no solution. As I said above, the (suboptimal) solution is to run home bridge-squeezebox in an individual child bridge as in this case not the whole home bridge hangs (I am running for each plugin a child bridge).
I would suggest to use either fixed IPs (you should be able to set them in your DHCP server (Router), or they the hostname instead.
I will close this issue, as I do not think I will fix it.


add gloria-zhao.json

I know I haven't been around very long but here's a list of PRs. 100% understand if rejected, just wanted to put myself out there more.

ACK


feat(json-schema-form): add generate_id format & markdown keyword

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[x] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[x] Updated Storybook documents
[x] Tested with console

Description

Add generate_id custom format
Add markdown custom keyword

https://user-images.githubusercontent.com/26986739/188832811-309e2045-c1f2-488c-ba0e-a6b1f875d319.mov
Things to Talk About

:tada: This PR is included in version 1.1.0-beta.389 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket: