Running carbon gives the AttributeError: 'module' object has no attribute 'CAN_FALLOCATE'

Hi need help running the carbon. When i issue the following command:
/opt/graphite/bin/carbon-cache.py start
It throws the following exception and carbon does not start. Please help in this regard:
/usr/lib/python2.7/dist-packages/zope/init.py:3: UserWarning: Module twisted was already imported from /usr/local/lib/python2.7/dist-packages/twisted/init.pyc, but /opt/graphite/lib is being added to sys.path
import pkg_resources
Traceback (most recent call last):
File "/opt/graphite/bin/carbon-cache.py", line 32, in
run_twistd_plugin(file)
File "/opt/graphite/lib/carbon/util.py", line 94, in run_twistd_plugin
config.parseOptions(twistd_options)
File "/usr/local/lib/python2.7/dist-packages/twisted/application/app.py", line 614, in parseOptions
usage.Options.parseOptions(self, options)
File "/usr/local/lib/python2.7/dist-packages/twisted/python/usage.py", line 266, in parseOptions
self.subOptions.parseOptions(rest)
File "/usr/local/lib/python2.7/dist-packages/twisted/python/usage.py", line 276, in parseOptions
self.postOptions()
File "/opt/graphite/lib/carbon/conf.py", line 221, in postOptions
if whisper.CAN_FALLOCATE:
AttributeError: 'module' object has no attribute 'CAN_FALLOCATE'

@frejsoya could you please tell me how to update whispher

It really depends on how it was installed, @susampath

Thnk you very much
On 26 Jul 2017 12:58 pm, "Denis Zhdanov"<EMAIL_ADDRESS>wrote:
It really depends on how it was installed, @susampath
https://github.com/susampath
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/426#issuecomment-317972055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdDAurEG6eB1MbXkjyQwyHvPKXHvyq6Aks5sRuqDgaJpZM4A-iIi
.


inconsistency in toast

What's the issue ?
The toast the appears on clicking the copy button in the modal is not consistent with the other toasts that's present in the app. For more reference you can check the screen shot below 👇

The text should be centered
Font color should be consistent

How should it look 🤔

Along with the toast the appears when there is an error can also be made consistent. The text is left aligned which can be made centered. For more reference you can check the screenshot below 👇

@Bhartirana2812 Sure go ahead 🚀
cc: @alceil


Update code of conduct to use CDF code of conduct

This is already completed in all places it is used.


Portable terminal is invisible to all players in the sessions

Describe the bug
After pressing X (the button assigned to the portable terminal) the animation of opening the terminal is present but the terminal itself is invisible. You can still type in commands and hear sounds from the terminal but it is totally invisible to all players in the lobby.
To Reproduce
Press the button assigned to the terminal
Expected behavior
I expected to see the terminal
Screenshots
(https://github.com/FluffyFishGames/AdvancedCompany/assets/158285077/a8995083-6b7e-4010-b809-fc41dc4a45ff) I dont have another player with me right now so i can't show it from another perspective :(
Additional context
Logfiles
Player.log
Add a list of all of your mods
BepInEx-BepInExPack-5.4.2100
Rune580-LethalCompany_InputUtils-0.6.1
PotatoePet-AdvancedCompany-1.0.145
RickArg-Helmet_Cameras-2.1.5
AlexCodesGames-AdditionalContentFramework-1.0.3
AlexCodesGames-AdditionalSuits-2.0.0
Sligili-HDLethalCompany-1.5.6
x753-Mimics-2.3.2
tinyhoot-ShipLoot-1.0.0
HomelessGinger-MaskedEnemyOverhaul-3.1.1
RugbugRedfern-Skinwalkers-4.0.1
Ozone-Runtime_Netcode_Patcher-0.2.5
KlutzyBubbles-BetterEmotes-1.4.2
AinaVT-LethalConfig-1.3.4
funfoxrr-ShowLootOnPlanet-1.0.5
jockie-LethalExpansionCore-1.3.15
Justice69-ImmersiveScraps-1.1.7
Muldjord-MuldjordCosmetics-1.0.0
ThePotato-scanForItemsFix-1.0.4
matsuura-HealthMetrics-1.0.2

Maybe conflict with BetterEmotes?

yep, for some reason this is the only mod i did not check


Serenity 3.0 migration from Serenity 2.0

@jan-molak
Hi Jan- Good Morning ! I am bit worried that I might need to do too many changes when we start migrating to the SerenityJS version 3.0. Currently i am using SerenityJs protractor with cucumber in Typescript with Version - "^2.33.10".
I am using the below Code snippet
upButton: () => Target.the('Go to Top Button').located(by.id('btnUpwardsId')),
await actorCalled('User').attemptsTo(
Wait.upTo(Duration.ofSeconds(10)).until(upButton, isClickable()),
Scroll.to(upButton),
Click.on(upButton));
This is just a snippet, I have huge scenarios with such syntax. Kindly suggest me how can i handle this with 3.0. The reliability with SerenityJS may impact with my Clients. :( Thanks in advance !

Hey @harivsudhang!
You're right: Target to PageElement change does require a code change, as per the migration guide.
It should be a reasonably straight-forward regex replacement, though:
Target.the\((?<description>.*?)\).located\(by\.(?<selectorType>.*?)\((?<selector>.*?)\)\)

Using a JetBrains IDE you could do something like this:

Having said that, if people find migrating code from v2 to v3 challenging, please upvote this ticket and I'd be happy to look into writing an automated codemod.

@jan-molak
I understand, but is it possible to continue with the same 2.0 version even after 3.0 is released? Also is it possible to use protractor along with this? Please suggest

Hey @harivsudhang - no, version 3.0 introduces several backwards-incompatible changes. In particular, class Target is replaced by PageElement and PageElements classes.
This change requires consuming code to be updated, hence the major version bump in the framework itself.
Does this help?

Thanks Jan for the response 👍

You're welcome! There's also a v2->v3 migration guide that will be published with the new website - https://github.com/serenity-js/serenity-js/blob/main/documentation/serenity-js.org/docs/about/serenity-js-v3.mdx


Add test for batch put side effects

This makes sure that only the final mutation's index entries are written during a batch put.

http://ocd.appscale.net:8080/job/Datastore/1308/


(SP:_) Create a pop up window with sign up fields.

UserStory: #57
Description
The user clicks on the "Become a student" or "Become a tutor" buttons and Sign up form must pop up.
Design

Acceptance Criteria

[ ] The pop-up window must contain all the elements in accordance with the mockup.
[ ] The clicking elements must be disabled for now.

Already implemented


Sector drop down is listing non-sector values

Sector on OS Hub appears to be displaying a drop down list wtih product type values:

Expected Behavior
Sector drop down lists only submitted sector values (this behavior will change with #2080 because only sector values that are on the list AND have been submitted should be displayed in the drop down)
There was a similar bug to this related to #2004

Closed because this was due to a user error.


local bazel build fails

➜  grpc git:(master) ✗ bazel build test/cpp/end2end:xds_end2end_test --incompatible_disallow_filetype=false --incompatible_disallow_dict_plus=false

ERROR: /usr/local/google/home/juanlishen/.cache/bazel/_bazel_juanlishen/0c1362b4d21ac61a36ee0d11cff5a635/external/com_github_bazelbuild_bazeltoolchains/configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default/BUILD:57:1: @com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8: no such attribute 'dynamic_runtime_libs' in 'cc_toolchain' rule
ERROR: /usr/local/google/home/juanlishen/.cache/bazel/_bazel_juanlishen/0c1362b4d21ac61a36ee0d11cff5a635/external/com_github_bazelbuild_bazeltoolchains/configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default/BUILD:57:1: @com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8: no such attribute 'static_runtime_libs' in 'cc_toolchain' rule
ERROR: /usr/local/google/home/juanlishen/.cache/bazel/_bazel_juanlishen/0c1362b4d21ac61a36ee0d11cff5a635/external/com_github_bazelbuild_bazeltoolchains/configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default/BUILD:87:1: @com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-armeabi-v7a: no such attribute 'dynamic_runtime_libs' in 'cc_toolchain' rule
ERROR: /usr/local/google/home/juanlishen/.cache/bazel/_bazel_juanlishen/0c1362b4d21ac61a36ee0d11cff5a635/external/com_github_bazelbuild_bazeltoolchains/configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default/BUILD:87:1: @com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-armeabi-v7a: no such attribute 'static_runtime_libs' in 'cc_toolchain' rule
ERROR: /usr/local/google/home/juanlishen/.cache/bazel/_bazel_juanlishen/0c1362b4d21ac61a36ee0d11cff5a635/external/com_github_bazelbuild_bazeltoolchains/configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default/BUILD:57:1: Target '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:compiler_deps' contains an error and its package is in error and referenced by '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8'
ERROR: /usr/local/google/home/juanlishen/.cache/bazel/_bazel_juanlishen/0c1362b4d21ac61a36ee0d11cff5a635/external/com_github_bazelbuild_bazeltoolchains/configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default/BUILD:57:1: Target '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:empty' contains an error and its package is in error and referenced by '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8'
ERROR: /usr/local/google/home/juanlishen/wip/xds_to_lb/grpc/BUILD:273:1: Target '//:gpr' depends on toolchain '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8', which cannot be found: Target '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8' contains an error and its package is in error'
ERROR: /usr/local/google/home/juanlishen/wip/xds_to_lb/grpc/test/cpp/end2end/BUILD:446:1: Target '//test/cpp/end2end:xds_end2end_test' depends on toolchain '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8', which cannot be found: Target '@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.20.0/default:cc-compiler-k8' contains an error and its package is in error'
ERROR: Analysis of target '//test/cpp/end2end:xds_end2end_test' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.195s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 7 targets configured)
    currently loading: @upb//

I've also experienced build failures with bazel versions 18, 20, and 24. This has been on grpc releases 1.18, 1.19, 1.19.1, and 1.20.0-pre1. Each failure is different. Is there a known combination of grpc release and bazel version that is supported, or is bazel support just broken at the moment?

I think Bazel 0.22 allows passing builds

cc @vishalpowar

With #18648, the current supported bazel version is 0.23.2. Please make sure you download the correct version from Bazel directly (https://github.com/bazelbuild/bazel/releases), the apt and pip repos may not have the latest versions.

Also, @software-dov, it's impossible to support all versions of Bazel, due to how Bazel changes its API. We can only support recent versions, but this will definitely break older versions. Until Bazel hits a 1.0 release, the API breaking changes in it will continue making us to try and only support the latest versions.

Downgrading to 0.23.2 works for me.


Fix: pcluster configure should not fail with bad config files

If pcluster configure was executed against an existing config file with
wrong parameter values it failed without letting the user enter new values.
Signed-off-by: ddeidda<EMAIL_ADDRESS>

As a general suggestion we could split the different changes in different commits.
E.g one to avoid the repetition of the warning message in the cycle, one to fail when a wrong file is passed, etc

Great job!

Thanks for all the help! :)


Expired Slack link in the engineering team page.

Describe the bug
Expired Slack link in the engineering team page.

Describe the solution you'd like
Replace the expired slack link with an active link.
There is an active slack link you can find in the sef-site join us page.
Expected behavior

Are you working on it?
Yes

@jayasanka-sack Shall I work on this ?

@jayasanka-sack Shall I work on this ?

Sure, Let me provide you the link.

https://join.slack.com/t/sefheadquarters/shared_invite/zt-1jwub1lpd-RXYAMG46qXRUhOGZ7u_ewg Here's the link @janithlahirukariyawasam

@anjula-sack @jayasanka-sack please close this issue because its done


Documentation - Configuration Handling

Expected Behavior

While pouring through the documentation to learn the approaches to configuration handling, I spend time trying to replicate the subclass approach (thinking it was elegant):
class Config(object):
    DEBUG = False
    TESTING = False
    DATABASE_URI = 'sqlite:///:memory:'

class ProductionConfig(Config):
    DATABASE_URI = 'mysql://user@localhost/foo'

class DevelopmentConfig(Config):
    DEBUG = True

class TestingConfig(Config):
    TESTING = True

While it was possible to have the server run in DEBUG mode when I set the environment variable FLASK_ENV to development, or set the DEBUG=1, as well as when I ran a simple python module that set app.config['DEBUG']=True and ran the script with the python app.py command (where the name of the simple app script was app.py), it would not run in debug when I simply ran the flask server without explicitly setting the environment variable.
After a day of hunting I was finally able get clarity asking a question in Discord. It seems that the documentation refers back to configuration examples that preceded the flask CLI.
I just wanted to share this experience and suggest removing the DEBUG configuration setting from the config file documentation examples to help newbies like myself avoid a day of hair loss.
I am very much enjoying learning the framework and all the documentation otherwise. Thanks.
# Paste a minimal example that causes the problem.

Actual Behavior

Paste the full traceback if there was an exception.

Environment

Python version: 3.7.5
Flask version: 1.1.2
Werkzeug version: 1.0.1

I cannot reproduce this.
from flask import Flask

app = Flask(__name__)
app.config['DEBUG'] = True

app.run()

python app.py
$ python app.py
 * Serving Flask app "app" (lazy loading)
 * Environment: development
 * Debug mode: on
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 106-266-633

Debug mode is on

Perhaps I misrepresented myself in my description of the issue. Your additional information is what I learned in my conversation on Discord and what I was suggesting would be a helpful addition to the existing documentation. Nowhere in the documentation (that I was able to find) does it say as clearly and explicit as you just have in your "additional information":

[If] you use the flask cli, you must use environment variables, as FLASK_ENV will override the values of DEBUG, and it defaults to 'production' which sets DEBUG to false.

Thanks for taking the time to respond.

https://flask.palletsprojects.com/en/1.1.x/config/#DEBUG

This is enabled when ENV is 'development' and is overridden by the FLASK_DEBUG environment variable. It may not behave as expected if set in code.


Support for Nodejs Jasmine Tests

We are working on UI automation using Protractor ( https://www.protractortest.org ). We use Jasmine ( https://jasmine.github.io/setup/nodejs.html ) as our test runner.
We could make use of Meissa for test execution if you could add support. I met you in Selenium Conference 2018 and discussed the same with you.
Below is example of simple protractor test using Jasmine.
https://github.com/angular/protractor/tree/master/example
Please let me know if you need more info.
Thanks,
Raghav

Hi Raghav,
Thank you for writing. It was a pleasure to meet you.
To develop the plug-in, I will need a little more help since I am not a JS developer. I have like basic knowledge of JS.
So, can you give me detailed instructions on what I need to install on my machine and how to run the examples you supplied? Can you also tell me more about your use case- how many tests do you have and what your setup is.
How can we send a list of tests to the Jasmin runner? Guess we can start it from the console?
In Meissa, we need a way to get all tests from your files? Maybe we can parse them or is there a better way? In C# and Java, we use reflection to extract all test methods that we later supply to native test runners.
Anton

You need to install latest nodejs from https://nodejs.org.
Create a directory say test and place the files in https://github.com/angular/protractor/tree/master/example
Then open command prompt in test directory and run below command.
npm install protractor
node_modules/.bin/webdriver-manager update
Now to run tests,
node_modules/.bin/protractor conf.js
Jasmine identifies the tests by spec file names. In https://github.com/angular/protractor/blob/master/example/conf.js : line 15, we provide the file names as a list.
All the it blocks (lines between 2-10) in https://github.com/angular/protractor/blob/master/example/example_spec.js are treated as tests. In jasmine, we can not run the tests within a spec file in parallel. Multiple spec files can be run in parallel.
In Meissa, you can treat each spec file as a test. If you clone example_spec.js as example_spec.1js, example_spec2.js etc and show me how to run these spec files in parallel, it would be helpful.
Thanks,
Raghav

Do you need any clarifications?

Thank you for the detailed info. Sorry for not writing immediately, was traveling for a two weeks and didn't have internet most of the time. I will find time during the weekend to work on that and will give you an update if I don't understand something.
Have a nice day!

Thank you..

Okay, I managed to setup and execute the tests. Read a bit Protractor and Jasmine docs but have a few questions.
I couldn't find how to generate a tests results file. Since we need it to merge the results, find failures etc. It will be perfect if you can tell me how to use - https://www.npmjs.com/package/jasmine-reporters
The NUnitXmlReporter will be perfect since we already have logic for merging NUnit tests results and we will reuse it.
As far as I understood, describe and it- specify the different tests which can be placed in more than one file. So my question here is, how we can filter the specs, I saw that there should be --filter="a spec name" arg but couldn't make it work. All 3 tests are executed.
The goal here is I guess if you have multiple files, we will parse them and will get the names of all specs (string in describe and it functions) and then we will filter them in multiple runs. When we have multiple results file we will parse and merge them. Is this logic correct or I don't understand fully how this works?
Anton

Sorry, for not writing immediately, for some reason I didn't receive email notifications. Guess they have some bug here. Anyhow, I will check now your instructions and will write after.
Thanks,
Anton

Okay, I managed to executed the tests and save them to NUnit.xml results file. But not quite sure how to use the filter option. Can you give an example how to execute 1 of these 3 specs? Is there a way to fully specify the names- like suite.specName so that some test not to be executed twice.
About ex command:
"D:\protractor-tests>ex : set SPECS='example_spec2.js'
'ex' is not recognized as an internal or external command,"
Maybe will be easier to talk on skype, mine is - withfullspeed
Thanks

Just execute below command..
SPECS='example_spec2.js'
There is no way to specify suite.specName.. Same you can achieve by setting the SPECS like above to filter files and then using grep option to filter spec in the spec file.
Try this, we can have Skype if this does not work.

Hey man,
Yesterday, I finished the plugin. Now released a beta version. You can try it from here.
You need to use the new testTechnology=Protractor
A few other things you need to know- do not manually install the NUnit Jasmin reporter, the plugin installed it in the temp conf.js files.
For library path- you need to point the path to your conf.js file.
As we talked, I didn't include the protractor folder in the plugins since you may want to install other dependencies. So, for everything to work, you need to make all installations in the Meissa\Plugins folder (node_modules) with the latest updated version of Protractor. The plugin gets the path to protractor as a relative path starting from the Plugins folder.
I wrote the merge logic for test result files as good as I could considering the simple example tests files. I tested it, and it should work. But, you are the man to tell me 100% if it is working as expected. Keep in mind that it is best if the tests names (it) are unique since in the tests report there are not IDs, I update them based on these names.
Please try it and tell me if everything is OK. When you confirm I will move the release to productions since now, I marked it as beta. Feel free to drop me a line in Skype if you prefer.
Best,
Anton

@mmraghavendra Did you have the chance to test the new plugin? Or you are still travelling? :)

Sorry for the late reply. I have downloaded the latest beta zip file. I am able to start server and agent, but not getting how to execute tests. Can you please provide detailed steps?

Okay, maybe I didn't explain well enough in the first message. Second try.
A few things need to be done before you can start the Meissa agent.

Open MeissaFolder/Plugins/ , make all installations for Protractor there (all steps you previously told me), no need to copy your conf.js or test files here, only install protractor.

DO NOT include NUnit Jasmin reporter module to your conf.js, the plugin does it automatically

Start Meissa in agent mode, as you normally do.

Start runner with similar arguments:

meissa.exe runner --resultsFilePath="D:\protractor-tests\mergedResult.xml" --outputFilesLocation="D:\protractor-tests" --agentTag="TestAgent" --testTechnology="Protractor" --testLibraryPath="D:\protractor-tests\conf.js" --testServerUrl="http://<IP_ADDRESS>:5000"
outputFilesLocations - all tests and other JS related files are here
testLibraryPath - path to your conf.js file where all tests are described
testTechnology - should be 'Protractor'
If you want distributed run, you have to start Meissa agent on two separate machines and repeat the operation with the installation of protractor. At the end of the run, you will have all test results merged into the file mergedResult.xml

I am seeing errors in Agent and agent is getting restarted. Please refer attached snapshots.

Please let me know how this works. I am seeing a temp directory getting created with contents of outputFilesLocation. Node modules directory  in temp has only mkdirp and jasmine-reporters modules.
While outputFilesLocation i specified had node modules directory with many dependent modules.

attached dump file
08-20-2018-02-41-17-2490.txt


Bomberman Online - Help needed.

Hi if you could get bomberman online http://bomber-world.com working on windows 10 i would be grateful i will even pay if needed. there are some integrity checks after the game is loaded. But as long as you can make it at least boot up i know how to get around these issues.

Looks like you got it working in the meantime. Also starts up fine with latest experimental release.


Cross compile failed with OpenHarmony

Bug Description
Now i try to use sqlx with sqlite.   when i try to build and i get some errors with sql-macro.

Looks like sqlx-macro try to build with sqlite-sys which is built with ohos. For proc-macro lib that always be built with host system. And then i get this error.
Any suggestions?
Minimal Reproduction
Use this guide to build it. https://doc.rust-lang.org/rustc/platform-support/openharmony.html
use napi_derive_ohos::napi;
use sqlx::SqlitePool;

#[napi]
pub async fn test_sqlite() {
    let pool = SqlitePool::connect(":memory:").await.unwrap();
    let mut conn = pool.acquire().await.unwrap();

    // Insert the task, then obtain the ID of this row
    let id = sqlx::query(
        r#"
INSERT INTO todos ( description )
VALUES ( ?1 )
      "#,
    )
    .execute(&mut *conn)
    .await
    .unwrap()
    .last_insert_rowid();
}

Before build it, should run this shell.
#!/bin/sh

export CC=$OHOS_NDK_HOME/native/llvm/bin/clang \
export CXX=$OHOS_NDK_HOME/native/llvm/bin/clang++ \
export AR=$OHOS_NDK_HOME/native/llvm/bin/llvm-ar \
export AS=$OHOS_NDK_HOME/native/llvm/bin/llvm-as \
export LD=$OHOS_NDK_HOME/native/llvm/bin/ld.lld \
export STRIP=$OHOS_NDK_HOME/native/llvm/bin/llvm-strip \
export RANLIB=$OHOS_NDK_HOME/native/llvm/bin/llvm-ranlib \
export OBJDUMP=$OHOS_NDK_HOME/native/llvm/bin/llvm-objdump \
export OBJCOPY=$OHOS_NDK_HOME/native/llvm/bin/llvm-objcopy \
export NM=$OHOS_NDK_HOME/native/llvm/bin/llvm-nm \
export CFLAGS="-target aarch64-linux-ohos --sysroot=${OHOS_NDK_HOME}/native/sysroot -D__MUSL__" \
export CXXFLAGS="-target aarch64-linux-ohos --sysroot=${OHOS_NDK_HOME}/native/sysroot -D__MUSL__" \

Info

SQLx version: 0.7.4
SQLx features enabled: sqlx = { version = "*", features = ["sqlite", "macros"] }
Database server and version: sqlite 3.44.0
Operating system: target: aarch64-unknown-linux-ohos host: aarch64-apple-darwin
rustc --version: rustc 1.78.0 (9b00956e5 2024-04-29)

Looks i can't set CC directly which will cause proc-macro build failed.


Fix "Hotfixes are not applied on GitHub Enterprise." error

This has been here ever since I added this feature and nobody ever complained 😅

I have been annoyed that hotfixes disable GHE, but never realized that was not the intended behavior :D

We don't apply CSS hot fixes to GHE because they're meant to fix brand new changes on GitHub.com. The bug here was that the GHE message was showing for everyone.


build: add rust toolchain and other build packages

Add the rust toolchain and other dependencies to avoid issues at build time.
Ref https://github.com/canonical/bundle-kubeflow/issues/989

@orfeas-k I think we can close this PR because these packages will not be required after all. Please check https://github.com/canonical/bundle-kubeflow/issues/989#issuecomment-2247407205 for more context on the actual solution. Thanks!


Remove useless @Configuration on MongockSpringConfiguration

Remove useless @Configuration on MongockSpringConfiguration and causes issues with spring-native
Description
When trying to use mongock in a spring-native application, the useless @Configuration annotation on the @ConfigurationProperties class confuses the aot engine and prevent to start the app.
Checklist before PR

[x] Branch name follows strategy (ISSUE|FEATURE|REFACTOR|DOC|TEST)[-issue_number][/description_underscored].
Ex: ISSUE-294/fix_read_concern_driver_v3

[x] If depends on a new change in the mongock-core project, version updated and snapshot removed

[x] Unit tests provided

[x] Integration tests provided in separated project

[ ] Github build passing

[x] Codacy analysis not adding new issues

[x] Documentation updated

[x] Example projects updated

Hello @olivierboudet ,
yur change looks good, thanks!! however, can you please make the PR agains develop branch? It's the default one, master is what's live and it's used for relases 😃
We need to update the collabration documentation to reflect this. Thanks!

Oh yes, it,seems my old fork stayed on the old master default branch :)
I sent another PR against develop :)


docs: Have Makefile print generated image tags when running with V=0

When building Docker images for documentation with V=0, the Makefile for documentation does not print the name of the generated images.
One particular example of calling the Makefile with V=0 is for Cilium's runtime tests in CI, with .travis/build.sh calling:
`V=0` make -j 2 --quiet

This calls the default target for Cilium's main Makefile, which relies (among others) on the postcheck target, which in turns calls the check target from Documentation/Makefile, passing the V=0 flag. The absence of the docs-builder string from the logs make it harder to figure out whether the workflow successfully built the image.
This commit simply adds the image tag (passed to Docker with --tag, but not actually containing the version tag) to the invocation of $(ECHO_DOCKER), so that Documentation/Makefile can print it when we request a non-verbose build with V=0.

/test

This probably doesn't matter too much for older branches, but I've tried to keep the doc framework mostly identical on all branches and this commit should be trivial to backport, so let's go for it.


Implement Channel Upgrade Try functionality for 04 channel

Description

closes: #1619
This PR adds the ChanUpgradeTry handshake.
A few smaller items will be addressed in follow up issues.

Event Emmision
Clean up upgrade channel inputs
adding a validateProposedUpgradeChannelFields function
create a generic k.getConnectionForVerification function
generic if !connectionEnd.IsOpen()
Add helper function for configuring upgrade channel see this comment

Commit Message / Changelog Entry
N/A  - part of feature branch
see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Codecov Report

Merging #3333 (903396f) into cian/issue#1608-add-verifychannelupgradesequence-method-to-03-connection (add66ad) will decrease coverage by 0.69%.
The diff coverage is 0.00%.

Additional details and impacted files

@@                                             Coverage Diff                                              @@
##           cian/issue#1608-add-verifychannelupgradesequence-method-to-03-connection    #3333      +/-   ##
============================================================================================================
- Coverage                                                                     78.27%   77.59%   -0.69%
============================================================================================================
  Files                                                                           186      186
  Lines                                                                         12980    13094     +114
============================================================================================================
  Hits                                                                          10160    10160
- Misses                                                                         2386     2500     +114
  Partials                                                                        434      434

Impacted Files
Coverage Δ

modules/core/04-channel/keeper/upgrade.go
26.89% <0.00%> (-55.17%)
:arrow_down:

modules/core/keeper/msg_server.go
47.01% <0.00%> (-2.99%)
:arrow_down:

closing in favour of https://github.com/cosmos/ibc-go/pull/3478


Added SolarStatus Watchface and Battery Guestimate Widget repo links.

Also found this repo if you want to add its links: https://github.com/GriffW/Garmin-Applications

Also found this repo if you want to add its links: https://github.com/GriffW/Garmin-Applications

Looks useful, feel free to PR!


Add view animation convenience functionality

E.g.

zoom to coordinates/zoom
zoom to geoJSON feature (passed as feature)
zoom to rendered feature via vector/vector tile layer

Please also consider zoom to extent

This could be an animateView property / animate-view attribute (I'd say default to true). If this is set, setting the center and/or setting the zoom would animate instead of "just" setting it.
It would need to check in the _changedProperties' (updated` hook) if both of them changed at the same time and do the animation only once.
Regarding features, extent etc. I don't have a clear idea yet...

Following scenarios are thouthg of:

setting zoom and/or center: animate view to given zoom/center
setting extent: animate view to given extent (overrules any zoom or center settings)
setting layer property fitView: true: animate view to layer extent (overrules anything set before)
selectInteraction.selectById([id], true/{fitOptions}): animate the view to fit progammatically selected feature(s)

Just a minor consideration of setting layer property fitView: true - how would it behave if more layers have this property? First found or the one which was freshly updated?

The last option is once a feature is already loaded in a vector layer, it is possible to zoom to the available features?
I guess at least for stac we usually will have a bbox for the collection or item, so the extent should be ok for those cases.
I can't think of any more options right now, not sure if being able to pass a feature would make sense.

Two things are not fully implemented yet:
1.) selectById
we do have the method to highlightById, which basically is selectById, and we also have the panIntoFeature option on the select interaction. However, we don't have both together yet.
2.) fitView layer property
I'm not sure if we really want this option on the layer, as multiple layers will interfere with this and having an extent on the eoxMap and an overruling extent on the layer seems counter-intuitive. I think it would be best if the application could just control the zoomExtent property

Closed in favor of the two newly created issues.


[#4551]  feat(iceberg): add S3 and GCS support for IcebergRESTService docker image

What changes were proposed in this pull request?

add AWS and GCP bundle jar to IcebergRESTServer docker image
use environment variable to change the config

Why are the changes needed?
Fix: #4551
Does this PR introduce any user-facing change?
no
How was this patch tested?
run SQL with access S3 and GCS data

@jerryshao @yuqi1129 @jerqi please help to review, thanks

Please update the doc docker-image-details.md also.

updated, please help to review again

@yuqi1129 any other comments? @jerryshao  do you have time to review again?

@yuqi1129 any other comments? @jerryshao do you have time to review again?

I have no further comments.


populate_db: Simplify how we create reactions.

For 3000 messages and 400 users, this saved
about 30 seconds.
We only do two queries per batch of messages
now, and the algorithm is easier to analyze,
as it's just three nested loops.

Testing plan:
GIFs or screenshots:

This is great, merged as 99e725cbde8f2bef5f5aeca3f157b248455cc9de after adjusting comments.  I think ideally the distribution would favor more messages with just a single reaction, but that's an easy follow-up tweak if we find it worth doing after using this for a while.  @galbwe FYI.
I had a thought while reviewing this that we can probably make populate_db with a large number of users much faster by creating all the num_extra_users as long_term_idle, which will in turn defer generating UserMessage rows for these users who are unlikely to ever log in.


Add proper way to navigate to filter page

Is presently being done through training page control bar

Remember to update the announcement about the filter feature on the front-page


[pwm] Wire up integrity alert

@msfschaffner @weicaiyang @cindychip Do I need to check alert signals at the unit level?

@msfschaffner @weicaiyang @cindychip Do I need to check alert signals at the unit level?

Yes, although I believe for this particular one @weicaiyang is developing partially automated tests.
Is that right @weicaiyang?

@msfschaffner @weicaiyang @cindychip Do I need to check alert signals at the unit level?

Yes, although I believe for this particular one @weicaiyang is developing partially automated tests.
Is that right @weicaiyang?

Right, the automatic tests (tl_intg_err and alert_test) should cover this alert, so we don't need to add other tests for it.


Backdrop with NavigationRail

Is your feature request related to a problem? Please describe.
Material Design Guideline have come up with a new component called NavigationRail which have explained its behaviour with backdrop (Check Backdrop section in the Guideline).
Describe the solution you'd like
The NavigationRail should rest on backLayer when backdrop is active (backLayer is visible) as shown in the picture in guideline

@WieFel Let me know your views on it.

Interesting!
As far as I can see, NavigationRail is aimed for tablet/desktop sized screens, or am I wrong?
I think we could include it in the future, but I would suggest to do that after v1.0.


Add XML Docs to Design Rule Classes (1)

Add docs to the following:

[x] SqlServer.Rules/Design/WrapStatementsWithTryCatchRule.cs
[x] SqlServer.Rules/Design/WrapStatementsWithTransactionRule.cs
[x] SqlServer.Rules/Design/WaitForRule.cs
[x] SqlServer.Rules/Design/UseProperCollationInTempTables.cs
[x] SqlServer.Rules/Design/UseParameterNamesWithProcsRule.cs
[x] SqlServer.Rules/Design/UseColumnListWithInsertsRule.cs
[x] SqlServer.Rules/Design/UpdateWithoutWhereRule.cs
[x] SqlServer.Rules/Design/UnusedVariablesRule.cs
[x] SqlServer.Rules/Design/UnusedParameterRule.cs
[ ] SqlServer.Rules/Design/TypesMissingParametersRule.cs
[x] SqlServer.Rules/Design/TopWithoutOrderByRule.cs
[x] SqlServer.Rules/Design/TableHasUniqueConstraintRule.cs
[x] SqlServer.Rules/Design/TableHasPrimaryKeyRule.cs
[x] SqlServer.Rules/Design/StartIdentity1000Rule.cs
[x] SqlServer.Rules/Design/RaiseErrorWithoutLogRule.cs
[x] SqlServer.Rules/Design/ProcedureContainsGrantRule.cs
[x] SqlServer.Rules/Design/PredicateCompareRule.cs

a bunch of these did not have the ShouldIgnore function so best i can tell their <IsIgnorable> is accurate but digress with the CSV

That is entirely possible. Can you list the ones that the CSV says should be ignorable, but don't have the function in a separate issue? I will address them.

Figure will extract the xml docs and then diff with the CSV before deleting it

Skipped the one class TypesMissingParametersRule since it's not a rule


Unable to spawn Julia executable while debugging an extension in VS Code insiders, but works in VS Code stable

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.88.0-insider
Commit: cc1f5e3acfad98ed519befc1ebfd199777d135f4
Date: 2024-03-07T05:50:38.946Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.3.0

Steps to Reproduce:
I'm working on the Julia extension, and found that while debugging the extension in VS Code insiders I'm unable to spawn the Julia executable,
However the exact same code works when debugging the same extension in VS Code stable (i.e. spawning julia executable works).
Here's the error message in the console window
 ERR spawn /Users/donjayamanne/.juliaup/bin/julia ENOENT: Error: spawn /Users/donjayamanne/.juliaup/bin/julia ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:284:19)
    at onErrorNT (node:internal/child_process:477:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

I feel this is a regression in VS Code insiders as it works in Stable.
Not sure where the problem is, i tried changing the arguments and that does not make any difference whatsoever,
Seems to be related to debugging.
Note

The executable is valid,
Spawning executable works in Stable
Spawning executable works in Insiders when not debugging

@connor4312 @deepak1556 /cc not sure where the problem lies.

Can you share the output of ls -l /Users/donjayamanne/.juliaup/bin/julia as well as verifying whether any cwd you're using when spawning the binary exists?

ifying whether any cwd you're using when spawning the binary exists?

You're right that doesn't exist, wonder why it works in stable.
Anyways, closing as the cwd is invalid.
thanks


Fix up the Gradle build file

See the attempt with Redis-Demo on the hotfix branch.

In progress.  It checks out on the command line but IDEA is pending.


[PREVIEW] Caffeine and converter wrapped cache changes

This PR is more to supply full test coverage.  I believe there are still some issues with as-modules that need to be patched and some other test failures.

@wburns I've fixed those testsuite failures in https://github.com/infinispan/infinispan/pull/4577

@rvansa Thank you very much!    I was trying to figure out how those were failing randomly, but didn't have much luck.

@wburns actually it was @danberindei who realized what the problem is, I am just the coding ape...

Should be ready as long as tests still pass :) Haven't checked it in a while.

fyi, released 2.3.4. Please upgrade prior to merging.

Updated.

Looks like some total order write skew are failing intermittently..

Doubtfully related, but FYI:
The cache does have some randomness to protect against HashDoS style attacks. That means tests can't rely on predictable order of eviction.

The test failures are also in master, if I backport just the test - so it seems like a latent bug with passivation.

Actually the randomness is what is causing the issue, but that itself isn't the issue.  It has uncovered a bug in write skew check with a cache store.  The bug resets the version of an entry.  And the test prior always evicted the same entry thus the versions matched, but when each node evicts a different entry the versions don't match anymore.

Finally a run passed :) http://ci.infinispan.org/viewLog.html?buildId=44231&tab=buildResultsDiv&buildTypeId=bt9

This can be integrated in with #4657.

@danberindei I will add the updates to the off heap PR #4673

@wburns this failure sounds like could be related:
testRemoveFailWriteSkewWithPassivation(org.infinispan.container.versioning.DistWriteSkewTest)  Time elapsed: 0.129 sec  <<< FAILURE!
java.lang.AssertionError: The key was not evicted after 10 inserts
at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24)
at org.infinispan.container.versioning.AbstractClusteredWriteSkewTest.doTestWriteSkewWithPassivation(AbstractClusteredWriteSkewTest.java:316)
at org.infinispan.container.versioning.AbstractClusteredWriteSkewTest.testRemoveFailWriteSkewWithPassivation(AbstractClusteredWriteSkewTest.java:152)


You have to sign in to use Huraga

Huraga forces you to login before letting you see any content in the website.
New visitors shouldn't have to sign up to see what's sold.

i wasnt sure if this was the same issue so i posted it: https://github.com/FOSSBilling/FOSSBilling/issues/306

i wasnt sure if this was the same issue so i posted it: https://github.com/FOSSBilling/FOSSBilling/issues/306

it's unrelated.

thanks

Resolved after PR was merged


chore: Change logs for sessionSigs support to remaining functions

What
This is the change logs for the PR#54

lgtm


Automate testing

It would be cool, if the loading tests could be done automatically. The easiest use case would be to load a save file, save after everything is done and check whether the created save is the same as the one that was loaded. Maybe tools like Autohotkey can help with that.

Uses pyautogui to automically load the Gloomhaven mod, loading a savefile, saving it again and comparing wether the savefile has the expected format. Currently only supports loading the latest version of the mod, but will also enhance to load from an existing save file, to easily test backwards compatibility.


tortoise: collect details on the number of specified layers

this will collect:

opinion on latest layer
block that should be applied on latest layer
number of blocks by layer

this collector is expensive and should be enabled only for debug. to enable it set tortoise-collect-details: 200 in tortoise section. number of layer that are metered can't be larger then the window size.

bors merge

bors merge

bors merge


feat: support custom tsconfig.json

Implements the cli option --tsconfig and solves #36

(again) 'lint' script and some tests fail due to an 'EPERM' error (see #74)

Cheers
fixes #36
closes https://github.com/privatenumber/pkgroll/pull/37

closes https://github.com/privatenumber/pkgroll/pull/37

:tada: This issue has been resolved in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Thanks for contributing @error-four-o-four & @Pirosauro
Great work


export the sourceFactory?

Would be nice to programatically generate urls for the implementation with material2
import { Pipe, PipeTransform } from '@angular/core';
import { AvatarSource } from 'ngx-avatar';
import { SourceFactory } from 'ngx-avatar/lib/sources/source.factory';

@Pipe({
  name: 'gravatar'
})
export class GravatarPipe implements PipeTransform {

  constructor(private sourceFactory: SourceFactory) {}
  transform(value: string, [size]: [number]): any {
    return this.sourceFactory.newInstance(AvatarSource.GRAVATAR, value).getAvatar(size);
  }
}

yarn add https://github.com/Venipa/ngx-avatar#build/dev
if people want to try it


Ubuntu Runner Az Cli-Unable to parse parameter

Description
I currently use a JSON string to pass parameters into deploying ARM templates to Azure using Az Cli using the command az deployment group what-if.  The task being used is below:
- task: AzureCLI@2
    displayName: What If Template
    inputs:
      azureSubscription: ${{parameters.azureSubscription}}
      scriptType: pscore
      scriptLocation: inlineScript
      inlineScript: |
        az deployment group create `
          --resource-group ${{parameters.resourceGroupName}} `
          --template-file ${{parameters.templatePath}} `
          --parameters '$(templateParameters)' `
          --what-if

The variable templateParameters is a JSON string e.g. {\"environment\":{\"value\":\"dev\"}}. When using the ubuntu image  20221114.1 I get the error **ERROR: Unable to parse parameter: **. This error does not happen when using 20221027.1 or when using the windows-latest image. The broken image is using Az Cli 2.42 and the working Ubuntu image is using Az Cli 2.41.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Image: ubuntu-20.04
Version: 20221114.1
Is it regression?
Yes, Image: ubuntu-20.04 Version: 20221027.1
Expected behavior
I would expect the json string parameters to be parsed and applied to the ARM template
Actual behavior
Error produced by Az Cli of Unable to parse parameter
Repro steps

Create pipeline using the ubuntu-latest vmImage
Check that the os runner is 20221114.1
Build JSON string parameters with the quotes escaped e.g. {"environment":{"value":"dev"}
Pass the parameters into the az deployment group command e.g. az deployment group what-if --resource-group rg-test  --template-file .\armtemplate.json --parameters '{"environment":{"value":"dev"}}'

Hello @milkyware
It looks like related with new Az Cli version. It happens, yes. For example similar situation https://github.com/Azure/azure-cli/issues/23854. We'll take a look at issue from our side. But it will be very nice if you open an issue with Az Cli developers so they can cover it from their side.

Hi @erik-bershel, that's fine, thanks. Just thought I'd start here as the windows image using Az Cli 2.42 is fine. Thanks for the link to the existing issue as well

@milkyware
Due to a bunch of issues with PowerShell 7.3 we decided to rollback latest updated images to previous version. It will cover your incident too. But only temporary I suppose. We'll return to your issue with the next image updates. And there is a chance to get new Az Cli release with the next images updates what would be very nice, but I don't think it will work.

For history. We rolled back "Ubuntu 20 - 20221114.1" image. On the very next week we'll deploy new one with same Az Cli but with pinned PowerShell 7.2. We'll see what triggering that bug with that deployment, was it PS 7.3 or Az Cli 2.42. After it we'll decide what should we do next.

Here is more information about my issue https://stackoverflow.com/questions/77577515/error-unable-to-parse-parameter-json-file-when-trying-to-deploy-bicep-with-gith


docs(tutorial/3 - Filtering Repeaters): trim title

trims the title when query is empty.

I think that's too much for a tutorial. The examples should focus on the exact stuff that is implemented, not the fine-tuning (which might be quite confusing to beginners).

OK,for a tutorial that does be too much


FeatureAdded:HandleRats

closes #10

now returns a string if rats in room and bread in inventory.
also edited the goto function according to handle rats return statement.


Add documentation for negated ignored files and add a test for it as well

I was looking into the source code to check how to add support for negated ignore because I didn't find any mention of it into the documentation until I went through the ignore crate source code, here in particular. Would have saved me a lot of time if such an example existed so here we are. :)

Updated!

Finally fixed the formatting. ^^'
Strangely enough, if I run cargo fmt on rustfmt, it formats other files that fail tests in CI.

Finally fixed the formatting. ^^'
Strangely enough, if I run cargo fmt on rustfmt, it formats other files that fail tests in CI.

Interesting! I wonder what's going on there


Document versioning scheme as EffVer

Summary
After some discussion with multiple members in the Discord channel, EffVer was brought to my attention and it seems to be a way better fit.
Next release will be a stable release 2.0.0 and EffVer will be applied from then on
Closes #1997

For reference: https://jacobtomlinson.dev/effver


Keynote add to calendar link is pointing to the wrong url

https://deploy-preview-388--cds2019.netlify.app/devsummit/schedule/keynote/

I've fixed this


Issue using RPI.GPIO Module in custom python scripts

I'm currently running the docker image on a Raspberry Pi 3.
I've installed the RPI.GPIO module with the command apt install python3-rpi.gpio and made the container privileged to have access to the GPIO Pins.
Once I try to import the RPi Module into the Custom script for Intent Handling I'm receiving this error in the console:
rhasspy    | DEBUG:CommandIntentHandler:['/profiles/en/command.py']
rhasspy    | Traceback (most recent call last):
rhasspy    |   File "/profiles/en/command.py", line 7, in <module>
rhasspy    |     import RPi.GPIO as GPIO
rhasspy    | ModuleNotFoundError: No module named 'RPi'
rhasspy    | ERROR:CommandIntentHandler:in_started
rhasspy    | Traceback (most recent call last):
rhasspy    |   File "/usr/share/rhasspy/rhasspy/intent_handler.py", line 328, in in_ready
rhasspy    |     self.command, check=True, input=json_input, stdout=subprocess.PIPE
rhasspy    |   File "/usr/lib/python3.7/subprocess.py", line 512, in run
rhasspy    |     output=stdout, stderr=stderr)
rhasspy    | subprocess.CalledProcessError: Command '['/profiles/en/command.py']' returned non-zero exit status 1.

Running the command python3 /profiles/en/command.py < testing_json_payload.json inside the running docker works just fine using the imported RPi Module.
Once I try using it in the custom script it doesn't see the module.
Is there a specific way to install the needed modules to be available in the sub-process?
Custom Script: https://hastebin.com/edejubejid.py
Version: 2.4.20

Found that I needed to add it to the Virtualenv. If anyone comes across this post here is how to add it to the docker.
Dockerfile

WORKDIR /usr/share/rhasspy

RUN apt-get update &&  \
  apt-get install -y build-essential

RUN /usr/share/rhasspy/.venv/bin/pip install RPi.GPIO

ENTRYPOINT ["/run.sh"]

Docker-compose:
services:
  rhasspy:
    container_name: rhasspy
    build: ./dockerfiles/rhasspy
    restart: always
    volumes:
      - "$HOME/.config/rhasspy/profiles:/profiles"
      # - "$HOME/.config/rhasspy/asound.conf:/etc/asound.conf"
    ports:
      - "12101:12101"
    devices:
      - "/dev/snd:/dev/snd"
      - "/dev/gpiomem:/dev/gpiomem"
    command: --user-profiles /profiles --profile en


Require "Epic" for a user story

What type of PR is this?
NA
What does this PR do / why we need it:
It asks "Epic" information for creating a "User Story" because Epics are high level items that can have a bunch of User Stories. And Epics are what are tracked by Milestones.
Which issue(s) this PR fixes:
Fixes NA
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

/lgtm
/override ci/prow/psi-kubernetes-integration-e2e
/override ci/prow/unit
/override ci/prow/v4.7-integration-e2e


&attributes not working

The "and attributes" syntax does not appear to work.
http://jade-lang.com/reference/attributes/
I've tested against online jade-to-html translators and it appears to be specific to this package.

We currently support
input($dyn = attrs)

Which is equivalent to spacebars
<input {{attrs}}>

We probably want to support the jade syntax instead of our custom $dyn thing. That would be
input&attributes(attrs)

+0.5, for use with this package: https://github.com/dalgard/meteor-viewmodel which uses dynamic attribute syntax (makes the code a bit cleaner)

+1 for &attributes

@mordra: For dalgard:viewmodel, I recommend the syntax that has since been added by dalgard:jade.


Update docker image

Hi, thanks for the tool!
Please update the docker image, the current version has outdated code that report false positive Exposed Run Inside Container that was fixed on https://github.com/aquasecurity/kube-hunter/pull/33
Also have tagged images would be nice.

Hi @yagonobre. Thanks for the feedback.
I've manually built the image with the new master code, so you can try it now.
In addition - we will add automatic build in the next few days.

Apologies, I forgot to rebuild after #33!
On Sun, 2 Sep 2018 at 16:40, jerbia<EMAIL_ADDRESS>wrote:

Hi @yagonobre https://github.com/yagonobre. Thanks for the feedback.
I've manually built the image with the new master code, so you can try it
now.
In addition - we will add automatic build in the next few days.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aquasecurity/kube-hunter/issues/36#issuecomment-417939444,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAb_eEYDXcAg_yveZdG9KYsVm0mQ3BJwks5uW_vsgaJpZM4WUfv5
.

--
Liz Rice
lizrice.com | +44 (0)<PHONE_NUMBER> | skype lizrice

@jerbia and @lizrice thanks 😄


Make a full review of the web administration

Make sure we did not loose any information during the internationalisation process.

Done.


Fix improperly named BPS patcher

This tool is quite obviously a fork or variant of https://media.smwcentral.net/Alcaro/bps/. That tool has never been named Flips, Floating IPS, or any variant thereof; its name has always been CPS.
I don't particularly care what you name this fork, or if it's named anything at all, but don't steal a completely different project's name.

Sorry for the inconvenience!


Implement USDT approval reset everywhere

Overview
Spotted for savers in https://github.com/shapeshift/web/pull/7392#pullrequestreview-2211222071:
Other domains are also affected
Savers

🚫 Approval needed (reset needed, unhandled by savers)
https://jam.dev/c/745cfa64-f6c2-404c-b1c2-3409d288037f
Borked gas estimations, though I was able to repro on develop

As can be seen in the Jam above, we're unable to continue with the deposit because of reset needed
LP
Things actually seem to be working there, and no reset seems to be needed. See below for an approval needed higher than the existing one (i.e reset). Can't test because of too low gas, but gut feel is the reset logic is only needed for USDT on mainnet?
https://jam.dev/c/a8d092e8-d770-4a1c-b387-2578c6447e29
Lending
I was unable to test, this needs to be confirmed to be an issue with mainnet USDT for repayments (and by extension, to possibly not be an issue for non-mainnet USDT?)
References and additional details
https://github.com/shapeshift/web/pull/7392 - same reset logic should be applied to all domains with USDT: savers, lending, LP
Acceptance Criteria

USDT contracts over all of our supported networks are sanity-checked to confirm they all require an allowance reset (i.e look for the approve function, see https://github.com/MetaMask/metamask-extension/issues/18610)
After confirming whether or not those USDT flavours are affected by this issue, test savers (confirmed borked on mainnet, see above), LP and lending with a known affected flavour, and improve allowance reset step for USDT
Remove swapper reset checks/logic for USDT flavours that do not require it

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

Confirmed mainnet is the only one affected:

Mainnet approve()

Avalanche approve()

Arb approve()

BSC approve()

OP approve()

Gnosis approve()

Polygon approve()

Moving back to up next/groomed for board vis since this will be tackled as a two-step work (make USDT approval resets mainnet only / actually implement everywhere)


Reproducibility instructions

Hello!
Thank you for uploading the efficient-mcts code. However, it appears that the current version is not reproducible. For example, the imports for pine module (which seems to be a custom-written package) looks like to be broken, and the atari.py module is missing.
Could you please provide suggestions on how to resolve these issues to run the code quickly and successfully? Also, could you let us know approximately when we can expect a working version?
Thank you in advance!

Hi! I apologize for the inconvenience you experienced. We've fixed the errors and added instructions for running the experiments in the README.md file.
If you encounter any further problems or have questions, please let me know! 🙂


combine-to-osv doesn't reflect last modified time of component parts

Describe the bug
Currently, the modified time of an OSV record emitted by combine-to-osv reflects the modified time of the underlying CVE record.
This means that if one of the PackageInfo parts combined has changed, the resultant OSV record is not routinely re-imported (see also https://github.com/google/osv.dev/blob/master/tools/datafix/reimport_gcs_record.py)
Expected behaviour

When one of the PackageInfo part files has changed, the OSV record is re-imported.
The modified field reflects the most recent modification to one of the parts that compromise the OSV record

Additional context
One possible solution is for https://github.com/google/osv.dev/blob/216c120c52f7ee7c310aba51cbaa57418b64ed2f/vulnfeeds/cmd/combine-to-osv/main.go#L93-L108 to also return the most recent timestamp of all of the parts files loaded

Thanks Andrew for recording this issue.
I just noticed that almost all the Debian part files will be modified each time run. This is because it uses a map to store all Debian releases, so the order is not the same every time when it outputs to the PackageInfos file.
I will need to fix this to avoid unnecessary updating. Also checked other parts output, Alpine doesn't have this issue, but I not sure about nvd (all last modified dates are today).


An Emacs package cannot have more than 17 dependencies

Describe the bug
It appears that when a Emacs package starts to have more than 17 dependent packages something related to implicit hooks goes wrong. Consider the following:
let
  pkgs = import <nixpkgs> {};
  mkConfig = epkgs: epkgs.trivialBuild {
    pname = "my-test";
    src = pkgs.lib.sourceByRegex ./. [
      "^.*\.el$"
    ];
    unpackCmd = ''
      echo "This is it: $curSrc"
      echo "Basename: $(basename -- "$curSrc")"
      echo "$(stripHash "$curSrc")"
      _defaultUnpack "$curSrc"
    '';
    packageRequires = with epkgs; [
      ace-link
      ace-popup-menu
      ace-window
      aggressive-indent
      auctex
      avy
      avy-menu
      char-menu
      counsel
      cyphejor
      direnv
      f
      yaml-mode
      zenburn-theme
      ztree
      zygospore
      zzz-to-char
    ];
  };
in mkConfig pkgs.emacs26Packages

In this form nix-build fails:
$ nix-build
these derivations will be built:
  /nix/store/4sviv2ilrkj4ww1c7qjdng2rk4xhirj2-emacs-my-test.drv
building '/nix/store/4sviv2ilrkj4ww1c7qjdng2rk4xhirj2-emacs-my-test.drv'...
unpacking sources
unpacking source archive /nix/store/zsz6k61jzdq8ykzsrknz04jnjm5wa3w5-emacs
Current source: /nix/store/zsz6k61jzdq8ykzsrknz04jnjm5wa3w5-emacs
/nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup: line 82: /nix/store/3qgg8xzdyfd7nql0qlkb1xpnrfz4k1s2-coreutils-8.31/bin/basename: Argument list too long
Basename on curSrc:
/nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup: line 805: /nix/store/3qgg8xzdyfd7nql0qlkb1xpnrfz4k1s2-coreutils-8.31/bin/basename: Argument list too long
Strip hash:
/nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup: line 805: /nix/store/3qgg8xzdyfd7nql0qlkb1xpnrfz4k1s2-coreutils-8.31/bin/basename: Argument list too long
/nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup: line 826: /nix/store/3qgg8xzdyfd7nql0qlkb1xpnrfz4k1s2-coreutils-8.31/bin/cp: Argument list too long
/nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup: line 805: /nix/store/3qgg8xzdyfd7nql0qlkb1xpnrfz4k1s2-coreutils-8.31/bin/basename: Argument list too long
/nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup: line 826: /nix/store/3qgg8xzdyfd7nql0qlkb1xpnrfz4k1s2-coreutils-8.31/bin/cp: Argument list too long
do not know how to unpack source archive /nix/store/zsz6k61jzdq8ykzsrknz04jnjm5wa3w5-emacs
builder for '/nix/store/4sviv2ilrkj4ww1c7qjdng2rk4xhirj2-emacs-my-test.drv' failed with exit code 1
error: build of '/nix/store/4sviv2ilrkj4ww1c7qjdng2rk4xhirj2-emacs-my-test.drv' failed

Looking at the /nix/store/ikywdrvfib46c2rwiphig16bppv8csv4-stdenv-linux/setup file, I found that it first sees that src points to a directory. So it tries to strip the hash from the directory name and copy it. basename invocation inside of stripHash fails. When I added an explicit invocation of basename, it reported line 82, this is inside of _callImplicitHook function definition. I have no idea what is going on here.
Interestingly, if I delete just one dependent package from the list, nix-build starts to pass:
$ nix-build
these derivations will be built:
  /nix/store/b3r3hbjrqczzmgrgdn5adfip5xqfzjp0-emacs-my-test.drv
building '/nix/store/b3r3hbjrqczzmgrgdn5adfip5xqfzjp0-emacs-my-test.drv'...
unpacking sources
unpacking source archive /nix/store/zsz6k61jzdq8ykzsrknz04jnjm5wa3w5-emacs
Current source: /nix/store/zsz6k61jzdq8ykzsrknz04jnjm5wa3w5-emacs
Basename on curSrc: zsz6k61jzdq8ykzsrknz04jnjm5wa3w5-emacs
Strip hash: emacs
source root is emacs
patching sources
configuring
no configure script, doing nothing
building
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/n2bl2cckismbwfjvgff8fbkws6xky0sv-emacs-my-test
strip is /nix/store/7wy2mifb0igrp9hzf9dzwddadbs7ai7d-binutils-2.31.1/bin/strip
patching script interpreter paths in /nix/store/n2bl2cckismbwfjvgff8fbkws6xky0sv-emacs-my-test
checking for references to /build/ in /nix/store/n2bl2cckismbwfjvgff8fbkws6xky0sv-emacs-my-test...
/nix/store/n2bl2cckismbwfjvgff8fbkws6xky0sv-emacs-my-test

It would be nice if we could fix this bug. I understand that this many dependencies is unusual for Emacs packages, but I'm experimenting with defining my configuration as a package which depends on packages that I use, so finally I can use emacsWithPackages and get Emacs with my configuration included and pre-built.
To Reproduce
You can use the snippet from above. I used b2935fbeceaea0b64df4401545d7c8ea29102120 of nixpkgs.
Metadata

system: "x86_64-linux"
host os: Linux 5.4.25, NixOS, 20.03.git.b2935fbecea (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.4pre7250_94c93437
channels(mark): "nixos-18.09.2337.5d972dd2c94"
channels(root): "nixos-19.03.173651.ca6b6595392"
nixpkgs: /home/mark/nixpkgs

I have more than 17 dependencies: https://github.com/grahamc/nixos-config/blob/master/packages/emacs/default.nix#L37

This is different. You use emacsWithPackages, whereas I try to define a Emacs Lisp package itself with its own dependencies. It is as if magit had 17+ dependencies and failed to build.

The problem appears to be something wrong in calculating the  EMACSLOADPATH, where each plugin is included many times:
    unpackPhase = ''
      env | grep EMACSLOADPATH | tr : '\n' | sort | uniq -c | sort -nr
    '';

with 16 dependencies:
     63 /nix/store/z6vpclw5qy8mhshln5xqvx4lpa1a49lp-emacs-swiper-20200105.1958/share/emacs/site-lisp
     63 /nix/store/x044jrmzv37ymnm85mjg66gi62c5nfhf-emacs-avy-20191106.1234/share/emacs/site-lisp
     63 /nix/store/wjvyy9n1jhipk4dx59r43vbnhn39ixcd-emacs-ace-popup-menu-20190713.1337/share/emacs/site-lisp
     63 /nix/store/s369q2b6r2g2p44y84sdap3cfj8p939l-emacs-f-20191110.1357/share/emacs/site-lisp
     63 /nix/store/qm24rw44f5j7ysdj4px8h86h4yvc5sn9-emacs-ace-window-20191022.1203/share/emacs/site-lisp
     63 /nix/store/q8i9kxr0hcczwhccxpg3b66yrx698x5w-emacs-auctex-12.2.0/share/emacs/site-lisp
     63 /nix/store/q4wphgsh4cm2f7ixgrvjffhjbcv3xncq-emacs-direnv-20191016.1907/share/emacs/site-lisp
     63 /nix/store/pll7a87qw27xyipxvjfq0798wi4ndyia-emacs-26.3/share/emacs/site-lisp
     63 /nix/store/lxd3a0r5fvjr69g0iva6jvk70b9jzsn3-emacs-yaml-mode-20191127.2314/share/emacs/site-lisp
     63 /nix/store/lkk1b8c4rn1fzcbn14d2lxfldp172pfn-emacs-counsel-20200105.1947/share/emacs/site-lisp
     63 /nix/store/iglhwyjc6jpra6kx1hwr6kb6a73x2526-emacs-ztree-20191108.2234/share/emacs/site-lisp
     63 /nix/store/d6zp6kanhi36q4a7wq6qnnzvk22s11wg-emacs-cyphejor-20190713.1339/share/emacs/site-lisp
     63 /nix/store/bxbzc1widlzjbw9y5s9m3158zc9mqdch-emacs-aggressive-indent-20190828.1828/share/emacs/site-lisp
     63 /nix/store/9ja2rbl0apmb1q5slb9az7y3yn735aqx-emacs-zygospore-20140703.852/share/emacs/site-lisp
     63 /nix/store/58ralp4c2pnqwjjrxi0vm6d2nhh5j586-emacs-dash-20191109.1327/share/emacs/site-lisp
     63 /nix/store/4y35kqnrkaxcqfsa0rrq8lx2mhx54hi5-emacs-zenburn-theme-20200105.1010/share/emacs/site-lisp
     63 /nix/store/4s7qznw8q62p9dn84wy2l8wld9bpipg5-emacs-s-20180406.808/share/emacs/site-lisp
     63 /nix/store/3mf3xcr8r2qr8p5gfyigrxvdb96rhgz4-emacs-char-menu-20190713.1343/share/emacs/site-lisp
     63 /nix/store/21b3f1h6jrvw68f2i5ycc04gd5cbwkzp-emacs-avy-menu-20190713.1348/share/emacs/site-lisp
     63 /nix/store/1z74f3rp27bpdhl9hrb56v7pndyhcsgq-emacs-ivy-20200105.1946/share/emacs/site-lisp
     62 /nix/store/q7d8zj1lyqbldvzkdfq92lz6yw5dgqdw-emacs-zzz-to-char-20190713.1344/share/emacs/site-lisp

with 8:

Could it be that if two plugins depend on the same package it's simply included several times?

Perhaps some filtering here https://github.com/nixos/nixpkgs/blob//pkgs/build-support/emacs/setup-hook.sh#L1-L7 is necessary.

Appears to be fixed by #82604.


Add custom meta panels for pages.

JS.

Install react
Add custom meta fields for panels and short title
Change admin script to block editor script.
PHP.
Register the required fields.
Add helper function to return if panel should be shown.

I'm yet to add documentation/comments to this. On hold - don't review / merge.


Suggestions

Expose Toast.text to allow the user to specify their own fonts/styles/etc. While you're at it, why not expose Toast.bg as well?
Set Toast.text and Toast.bg scrollFactor to 0, 0 so that the toast window is aligned with the screen.

Yes, the Toast class is pretty much in alpha and is underdeveloped, I haven't even used it anywhere. Will make it better 😃


Interpreter: Use dense stack frames

Whenever a function is called a new stack frame is created.
The stack frame contains information required for the function execution such as last block, current block as well as the set of registers that the function execution needs.
Currently the stack frame uses its own Vec under the hood for its registers. Thereby creating new stack frames also means freshly allocating space for the used registers. To compensate the costs the EvaluationContext caches previously used stack frames and allows to reuse their allocations.
However, certainly the registers from two consecutive functions calls very likely live in very different memory regions which is not cache efficient.
A better method is to use one global stack: Vec<u64> and introduce a stack of stack pointers or function frame indices frames: Vec<usize>. Whenever a function is called the current stack size is pushed onto frames and the stack vector is extended with the amount of registers the called function is going to use. This is possible since the amount of used registers per function is known up front. After extension the function inputs are written to the respective first N registers of the new frame and the stack pointer is set to point to the first register of the new frame.
When a function execution ends the global stack is truncated by the amount of registers the function used. To retrieve the stack pointer of the previously called function frames.pop() is called and the current stack pointer is updated to the popped value.
This new approach better reuses the preallocated areas of the global stack vector. Also registers of consecutive functions calls are potentially closer together in memory and therefore cache efficiency is increased. Fewer small allocations are performed overall. There is no longer a need to cache function frames since there is only going to be one global stack.
Note: There is still a need for function frames for the current and last visited basic block of an executing function. However, this is a very small and fixed amount of information that won't require caching and can be put into the frames vector besides the stack pointer.

Implemented in https://github.com/Robbepop/runwell/commit/0b64065786e1a96bca17eba3c1ccb8238cf2c5f0. Closed.


Allow updateName by opentelemtry Api.

We use the  plugin api to write a custom Hessian(http://hessian.caucho.com/doc/) plugin.  and want to update the span name, the span is created by the servlet plugin, and updated by the spring mvc plugin. So
span.updateName(), wich  callwithName(name, PRIO_DEFAULT), would not change the name.
Should  change the span.updatename to  call  withName(name, PRIO_USER_SUPPLIED)?
I found the apm api plugin setName call `withName(name, PRIO_USER_SUPPLIED)``

Hi @eisig thanks for reporting this!
Haven't had a deeper look yet, but it seems like your fix withName(name, PRIO_USER_SUPPLIED) is correct.
We will add this fix alongside with a test.


Develop into Master

This PR adds the necessary dependencies and improves the documentation.

@renancouto Don't we need a CONTRIBUTING.md?


git submodule issues when cloning

Describe the Bug
Running into the following error when trying to clone astra-sim.
fatal: remote error: upload-pack: not our ref 6504d0107372806ba40731026b52e97132ec2a75
fatal: Fetched in submodule path 'extern/network_backend/ns3', but it did not contain 6504d0107372806ba40731026b52e97132ec2a75. Direct fetching of that commit failed.
fatal:

This causes compilation to fail.

Note: I tried on both a remote server and my local machine running ubuntu22 and MacOS Ventura, respectively. Still no luck.

Steps to Reproduce
git clone --recurse-submodules git@github.com:astra-sim/astra-sim.git

And, yes. I do have an ssh key setup and am successfully authenticated as described in #124.
ssh -T<EMAIL_ADDRESS>
Hi wkaisertexas! You've successfully authenticated, but GitHub does not provide shell access.

Expected Behavior
The submodules should be cloned.

Hello @wkaisertexas, I just created PR(https://github.com/astra-sim/astra-sim/pull/180) to solve this issue.

Thanks!

Hi @wkaisertexas , apologies for the inconvenience. PR #178  solves this issue. Please retry cloning the repo, and let me know if this works. If, by any chance, you have astra-sim/extern/network_backend/ns3, (NOT ns-3 << This is the correct directory that should stick with you) go ahead and delete the ns3 directory.
Basically, we changed the NS3 backend submodule with a completely new repo. The new repo took over the same repo address as the old submodule (astra-sim/astra-network-ns3), but since the commit hash was different, you were unable to clone properly.


Can you post a demo video

Absolutely @Harshit-shrivastav. See the ReadMe for a few samples.

Thanks for it!


Cache with many urls

Hello @eneajaho!
Then, I've got to implement your lib in my project. It worked so good. I've implemented it in two projects. However, one of this, I'm getting a problem. Let me explain my context.
We have a site, which, many users access it by different urls. Our company has developed a site which can be hired by different customers. The layout, informations, site's configures, among others, are showed depending on the URL accessed. Example:
https://urlone.com
https://urltwo.com
That is, our customers have theirs domains. Their domains access our angular project. And, in our API, we've done a filter to identify which URL is being accessed. From this, we return the customer's site.
Then, the problem is: the cache from your lib is working as expected. However, due to cache, sometimes, in a fast moment, it gets the cache of the last site accssed. Example:
I requested:  https://urlone.com. Ok, worked so good with cache. After it, I requested: https://urltwo.com.
In a fast moment, on the first load, it showed some images of the first site (urlone). I understand the why: the lib makes cache of the last page accssed (I've configured the data for 5 seconds). But, it was a problem for this context. Is it possible I make cache for differents URLs?
I hope I was clear.
Anyway, I liked your lib. As I said before: I've implemented it in two projects. For the first one, which it has just one URL, it got very, but very good. Congrats for this project.

When I said URL's, I meant "domain".

Hello @baucosta
I would like to know if you use the InMemoryCacheHandler (the default one) or the FileSystemCacheHandler?
One solution is to create two ISRHandler class instances (one for each site). Then on the route handler you check for the domain of the request, and serve from cache or revalidate cache for that domain.
Something like this:
  const domainOneIsrHandler = new ISRHandler({
    indexHtml,
    invalidateSecretToken: 'MY_TOKEN',
    enableLogging: !environment.production
  });

  const domainTwoIsrHandler = new ISRHandler({
    indexHtml,
    invalidateSecretToken: 'MY_TOKEN',
    enableLogging: !environment.production
  });

  server.get('*',
    // Serve page if it exists in cache
    async (req, res, next) => {
        if (req.get('host')=== 'domainOne') {
            return await domainOneIsrHandler.serveFromCache(req, res, next);
        }

        if (req.get('host')=== 'domainTwo') {
            return await domainTwoIsrHandler.serveFromCache(req, res, next);
        }

       // don't forget to add a default case handler here, maybe create a default isr handler
    },
    // Server side render the page and add to cache if needed
    async (req, res, next) => {
        if (req.get('host')=== 'domainOne') {
            return await domainOneIsrHandler.render(req, res, next);
        }

        if (req.get('host')=== 'domainTwo') {
            return await domainTwoIsrHandler.render(req, res, next);
        }

       // don't forget to add a default case handler here, maybe create a default isr handler
    },
  );

Hope it helps!

Hi @eneajaho ! Thanks for your answer.
So, I thought that your lib had a way to make it. But, that's not a problem. This idea might work as well. I'm gonna make it here. In my case, there are many customers, not just two. Anyway, I had an idea from your comment.
I appreciate your attention.
Best regards

I forgot to let you know. I'm using InMemoryCacheHandler.

Your case is very specific and I don't think I'll add support for it.
What you can also do is to to create your own cache handler class that implements CacheHanlder interface. This way the implementation on outside is the same as now. The custom cache handler will handle the urls differently based on the usecase. You can check how the InMemoryCacheHandler class handles stuff so you can easily create custom logic from it.
Let me add an example here.

So, here's a repository that I have not tested but just added code on how I think it can work.
repo: https://github.com/eneajaho/isr-multiple-domains
here's how the default in memory cache handler works: https://github.com/eneajaho/ngx-isr/blob/main/projects/ngx-isr/src/lib/cache-handlers/in-memory-cache-handler.ts
implementation of CacheHandler that can handle multiple domains: https://github.com/eneajaho/isr-multiple-domains/blob/master/in-memory-multiple-domains-cache-handler.ts
usage of that cache handler: https://github.com/eneajaho/isr-multiple-domains/blob/master/server.ts#L29
So you can add a list of domains when you configure the cache handler and it will handle all the other parts.
That's it, that's all you have to add/change.

Very good, you've ever thought an implemention about it.
Nice @eneajaho . I'm gonna try it.
Thanks for your attention.

Happy to help! Let me know about anything else.
I'm closing this issue as there are 2 solutions for it in the comments, but feel free to reach out again.


fix(api): Fix row order in labware.create

overview
Fix row order in labware.create. Fixes #1748
changelog

Reverse row order in labware.create so that the top row is A

review requests
See steps to reproduce in attached bug ticket

Tested on Sunset, works as expected with same protocol. On a separate note, I did see some serial read failures that did not interfere with the run, but I've seen these on a few machines lately so they might need some attention (cc @andySigler)


Add TOC

Added TOC
Fix heading level for - import a component - examples
Remove dot in front of title Display Lint...

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

This looks great, thanks!


deprecation of throw syntax

As of 0.4.10 throw has been deprecated in favor of assert(), require() and revert(). Would a PR to replace throw accordingly in the ethereum API be welcomed?
I'm new to Solidity so I didn't know if throw was being kept for backwards compatibility or another reason.

Ah, my apologies. I was looking at the wrong file.
Cheers

It is indeed being kept for backwards compatibility for the whole 0.4 subversion. Our pre 0.5 api leverages the newer methods.


python311Packages.torchaudio: 2.1.2 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.torchaudio is: PyTorch audio library
meta.homepage for python311Packages.torchaudio is: https://pytorch.org/
meta.changelog for python311Packages.torchaudio is: https://github.com/pytorch/audio/releases/tag/v2.2.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.2.0 with grep in /nix/store/8n7j1fjr5c15kcbgfhwc7lf95jqaznw4-python3.11-torchaudio-2.2.0
found 2.2.0 in filename of file in /nix/store/8n7j1fjr5c15kcbgfhwc7lf95jqaznw4-python3.11-torchaudio-2.2.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.fairseq
python311Packages.speechbrain
python311Packages.torchaudio

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8n7j1fjr5c15kcbgfhwc7lf95jqaznw4-python3.11-torchaudio-2.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/9fe9f1942993f17b3d5be51eb499811de2be40af#python311Packages.torchaudio

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8n7j1fjr5c15kcbgfhwc7lf95jqaznw4-python3.11-torchaudio-2.2.0
ls -la /nix/store/8n7j1fjr5c15kcbgfhwc7lf95jqaznw4-python3.11-torchaudio-2.2.0/bin

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

1 package failed to build:

python311Packages.fairseq

2 packages built:

python311Packages.speechbrain
python311Packages.torchaudio

Maintainer pings
cc @junjihashimoto for testing.

Already on master.


Invalid cfg directives do not throw errors

Problem
The following code does not generate an error but silently ignores the directive:
define pipeline main
pipeline
  #!snot = "badger"
end;

Possible Solution(s)
This should cause a helpful error

fixed


New Fence not blocking thread until readpixels operation is done.

Hey guys,
So I am working on an app that is using filament. I started on this project a year ago and integrated into my app which basically uses modified Suzanne sample app code. I had some problems initially with reading from buffer and painting on my app using readpixel and pixelBufferDescriptor but I figured that out and my app is no longer crashing and copying the buffer nicely to my app thanks to help from you guys. I noticed that you guys had added ambient occlusion to filament which I had requested as a feature a while back and I wanted to try that on my app.
I solved the crash when I  readpixel to read data from filament buffer to my app buffer by blocking the current thread until the readpixel is done by calling fence::waitAndDestroy like this
Texture::PixelBufferDescriptor pb(image_data, area * 4, Texture::Format::RGBA, Texture::Type::UBYTE), [](void* buffer, size_t size, void* user) { 					CaptureState* state = static_cast<CaptureState*>(user);                                         // Copy filament buffer to my app buffer 				}, currentState); renderer->readPixels(0, 0, winwidth, winheight, std::move(pb)); Fence::waitAndDestroy(mEngine->createFence(Fence::Type::SOFT), Fence::Mode::FLUSH);
Now I noticed Type::SOFT was moved into FFence.h and createFence by default uses Type::SOFT ,so I tried this to block the current thread until the reading pixel is done Fence::waitAndDestroy(mEngine->createFence(), Fence::Mode::FLUSH);
But now it's not blocking the current thread until the reading is done and I am back to seeing crashes again. I do use the PixelBufferDescriptor callback to know when read is done and that's where I do the copying from filament buffer to my app buffer. The problem is I need to block this current filament thread until reading is done otherwise after endframe() the program execution continues and exits my app thread ( same thread as filament) and pixelbufferdescriptor callback is only invoked on the next render callback from my app. So essentially the program ends up copying older frame data to the next frame buffer in my app and this eventually causes crash. How do I properly block the current thread now until the read pixel is all done? I have a feeling this is due to Fence changes.

Try using mEngine->flushAndWait() instead of Fence::waitAndDestroy.
FYI we do something similar in filament/test/filament_rendering_test.cpp. We render, issue a readPixels and then call flushAndWait to block until the callback has executed.

Thank you so much that worked !!!
Another problem I am having is this fix that you pointed me to not so long ago https://github.com/google/filament/issues/1441#issuecomment-555283398 that I applied to the year old build worked then but now that I got the latest build, I tried applying the same fix, rebuild filament.lib and the alpha values are incorrect again so images doesn't show as transparent. @bejado

That fix still works for me with the latest release. Have you made sure you're clearing the screen with 0, 0, 0, 0 and creating the SwapChain with the SwapChain::CONFIG_TRANSPARENT flag?

Yeah I made sure again I am clearing screen like this
view = engine.createView();   view->setClearColor(math::float4(0.0f, 0.0f, 0.0f, 0.0f));   view->setName(name.c_str());
creating swapchain like this
       void* nativeWindow = ::getNativeWindow(mWindow); 	mSwapChain = mFilamentApp->mEngine->createSwapChain(nativeWindow,          SwapChain::CONFIG_TRANSPARENT);
and I show and hide my ibl environment background like this,
	if (bSkyboxChecked) { 		IBL* ibl = FilamentApp::get().getIBL(); 		FilamentApp::get().getScene()->setSkybox(ibl->getSkybox()); 	}  	else { 		FilamentApp::get().getScene()->setSkybox(NULL); 	}
Maybe clearing skybox like that doesn't clear the background in alpha anymore ?

That all seems right to me. You can take a look at my branch, bjd/windows-transparency to see how I'm testing. Try building and running the gltf_viewer sample. I've added a readPixels call which will read from the framebuffer and log the bottom-left pixel values. Note how the alpha value changes from 0 to 255 if you right click and drag the model to the bottom left of the screen.

I thought you said we need to set the clear color to 0 0 0 0, why would you set the alpha to 1 ?
window->mDepthView->getView()->setClearColor({0, 0, 0, 1});
But regardless if it set it to 0 or 1 or clear the way I did it, I am not getting transparent value.

That line of code is for clearing the depth view, which isn't used in the gltf_viewer sample. The actual clear color is set here:
view->setClearColor(LinearColorA{ 0 });

If you run the sample, does it output the correct alpha values?

Yes running the sample does give me correct alpha values.
It is working now when I copied filament buffer using nested for loops, for some reason the apps copying utilities seems to ignore alpha, but that's not filament's issue.
Thanks for your help !

Glad it's working now.


installKotlinterPrePushHook not working using 3.8.0

Pretty sure that's the reason. I updated the instructions here https://github.com/jeremymailen/kotlinter-gradle#git-hooks and also pushed 2.4.1 which will add this task even if there isn't a kotlin source code plugin present on the root project.

The same problem in 3.8.0 version. Helps only val installKotlinterPrePushHook by tasks.creating(InstallPrePushHookTask::class). We use kotlin-android
Originally posted by @AlexKuz13 in https://github.com/jeremymailen/kotlinter-gradle/issues/142#issuecomment-1250804896

The latest version is 3.12.0 can you verify the issue still persists? If not - can you share a repro project?

I'll close the issue for now - please let us know if you can reproduce the issue on the latest version (a repro project woul be much appreciated 🙏 )


Pausing Flash video in IE8 not documented?

Hi John,
First off, love mediaelements.js! Really don't know how we could live without it!
I ran into an issue this morning and thought I needed to post it here. First, a little background. I am using the built-in mediaelements.js plugin in the WordPress core for this site and was having difficulty firing a pause() method from my script. The need is to pause and hide the video when a user clicks on a navigational element. For browsers supporting HTML5 video this was not a problem. For IE8? Big problem (of course).
For HTML5 compliant browsers I simply called (in jQuery) where "video_id" is the ID of the video element:
$('#video_id')[0].pause();
In IE8, this obviously did not work and just threw up this error:
Message: Object doesn't support this property or method
Since IE8 is using the Flash fallback I researched various methods for controlling the playback using Javascript and Flash. Nothing worked that I found. I was about to give up when I found this old article. While the method described in the example didn't work it did offer me clues. I noticed when I tried this using the ID of the Object tag (which is different than the video ID) I was not getting any Javascript errors like before. So I decided to dive deeper into the object.
I first tried sending the object using the ID of the Object tag containing the Flash .swf to the console to see what I would get using:
console.log(window.flash_object_id);
Sending the object to the console resulted in:
[object]
So I found this post to figure out how to inspect the entire object and send it to the console. It resulted in a long list of properties and methods. At the end of the list I found this method:
pauseMedia: function () {
  return eval(instance.CallFunction("" + __flash__argumentsToXML(arguments,0) + ""));
 }
Cool! This is what I needed. Now from my Javascript I can pause the video by calling this on my click event:
window.flash_object_id.pauseMedia();
Or with jQuery:
$('#flash_object_id')[0].pauseMedia();
Finally, a solution! I simply test for IE8 and call the pauseMedia() method of if not IE8 call the pause() method.
Forgive the long post, but I thought you needed to understand how I got to this solution. If you're still with me, my question is where is this documented? It's unclear if the pauseMedia() method is something inside your .swf file or if it's built into the Flash player. (I'm using the latest Flash player 11 in my test IE8 browser.)
Please let me know if there is an easier way that I overlooked somewhere. Or if this is something that is really unique to my situation. Either way I hope this post helps others with supporting IE.
Chad

@chadwickcole Closing old issues. If you'd like to reopen this, let us know. Thanks!


Environment problem

Thanks for your amazing project.
I face some problems when I set up the environment. Is the installation guide can still work now?
Thank you

@1gfgfg
Hello, thanks for checkout out our repository.
Yes, the installation guide should still work. Can you please provide more information about the problem you are facing?

Maybe it's my problem because I run the setting on google colab.

@monjurulkarim
I still get wrong when I run
compile & install
pip install -v -e .
python setup.py install
in 1.1 (Optional) Setup MMDetection Environment

@1gfgfg
Although we haven't tested our repository specifically on Google Colab, we'd be happy to help you troubleshoot the issue and find a solution.
The error message you received, "Unknown CUDA arch (8.6) or GPU not supported," suggests that the CUDA architecture of your GPU might not be supported by the version of dependencies mentioned in our installation guide.
You need to verify GPU model and CUDA  compatibility. I also suggest checking the compatibility matrix or system requirements mentioned in the official documentation of the dependencies we listed (Torch, mmcv, mmdetection). Verify if your GPU's CUDA architecture is supported by these versions. If not, you might need to consider updating the dependencies to versions that are compatible with your GPU.
If nothing works, please note that the this part of the installation is optional. It is only necessary if you intend to utilize mmdetection for training and testing Cascade R-CNN models.

Hello author, I deployed the project, and there were some problems with the environment, please do the environment still work

Hello author, I deployed the project, there are some problems with the environment, can the environment still be used?


feat(init): write the git clone

https://github.com/rustwasm/create-wasm-app/pull/6 basically did the same as this.


"Lint on fly" customisable delay

I was looking for other issues surrounding this question, and found https://github.com/AtomLinter/Linter/issues/476.
However, I couldn't find any way to increase the delay between typing and linting. I like auto-linting, but prefer it to only trigger after x seconds, where x is higher than the current default.

we use @editor.onDidStopChanging which is provided by Atom.
It doesn't appear that it's customisable.

Thanks for the info. Given the quick-close, I assume there's no interest in changing this implementation?

@JeanMertz We just don't wanna re-invent the wheel and consume what's already provided by atom.

If someone were to create a plugin that monitored editor.onDidStopChanging and added a delay exactly how they want then executed linter:lint, it would be totally outside our control :wink:
With that hypothetical plugin in place you could disable lint on fly and I think you'd have the behavior you want.
I'm just going to leave this here.

@AsaAyers triggering linter:lint when the file hasn't been saved yet won't really do anything for non lintOnFly linters, 'cause they don't use bufferTexts they point their CLI linters to filePaths which wouldn't be modified unless you save. Except for atom-hasksell which is still a WIP by lierdakil.

That options should just prevent us from triggering lint when editing stops. lintOnFly linters trigger on save, why wouldn't they trigger on linter:lint?
If you're correct, then I'd consider that behavior a bug

lintOnFly triggers linters that doesn't care about the buffer.
The other linters are run when the file is saved, so this kind-of linters take the filePath and feed it to their CLI linter and get feedback,
Now linter:lint invokes both type of linters, so only linters who used the buffer text instead of filePath would work 'cause the changes wouldn't be guaranteed to have flushed to disk, and the linters that will work by this would be lintOnFly ones, and they're gonna be triggered when you stop writing anyway.

@AsaAyers  where can I find all the flags like for example lintOnFly to put on my config.cson file?
I cant find a list of all the available options.

You should be able to just find what you need under settings.


help center: Document reactivating a user in greater detail.

Adds info from the user reactivation modal to the help center page, following up on CZO discussion.
Modal

Before

After

@timabbott , was there anything else you had in mind in https://github.com/zulip/zulip/pull/21436#issuecomment-1072862453?

This is great, merged, thanks @alya!


Allow admins to change status to 'open' from 'admin'

Add option for an admin to change the status from admin to open

Fixes #42

Fixes #41

Looks good, thanks!


⚠ Bofrost.at has degraded performance

In 7b16d6c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2186 ms

Resolved: Bofrost.at performance has improved in a755150.


GetRates and GetRatesHttp

I have an issue with installing completely your ext to get the shipping rate and also how to figure out the usage of the cloud functions, currently experiencing this error although I have been able to add to my firestore the shipping details.
Errors : ext-calculate-rates-getRates

@andyhite


labwc-tweaks: unstable-2023-12-08 -> unstable-2024-01-04

Description of changes

labwc-tweaks: add update script
lawbc-tweaks: fix license
labwc-tweaks: add maintainer
labwc-tweaks: add dependence on xkeyboard_config
labwc-tweaks: unstable-2023-12-08 -> unstable-2024-01-04

Fixes https://github.com/NixOS/nixpkgs/issues/279659
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3242

Reviewed points
Result of nixpkgs-review pr 278985 run on x86_64-linux 1

1 package built:

labwc-tweaks

[X] package name fits guidelines
[X] package version fits guidelines
[X] package builds on ARCHITECTURE
[X] executables tested on ARCHITECTURE
[X] all depending packages build
[ ] patches have a comment describing either the upstream URL or a reason why the patch wasn't upstreamed

N/A: Patches are nix specific and self-evident

[ ] patches that are remotely available are fetched rather than vendored

N/A: Patches are nix specific